Skip to content
GDPR-K · EU-GDPR-K-NO-CHILD-PROFILING

GDPR-K Articles 6(1)(f), 21(2)-(3) and 22 read with Recital 38 - Lawful basis and objection handling for profiling and marke…

Identify and record the lawful basis for any profiling or marketing use of a child's data, apply the child-weighted Article 6(1)(f) balancing test, and honour the Article 21(2) right to object; the GDPR prohibits neither, the DSA does for platforms

CRITICALAssessment dutyProfilingBinding regulationIn forceApplies from 25 May 2018

Where this comes from

Provision: Articles 6(1)(f), 21(2)-(3) and 22 read with Recital 38 - Lawful basis and objection handling for profiling and marketing that reaches children

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

Citation: Regulation (EU) 2016/679, OJ L 119, 4.5.2016, Articles 6(1)(f), 21(2)-(3), 22 and 8; read with Recital 38, Recital 47 and Recital 71; Article 29 Working Party WP251 rev.01 (endorsed by the EDPB 25 May 2018) section V

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
  • Service uses content personalization
  • Service serves targeted advertising

What engineering work it implies

  • Profiling Opt-Out MechanismCovers it fully

    Allow users to disable behavioral profiling with immediate effect on recommendations.

Sample acceptance criteria Landfall generates for this obligation:

  • User model has `profilingEnabled` boolean field (default: false)
  • Recommendation engine checks profilingEnabled before processing user
  • Behavioral tracking skips users with profilingEnabled=false
  • Ad targeting excludes users with profilingEnabled=false
  • Admin dashboard shows count of users with profiling disabled

Questions people ask

Does GDPR-K Articles 6(1)(f), 21(2)-(3) and 22 read with Recital 38 - Lawful basis… apply to my service?
It applies when Service is likely to be accessed by children under 18; Service uses content personalization; Service serves targeted advertising.
From when does this apply?
GDPR-K Articles 6(1)(f), 21(2)-(3) and 22 read with Recital 38 - Lawful basis… applies from 25 May 2018. Its current status is: in force.
What engineering work does this imply?
Typically: Profiling Opt-Out Mechanism.

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