EU KIDS Act for esports tournaments

What the draft actually covers

On 17 September, the European Commission published a draft EU KIDS Act, short for Keeping Internet Digital Spaces Accountable and Trustworthy. In 2026 that draft remains the clearest public statement of where youth-online rules are heading. The sharpest proposals, including a ban on social media for under-13s and tighter limits for under-15s, apply to social networks and video-sharing services. Games are not given a blanket exemption.

Online games, AI companions, chatbots, app stores, and operating systems sit inside the wider text. A title used for esports tournaments can therefore pick up duties when it adds profiles, public clips, open lobbies, or persistent messaging. Tournament Click reads the draft as a planning baseline: it is not adopted law, and wording can still move, but waiting for a final text leaves product and event teams exposed.

Where games differ from social networks

The controversial age bans are aimed at services whose main job is open social distribution. A competitive game is judged by what it actually offers, not by its marketing label. Friend graphs, clubs, user-generated video, and always-on chat can make a game look like the services the draft restricts. A closed match with a fixed roster looks different from a public square.

Developers should write down each social surface and the age it is meant to serve. School and junior esports tournaments need that map before registration opens. Age bands, guardian consent, and off-by-default discovery are easier to defend than a single toggle buried in settings. If a feature is not required to play the match, treat it as optional for minors.

Running youth events on a tournament platform

A tournament platform should collect only what seeding and safety require: an alias or name, an age band, a team, and a reachable adult. Location trails, open direct messages, and broad behavioural ads do not improve a bracket. In 2026, regulators and parents will look for purpose limitation, not for slogans about safety.

Tournament Click advises a data map before the first invite. Keep public results, such as placements and scores, apart from private contact details. Set a deletion date for guardian emails once the season ends, unless a legal claim or accounting rule still applies. Staff should be able to explain every field on the signup form in one sentence.

Why a bracket maker is a safety control

A bracket maker structures competition without forcing players into a permanent social graph. Publish the draw, the schedule, and the result. For junior divisions, leave spectator chat off, or staff it with named moderators and a response time written into the event rules. Structure reduces the chance that a youth event drifts into an unmoderated hangout.

Match voice is not the same as a lobby that never closes. Limit talk to checked-in teams, say so before players join, and keep recordings only when the rules allow it. Match-scoped chat, human moderation, and a short retention window are the controls that matter. Automated filters help, but they do not replace a person who can remove a user during a live final.

AI companions and in-game chatbots

The draft also reaches AI companions and chatbots attached to games. A tips bot at a youth final is not minor-risk if it profiles a child, stores personal questions, or nudges spending. Treat the assistant as a product feature with an age policy. Log what it can see, what it stores, and who can switch it off during an event.

Disable companion features for junior brackets unless they are optional, non-profiling, and easy to refuse. Do not let a bot message a minor outside the match window. Keep a human owner for the feature and a written shutdown path. No profiling of minors should be the default, including inferred mood, spend likelihood, or social rank beyond the published result.

Practical duties for developers in 2026

Inventory friends, clips, clubs, direct messages, and any bot. For each one, record the minimum age, the default setting, and the guardian path. Mirror that inventory in the event rulebook so parents, referees, and engineers see the same promise. A feature that ships without an owner will fail the first serious complaint.

Choosing tournament software does not move legal responsibility off the developer or the organizer. It can enforce age bands, check-in gates, and closed junior draws if those rules are configured on purpose. Pair the tool with staff training and a complaint route a parent can use the same day. Review the setup every season against the latest Commission text and any national guidance that follows.

Conclusion

The EU KIDS Act draft, as published and still the working reference in 2026, hits games through social features, chat, app distribution, and AI companions rather than through competition itself. Teams that run esports tournaments should separate match structure from open social tools, minimise data, and document age rules before a youth event goes live. Tournament Click will keep tracking the text so organizers can adjust a tournament platform, a bracket maker, and their rulebooks as the law settles.

Frequently Asked Questions

What is the EU KIDS Act?

It is a European Commission draft, titled Keeping Internet Digital Spaces Accountable and Trustworthy, aimed at making digital services safer for children. It is a proposal, not finished law.

Does the under-13 ban apply to every game?

No. The strictest age bans in the draft target social networks and video-sharing platforms. Games can still be covered when they offer similar social or sharing functions.

Do esports tournaments need guardian consent?

Youth events should plan for guardian involvement wherever the draft or national age rules require it. A written consent path is safer than assuming a player’s click is enough.

What data should a youth signup collect?

Collect the age band, team, alias, and an adult contact needed to run the event. Avoid extra tracking that does not serve seeding, safety, or a legal duty.

Should junior events have public chat?

Public spectator chat should be off by default for junior divisions. If chat is on, it needs named moderators and a clear response time.

Is match voice chat allowed?

Match-limited voice can be justified when only checked-in teams can join and players are told about any recording. Always-on lobbies are a higher risk.

Are AI companions covered?

Yes. The draft discusses AI companions and chatbots alongside games. Youth events should disable profiling bots unless they are optional and tightly limited.

Does event software remove the organizer’s duty?

No. Tools can enforce gates and brackets, but the developer and organizer remain responsible for settings, notices, and moderation.

What should developers inventory first?

Start with friends, clubs, clips, direct messages, and bots. Note the age limit, default state, and guardian path for each.

When should teams revisit their setup?

Review at least once a season in 2026, and again when the Commission or a member state publishes changes. Keep a short change log so staff can see what moved.

Are app stores and operating systems relevant to games?

Yes. The draft also addresses app stores and operating systems, which can affect how age signals and installs reach a game. Developers should not assume store rules replace their own design duties.