Your data is yours.

Export Anytime, Delete Anytime Live

An owner can export the whole workspace whenever they want, and anyone can export their own personal data. An owner can delete the workspace from Settings without asking us.

• Full export: every table as CSV and JSON, files and call recordings decrypted, in one zip with a SHA-256 hash for every file. The zip is encrypted while it waits and deleted after 7 days.
• Personal export: what the workspace holds about one person, for GDPR and CCPA requests.
• Delete: the workspace closes at once and can be restored for 14 days. Then every row, file and recording is deleted, the plan is canceled, phone numbers are released, connected accounts are revoked, and the company encryption keys are destroyed so backups can no longer be read. You get a certificate of deletion by email.
• We keep only the billing records the law requires and the security log entry of the deletion.

A Separate Encryption Key For Every Company Rolling Out

Each company gets its own AES-256 data key, created by AWS Key Management Service in us-east-1. Only a wrapped copy is stored; the unwrapped key lives in server memory for at most 5 minutes. Every encrypted value is bound to your company, so a value copied into another company cannot be opened. Key creation and rotation are written to a tamper evident log.

• Encrypted with your company key: secret settings and provider API keys you add, connected account credentials, Google, LinkedIn, Instagram and Facebook tokens, Sensei WhatsApp messages and queued replies, and archived Sales Floor call recordings.
• Encrypted with a platform key shared by all companies: Data Room documents and investor records, team chat and admin messages sent as encrypted, some social account tokens, and developer webhook secrets.
• Not encrypted field by field yet: most business records such as CRM leads and notes, email bodies, tasks, Sensei notes, call transcripts and finance notes, and uploaded files. These are protected by database and storage encryption at rest, TLS in transit and per company isolation, but people with database access could read them.

End To End Encrypted Chat Coming

Team chat that only the people in the conversation can read, with keys that stay on your devices. It is being built now and is not switched on yet. Until it is, use the encrypted option on a message for platform key encryption.

Companies Are Kept Apart Live

Every company table in our database has row level security, so a request made for one company only sees the rows of that company. Every request runs with the company it belongs to, and encrypted values are bound to their company.

What Our Staff Can See Live

Our support tools show account facts such as your plan, member count, usage and connection health, not your content. Every time staff open your workspace in those tools it is written to your audit log, and the Your Data page in Settings shows how often it happened in the last 90 days.

• A small number of engineers can reach the production database to keep it running. Fields encrypted with your company key cannot be read there; other fields can.
• Access to your content that needs your approval first (break glass) is coming and is not built yet.

Where Your Data Lives Live

In the United States. The database is Neon Postgres in AWS us-east-1 (Virginia). Encryption keys and files are in AWS us-east-1. The app servers run on Heroku in its United States region.

SOC 2 Coming

We are preparing for a SOC 2 Type I audit and track every control in our own Compliance app. We are not SOC 2 certified and do not have a SOC 2 report yet. We will say so here when an independent CPA firm issues one.

Subprocessors

Companies that process data so Founder Balance can run. We update this list when it changes.

Questions, a security report or a data request: write to support@founder-balance.com.