Skip to content
GDPR-K · EU-GDPR-K-ART17-ERASURE

GDPR-K Article 17 - Right to erasure ('right to be forgotten') (Article 17(1)(f): data collected in relation to the offer of…

Facilitate the right to erasure of childhood data, especially when consent was given as a child and the data subject later wishes to remove it upon reaching adulthood

CRITICALRequirementUser rightsBinding regulationIn forceApplies from 25 May 2018

Where this comes from

Provision: Article 17 - Right to erasure ('right to be forgotten') (Article 17(1)(f): data collected in relation to the offer of information society services referred to in Article 8(1))

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

Citation: Regulation (EU) 2016/679, OJ L 119, 4.5.2016, Article 17(1)(f), 17(2) and 17(3); Article 12(3) (one-month response); read with Recital 65

Text version: Regulation (EU) 2016/679 (GDPR), OJ L 119, 4.5.2016, as adopted (CELEX 32016R0679), read from the Publications Office Cellar manifestation on 2026-09-21 because EUR-Lex served an empty body to non-browser clients; the 2018 corrigendum (OJ L 127, 23.5.2018) was not retrievable, so any correction it made is unverified.

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 retention period — any answer

…unless:

  • Paragraphs 1 and 2 do not apply to the extent processing is necessary (a) for exercising the right of freedom of expression and information; (b) for compliance with a legal obligation under Union or Member State law or for a public-interest or... (Regulation (EU) 2016/679, Article 17(3)(a)-(e))

What engineering work it implies

Sample acceptance criteria Landfall generates for this obligation:

  • A user/guardian can request access, deletion, and export from the account UI
  • Deletion removes or irreversibly anonymizes the data across primary stores and backups within the required window
  • Export is provided in a structured, machine-readable format
  • Requests, identity checks, and fulfillment are logged with timestamps
  • A request that fails identity verification is refused safely (no data disclosed) and the user can retry

Questions people ask

Does GDPR-K Article 17 - Right to erasure ('right to be forgotten') (Article 17(1)… apply to my service?
It applies when Service is likely to be accessed by children under 18; Data retention period — any answer. It does not apply where Paragraphs 1 and 2 do not apply to the extent processing is necessary (a) for exercising the right of freedom of expression and information; (b) for compliance with a legal obligation under Union or Member State law or for a public-interest or... (Regulation (EU) 2016/679, Article 17(3)(a)-(e)).
From when does this apply?
GDPR-K Article 17 - Right to erasure ('right to be forgotten') (Article 17(1)… applies from 25 May 2018. Its current status is: in force.

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