Notifications
Clear all
Topic starter
02/08/2026 12:18 pm
TL;DR: Italy’s AGCOM rules for adult content require double blind, per-session age checks that return only an over-18 result and do not expose user identity or site context, according to Yoti. That makes reusable digital credentials and wallet-based proofing the practical model, while one-time checks, direct logins, and identity-linked methods no longer fit the compliance bar.
NHIMG editorial — based on content published by Yoti: Italy’s AGCOM age assurance requirements and double blind verification methods
Questions worth separating out
Q: How should security teams implement double blind age verification?
A: Security teams should design age verification so the relying party receives only an over-18 claim and the verifier cannot see which site requested it.
Q: Why do account-based age checks fail privacy-preserving verification requirements?
A: Account-based checks often reveal who the user is, which account they used, or which identity provider authenticated them.
Q: What breaks when age verification is treated as a one-time control?
A: A one-time control assumes the trust decision persists.
Practitioner guidance
- Separate verification from identification Design the flow so the relying party receives only an age result, not name, location, or identity attributes.
- Re-check age on each session Do not treat first-time verification as durable authorisation for future visits.
- Classify methods by disclosure risk Rank verification methods by both assurance strength and the amount of identity data they reveal.
What's in the full article
Yoti's full article covers the operational detail this post intentionally leaves for the source:
- How the double blind model is expected to work in practice for websites and wallet-based proofing flows
- Which age assurance methods AGCOM classifies as not permitted, weak, or conditional
- How Yoti describes its wallet and facial age estimation approach under the new privacy requirements
- The specific user journey and trust boundaries for reusable digital identity credentials
👉 Read Yoti’s analysis of AGCOM age assurance requirements and double blind verification →
AGCOM age checks: what double blind verification means for IAM teams?
Explore further
02/08/2026 1:20 pm
Double blind age verification is an identity architecture problem, not just a compliance checkbox. AGCOM’s requirement that neither the verifier nor the content provider learn unnecessary identity data forces the control boundary away from accounts and toward claims. That matters because the system must prove eligibility without turning the user into a reusable identity record. Practitioners should view this as a policy design issue, not a UI toggle.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.
A question worth separating out:
Q: Which frameworks are relevant to privacy-preserving age assurance?
A: Controls that emphasise data minimisation, access governance, and security of processing are the closest fit. For practitioners, that usually means mapping the flow to NIST Cybersecurity Framework principles and, where personal data is involved, to GDPR obligations around minimisation and security.
👉 Read our full editorial: AGCOM age checks shift identity proofing toward double blind verification
