Bitpanda (AT) (com.bitpanda.bitpanda): 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 Bitpanda (AT).
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Bitpanda (AT)
Private
2026-06-26
91d ago
CS deflect
High
Bitpanda's trading app is built to start Google tracking before you have even unlocked your phone, so there is no way consent could have happened first. It also scans your passport chip and takes a biometric selfie for identity checks through two separate, parallel identity-verification systems, then sends your location and trading activity to a New York marketing company linked to your advertising ID, on a platform regulated under EU investment rules. When RFI-IRFOS raised this, the only responses across seventy-eight days were two identical automated customer-support ticket confirmations that addressed none of it.
com.bitpanda.bitpanda v3.26.0. All six findings re-scored under CVSS v4.0. Fourthline's dual biometric KYC pipeline (NFC passport chip + selfie liveness, running in parallel with a second, entirely separate KYC SDK with no documented DPIA justification) and Braze's (NY) transfer of trading behavior and location data linked to a hardware AD_ID both reach HIGH on their own computed CVSS scores. Pre-consent Firebase initialization with directBootAware=true, an Adjust attribution SDK linking ad campaigns to trading behavior, and an auto-initializing Datadog US session monitor all correct to MEDIUM. Eight messages sent across 78 days to privacy@bitpanda.com, info@ and eric.demuth@bitpanda.com blocked by an enterprise mail policy throughout; the only inbound replies were two identical automated Zendesk support-ticket acknowledgments addressing none of the six findings. No substantive reply was ever received. Case closed and published 2026-09-25, one day after the stated 2026-09-24 embargo.
click to expand
GDPR Art. 7GDPR Art. 9
Yes
Closed
Disclosure
91d 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.

© 2026 RFI-IRFOS  ·  Graz, Austria  ·  GISA 39261441  ·  UID ATU83405245

Foundation

Intelligence

Applications

Repositories

Crates (crates.io)

all packages →

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.