Preparing your workspace…
Preparing your workspace…
Security & privacy
Encrypted before it’s stored, walled off per workspace, screened before your AI reads it, and every app’s access revocable in one click.
At a glance
How we protect it
Your memories and the keys to your connected tools are encrypted before they are stored. Nobody browsing a disk or a backup can read them. Enterprise workspaces can add their own encryption key on top.
AES-256-GCM at the application layer for stored content and integration credentials.
Encryption keys rotate on a keyring: the previous key keeps old rows readable while an hourly job re-encrypts them under the new one.
Bring-your-own-key encryption on the Enterprise plan.
Every workspace is walled off from every other. Another customer's AI can never read your data — every request is bound to your workspace before it reaches storage.
Tenant isolation is enforced in the application layer: every workspace-scoped query resolves its tenancy server-side, gated in CI.
Postgres row-level security is enabled on every table as defence in depth.
Your AI apps connect by signing in with your account, the same way you approve any app on your phone. Each app's access key is stored as a one-way fingerprint, shown to you once, and you can revoke it whenever you want — effective immediately.
Standards-based OAuth 2.1 with PKCE and dynamic client registration for web AI clients.
API access keys stored only as SHA-256 hashes, shown once when created; revocable per client.
Everything synced from your documents and connected tools is checked for hidden instructions before it can enter your AI's memory — so a malicious message can't steer your assistant.
Prompt-injection screening runs on all integration-synced content at ingest.
Paste an API key or another secret by accident and it is replaced with a [redacted] marker before anything is saved.
Recognised credential formats are detected at ingest and replaced with [redacted:credential]; the rest of the item is kept.
Meetings, campaigns and plans show you a preview first, and nothing goes out until you approve it. Sensitive data stays unshared unless you turn it on.
Meeting invites are previewed before they are created; sensitive sharing categories are off in the default sharing policy.
Content is used to improve our models only while you have switched on “Improve our models” — and even then, only content you wrote yourself. Anything synced from your connected tools is never used for training, whatever you choose. Google data is used only to provide the features you turn on, under Google's Limited Use rules.
Training writers require a recorded opt-in in the consent ledger AND an authored source; integration-synced sources are refused.
Disconnect Google or Microsoft 365 from your last workspace and the data we synced from it is scheduled for permanent deletion 21 hours later — time to change your mind — then removed by the next hourly cleanup, so it is gone within 24 hours. A contact you have since made your own — moved into your pipeline, say — stays. Unlinking one workspace while others still use the connection archives that workspace's copy instead.
The last unlink of a Google or Microsoft 365 connection stamps a purge time 21 hours out; the hourly purge job hard-deletes every row past it.
Our server logs blank out passwords, access tokens, email addresses and the text of your content before a line is written. Error reports are scrubbed of email addresses, phone and card numbers before they leave our servers.
Structured logging redacts credential, email and content fields by key; every error-report hook scrubs PII and token-shaped values from messages, breadcrumbs and request data.
Your account
Your control
Retention periods, sub-processors and your rights are set out in the privacy policy. How to report a vulnerability is published in our security.txt.
Found a vulnerability?
For IT and security teams
Five permission scopes for AI apps: read, write, agents, integrations and admin.
Workspace actions are recorded, and every AI tool call is logged with its cost.
Session cookies the browser's scripts can't read, and passkey sign-in for every account.
Your own encryption key, multi-seat workspaces and team roles.
Talk to usTry it on your own data