One REST endpoint returns a verified age band, confidence score and compliance decision, so you can gate content, purchases or access on a user's real age, not a self-declared birthday. Age-calibrated protections are meaningless if a user can claim any age.
Integrate in minutes with official SDKs for Node.js, Python, Swift, Kotlin, Flutter, Unity, React Native and .NET, or call POST /api/v1/verify/age/submit directly. Webhooks return the result asynchronously, responses are typed and idempotent, and no images or documents are ever stored. Configure verification modes per jurisdiction: set "Complete" (document + liveness) for strict markets and "Liveness Only" for lower-friction flows, down to individual EU member states and US states.
Two verification modes
Choose per market, or let users flow through the default. Both include real-time anti-spoofing.
Document + Liveness
Users photograph a government-issued ID. ICAO 9303 MRZ parsing, PDF417 barcode decoding (US/CA licenses), and multi-pass OCR extract date of birth, with text recognition currently optimised for English and Swedish, while 128-dimensional face matching confirms the document holder matches the live selfie.
Best for: strict compliance markets, age-restricted purchases, high-risk platforms
Biometric Age Estimation
Lower-friction: users take a selfie with an HMAC-signed liveness challenge. Age is estimated by our own model running on our infrastructure, no image is sent to any language model and no document is needed. If combined with document mode, dual-source consistency cross-checks both estimates.
Best for: lower-risk content gating, social features, first-time onboarding
Both modes share the same architecture. The most sensitive images we ever see, a child's selfie and an identity document, never leave our own local pipeline and never reach a language model. General content moderation uses vision models we run on our own Vertex AI infrastructure in an EU region. Neither path retains the image.
Different countries. Different rules. One dashboard.
Set "Complete" for Germany (consent age 16) and "Liveness Only" for Sweden (consent age 13) , or override any of the 27 EU member states and 15 US states individually.
EU, GDPR Article 8
The digital age of consent varies from 13 to 16 across the EU. Your verification strictness should match. Tuteliq lets you set mode overrides per member state. Learn more about GDPR Article 8 consent ages →
Belgium, Denmark, Estonia, Finland, Latvia, Portugal, Sweden
Austria, Bulgaria, Cyprus, Italy, Lithuania, Spain
Czech Republic, France, Greece, Slovenia
Croatia, Germany, Hungary, Ireland, Luxembourg, Malta, Netherlands, Poland, Romania, Slovakia
US. State-Level Laws
Beyond federal COPPA, states are passing their own child safety and age verification laws, each with different requirements and enforcement timelines.
Override resolution: Country/State → Group (EU/US) → Default → Global fallback. Set a group default, then override specific jurisdictions as needed.
What you get back
Frequently asked questions
How accurate is Tuteliq's age verification?
Document-based verification is the higher-assurance path, because the date of birth is read from check-digit-validated MRZ or barcode data rather than estimated. Biometric estimation is designed for the 13–25 band where regulatory thresholds cluster, and applies a conservative buffer biased toward the younger estimate, so borderline cases fail safe.
Do you support the UK Online Safety Act and EU DSA age assurance rules?
Yes. Tuteliq offers highly effective age assurance methods accepted by Ofcom (facial age estimation, document + liveness, digital ID) and produces the audit records required under the EU DSA Article 28 and the OSA children's safety duties.
Which age thresholds can I configure?
You can set jurisdiction-specific age thresholds for all 27 EU member states, 15 US states with youth privacy laws, the UK, Australia and other regions. Cascading rules let you enforce the strictest applicable minimum automatically.
Is user data retained after verification?
No. Document images and biometric templates are processed in memory and destroyed once the verification completes. Only the pass/fail outcome, age band and audit metadata are retained.
Which pricing tier includes age verification?
Age verification is included on the Assure plan ($499/mo) and above. Age verification costs 10 credits in Liveness Only mode and 20 credits in Complete mode (document + liveness), with volume discounts on Enterprise. Each completed verification is charged on its own mode, so if a liveness-only attempt fails and document fallback is enabled, the retry is charged separately (10 then 20). The Build plan does not include the /api/v1/verify endpoints.
Ready to verify?
Included on the Assure plan and above. Age verification costs 10 credits in Liveness Only mode and 20 credits in Complete mode (document + liveness).
Configure per-jurisdiction verification modes directly from your dashboard.