DPIA for AI Systems: When It's Required and How to Do It

What is a DPIA, and why does the AI Act make it more urgent?
The Data Protection Impact Assessment (DPIA) is the analysis GDPR Article 35 requires before starting a processing operation that's likely to result in a high risk to people's rights. It isn't a form you fill in and file away — it's the document data protection authorities ask to see first when investigating a high-risk processing operation, and its absence has been cited as an aggravating factor in multiple enforcement decisions.
Spain's AEPD has been explicit that AI systems capable of acting autonomously — agents that make decisions or take actions without human intervention at every step — disrupt the usual data flows and make the impact assessment even more necessary before deployment, not less.
When is it mandatory?
The general rule under Article 35.1 is "likely high risk" — deliberately broad wording. But Article 35.3 sets three cases where a DPIA is always mandatory, with no case-by-case judgment call needed:
- Systematic and extensive evaluation of personal aspects based on automated processing, including profiling, that leads to decisions producing legal effects or similarly significantly affecting the person.
- Large-scale processing of special categories of data (health, ethnicity, biometrics, etc.) or data on criminal convictions and offences.
- Systematic monitoring of a publicly accessible area on a large scale — think video surveillance with behavioral analytics, not just cameras recording footage.
Beyond these three cases from the Regulation itself, data protection authorities publish their own lists of processing types that require a DPIA (Art. 35.4), and lists of exempt ones (Art. 35.5) — worth checking both before assuming a given processing operation does or doesn't need one.
The direct bridge to the AI Act
Here's the connection most companies miss: if an AI system processes personal data — and the vast majority of Annex III high-risk systems do, since we're talking about HR, credit scoring, education, or biometrics — its high-risk classification under the AI Act is almost always, in practice, a sign that one of the GDPR Article 35 triggers is also met. Treating the AI Act and GDPR as two separate exercises duplicates work that, framed correctly, is essentially the same analysis documented twice.
What a DPIA must include (Art. 35.7)
| Element | What it answers |
|---|---|
| Systematic description | What's being processed, for what purposes, and on what legal basis. |
| Necessity and proportionality | Is this processing necessary for the stated purpose, or is there a less invasive way? |
| Risk assessment | What specific risks exist for the rights and freedoms of the people affected. |
| Mitigation measures | What's being done to bring those risks down to an acceptable level. |
When prior consultation with the regulator is required (Art. 36)
If, after applying the planned mitigation measures, the DPIA itself concludes that the residual risk remains high, GDPR Article 36 requires prior consultation with the supervisory authority before starting the processing. This isn't the usual path — it's the exception for when an honest assessment concludes the risk can't be brought down enough on your own. Skipping this consultation when it applies is, on its own, an additional compliance failure beyond the underlying processing itself.
The case that explains it better than any regulation
In 2021, Spain's AEPD fined supermarket chain Mercadona €2.52 million over a facial recognition system deployed in stores without a solid prior impact assessment. The case sums up the real risk well: it isn't necessarily that the technology itself was unlawful — it's that it went live without first documenting why it was necessary, what risks it carried, and how those risks would be mitigated. That's exactly what a DPIA requires you to answer before you start, not after something goes wrong.
The EDPB's nine criteria: how to decide in practice
Beyond the three automatic cases in Article 35.3, European data protection authorities (the EDPB, endorsing the earlier Article 29 Working Party guidelines known as WP248) published nine criteria for judging whether processing is "likely to result in a high risk". The working rule: if the processing meets two or more criteria, a DPIA is generally required. Sometimes a single criterion is enough, and if you decide not to carry out a DPIA you should document why.
| # | EDPB criterion | What it looks like in an AI system |
|---|---|---|
| 1 | Evaluation or scoring (including profiling and prediction) | Credit scoring, candidate ranking, churn or fraud prediction. |
| 2 | Automated decision-making with legal or similar effect | Automatically rejecting a loan, an application or a claim with no human review. |
| 3 | Systematic monitoring | Employee productivity tracking, video analytics, behavioral monitoring online. |
| 4 | Sensitive or highly personal data | Health, biometrics, location, financial data, private communications. |
| 5 | Large-scale processing | Many people, many records, wide geographic reach or long duration. |
| 6 | Matching or combining datasets | Enriching customer data with third-party sources to train or feed a model. |
| 7 | Vulnerable data subjects | Employees, children, patients, job applicants: anyone in a position of imbalance. |
| 8 | Innovative use or new technology | Generative AI, agents, emotion recognition, new biometric methods. |
| 9 | Processing that blocks a right, service or contract | Scores that decide who gets credit, insurance, housing or a job. |
Worked example, a CV-screening tool. It ranks candidates (criterion 1), may discard applications automatically (2), involves applicants, who are in a position of imbalance (7), uses an innovative technology (8) and can block access to a job (9). That is five criteria out of nine, so a DPIA is clearly required before launch.
Frequently asked questions
Is a DPIA always required for an AI system?
No. A DPIA is required when the processing is likely to result in a high risk to people's rights. In practice, most AI systems that process personal data for scoring, profiling or automated decisions meet two or more of the EDPB's nine criteria, which is the usual signal that one is needed.
How many EDPB criteria trigger a DPIA?
As a rule of thumb, two or more. A single criterion can be enough in some cases, and when you decide a DPIA is not needed you should record the reasoning.
Who has to carry out the DPIA?
The controller, meaning the organization that decides the purposes and means of the processing. Where a data protection officer has been designated, the controller must seek their advice (Art. 35.2). Processors and AI providers help with the information.
How does a DPIA relate to the AI Act's fundamental rights impact assessment?
Article 27 of the AI Act requires a fundamental rights impact assessment from certain deployers of high-risk systems. When part of its content is already covered by a DPIA under GDPR Article 35, the fundamental rights assessment complements that DPIA instead of repeating it.
When do I have to consult the regulator before starting?
Under GDPR Article 36, when the DPIA concludes that the residual risk is still high after applying your mitigation measures. In that case you consult the supervisory authority before starting the processing.