Amazon Music (com.amazon.mp3): 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 Amazon Music.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Amazon Music
NASDAQ
2026-06-21
90d ago
ACK
Critical
What you listen to on Amazon Music does not stay inside the music app. It flows directly into the same customer-profiling system that powers Amazon's advertising business, so a music subscription becomes raw material for ad-targeting decisions made elsewhere across Amazon's platform.
CUSTOMER_ATTRIBUTE_SERVICE: music listening behaviour feeds Amazon's $47B DSP advertising profile. Alexa sends all playback events. DETECT_SCREEN_CAPTURE + BLE advertising
click to expand
GDPR Art. 32GDPR Art. 6(1)(b)(f)GDPR Art. 5(1)(b)+4
Yes
Closed
Disclosure
90d 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.