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.
262+
Critical findings recorded
Confirmed findings copied to regulators, not theoretical risks.
970+
Weak points found and documented
Third-party tracking we have provably found inside the binary.
567+
Endpoints investigated
Real servers and countries where data actually flows.
132+
SDK instances mapped
Reusable libraries correlated across the entire corpus.
1 of 387 entries · sorted by elapsed ↓
Showing the report for FRITZ! Smart Home.
OrganisationNotifiedStatusSEVIntel (click to expand)StatutesResolvedDisclosureElapsedReport
FRITZ! Smart Home
PRIVATE
2026-07-01
108d ago
RESOLVED
MEDIUM
FRITZ!, a brand built on the promise that your network data stays inside your own home, actually sends analytics and crash reports to Google in the US from the very first time you open the app, unless you find and switch off a setting buried in the menu. Aside from that, it is one of the more disciplined smart-home apps reviewed, but the core privacy promise does not hold up for the app itself.
de.avm.android.smarthome. FRITZ! GmbH (ex-AVM, Berlin). The FRITZ!Box maker - a brand sold on data staying home - ships Firebase Analytics + Crashlytics on an OPT-OUT basis (preference literally named tracking_opt_out, default off), live to Google US from first launch before consent. Global cleartext, two extractable Google keys. Otherwise disciplined (no ad / attribution / Chinese SDKs, SQLCipher, ad-ID off) - the closest of the smart-home set to the Bosch benchmark. R1 2026-07-01. Nine messages over 73 days drew no reply of any kind. Case closed and published 2026-10-17, 18 days after the 2026-09-29 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.