ScanRecords

Companies / Wire

Wire

Can't read your messages
What we watch for — Wire's content is end-to-end encrypted, which keeps it out of Chat Control's scope. We watch for weakened encryption claims, client-side scanning language, or new qualifiers around E2EE in these documents.
Status
Can't read your messages
Held since
26 Jul 2026
Documents
3 tracked
Changes recorded
2 — latest 6 Aug 2026

Tracked documents

DocumentLast fetchedSizeHashSnapshot
Privacy Policy
wire.com		 6 Aug 2026 45,988 chars 4299e085d156 text · raw · wayback
Security page
wire.com		 6 Aug 2026 13,418 chars c10169bc6ca9 text · raw · wayback
Google Play Data Safety
play.google.com		 26 Jul 2026 1,373 chars 9e7f86ff49c1 text · raw · wayback

text is the extracted record we hash and diff; raw is the page's original HTML kept verbatim as evidence — it renders without its styling here, by design.

What we searched for

A status that rests on absence is only as good as the search behind it. Every one of Wire's 3 archived documents (60,782 characters) was searched for the same published vocabulary used on every company here — in English, German and French. The search is a plain function of the archived text and re-runs whenever that text changes, so it always describes the documents listed above. Re-run it against this archive yourself with tools/scan-terms.mjs.

Not one term matched anywhere in these documents. Whatever this company does or does not do, its own tracked documents do not discuss scanning at all.

Found nowhere in these documents: Regulation 2021/1232 · derogation / Ausnahmeregelung / dérogation · Chat Control / Chatkontrolle · ePrivacy · CSAM / CSAE · child sexual abuse / Kindesmissbrauch · NCMEC / CyberTipline · PhotoDNA · hash matching / hash database · Internet Watch Foundation · scan / scanning / gescannt · automated detection / automatisierte Erkennung · classifier / machine learning detection · monitor content / review content

Record RSS ↗