FlixBus (de.flixbus.app): 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 FlixBus.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
FlixBus
Private
2026-06-25
92d ago
Silent
High
At FlixBus, a single tap granting permission for notifications also quietly enrolls you in Braze's marketing and location-tracking platform, with no separate consent screen for that second, distinct purpose, and the app tracks when you enter or leave bus stations and sends that to US servers.
de.flixbus.app v9.81.0. All findings re-scored under CVSS v4.0. A Braze flag conflating push-notification permission with marketing-platform consent, plus active geofence/continuous location tracking to a US datacenter, reaches HIGH on the computed score alone (Art. 7(2)). A hardcoded Google Maps key, a production debug activity with inconsistent Crashlytics/Analytics consent gating, and undisclosed advertising-attribution tracking correct to MEDIUM. Twelve messages sent across 79 days, one bounce, zero reply of any kind ever.
click to expand
GDPR Art. 7(2)GDPR Art. 5(1)(f)GDPR Art. 5(1)(b)
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.