Every app asks how old you are. Answer once.
A fourteen-year-old with two games and one chat app has typed her birthday in three times this year. One of them keeps a photo of her ID. Brussels has noticed: every member state is asked to offer a privacy-preserving age check by the end of 2026.3
With game3 she confirms her age once, and the answer travels into every game and app that asks. The app learns she's over 13. The ID stays with the verifier. The same identity can stand behind an agent she puts to work, within limits she sets.
Why it matters
Regulators have stopped taking a typed-in birthday at face value. Four facts, each with its source.
Preliminary finding
In April 2026 the Commission preliminarily found Meta in breach of the DSA because self-declared birth dates, with no checks, let under-13s onto Instagram and Facebook.2
In force
Under the EU Digital Services Act, every online platform accessible to minors must take appropriate and proportionate measures for a high level of privacy, safety and security of minors (Art. 28(1)).1
Commission recommendation
The Commission has asked every EU member state to make at least one privacy-preserving age-verification solution available to citizens by 31 December 2026.3
Proposal
The proposed EU KIDS Act would oblige online games to keep minors' settings private by default, restrict contact from strangers, and allow under-13 access only through guardian tools.4
For studios and platforms
Every title you ship rebuilds the same gate: a verifier contract, a consent screen, a table of birthdays nobody wanted. Integrate game3 once, and players who confirmed their age elsewhere arrive with the answer in hand.
- What you receive
- Over 13, 16 or 18, whichever you set. One real person behind the account. An account in good order.
- What stays with the verifier
- Documents, dates of birth, names, addresses. A breach on your side has nothing to find.
- Where it runs
- Web and Unity, through the early SDK. Other engines and platforms on request.
Give an agent a job. Set the limits yourself.
Software is starting to play and shop alongside people. With game3 you name an agent under your own identity, give it a scope and an expiry, and withdraw it when you're done. Whoever it deals with sees an accountable person, and nothing about who you are.
Three jobs a mandate can cover
- The queue sitter
- The raid queue opens at three in the morning. An agent holds your place and wakes you when the group fills. Nothing more.
- The auction watcher
- A bot waits for the one sword you want and bids up to the cap on its mandate. Nothing else is within its reach.
- The stand-in for the guild run
- A co-player fills Thursday's empty slot in your guild run, under your name and for one evening. The guild can see you sent them.
- Naming an agent under the identity of a player, with a scope and an expiry, runs on a public test network.
- Agents acting inside a game under a sub-identity are planned.
- Agents spending on behalf of a player within set limits are planned.
Built with game3
RIZZ
A chat app for teenagers in the EU, by LAB75. Its own page says you show your age with a government wallet and the passport stays in the drawer.
RIZZ runs its own SDK programme.
- In development with game3
spray.cash
Person-to-person payments from ZERO.IO. Sending money has the same chore as playing: every service wants to know who you are, from scratch.
- In development with game3
For players and parents
You've typed your birthday into more apps than you can name, and at least one has a photo of your ID. With game3 you confirm your age once. Every app that asks gets its yes; your ID stays where it is.
As guardian approval arrives, parents get a say: a request to join voice chat lands on your phone with an age band and two buttons.
Who allowed this, and what did they allow?
A payment carries an amount and a destination. A chat message carries text. Neither says who sent the agent behind it, or how far it may go. game3 keeps that record under the player's identity, where the other side can read it.
ERC-8004 lets agents be found, x402 lets them pay. game3 works alongside both and answers the question they leave open: who allowed this agent, and for what. The agents and the money stay with the platforms that run them.
Where things stand
On a public test network
- Age proofs run on a public test network.
- Identity checks through Sumsub are anchored as attestations on a public test network.
- Proofs that a player is a unique person run on a public test network.
- Account standing checks run on a public test network.
- Naming an agent under the identity of a player, with a scope and an expiry, runs on a public test network.
Early access
- Sign in with game3 is in early access.
- The web SDK is in early access.
- The Unity SDK is in early access.
Planned
- Support for the EU Digital Identity Wallet is planned.
- Support for the EU age-verification app is planned.
- Participation in the EUDI sandbox and an independent certification are planned.
- Guardian approval is planned.
- Agents acting inside a game under a sub-identity are planned.
- Agents spending on behalf of a player within set limits are planned.
Governed by the Game3 Association and operated by ZERO.IO, from Switzerland. Home market: the EU. The aim is one check that counts wherever people play.
Apply for the early SDK
We read every application ourselves. Tell us what you're building, who plays it, and where an age check gets in the way. If it fits the early SDK, you'll hear from us by email.
Start your application