%201.svg)
How Emblem Works
From first verification to reusable passkey: a complete breakdown of the Emblem flow.
Get StartedContact Us
Three parties. One token.
No shared data.
User is prompted to verify
A user visits an age-restricted platform that uses Emblem. They're prompted to complete an age check through a compatible verification provider.
.png)
Verification is completed
The user verifies through the provider — via selfie, ID, or both. The provider confirms age status and passes the result to Emblem. The provider has no knowledge of which platform initiated the request.
Emblem issues a token
Emblem receives the verification result and generates a cryptographic age token. No personal data is attached. The link between provider and platform is severed at this point.
Platform receives age status
The platform receives the token from Emblem — a simple age-verified yes/no. It has no visibility into which provider performed the check or any user PII.
User creates a passkey
The user is offered the option to create an Emblem passkey. This is browser-based — no app or download required. The passkey is tied to the token, not to any personal data.
Passkey works everywhere
On any future visit to an Emblem-enabled site, the user authenticates with their passkey. No new verification, no new cost, instant access.
Double Anonymity
See why it's important for none of the sides to see each other.
The provider confirms the user's age but has no visibility into which site requested the check.
The platform receives a valid age token but has no visibility into who issued it.
The user's identity and their destination are never held by the same entity.
The verification provider knows both the user's identity and which platform they're accessing.
The platform knows the user verified and which provider performed the check.
Between the two parties, enough data exists to build a complete profile of user behavior.
How Passkeys Work
Age verification
Before a passkey can be created, the user must complete a standard age verification through a compatible provider. This is the initial identity check — selfie, ID, or both.
Passkey creation
Passkeys are generated during the user's first verification, stored in the browser, and tied to a cryptographic token, not to any personal data.
Re-authentication with passkey
On return visits, the passkey is used to authenticate instantly. No new verification event is triggered. The platform receives the same age-verified status.
