🛡️
Data & Security

We read your org's metadata — never your data.

Hubbl analyzes your Salesforce org through a read-only, credential-free connection, builds its picture from metadata alone, and deletes everything it retrieved when the scan is done. No transactional data. No human access. No PII or PHI.

OAuth2 · metadata-only · nothing retained by default
How it works

Secure Salesforce Org Analysis

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.

☁️
Your Salesforce org
Production, sandbox, or a prospect's
1 – N orgs
1
Authorize
OAuth2 · read-only
🔒
Secure scan environment  encrypted · temporary · no human access
2
🗄️
Temporary scan container
Reads metadata + object record counts into isolated, encrypted storage
3
Analyze
📊
Aggregated analysis
Derived, anonymized findings — the only thing that leaves the container
4 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.
5
Empower
Hubbl App & MCP
Security Intelligence
Process Intelligence
Industry Benchmarks
Prioritized Recommendations
Org Monitoring
Hubbl MCP
1
Authorize

A secure, read-only OAuth2 connection to the org — no credential handoff.

2
Scan

Metadata and record counts collected to a temporary, encrypted container no human can access.

3
Analyze

Metadata is turned into aggregated, anonymized analysis.

4
Purge

Token and all retrieved metadata are deleted once analysis completes.

5
Empower

Findings surface across the Hubbl app and MCP — security, process, benchmarks, recommendations, and monitoring.

✓ What Hubbl reads
Object & field definitions, flows and automations, profiles and permission sets, installed packages — and object record counts.
✕ What Hubbl never touches
Field values, customer records, and any personal data (PII / PHI). The picture is built from structure, never contents.
Data handling & security

Built so security teams can say yes.

The controls behind the diagram — how the connection, the data, and the people are governed.

🔑

Secure, scoped connection

The org is authorized over OAuth2 with a read-only, least-privilege scope. No admin credentials change hands, and the connection can be revoked at any time.

🙈

No human access

Metadata and record counts are collected to a temporary, encrypted container that no Hubbl employee can access. The analysis is automated end to end.

🧹

Purged when done

When analysis completes, the access token and all retrieved metadata are deleted — retained only if you explicitly schedule ongoing monitoring.

🔐

Encrypted in transit & at rest

All data moving to and held in the scan environment is encrypted. The limited personal data Hubbl stores — user names and emails — is encrypted as well.

👤

Least-privilege employees

Employee access is restricted to what each role requires. All staff sign data-security agreements, and workstations require encryption, antivirus, and compliance checks.

📋

Minimal personal data

Hubbl collects only user names, emails, and scan-request recipients — never the personal data inside your org. That's what keeps the scan PII/PHI-compliant.

The specifics

What Hubbl accesses — and what it doesn't.

How it connects
A secure OAuth2, read-only connection to your org. No credential handoff, no standing admin access — revoke anytime.
What Hubbl reads
Org metadata — objects, fields, flows, automations, packages, profiles, and permission sets — plus object record counts, collected to a temporary, encrypted container.
What Hubbl never retrieves
Transactional data, customer records, field values, and any PII / PHI. It never leaves your org, ensuring compliance.
Who can see it
No human has access to the scan container. Analysis runs automatically, and results are aggregated and anonymized.
What's retained
Nothing by default. The token and retrieved metadata are deleted on completion — kept only if you schedule ongoing monitoring.
Personal data collected
Only user names, emails, and scan-request recipients — encrypted in transit and at rest.
Our partners

Built on GDPR-compliant infrastructure.

Hubbl runs on established, compliant providers — the same names your security team already trusts.

Salesforce
AWS
Auth0
Microsoft

Safe enough to run on any org.

See exactly what Hubbl sees — a credential-free, metadata-only scan in about two minutes, with nothing retained. For our full security program, certifications, and to request our SOC 2 report or a DPA, visit the Trust Center.

Questions? Port Moody, BC · support@hubbl.com