Inbox Zero AI

Privacy policy

Last updated: July 29, 2026

1. The principle everything else follows from

We do not retain the content of your emails. That was the constraint we set ourselves before writing a line of code.

In practice: the subject and a short snippet go to the AI model, a score comes back, and the content is destroyed. Nothing is written to disk, nothing lands in a database.

2. What we actually store

Your email address and name, to identify your account. Your Google OAuth tokens, encrypted at rest (AES-256).

For each processed email: its Gmail ID, the urgency score, the category and a timestamp. Not the subject, not the body, not attachments.

Your settings, and aggregated non-identifying usage metrics.

3. The Google permissions

gmail.readonly: to read the metadata and snippets needed for ranking. gmail.modify: to add and remove labels, which is how archiving works. It does not grant deletion, and we never delete.

Our use of Google API data complies with the Google API Services User Data Policy, including its Limited Use requirements.

4. Subprocessors

Hosting: Vercel. AI model: Anthropic — data sent is not used to train models. Payments: Stripe and RevenueCat; we never see your card number. Advertising on the free plan: Google AdSense.

Any addition to this list is announced to active users 30 days in advance.

5. Advertising and cookies

The free plan shows Google AdSense advertising, which sets measurement cookies. Paid plans show no advertising and do not load those scripts.

We also use a Google Ads tag to measure our advertising conversions. You can refuse these cookies through the consent banner.

6. Retention, deletion and your rights

Triage metadata is kept for 12 months. Settings → Danger zone cuts access and triggers deletion within 24 hours (backups within 30 days). You can also revoke access from your Google account without going through us.

Under GDPR: access, rectification, erasure, restriction, portability, objection. Write to privacy@inboxzero.ai. You may also lodge a complaint with your data protection authority.

7. Security

Encryption in transit (TLS 1.3) and at rest. OAuth tokens encrypted with a key held separately from the database. Internal access is logged. In the event of a breach affecting your information, notification within 72 hours.