The pitch is unusual enough to sound like a gimmick, but the logic is sound. Email is the largest open, federated communication system on earth. It has no single owner, no app store gatekeeper, and any provider can talk to any other. Delta Chat — an open-source project — takes that substrate and puts a modern instant-messaging interface on top of it, so two people with ordinary email accounts can chat with end-to-end encryption and never think about IMAP, SMTP, or PGP keys.
No phone number, no new account
The most immediately useful property is what Delta Chat doesn't require. There is no phone number, which sidesteps the entire class of problems we covered in our piece on Signal's phone-number requirement — no SIM, no carrier, no number to be linked to your identity or stolen in a SIM swap. You sign in with an email address you already have, or one created for the purpose.
Because the transport is email, there is no Delta Chat server to register with, go down, or get blocked. Your "account" is your mailbox. If your provider is reachable, you can message anyone whose provider is reachable. The project also runs lightweight "chatmail" servers tuned for instant messaging — minimal retention, push-friendly — but the point is that you are not locked to them; any standards-compliant email account works.
A messenger with one company's servers has one point of failure and one point of coercion. A messenger built on email federation inherits email's resistance to both: there is no central switch to flip off, and no single operator who can be ordered to surrender the whole network.
How the encryption works
Delta Chat encrypts messages end-to-end using Autocrypt, a standard for opportunistic OpenPGP key exchange. The mechanics are designed to be invisible: each client attaches its public key to outgoing mail in an Autocrypt header, so when two Delta Chat users exchange messages their apps automatically learn each other's keys and switch to encryption with no manual key management.
This is opportunistic encryption, which is both the strength and the caveat. The first contact establishes keys on a trust-on-first-use basis — the same model behind TOFU verification — meaning an attacker positioned to intercept that very first exchange could in principle substitute their own key. To close that gap, Delta Chat supports a QR-code verification flow ("Securejoin"): scan a contact's code in person and the app cryptographically confirms you have the right key, upgrading the conversation to a verified state.
The metadata trade-off you can't escape
Building on email buys decentralization at a real cost: email's metadata model. End-to-end encryption protects message bodies, but the surrounding envelope is a different story.
| Protected by Delta Chat's E2EE | Exposed as email metadata |
|---|---|
| Message text and attachments | Sender and recipient addresses |
| Subject line (encrypted by Delta Chat) | Timestamps of every message |
| The body of group messages | The chain of mail servers a message traversed (Received headers) |
Your email provider — and the providers your contacts use — can see who is talking to whom and when, even when they cannot read what is said. This is the same fundamental limit that affects all email, and it is why metadata surveillance is such a persistent problem. Apps built on closed networks like Signal can do more to minimize this (with techniques like sealed sender), at the price of the centralization Delta Chat deliberately avoids. There is no free lunch here — only a choice about which property you value more.
The honest framing: Delta Chat gives you the openness and unblockability of email with the usability of a chat app and real content encryption. What it cannot give you is metadata protection, because email's routing metadata is load-bearing for delivery.
Who Delta Chat is for
Delta Chat fits people who want a messenger that no company controls, who refuse to tie their communication to a phone number, or who operate where app-based messengers are blocked but email still flows. It is genuinely good at being uncensorable and account-free. It is a weaker fit if hiding the fact and pattern of your communication — not just its content — is central to your threat model.
How Haven compares
Haven shares some of Delta Chat's instincts: we use PGP for email so we interoperate with the open mail world, and we treat encryption as the default rather than a setting. Where we differ is the chat layer — Haven uses the MLS protocol for group messaging, which gives forward secrecy and clean group-membership cryptography that opportunistic PGP wasn't built for, and we work to minimize metadata rather than inherit email's. Delta Chat and Haven are both honest about their limits, which is the part that matters most when you're choosing. If you're weighing options, our comparison of secure group-chat protocols lays out the underlying trade-offs.