Privacy Policy

How we use it

Your data is used to operate TheCabinet: routing directives to the right secretaries, maintaining your memory layer, and delivering outputs for your approval. We do not sell your data. We do not use your data to train third-party models. We do not share your data with advertisers or analytics brokers.

Memory and context

TheCabinet maintains a persistent memory layer on your behalf — this is core to how the product works. You may request a full export of your memory at any time, and you may delete it at any time. Deletion is permanent. Exporting your memory does not delete it; you must request deletion separately.

Desktop App

The TheCabinet Desktop App reads files from directories you authorise. It does not run in the background without your knowledge, and it does not transmit any file content to our servers without your explicit instruction as part of a Cabinet directive. You can revoke file access at any time from within the app.

Connected accounts (Google)

When you connect a Google account, TheCabinet requests only the access needed for the features you choose to use, and only after you grant it on Google's own consent screen. Google Calendar — to read your schedule and create events, with invitations, on your behalf. Gmail — to send email as you when you ask us to; we request send-only access and do not read your inbox. Google Drive — to create files and read back only the files TheCabinet itself creates or that you explicitly open with it; we cannot see the rest of your Drive. We use this information solely to perform the actions you request, store only what is needed to carry them out, and never sell it, use it to train models, or share it for advertising. You can review or revoke TheCabinet's access at any time at myaccount.google.com/permissions. TheCabinet's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect your data

Some of what you trust us with is sensitive: the Google account data reached through the scopes above (calendar entries, the files TheCabinet creates in your Drive, mail sent on your behalf), the OAuth tokens that authorise that access, and the documents and directives you hand to the Cabinet. These are the specific mechanisms we use to protect it.

• Encrypted in transit. Every connection between your browser, the Desktop App and our servers is encrypted with TLS 1.2 or higher (HTTPS, and WSS for live sessions). Plain HTTP is redirected rather than served, and certificates are issued and renewed automatically.
• Encrypted at rest. Google OAuth access and refresh tokens are never written to disk in readable form. Each one is sealed with Fernet authenticated encryption — AES-128-CBC with an HMAC-SHA256 integrity tag — under a key derived by HKDF-SHA256 from a server-side secret that exists only in the server's environment and is never stored in the database. A copy of our database on its own therefore yields no usable Google credentials.
• Least-privilege access. A token is decrypted only at the moment an action you asked for is carried out. Tokens are never returned in an API response, never written to logs, and never handed to the AI agents that execute your directives — an agent asks an internal broker to perform the call, so no prompt can extract the credential. Rotating the server-side secret invalidates every stored credential at once.
• Separation between customers. Every stored record carries your organisation's identifier and every query is scoped to it, so one customer's Google data cannot be served to another. Access to production infrastructure is limited to the named engineers who operate the service, over key-authenticated connections.
• Account security. Passwords are stored only as salted bcrypt hashes and cannot be recovered by us or by anyone reading the database. Session cookies are HttpOnly, Secure and SameSite-restricted, so they cannot be read by page scripts or sent over an unencrypted connection.
• Monitoring and audit trail. Sign-ins, permission changes, integration connections and disconnections, and errors are written to an append-only audit log, so unexpected access to a connected Google account is visible and reviewable after the fact.
• Revocation and secure deletion. Disconnecting Google inside TheCabinet deletes the encrypted token from our vault immediately. Revoking access at myaccount.google.com/permissions invalidates it at Google's end. When you delete your account we destroy the Google data we hold within 30 days, and our backups are a short rolling window of nightly snapshots, so copies age out within days rather than being retained indefinitely.
• Breach notification. If we confirm a security incident affecting your Google account data, we will tell you by email without undue delay and within 72 hours, including what was affected and what we recommend you do.

Data retention

We retain your data for as long as your account is active. If you close your account, we delete your data within 30 days, except where retention is required by law. Waitlist data is retained for 12 months, after which it is deleted automatically if you have not created an account.

Third-party services

TheCabinet uses large language model providers to power its secretaries. Directives and documents you submit are processed by these providers subject to their data processing agreements. We select providers that offer data processing agreements compatible with enterprise privacy requirements and that do not use submitted data for model training.

Your rights

You have the right to access, correct, export, and delete your personal data at any time. To exercise any of these rights, email us at contact@thecabinet.dev. We will respond within 30 days.

Contact

Questions about this policy? Email us at contact@thecabinet.dev. We are a small team and we will read it.