Beta notice

Please read this before you connect Gmail. It's short, and it's the whole deal.

What this is

A personal, experimental project run by one person in their own time. It isn't a company product, it comes with no guarantees, and it may change or shut down. Contact: thenapkinlab@gmail.com.

What happens when your assistant reads email

• Only the emails your assistant (Claude or ChatGPT) asks for are fetched from Gmail, read-only. Your inbox is never scanned in the background.
• Medical and financial emails (lab results, bank statements, payslips…) are withheld completely.
• In other emails, card and bank numbers, ID numbers, passwords and keys, one-time codes, home addresses and dates of birth are replaced with [removed: …].
• Attachments are never opened or sent. The assistant only sees their names, and names that reveal a sensitive document, like "passport", are removed too.
• Very long emails are cut off where the filter stops checking, and the assistant is told.
• Everything that isn't withheld or removed goes to your assistant and is handled under that assistant's own terms.

The filter can make mistakes

In testing it removes about 96 to 100% of sensitive values and withholds about 96% of medical and financial emails, so it sometimes misses one. Don't connect an inbox where a single slip would be serious. If you see something that should have been removed, press "Something leaked" on your dashboard.

What is stored, and for how long

• Your sign-in email, your Gmail address, and your Gmail access token (encrypted). Until you disconnect or delete your account.
• For each request: time, which assistant, the search your assistant ran (for example "flight newer_than:2m"), and counts. 90 days. Note that a search can itself say something about you.
• For each email: its Gmail ID (for "Open in Gmail"), the decision, the reason types, and your feedback. 7 days.
• Usage counters and service-wide daily totals with no personal data.
• Never stored: email bodies, subjects, senders, attachments, or the sensitive values themselves.

Where, and who's involved

The service runs on Amazon Web Services in Stockholm (EU), and the filter's AI model runs on Amazon Bedrock in EU regions. Sign-in uses WorkOS. Gmail access uses Google's API. Only you see your dashboard. The person running the beta can technically access the stored records above to operate the service, but never email content, because it isn't kept.

A technical log of each request goes to Langfuse, in the EU: the time, assistant, tool, result, counts of shared, redacted and withheld emails, reason types (for example "medical"), timings and error types. It has no email content, searches, message IDs, names, email addresses or account IDs.

Leaving

Disconnect Gmail on Setup, or delete everything in Settings → "Delete my data", which also revokes our Google access. You can also remove access in your Google Account → Security → Third-party connections.