Blog · April 5, 2026

Serverless is safer than encrypted

Encryption protects the content. But what really gives you away is everything else.

The sealed envelope and the postman

Imagine you send a letter inside an armored envelope. Nobody can open it. Nobody can read what it says. You feel safe. But the postman carrying it knows who sent it, who it's addressed to, when it was sent, from where, and how often you send letters to that address. The content is protected. Everything else is not.

That's exactly what happens with most messaging apps that claim to offer end-to-end encryption. The message content may be encrypted. But the server transporting it sees who talks to whom, at what time, how often, and from what location. That's called metadata. And metadata tells your story better than your own words.

What the server sees even if it doesn't read your messages

A messaging server, by design, needs to know who sends the message and who it's addressed to. Without that information, it can't deliver it. It also logs when it was sent and when it was read. And if the app uses location services, it can know from where.

With that data — without reading a single word of your conversations — it's possible to know who you have a close relationship with, how often you talk, at what times you're active, whether you're in the same place or different places. Behavioral patterns can be detected, new relationships, relationships that cool off, unusual activities. All without opening a single message.

The uncomfortable question

If an app sent your messages as plain text — unencrypted, completely readable — but did it directly from your device to the other person's, without going through any server, it would be more private than an app with end-to-end encryption that goes through a central server.

It sounds contradictory. But think about it. In the first case, someone would have to intercept the direct connection between your two devices to read the message — something technically possible but difficult and localized. In the second case, there's a company with a server that logs all your metadata continuously, automatically, massively, and permanently. Content encryption is irrelevant if the pattern of your life is already recorded.

Why this won't change

The big messaging platforms won't eliminate their servers. They can't. Their business model depends on knowing your communication patterns. Knowing who you talk to, when, and where has enormous commercial value. That information feeds advertising algorithms, user segmentation, and behavioral analysis. Eliminating the server would mean giving up all of that.

It's not a technical issue. It's a conflict of interest. The company that carries your messages has a financial incentive to observe how it carries them. That's why content encryption doesn't bother them at all: the business was never in the content. It was always in the metadata.

The only structural solution

The only way for nobody to have your metadata is for nobody to be in the middle. For the message to go directly from your device to the other person's. No server to transport it, no company to observe it, no record of who talked to whom.

When there's no server, there's no metadata to collect. No pattern to analyze. No history to hand over in response to a court order. No database to hack. Privacy doesn't depend on a corporate promise or a privacy policy that can change tomorrow. It depends on the architecture. And architecture doesn't lie.