Artifact GuideUKChildren's Code

UK GDPR Children's Code

Children's Code decisions under the UK GDPR should be written in operational language: who is in scope, what must happen, what evidence proves it, and when escalation is needed.

This guide converts requirements into implementation-ready ownership, evidence, and review decisions. It is practical guidance, supporting implementation planning and should be validated against jurisdiction-specific legal, contractual, and policy requirements before implementation.

Back to main artifact Review sources

Author

Sorena AI

Published

May 9, 2026

Updated

May 9, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published May 9, 2026

Updated May 9, 2026

Overview

This page maps Children's Code into a trigger, owner, deadline, required evidence, and review path so legal, privacy, security, and compliance teams can execute consistently.

Section 1

What should teams decide about Children's Code under the UK GDPR?

Start by deciding whether the issue affects controller/processor roles, lawful basis, transparency, DPIA, data-subject rights, breach notification, IDTA/Addendum transfers, children data, or ICO enforcement exposure. The useful answer should name the exact trigger, affected product or process, required action, owner, evidence, and escalation point.

Keep the UK GDPR source, DPA 2018 context, role map, lawful-basis analysis, DPIA/rights/breach/transfer evidence, and ICO-facing record together.

Define the exact Children's Code trigger and the business process it affects.
Record which role, product, system, customer group, or data flow is in scope.
Attach the source-linked rule, the owner, and the evidence field before approving the control.
Escalate uncertainty when the facts depend on thresholds, exemptions, cross-border activity, vulnerable users, or enforcement-sensitive wording.

Sources for this answer

UK ICO Age Appropriate Design Code

ICO statutory code source for Children's Code scope, design standards, DPIA, transparency, and child-user protection under UK data protection law.

ICO Introduction to the Children's code

ICO guidance confirming the Children's Code applies to information society services likely to be accessed by children, including UK and non-UK companies processing UK children's data.

Age Appropriate Design Code explanatory memorandum

UK government publication context for the statutory Age Appropriate Design Code laid before Parliament.

Section 2

Who should own Children's Code, and what evidence should prove the decision?

Ownership should sit with the team that controls the processing purpose, system behavior, vendor terms, transfer mechanism, rights channel, breach process, or child-user journey.

Evidence should show role mapping, lawful basis, Article 9/10 basis where needed, transparency wording, DPIA outcome, DSAR response, breach assessment, transfer mechanism, processor terms, and ICO escalation note.

Name one accountable owner and one reviewer for the Children's Code workflow.
Keep source screenshots or source links, decision notes, implementation tickets, and approval records together.
Use dated evidence for deadlines, notices, risk assessments, contracts, user journeys, and regulator-facing records.
Review the evidence after product changes, new markets, new vendors, enforcement updates, or material changes in the source text.

Sources for this answer

ICO Introduction to the Children's code

ICO guidance confirming the Children's Code applies to information society services likely to be accessed by children, including UK and non-UK companies processing UK children's data.

Age Appropriate Design Code explanatory memorandum

UK government publication context for the statutory Age Appropriate Design Code laid before Parliament.

ICO Data sharing: a code of practice

ICO source for data-sharing controls that may be relevant when Children's Code decisions involve partners or onward sharing.

Section 3

Which edge cases should teams check before relying on a Children's Code decision?

Most UK GDPR mistakes happen at the boundary between UK GDPR, DPA 2018, PECR, EU GDPR divergence, IDTA/Addendum transfer rules, children data, and processor/subprocessor duties.

Use this section before approving a new processing purpose, vendor, transfer, profiling flow, DSAR workflow, breach process, or child-facing product change.

Check whether the rule changes for minors, consumers, business users, public-sector bodies, regulated sectors, high-risk services, or cross-border transfers.
Separate binding law, regulator guidance, consultation material, standards, and enforcement commentary in the evidence record.
Do not rely on a previous answer if the data categories, user interface, vendor role, or contractual flow changed.
Track unresolved assumptions in an open-questions section and route legal interpretation points for review.

Sources for this answer

UK ICO Age Appropriate Design Code

ICO statutory code source for Children's Code scope, design standards, DPIA, transparency, and child-user protection under UK data protection law.

ICO Introduction to the Children's code

ICO guidance confirming the Children's Code applies to information society services likely to be accessed by children, including UK and non-UK companies processing UK children's data.

Age Appropriate Design Code explanatory memorandum

UK government publication context for the statutory Age Appropriate Design Code laid before Parliament.

ICO Data sharing: a code of practice

ICO source for data-sharing controls that may be relevant when Children's Code decisions involve partners or onward sharing.

Section 4

How should teams operationalize Children's Code with proportionate controls?

Use a UK GDPR workflow that captures role, purpose, lawful basis, special-category status, DPIA trigger, rights/breach/transfer trigger, evidence, owner, and review date.

The output should be a lawful-basis note, DPIA decision, privacy notice update, DSAR record, breach assessment, transfer pack, processor clause map, or ICO response record.

Create a short intake question that identifies the Children's Code scenario.
Map the answer to a required action, evidence field, owner, reviewer, and review date.
Link related artifact pages with descriptive anchors so users can move from scope to deadlines, controls, penalties, and templates.
Update the workflow when official source material changes or when internal evidence shows recurring exceptions.

Sources for this answer

UK ICO Age Appropriate Design Code

ICO statutory code source for Children's Code scope, design standards, DPIA, transparency, and child-user protection under UK data protection law.

ICO Introduction to the Children's code

ICO guidance confirming the Children's Code applies to information society services likely to be accessed by children, including UK and non-UK companies processing UK children's data.

Age Appropriate Design Code explanatory memorandum

UK government publication context for the statutory Age Appropriate Design Code laid before Parliament.

Recommended next step

Turn UK GDPR Children's Code into assigned work

This UK GDPR guide turns Children's Code into owners, evidence requests, review checkpoints, and reusable operating records for implementation execution.

Assessment workflow

Open Assessment Autopilot for UK GDPR

Turn Children's Code into scoped questions, evidence fields, and review tasks.

Explore next step

Research workflow

Review UK GDPR source evidence

Use Research Copilot to answer follow-up questions with cited source material.

Explore next step

Talk to Sorena

Talk through implementation

Review scope, evidence, owners, and the next compliance actions with Sorena.

Explore next step

Primary sources

References and citations

Age Appropriate Design Code explanatory memorandum

gov.uk

Referenced sections

UK government publication context for the statutory Age Appropriate Design Code laid before Parliament.

"The Age Appropriate Design Code was laid before Parliament"

Article 30 Record of Processing Activities

ico.org.uk

Referenced sections

Supports Children's Code under the UK GDPR.

"Headings highlighted green are required areas of documentation under Article 30 of the GDPR"

ICO Data sharing: a code of practice

ico.org.uk

Referenced sections

ICO source for data-sharing controls that may be relevant when Children's Code decisions involve partners or onward sharing.

"Data sharing must be fair and transparent"

ICO Introduction to the Children's code

ico.org.uk

Referenced sections

ICO guidance confirming the Children's Code applies to information society services likely to be accessed by children, including UK and non-UK companies processing UK children's data.