Topic starter
02/08/2026 12:11 pm
TL;DR: Privacy-preserving age tokens, passkey binding, and device-local reuse are becoming practical at scale, with Yoti saying it has completed 1 billion age and identity checks globally and now supports millions of token generations each month. The key issue is governance, not novelty: verifiers need age assurance without building cross-site tracking into the identity layer.
Editorial analysis by NHI Mgmt Group, based on content published by Yoti: “Yoti age tokens, passkeys and privacy: Reflections on 6 years of scaling privacy-preserving age assurance”.
By the numbers:
- Over 21 million people globally have downloaded the Yoti Digital ID app.
Key questions
Q: How should organisations govern reusable age tokens without creating cross-site tracking?
A: Use a policy that limits what the verifier learns at presentation time, and avoid collecting token-use telemetry that would reintroduce traceability.
Q: When should teams allow passkey-bound age proofs instead of browser-local tokens?
A: Allow passkey-bound age proofs when the programme needs persistence across sessions or private browsing modes and can support device-controlled lifecycle management.
Q: What are the best practices for age assurance acceptance rules?
A: Best practice is to define the proof sources you will accept, the minimum verification strength for each use case and the jurisdictions where those proofs are valid.
Practitioner guidance
- Define acceptance policy by assurance level Set explicit rules for which age proof sources are acceptable, including whether you require document verification, live selfie matching or inference-based checks.
- Separate token reuse from user tracking Design controls so that verification succeeds without retaining user-level visibility into where or how often a token is later presented.
- Decide whether device-bound persistence is permitted Review whether passkey-bound age tokens fit your retention, recovery and device trust model before enabling them in production.
Bottom line: Privacy-preserving age tokens have matured into a reusable verification pattern that can operate at scale without exposing full identity data.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 1:15 pm
Privacy-preserving age tokens are becoming an identity pattern, not a niche privacy feature: The article shows that age proofs can now be reused across sites while revealing only the minimum required attribute. That matters because the control objective is shifting from one-off verification to governed credential reuse. For practitioners, the question is whether their identity programme can classify and manage a token that is intentionally opaque after issuance.
A few things that frame the scale:
- eBay's passkey data shows 55-60% of passkey adoption happens on mobile, against around 20% on desktop.
A question worth separating out:
Q: What is the difference between an age token and an age key?
A: An age token is the result of an initial age check that can be recognised by participating websites. An age key is the device stored passkey version of that token, designed for continued use across browsers, including private mode. In practice, the token proves the check happened, while the key lets the user present that result again without re-verifying from scratch.
👉 Read our full editorial: Privacy-preserving age tokens are moving from theory to scale