Last month this site argued that the scanning proposal always comes back and that architecture — messages that never pass through a platform scanner — is the only defense that doesn't depend on the next vote. Since then the negotiation calendar has firmed up and the Council's internal legal analysis has leaked in enough detail to sharpen that argument in one specific way. The defense isn't encryption. It's operatorship.

What is actually scheduled

The Irish presidency's planning note (document 11501/26, dated July 7) schedules the sixth political trilogue on the permanent Child Sexual Abuse Regulation for September 29, with technical preparatory meetings on September 10 and 18. The Irish presidency's planning documents point to a formal adoption push at the Justice and Home Affairs Council meeting October 1–2 in Luxembourg. Four of five previous trilogue rounds ended without agreement on exactly one question: may scanning target everyone, or only people a judge has named?

The institutions haven't announced the date publicly. It is known from Council minutes published by netzpolitik.org. That is worth pausing on: the most consequential digital-legislation negotiation in Europe is being scheduled quietly, in LIMITE-stamped documents.

What the Council's own lawyers said — three times

The Council Legal Service is the group of lawyers who tell the 27 governments whether a text will hold up in court. Their opinions are normally LIMITE. Three have become public anyway, and all three say the same thing.

The first, 8787/23 (April 2023), analyzed the Commission's detection-order regime and concluded it "would require the general and indiscriminate screening of the data processed by a specific service provider, and apply without distinction to all the persons using that specific service, without those persons being, even indirectly, in a situation liable to give rise to criminal prosecution" — a serious risk of compromising the essence of privacy and data protection under Articles 7 and 8 of the Charter. "The essence" is the line no law may cross, whatever the aim. The opinion also flagged that scanning encrypted content means either abandoning end-to-end encryption, building a back door, or scanning on the device before encryption — and that any of these is a stronger rights interference, not a weaker one. Its advice was plain: target people there are reasonable grounds to suspect, or drop it.

Then the Danish presidency found the workaround. A compromise text of 6 November 2025 (14092/25) deleted the detection orders — Articles 7 through 11 — and kept the "voluntary activities" providers already perform under the temporary ePrivacy derogation. The Council adopted that as its negotiating mandate on 26 November 2025: providers may voluntarily check content. No order, no court, no state. Just permission.

The Legal Service's answer to that, recorded in working-party minutes of 12 November 2025, is the part operators should read twice: nothing in the voluntary text prohibits a provider from scanning inside end-to-end encrypted communications — which the lawyers described as no change to current law. The presidency text says nothing "should be interpreted as prohibiting, weakening or circumventing end-to-end encryption." The lawyers' reading: it also doesn't stop scanning inside it. The word "voluntary" didn't resolve the encryption question. It handed it to the provider.

Asked again in 2026 — minutes of 21 May and 10 June, published 12 June — the lawyers said their concerns about detection orders were still unresolved, because even Parliament's targeted-order model "still meant general searching in interpersonal communication." An objective, sufficient link to abuse material is required, and that judgment cannot be delegated to service providers. Voluntary scanning of public content: unproblematic. Voluntary scanning of private messages: possible where a legal basis exists, nothing more.

So the legal landscape going into September 29 is: the state may not order indiscriminate scanning. Parliament's suspect-based orders are drafted too broadly. And the Council's voluntary model leaves the scanning decision with the company — which the Charter does not restrain.

The arithmetic of near-misses

The procedural history is the part that should make every community organizer distrust any single "win":

  • March 26: Parliament rejects the derogation extension 311–228. It lapses April 3.
  • July 9: a motion to reject the Council's interim law gets 314 votes — short of the 360 absolute-majority threshold (this site's August post said 361; the Parliament press office figure is 360). 607 MEPs voted. Under second-reading rules, every silent seat counts, in effect, for the Council's text.
  • Parliament amends instead: end-to-end encrypted communications are excluded. The Council accepts on 23 July — and appends, in its own press release, that the encryption exclusions "do not imply" acceptance of the same limit in the permanent regulation.
  • Regulation (EU) 2026/1881 has been in force since 31 July and runs to 3 April 2028.

The blocking-minority math in the Council is nearly as tight. Per Brussels Record's tracker, nine governments representing 32.9% of the EU population are on record against mandatory scanning — 2.1 percentage points short of the 35% needed to block. Germany, Belgium, and Portugal together would close the gap; Germany's negotiating instructions since June do not oppose mandatory detection where it supplements voluntary scanning. A "no" that wins the room by one vote can still lose the rulebook, twice, in two different chambers.

What this changes about the architecture argument

The August post's claim — architecture is the defense — survives, but the September documents force a correction to a version of it that is circulating in self-hosting circles: encryption is not the defense.

If a community's messages live on a hosted platform — WhatsApp, Discord, Slack, Google Chat, or an E2EE messenger operated by a US company — the scanning decision now belongs to that provider's trust-and-safety team, under its terms of service, on a legal basis that says it may. Nobody has to authorize it. Nobody has to justify it to the users. The Legal Service was asked whether the state can do this; it was never asked whether a company should, because that is not a question the Charter puts to companies. And the Council's lawyers have explicitly read the voluntary model as not prohibiting scanning inside encrypted services. Signal's and WhatsApp's client-side encryption protects content from interceptors. It does not protect it from the operator's client, if the operator decides to scan. Client-side scanning proposals in earlier drafts of this regulation were aimed precisely at that surface.

What remains is operatorship. A Matrix homeserver a fire hall runs on hardware it owns has no trust-and-safety team to deputize, no terms of service that changed this month, and no scanning stack to legalize. The India/BitChat case is the same property from the other side: no central choke point to regulate. The EU's own legal machinery has now documented, in its own words, that the decision point for message scanning is the operator. Choose operators you can read the source of, on hardware you control, in a jurisdiction you live in.

One more correction worth keeping on the record: the interim regulation's scope covers interpersonal communications services as platforms. A self-hosted homeserver was never inside any draft's enforcement reach in the first place — there is no provider account to deputize. The argument for running it was never legal cleverness. It was that the legal perimeter keeps expanding, in both directions at once, and the only fixed point is hardware you hold.

What to watch October 1–2

Three signals tell you what September 29 produced:

  1. Whether "voluntary" carries the encryption exclusion Parliament won in July, or ships without it, as the Council's mandate has it. Without it, the permanent text inherits the lawyers' reading that scanning inside E2EE is untouched.
  2. Whether suspect-based detection orders survive in any form. The Legal Service's position is that even those are drafted too broadly — the negotiators' compromise space is narrower than either side's public position.
  3. Whether the Legal Service's view goes on the public record before COREPER endorsement. If it is overruled silently, the resulting law gets litigated rather than settled — years of court cases against a text the Council's own lawyers flagged.

If none of the three lands, the file passes to the Lithuanian presidency on January 1 and the voluntary interim regime runs to April 2028. That is not the status quo before July. It is a standing permission to scan private messages, granted without a single affirmative vote by anyone the users elected — and the architecture answer to it hasn't changed: don't be inside the perimeter.