Security & transparency
What this service guarantees, stated precisely — and what it cannot protect.
What we guarantee
- Message content. With client-side OpenPGP (Curve25519 keys generated in your browser), the server stores ciphertext only — before and after any server compromise. Private keys never touch the server.
- Subject, sender, recipient. For encrypted mail these travel inside the encrypted payload (protected headers). The stored copy is sealed:
From: Sealed Sender, To/Cc/Bcc removed. At rest we store only "who received ciphertext, when". - Encrypt-on-delivery. If you upload an OpenPGP public key in My account, incoming unencrypted mail is encrypted to that key before it touches disk.
- SMTP. Authentication required, envelope sender bound to the authenticated user, delivery jitter (random 5–20 s batching) to blunt timing correlation, zero address logging.
- No IP logs. Nowhere in the stack. Rate limiting uses only salted, one-way hashes of addresses.
- No personal data at signup. Invite-only or human-reviewed requests. No phone number, no real name, no required recovery email.
- Account recovery. Only via a recovery code you generate yourself. Without it, we cannot recover your account — by design.
Warrant canary
Warrant canary last updated: never
As of the date shown, this service has received no search warrants, subpoenas, gag orders, National Security Letters, or other compulsory legal process, and has not been required to modify the software or disclose user data.
This canary is overdue — it has not been renewed within 90 days. Treat its absence of update as a warning.
What we cannot protect
- Live server compromise. An attacker controlling the server in real time can observe connections as they happen. Signal has the same property; anyone claiming otherwise is lying.
- Your recipient. We cannot control what happens on the other end of a message.
- Federation metadata. Mail to outside providers exposes envelope metadata (who mails whom, when) by protocol design. Sealed sender applies only between users of this service.
- The browser trust model. Web E2EE means the server ships the crypto code each session; a compromised or coerced server could serve a backdoored build. We mitigate with reproducible builds and signed releases, and we say so honestly rather than claiming parity with native apps.