Messenger metadata: what encryption does not hide
Published 31 August 2026 by Nyra
End-to-end encryption protects exactly one thing: the content of your messages. Everything around the content is metadata, and metadata is where most real-world surveillance actually happens.
What metadata is
Metadata is the information about a message rather than the message itself. For a messenger, that means who talked to whom, when they talked, how often, how large each message was, and from where each device connected. None of that requires reading a single word.
Here is why it matters. Imagine your messages are perfectly encrypted, and an observer watches the traffic anyway. They see your account exchange messages with an account belonging to a divorce lawyer. The first message goes out at 2am on a Tuesday. Short bursts follow every night that week, then an attachment about the size of a scanned document. The observer read nothing. They still know close to everything that matters: you are talking to a divorce lawyer, it is urgent enough for 2am, it is ongoing, and paperwork has started to move. Swap the lawyer for a journalist, a clinic, or a helpline, and the pattern tells the story on its own.
Intelligence agencies have said for years that patterns of communication are often more useful at scale than content, because metadata is structured, cheap to store, and easy to search.
Why end-to-end encryption does not touch metadata
End-to-end encryption means a message is sealed on your device and opened only on the recipient's device. The server in the middle relays a locked envelope it cannot open. That is a strong guarantee about the envelope's contents, not about the envelope.
The envelope still has to be delivered. To deliver it, the relay must know which account it is for, and it inevitably observes when the envelope arrived and roughly how big it is. Encryption cannot remove that information, because delivery depends on it. This is why the phrase encryption does not hide metadata is not a criticism of encryption. It is a description of what encryption is for.
What a relay server inherently sees
Any store-and-forward messenger server, run by anyone, honest or not, is in a position to observe:
- Timing. When each envelope was submitted and when it was fetched.
- Sizes. Roughly how large each envelope is, which separates a short text from a photo from a document.
- Queue state. How many envelopes are waiting for an account, which reveals activity levels and when someone is offline.
- Network addresses. The IP address each device connects from, at least at the moment of connection.
A trustworthy server logs as little of this as possible, for as short a time as possible. But the ability to observe it is built into the job of relaying messages. Anyone who tells you their relay sees nothing at all is describing physics that does not exist.
What different apps do about it
The serious private messengers all acknowledge this problem and attack it from different angles.
Signal minimizes what its servers can associate. Its sealed sender feature strips the sender's identity from the envelope, so the server knows a message arrived for you without knowing who sent it. Signal's published responses to legal requests have shown it could produce only an account's registration date and last connection date. That discipline, plus years of independent audits and a protocol the rest of the industry copied, is why Signal is the gold standard. Its one structural trade-off is that registration requires a phone number, so the account is anchored to a real-world identifier.
SimpleX goes further on identity: it has no user identifiers at all. Each conversation runs over its own pairwise message queues, so a server sees disconnected queues rather than an account with a social graph.
Session routes messages through an onion-routed network of nodes so that no single node sees both sender and destination, and it needs no phone number. It made a widely criticized trade in the other direction: its redesigned protocol dropped forward secrecy, meaning a compromised key exposes past messages.
WhatsApp is the clearest illustration of the gap this page is about: its content encryption is genuinely strong, yet Meta collects extensive metadata around it, a trade we walk through in is WhatsApp private.
Telegram deserves a plain warning in this context: regular Telegram chats are not end-to-end encrypted at all. Only secret chats are, and they are off by default. For everything else, the server sees content, not just metadata.
We keep a fuller side-by-side of these trade-offs on our comparison page.
What Nyra does, and what it does not claim
Nyra is an anonymous, end-to-end encrypted messenger in development. It is not launched yet, and it has not yet been independently audited, so read this as a design description, not a track record. The design attacks metadata in three specific places:
- Identity is not anchored. Nyra never asks for a phone number or email. An account is a username and keys derived from a recovery phrase, so the metadata that does exist is not pinned to who you are.
- Sizes will be padded into buckets. Padding envelopes to a small set of standard sizes is planned but not built yet. Until it ships, the server sees roughly how large an envelope is, and we say so plainly instead of claiming the protection early.
- The queue forgets quickly. Envelopes are deleted on delivery, or after 7 days in the queue. Combined with disappearing messages on by default, old traffic simply stops existing.
- Sealed sender is in development. We are building support for stripping the sender's identity from the envelope, the same idea Signal ships, so the server would know an envelope arrived for you without knowing who sent it. It reduces what the server learns; it does not hide your IP address or the timing of traffic, and we will not pretend it does.
The plain admission: no relay can promise zero metadata, including ours. Nyra's server still sees your username and public keys, the IP address at connection time (kept briefly for rate limiting), that an envelope of roughly some size moved between two accounts, and how many envelopes wait in your queue. This mirrors the "what our server can and cannot see" table on our home page, and it is the same list the app will show on its privacy screen. How the encryption itself works is covered on our security page.
How to reason about your own threat model
There is no universally correct messenger, only a correct one for a given threat. A few honest questions get you most of the way.
Who are you worried about? If it is someone with your unlocked phone, metadata protections do nothing and disappearing messages do a lot. If it is a nosy platform, any real end-to-end encrypted app already beats SMS and default Telegram. If it is someone who can subpoena a server, what matters is what the server can produce, so read each app's honest list of what its servers see. If it is someone watching the network itself, onion routing and traffic analysis resistance start to matter, and every tool has limits there.
Does your identity need protecting, or just your content? A phone-number-based account can be strongly encrypted and still identify you the moment the number is linked to the account. If being identifiable is the risk, choose a tool where identity was never collected.
What happens to history? Data that no longer exists cannot be demanded from anyone. Short retention and disappearing messages are quiet, unglamorous, and extremely effective.
Encryption hides what you said. Metadata is everything else, and everything else is worth taking seriously.
Frequently asked questions
What is metadata in messaging?
Metadata is everything about a message except its content: who sent it, who received it, when, how often, how large it was, and from what network address. End-to-end encryption protects the content. Metadata is what remains visible around it.
Does Signal collect metadata?
Signal is engineered to keep almost none. Its sealed sender feature hides the sender's identity from its own servers, and its published responses to legal requests have shown only an account's registration date and last connection date. Signal does require a phone number to register, which links the account to a real-world identifier. It remains the gold standard for a mainstream private messenger.
Does end-to-end encryption hide who I am talking to?
No. End-to-end encryption protects what a message says, not the fact that it was sent. The server that relays a message still handles routing information: which account it came from, which account it goes to, when, and roughly how big it is. Hiding those facts requires separate techniques such as sealed sender, padding, onion routing, or unlinkable queues.
Can any messenger have zero metadata?
No. A relay server must know enough to deliver a message, and a network observer can always see that traffic flowed. Honest projects say which metadata they minimize and which remains. Claims of zero metadata are a red flag, not a feature.