Consumer platforms

Verified human and age checks for dating and social apps

Selective disclosure separates the trust signal from the identity. The wallet proves the account holder is over 18, is a unique human, and lives in a given country, without giving up a name, a birth date or a document. You get better safety guarantees than an ID selfie and hold far less data.

The problem

What teams do today

Dating and social platforms are squeezed from two directions. Regulators want provable age assurance, and users want protection from bots, catfishing and duplicate accounts. Both usually get solved by demanding an ID selfie, which turns a consumer app into the custodian of an identity document database. It is hard to think of a more attractive breach target.

01
Provable age assurance without an ID document store
02
Duplicate and bot accounts get expensive, because uniqueness is cryptographic
03
Verification becomes a product feature instead of pure friction
How it works

Three steps with Authbound

  1. Step 01

    Verify at profile creation

    Run the check once when the profile is made and mark the account verified.

  2. Step 02

    Ask for proofs, not identity

    Typically age_over_18, a uniqueness proof, and residence country. No name, no birth date, no document.

  3. Step 03

    Make it a feature

    A verified badge and verified-only filters turn the check into something users want rather than an obstacle.

Rules in play

Online safety and age assurance rules including the UK Online Safety Act and DSA obligations, GDPR data minimisation

Live demo

We built Surepath, a company that does not exist, to show this running inside a finished product. The wallet flow in it is the real SDK.

Open the Surepath demo
Questions

What people ask

How can you prove uniqueness without identifying someone?
The wallet derives a pseudonymous identifier that is stable for your platform and cannot be linked to the same person elsewhere. You can tell two accounts are the same person on your service. You cannot tell who they are, and nobody can correlate them across platforms.
Does this satisfy age assurance regulation?
It gives you a signed, government-rooted proof of adulthood, which beats self-declaration and facial age estimation. Regulatory acceptance is still settling, so confirm against your target markets.
What do we store afterwards?
A boolean, a pseudonymous identifier and a timestamp. That is the whole record. There is no document and no identity to leak.

Built on Authbound Identity Verification. One API key covers every flow you add later.