Data about a person's "sex life or sexual orientation" is special category data under Article 9 of the GDPR, and on adult and dating sites it is closer than most operators think. The Court of Justice of the EU has ruled that data which indirectly reveals a sensitive characteristic counts, so a membership record, purchase history or browsing log can become special category data if it lets someone infer a person's sexual preferences or orientation. Once it does, you need an Article 9 condition (in practice, usually explicit consent) on top of an ordinary lawful basis, plus stronger safeguards.

This guide explains the case law, where adult and dating businesses typically cross the line, and what safeguards follow. It is general information, not legal advice.

Special category data, sex life and the GDPR: the basics

Article 9(1) GDPR prohibits processing personal data "concerning a natural person's sex life or sexual orientation", along with health, biometric, genetic, racial or ethnic, political, religious and trade union data, unless one of the conditions in Article 9(2) applies. The UK GDPR contains the same rule, supplemented by Schedule 1 of the Data Protection Act 2018.

Two features make this especially relevant to adult businesses:

  • The prohibition comes first. You need both an Article 6 lawful basis and an Article 9 condition. "Contract" or "legitimate interests" alone are not enough.
  • The breach stakes are higher. Regulators and courts treat exposure of this data as serious harm, which affects DPIAs, breach notifications and fines.

When does browsing or purchase data reveal sex life? The case law

Three CJEU rulings set the current EU position:

CaseWhat the court decidedWhy it matters for adult sites
OT, C-184/20 (August 2022)Publishing a partner's name could indirectly reveal sexual orientation, so it was special category dataInference counts: data need not state the characteristic directly
Meta Platforms v Bundeskartellamt, C-252/21 (July 2023)Data collected from visits to websites and apps can be special category data if it reveals sensitive information, such as visits to dating sites or sites aimed at a particular sexual orientationBrowsing and tracking data on adult and dating services can fall within Article 9
Lindenapotheke, C-21/23 (October 2024)Order details for pharmacy products were health data, regardless of the seller's intent or whether the order was for someone elsePurchase records for products linked to sexual health or sex life may be treated the same way

National enforcement points the same way. In Norway, the Borgarting Court of Appeal in October 2025 upheld a NOK 65 million fine against Grindr, agreeing that the fact someone used an app aimed at gay and bisexual men was information about their sexual orientation, and that bundled consent to share it with advertisers was invalid. (Norway applies the GDPR through the EEA Agreement.)

In the UK, post-Brexit CJEU rulings are not binding, but the ICO's own guidance takes a similar view of inferences: if you can infer a special category characteristic with reasonable certainty, or you treat people differently because of it, you should treat it as special category data.

Article 9 GDPR and adult websites: where the line falls

Not every piece of data on an adult site is special category data. A sensible way to assess it is to ask what someone could reasonably infer from the record, and whether you use it to do so.

  • Likely special category: dating profiles stating orientation or preferences; viewing histories organised by niche; purchase histories for specific products; recommendation profiles built from those; tags that segment users by preference for marketing.
  • Arguably special category: the bare fact of membership of a general adult site or a customer list for a sexual wellness shop. After Meta and the Grindr ruling, the cautious view is to treat these as sensitive, especially where the service is niche-specific.
  • Usually not special category on its own: aggregated, anonymous traffic statistics; payment records that cannot be linked to content choices (though they are still personal data and still need protecting).

Affiliate angle: if you run a review or comparison site that tracks which niche offers a user clicks, and passes that to ad networks or builds audiences, you may be processing sexual orientation or sex life data about your visitors. Keep niche-level signals out of advertising pixels and retargeting audiences unless you have explicit consent.

For commercial adult and dating services, the realistic Article 9(2) conditions are limited:

  1. Explicit consent (Article 9(2)(a)). The main route. It must meet all ordinary GDPR consent standards (freely given, specific, informed, unambiguous) and be expressed clearly, for example a separate tick box or a confirmed statement covering the specific sensitive processing. It cannot be bundled into terms and conditions, and refusing must not lock users out of unrelated parts of the service.
  2. Data manifestly made public by the person (Article 9(2)(e)). Narrow. It may apply to information a creator deliberately publishes about themselves, but it does not cover inferences you draw from their behaviour.
  3. Legal claims (Article 9(2)(f)). Useful for retaining records needed to defend chargebacks or disputes, but only for that purpose.

Legitimate interests is not an Article 9 condition. Our guide to legitimate interest vs consent explains how the ordinary Article 6 bases interact with this. Note also that under the EU Digital Services Act, online platforms may not show adverts based on profiling using special category data at all, whatever the consent position.

Sexual orientation data and dating sites

Dating services almost always process sexual orientation data at scale, because matching depends on it. In practice that means:

  • collect explicit consent at registration for processing orientation and preferences to provide matches, separate from marketing consent;
  • never share orientation-revealing data with ad networks or analytics vendors without a further, specific explicit consent (the core failing in the Grindr case);
  • carry out a DPIA, because this is large-scale processing of special category data under Article 35(3)(b). See when a DPIA is required;
  • think about users in countries where same-sex relationships are criminalised: location, profile visibility and data-sharing choices can put people at physical risk.

Safeguards for adult site user data protection

Whatever condition you rely on, special category data calls for stronger protection. A practical baseline:

  • Minimise and separate. Keep viewing and purchase history apart from identity and payment data; pseudonymise where you can.
  • Discreet billing and communications. Neutral billing descriptors, neutral email subject lines and sender names.
  • Short retention. Delete inactive accounts and old viewing logs on a schedule.
  • Access controls. Restrict staff access, log it and review it.
  • Vendor discipline. Audit every third-party script on member pages; many tag managers leak page URLs that reveal niches.
  • UK appropriate policy document. Where you rely on certain Schedule 1 DPA 2018 conditions, UK law requires an appropriate policy document; explicit consent does not need one, but documenting your approach is good practice.
  • Breach readiness. A leak of this data will almost always be high risk to users, triggering notification to individuals. See the 72-hour breach notification rule.

Frequently asked questions

Is every adult site user's data special category data?

Not automatically, but the risk is high. Records showing which niches someone views or buys are likely to be special category data; bare membership of a niche-specific service may be too. Treat it as sensitive unless you have a documented reason not to.

Can I rely on my terms and conditions for consent?

No. Explicit consent must be separate and specific. Consent buried in terms of service, or made a condition of using the service when the data isn't needed for it, is unlikely to be valid.

Does this apply to creators' data as well as fans'?

Yes. Platforms and agencies may hold information about creators' sexual orientation, sex life and health. The same Article 9 rules apply, alongside identity and age verification records for performers.

Next steps

Map where sex life and orientation data appears in your systems, decide your Article 9 condition for each use and record it in a DPIA. For dating offers specifically, our guide to dating affiliate programs covers what to check in a partner's data handling, and our GDPR and cookies section has the rest of this series.