Zero-access email: what it means and what it does not cover

Zero-access email is email hosting where every message that arrives for you is encrypted with your public key before it is written to disk, so the provider stores a copy it cannot open. The matching private key sits on the provider’s servers too, but encrypted under a key derived from your password — which the provider never holds in plaintext. Nothing about the arrangement is exotic; it is ordinary public-key cryptography applied at the moment of delivery, and it is the strongest honest claim a mail host can make about data it keeps.

It is also narrower than most people hear. “We cannot read your email” is a statement about stored messages. It says nothing about how a message travelled, who read it on the way in, or what happens when the account itself becomes the problem.

How does zero-access encryption work?

One key pair per mailbox, generated when the account is created. The public half stays on the server so that mail can be encrypted the instant it arrives; the private half is stored wrapped in a key derived from your password, and unwraps only when you log in and supply it.

Delivery runs in a fixed order. A sending server hands the message to the receiving edge over SMTP; the service checks SPF, DKIM and DMARC, runs spam and malware filtering, builds whatever index it needs, then encrypts the result with your public key and writes it. From that point the file opens only with a key the provider is holding in a form it cannot use.

Two consequences fall straight out of the design. Anything the server needs to do with the content of your mail has to happen in the window before encryption, or in your client afterwards — which is why zero-access providers run search in the browser instead of on the server, and why their search is slower than Gmail’s. And your password becomes load-bearing in a way it never was with a classic host: it is the thing that unwraps the key. The recovery phrase handed to you at account creation is therefore the actual credential.

Is zero-access encryption the same as end-to-end encryption?

No, and the two get conflated constantly. Zero-access encryption protects a message at rest from the company storing it. End-to-end encryption protects a message in transit, so that no intermediary — including both parties’ mail providers — ever holds plaintext.

A message sent from a Gmail account to a zero-access mailbox is not end-to-end encrypted. It crossed the internet under transport TLS between hops, arrived readable, was read by the receiving service for filtering, and only then became ciphertext. The encryption at rest was applied by a party that had already seen the whole message.

Genuine end-to-end email requires both ends to participate: PGP or S/MIME with a key exchange, or two accounts on the same provider whose clients do it silently. That last case is why the confusion survives — Proton-to-Proton and Tuta-to-Tuta mail really is end-to-end — and for most people it covers a small slice of their correspondence. Everything to and from the rest of the world is transport-encrypted in flight and zero-access at rest, which is a different and weaker guarantee.

What does zero-access encryption not cover?

Metadata in transit, the plaintext window at delivery, the copies other people hold, and custody.

Envelope data is not payload. Who wrote to whom, when, from which IP address and through which relays is visible to every server that touches a message, and is logged by all of them. Subject lines are a grey area: some implementations encrypt them at rest, many do not, and any subject line that crossed SMTP crossed it readable.

Filtering has to read the message. A provider that filters your spam has seen your mail, and both facts are true simultaneously. Anyone claiming to filter mail they have never been able to read is describing something that does not work.

Your correspondents’ copies are not yours. The message sitting in their Gmail is Google’s business, and no key on your side reaches it.

Who holds the ciphertext, and why does that matter?

The provider does — on its disks, in its datacenter, under its jurisdiction, behind its account system. Encryption answers “can they read it”. Custody answers “can they keep it from me”, and the two fail independently.

A subpoena served on a zero-access provider produces everything the encryption does not cover: ciphertext, account and billing records, login IP addresses, envelope logs. That is often exactly what an investigator wanted. In 2021 Proton complied with a legally binding Swiss order and logged the IP address of an account under investigation; nothing was broken, because nothing had to be.

Jurisdiction follows the company rather than the hardware. The US CLOUD Act, in force since 2018, reaches data a US-incorporated provider controls no matter which country the disks occupy.

Lockout is the failure mode nobody plans for. A suspended account, a failed card, a terms dispute or a forgotten password with no recovery phrase leaves your archive mathematically safe and permanently unreachable. Zero-access encryption makes this sharper, not softer: a provider that truly cannot read your mail also cannot let you back in.

What should you ask a provider that claims zero access?

Six questions, and each has a specific answer if the provider is being straight with you.

At what exact point is a message encrypted, and what runs before that? Everything touching plaintext should be nameable.

Is the subject line encrypted at rest, or only the body?

Where does the private key live, what unwraps it, and does the server ever hold the unwrapped key in memory in order to render my mailbox in a browser?

If I lose my password and my recovery phrase, what recovers my mail? “Nothing” is a respectable answer; vagueness is not.

Who holds the ciphertext, and under which country’s corporate law does that entity sit?

Is the stored format documented well enough that software other than yours could read an exported archive?

Zero-access encryption is a real advance and worth choosing. The provider to be wary of is the one whose homepage says nobody can read your email and whose answer to the first question is a paragraph about how much they care.