Age verification without ID uploads: comparing the methods
Self declaration, ID upload with a selfie, facial age estimation, credit cards and digital identity wallets compared on privacy, accuracy, cost, conversion and GDPR data minimisation.
In short
- Self declaration is free and easy, and the Commission says it is not an appropriate age assurance method. Its preliminary findings against four adult platforms called a one click age gate ineffective.
- ID upload with a selfie gives high certainty, but you or your vendor handle document images and face data. Facial age estimation avoids documents, yet has a margin of error that matters most near the legal age.
- Wallet based proofs, including zero knowledge proofs, are the approach the Commission and the EDPB point to for privacy, because the site learns only that the person is over the threshold. Their weak spot today is coverage: not every visitor has a wallet yet.
- There is no single best method. The guidelines advise offering more than one, with a way to challenge a wrong result.
What you are choosing between
Every age check answers one question: is this person old enough? The methods differ in what they collect to answer it. The Commission's guidelines under Article 28 of the DSA sort them into self declaration, age estimation and age verification, and judge each on five criteria: accuracy, reliability, robustness, non intrusiveness and non discrimination. Our guide to DSA Article 28 covers the legal background. This guide compares the practical options.
One caution on numbers. Vendors publish prices, but we found no neutral, published conversion benchmarks for these methods, so we do not quote any. Measure drop off in your own funnel before and after a change.
The methods side by side
| Method | What the site or vendor receives | Commission view | Main weakness |
|---|---|---|---|
| Self declaration | A checkbox or a typed birth date | Not appropriate (paragraph 52) | Anyone can lie |
| ID upload and selfie | Document image, face image, extracted data | Verification, if robust and data is minimised | Collects identity and biometric data, extra steps |
| Facial age estimation | A face image or a local estimate | Appropriate in defined cases, with independent or audited providers | Margin of error near the threshold |
| Credit card check | Card data processed by a payment provider | Not named in the guidelines | A card is not an age document |
| Wallet proof, including zero knowledge | A signed yes or no | Pointed to as the reference approach | Not every visitor has a wallet yet |
Self declaration
A tick box or a typed birth date costs nothing and adds almost no friction, which is why it is still common. The Commission's guidelines say it does not meet the requirements of robustness and accuracy and is not an appropriate method under Article 28(1) (paragraph 52 of the guidelines). In its preliminary findings of 26 March 2026 against four pornographic platforms, the Commission said a single click to confirm being over 18 is not effective.
Self declaration can still be reasonable as a notice, for services with no legal age requirement and low risk. It should not be your only control for alcohol, gambling or adult content.
ID upload and selfie
The visitor photographs a passport or ID card and takes a selfie, and a vendor checks the document and matches the face. The certainty is high, which fits the guidelines' definition of age verification as relying on physical identifiers or verified sources of identification.
- Privacy: the vendor or the site handles document images, names, birth dates and a face. The EDPB says that when identity documents or biometric data are processed, the utmost attention should be paid to avoiding unnecessary access, processing, sharing and storage. A store of IDs is also a breach target.
- Cost: public list prices run from about USD 0.15 per ID check at Didit to USD 0.80 per verification with a monthly minimum at Veriff, and from EUR 0.30 down to EUR 0.01 depending on volume at Ondato. Prices change and vary by plan, so check before you quote them.
- Conversion: the visitor needs a camera, a document at hand and several steps. Expect some to leave. We do not have neutral data on how many.
- Legal: you now run a high risk processing operation. You will probably need a data protection impact assessment and a processor agreement with the vendor. Ask your data protection officer.
Facial age estimation
Software estimates age from a face image. The guidelines treat it as appropriate where your terms set a minimum age below 18 or the risk review finds medium risk, and they ask for an independent third party or an independently audited system (paragraph 47). For adult content they accept it only as an interim or complementary measure when verification is not yet available, and not beyond the first review of the guidelines (paragraph 38).
- Accuracy: the US standards body NIST evaluated six algorithms in NIST IR 8525 (May 2024). On a common visa photo dataset the best mean absolute error fell from 4.3 to 3.1 years since 2014. NIST warns that this average is not an appropriate metric for age verification, and that error varies with image quality, sex, ethnicity and eyeglasses.
- The consequence: a person aged 17 can be estimated as 20. Services therefore use a challenge age, for example asking anyone estimated under 25 for a second check. That adds a fallback you must also run.
- Fairness: the guidelines require that a method be usable by everyone and that users can contest a wrong result. They give a poor practice example of an estimation model with a margin of error of two years that lets many minors in and keeps many adults out (see the example before paragraph 48).
- Privacy: no document is needed, but a face image still leaves the device in many products. The guidelines note that a less accurate method does not automatically mean less impact, because it may process more personal data (paragraph 33).
- Cost: Didit publishes USD 0.10 per age estimation.
Credit card checks
The visitor enters a credit card, a payment provider asks the issuing bank if the card is valid, and approval is taken as evidence of adulthood. The UK regulator Ofcom lists this among methods that can be highly effective for an 18 plus threshold, and explains that it relies on credit cards being generally limited to adults. Debit cards and other routes that do not require an adult account do not count. Ofcom's preliminary 2026 assessment for age 16 excludes credit cards, because they say little about 16 year olds.
This is UK guidance. We did not find a position on card checks in the Commission guidelines, and the guidelines require that the data relied on comes from a reliable source (paragraph 49). Check with the authority that supervises your sector. A card check can also exclude eligible adults who do not hold a credit card.
Digital identity wallets and zero knowledge proofs
Here the person already holds a credential issued after a proper check, for instance by a government, and their wallet answers one question. The EU age verification solution is the main example. The Commission's guidelines say methods based on trusted government IDs may constitute effective verification when the platform receives no additional personal data, for example through anonymised age tokens, and name zero knowledge proofs as suitable cryptography (paragraph 41). They encourage double blind designs (paragraph 46). The EDPB recommends architectures with user held data, local processing, unlinkability and selective disclosure, and zero knowledge proofs for higher risk cases (paragraph 34).
- Privacy: the site receives a signed yes or no. In the blueprint the proof is single use, and the design aims to stop sites or the issuer from linking visits.
- Accuracy: as good as the issuer check behind the credential, which is the same document based verification, done once.
- Cost and conversion: the visitor approves in an app they already have, with no document or camera. The site pays for integration and verification, not for each ID scan. Conversion depends on how many of your visitors have a wallet.
- Coverage: this is the limit today. National apps are being piloted in seven Member States during 2026, and wallets are due by the end of 2026 (see our guide to the EU age verification app). Browser support also differs. Keep a fallback.
- Engineering: the Commission says its reference verifier is not production ready, so you build, host or buy a verifier.
GDPR data minimisation in practice
Article 5(1)(c) of the GDPR requires personal data to be limited to what is necessary. The EDPB statement applies that to age assurance. A provider should process only the age related attributes strictly necessary for its purpose. It says a service may only need to know whether a user is over or under a threshold, which a token can deliver (paragraph 20). Age assurance should not give additional means to identify, locate, profile or track people (paragraph 15), and a no log policy, where no record of the data used is kept once age is verified, may be a valuable safeguard (paragraph 36).
The Commission guidelines go further for platforms: age data may not be stored or used for other purposes, and the age check should be separate from other data collection (paragraphs 39 and 49). In practice, if you do not need to keep a document, a face or a birth date, do not. What you do not hold cannot leak, and you need fewer controls to defend.
How to choose
| Your situation | A reasonable starting point |
|---|---|
| Adult content, gambling or alcohol, EU audience | Wallet proof as the primary route, plus one document or estimation fallback with a data retention limit |
| Social platform with a minimum age below 18 | Age estimation from an independent or audited provider, plus an appeal route to a verification method |
| Low risk service with no legal age limit | Self declaration and other protective design, documented in your risk review |
| Regulated sector with a national rule | The method your national regulator names, then the least intrusive way to satisfy it |
Offering at least two methods is also what the guidelines ask for (paragraph 48): it avoids excluding people who cannot use one method, and a second route gives a way to correct wrong results.
Where Ageseal fits
Ageseal covers the wallet row only. It asks the visitor's wallet whether they are over 18 and returns a signed yes or no, and it stores no personal data. It does not process documents or faces, so you keep your own fallback for visitors without a wallet. It is in development and has no customers yet.
Sources
- Commission guidelines C(2025) 6826 under Article 28(4) DSA (PDF)
- EDPB Statement 1/2025 on age assurance
- EDPB Statement 1/2025 on age assurance (PDF)
- NIST IR 8525: Face Analysis Technology Evaluation, age estimation and verification
- Commission press release IP/26/722: preliminary findings on four pornographic platforms
- Ofcom: age checks to protect children online
- Ofcom: rapid assessment of highly effective age assurance at 16
- European Commission: EU age verification app and blueprint
- EU age verification project (ageverification.dev)
- Developer guide for verifiers
- Didit pricing, read November 2026
- Veriff plans, read November 2026
- Ondato age verification pricing, read November 2026
This guide is general information, not legal advice. Check your own duties with a lawyer or your regulator.
Ageseal is building the wallet check described here
A script tag asks the visitor’s wallet whether they are over 18 and your server gets a signed yes or no. Ageseal is in development and has no customers yet. Join the waitlist to hear when test mode opens.
Join the waitlist