Security & privacy
Your inbox is yours. Triagd is just a careful reader.
We've written this page in plain English. The goal is to tell you exactly what Triagd does and doesn't do with your data — not to bury it under marketing.
OAuth, not passwords
We use Google OAuth (and Microsoft OAuth, when Outlook ships). Your credentials never touch our servers. You can revoke Triagd's access in your Google account at any time and we lose access immediately.
Encryption at rest
Refresh tokens are encrypted application-side with AES-256-GCM using a key we never log. Tokens are decrypted in memory only at the moment an API call is made. Beyond that, the underlying database (Supabase / AWS RDS) is encrypted at rest with AWS-managed keys.
What we send to AI
For classification we send sender, subject, snippet, and the first 1,000 characters of the body to Anthropic. For thread summaries (an on-demand action) we send the full thread. We do not send attachments. Anthropic does not train on our API traffic — this is in our DPA with them.
What we permanently store
Email metadata (sender, subject, snippet, received time, our classification, and the action items we extracted) lives in our database. We do not permanently store full email bodies. The first 1,000 characters are used in-memory at classification time and then discarded.
What we DO NOT claim
We are not a zero-access or end-to-end-encrypted service, because the product fundamentally requires reading your email content to triage it. If you need a service where the provider cannot read your data at all, Triagd is not that — and you should use a different tool. We say this explicitly because some competitors blur the line.
Row-level security
Every database table has Postgres row-level security: a query authenticated as user A can never read or modify a row owned by user B. The service-role key (which can bypass RLS for internal jobs) lives only on the server and never reaches the browser.
The voice index (Pro feature)
When you enable 'Reply in your voice,' we index up to 200 of your recent sent replies, embed them with Voyage-3-lite, and store both the embeddings and the original reply text in your account. The embeddings are searchable only by your own queries; RLS prevents cross-user access. You can delete the index at any time from Settings.
One-click delete
Email support@triagd.com (or click the link in Settings → Danger zone). We erase all your data — emails, classifications, briefings, rules, drafts, voice index, tokens — within 72 hours, and revoke our Google OAuth access immediately so we lose mailbox access in the meantime.
Compliance roadmap
GDPR: we offer a Data Processing Addendum (DPA) on request for any customer in the EU/UK; one-click data export and deletion are already in place; a EU representative will be named before we accept paid EU customers. SOC 2 Type I audit kickoff is scheduled with our auditor for Q3 2026; Type II evidence-collection follows over the next 9 months. We won't claim SOC 2 attestation until we have a signed report — until then, this page is the contract.
Where we're hosted
Vercel (Frankfurt + Mumbai regions for app traffic), Supabase (AWS ap-south-1, Mumbai) for the database. Cross-region replicas off.
Found a security issue?
Email support@triagd.com. We respond within one business day. We don't run a public bug-bounty yet but we acknowledge and credit good-faith reports.