mein dm (de.dm.meindm.android): 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 mein dm.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
mein dm
Private
2026-06-21
90d ago
Waiting
Critical
Your purchase history at dm can reveal whether you are pregnant or managing a health or sexual-health condition, simply from the pattern of what you buy. That inference-ready data is shared with three separate advertising networks, including a cross-app tracking ID via Adjust, and dm has no formal risk assessment on file for data this sensitive, even though Germany's data-protection regulator has already logged the complaint as received.
de.dm.meindm.android. dm-drogerie markt GmbH & Co. KG. 2C 2H 1M. Firebase key hardcoded (project mein-dm). Three ad networks (incl. Adjust + AD_ID cross-app linkage) on purchase data from which pregnancy/health/sexual-health status is inferable (Art. 9-adjacent) - no DPIA found for this high-risk combination. R1 sent 2026-06-21 to datenschutz@dm.de, real regulator ACK (LfDI BW) received, dm itself silent, FOLLOW-UP 2026-06-28
click to expand
GDPR Art. 32GDPR Art. 35GDPR Art. 9
Yes
Closed
Disclosure
90d 00h 00m 00s
Published

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.