Prove the human.
Keep the privacy.
Age assurance, bot resistance, and verified accounts that never require you to store a passport scan, so you can meet the new online-safety laws without becoming the next identity breach.
What trust & safety teams are up against
New statutory duties, cheaper fake accounts, and a verification market that never proved identity in the first place.
Age-verification law arrived, and it is not optional
The UK Online Safety Act, Australia's youth social-media rules, the EU Digital Services Act, and a growing list of US state laws require platforms to know who is a minor. Face-estimation alone is being challenged; document checks create a honeypot of ID scans.
Bots are cheaper than users
Generative AI made fake accounts indistinguishable in text, image, and now video. CAPTCHA and phone verification no longer separate people from scripts.
Verified badges built on payment cards are not identity
A badge that proves someone has a credit card proves nothing about the person, and nothing about whether the same person is behind many accounts.
What goes live
The modules you can turn on in the current product, without a platform migration first.
Age assurance
Document-based age verification with configurable minimum and maximum age rules per flow or globally; age calculated from the document and validated against your rules.
Liveness and face match
Live selfie, anti-spoofing against photos, masks, and deepfakes; facemap persistence across sessions; configurable thresholds with a manual-review queue for edge cases.
Verified-account credential
Issue a “verified human” or “of age” credential the user holds; your platform checks the signature, not the document.
Geo and jurisdiction rules
IP-based geo-blocking, per-flow country overrides, restricted-jurisdiction enforcement.
Integration
Embeddable Web SDK widget, QR handoff to mobile, webhooks, GDPR user-deletion endpoints; production and sandbox environments.
The same deployment, on the trust layer
One human per account, provably
A key derived from a verified identity cannot be cloned into a second account without the person. Sybil resistance becomes a property of the credential, not a moderation heuristic.
Minimum disclosure by design
Zero-knowledge proofs let a user prove “of age” or “unique human in this region” without revealing name, date of birth, or document.
Portable verification
A user verified once can present the credential to another product or platform you run; no second capture, no second data store.
Content authenticity
Posts, uploads, and messages can be signed with the account's identity-bound key, giving you a verifiable origin for provenance and creator programs.
Where teams start
Each one runs on the modules above — pick the one that matches the quarter you are in.
- Age gating for youth-protection rules with a credential, not a stored ID scan
- Verified creator and marketplace-seller programs with revocable credentials
- Bot and Sybil resistance for sign-ups, referrals, and reward programs
- Signed content provenance for creator attribution and deepfake defense
- Account recovery backed by the identity key instead of email or SMS
What we build on, and what we claim
Open specifications, named without the version churn. Every status below is a different promise.
W3C Verifiable Credentials
NIST post-quantum standards
FIDO/WebAuthn
OpenID Connect
eIDAS
Data minimization and GDPR deletion endpoints built in.
Trust atplatform scale.
Meet the age-assurance deadline with a flow you configure in the dashboard, then give every verified user a credential that works across everything you build. Request a demo, or start in the sandbox.