Delta Chat: encrypted messaging over email, without a phone number

Delta Chat doesn’t set up a new central server. It’s a messaging app that uses email as its transport layer — and with it, the decentralized email network that has existed for decades.

Delta Chat: encrypted messaging over email, without a phone number

Delta Chat: encrypted messaging over email, without a phone number

Delta Chat doesn’t set up a new central server. It’s a messaging app that uses email as its transport layer — and with it, the decentralized email network that has existed for decades.

That might sound like a workaround, but it has a concrete consequence: no single operator holds everyone’s messages, no single platform can suddenly disappear or get acquired, and no phone number is required. Relay and email operators can still be asked for what they hold, and the developers run a few small helper services (see below).


Who this guide is for

This guide is for readers who:

  • want encrypted messaging without a phone number
  • prefer decentralised infrastructure over one central platform
  • can accept some metadata tradeoffs in exchange for signing up without personal data

What you gain, and what it costs

What you gain:

  • no dependence on a single chat platform operator
  • a default profile on random addresses, not linked to a real identity by anything you enter
  • practical encrypted messaging on top of existing email infrastructure

What it costs:

  • relays still see addresses, message size and your IP address
  • Delta Chat is less mainstream than Signal or WhatsApp
  • no forward secrecy yet, unlike the strongest modern messengers

When this is overkill

If you mainly want the simplest secure messenger for everyday contacts, Signal is usually the easier first move. Delta Chat makes more sense when decentralisation, account independence, or identity separation matters enough to justify the extra complexity.

How it works

Delta Chat sends messages as encrypted emails via standard IMAP/SMTP. Your contact receives them as email, but sees a chat interface — not a traditional inbox.

For end users, Delta Chat feels like a normal messaging app. Under the hood, everything runs over email infrastructure. It also has one-to-one audio and video calls (peer-to-peer WebRTC, set up through Delta Chat messages), on Android 8 and newer, iOS, Desktop and Ubuntu Touch.


No email address required: chatmail relays

By default Delta Chat puts your profile on chatmail relays: minimal email servers built for chat. You enter no phone number, email address or other personal data, and you get a randomly generated address on each relay.

Since Android 2.62 (September 2026) a new profile no longer lands on one hardcoded relay (nine.testrun.org). The app picks from a list of community relays built into the app (17 in core 2.68, aiming for three per profile), and you can change them at Settings → Advanced → Relays.

“No account” is not quite right: each relay holds a real login, with a random name and password. It’s just not tied to anything you gave it.

Who runs them: different people and groups, not the Delta Chat developers, and you choose whom you trust. nine.testrun.org is run by testrun UG in Freiburg, by a small volunteer team according to its own privacy policy.

What they keep: Delta Chat’s policy says relays delete messages after delivery, or typically after a few weeks. The relay software’s defaults delete mail after 20 days (large messages after 7) and accounts with no login after 90 days, so a profile you leave unused for months can lose that address. Operators can change these values. Each relay’s own policy applies; nine.testrun.org says it stores no IP addresses but keeps logs of messages in transit for a limited time.

You can also use a classic email address at your own provider or self-hosted server, via Use Classic Email as Relay. The project says to use such an address only with chatmail apps, not next to a normal mail app. Classic providers generally have no push notifications, the address is tied to your account, and the provider keeps its own rules on storage.


Encryption

Delta Chat uses a subset of OpenPGP as the encryption standard. Keys are exchanged through a QR code or invite link (SecureJoin), and Autocrypt sets up encryption among contacts and group members. It uses no key servers and no manual import. Attachments and file names are encrypted too.

Padlocks are gone. Since Delta Chat version 2 (2025), chats are end-to-end encrypted by default and the app shows no lock icons, so a missing padlock means nothing. The marker to look for is the opposite one: a mail icon means a message or chat is not end-to-end encrypted.

When it doesn’t apply. On chatmail relays, unencrypted messages can’t be sent or received. Unencrypted mail only becomes possible on a classic email profile, and then only after you turn off Enforce Encryption for All Relays. Your and your recipient’s providers can then read, analyse or change those messages, and a mail chat never becomes end-to-end encrypted later. Add Contact Manually creates such a contact, without an encryption guarantee.

What the QR code proves. The invite carries a fingerprint of the inviter’s key, so someone controlling the mail route can’t swap in their own key. That only holds if the invite itself wasn’t tampered with: an attacker who controls both the mail route and the channel you sent the link over can. So scan in person, or send the link over a channel you trust. It proves the key belongs to whoever gave you the invite, not who that person is.

Delta Chat no longer shows who is “verified”: Android 2.62 removed the verification icon and “Introduced by”. To check by hand, open the contact’s profile, tap Encryption and compare the two fingerprints on both devices. In a group, the app exchanges members’ keys automatically; if a member’s identity matters, check them this way.

Perfect Forward Secrecy (PFS) is not yet present. If your private key leaks and someone collected your earlier messages in transit, they can decrypt them. Autocrypt v2, an IETF draft with post-quantum encryption and reliable deletion (forward secrecy), was presented at FOSDEM 2026 and is scheduled by the project for 2026. It isn’t there yet: the FAQ still says “not yet”, and core 2.50 (May 2026) added only preparatory post-quantum support and generates no such keys. There is no “sealed sender” equivalent either.


What a relay or email server sees

Since the 2.48+ “zero metadata” release (March 2026), Delta Chat implements full header protection (RFC 9788): the subject, To, References, In-Reply-To and group-membership headers are no longer visible in cleartext, and the outer Date is randomised over five days.

The server still sees:

  • The sending and receiving address (random by default), and so which addresses talk to each other
  • Message size
  • Your IP address, for connectivity. Delta Chat says it neither stores nor exposes it; the relay’s own policy decides what that operator does
  • Roughly when it handled the message, whatever the outer date says

The server does not see:

  • Message content and attachments (end-to-end encrypted)
  • Subject or threading headers
  • Group names and members (end-to-end encrypted, kept on devices)
  • Your address book or contact list

Addresses on a relay link to nothing you entered, but your IP address does reach it, and with several relays per profile more than one operator sees this. With a classic email provider the address is tied to your account. If your IP address is a risk, the project recommends a system-wide VPN.

Delta Chat is still not the choice for anyone who needs to hide who talks to whom from the server, which Session, SimpleX and Briar aim for with their designs.

Services the developers do run:

  • Push notifications (Google Play and App Store versions): a central proxy passes an encrypted wake-up token on to Apple or Google, and they never see profile data or message content. F-Droid and desktop versions use no push at all.
  • Calls: a direct call shows both devices each other’s IP address, and a call relay sees both, even on a direct call. If your relay has no call relay, the fallback is turn.delta.chat, which by its policy keeps a connection log in memory for at most three days.

Lost phone, backups and a second device

Your profile, keys and chats live on your devices only, and no server can restore them. Without a second device or a backup, a lost phone means a lost profile; your contacts would have to connect to a new one.

  • Second device: with both on the same network, go to Settings → Add Second Device and scan the QR code from Add as Second Device on the new one. Both then work independently. With more than one device, messages stay on the relay until it deletes them.
  • Backup: Settings → Chats → Export Backup writes a file with all messages, contacts and your keys. The Android app sets no password on it, so anyone holding the file can read everything. Your screen lock only protects starting the export. Store it encrypted, or delete it after use.

Security audits

Delta Chat has been independently audited multiple times:

  • Cure53 (March 2023): TLS handling and a recommended mail server setup. Eight findings, four of them vulnerabilities; the only High was in the mailcow mail server software. One Low: the desktop app stored its database unencrypted.
  • ETH Zurich (2024): five new attacks in the paper’s abstract, exploiting SecureJoin and Autocrypt interactions and bugs in rPGP. The project counts 20 issues, fixed in version 1.44 (March 2024).
  • Radically Open Security (December 2024): a test of the rPGP encryption library with 14 findings (5 High, 1 Elevated, 2 Moderate, 6 Low), mostly on malformed input. Two public advisories (CVE-2024-53856, CVE-2024-53857); the project says the fixes shipped in December 2024.

The project’s list also has Include Security reviews from 2019 and 2020. It shows no audit after December 2024, so the 2025-2026 changes (version 2, SecureJoin v3, multiple relays) aren’t covered by a listed audit.


Installing and getting started

Android: via Google Play, F-Droid, Huawei AppGallery or APK from delta.chat. The project recommends F-Droid or other non-Google sources. F-Droid versions have no push, so messages can arrive later unless you allow a background connection.

iOS: via the App Store.

Desktop: Linux (Flatpak, Arch, Nix), macOS, Windows — download from delta.chat.

Labels below are from Android 2.67. On first launch:

  1. Tap Create New Profile. Your contacts see the name you enter, so it needn’t be your real one.
  2. Tap Agree & Create Profile. For a relay of your own choice or a classic email address, first tap Use Other Server, then List Chatmail Servers or Use Classic Email as Relay.
  3. Tap the QR code icon on the main screen and let your contact scan it, or share the invite link through another private chat.

Already have a profile? Tap I Already Have a Profile, then Add as Second Device or Restore from Backup.

Multiple profiles per device are supported — useful for compartmentalization.


Honest caveats

No PFS yet — see above.

Routing metadata visible to relays — addresses, message size and your IP address. With chatmail the addresses are random; with regular email they’re not.

Group size — there’s no strict limit, but the project doesn’t recommend more than 150 members.

Disappearing messages — you set a time from 5 minutes to 1 year for all chat members, and it starts when the receiver first sees the message. Each member’s app deletes it, in the app and on the server. That protects against neither people nor copies outside the app’s reach: a chat partner can save or photograph messages first, a partner who uninstalled the app can leave the encrypted copy on their relay for longer, and our reading is that the app can’t reach an operator’s backups either.


Who Delta Chat is for

Direct value:

  • People who don’t want to give a phone number or personal data to sign up
  • Anyone skeptical of central platforms who prefers existing decentralized infrastructure
  • Organizations that want data sovereignty by running their own relay
  • Users who want to separate multiple digital identities via multiple profiles
  • Anyone who already trusts email as a channel and wants an encrypted chat layer on top

Less suitable for:

  • Anyone who needs to hide from the server who talks to whom (Session, SimpleX, or Briar are built for this)
  • Anyone who requires PFS today
  • Large groups (above 150)
  • Group calls — Delta Chat’s calls are one-to-one

Delta Chat vs. the rest

Delta Chat Signal Session SimpleX
Phone number required No Yes No No
Central server No (independent relays; central push proxy) Yes (US company) No (decentralized) No (independent servers)
Perfect Forward Secrecy Not yet; planned in Autocrypt v2 Yes Not yet (planned in Protocol V2) Yes
Hiding metadata Headers encrypted; relay sees addresses, size, IP Sealed sender Onion routing No user identifiers

Background

Delta Chat is an open source community project; legal responsibility and most of the funding run through merlinux GmbH in Freiburg, Germany. It has no venture capital and has been coordinated since 2017. It’s funded by public grants (EU and US so far) and donations. In June 2025 the project said public funding for its relay work had suddenly dried up that year and asked for donations; merlinux now names the Sovereign Tech Fund as a supporter of chatmail. The apps are open source under GPL-3.0, the core library under MPL-2.0.

On 14 May 2025 the Moscow City Court ruled against merlinux for not handing over user data and decryption keys; merlinux replied that it can’t hand over data it doesn’t have. It shows how the model works: pressure lands on the developer, who has no message store to hand over.

Next step

Alternatives

Reviews