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

GDPR-K Article 35 / Recital 75 - Data protection impact assessment for children's data

Conduct a Data Protection Impact Assessment before processing children's data, as processing data of vulnerable persons (including children) is considered likely to result in high risk

CRITICALAssessment dutyRisk assessmentBinding regulationIn forceApplies from 25 May 2018

Where this comes from

Provision: Article 35 / Recital 75 - Data protection impact assessment for children's data

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

Citation: Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016, Article 35 and Recital 75

Text version: Regulation (EU) 2016/679 (GDPR), OJ L 119, 4.5.2016, consolidated

Read the official text ↗

Who it applies to

It applies when all of these are true:

  • Service is likely to be accessed by children under 18
  • Data categories collected — any answer

…unless:

  • DPIA not required where processing is not likely to result in high risk to individuals. (UK GDPR Article 35(1))
  • DPIA not required where processing has a legal basis in law and DPIA was already carried out as part of establishing that legal basis. (UK GDPR Article 35(10))

Scope in the source's own terms

  • Processing involves children's data (high risk)
  • Processing subject to GDPR (EU scope; block moved from UK-GDPR authorship)

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • Assessment covers data flows, the risks to the affected group, and likelihood/severity
  • Each identified risk has a mitigation mapped to a concrete control or backlog item
  • The assessment is dated, has named sign-off, and is scheduled for review
  • The assessment is retrievable for regulators on request
  • Signed assessment document is stored and version-controlled

Evidence an auditor expects

  • Assessment documentDocument reviewRetain 6 years from completion

    Data Protection Impact Assessment (DPIA)

    Full DPIA covering: systematic description, necessity/proportionality, risks to children, and mitigation measures

  • Process recordDocument review

    DPIA review schedule and updates

    Record of when DPIAs are reviewed and updated, triggered by changes to processing

  • Audit reportDocument reviewRecommended

    DPO consultation record

    Evidence of DPO involvement in DPIA where applicable

Questions people ask

Does GDPR-K Article 35 / Recital 75 - Data protection impact assessment for childr… apply to my service?
It applies when Service is likely to be accessed by children under 18; Data categories collected — any answer. It does not apply where DPIA not required where processing is not likely to result in high risk to individuals. (UK GDPR Article 35(1)).
From when does this apply?
GDPR-K Article 35 / Recital 75 - Data protection impact assessment for childr… applies from 25 May 2018. Its current status is: in force.
What evidence does an auditor expect?
Data Protection Impact Assessment (DPIA); DPIA review schedule and updates; DPO consultation record.

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