Secure Email

Category overview · ProPrivacyTime

Encrypted email closes one specific gap: a readable mailbox in your provider's custody. Its honest limits - metadata, recipient-side, inter-domain transport - are where evaluation begins.

Most email is, structurally, a document the provider keeps. Your messages rest on the company's servers in a form it can read, process for spam filtering and features, and hand over when legally required. A conventional mailbox is therefore less like a sealed letter and more like a file in someone else's office. Encrypted email services change that one fact: they are designed so the provider stores your mail encrypted and cannot decrypt it themselves. That is the gap being closed - not a new internet, but a different relationship between you and the company that hosts your mail.

The reason evaluation has to start with the limits is simple. Encryption that protects your mailbox at rest does not, by itself, hide who you correspond with, does not protect a message once it reaches a recipient on a different provider, and does not wrap the wider internet's transport in a cloak. A sober read of what a service actually publishes - its cryptography documentation, its privacy policy, its audit scope - tells you far more than the padlock on the homepage. This category collects that kind of reading.

How we evaluate secure email

We do not run speed tests or infection simulations, and we never write "we tested / we found" claims. Our evaluation is document-based: we read what vendors actually publish and compare it against what the marketing says. The criteria we apply, in plain terms:

• Encryption model. Is the service end-to-end (decryption happens only on your device), or is it provider-side encryption (the provider holds the keys and can read your mail)? The difference is the single most important fact on the page.
• Metadata handling. What the provider logs and retains about who emailed whom, when, and from where. Content encryption is the headline; metadata policy is the quieter, often more revealing document.
• Jurisdiction. Where the company is based shapes which legal processes can reach it - worth the same sober reading it gets in our VPN coverage, rather than privacy folklore.
• Audit and transparency. Are independent audits published, and do their scope pages actually cover the systems that matter? Narrow audits can look reassuring while excluding the things you care about.
• Open-source status. Whether the client and server code can be inspected. Publication is not a guarantee, but it changes who can check the claims.

None of these require us to touch the product. They require reading - which is the point of this site.

Common misconceptions

• "Encrypted email hides metadata." Content encryption is what gets sold. Routing metadata - sender, recipient, timing - usually still exists, because mail has to be delivered. The real question is how little of it the provider keeps.
• "Switching makes you fully private." Your protection ends where the recipient's provider begins. Email a Gmail or corporate Outlook user and the message is ordinary on their side, regardless of your provider.
• "Any 'secure' label means end-to-end." "Secure" and "encrypted" cover a range from marketing language to genuine E2E with published key management. The label tells you almost nothing; the documentation does.
• "It replaces a VPN." Encrypted email protects mail in your provider's custody. It does nothing for your browsing traffic, your IP address, or the rest of your connection. The two tools solve different problems.

Where to start

If you read one thing in this category, read the guide below. It walks through what encrypted email protects, what still leaks, and how to read a provider's metadata and recovery policies without taking the homepage at its word.