We decompile publicly distributed Android and iOS apps and trace their data flows to real endpoints in real countries. We document what we observe, distinguish verified findings from interpretation, and preserve the evidence behind every conclusion. No company can buy a better result — every organisation is held to the same standard, whether it pays us or not. This permanent disclosure ledger puts that principle into practice.
Every app is decompiled at source-code level, not just scanned from outside.
1.04M+
Smali classes read
The full shipped code we have actually read, not an estimate.
231+
Critical findings recorded
Confirmed findings copied to regulators, not theoretical risks.
862+
Weak points found and documented
Third-party tracking we have provably found inside the binary.
500+
Endpoints investigated
Real servers and countries where data actually flows.
117+
SDK instances mapped
Reusable libraries correlated across the entire corpus.
1 of 387 entries · sorted by elapsed ↓
Showing the report for ZDF Mediathek.
OrganisationNotifiedStatusSEVIntel (click to expand)StatutesResolvedDisclosureElapsedReport
ZDF Mediathek
PUBLIC
2026-06-30
109d ago
RESOLVED
HIGH
ZDF is legally required to stay free of advertising and sponsorship because the broadcaster is funded by the mandatory broadcasting fee, yet its app still carries a persistent advertising-tracking identifier with no identifiable public-service purpose, which directly contradicts that legal requirement. It also runs a commercial marketing measurement tool before you have consented, which raises the question of which paid advertising campaigns are being measured here with mandatory-fee money, and it sends your account data to Google's US servers with no documented legal basis.
com.zdf.android.mediathek. Zweites Deutsches Fernsehen, Mainz, a public broadcaster funded by the German broadcasting fee (§ 10 RBStV), legally required to be free of advertising and sponsorship (§ 30 MStV). C1: Firebase API Key AIzaSyB6c3Wu… + DB zdfmediathek-74412.firebaseio.com hardcoded. H1: AD_ID (Advertising Identifier) declared, a persistent advertising-profiling ID on an ad-free, mandatory-fee-funded app; no identifiable public-service purpose; conflicts with § 30 MStV. H2: Adjust Attribution SDK (SystemLifecycleContentProvider before consent), a commercial paid-user-acquisition measurement SDK on a public-broadcaster app; which paid campaigns funded by broadcasting-fee budget is this measuring? H3: Firebase InitProvider pre-consent (initOrder=100) + Firebase Auth + Firebase Firestore, Google LLC US transfer, no Art. 44-49 GDPR mechanism made transparent. + Piano Analytics (first-partied mefo1.zdf.de), Firebase Push reserved. R1 sent 2026-06-30. DSB + EDPS + LfDI RLP in CC. Embargo 2026-09-28. Deadline 2026-07-14. Eight messages over 74 days drew one reply on 2026-07-10 that named a legal basis and disputed the assessments, followed by five messages without reaction; the questions on the advertising ID, Adjust, Firebase transfers and key restrictions stay open. The headline finding is rated HIGH after the controller pointed to key restrictions and database rules. Case closed and published 2026-10-17, 19 days after the 2026-09-28 embargo.
this ledger is updated in real time as companies respond. silence is public. severity is scored primarily by CVSS v4.0, we reserve the right to deviate based on blast radius. · github.com/rfi-irfos/android-security-audit-2026
this is a useless cookie banner. it's just here to look like one * we don't use cookies, so there's nothing to consent to. don't let anyone tell you otherwise.two buttons, one closes this and throws some confetti. the other literally does nothing.