Headspace (com.getsomeheadspace.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 Headspace.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Headspace
Private
2026-06-22
95d ago
CS deflect
Critical
Headspace ships a continuous screen recorder that keeps running while a user is in a live video therapy session with a licensed therapist or speaking to its AI voice journaling assistant about a mental health crisis, sending that recording to a US company. Therapy engagement is also shared across four separate marketing systems at once. When RFI-IRFOS reported this, Headspace's only response was an automatic link to its bug-bounty program, treating deeply sensitive mental health data as an ordinary software bug, and no human ever engaged with the finding afterward.
com.getsomeheadspace.android. All six findings re-scored under CVSS v4.0. Continuous Sentry session-replay screen recording, active during live WebRTC therapy sessions and AI voice journaling about mental health crises, reaches HIGH/8.7 on the computed CVSS score alone and is held at CRITICAL under blast-radius escalation as the single most sensitive finding in this entire audit campaign. Therapy-engagement behavioral data shared across four marketing platforms (Amplitude, Braze, Facebook, AD_ID) reaches HIGH without escalation. Health Connect boundary risk and a hardcoded Firebase key correct to MEDIUM; enterprise SDK bloat and a broad but individually-explicable permission surface both correct to LOW. bugbounty@headspace.com redirected the disclosure to HackerOne within minutes, a response RFI-IRFOS named the same day as Pattern 7, Scope Deflect / Bug Bounty Redirect, since a bug-bounty triage team has no authority over Art. 9 special-category processing decisions. Eight messages sent across 70 days to bugbounty@, privacy@, legal@, and security@headspace.com; no further reply of any kind was ever received. Case closed and published 2026-09-25, one day after the stated 2026-09-24 embargo.
click to expand
GDPR Art. 9(1)GDPR Art. 26
Yes
Closed
Disclosure
95d 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.