A DPIA (data protection impact assessment) is required whenever processing is "likely to result in a high risk" to people's rights and freedoms, and in particular when you process special category data on a large scale, systematically monitor people, profile them, or use innovative technology such as biometric age estimation. For most adult sites, dating services and creator platforms, at least one of those triggers applies, so the honest answer to "when is a DPIA required?" is: before you launch, and again whenever you add something risky like age assurance.
This guide sets out the legal triggers under Article 35 of the GDPR and UK GDPR, the regulators' lists, and a worked walkthrough for a hypothetical adult site. It is general information, not legal advice.
When is a DPIA required under Article 35?
Article 35(3) names three cases where a DPIA is always required:
- Systematic and extensive evaluation of people based on automated processing, including profiling, that leads to decisions with legal or similarly significant effects.
- Large-scale processing of special category data (including data about sex life or sexual orientation) or criminal offence data.
- Large-scale systematic monitoring of a publicly accessible area.
Beyond those, each regulator publishes a list of processing types that need a DPIA. The UK ICO's list, in its guidance on when you need to do a DPIA, includes innovative technology, large-scale profiling, biometric data, data matching, invisible processing, online tracking of behaviour, targeting children or vulnerable people, and processing where a breach could put people's physical safety at risk. Several of these need a DPIA only when combined with another risk factor.
The EDPB's nine criteria and the "rule of two"
European guidance (originally from the Article 29 Working Party, endorsed by the EDPB) lists nine indicators of high risk: evaluation or scoring; automated decisions with significant effect; systematic monitoring; sensitive or highly personal data; large scale; matching or combining datasets; vulnerable data subjects; innovative technology; and processing that stops people using a service. As a rule of thumb, two or more indicators mean you should carry out a DPIA, but one strong indicator can be enough. If you decide not to do one, record why.
Why adult sites usually hit the triggers
A data protection impact assessment on an adult or dating site is rarely optional, because the business model tends to stack several high-risk indicators:
| Feature | High-risk indicator |
|---|---|
| Membership, purchase or viewing history on an adult service | Sensitive or highly personal data; possibly special category data about sex life |
| Dating profiles with preferences or orientation | Special category data, often at scale |
| Age verification or facial age estimation | Innovative technology; possibly biometric data; can block access to a service |
| Behavioural recommendations and ad targeting | Profiling; tracking online behaviour; data matching |
| Creator payouts and identity checks | Identity documents; financial data; risk of harm if exposed |
The reason this matters is the harm profile. A leak of an adult-site customer list carries a real risk of embarrassment, blackmail, discrimination or worse. That is exactly the "high risk to rights and freedoms" Article 35 is aimed at. Our guide to special category data on adult sites explains when browsing and purchase data cross into Article 9 territory.
Age assurance is a fresh trigger. If you are adding age checks to meet the Online Safety Act or a national law in the EU, treat it as new processing that needs its own DPIA, even if you already have one for the site. The EDPB's 2025 statement on age assurance says a DPIA will often be required. See age verification and GDPR.
How to do a DPIA: a step-by-step walkthrough
Article 35(7) sets the minimum content. In practice, a DPIA for a small operator can be a structured document of a few pages, as long as it is honest and specific. Here is the process, using a hypothetical example: a UK-based operator launching a subscription video site for UK and EU customers, with facial age estimation at sign-up.
- Describe the processing. What data (email, payment token, viewing history, face image for age estimation), from whom, for what purposes, who receives it (payment processor, age-assurance provider, hosting, analytics) and where it is stored.
- Consult where appropriate. Talk to your developers, your age-assurance provider and, if you have one, your DPO. You can seek users' views, for example through a short survey, where it is practical.
- Assess necessity and proportionality. Do you need each data item? Could you use an age token instead of storing a face image? Is your retention period justified? What is your lawful basis for each purpose?
- Identify the risks to individuals. Think from the user's side: exposure of membership, inference of sexual preferences, misuse of biometric data, wrongly blocked adults, function creep by vendors.
- Score each risk for likelihood and severity (for example, remote, possible or probable against minimal, significant or severe).
- Set out mitigations and score the residual risk. In the example: the provider deletes images immediately after estimation, the site receives only an over-18 result, viewing history is pseudonymised, and billing descriptors are discreet.
- Sign off and act. Record who approved it, which actions were agreed and who owns them.
- Review. Revisit the DPIA when you change provider, add features or after a breach.
If high risk remains: prior consultation
If, after mitigation, a high risk remains that you cannot reduce, Article 36 requires you to consult the regulator before processing starts. In the UK that means the ICO. This is uncommon for well-designed services, and it usually signals that the design itself needs to change.
DPIA template: what a good one contains
The ICO publishes a sample DPIA template and guidance on completing it, and many EU regulators publish their own. Whichever you use, check yours covers:
- a clear description of data flows, including every processor and sub-processor;
- the lawful basis for each purpose, and the Article 9 condition if special category data is involved;
- a necessity and proportionality section that actually considers less intrusive alternatives;
- a risk register with likelihood, severity and residual risk;
- named owners and dates for each mitigation;
- a link to your breach response plan, because severity of harm feeds directly into whether you must notify users (see data breach notification and the 72-hour rule).
ICO DPIA checklist: common mistakes
- Doing it after launch. A DPIA is meant to shape the design, not justify it afterwards.
- Copying a template without adapting it. Generic risks such as "unauthorised access" without any link to your actual systems add nothing.
- Ignoring vendors. Age assurance, payment and analytics providers often carry the highest risks. Ask for their own DPIAs, certifications and retention commitments.
- Treating it as a one-off. Adding a recommendation engine or a new traffic partner can change the risk profile.
- Not recording a decision not to do one. If you conclude a DPIA isn't needed, keep a short note explaining why.
Frequently asked questions
Does a small affiliate site need a DPIA?
Usually not, if it only runs ordinary analytics and affiliate links. A DPIA becomes likely if you build user accounts, collect preferences, run large-scale profiling or add age checks yourself.
Do I have to publish my DPIA?
No. There is no legal duty to publish it, though some organisations publish a summary to build trust. You must be able to show it to the regulator on request.
Who should carry out the DPIA?
The controller is responsible. If you have appointed a data protection officer, you must seek their advice. Processors such as age-assurance vendors should help by providing the information you need.
Next steps
If age assurance is the trigger for your DPIA, compare vendors in our compliance and verification services directory and read our guide to choosing an age verification provider, asking each one for their own DPIA and retention policy before you sign.