How we protect your mail

Merritt asks for a lot of trust: access to your email. Here is how we hold it.

Your mail password

You give Merritt an app-specific password, never your main Apple or Google password, and you can revoke it from your provider at any time.

Merritt encrypts it the moment it arrives, with a key held in Amazon Web Services’ key management service (AWS KMS). The key never leaves AWS. The part of Merritt that saves your password can encrypt with it but never decrypt; only the part that holds your mail connection can decrypt, and only for your account. Not even the people who run Merritt can use the key without changing its rules, and any such change sends an alert. Every use of the key is recorded in an audit log.

Your mail

• Message bodies are never stored on our servers. When you open a message, it’s fetched from your provider, sent to your phone, and dropped.
• What we keep to sync your phone (subjects, senders, folder names, AI summaries and drafts) is encrypted with a key for your account alone.
• Logs never contain subjects, bodies or passwords, and email addresses in them are hashed.

The AI

Parts of your new mail are sent to Anthropic to write summaries and drafts, as described in the privacy policy. Passwords and keys are never sent. Email is treated as untrusted: a message can’t send mail or delete anything on its own, and nothing is sent without you.

Connections

Every connection, from your phone to Merritt and from Merritt to your email provider, uses encrypted, verified TLS.

Found a problem?

If you think you’ve found a security issue, please email support@trymerritt.com. We’ll respond quickly and keep you updated.