Policies · eGov

The European Commission's EU KIDS Act proposal, published on 17 September 2026, introduces safety-by-design requirements and age-rating obligations for online games and software application stores.
✦ AI SUMMARY 30-second read

- Online games must apply safety-by-design measures by default; age assurance is required only when a player seeks to disable those safeguards.
- App stores — including mobile, PC and console platforms — must rate every app for age-appropriateness and block access to age-inappropriate titles.
- Age-rating criteria are left to voluntary codes of conduct developed through a Commission-facilitated multi-stakeholder process, leaving room for inconsistency across stores.
Why it matters: How the under-13 rule is interpreted will determine whether age checks become universal across all video games, regardless of their risk profile.

This summary was generated by AI. Editors may review and update it.
Document details
| Document type | Rules & Regulation |
|---|---|
| Issued by | European Union |
| Region | Global |
| Published | 17 November 2026 |
The European Commission published its proposal for the EU KIDS Act on 17 September 2026. While much attention fell on its minimum-age provisions for social networks and video-sharing platforms, the proposal also contains requirements that apply directly to providers of online games and software application stores.

Online games are not subject to a minimum age under Articles 6 or 7 of the proposal. However, separate provisions in Articles 8, 15 and 16 introduce safety-by-design obligations and age-rating requirements that could affect how games are accessed across all major distribution platforms.
What the document says
Under Article 15(1), providers of online games must implement safety designs by default. These include measures against compulsive use, high privacy settings, safeguards on player-to-player contact, and tools for guardians. Article 8(1) specifies that providers may allow users to deactivate these defaults only after establishing through age assurance that the user is an adult.
Article 15(1)(d) adds that players below 13 may only access a game through guardian-controlled tools referred to in Article 20. Unlike comparable provisions for video-sharing platforms, the proposal does not specify whether age assurance or self-declaration is required to identify which players fall below that threshold.
Article 16 requires software application store providers to assign an age-appropriateness rating to every app and to prevent minors from accessing or purchasing titles rated as inappropriate for their age group. Stores must also assess users' ages and ensure that children below 13 access the store only under parental supervision.
Who is affected
The definition of online games in Article 3(5)(e)-(g) covers both video games in general and video gaming platforms. The definition of software application stores is drawn from Article 2(14) of the Digital Markets Act and is considered broad enough to cover not only mobile stores but also PC and console game stores.
Game providers, app store operators and, indirectly, players and their parents are all affected. Parents currently have no mechanism under Article 16(2) to override an age-rating restriction for their own child, and no equivalent of the developer appeal process in Article 17(2)(c) is set out for players or parents.
Key ambiguities
The proposal does not state explicitly whether the under-13 rule in Article 15(1)(d) requires full age assurance or whether self-declaration would suffice. If age assurance is required, every online game would need to verify every player's age before granting access, irrespective of its risk profile. If self-declaration is accepted, the obligation remains lighter.
At the store level, Article 16(4) refers both to Chapter V, which points toward age-assurance measures, and to Article 20, which some read as permitting a guardian's declaration. The proposal does not resolve this tension expressly.
Age-rating criteria are not defined in the legislation itself. They are to be developed through codes of conduct facilitated by the Commission. Until such codes are in place and widely adopted, the same game could receive different ratings and face different access restrictions depending on the store. The Commission is to assess code effectiveness 42 months after the Regulation enters into force.
What happens next
The proposal is at the stage described in the published document. Code-of-conduct development will follow a multi-stakeholder process facilitated by the Commission. Adherence to a code assessed as adequate by the Commission assists game providers in demonstrating compliance with Article 15, and declining to participate without explanation may count against a provider under Article 15(4) and recital 39.
Participation in a code does not, however, presume compliance. A store that does not adhere remains bound only by the obligation under Article 16(5) to publish the methodology, criteria and sources used for its rating system.