Skip to content
Certifyi

Glossary

What is a Data Protection Impact Assessment (DPIA)?

A Data Protection Impact Assessment (DPIA) is a GDPR-required assessment of processing likely to result in a high risk to individuals. It records the processing, the risks to people and the measures that reduce them, and it must be completed before the processing starts.

When a DPIA is required

Article 35 requires a DPIA when processing is likely to result in a high risk to people’s rights and freedoms, particularly where new technologies are used. Supervisory authorities publish lists of processing that needs one in their country.

European guidance adds nine criteria, such as data about vulnerable people or the innovative use of technology, and says processing that meets two or more will usually need a DPIA. Article 35(3) names three cases where one is always required.

  • Profiling with significant effects. Systematic and extensive evaluation of people based on automated processing, including profiling, that leads to decisions with legal or similarly significant effects.
  • Sensitive data at scale. Large-scale processing of special categories of data, such as health data, or of data about criminal convictions and offences.
  • Public monitoring. Systematic monitoring of a publicly accessible area on a large scale.

What a DPIA contains

Article 35(7) sets the minimum content: a systematic description of the processing and its purposes, an assessment of whether the processing is necessary and proportionate to those purposes, an assessment of the risks to individuals, and the measures planned to address them, including safeguards and security measures.

The risks assessed are risks to the people whose data is processed. A DPIA asks what happens to an individual if their data is lost, misused or used to make a decision about them, how likely that is and how severe it would be.

If the assessment shows a high risk that the planned measures cannot reduce, Article 36 requires the controller to consult the supervisory authority before starting.

Keeping it useful after sign-off

A DPIA describes processing at one point in time. Article 35(11) asks the controller to review whether processing still matches the assessment, at least when the risk changes, such as when a new data source, vendor or use is added. Keep the DPIA with the record of processing for that activity so the link is clear to a regulator.

DPIAs now often sit alongside AI assessments. The EU AI Act requires certain deployers of high-risk AI systems to carry out a fundamental rights impact assessment, and where a DPIA already covers some of the same ground, the new assessment complements it.

Questions

Data Protection Impact Assessment (DPIA), answered

Is a DPIA mandatory?

For processing likely to result in a high risk to individuals, yes. For other processing it is optional, but a short screening record showing why no DPIA was needed is good practice.

Who is responsible for a DPIA?

The controller. Where a data protection officer is designated, Article 35(2) requires the controller to seek the DPO’s advice. Record that advice and whether it was followed.

Is a DPIA the same as a privacy impact assessment?

They cover similar ground. DPIA is the GDPR term, with a minimum content set by Article 35. Privacy impact assessment is an older, more general term used in other countries and frameworks.

Working through this for an audit?

Talk it through with someone who has run the audit before, or look up another term.

  • Each customer workspace has its own database
  • Every change written to a tamper-evident activity log
  • Auditors get scoped, read-only access
  • AI suggestions wait for a person to accept them
Scroll to Top