How it works

How Age Verify Works

Age Verify enables secure, privacy-first age verification directly on a user's device -- without collecting personal information.


Privacy-first


Policy-driven


Fully customizable

Everything you need to provide age assurance.

More credible than a checkbox-only popup. Lighter than identity verification. Privacy-preserving by design.

An all-in-one platform.

Apply the right age assurance method for the right context. Age Verify supports self-attestation, on-device biometric age assurance, and fallback to another service when policy requires it.

Biometric age assurance

Stronger than a checkbox -- without the friction of document-heavy verification. Combine biometric age assurance with unlimited checkbox self-attestation so you can match assurance strength to the risk of the flow.

Rules engine

Decide who sees what verification, where, and when. Configure age assurance by country, market, page, route, product, category, action, and property. Use allow, block, redirect, or stronger-verification outcomes.

Fallback orchestration

Redirect or escalate only when policy requires it. Apply the lightest acceptable method first, then hand off to a stronger external provider only where necessary.

Analytics portal

See what is passing, failing, converting, and getting blocked. Track verification outcomes, fallback activity, fresh versus reused results, policy behavior, included volume, and overages from one portal.

Policy templates and configuration

Start with structure, not guesswork. Launch from templates designed for common age-gated use cases, then configure and govern them centrally through the portal.

Customizable UI

Verify your users in your own words. Use your own brand voice and localize to whichever language you choose, with easily customized verification messaging

Reusable verification

Reuse eligible verification outcomes instead of checking every time. Signed reusable decision tokens reduce repeat friction while preserving policy control.

How Age Verify Works in Six Steps

1) Trigger age check only where needed

Prompt users in sensitive flows while keeping lower-risk paths on lightweight attestation.

2) Apply policy by context

Choose threshold and verification mode by product area, action, and geography.

3) Return a signed outcome

Receive a tamper-resistant pass/fail result designed for backend trust decisions.

4) Enforce access on your server

Gate content, features, and commerce actions with server-side checks, not client-only logic.

5) Route users to a step-up flow if needed

Escalate to an identity-based service only when you need to.

6) Reusable tokens for repeat sessions

Support a smoother return-user experience using policy-controlled verification lifetime windows.

Ready to jump in?

Use stronger age assurance where it matters, and lighter flows where it does not.