Babbel (com.babbel.mobile.android.en): Privacy & Security Findings

report - rfi-irfos
Skip to content

Permanent Disclosure Ledger

The discipline, demonstrated

On behalf of our research partners, we investigate publicly distributed Android and iOS apps: we decompile them, follow their code and data flows, and trace every connection to the servers it reaches. Hundreds of agents work through each app and join the technical evidence into one picture, which our specialists then review and verify.

387+
Android/iOS apps audited
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
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 Babbel.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Babbel
Private
2026-06-25
92d ago
Silent
Medium
Babbel starts Google and Facebook tracking before you have given consent, and it reads a permanent hardware ID from your phone so your language-learning activity can still be linked back to you even after you uninstall and reinstall the app. It also carries advertising permissions that let it group paying subscribers into targeting cohorts usable in other apps entirely.
com.babbel.mobile.android.en v22.2.2. All findings re-scored under CVSS v4.0, correcting to MEDIUM. Pre-consent Firebase+Facebook ContentProvider init. Adjust IMEI fingerprinting - unique hardware ID linked to language-learning behavior across uninstalls. All four Privacy Sandbox permissions incl. Custom Audience cross-app cohort targeting on a paid language app. Eleven messages sent across 84 days, one automated acknowledgment, zero substantive human reply ever.
click to expand
GDPR Art. 7GDPR Art. 5(1)(b)GDPR+1
Yes
Closed
Disclosure
92d 00h 00m 00s
Published
PDF

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.