Status
zonask is in development; this notice describes the processing as designed, and features that are not built yet are described as planned.
Email content
zonask never stores the content of your emails; it reads it in memory to decide what needs you and drops it when the request ends.
Content never reaches the database, logs or error reports.
To send your daily summary, zonask asks Google for permission to send email (gmail.send) from your own account, and uses it only to send the summary from that account to itself.
zonask also asks Google for permission to manage drafts (gmail.compose), and uses 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 asks Google for access to the files it creates in your Google Drive (drive.file), and uses 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.
What is processed
- Never stored: email bodies, message text, comment text, attachments and media are processed in memory only and never stored or logged.
- Sensitive and short-lived: the subject or first line, the sender or author label and the AI summary are held in encrypted columns with your tenant's data key.
- History: provider ids, role, category, action, tasks, blocks, labels, learned rules and the audit log, held in Supabase Postgres in Frankfurt with row-level security.
- Secrets: OAuth refresh tokens and app passwords, protected by envelope encryption with your tenant's data key, which is wrapped by a master key.
Email sync stores the subject and sender of each new email, encrypted, for 30 days; whether the subject stays stored at all, or only the AI summary, is not yet decided.
To decide whether a new email needs you, zonask reads its content in memory, with names, addresses and numbers replaced, and keeps a one-sentence AI summary, encrypted, which is removed with the subject after 30 days; the content itself is never stored.
Google user data
zonask asks for access to your Google account only through Google's consent screen, and uses each permission for one feature:
- Gmail, read only: zonask reads the subject, sender and date of new emails to show them on Today and to decide what needs you, and reads the text of an email in memory only when the role it belongs to asks for tasks or updates.
- Gmail, send: when you switch on the daily summary, zonask sends it from your connected account to that same address and to no one else.
- Gmail, drafts: drafting replies is planned; zonask will ask for this permission only when you switch drafts on.
- Google Calendar: zonask reads your events to show your day; event titles are stored encrypted and removed after 30 days.
- Google Tasks: zonask reads your Google Tasks.
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.
Read the Google API Services User Data Policy.
Google user data is used only for the features above, which you see in zonask.
Google user data is never sold.
It is never used for advertising.
It is never used to train or improve general AI models; the rules zonask learns from your corrections stay with your own account.
People do not read it, except with your agreement, for security reasons such as investigating abuse, or to comply with the law.
It is shared only with the sub-processors below, which process it for zonask.
When you disconnect a Google account, zonask revokes its access at Google and deletes the account's record.
Where your data is hosted
The app runs on Vercel in the fra1 region (Frankfurt).
The database and sign-in run on Supabase in Frankfurt.
Frankfurt is in the EU, which Switzerland recognises as having adequate data protection under the revFADP.
Sub-processors
- Vercel: hosting, scheduled jobs and the AI Gateway.
- Supabase: sign-in, the database and background queues, in Frankfurt.
- Google Cloud: the OAuth client and the Google APIs only, and Google sign-in through Supabase Auth.
- TypeSafe AI, through the Vercel AI Gateway: deciding what needs you.
- Anthropic, through the Vercel AI Gateway: the one-sentence summary.
- Stripe will be added later for billing.
Every call through the AI Gateway is made with zero data retention.
No other company processes your mail; zonask uses no mail aggregator.
Retention
- The subject or first line, the sender label and the AI summary are redacted after 30 days.
- History is kept until you delete your data.
- Secrets such as OAuth refresh tokens are kept until you revoke access.
Deletion
Each tenant has its own data key, and deleting a tenant key makes that tenant's encrypted data unreadable.
Delete all my data is built but not yet live; once it is, it will revoke your Google access, remove the rows and destroy the tenant key after a confirm step.
Backups keep the wrapped tenant key until they expire, so deletion is final for each backup when it expires.
Your rights
Under the Swiss revFADP and, where it applies to you, the EU GDPR, you can ask for access to your data, rectification, erasure, restriction of processing and data portability, and you can object to processing.
Where processing rests on your consent, you can withdraw your consent at any time, for example by disconnecting an account.
You can complain to a supervisory authority: in Switzerland the Federal Data Protection and Information Commissioner (FDPIC), in the EU the authority where you live or work.
Controller
The legal entity that operates zonask, and so the controller, is not yet decided; its name and address will follow.
Until then, privacy requests go to the contact below.
Contact
Questions and requests go to michal.myszkowski@cx-advisory.com.