It reads your inbox. Here's exactly how we treat it.
Voix only works because you let it see your mail. We designed it so that trust is the easy part: minimal access, nothing sent without you, and a one-click off switch.
Read-only to brief you
Your first sign-in asks for gmail.readonly and nothing else. Voix reads your recent mail on demand. It does not modify, label, or delete anything.
You approve every send
We ask for gmail.send later, in context, the first time you approve a drafted reply. Approve none and Voix never holds permission to send at all. Nothing leaves your inbox on its own, ever.
We don't train on your mail
Your email is processed to rank and draft. It's handled by our AI provider under commercial terms, never used to train AI models, and never sold or shared with advertisers.
Encrypted at rest
Data lives in Supabase on AWS in the US (us-east-1), under EU Standard Contractual Clauses. Traffic is TLS 1.2+, storage is AES-256 at rest, and your OAuth token is encrypted in a server-only table.
You can delete it all
Disconnect Gmail or Slack in one click, or delete your account: every row tied to you is erased within 30 days, backups within 90.
Minimal scope, by design
gmail.readonly to start, gmail.send only once you approve a reply, and a read-only calendar scope only if you add your calendar. Not modify, not labels, not full mailbox access, even though those would enable more features.
Your rows are only yours
The database itself enforces the wall. Row-level security means a query can only ever return rows carrying your own user ID, so one account cannot reach another's even if the app above it got something wrong. An automated test proves it on every change.
gmail.readonlyReads about the last 14 days of your Primary and Updates mail, up to about 90 messages, to pull the sender, subject, and the message text for ranking. Without it, Voix can't tell you what's in your inbox.
gmail.sendNot requested at sign-up. Google only shows you this permission the first time you approve a drafted reply, and you can decline. Once granted, it sends a reply on your behalf from your own account, only after you approve a draft. Every send is an explicit action. Voix never sends autonomously.
We submitted these scopes for Google's restricted-scope verification on 6 August 2026, and Google's review is in progress. It is not finished, and the CASA security assessment it leads to has not started. More on how we handle your data lives in the Privacy Policy.
Mail.Read · Calendars.Read · Chat.Read · Mail.SendIf you connect Microsoft 365: Mail.Read and Calendars.Read to read your Outlook mail and calendar, and Chat.Read only where Teams reading is switched on. Mail.Send is not asked for when you connect. Exactly like Gmail, it is requested later, the first time you approve a reply to send from Outlook.
im:read · im:history · users:read · search:read · chat:writeIf you connect Slack: im:read and im:history to read your direct messages, users:read to turn sender IDs into names, and search:read to find your channel mentions and answer questions across Slack. chat:write is used only to send a reply you have already approved, never on its own.
You will see a warning from Google. It is accurate.
When you connect Gmail, Google shows a screen saying it hasn't verified this app, and the button to continue is labelled “unsafe”. That screen is correct. Google's full verification is a months-long security review we have not done yet, and we would rather tell you before you see it than explain it after. Nothing about the sign-in itself changes: it is read-only, it cannot delete or change anything in your mailbox, and you can revoke it from your Google account at any time.
If that screen is a no for you, that is a reasonable no. Disconnecting is one click, and deleting your account revokes Google's permission at Google's end and removes every row we hold, rather than just hiding it.
Every company that touches your data, and what it sees.
Read-only sign-in. Sending is a separate permission, and nothing sends without your tap.
Your briefing content auto-deletes after 30 days. Full email bodies are never stored.
Some of our processors are in the US. Transfers from the EU are safeguarded by Standard Contractual Clauses (SCCs). Full detail in the Privacy Policy and DPA.
| Processor | What it sees | Used to train AI? | Retention |
|---|---|---|---|
| SupabaseDatabase · AWS us-east-1, US | Your account row, encrypted connection tokens, and the briefing output: the transcript and the ranked list. Never full email bodies. | No. Infrastructure only. | Briefing content auto-scrubbed after 30 days. Everything deleted when you delete your account. Transfer: SCCs. |
| AnthropicClaude, ranks your messages and drafts replies · US | Transiently, per briefing: sender, subject, the full text of each message (capped at about 6,000 characters per email and marked where it is cut), and text extracted from PDF or Word attachments, from your last 14 days. Voix stores none of it. | No. Anthropic's commercial API terms exclude training on API data. | Anthropic auto-deletes API inputs and outputs within 30 days. We have not yet signed a zero-data-retention addendum, and we say so plainly. Transfer: SCCs. |
| GoogleGmail API, sign-in, and Cloud text-to-speech · US | Your Gmail, through the read-only scope you grant. The text-to-speech service receives the briefing transcript to generate the audio. | No. Google's Workspace API policy binds Voix never to train a model on your Gmail data, and what we send is processed only to provide the service. | Transient processing. Transfer: SCCs. |
| VercelApp hosting and server logs · US | Request traffic and server logs. Not your mailbox. | No. | Standard log retention. Transfer: SCCs. |
| ClerkSign-in · US | Your name, email, and login session. | No. | Until account deletion. Transfer: SCCs. |
| PostHogProduct analytics and error monitoring · EU, Frankfurt | Anonymous usage events only. Cookieless, off until you accept the banner, never email content, session replay disabled. | No. | EU-resident. |
| StripePayments · US/EU | Your card details go to Stripe directly. Voix never sees the card number. | No. | Per Stripe's terms. Transfer: SCCs. |
Only if you use the feature: Resend (morning email), Microsoft (if you connect Outlook), Slack (if you connect Slack), Twilio and Vapi (private calls, not yet active), Meta (WhatsApp and Instagram business inboxes, not yet active), Modal and ElevenLabs (signature-voice synthesis and voice evaluation, not yet active). Same rules: no training, minimum necessary data.
Deletion and export are self-serve (GDPR Art. 17 and 20): deleting your account revokes the Google and Slack grants provider-side, then removes every row.