Every guarantee below is enforced by architecture, not by policy. We publish how it works precisely so you don't have to take our word for anything.
Mail is encrypted in the browser before it leaves the machine (Ed25519 signatures, X25519 key agreement, AES-256-GCM). Keys are held as non-extractable handles — the private key can't be exported by script, ours included.
Our servers hold no key material at all — not even encrypted copies. The web backend is a relay to the network, nothing more. There is nothing on our side to breach, subpoena or quietly hand over.
Every message carries its sender's signature, checked against the sender's published identity record before it's accepted for delivery. A message that doesn't verify is dropped at the first relay — spoofing isn't filtered, it fails.
Signing in is a cryptographic challenge: your device proves it holds the account key. There's no password database to steal and no reset flow to socially engineer.
Blocking binds to the sender's cryptographic identity, not their address string. A blocked sender can't come back with a fresh address — burning an identity costs them everything, which is why spam economics collapse.
On a managed domain your administrator custodies account keys — onboarding, recovery and offboarding run inside your organization. Managed accounts say so in the product: employees see who can recover their mailbox.
The message is signed by the sender's key and encrypted to the recipient before it leaves the machine.
Relays carry and store sealed envelopes they cannot open. Storage is encrypted because it never sees plaintext in the first place.
The recipient's device checks the signature against the sender's published identity before showing the message. No valid signature, no display.
Mail from the old world is authenticated at the bridge (SPF, DKIM, DMARC) and arrives with a signed verdict your client verifies — trust tiers with receipts.
Two honest edges. Mail crossing the bridge to or from legacy email is protected in transit (TLS), not end-to-end encrypted — that's the floor every other provider calls normal, and you can run your own bridge to remove us from that path. And while message contents are always sealed, stronger delivery-metadata protection (onion-routed transport) is designed and on the roadmap.
Security is a process, not a promise. If you believe you've found a vulnerability, tell us privately and we'll work with you to fix it quickly — and credit you if you'd like.