Skip to content
EU GDPR · EU-GDPR-ART35-DPIA

EU GDPR Article 35(1), (3) and (7) — Data protection impact assessment

Carry out a data protection impact assessment before processing that is likely to result in a high risk to people's rights and freedoms

HIGHAssessment dutyRisk assessmentBinding regulationIn forceEnforceable from 25 May 2018

Where this comes from

Provision: Article 35(1), (3) and (7) — Data protection impact assessment

Instrument: EU General Data Protection Regulation (Regulation (EU) 2016/679)

Citation: Article 35, Regulation (EU) 2016/679

Text version: Regulation (EU) 2016/679 (GDPR), OJ L 119, 4.5.2016, p. 1 (CELEX 32016R0679)

Checked against the source: 2 September 2026

Read the official text ↗

Who it applies to

Personal data is processed (GDPR Art. 2(1)) — all of these:

  • Service processes personal data

A high-risk screening signal is present (Art. 35(1); WP248 rev.01) — any one of these:

  • DPIA screening criteria includes Evaluation or scoring, including profiling and predicting
  • DPIA screening criteria includes Automated decision-making with legal or similarly significant effect
  • DPIA screening criteria includes Systematic monitoring of people, including in publicly accessible areas
  • DPIA screening criteria includes Sensitive data, or data of a highly personal nature
  • DPIA screening criteria includes Processing on a large scale
  • DPIA screening criteria includes Matching or combining datasets from different processing operations
  • DPIA screening criteria includes Data about vulnerable people, such as children, employees or patients
  • DPIA screening criteria includes Innovative use of new technological or organisational solutions
  • DPIA screening criteria includes Processing that stops people exercising a right, or using a service or contract
  • Service makes solely automated decisions with legal or similarly significant effects
  • Service deploys AI systems in a professional capacity

…unless:

  • Art. 2(2)(c): the Regulation does not apply to processing of personal data 'by a natural person in the course of a purely personal or household activity'. Recital 18 keeps controllers or processors providing the means for such processing in scope. (GDPR Art. 2(2)(c))
  • Art. 35(10): where processing under Art. 6(1)(c) or (e) has a legal basis in Union or Member State law, that law regulates the specific processing operation, and a data protection impact assessment 'has already been carried out as part of a general impact... (GDPR Art. 35(10))
  • Art. 35(5): a supervisory authority may publish a list of the kinds of processing for which NO data protection impact assessment is required. Where the processing appears on the competent authority's Art. 35(5) list, no DPIA is required. (GDPR Art. 35(5))

Scope in the source's own terms

  • Art. 3(1)/(2): the processing is carried out in the context of the activities of an establishment in the Union, or relates to offering goods or services to, or monitoring the behaviour of, data subjects in the Union
  • Art. 2(1) read with Art. 4(1): the activity is the processing of personal data — any information relating to an identified or identifiable natural person
  • Art. 4(7): the duty binds the 'controller' — the person which, alone or jointly with others, determines the purposes and means of the processing (a processor's parallel duties sit in Art. 28/30(2))
  • Art. 35(1): the processing is 'likely to result in a high risk to the rights and freedoms of natural persons', in particular where it uses new technologies. Art.

What engineering work it implies

  • FRIA / DPIA Assessment ScaffoldCovers it fully

    An assessment record carrying the Article 27(1)(a)-(f) headings and the WP248 DPIA sections in one artefact, stored with the project and linked to the evidence that...

Sample acceptance criteria Landfall generates for this obligation:

  • (a) A systematic description of the processing operations and their purposes is recorded, including the legitimate interest where relied on
  • (b) Necessity and proportionality are assessed against the purposes, with the rejected alternative named
  • (c) The risks to the rights and freedoms of data subjects are assessed, with likelihood and severity stated
  • (d) The measures envisaged to address the risks are recorded, each with an owner and a date
  • The DPIA is completed before the processing starts, and the launch is blocked until it is (Art. 35(1))

Evidence an auditor expects

  • Assessment documentDocument reviewReviewed Art. 35(11): review where necessary, and at least when there is a change of the risk represented by the processing operations

    Data protection impact assessment report containing the Art. 35(7) minimum content

    A DPIA carried out PRIOR to the processing containing at least: (a) a systematic description of the envisaged processing operations and the purposes, including where applicable the legitimate interest pursued; (b) an assessment of the necessity and proportionality of the processing in relation to the purposes; (c) an assessment of the risks to the rights and freedoms of data subjects; and (d) the measures envisaged to address the risks, including safeguards, security measures and mechanisms to ensure the protection of personal data and to demonstrate compliance. Art. 35(9): where appropriate, the views of data subjects or their representatives must be sought

  • Process recordDocument review

    DPO advice record (Art. 35(2)) and the screening decision for processing where no DPIA was carried out

    Evidence that the controller sought the advice of the data protection officer where one is designated, together with the advice given; and, for processing screened and found not to require a DPIA, a dated record of the screening and its reasons — the accountability artefact under Art. 5(2) is the screening decision, not only the DPIA

  • Process recordDocument reviewRecommended

    Processor assistance evidence (Art. 28(3)(f))

    Where processors are engaged, evidence of the assistance they provided to the DPIA under Art. 28(3)(f), and the contractual term requiring it

Questions people ask

Does EU GDPR Article 35(1), (3) and (7) — Data protection impact assessment apply to my service?
It applies when Service processes personal data; and at least one of: DPIA screening criteria includes Evaluation or scoring, including profiling and predicting; DPIA screening criteria includes Automated decision-making with legal or similarly significant effect; DPIA screening criteria includes Systematic monitoring of people, including in publicly accessible areas; DPIA screening criteria includes Sensitive data, or data of a highly personal nature; DPIA screening criteria includes Processing on a large scale; DPIA screening criteria includes Matching or combining datasets from different processing operations; DPIA screening criteria includes Data about vulnerable people, such as children, employees or patients; DPIA screening criteria includes Innovative use of new technological or organisational solutions; DPIA screening criteria includes Processing that stops people exercising a right, or using a service or contract; Service makes solely automated decisions with legal or similarly significant effects; Service deploys AI systems in a professional capacity. It does not apply where Art. 2(2)(c): the Regulation does not apply to processing of personal data 'by a natural person in the course of a purely personal or household activity'. Recital 18 keeps controllers or processors providing the means for such processing in scope. (GDPR Art. 2(2)(c)).
When does this become enforceable?
EU GDPR Article 35(1), (3) and (7) — Data protection impact assessment is enforceable from 25 May 2018. Its current status is: in force.
What evidence does an auditor expect?
Data protection impact assessment report containing the Art. 35(7) minimum content; DPO advice record (Art. 35(2)) and the screening decision for processing where no DPIA was carried out; Processor assistance evidence (Art. 28(3)(f)).

Find out whether this one lands on you

Landfall's pre-scan answers the applicability question above for your product in minutes, then turns every obligation that applies into traceable engineering tickets with a citation chain your auditors can follow.

Not legal advice. Landfall maps regulatory obligations to engineering work for planning purposes. Its verdicts are not legal advice and create no attorney-client relationship — verify with qualified counsel before relying on them.

What Landfall Is NOT

Critical Boundaries

Understanding these boundaries is essential before using this product. Misuse of this tool for purposes outside its scope may create legal, regulatory, or commercial risk for your organization.

NOT Legal Advice

This product does not provide legal advice and does not create an attorney-client relationship.

Interpretations are informational analysis, not legal counsel. Always consult qualified legal professionals for compliance decisions.

NOT a Risk Score

We do not quantify, calculate, or certify your compliance risk level.

No numerical risk rating, compliance percentage, or safety score. Risk assessment requires human judgment about your specific context.

NOT Runtime Enforcement

This is a planning and mapping tool, not a runtime enforcement system.

Does not integrate with your production systems. Does not block, filter, or enforce compliance in real-time. Implementation is your responsibility.

NOT Regulatory Approval

Using this tool does not mean you are compliant with any regulation.

No certification, seal of approval, or compliance guarantee. Regulators will evaluate your actual implementation, not your use of this tool.

NOT Authoritative Interpretation

Our interpretations are not binding and may differ from regulatory guidance.

Only regulators and courts provide authoritative interpretation. Our analysis reflects our reading of requirements, which may be incomplete or incorrect.

NOT a Safe Harbor

This tool does not shield you from enforcement actions or liability.

Documentation of your process is valuable, but does not constitute a legal defense. Compliance is ultimately your organization's responsibility.

NOT an AI Compliance Agent

AI features assist analysis but do not make compliance decisions for you.

AI-generated interpretations require human review and approval. Automated suggestions are starting points, not final answers.

NOT Complete Coverage

We do not cover all regulations, all obligations, or all jurisdictions.

Regulatory landscape is vast and evolving. Gaps in our coverage do not mean those requirements don't apply to you.

What This Tool IS:

  • A structured workflow for mapping regulatory requirements to implementation tasks
  • A documentation system for compliance decisions (audit trail)
  • A collaboration platform for compliance, legal, and engineering teams
  • An informational resource for understanding regulatory obligations