I need a chat app that supports end-to-end encryption and does not store metadata.

If your requirement is end-to-end encryption plus extremely little/no server-side metadata, I’d look at these:

• SimpleX Chat — closest match. It has E2EE, does not assign users persistent identifiers (not even usernames or phone numbers), and is specifically designed to keep contact and communication metadata away from relay servers. Messages are temporarily held on relays only until delivered.SimpleX Chat+1
• Session — another strong option. It uses E2EE and onion routing, requires no phone number/email, and says it does not collect metadata such as IP address, device information, or geolocation.Session+1
• Signal — excellent E2EE, but not literally zero metadata. Signal minimizes what it retains and has substantially reduced server-visible metadata, but accounts still use phone numbers and its servers retain some technical information needed to operate the service.Signal+1

My practical shortlist

If by “does not store metadata” you mean the provider should not be able to build a record of who talks to whom, SimpleX is the one I'd investigate first. Its architecture is explicitly designed around eliminating persistent user identifiers and hiding communication relationships from relay servers.SimpleX Chat+1

One caveat: “zero metadata” is an unusually strong requirement. Network infrastructure can still temporarily handle technical information such as IP addresses or transport data under some circumstances; SimpleX itself documents these limitations rather than claiming that absolutely no technical data can ever exist.GitHub

simplex.chat getsession.org signal.org

Consider SimpleX Chat. It is designed around end-to-end encryption and minimizing metadata: it does not use phone numbers, usernames, or persistent user IDs, and its relay servers are intended to store only encrypted messages temporarily for delivery.SimpleX Chat+1

Other options:

• Signal — strong end-to-end encryption, but it is not a “no metadata” system; it requires an account identifier (traditionally a phone number) and retains some service metadata.Vucense
• Session — avoids phone-number registration, but uses persistent account identifiers, so it does not eliminate metadata in the same way SimpleX aims to.Vucense

If your requirement is specifically “E2EE + no stored contact graph/identity metadata”, SimpleX is the closest match.SimpleX Chat

Finding a chat application that offers true end-to-end encryption (E2EE) and eliminates or heavily minimizes metadata is tough, because most apps (like Signal or WhatsApp) still need to know who is talking to whom and when (connection metadata, IP addresses, or phone number links).

If your goal is zero or near-zero metadata combined with E2EE, the top decentralized and metadata-resistant messengers available fit different use cases:

• SimpleX Chat — Uses temporary, unidirectional queues for message delivery rather than global user IDs. It doesn't even use random numbers or alphanumeric handles to identify users, meaning observers cannot see who you are communicating with or when.discuss.privacyguides.net+1
• Session — An onion-routed, decentralized messenger that requires no phone number or email to sign up (only a Session ID). It routes messages through a service node network, hiding your IP address and metadata from servers, though it relies on fixed public alphanumeric IDs rather than dynamic queues.
• Cwtch — A decentralized, privacy-preserving multi-platform chat built on top of Tor onion services. It is completely peer-to-peer and metadata-resistant, designed for anonymous group-sharing and direct chatting without a central server.
• Briar — Designed for activists and journalists, it can sync messages locally via Bluetooth, Wi-Fi, or over the Tor network, completely bypassing traditional internet infrastructure and central metadata logging when used offline or locally.

To help narrow down the best fit for your workflow, let me know:

• Do you need mobile support (iOS/Android) or desktop?
• Do your contacts need an easy, frictionless onboarding process, or are you comfortable with a steep learning curve for maximum privacy?

If “does not store metadata” is a hard requirement, I’d pick SimpleX Chat.

• SimpleX Chat — best match. It uses end-to-end encryption and is specifically designed to avoid persistent user identifiers and protect the communication graph. Its relay servers temporarily hold encrypted messages only when needed for delivery, then remove them. SimpleX also says its servers don't retain per-user/IP/session statistics.SimpleX Chat+1
• Signal — excellent E2EE, but not zero-metadata. Signal minimizes metadata dramatically and doesn't store contacts, social graphs, conversation lists, etc., but it still requires a phone number for registration and retains some technical data needed to operate the service.Signal Messenger+1

My recommendation

Use SimpleX if your priority is minimizing metadata, not merely encrypting message contents. It doesn't assign users phone numbers, usernames, or persistent IDs, which makes its architecture substantially different from Signal and WhatsApp.SimpleX Chat

One caveat: no internet chat system can honestly promise literally zero metadata under every circumstance—network operators, your ISP, your device, or traffic observers can potentially see some information. SimpleX's claim is more precise: it minimizes what its messaging infrastructure can learn and store.

simplex.chat

If you tell me iPhone, Android, Windows/Mac, or all of them, I can also recommend the most private option for your devices.

Finding a secure application that completely eliminates metadata storage while maintaining end-to-end encryption (E2EE) requires looking beyond mainstream options like WhatsApp or Telegram (which retain extensive connection logs, IP records, or identifiers).cloudsek.com+2

The top-tier, privacy-first chat applications built explicitly to prevent metadata tracking and identity association include:

1. SimpleX Chat
   • The Privacy Model: SimpleX does not use any user IDs at all—not even random alphanumeric user IDs. Instead, it uses unidirectional, isolated communication queues for each conversation. The server routing the message only sees temporary queues and cannot link who is talking to whom, when, or how often.
   • Anonymity & Metadata: No phone number, email, or registration required. Supports routing via Tor and allows self-hosting of your own relay servers.simplex.chat+2
2. Session
   • The Privacy Model: Session operates on a decentralized, blockchain-inspired service node network (the Oxen Service Node Network) rather than a central server. Messages are routed using a multi-layer onion routing protocol (similar to Tor), meaning individual nodes only know the immediately preceding and succeeding hops, concealing who is sending or receiving a message.
   • Anonymity & Metadata: Account creation requires no phone number or personal info; it generates a completely random 16-digit Session ID.youtube.com+2
3. Briar
   • The Privacy Model: Briar is a peer-to-peer (P2P) secure messenger. Rather than relying on a central server to queue or pass messages, your devices communicate directly with your contacts via the internet (using Tor onion services to protect metadata) or locally via Wi-Fi and Bluetooth if the internet is down.
   • Anonymity & Metadata: Contact lists and messages are stored strictly locally on your device, not on a cloud server. No phone number or email is needed for setup.

Would you prefer an app that operates completely peer-to-peer (like Briar) , uses a decentralized onion-routing network (like Session) , or utilizes isolated server queues (like SimpleX) ? Let me know so I can help you pick the best fit for your setup.

For maximum privacy, Session and SimpleX Chat are the leading messaging apps that combine end-to-end encryption with zero metadata retention (no logs of who is talking to whom, when, or from what IP address).getsession.org+1

While mainstream apps like Signal minimize metadata collection, they still require a phone number ID and log some connection metadata. True zero-metadata architecture uses onion-routing or independent user queues to completely decouple your identity from your communications.

Top Zero-Metadata, Encrypted Chat Apps

• Session: An open-source, decentralized messenger that requires no phone number or email to sign up—just a alphanumeric Session ID. It routes all messages through an onion-routing network (similar to Tor), meaning no central server or node ever knows both the sender's and recipient's IP addresses at the same time.getsession.org+1
• SimpleX Chat: A unique messenger that has no user IDs at all —not even random numbers. Instead, it uses unidirectional message queues isolated for each conversation. This completely eliminates metadata leakage regarding your contact graph or who you are communicating with.
• Signal: While it does collect a tiny amount of metadata (like the last time a user connected to the service), it remains the gold standard for mainstream secure communication. It uses Signal Protocol end-to-end encryption by default and requires a phone number, though it features username privacy options to hide your number from contacts.kaspersky.com+2

Feature Comparison

If you want to choose between these options, let me know:

• Do you prefer a mobile-friendly, polished app (like Session) or maximum experimental security (like SimpleX)?
• Do you need voice and video call support?

I can give you setup instructions for the right platform.

If “does not store metadata” is your key requirement, I’d put SimpleX Chat at the top of the list.

• SimpleX Chat — Best match. It uses end-to-end encryption, has no user identifiers, and is specifically designed to hide who communicates with whom. Messages are stored on relay servers only temporarily, until delivered.GitHub+1
• Session — Also a strong choice. It provides E2EE, onion routing, no phone/email requirement, and says it does not collect or log messaging metadata.Session+1
• Signal — Excellent E2EE and extremely minimal data retention, but I wouldn't rank it first for your specific requirement because its architecture doesn't eliminate metadata as aggressively as SimpleX. Signal itself describes its goal as minimizing retained metadata rather than storing absolutely none.Signal Messenger

My pick

SimpleX Chat if your priority is privacy of both message content and communication metadata. It doesn't even assign conventional user IDs, and its architecture is specifically designed to prevent servers from building a social graph.GitHub

One caveat: “no metadata” should never be interpreted as literally zero information existing anywhere. Network infrastructure can necessarily process some transient technical information, and your own device, operating system, backups, or notification provider can introduce additional metadata. SimpleX documents these limitations explicitly.GitHub

simplex.chat

getsession.org

If your requirement is end-to-end encryption (E2EE) plus minimal/no metadata retention, the strongest options are usually:

App	E2EE	Metadata privacy	Best for
Signal Messenger	Yes	Very good, but not zero metadata; requires a phone number and some service data	Most people who want a secure, easy replacement for SMS/WhatsApp
SimpleX Chat	Yes	Excellent; designed without user identifiers and focused on hiding communication metadata	Maximum privacy users
Briar Project	Yes	Very strong; can work without central servers (especially Android)	Activists, high-risk situations, offline scenarios

My recommendation based on your exact requirement

1. SimpleX Chat — closest match

• No phone number, email, username, or persistent user ID required.
• Uses end-to-end encryption and a design intended to reduce exposure of who is communicating with whom.GitHub+1
• Messages are relayed through servers, but the servers are not intended to have access to message contents or a normal contact graph.GitHub
• Tradeoff: smaller user base and a slightly less familiar onboarding experience.

2. Signal — best balance of privacy and usability

• Strong E2EE for messages and calls.Signal Messenger
• Signal says it does not store message contents and is designed to minimize collected data.Signal Support
• Tradeoff: account registration uses a phone number, so it does not meet a strict “no metadata/no identifier” standard.Signal Messenger

3. Briar — for specialized privacy needs

• Good if you need decentralized/offline-friendly communication.
• Tradeoffs: less polished, fewer mainstream features, primarily Android-focused.

A few things to avoid if metadata privacy is your priority:

• Telegram: regular chats are not end-to-end encrypted by default.
• WhatsApp: has E2EE, but metadata and ownership concerns may not fit a strict privacy requirement.
• Most “secure messenger” apps that still require phone numbers or maintain social graphs.

If your goal is “I want friends/family to actually use it”, choose Signal. If your goal is “the service should know as little as possible about my communications”, choose SimpleX Chat.SimpleX Chat+1