Privacy

What is a DPIA under GDPR?

Direct answer

A Data Protection Impact Assessment (DPIA) is required under GDPR Article 35 when processing is likely to result in a high risk to the rights and freedoms of individuals. This includes systematic profiling with legal effects, large-scale processing of special categories of data, and systematic monitoring of public areas.

A DPIA must describe the processing, assess necessity and proportionality, identify risks, and define mitigating measures. If residual risk remains high after mitigation, the controller must consult the supervisory authority under Article 36.

Who carries out a DPIA, and who has to be involved?

The controller is responsible for making sure the DPIA is carried out (Article 35(2)). The work itself can be done by someone else, inside or outside the organisation, but the controller stays accountable for it.

Three other parties have a defined role:

  • The data protection officer, where one is designated. The controller must seek the DPO’s advice, and the EDPB-endorsed guidelines say that advice, and the decisions taken on it, should be documented in the DPIA. See can a DPO be external?
  • Processors. Where a processor performs all or part of the processing, it assists the controller and provides the information needed (Article 28(3)(f)).
  • Data subjects or their representatives. Where appropriate, the controller seeks their views (Article 35(9)), for example through a survey or a question to staff representatives. If the controller decides not to, or decides against their views, it documents why.

When should a DPIA be done, and when is it reviewed?

Before the processing starts (Article 35(1)). The guidelines recommend starting as early as practicable in the design, even while some details are still unknown, and updating the assessment as the project develops. The fact that a DPIA may need updating after go-live is not a reason to postpone it.

A DPIA is a continual process, not a one-time exercise. Article 35(11) requires the controller to review whether processing still matches the assessment, at least when the risk changes: a new technology, a new purpose, new recipients or a new category of data subjects. Processing that already exists is also caught when its risks change.

The starting point is usually the record of processing activities: it already describes the purpose, data, recipients and transfers that the DPIA has to assess. Whether an activity needs a DPIA at all is covered in when is a DPIA required?

What happens when the residual risk stays high?

If the measures you identify cannot bring the risk down to an acceptable level, you must consult the supervisory authority before processing (Article 36(1)) and send it the DPIA with your request (Article 36(3)). The guidelines give examples of an unacceptable residual risk: consequences for individuals that are significant or irreversible, or a risk that is obvious to occur, such as a known vulnerability left unpatched.

If the authority considers the processing would breach the GDPR, it gives written advice within up to eight weeks of receiving the request, extendable by six weeks depending on the complexity of the processing (Article 36(2)).

The Swiss FADP works in a similar way: Article 22 requires an impact assessment for processing likely to result in a high risk, and Article 23 requires consulting the FDPIC if a high risk remains despite the measures. A private company that has appointed a data protection advisor who meets the legal conditions can consult the advisor instead. See the Swiss FADP guide.

What are the most common DPIA mistakes?

  • Running it after launch. The DPIA is meant to inform the decision to process, so it belongs in the design phase.
  • Assessing risk to the company instead of risk to people. A DPIA takes the perspective of the data subjects, unlike an information security risk assessment, which focuses on the organisation.
  • Not documenting a decision not to do one. Where a processing operation matches the high-risk criteria but you conclude it is not likely to result in a high risk, the guidelines expect you to record the reasons and the DPO’s views.
  • Listing measures that never get implemented. The measures in the DPIA have to exist in practice, and the assessment has to be revisited when they change.
  • Filing it and forgetting it. Under the GDPR, failing to carry out a required DPIA, carrying it out incorrectly or failing to consult the authority when required can lead to fines of up to EUR 10 million or 2% of worldwide annual turnover, whichever is higher.

How Acuna GRC handles it

In Data Privacy in Acuna GRC, a nine-question screener on each processing activity shows whether a DPIA is required, and the DPIA wizard (Threshold, Necessity, Risks and Review) starts pre-filled from that activity.

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), Articles 28, 35 and 36

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

Frequently asked

Does a DPIA have to be published?

No. Publication is not a GDPR requirement. The guidelines encourage publishing at least a summary or conclusion to build trust, especially where the public is affected, but the full DPIA goes to the supervisory authority only in a prior consultation or when it asks for it.

Can one DPIA cover several processing operations?

Yes, if they are similar. Article 35(1) allows a single assessment for a set of similar processing operations that present similar high risks, for example video surveillance across all stations of one railway operator. Processing with a different nature, scope, context or purpose needs its own assessment.

Who decides whether a DPIA is good enough?

The controller, with the advice of its DPO where one is designated. The GDPR lets the controller choose its methodology, as long as the DPIA contains the minimum content of Article 35(7) and is a genuine assessment of risks that leads to measures.

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