An age-appropriate design code is a set of legally backed design standards that requires online services likely to be accessed by children to put the best interests of the child first when they collect and use personal data. In tech regulation and online safety, the best-known example is the UK Age Appropriate Design Code, often called the Children’s code, which the Information Commissioner’s Office issued under the Data Protection Act 2018.
Unlike rules that only restrict harmful content, a design code targets the architecture of the service itself: default settings, data flows, recommendation features and interface patterns. It turns abstract data protection principles into concrete product requirements for apps, games, social platforms, streaming services and connected toys.
How an age-appropriate design code works
A design code works by translating general data protection law into specific expectations for services used by minors. The UK code is a statutory code of practice: it does not create new offenses, but regulators and courts must take it into account when they decide whether a service has complied with the UK GDPR and related law.
The code applies a risk-based, proportionate approach. A service must first decide whether children are likely to use it, then assess the specific risks its features create, and finally adjust its design to the age and developmental stage of its actual users. A child is anyone under 18, not only the under-13 group covered by many consent rules.
The scope test is deliberately broad. It covers information society services, meaning most commercial apps, websites, online games and connected devices, even when they are not aimed at children, provided that a significant number of children in practice use them.
The core standards of the UK code
The UK code contains 15 interlinked standards that a service must meet together. The table below groups the most influential ones by what they require in practice.
| Standard | Core requirement | Typical design change |
|---|---|---|
| Best interests of the child | Child welfare outweighs commercial interest | Reassess engagement-driven features |
| Data protection impact assessment | Assess risks to children before launch | Documented risk review per feature |
| Default settings | High privacy by default | Private profiles for young users |
| Geolocation | Location tracking off by default | Visible indicator when location is shared |
| Profiling | Profiling off by default unless justified | Opt-in personalized recommendations |
| Nudge techniques | No designs that push weaker privacy | Neutral choice buttons |
| Data minimization | Collect only what each feature needs | Separate opt-ins per feature |
| Parental controls | Tell the child when monitoring is active | On-screen monitoring notice |
The remaining standards cover age-appropriate application, transparency, detrimental use of data, published policies, data sharing, connected toys and devices, and accessible online tools that let children exercise their data rights.
Designing for different age ranges
An age-appropriate design code expects services to tailor protections to developmental stages rather than treat all minors alike. The UK guidance uses five age bands, and services may either establish a user’s age with appropriate certainty or apply the protections to all users.
| Age band | Developmental context | Design emphasis |
|---|---|---|
| 0 to 5 | Pre-literate, relies on parents | Audio or visual cues, parental involvement |
| 6 to 9 | Core primary school years | Simple explanations, strong defaults |
| 10 to 12 | Growing independence online | Clear prompts before risky choices |
| 13 to 15 | Early adolescence, peer pressure | Explain risks, limit public exposure |
| 16 to 17 | Approaching adulthood | More autonomy with clear information |
This link to age is why the code interacts closely with age verification and age estimation. The code does not mandate one method; it requires that the level of certainty match the risk created by the data processing.
Comparison with other child safety laws
Age-appropriate design codes differ from other child safety measures mainly in their legal basis and target. Several jurisdictions have copied or adapted the UK model, with varying legal success.
| Instrument | Jurisdiction | Main focus | Status |
|---|---|---|---|
| UK Age Appropriate Design Code | United Kingdom | Data protection by design | In force since September 2021 |
| California Age-Appropriate Design Code Act | California | Impact assessments and defaults | Largely blocked by litigation |
| Maryland Kids Code | Maryland | Best interests and defaults | Enacted 2024, challenged in court |
| Online Safety Act | United Kingdom | Illegal and harmful content duties | Phased implementation by Ofcom |
| Kids Online Safety Act | United States (federal) | Duty of care for platforms | Proposed, not enacted |
The UK code governs how data is processed, while the Online Safety Act governs what content users encounter. In the United States, design codes face First Amendment challenges because courts may treat mandated assessments of content risk as compelled speech, which is the main reason the California law has been enjoined.
Compliance in practice
Compliance starts with a documented data protection impact assessment that maps each feature, the data it uses and its potential harm to children. Product teams then change defaults, interfaces and data flows, and they record why each choice serves the child.
| Situation | Recommended action | Reason |
|---|---|---|
| General audience app with many teen users | Apply code protections to all users or verify age | Avoids guessing who is a child |
| Feed ranked by engagement | Offer a non-profiled feed by default | Profiling off by default |
| Feature shares precise location | Switch off and show an indicator | Reduces stalking and contact risk |
| Streak or reward mechanics | Assess for compulsive use | Detrimental use of data standard |
| Third-party advertising SDKs | Disable or restrict for child users | Limits data sharing |
Enforcement under the UK regime runs through the UK GDPR penalty framework, with fines of up to 17.5 million pounds or 4% of global annual turnover, whichever is higher. In practice, regulators have relied heavily on audits, engagement and compliance commitments rather than headline fines.
Limitations and common misunderstandings
A design code is often described as a ban or a content filter, but it is neither. It sets outcome-oriented standards, which leaves room for interpretation and makes enforcement depend heavily on regulator guidance.
- Not limited to children’s services: general platforms with significant child audiences are in scope.
- Not a parental consent rule: consent thresholds are a separate legal question.
- Not a mandate for identity checks: age assurance must be proportionate, and intrusive checks create their own privacy risk.
- Not a content moderation regime: harmful content duties sit in separate online safety laws.
- Vague terms invite dispute: phrases such as best interests require judgment and documentation.
Critics also note a tension between privacy and safety: stronger age assurance can mean collecting more data about everyone, which is exactly what the code otherwise discourages.
Stripped to the essentials
An age-appropriate design code tells apps and websites that children use to be safe by default. Instead of expecting a young user to find hidden privacy settings, the service must start with the protective choice already switched on.
Think of it as a building code for online spaces. A playground must have soft ground and safe railings before children arrive. In the same way, an app must keep a child’s profile private, turn off location sharing and avoid tricks that push the child to give away more information. The key idea is simple: the child’s well-being comes before the company’s profit.
Where it is applied
A mid-sized video-sharing app based in Europe discovers that roughly a third of its UK users are between 13 and 17. Its compliance team runs a data protection impact assessment and finds three high-risk features: public profiles by default, precise location tags on posts and an autoplay feed ranked by engagement signals.
The team makes accounts of users estimated to be under 18 private by default, removes precise location tagging for those users and adds a chronological feed as the default option. Direct messages from unknown adults are blocked, and push notifications stop overnight.
Within one release cycle, the app can show the regulator a documented rationale for every change. Engagement among teen users dips slightly, but the company reduces its regulatory exposure and gains a defensible position if a parent or the regulator raises a complaint.