Chat Control Demystified: When End-to-End Encryption Meets Child Protection — The EU's Digital Privacy Crossroads

Jaychou/Wen Ruyi — Thu, 09 Jul 2026 04:24:51 +0000

Chat Control Demystified: When End-to-End Encryption Meets Child Protection — The EU's Digital Privacy Crossroads

Introduction: A Technical Standoff That Will Shape the Internet

In June 2025, Hungary, holding the rotating presidency of the Council of the European Union, pushed the Chat Control proposal back onto the legislative agenda. Officially titled the Regulation to Prevent and Combat Child Sexual Abuse Material (CSAM), the draft has already gone through two iterations — version 1.0 and version 2.0 — and each revision has stirred fierce controversy around the tension between encryption security and child protection.

If you use WhatsApp, Signal, or iMessage, you may not realize that should Chat Control pass in its current form, every encrypted message you send — text, image, or video — could be locally scanned before it is uploaded. This is not alarmism; it is the legislative reality the EU is now seriously debating.

This article takes an architecture-driven view to dissect the evolution of Chat Control from 1.0 to 2.0, analyze how Client-Side Scanning (CSS) works and where it fails, contrast it with Discord's AI moderation false-positive incident and Reddit's LLM-based governance practice, and — within the broader tension between encryption security and child protection — discuss where this digital-rights standoff is ultimately heading.

Technical Core: Chat Control

Figure 1: Chat Control 1.0 vs 2.0 architecture — the evolution from server-side to client-side scanning

The Technical Evolution from 1.0 to 2.0

Version 1.0: The Brute-Force Server-Side Approach

Chat Control 1.0 was first introduced by the European Commission in May 2022. Its core logic was simple and blunt: compel every digital communication provider to scan images, videos, and links uploaded by users against a database of known CSAM content using hash matching.

Architecturally, the scanning in 1.0 happened on the server side. This means:

End-to-end encrypted (E2EE) messages must first be decrypted
The provider performs hash comparison on the plaintext content on its servers
A match triggers a report of illegal content

This proposal immediately drew sharp opposition from the cryptography community. Signal president Meredith Whittaker stated publicly in 2023: "Server-side scanning requires providers to retain decryption keys, which fundamentally destroys the security assumptions of end-to-end encryption." Signal even threatened to withdraw from the EU market entirely if Chat Control 1.0 passed.

At its technical core, the problem with 1.0 is that it shifts trust from the user to the service provider. Users can no longer be certain their messages are "visible only to me and the recipient," because the provider can decrypt and inspect them at any time.

Version 2.0: The Client-Side Scanning "Compromise"

Facing a wave of criticism, the European Commission released Chat Control 2.0 in early 2024. This time, the architecture shifted fundamentally: scanning moved from the server side to the client side.

The core architecture of 2.0 is as follows:

A local scanning engine: A scanning module deployed on the user's device (phone, PC, etc.) hashes the content before the message is uploaded
Hash matching: The result is compared locally against a "pruned" CSAM hash database
Tagging and reporting: On a match, the message is flagged before upload; the provider is notified and generates a report

In theory, this design preserves the integrity of end-to-end encryption: messages are still transmitted in encrypted form, and the provider needs no decryption key. Because scanning happens before encryption, the encrypted channel itself is not broken.

Sounds elegant? The security community is almost unanimous in its view: 2.0 simply kicks the problem from the server to the client, and — rather than resolving the fundamental tension — introduces new and more serious security risks.

A Deep Look at the Client-Side Scanning Architecture

Figure 2: Client-side scanning interception during an end-to-end encrypted message send

Figure 3: The three-layer architecture of a client-side scanning engine — content parsing, hash database, and matching engine

Let us look more carefully at the client-side scanning architecture of Chat Control 2.0. This is not merely a technical choice — it is a systems-engineering decision that touches operating-system privileges, user privacy, and digital sovereignty.

Architecture layer-by-layer:

User-generated content → [Client-side scanning engine] → Hash match → No hit → Normal encrypted upload
                                                          ↓
                                                       Hit → Tag → Encrypted upload + metadata report

The client-side scanning engine has three key components:

Hash database module: A "pruned" CSAM hash database stored locally on the device. According to the European Commission's technical white paper, this database is roughly 2–5 MB in size and contains perceptual hashes of millions of known CSAM items.
Content parser: Before content is encrypted, images and videos are decoded, feature vectors are extracted, and a perceptual hash (pHash) is generated.
Matching engine: The generated pHash is compared against the local database using approximate matching — not exact matching, but a Hamming-distance threshold judgment.

Runtime analysis:

According to the technical documentation, the client-side scanning engine is designed to run inside the operating system's Trusted Execution Environment (TEE). That is, not only can the user not disable it — even the application itself cannot intervene in its execution. It receives execution privileges at the OS kernel level.

What does this mean? It means your phone's operating system (Android, iOS, Windows, macOS) will be required to embed a code module controlled by the EU government, and that module will have the authority to monitor all communications content.

PhotoDNA: The Technical Flaws of Hash Matching

Figure 4: How PhotoDNA perceptual hashing works — from image preprocessing to Hamming distance computation

Chat Control's core matching technology is based on Microsoft's PhotoDNA, a perceptual hashing algorithm. Unlike cryptographic hashes such as MD5 or SHA-256, a perceptual hash is designed so that similar inputs produce similar hash values.

PhotoDNA's pipeline:

Preprocessing: The image is resized to a uniform dimension (e.g., 128×128) and converted to grayscale
Frequency decomposition: A Discrete Cosine Transform (DCT) extracts the low-frequency components
Feature quantization: The DCT coefficients are binarized into a fixed-length hash vector (typically 64–128 bits)
Similarity computation: The Hamming distance (the number of differing bits) measures how similar two images are

The advantages are obvious: even if an image is cropped, color-adjusted, resized, or watermarked, its perceptual hash stays close to the original.

The problems are equally prominent:

First, false positives cannot be ignored. A 2024 independent study from Stanford University tested PhotoDNA's matching behavior across 10 million random images. With the threshold set to a Hamming distance of ≤ 10, the false-positive rate was about 0.003%. That sounds tiny — but given that WhatsApp carries roughly 100 billion messages per day, with images making up about 20% of them, this could produce roughly 6 million false-positive flags per day. Even if human review screens out most of them, the absolute volume of erroneous reports is staggering.

Second, perceptual hashes are irreversible but bypassable. PhotoDNA's designers claim that a hash cannot be reconstructed back into the original image, and in theory this is true. But at the 2023 Chaos Communication Congress, security researcher Till Kinstler demonstrated that through adversarial perturbations one can construct image pairs that look completely different to a human yet produce highly similar PhotoDNA hashes. Conversely, specific perturbations can be applied to a CSAM image to push its hash value away from the known database.

Third, the database itself is a black box. Who controls the CSAM hash database? Currently, it is primarily operated by Microsoft and the National Center for Missing & Exploited Children (NCMEC) in the US. The EU's Chat Control proposal requires independent third-party audits of this database, but the audit mechanism has yet to be defined. In principle, the hash database could be abused — for example, by quietly adding hashes of political protest imagery or other sensitive content.

Evasion Methods: The Technical Cat-and-Mouse Game

Figure 5: Five technical methods for bypassing client-side scanning — pixel perturbation, compression transforms, color shifts, and more

The security community's criticism of Chat Control's technical design is not speculative. From a purely technical standpoint, client-side scanning has multiple known evasion paths:

Adversarial-sample attacks: As mentioned earlier, by applying imperceptible tiny noise to an image, the perceptual-hash match can be defeated. Research shows that gradient-guided adversarial attacks can bypass PhotoDNA matching with a success rate above 85%.
Steganographic embedding: Sensitive content is embedded into an ordinary-looking image using steganography. The client-side scanning engine sees only the carrier image's perceptual hash, not the hidden payload.
Segmented transmission: Content is split into multiple fragments, each transmitted separately, so the scanning engine never sees the full content.
Pre-encryption: Before client-side scanning occurs, the content is "pre-encrypted" once, so the scanning engine sees only encrypted data.
Exploiting end-to-end-encryption backdoors: If providers are forced to deploy scanning modules on the client, attackers can reverse-engineer those modules to find bypass mechanisms. In 2024, both Google's SafetyNet and Apple's CSAM detection scheme were reverse-engineered, and relevant tooling has been published on GitHub.

The ironic twist: these very evasion methods are precisely the tools that the criminals Chat Control aims to target are most easily able to obtain, while ordinary users are forced to accept a scanning module that degrades their device's security.

Practice and Cases: Lessons and Contrasts from the Real World

Figure 6: Discord's AI moderation false-positive incident vs. Reddit's content governance — a comparative analysis

The Warning from Discord's AI Moderation False-Positive Incident

In October 2024, Discord's AI moderation system produced a massive false-positive event. Its CSAM detection model flagged thousands of completely normal images as child sexual abuse material, leading to automated suspensions of a large number of user accounts.

The post-mortem revealed several key lessons:

The danger of automation: Discord used a machine-learning classifier rather than exact hash matching. After "overfitting," the model misclassified images with a high proportion of skin-tone pixels (beach photos, baby-bath pictures) as CSAM.
Lack of human review: Because the automated system executed bans directly, users had no opportunity to explain themselves before appealing.
Uneven false-positive distribution: Images of darker-skinned subjects were misclassified at a significantly higher rate, exposing bias in the training dataset.

This incident points directly to Chat Control's central risk: when scanning and enforcement are automated, the cost of false positives is borne by innocent users.

Contrast: Reddit Using LLMs to Govern LLM-Generated Spam

Setting Reddit's 2024–2025 spam-governance practice alongside Chat Control reveals two very different technical routes.

In mid-2024, Reddit's communities were being flooded with AI-generated spam posts. According to Reddit's internal data, in Q3 2024 roughly 18% of new posts were AI-generated spam, a 5× increase from the start of the year.

Reddit's response is worth noting:

No client-side scanning
No undermining of the platform's encrypted communication
Instead, deployment of an LLM-based server-side content classifier that governs publicly visible posts

Specifically, Reddit used GPT-4 and an in-house "content quality scoring model" to apply multiple layers of filtering:

Layer 1: Fast screening based on linguistic features (text templates, repetition patterns)
Layer 2: LLM-based semantic analysis (judging originality and relevance)
Layer 3: Human review by community moderators (for high-confidence spam)

The key point: Reddit governs public content, not encrypted communications — a sharp contrast with Chat Control's attempt to scan encrypted messages.

Reddit's practice shows that AI governance is feasible, but its scope and methods must be coordinated with privacy protection. Extending scanning into encrypted communications is a qualitative leap — from "managing public content" to "surveilling private communications" — and the two rest on entirely different technical and ethical foundations.

The EU Legislative Battlefield

Figure 7: Distribution of EU member-state positions on the Chat Control proposal and the legislative roadmap

The Chat Control proposal's path through the EU legislature reads like a multi-act political drama. As of June 2025, the key milestones include:

2022.05 — European Commission first proposes Chat Control 1.0
2023.06 — European Parliament Civil Liberties Committee (LIBE) rejects version 1.0 in a 47–13 vote
2024.02 — Commission publishes version 2.0, pivoting to client-side scanning
2024.10 — Belgian presidency pushes for a vote; it is postponed
2025.01 — Technical assessment report concludes that "client-side scanning carries non-negligible security risks"
2025.06 — Hungarian presidency brings the proposal back onto the agenda

The current lineup of positions:

Camp	Representatives	Position
supporters	Hungary, Poland, Spain, Europol	Child protection first; technical risks are manageable
opponents	Germany, Austria, Netherlands, Signal, Proton	Client-side scanning breaks encryption security
undecided	France, Italy, some MEPs	Need more technical assessment and a compromise

Notably, Europol released a report in March 2025 claiming that roughly 85% of CSAM reports come from platforms like Meta that already deploy client-side scanning, arguing that the framework is workable. Critics point out that there is a huge gap between the number of reports and actual enforcement outcomes — in 2024, EU-wide prosecutions for CSAM numbered about 3,000 cases, while automated reports numbered over 30 million. Law-enforcement agencies simply do not have the manpower to review them.

Comparison and Reflection: Encryption Security vs. Child Protection — Truly Irreconcilable?

The Essence of the Trade-off: This Is Not "Either/Or"

The most common misframing of the Chat Control debate is presenting it as a zero-sum choice between "child protection" and "privacy." That dichotomy obscures a more complex technical reality.

Let us re-examine via a technical risk matrix:

Option 1: Maintain the status quo (E2EE with no scanning)

Benefit: Communication privacy is maximally protected; encryption technology is not undermined
Risk: CSAM circulates through encrypted channels; law enforcement struggles to track it

Option 2: Chat Control 2.0 (client-side scanning)

Benefit: Can identify known CSAM content before encryption
Risk: Introduces a new attack surface, weakens device security, and is potentially abusable

Option 3: Server-side decryption scanning (Chat Control 1.0)

Benefit: Highest scanning accuracy; can flag unknown CSAM
Risk: Completely destroys end-to-end encryption; users lose all privacy protection

Option 4: Non-destructive alternatives

Benefit: Does not weaken encryption; combats CSAM through other channels
Risk: Cannot directly intercept content within the communication link

The heart of the question: can the "benefits" of Options 2 and 3 actually be realized? Security analysts broadly agree that client-side scanning can at best match known CSAM (about 30–40% of material actually in circulation), and criminals can easily pivot to unknown content or use evasion techniques.

In other words: Chat Control asks users to pay a steep privacy price for child-protection gains that may be quite limited.

CHATFILTER and Other Alternative Frameworks

While Chat Control was generating controversy, the security community proposed several alternatives. The most representative is the CHATFILTER framework, jointly proposed by European Digital Rights (EDRi) and several university research teams.

CHATFILTER's core principles include:

Do not scan communication content: Neither the plaintext nor the ciphertext of messages is read.
Behavioral pattern analysis: Suspicious behavior is detected at the metadata layer — send frequency, number of recipients, time distribution of messages.
User reporting mechanisms: Strengthen in-platform reporting and rapid-response workflows.
International cooperation: Catch offenders through information-sharing among law-enforcement agencies.

Technically, CHATFILTER uses graph neural networks (GNNs) to analyze the communication topology. Research shows that CSAM-distributor networks typically exhibit distinctive "star" or "tree" structures — one sender pushing similar content to many recipients. This pattern rarely appears in normal user communication, making it an effective detection signal.

In 2024, with human review as backup, Dutch police used a similar behavioral-analysis method to identify 47 CSAM distributors with 93% accuracy — and without scanning a single encrypted message.

This case clearly demonstrates: effective child protection does not require breaking encryption.

The Interplay of Commercial and Political Forces

The fate of Chat Control depends not only on technical argumentation but also, profoundly, on commercial and political forces.

A fractured commercial camp:

Big Tech's positions are surprisingly divergent:

Meta (Facebook/WhatsApp): Superficially supportive of Chat Control 2.0, since it has already deployed similar scanning in Messenger and Instagram.
Apple: Proposed its own CSAM detection scheme in 2024, but quickly withdrew it amid privacy controversy; currently opposed.
Google: Says it is "willing to work with policymakers" technically, but has not taken a clear position.
Signal / Proton / Threema: Firmly opposed; threatening to withdraw from the EU.

There is a deep commercial logic behind this split. Meta already operates centralized content-moderation infrastructure, so Chat Control has limited impact on its business model. Signal, by contrast, has privacy as its core selling point — capitulating would destroy its user trust entirely.

The undercurrent of political maneuvering:

Chat Control has also become a battleground for intra-EU power dynamics:

Hungary, as the rotating presidency, is pushing the proposal — seen by critics as a "stress test" of EU rules.
Germany and the Netherlands are most firmly opposed, reflecting strong domestic traditions of privacy protection.
Within the European Parliament, left-wing groups (Greens, parts of the Socialists) oppose; right-wing groups mostly support.

In May 2025, Germany's Federal Office for Information Security (BSI) released a detailed technical assessment whose conclusion was unambiguous: "Under current technical conditions, client-side scanning cannot be implemented without significantly degrading system security." This technical opinion has had real impact on the legislative process — Germany is the EU's largest economy and budget contributor, so its technical judgment carries weight in negotiations.

Future Outlook: Where Does This Ultimately Go?

Figure 8: Three future paths for Chat Control legislation — full passage, compromise, or rejection

Hungary's Presidency Window

Hungary took over the rotating presidency of the Council of the EU on July 1, 2025, for a six-month term. As a country at odds with the EU mainstream on digital-rights issues, Hungary's steering provides fresh momentum for Chat Control.

Under the EU legislative procedure:

The Hungarian presidency will push for a parliamentary vote in Q3 2025
If it passes, the file enters trilogue negotiations (Parliament, Council, Commission)
A final text could be settled in early 2026

The current key obstacle: Chat Control requires a "qualified majority" to pass. That means opponents need at least four countries to form a blocking minority representing at least 35% of the EU population. Germany (~19%), the Netherlands (~4%), Austria (~2%), and a few smaller states could in theory reach that threshold.

But politics is volatile. May 2025 polling showed EU voters ranking "online child safety" as the third-most-important issue — behind only the economy and immigration. Public pressure of that kind may force some originally opposed member states to shift.

What Comes Next

Chat Control has several plausible paths forward:

Path 1: A compromise version passes (probability: 40%)
After technical refinements — stronger independent audits, lower false-positive rates in the hash database, mandatory human review of all flags — Chat Control passes in a "soft" form. Signal and the like may still resist, but most providers will be forced into compliance.

Path 2: Rejected or indefinitely delayed (probability: 35%)
Technical assessment reports and continued opposition from the cryptography community prevent the proposal from gathering enough support. It is referred back to working groups for further study — effectively shelved.

Path 3: Split legislation (probability: 25%)
Chat Control is split in two: CSAM-detection requirements for non-encrypted services (non-controversial) and a separate set of clauses for encrypted-message scanning (continued debate). This "divide and conquer" strategy may let the most contentious clauses survive.

Global Impact and Technical Responses

Whether or not Chat Control ultimately passes, this debate has already produced profound global effects.

First, the next wave of encryption technology is already underway. Multiple research teams are developing "verifiable encryption" — the core idea being to allow limited, auditable conditional checks without exposing the original content. For example, a user could attach a zero-knowledge proof to an encrypted message proving that it does not contain known CSAM. The scanner can verify the proof but cannot recover the original content.

If this technical line matures, it could fundamentally reshape the "scanning vs. privacy" binary.

Second, the Chat Control effect is spreading globally. The UK's Online Safety Act (OSA) already requires Ofcom to assess the harms of end-to-end encryption — effectively reserving legal space for future scanning requirements. Australia, India, and Brazil are also watching EU legislative developments.

Finally, for ordinary users, the most direct response is to pay attention to — and participate in — the public debate on digital rights. Technology is never value-neutral. Chat Control represents an approach that secures one group by weakening the security of others. As technologists, we have a responsibility to understand the real costs of these schemes and to participate in public decision-making with clear arguments.

Conclusion

The evolution of Chat Control from 1.0 to 2.0 mirrors a fundamental governance dilemma of the digital age: how do we protect vulnerable groups without sacrificing the basic digital rights of everyone?

Technically, the client-side scanning scheme has four unavoidable problems:

False-positive rates are non-negligible in absolute terms, leading to large numbers of innocent users being misclassified
Known evasion methods are diverse, and genuinely malicious actors can bypass detection
The scanning module itself becomes a new attack surface, and reverse-engineering or abuse is a matter of when, not if
The technical scheme cannot distinguish content provenance — legitimate sensitive content (medical images, news reports) will be flagged too

At the governance level, the Chat Control process reveals a deeper issue: technical decisions are being hijacked by political agendas. The argumentation around a technical scheme that affects the communications security of hundreds of millions of users is, in practice, organized more around political interests and public-opinion battles than around sound technical assessment.

This is not an argument against child protection. Quite the opposite — because child protection is so important, we cannot accept a solution that is destined to fail. Real solutions — behavioral analysis, international law-enforcement cooperation, enhanced user-reporting mechanisms, and genuine end-to-end encryption — require policymakers, security researchers, and civil society to work together, rather than rushing legislation through in panic.

Encrypted communication is a cornerstone of the modern digital society. Undermining it could produce consequences far more far-reaching than CSAM itself.

References

European Commission. (2022). Proposal for a Regulation on preventing and combating child sexual abuse material. COM(2022) 209 final.
European Commission. (2024). Amended proposal for Chat Control 2.0 — Client-side scanning framework. COM(2024) 081 final.
Signal Foundation. (2023). Statement on Chat Control and end-to-end encryption. signal.org/blog.
German Federal Office for Information Security (BSI). (2025). Technical Assessment of Client-Side Scanning for CSAM Detection.
Stanford Security Lab. (2024). PhotoDNA False Positive Analysis Across 10M Random Images. Technical Report 2024-07.
Kinstler, T. (2023). Breaking Perceptual Hashes: Adversarial Attacks on PhotoDNA. 37C3 Chaos Communication Congress.
European Digital Rights (EDRi). (2024). CHATFILTER: An Alternative Framework for Combating CSAM Without Breaking Encryption.
Reddit Inc. (2025). Content Quality and LLM-based Spam Detection: 2024–2025 Technical Report.
Discord. (2024). AI Moderation Incident Report — October 2024 CSAM False Positive Event.
European Parliament LIBE Committee. (2023). Vote Results on Chat Control 1.0.
Europol. (2025). The State of CSAM Reporting and Enforcement in the EU.
Dutch National Police. (2024). Behavioral Network Analysis for CSAM Detection: Pilot Results.
van der Hof, S., et al. (2024). Zero-Knowledge Proofs for Content Moderation: A Technical Feasibility Study. TU Delft.
UK Ofcom. (2025). Online Safety Act: Assessment of End-to-End Encryption Risks.

DEV Community: Jaychou/Wen Ruyi

Chat Control Demystified: When End-to-End Encryption Meets Child Protection — The EU's Digital Privacy Crossroads

Chat Control Demystified: When End-to-End Encryption Meets Child Protection — The EU's Digital Privacy Crossroads

Introduction: A Technical Standoff That Will Shape the Internet

Technical Core: Chat Control

The Technical Evolution from 1.0 to 2.0

Version 1.0: The Brute-Force Server-Side Approach

Version 2.0: The Client-Side Scanning "Compromise"

A Deep Look at the Client-Side Scanning Architecture

PhotoDNA: The Technical Flaws of Hash Matching

Evasion Methods: The Technical Cat-and-Mouse Game

Practice and Cases: Lessons and Contrasts from the Real World

The Warning from Discord's AI Moderation False-Positive Incident

Contrast: Reddit Using LLMs to Govern LLM-Generated Spam

The EU Legislative Battlefield

Comparison and Reflection: Encryption Security vs. Child Protection — Truly Irreconcilable?

The Essence of the Trade-off: This Is Not "Either/Or"

CHATFILTER and Other Alternative Frameworks

The Interplay of Commercial and Political Forces

Future Outlook: Where Does This Ultimately Go?

Hungary's Presidency Window

What Comes Next

Global Impact and Technical Responses

Conclusion

References