Privacy and security

Every control on this page is planned; the overview has the current status.

What will be readCopy Anchor Link

Email and message content will be processed in memory and dropped when the request ends.

Items that a role has switched off will never have their body fetched, because the role matrix will decide before any content is requested.

Mailbox, message and comment text will be treated as data and never followed as instructions.

When you discuss your daily brief in the chat, the brief goes to the assistant as marked data after your question, never among zonask's own instructions, because its lines come from other people's emails.

The notice about an overdue obligation says only since when an obligation is overdue; its title and counterpart stay encrypted. An older notice that still named them is rewritten that way the next time your notices are read.

zonask also reads the mail you send, in memory only, to find what you promised and what you wait for; it stores none of that mail, only the commitments you approve.

A contract you ask zonask to read, uploaded or attached to an email, is read once in memory and not kept: only the dates it found are stored, encrypted, as a proposal for you to confirm, and the file never goes to Drive.

What will be stored and what will notCopy Anchor Link

Email bodies, message text, comment text, attachments and media will never be stored and never logged.

The subject or first line, the sender label and the AI summary will be stored in encrypted columns with a key per tenant, and redacted after 30 days.

History such as provider ids, role, category, action, tasks, learned rules and the audit log will be kept in Supabase Postgres in Frankfurt with row-level security.

Logs will be structured and will hold no content.

Compute and the database will run in Frankfurt, in the EU.

The sub-processors will be Vercel, Supabase, Google Cloud, TypeSafe AI and Anthropic, both through the Vercel AI Gateway, and Stripe later for billing.

TokensCopy Anchor Link

OAuth refresh tokens will be protected with envelope encryption, using the tenant's data key stored in Supabase and wrapped by a master key held as a sensitive Vercel environment variable, and kept until they are revoked.

Google access will use least-privilege scopes: read-only Gmail access, Calendar and Tasks, with modify access added only for labels.

zonask will also ask for permission to send email (gmail.send), and will use it only to send your daily summary from your own account to itself.

zonask will also ask for permission to manage drafts (gmail.compose), and will use it only to save the reply and forward drafts your standing orders prepare in your own mailbox; you review and send them yourself, and zonask never sends them.

If you keep expenses with zonask, it will ask for access to the files it creates in your Google Drive (drive.file), and will use it only to save the receipts you keep with zonask in a zonask folder there; it cannot see your other files. zonask keeps the file's id and the receipt's amounts, encrypted, not the file.

If you set up the SEO and GEO agent, zonask asks for read-only access to your Search Console data (webmasters.readonly) only for the Google account where you choose Allow Search Console, and uses it only to read the numbers of the properties you pick; it does not store them, and Remove Search Console stops it.

For each connected account, Settings will show which of these permissions Google granted, and a reconnect link for any that is missing.

When Google no longer accepts an account's access, the account will be marked for reconnecting; reconnecting will store the new token for that same account, and Disconnect will revoke the token at Google and delete it.

Every AI Gateway call will be made with zero data retention.

zonask's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data will never be sold, used for advertising or used to train general AI models.

MCP clients will receive audience-restricted tokens and rotating refresh tokens, with a read-only token as an option.

Second brainCopy Anchor Link

You will be able to connect your second brain, a notes vault that runs as an MCP server, under Settings, Second brain, with its https address and a token.

The token will be stored only encrypted in the token vault, never shown back, logged or put in a URL, and sent only to the address you entered.

With the server's own sign-in instead of a token, zonask stores only the encrypted renewal token and keeps the short-lived access token in memory, never in the database.

The sign-in is tied to your zonask session, expires after ten minutes, and returns only to zonask's own fixed address.

zonask will connect only to an https address with a public name, and will check the address again at every request.

zonask will search your second brain only with the day's role names and sender domains, never with email content, and will treat what comes back as data that is never stored or logged.

zonask will add a note to your second brain's inbox or ideas only after you confirm the exact note, and will never change, move or delete a note that is already there.

Disconnect will delete the connection, and Delete all my data will remove it as well.

Retention and deletionCopy Anchor Link

Each tenant will have its own data key, and deleting that key will make the tenant's encrypted data unreadable.

Deleting all data will remove the rows and destroy the tenant key, after a confirm step.

Delete all my data will first disconnect your Google accounts at Google, then destroy the tenant key, delete every row of your tenant and your sign-in account; a deletion that stops half-way will be finished automatically.