A proposal, not a law
On 17 September 2026 the European Commission adopted its proposal for an EU KIDS Act ("EU Keeping Internet Digital Spaces Accountable and Trustworthy"), COM(2026) 681. It sets an EU-wide minimum age of 15 for autonomous accounts on risky social networks and video-sharing platforms, adds safety-by-design duties for online games, app stores, operating systems, AI companions and chatbots, and has a full chapter on age assurance.
Everything here is proposed. Parliament and Council still have to agree on a text, and under Article 43 most of it would apply six months after entry into force. Nothing changes this year.
What the text says about age assurance
The key lines of Chapter V, quoted from the proposal text:
- Article 28(1), no identification. Age assurance solutions "shall not enable the identification of the recipient nor locate, track, target, advertise to or profile recipients for any purpose."
- Article 28(3), zero knowledge. Providers, "and any entity acting on behalf or together with such providers in age assurance", must use state-of-the-art technology, and: "Any age assurance measure shall be zero knowledge proof."
- Article 29(2), one route for social-media accounts. To enforce the minimum age of 15, platforms "shall rely exclusively on an EU age verification solution using an EU proof of age attestation, provided by a third party, certified as conforming with the EU Age Verification Scheme". The recitals add that the solution "should be provided by an independent third party". The scheme itself was set up in Commission Recommendation (EU) 2026/1035.
- Article 29(3), certification by a public authority. EU Digital Identity Wallets certified under eIDAS that meet the scheme are deemed certified.
- Article 29(4), other methods elsewhere. For the general safety-by-design duty (Article 8(1)) and for app stores (Article 16(2) and (3)), providers "may use age assurance solutions other than the EU age verification solutions", if they can show those solutions meet Articles 27 and 28, the zero-knowledge sentence included.
- Article 30(1), two EU lists. The Commission would keep machine-readable lists of certified proof-of-age attestation providers and of certified EU age verification solutions.
- Article 31(5), a free route in every country. Each Member State must make at least one certified EU age verification solution available to citizens and residents free of charge.
In short: one locked route for social-media sign-ups, an open door for everything else, and the same zero-knowledge rule for both. Yet the proposal never defines "zero knowledge proof".
Who leads in Parliament
The file was referred to committees on 22 October. The Legislative Observatory lists IMCO (Internal Market and Consumer Protection) as the committee responsible, with SANT, ITRE, CULT, JURI and LIBE giving opinions. As of today it names no rapporteur, and it lists Leila Chaibi (The Left) as shadow rapporteur. ITIF's EU Kids Act Bulletin #3 reported on 10 November that the EPP and S&D groups will co-lead Parliament's work. We found no draft report and no Council position yet.
Where the real debate is: scope and timing
The documents show no real fight over zero-knowledge proofs. None of the voices below argues against ZKP itself. The concerns are about how widely age checks are used and when they start.
The EDPS supports ZKP but questions the scope and the timing. In Opinion 36/2026 of 12 November, the European Data Protection Supervisor "very much welcomes the requirement to use zero knowledge proofs in Article 28(3)". It asks for a definition in Article 3, so that a proof shows the statement (for example "over 18") and nothing more. Its concerns lie elsewhere, as Agence Europe reported: the approach "de facto incentivises the widespread deployment of age assurance mechanisms". One key recommendation is that the obligations "should only enter into application when the privacy-preserving solutions envisaged by Proposal are effectively available across the EU". It also wants several age-assurance options rather than one, reminds lawmakers that using the EUDI Wallet must stay voluntary, and is sceptical of age estimation. In its words, "a zero-knowledge proof of an estimated result does not establish either the accuracy of that result".
Nineteen NGOs want broader, risk-based rules. On 29 October the Coalition for Children's Rights Online, including 5Rights, COFACE Families Europe, Eurochild, ECPAT International and the Internet Watch Foundation, published a joint reaction. It welcomes the proposal and asks for "a greater tech neutral approach through streamlined obligations and safety requirements for services, which should be based on the level of risks". In context, "tech neutral" is about which services the rules cover (risky features rather than service categories), not about age-verification technology. The letter does not mention zero-knowledge proofs. It also wants pre-certification of services.
Digital-rights groups question age-gating itself. EDRi wrote on 30 September that "age-gating cannot be a technological shortcut for a problem rooted in platform design and business incentives", and pointed to DSA enforcement and the Digital Fairness Act instead. A KU Leuven report, as summarised in the same bulletin, concludes that age assurance should be a limited, rights-preserving tool rather than a quick fix.
Our reading: the zero-knowledge requirement has a strong ally in the EDPS. The risk to it is timing. If ZKP-capable solutions are not widely available when the rules would apply, co-legislators can either delay the obligations, as the EDPS suggests, or water down the requirement. That choice is still open.
What it means for webshops: mostly indirect
Article 2(1) lists the services in scope: social networks, video-sharing platforms, app stores, online games, operating systems, AI companions and chatbots. A webshop selling alcohol, tobacco, nicotine or vapes is not on that list, and Article 2(7) leaves EU consumer law untouched. Your age obligations still come from national law, such as the Dutch Alcoholwet (see our Netherlands post).
The indirect effects are still worth knowing:
- More customers would hold a proof of age. If Article 31 survives, every Member State would have to offer a free, certified way to obtain and present one.
- A recognised quality bar. Certified, listed EU solutions would give national regulators an obvious reference point. That is our inference, not something the text says.
- But no automatic recognition for your sector. Article 31(7) makes listed solutions recognised "for the purposes of this Regulation", not for national alcohol or tobacco law.
What it means for age-verification vendors: certification and ZKP
For vendors, the stakes are direct:
- Social-media sign-up becomes a closed route. ID-document scans and facial age estimation would not count for the minimum-age rule. Only certified EU solutions built on EU proof-of-age attestations would. How certification works will be set in implementing acts under Article 30(2), which do not exist yet.
- Everywhere else, your own method must clear the ZKP bar. Article 29(4) allows other solutions, but Article 28(3) applies to "any age assurance measure". Delegated acts under Article 30(3)(a) would set the details.
- The obligations reach you, not just your client. Article 28(2) and (3) explicitly cover "any entity acting on behalf or together with" a provider.
- Operating systems could compete for volume. Under Article 29(6) an OS that has checked a user's age would share that age signal, with the user's consent.
- An open question. The text does not say whether a hosted verifier serving many platforms needs certification as an "EU age verification solution" itself, or how it gets onto the list.
Where eIDAS Pro stands
Today we verify the EU proof-of-age attestation from the EU Age Verification app route, which needs no relying-party registration. We have tested it end to end with the EU reference app against the acceptance list. The production EU trusted list, reissued on 5 November, names one issuer, Denmark's Agency for Digital Government (AltID). Its next scheduled update is 28 April 2027.
Those presentations share only an issuer-signed age-over attribute, such as over 18. That is data-minimal, but not a zero-knowledge proof in the strict cryptographic sense. Verifying zero-knowledge age proofs (based on Google's open-source Longfellow ZK) is on our roadmap for Q1 2027; it is not available today. More in the DC API, OpenID4VP and ZKP fallback matrix.
What to do now
- Read Chapter V (Articles 26 to 32). It is short, and it is the part that matters for age checks.
- Submit feedback on the Have Your Say page. The Commission's press release says the period closes on 26 November 2026. The same page, and the portal itself, give 3 December (midnight Brussels time). Plan for 26 November. Points we think are worth making:
- keep the zero-knowledge requirement and define it, as the EDPS proposes;
- spell out how hosted verifiers and intermediaries get certified and listed, with a route small companies can afford;
- adopt the implementing acts and open certification well before the obligations apply;
- fix the cross-references: Article 30(1) refers to certification "in accordance with Article 29(2)", which is in Article 29(3), and Article 31(7) refers to lists in "Article 29(1) point (a) and (b)", which are in Article 30(1).
- Webshops: nothing new to do under this proposal. Keep meeting your national rules with a check that returns only yes or no.
- Age-verification vendors: map each method you sell against Article 28(3), and plan for certification.
- Watch for the IMCO rapporteur, the draft report, the Council's position and the first implementing acts.
eIDAS Pro provides privacy-first age verification for European merchants and age-verification vendors: the EU proof-of-age attestation via the EU Age Verification app route, bank eID through the broker IDURA (Dutch iDIN today, Danish MitID coming), and EUDI Wallet + managed access certificates as national registers open (2027). Book a consultation →
This post reflects the position as of 17 November 2026 and is general information, not legal advice. The EU KIDS Act is a Commission proposal and may change substantially in Parliament and Council. Verify against the proposal text before relying on specifics.
Related Articles
DC API, OpenID4VP, ZKP: The Runtime Fallback Matrix Every Age-Verification Verifier Must Implement
The EU age-verification verifier guide is unambiguous: your verifier must support two presentation mechanisms and select the best one at runtime. DC API is primary, OpenID4VP is the fallback. Get the fallback matrix wrong and a slice of your users silently fail the age gate.
10 min read
The End-2026 Deadline That Isn't a Law: Inside the Commission's 29 April Age-Verification Recommendation
On 29 April 2026 the European Commission urged Member States to make an age-verification app available to citizens by the end of 2026. It is a Recommendation, not a Regulation — non-binding by design. For relying parties, the distinction between 'urged' and 'mandated' is exactly where the planning happens.
9 min read
Tags
Share this article
Help others learn about eIDAS verification
