You trusted Element because it was built on Matrix — the decentralized, open-source, end-to-end encrypted paradise. You believed your conversations were safe from prying eyes. Then they dropped version 26.07.3, and quietly added something called content scanning infrastructure.
This is not a feature. It’s a structural betrayal. A backdoor dressed up as an update, slipped into release notes you never read. And if you’re using Element right now, your privacy just got a little more theoretical.
Let me be clear: I’m not talking about a bug. I’m talking about an architectural compromise. Element — the flagship client of the Matrix protocol — has built a system that allows third parties to scan your encrypted messages before they reach you. The company frames it as a safety measure, but the language tells a different story: “content scanning infrastructure” is the polite term for “we built a surveillance chokepoint.”
Here’s the thing about end-to-end encryption: it’s all-or-nothing. Either your device holds the only key, or it doesn’t. The moment you introduce a scanning layer — even one that runs locally — you change the trust model. E2EE is quietly becoming a marketing term, not a technical reality. It’s the label they print on the box, while the inside gets hollowed out by compliance.
You’ve probably noticed this pattern before: WhatsApp announces encryption, then adds business messaging with server-side processing. Signal adds phone number linking that makes metadata more leaky. Now Element follows suit, and the common thread is regulation. The UK’s Online Safety Bill, the EU’s chat control proposals — they’re all pushing for “voluntary” scanning. And companies are pre-building the infrastructure so they can say, “We’re already compliant.”
But here’s the twist: Element and Matrix were supposed to be the safe harbor. The project that couldn’t be pressured because it’s decentralized, open source, and run by a nonprofit. If Matrix can be bent, no one is safe. This isn’t just about one app — it’s a signal that the regulatory tide is pulling encryption apart, one update at a time.
I saw this happen firsthand when I read the release notes. They frame it as “infrastructure” — a neutral term. But infrastructure is never neutral. It’s the plumbing that determines what can flow. And with this change, the plumbing now includes a tap for content scanning.
Take a side: this is dangerous. Privacy isn’t a feature you toggle on; it’s the architecture of trust. Once you add a scanning layer, you’ve created a mechanism that can be expanded, repurposed, or mandated. Today it’s for illegal content. Tomorrow it’s for political speech. Engineering a backdoor for one purpose is engineering a backdoor for all purposes.
The real question isn’t whether Element will actually scan your chats. It’s whether the infrastructure exists. And now it does. The horse has left the barn, lock the stable door all you want.
If you’re using Element, ask yourself: do you still believe your messages are private? Or have you just been marketed to? The update is already rolling out. The scanning infrastructure is live. And nobody is talking about it — until now.
FAQ
Q: Is this really a backdoor, or just an optional feature?
A: It's an infrastructure layer that enables content scanning. Whether it's optional or not, the existence of that infrastructure changes the trust model. A backdoor doesn't have to be open to be dangerous.
Q: What should I do if I use Element?
A: Read the release notes carefully. If content scanning is enabled server-side, consider switching to a fork that refuses this update. For truly private communication, look at platforms that run entirely local encryption with no scanning hooks.
Q: Don't we need content scanning to catch illegal content?
A: That's the argument, but it's a slippery slope. Encrypted systems that add scanning are no longer truly encrypted. The trade-off is between universal privacy and targeted enforcement. Once you build the infrastructure, it can be expanded beyond any initial use case.