How it works
We read metadata — never your data — and delete it when we're done. Hubbl connects read-only, builds its picture from metadata and record counts, then destroys the connection and everything it retrieved.
To a prospect, customer, or your Salesforce Admin
Production, sandbox, or multiple orgs
Reads metadata + object record counts into isolated, encrypted storage
Derived, anonymized findings — the only thing that leaves the container
Purge — on completion the access token and every byte of retrieved metadata are deleted (kept only if you schedule ongoing monitoring).
Never retrieved: transactional data, customer records, field values, and any PII / PHI. It never leaves your org — ensuring compliance.
Object & field definitions, flows and automations, profiles and permission sets, installed packages — and object record counts.
Field values, customer records, and any personal data (PII / PHI). The picture is built from structure, never contents.