AgeOnce is a privacy-first age verification API for B2B. Platforms receive a signed age threshold and Audit ID—not passport scans or face photos. Aligned with DSA, GDPR, and BIPA, with light reverification for returning users.
GDPR Compliant
BIPA & CCPA Ready
eIDAS 2.0 Aligned
AES-256 Encryption
New Users: Complete a secure identity check in under 30 seconds using AI-powered document analysis and liveness detection.
Returning Users: Instant re-authentication via biometric confirmation. No repeat ID uploads, no friction, just a secure status token.
Whether it's your first time or a quick return, we've removed every possible friction point.
AgeOnce stores only what's needed for compliance: anonymized verification receipts and audit IDs. No face images, no personal data. You get proof, and we keep nothing sensitive.
From 25+ U.S. states to the European Union, UK, and Australia, governments are strictly enforcing new laws that require platforms to prevent underage access to restricted content and services.
The legal landscape has fundamentally changed: regulatory frameworks are now shifting direct liability - and the risk of massive fines - onto platform operators.
Effective age validation (without degrading UX)
Strict data minimization (Zero-Knowledge processing)
Secure handling of identity information
Auditability and compliance readiness
AgeOnce is a privacy-first age verification API for B2B products. Redirect users to verify, validate a signed token server-side, and receive only an age threshold plus an Audit ID. No passport images or face photos are stored on your servers.
Built for custom apps, marketplaces, and streaming platforms. A typical integration takes a day or less: add a redirect URL, handle the callback, validate the token, and set a session flag.
SDK-ready (Node, Python, PHP, Go, Ruby, Java)
WordPress / WooCommerce Plugin
REST API
OAuth 2.0 & token validation
POST /api/oauth/validate HTTP/1.1
Status: 200 OK
{
"valid": true,
"payload": {
"age_verified": true,
"min_age": 18,
"verification_id": "uuid"
}
}
New York SAFE for Kids, Texas HB 1181, and California's Age-Appropriate Design Code push real age assurance in 2026. How to comply without storing IDs or losing sign-ups.
On 15 June 2026 the UK announced a social media ban for under-16s, with enforcement from Spring 2027. What it means for forums, WordPress sites, and conversion — and how to verify age without passport fatigue.
How online retailers can verify age for alcohol, tobacco, vape, and other restricted products without storing IDs or adding checkout friction.
The user is redirected to AgeOnce, grants camera permission, the system analyzes biometric data in real time, and returns a result: age confirmed or not.
No. Biometric data is processed in real time and not stored. We only store the fact of a successful verification.
Basic integration takes from 30 minutes to a few hours depending on your stack. WordPress takes 5–10 minutes with our ready-made plugin. Node.js, Python, or PHP usually takes 30–60 minutes. Custom integrations take several hours.
Yes. We minimize data collection and do not store biometric information, which aligns with GDPR data minimization principles.
Yes. The Free plan is free forever and includes up to 100 verifications per month.
By default, the age_token is valid for 10 minutes.
Each successful verification returns a Transaction ID (the same as verification_id in the JWT). Store this ID in your order, database, or CRM. In the Dashboard Audit Logs you can search by Transaction ID to see when and how the verification was completed, for compliance and support.