Back to all lessons
Awareness Lessons
2 months ago

Grindr's £26M HIV Data Sharing Settlement: A Costly Lesson in Sensitive Data Governance

Written by AI from the linked story. Not reviewed by an editor. How this works

Grindr shared highly sensitive personal data — including users' HIV status — with third-party advertising partners without adequate legal basis or transparency, violating core data protection principles. This type of special category data carries the highest level of legal protection under GDPR and equivalent UK law, meaning any processing requires explicit, informed consent. The failure to implement technical and contractual controls over third-party data flows exposed users to potential discrimination, stigma, and serious personal harm. This case illustrates that commercial data-sharing practices must be rigorously audited against privacy obligations, especially when sensitive health information is involved. The £26 million settlement underscores that regulatory and litigation risk from data misuse can far exceed any short-term commercial gain.

Tactical Insight

Immediate actions

  • Conduct an urgent audit of all third-party data-sharing agreements to identify whether special category data (health, sexuality, religion, etc.) is being transmitted without explicit user consent.
  • Implement technical controls (e.g., data masking, field-level encryption) to prevent sensitive attributes from being included in advertising or analytics data payloads.

Long-term improvements

  • Establish a formal Data Protection Impact Assessment (DPIA) process mandating review before any new third-party data integration or SDK is introduced.
  • Appoint or empower a Data Protection Officer (DPO) with authority to halt data-sharing practices that lack a lawful processing basis under GDPR/UK GDPR.
  • Adopt a data minimisation strategy ensuring only strictly necessary data is collected, retained, and shared with any external party.

Detection & Governance measures

  • Deploy continuous monitoring of outbound data flows to third-party SDKs and APIs to detect unexpected transmission of sensitive fields.
  • Implement a regular third-party vendor privacy review process, including contractual Data Processing Agreements (DPAs) with audit rights.
  • Maintain a publicly accessible and accurate Record of Processing Activities (RoPA) to ensure accountability and enable rapid regulatory response.

Back this up with a control

All controls and vendors

Training helps people spot this. These controls make the attack fail even on the day someone does not.