EU prepares online age checks without disclosing identity

EU prepares online age checks without disclosing identity

Rating
—/5 0 ratings
Follow us on Google News
Technology7 min read

The European Union is preparing an online age-verification solution under which a website should learn, for example, only that a person is over 18. It should not automatically receive their name, date of birth or a photograph of their identity card.

This differs significantly from the process now common on many platforms: uploading an identity document, taking a selfie, or allowing an intermediary to retain a copy of the document. Under the model promoted by the European Commission, identity is verified when a digital credential is issued; the platform subsequently receives only the answer relevant to access — for example, “over 18: yes”.

What is known so far: the 31 December 2026 deadline is a target in a recommendation to Member States, not evidence that every country, platform and phone will have a working system by then. In Romania, the official RO Wallet page says features will be introduced gradually and does not yet confirm an exact availability date.

What the platform would see — and what it should not

The European Commission’s published explanation describes a mechanism based on an attribute rather than the transfer of a person’s full identity. If a service requires users to be at least 18, the app can present confirmation that the threshold has been met, rather than a copy of the document used to establish the person’s age.

Different parties have distinct roles in the basic model. An issuer or attestation provider verifies the person’s age and issues the credential. The user’s app stores it. The website or app requesting the check validates the credential when access is sought.

Stage Role Remaining limitation
Issuing the credential A provider verifies that the user is above the age threshold. This party processes the data needed for the check; those data do not disappear from the initial chain.
Storage in the app The credential is stored on the user’s device. Protection of the phone, app and account remains important.
Presentation to the platform The platform should receive the answer related to the required threshold. The platform may already hold other data: an account, IP address, cookies, payment data or device data.

So the accurate claim is not “no personal data” in every sense. Data may be needed to issue the credential. The promise is narrower, and more useful: minimising the data sent to the platform requesting the check.

Why the difference between ZKP and the fallback matters

The technical blueprint for the European solution requires apps to implement zero-knowledge proofs, or ZKPs, as the preferred presentation method. In plain terms, a ZKP is intended to allow a fact — “I am over 18” — to be verified without disclosing the information behind it, such as an exact date of birth.

The European project’s technical specification also includes an ISO mDoc-based alternative for devices that cannot use the ZKP flow. This technical detail has a practical consequence: not all phones and national implementations will necessarily provide the same level of privacy protection on day one.

ZKP is preferred precisely because it can reduce the risk that several checks can be linked to one another. In the technical documentation, straightforward mDoc presentation is described as a fallback mechanism, and exactly how it is used depends on the app, operating-system version and platform integration.

A categorical conclusion should be avoided here. Cryptographic technology can limit the information transmitted in a check, but it does not automatically make the user invisible. A platform may still recognise the logged-in account, device or session from which access was requested.

Privacy does not automatically mean unlinkability

The less visible issue is unlinkability: preventing multiple presentations of a credential from being associated with the same person. In its analysis of digital identity wallets, the European Data Protection Supervisor (EDPS) warns that selective disclosure of attributes alone does not resolve the risk of correlation: certain identifiers or signatures may make it possible to link transactions.

The EDPS document on digital wallets does not say that the European age-verification solution is useless. It does explain why the statement “the platform does not receive the name” is insufficient to assess a user’s privacy. What matters is the protocol actually used, whether the credential can be reused, technical logs, attached identifiers and data the service collects separately.

This is also why an app with a simple interface should not be judged solely by its on-screen message. The architecture behind it — the issuer, trust lists, validation mechanism and security updates — determines how much of the privacy promise reaches the user in practice.

The European deadline does not automatically bind every site or user

On 29 April 2026, the European Commission adopted a recommendation calling on Member States to make an age-verification solution available by 31 December 2026. It may be integrated into the European Digital Identity Wallet, delivered in a separate app, or used in both forms.

The text of the recommendation published in the Official Journal of the EU also matters for its legal nuance: a recommendation sets a policy direction and timetable, but does not demonstrate that the same experience will be available simultaneously in every Member State. Nor does it, by itself, establish that every platform or every citizen will have an identical obligation on that date.

Adoption will depend on national apps, device compatibility and online services’ decisions to accept the credential. In practice, age checks could appear on platforms with adult content, certain games or services with age limits, but the specific list of services and thresholds applied will depend on the relevant rules and each platform’s implementation.

Where Romania stands: a project in development, not a publicly confirmed feature

For Romanian users, the practical question is whether RO Wallet will already be able to issue and present such a credential. The cautious answer is that there is not yet public confirmation of general availability for this flow.

The official RO Wallet FAQ says Romania is working on the digital wallet, that functions will be added in stages, and that the exact availability date is yet to be confirmed. It is therefore not justified to say that Romanians can already use European age verification widely across online services.

Several issues still need to be clarified publicly: which documents or credentials will support issuing the proof; which phones will be compatible with the ZKP method; which platforms will accept it; and what alternative will be available to people without a compatible phone or access to the digital wallet.

For more information on digital identity, see RO Wallet in stages: which documents remain outside the digital wallet for now, which provides complementary details on the subject.

The discussion forms part of a broader shift: digital identity is becoming infrastructure for access, not merely a password. The difference between authentication and proving an attribute matters in other situations too, from account access to public services, as explained in InfoBuz’s analysis of passwordless authentication and digital identity.

What to watch before launch

A credible system is not measured only by its promise not to send a copy of an identity card to a website. To assess the mechanism in Romania, publicly verifiable information should be available on:

  • the method used in the released version: ZKP, ISO mDoc or both;
  • compatible phone models and operating-system versions;
  • providers authorised to issue attestations and the validation rules;
  • platforms that accept the credential and options for users who are technically excluded;
  • audits, security updates and data-protection assessments.

From a technical standpoint, age verification without disclosing identity is a more privacy-protective direction than repeatedly uploading an identity document to websites. But the outcome for the public will not be determined by cryptography alone. It will depend on national implementation, available apps, platform rules and the transparency with which all of these elements can be scrutinised.

Frequently asked questions

Will I have to send my ID directly to a website for age verification?

In the architecture proposed by the European Commission, the site should receive only confirmation that you are above the required threshold, not a copy of the document or your date of birth. The document or other data may nevertheless be needed at the separate stage of issuing the credential.

Does this mean platforms will no longer be able to learn anything about me?

No. The age credential may limit the data sent through that flow, but the platform may already have account data, an IP address, cookies, payment information or device signals.

Is online age verification already available in Romania?

There is no public confirmation that the European mechanism is widely available to Romanian users. RO Wallet is officially presented as a project in development, with features being introduced gradually.

What is a zero-knowledge proof?

It is a cryptographic method for proving a fact, such as being over 18, without disclosing the full information from which that fact follows, such as the exact date of birth.

Sources consulted

Etichete: online privacyEUDI WalletDigital identityData protectionRO WalletEuropean UnionAge verification
Share this article
COMUNITATEA INFOBUZ

Discuția cititorilor

Ai o opinie sau o întrebare despre acest articol? Spune-ne ce crezi.

0 comentarii

Fii primul care deschide discuția.

Lasă un comentariu

Email address este vizibilă doar administratorilor și nu va fi publicată. Câmpurile marcate cu * sunt obligatorii.

Te rugăm să păstrezi un limbaj civilizat și să discuți la subiect. Comentariile spam sunt filtrate automat.