When a site asks you to prove your age, the buttons all look the same: “continue”, “verify”, “confirm”. Behind them, though, are very different technologies. Some hand the site a single fact, “over 18”. Others hand over your document, your face or your date of birth, sometimes to a company you do not know.
This post describes the age assurance methods you may come across, from anonymous proofs to document matching, and the tools that go with them: privacy notices, rights and rules. Brand names vary; we describe them generically.
It is the technical side of the recommendation to prove only what is asked. The practical sequence for choosing between them, in the right order, is in the guide on how to verify your age without oversharing.
How to read this list
The technologies are divided into four groups, like the phases of security:
- prevention: the verification methods themselves, ordered from those that hand over least to those that hand over most;
- detection: the tools that let you see what you are handing over, and to whom;
- response: the tools to remove what is no longer needed or to correct a mistake;
- governance: the rules and authorities that set what a check may ask for.
For each method you will find what the site receives, the risk it reduces, strengths, limits, an example and complexity. One principle applies to all of them: a site usually needs a fact, not your identity. The EDPB, the board that brings together the EU’s data protection authorities, puts it this way: a service may only need to know whether the user is over or under an age threshold.
1. Prevention technologies
Double-anonymity proof
This is a model in which two pieces of knowledge stay in different hands. A party that has already identified you, such as a bank or a digital identity provider, issues a proof that you are an adult, but does not know which site you need it for. The site checks the proof, but does not receive your identifying details. In Italy it is the model AGCOM chose for adult content sites; the CNIL, the French regulator, recommended it back in 2022, with an independent third-party verifier.
- What the site receives: proof that you are an adult, without your name.
- Risk reduced: a link between your identity and the sites you visit.
- Strengths: none of the parties holds the complete link on its own.
- Limits: it works only if whoever issues the proof is genuinely independent of the site.
- Example of use: a site sends you to an app that generates the proof and then lets you present it.
- Complexity: low for you, once set up.
Digital identity wallet and age verification app
A digital identity wallet is an app on your phone that holds verified attributes about you and lets you show just one, such as “over 18”. The European Commission writes that Member States will make European Digital Identity Wallets available to every citizen, resident and business by the end of 2026, and that users share only what is necessary. For age, the Commission has also developed a solution that, according to its page updated on 18/05/2026, lets the platform know only whether you are over the threshold, without telling it who you are, and without linking the different uses by the same person.
- What the site receives: a yes or a no to the age question.
- Risk reduced: handing your document and your face to the site.
- Strengths: you register your document once, with whoever issues the proof, and then show only the fact.
- Limits: the Commission expects it EU-wide by the end of 2026, so you may not find it yet; how well it protects you depends on how each national app is built.
- Example of use: a video platform asks for your age and you confirm it from the app.
- Complexity: medium the first time, low afterwards.
Zero-knowledge proofs
A zero-knowledge proof is a cryptographic technique that shows a statement is true, for example “is over 18”, without revealing anything else, not even the date of birth. The EDPB mentions it among the protocols that help share less, together with unlinkability, meaning that different uses by the same person cannot be joined up. The EU age solution is based on this technology.
- What the site receives: proof that the statement is true, and nothing else.
- Risk reduced: reconstruction of your visits and your date of birth.
- Strengths: it works invisibly, inside the app you use.
- Limits: you do not choose it directly: it depends on the method the service offers.
- Example of use: two different sites receive your proof of age and cannot tell it was you both times.
- Complexity: none for you.
Bank confirmation
In the UK, Ofcom lists among the possible methods secure access to your bank data to confirm you are over 18. The EFF, a digital rights organisation, writes (June 2026) that with this method the service receives the confirmation, and that the user’s full date of birth is not shared.
- What the site receives: confirmation that you are over 18.
- Risk reduced: handing over your document and your face.
- Strengths: your bank already knows you; you do not need to upload anything.
- Limits: your bank knows you asked for a check; you sign in to your bank from a page linked to the check, so start only from the service you opened yourself.
- Example of use: an online off-licence offers to confirm your age with your bank.
- Complexity: low.
Mobile network confirmation
Your mobile network checks whether your line has the restrictions set for under-18s: if it does not, it confirms you are an adult. Your phone number is needed, so it becomes the link between you and the check: when to give it, and to whom, is the subject of the recommendation on sharing your phone number only where needed.
- What the site receives: confirmation that you are an adult, tied to your number.
- Risk reduced: handing over your document and your face.
- Strengths: quick, with no images.
- Limits: it may not work with lines registered to someone else or with restrictions switched on; the site knows your number.
- Example of use: a platform that already has your number asks for your network’s confirmation.
- Complexity: low.
Facial age estimation
A system analyses a photo or short video of your face and estimates an age. Some systems run the analysis on the device, so that only the result leaves your phone; many, according to the EFF, upload the image to the servers of whoever runs the check. The CNIL points out that face analysis is intrusive and that every estimate has a margin of error.
- What the site receives: the result of the estimate; the image, depending on the system, stays on your phone or passes through a company.
- Risk reduced: handing over your document.
- Strengths: quick, with no document.
- Limits: you hand over an image of your face; the estimate can be wrong, especially close to the threshold.
- Example of use: an app asks you to look at the camera for a few seconds.
- Complexity: low.
Payment card check
Ofcom lists credit card checks, because you must be over 18 to hold a credit card.
- What the site receives: your card details, or the network’s confirmation that the card is valid.
- Risk reduced: handing over your document.
- Strengths: convenient if you are already paying.
- Limits: you hand over payment details; outside a purchase, a request for your card is a common trick of fake pages.
- Complexity: low.
Document and selfie matching
You upload a photo of your document and a selfie; a system checks that the face matches. It is the method that hands over the most. For adult content sites, AGCOM’s resolution of 08/04/2025 does not consider it compliant with privacy requirements.
- What the site receives: your full document and an image of your face, directly or through a provider.
- Risk reduced: use of someone else’s document.
- Strengths: it works when no other method is available, and it suits genuine identity checks.
- Limits: it creates a copy of your identity with others, to be kept safe and, one day, deleted.
- Example of use: opening a payment account, where the law requires you to be identified.
- Complexity: low for you, high for whoever looks after the data.
Self-declaration
You type your date of birth or tick a box. It hands over little, but for services covered by the UK rules, Ofcom points out, ticking a box is no longer enough.
- What the site receives: what you declare.
- Risk reduced: handing over your document and your face.
- Strengths: simple.
- Limits: it is not accepted where the law requires effective checks; your full date of birth is still a permanent detail.
- Complexity: none.
2. Detection technologies
The explanation of the check
Ofcom says users should be able to read a statement setting out the kinds of age checks available and how they work. It is the simplest tool for understanding what you are about to hand over.
- Risk reduced: choosing a method without knowing what it hands over.
- Strengths: it is there before the first button.
- Limits: it can be vague or hard to find.
- Example of use: a “How we check your age” page with a paragraph for each method.
- Complexity: low.
The privacy notice and the provider’s name
The ICO, the UK regulator, expects those carrying out age assurance to be clear, open and honest about how they use people’s information. The privacy notice should say who runs the check, what it keeps and for how long.
- Risk reduced: data handed over to unknown parties.
- Strengths: it tells you whom to contact to use your rights.
- Limits: it has to be read, and it is not always clear.
- Example of use: the notice names the outside company and how long document images are kept.
- Complexity: medium.
The wallet’s sharing screen
When a digital wallet asks you to show an attribute, it usually shows you what it is about to share, and the Commission lists among its principles full control over what you share and the ability to keep track of it.
- Risk reduced: sharing attributes that are not needed.
- Strengths: you see the request before confirming it.
- Limits: it works only if you read it.
- Example of use: the wallet shows “the service is asking for: over 18” and waits for your confirmation.
- Complexity: low.
3. Response technologies
Access and erasure
The GDPR and the UK GDPR give you the right to know what an organisation holds about you (Article 15) and to ask for data that is no longer needed to be erased (Article 17), with a reply normally within one month.
- Risk reduced: copies kept beyond the purpose of the check.
- Strengths: free, with no special formalities.
- Limits: you need to know whom you handed the data to.
- Example of use: you ask a shop you no longer use to delete the photo of your document.
- Complexity: low.
Alternative method and challenge
If a check gets it wrong, a channel to challenge it and an alternative method spare you from handing over more. The EDPB recommends that alternatives be available when reasonably possible.
- Risk reduced: being shut out of a service because of an estimation error.
- Strengths: you do not have to send a document straight away.
- Limits: not every service offers this prominently.
- Example of use: after a wrong estimate, you ask for confirmation through your bank.
- Complexity: low.
4. Governance technologies
The rules on age checks
In the UK since 25/07/2025, in Italy since 12/11/2025, in the EU with the solution expected by the end of 2026: the rules set who must carry out checks and with what safeguards. Alongside them sits the GDPR, which requires data minimisation (Article 5) and data protection by design (Article 25). Regulators oversee them: in the UK, Ofcom and the ICO; in Italy, AGCOM and the Garante.
- Risk reduced: checks that collect more than needed.
- Strengths: they apply even when you cannot choose.
- Limits: they vary between countries and over time; a complaint takes time.
- Example of use: an Italian site offers you only double-anonymity methods.
- Complexity: none for you.
Comparison table
| Method | What the site receives | Complexity | When to use it |
|---|---|---|---|
| Double-anonymity proof | A proof with no name | Low | Always, when offered |
| Wallet or verification app | A yes or a no | Medium, then low | When available |
| Bank confirmation | That you are over 18 | Low | Starting from the service you opened yourself |
| Mobile network confirmation | That you are over 18, with your number | Low | If the site already has your number |
| Facial estimation | The result; the image depends on the system | Low | If the analysis is on the device or deletion is clear |
| Payment card | Card details or confirmation | Low | Only during a genuine purchase |
| Document and selfie | Full identity and face | Low | For genuine identity checks |
| Self-declaration | What you declare | None | Where the law does not require more |
How to choose
- If you only need to prove your age: look first for an anonymous proof, a wallet or confirmation from your bank or mobile network; keep the document for last.
- If you need to prove who you are: the document may be genuinely needed; send only what the process asks for, covering, where it is allowed, the details that are not needed, as explained in the recommendation on sharing documents with only what is needed.
- If only a face estimate is left: check whether the image stays on the device or is deleted, and when.
- If no method feels right: ask for an alternative, or give up that service.
The practical rule: for age, the right method is the one in which the site receives a fact. You use your document only when the fact to prove is your identity.
How this connects to the Cyber Welfare Framework
| Pillar | What this content contributes |
|---|---|
| Skills | Knowing the verification methods and the tools that go with them, and recognising them when you meet them |
| Awareness | Understanding what the site receives with each method, and that a fact and an identity are two different things |
| Secure Behaviour | Choosing the method that fits the fact to prove, and using your rights when something is kept longer than needed |
Reference level: FL3 — Autonomous. This is the level where the method is chosen with judgement, rather than accepting the first button, and response tools are used when needed. To measure your other digital habits, you can take the digital resilience self-assessment.
Conclusion
The methods for proving your age range from a proof that says only “over 18” to a full copy of your identity. None is perfect, and some, like face estimation, depend heavily on who runs them.
Knowing what the site receives with each one gives you back a choice the first button would have made for you.
Related content
- Prove only what is asked — the recommendation this post comes from
- How to verify your age without oversharing — how to use these methods, in the right order
- Age verification privacy risks — what these methods protect
- How social login works — the neighbouring topic of what a site receives when you sign in with your social media profile
Related resources
Short reads from the Resources section, for anyone who wants to focus on a single aspect:
- Age Verification and Anonymity: What Changes for You
- Online Age Verification: Prove Your Age, Share Less
Start with the first step: the Cyber Welfare Programme guides you free of charge, one recommendation at a time.




