Privacy

When is a DPIA required under the GDPR?

Direct answer

A Data Protection Impact Assessment (DPIA) is mandatory under GDPR Article 35 whenever processing is likely to result in a high risk to the rights and freedoms of individuals. Article 35(3) names three cases that always require one: systematic and extensive profiling with legal effects, large-scale special-category data processing, and systematic monitoring of a publicly accessible area at scale.

The EDPB adds nine criteria; two or more typically require a DPIA.

What are the nine criteria, and how do you apply them?

The Article 29 Working Party guidelines on DPIAs (WP248 rev.01), endorsed by the EDPB, turn the high-risk test of Article 35 into nine criteria:

  • Evaluation or scoring, including profiling and predicting, for example building behavioural or marketing profiles from use of a website.
  • Automated decision-making with legal or similarly significant effect.
  • Systematic monitoring, including data collected through networks or the monitoring of a publicly accessible area.
  • Sensitive data or data of a highly personal nature: special categories under Article 9, criminal convictions and offences under Article 10, and data such as location or financial data.
  • Data processed on a large scale, judged by the number of people concerned, the volume and range of data, the duration of the processing and its geographical extent.
  • Matching or combining datasets in a way that would exceed the reasonable expectations of the people concerned.
  • Data concerning vulnerable data subjects, such as children, employees, patients or the elderly.
  • Innovative use or new technological or organisational solutions, such as combining fingerprint and face recognition for access control.
  • Processing that in itself prevents people from exercising a right or using a service or a contract, such as screening loan applicants against a credit reference database.

In most cases, processing that meets two criteria requires a DPIA, and the more criteria it meets, the more likely the high risk. One criterion can be enough in some cases. The guidelines also give examples that need none: a generic daily newsletter to subscribers meets only the large-scale criterion.

Do national DPIA lists change the answer?

They add to it. Article 35(4) requires each supervisory authority to establish and publish a list of the kinds of processing that always need a DPIA, and to communicate it to the EDPB. Article 35(5) lets an authority also publish a list of processing for which no DPIA is required. Where a list covers processing related to offering goods or services, or monitoring behaviour, in several member states, the authority must first go through the EDPB consistency mechanism (Article 35(6)).

Check the list of the authority competent for your processing before you rely on the nine criteria alone. In France, for example, the CNIL list includes health data processed by health establishments for patient care and profiling for human resources management. A list entry is not the whole story either: processing that is not on the list can still be high risk under the general test.

When is a DPIA not required?

The guidelines name five cases:

  • The processing is not likely to result in a high risk.
  • Its nature, scope, context and purposes are very similar to processing that already has a DPIA, whose results can be reused (Article 35(1) allows one assessment for a set of similar operations).
  • It was checked by a supervisory authority or a data protection official before May 2018 under Directive 95/46/EC and has not changed since.
  • It has a legal basis in EU or member state law under point (c) or (e) of Article 6(1), the law regulates the specific operation, and a DPIA was carried out when that legal basis was adopted (Article 35(10)), unless the member state requires one anyway.
  • It is on the authority’s Article 35(5) list of processing that needs no DPIA.

Existing processing is not exempt for good. A DPIA becomes necessary when its risks change, for example through a new technology, a new purpose or new recipients. If an activity meets the criteria but you conclude it is not likely to be high risk, record why, together with the DPO’s views. The steps of the assessment itself are covered in what is a DPIA under GDPR?

How does the Swiss FADP test compare?

Article 22 of the revised FADP uses the same trigger: an impact assessment is required beforehand when processing is likely to result in a high risk to the personality or fundamental rights of the person concerned. The law gives two examples, large-scale processing of sensitive personal data and systematic large-scale monitoring of public areas, and says the risk depends on the nature, extent, circumstances and purpose of the processing, in particular when new technologies are used.

The exemptions differ from the GDPR. A private controller is exempt where it is required by law to process the data (Article 22(4)). It can also dispense with the assessment where it uses a system, product or service certified for the intended use, or complies with a code of conduct that is based on an impact assessment, provides protective measures and has been submitted to the FDPIC (Article 22(5)). See the Swiss FADP guide.

How Acuna GRC handles it

Data Privacy in Acuna GRC carries a nine-question DPIA screener on every processing activity that derives the risk level and whether a DPIA is required, so the question is answered as part of recording the activity, not as a separate project.

Sources

  1. Article 29 Working Party, Guidelines on Data Protection Impact Assessment (WP248 rev.01), endorsed by the EDPB
  2. Regulation (EU) 2016/679 (GDPR), Article 35
  3. CNIL, list of processing operations for which a DPIA is required
  4. Federal Act on Data Protection (FADP), Article 22

This page explains the rules in general terms and is not legal advice.

Frequently asked

What if it is unclear whether a DPIA is required?

Carry one out. The WP29 guidelines, endorsed by the EDPB, recommend a DPIA wherever it is not clear whether one is needed, because it is a useful tool for showing compliance in any case.

Does processing that started before May 2018 need a DPIA?

Not automatically. It needs one where it is likely to be high risk and its risks have changed, for example through a new technology or a new purpose. Processing that a supervisory authority checked under the old directive and that runs unchanged is not caught.

Does one criterion ever trigger a DPIA on its own?

It can. The guidelines say two criteria will require a DPIA in most cases, but a controller can conclude that processing meeting only one criterion is high risk. The three cases in Article 35(3) always require one.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US