OAuth tokens, encryption at rest, and tenant isolation on every read
A backup is a copy of your most sensitive data. How bluefactory connects to your org, where it keeps that copy, and who can reach it are all decided deliberately, and written down here.
Every control, and the mechanism under it
Each item below names a control that ships today. Nothing here is a roadmap entry, and no certification is claimed.
Encrypted at rest and in transit
Backup data is encrypted at rest and every connection is served over TLS. You choose the region the data lives in.
OAuth, never passwords
bluefactory connects through Salesforce OAuth and stores refresh tokens, not credentials. Your password never reaches our systems, and you can revoke access from Salesforce at any time.
Tenant isolation on every read
Every query is scoped to your account server-side, from the session and never from client input. One tenant cannot read another's data.
Roles per module and per org
Grant each teammate No Access, Read Only, or Full Access, module by module and org by org, so rights in production do not leak into every sandbox.
IP allowlisting
Restrict sign-in to approved IP ranges, enforced per account on Enterprise.
Bring your own storage
Point backups at your own Amazon S3, Azure Blob, or Google Cloud bucket, so the data stays inside infrastructure you own and audit.
Impersonation-audited support
Support and admin access runs through audited impersonation sessions, so every action stays attributable to the real operator.
GDPR at restore time
Log a forget or rectify request once, and every restore honors it: records excluded, fields rewritten.
The Salesforce connection, end to end
Authorize once over OAuth
You grant access through Salesforce's own OAuth screen. bluefactory receives a token, never your password, and you can take it back at any time.
Run scoped, server-side
Backups and scans run against your org with the minimum access the job requires, isolated to your account.
Store where you choose
Encrypted results land in bluefactory-managed storage, or your own S3, Azure Blob, or Google Cloud bucket, in the region you select.
What bluefactory never does
Least privilege by default: each module asks only for the access its job requires, and nothing is granted speculatively. The same restraint, in writing.
- Store or ask for your Salesforce password.
- Move your backup data outside the region or storage you choose.
- Let one account read or restore into another's org.
- Request Salesforce permissions a module does not need.
- Bypass the audit trail on a data path.
- Touch your account in support without an audited impersonation session.
Send us your vendor questionnaire
Or ask for specifics: OAuth scopes, storage layout, the isolation model. We reply within one business day.