The EU's Age-Verification App: Privacy by Design, or Just by Press Release?

1. What Brussels actually announced

On 15 April 2026, European Commission President Ursula von der Leyen said the EU's age-verification app was 'technically ready' and would reach smartphones by summer. It is a 'mini-wallet' — a deliberately narrow slice of the much larger EU Digital Identity Wallet that every member state must offer citizens by the end of 2026 under the eIDAS 2.0 regulation.

The pitch is appealing: prove you are old enough to access a service without handing over your passport, your name, or your date of birth. The service learns one fact — over 18, yes or no — and nothing else. The technology that makes this claim plausible is genuinely real, and it is worth understanding, because the gap between how this can work and how it will be deployed is the whole story.

2. Zero-knowledge proofs, explained without the maths

A zero-knowledge proof lets one party prove a statement is true to another party without revealing any information beyond the truth of that statement. The classic intuition: imagine proving you know the password to a door without ever saying the password — by repeatedly demonstrating you can open it. The verifier becomes convinced; they never learn the secret.

For age, the relevant flavour is a zero-knowledge range proof. Your wallet holds a credential issued by a trusted authority that encodes your date of birth. When a website asks 'are you over 18?', the wallet generates a fresh cryptographic proof that your encoded birth date falls before a threshold date — and the website verifies that proof mathematically. It never sees the birth date itself. Crucially, a well-designed system records only the result of the check, not the underlying data.

This is not theoretical. Range proofs are deployed cryptography, and standards bodies are actively maturing the wider family of techniques. NIST's Privacy-Enhancing Cryptography project tracks zero-knowledge proofs alongside multi-party computation and homomorphic encryption, and contributed to the 2025 National Privacy Research Strategy. The building blocks are sound.

3. The word that decides everything: unlinkability

Here is where 'privacy by design' becomes either true or a slogan. A zero-knowledge age proof can be built so that two checks — say, one at a gambling site on Monday and one at a dating app on Friday — cannot be correlated with each other or traced back to a single identity. That property is called unlinkability, and it is the difference between a privacy-preserving credential and a tracking beacon.

If each proof is freshly randomised and carries no persistent identifier, the issuer and the relying parties cannot reconstruct a profile of where you went. If, on the other hand, the wallet attaches a stable token, or the issuer is pinged to validate each use in real time, then you have built a system that logs every adult site, betting page, and app you ever proved your age to — under a banner that says it protects privacy.

The cryptography supports the good version. Whether the deployed app delivers it depends on engineering choices that are not visible from the marketing. The research community knows this: a strand of 2026 work focuses on combining trusted execution environments with zero-knowledge proofs precisely to guarantee unlinkable, self-sovereign use of wallet credentials.

4. Three questions to ask of any age-check system

You do not need a cryptography degree to evaluate one of these systems. You need three questions. One: can the issuer see where I used it? If the proof requires the issuer to be contacted at the moment of each check, the issuer can build a log. A good system lets the wallet generate proofs offline, with no phone-home.

Two: are my separate uses linkable? Ask whether each proof is unique and unlinkable, or whether a persistent identifier rides along. Reused identifiers are how anonymous checks quietly become a behavioural profile. Three: what is retained, and by whom? The privacy-preserving design stores only a yes/no result on the relying party's side and nothing on the issuer's. If the answer involves 'we keep an audit log for security,' ask exactly what is in it and for how long.

These three questions cut straight through 'privacy by design' language to the architecture underneath. They are also the questions journalists and regulators should be putting to the Commission and to every member-state implementation as the app ships this summer.

5. Why this matters beyond pornography

Age verification is the thin end of a much larger wedge. The same wallet infrastructure that proves your age can prove your nationality, your residency, your professional licence, your right to work. Once the rails exist and the public is habituated to 'just prove it with the app,' the cost of extending mandatory verification to new contexts falls to almost nothing. That is why the architecture of the first mandatory use case matters so much: it sets the privacy baseline for everything that follows.

If the age-verification mini-wallet ships with genuine unlinkability and no issuer-side logging, it becomes a template for privacy-preserving identity across Europe — a genuinely good outcome, and proof that safety and anonymity are not opposites. If it ships with shortcuts, it normalises a surveillance pattern dressed in privacy language. The technology is not the variable. The deployment is. Watch the deployment.

6. References