Separate general duties from the Code’s scope

UK data protection requirements can apply whenever a business processes children’s personal information. The Children’s Code has a more specific scope: relevant information society services likely to be accessed by children in the UK. It can cover many commercial websites, apps, games and connected services, including services not specifically aimed at under-18s.

Do not decide scope solely from the marketing department’s intended audience. Examine who is likely to use the actual service. Conversely, a company’s employee records involving a young worker are not automatically within the Code merely because the person is under eighteen. They still require appropriate protection. Record the distinction and obtain specialist advice if the service definition or territorial position is uncertain.

Use evidence about likely access

The ICO expects a supported assessment, not a sentence in the terms declaring that users must be adults. Consider the content, presentation, audience research, experience of similar services and evidence of actual use. The relevant question is not whether a child could theoretically reach a web address, but whether the service is likely to be accessed by children.

Our practical recommendation is a short scope file owned by the product lead. Include the evidence considered, assumptions, decision and triggers for review. A new game feature, school promotion or social campaign may change the audience. If evidence contradicts the original assumption, revisit the design or access controls. Do not continue relying on an old assessment simply because changing the product would be inconvenient.

Make children’s interests a design input

For in-scope services, the best interests of children must be a primary consideration. The ICO’s guidance links that assessment to the DPIA process. Consider not only immediate disclosure risks but how data use may affect children’s autonomy, wellbeing and understanding of the service.

A useful workshop starts with a real journey: registration, choosing settings, receiving recommendations and leaving the service. At each point, ask what the child understands, what information is needed and what could go wrong. Include different ages and abilities rather than designing around a single imagined teenager. Document where a commercial objective conflicts with a protective design choice and how the decision was resolved.

Build high privacy into the default experience

The Code expects high-privacy settings by default unless there is a compelling reason for a different setting, taking account of children’s best interests. Merely allowing a child to discover and activate protective settings later is not the same approach. Data minimisation and avoiding manipulative nudges are also important design considerations.

In practice, test the first-use experience before any settings are changed. Which information becomes visible? Which features start automatically? Does declining an optional use leave a usable service? Avoid rewarding children for disclosing unnecessary information or presenting privacy choices in confusing language. Keep a record of the default configuration so that later product experiments do not quietly weaken it.

Age assurance creates its own privacy questions

Understanding age can help provide appropriate protections, but collecting more identity information is not automatically the right answer. The method should reflect the risks and the purpose. Some services may choose protections suitable for children across their user base; others may need a proportionate way of establishing age or restricting access.

Our suggested assessment asks what the method collects, who receives it, how long it is retained and whether it can be used for another purpose. Do not ask every visitor to upload a document simply because it feels thorough. Review the provider, accuracy, accessibility and consequences of mistakes. Age assurance should reduce the relevant risk, not introduce a larger identity-data exposure without justification.

Do not confuse the Code’s under-eighteen scope with the UK digital-consent threshold. Where the Article 8 rules apply and an online service offered directly to a child relies on consent, under-thirteens require consent given or authorised by someone with parental responsibility, with reasonable verification efforts. That does not mean a thirteen-year-old loses the Code’s protections or that parental consent is the appropriate basis for every processing activity.

Explain the service so children can understand it

Privacy information must be clear and appropriate to the audience. A lengthy adult legal notice is unlikely to answer a child’s question at the moment a feature asks for location or a photograph. Consider concise explanations at meaningful points, backed by fuller information where needed.

Test understanding rather than reading age alone. Can a young user explain who will see something, whether a choice is optional and how to change it? Parents and carers may also need useful information, but that does not erase the child’s own privacy interests. Build a workable route for questions and rights requests, including situations where the child and an adult disagree.

Do not confuse privacy obligations with online-safety duties

The Children’s Code concerns personal-data use. Depending on the service, separate online-safety, consumer, safeguarding or sector obligations may also apply. Meeting one framework does not establish compliance with the others, and the relevant age thresholds and scope tests may differ.

For a business team, the practical answer is one coordinated product review with distinct legal questions and owners. Map each feature to the obligations it triggers, rather than creating unrelated checklists that make contradictory assumptions. Escalate sensitive design choices, especially profiling, location, contact between users or high-impact recommendations, to suitably experienced advisers.

Keep the assessment alive after launch

A service changes through suppliers, integrations, experiments and user behaviour. Set review triggers for material changes and monitor whether the intended protections operate in practice. Make it possible to pause a problematic feature without dismantling the entire product.

Useful evidence includes configuration records, risk decisions, test results and the resolution of complaints. Avoid describing the service as “Children’s Code certified” merely because an internal checklist has been completed. The stronger position is to show why the design is appropriate, where uncertainties remain and how those uncertainties are being addressed.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.