Age verification, rebuilt around privacy

Prove your age.
Not your identity.

Ekuproof lets someone prove they meet an age requirement, at a door, at a till, or online, without handing over their name, date of birth, address or ID photo. Verify once. Present it anywhere.

No credit card. Your first location is ready to verify customers in minutes.

One verification. Nothing else disclosed.

The same three steps whether it's a bouncer at the door or a checkout online.

  1. 1

    Verify once, in the app

    A consumer proves their age a single time. Ekuproof never keeps more than it needs, and nothing is re-checked on every visit.

  2. 2

    Present a code, not your ID

    A short-lived, single-use code stands in for the identity document, whether at a venue's scanner or through an API call from a till.

  3. 3

    Get a minimal result

    The venue or platform sees a pass/fail result for the age requirement that matters to them. Nothing more.

Scanning…
✓
18+ VERIFIED
No name. No date of birth. No photo.

Your identity stays yours.

Verify your age once with a recognised identity check, and Ekuproof issues a reusable, revocable credential, not a copy of your passport sitting on someone else's server. Every venue you show it to gets a yes/no answer, never your details.

From one pub to a whole estate.

The same account model scales from a single independent venue to a multi-location business, without your staff needing a different login for each site.

A pub, club or shop that just needs a fast, reliable door check.

  • Register in minutes, get a printable QR straight away
  • Staff sign in with a PIN. No accounts to manage
  • Full scan history for your own licensing records

Retail chains and hospitality groups running several sites under one organisation.

  • One dashboard for every location's staff and activity
  • Add a new location and its QR code any time
  • Staff move between sites on the account they already have

Teams whose staff work shifts across several client venues.

  • One account per employee, assigned to the venues they cover
  • Scanning a venue's code activates it for that shift. Nothing more
  • Access to a client venue is revoked the moment a contract ends
Register your business

Bring it to your existing POS.

Large retailers don't need to put every checkout operator on a separate app. Integrate Ekuproof's verification API directly into the systems you already run.

  • ✓
    One endpointSend a scanned code and the age requirement that applies. Get a pass/fail back.
  • ✓
    Scoped API credentialsYour own key, independent of any staff login: issued, rotated and revoked by your account admin.
POST /v1/verifications/verify
Authorization: Bearer op_live_••••••••

{
  "presentationToken": "eyJhbGciOi...",
  "requirement": { "minimumAge": 18 }
}

→ 200 OK
{
  "verified": true,
  "result": "pass"
}

Minimal disclosure isn't a feature. It's the design.

Ekuproof is built so that the party asking "are they old enough?" only ever learns the answer to that question, not who's asking and not anything else about them.

  • ✓
    No identity documents shown to venuesA venue or till sees a result, never a name, date of birth, address or photo.
  • ✓
    Short-lived, single-use codesA presentation code can't be replayed or reused once it's been checked.
  • ✓
    Revocable, not permanentA credential, a device or an API key can be revoked immediately: access stops the moment it should.
  • ✓
    Separated by designOne organisation's locations, staff and data are never reachable from another's.
  • ✓
    Built to UK DIATF requirements Designed to the standards a UK DIATF-accredited Conformity Assessment Body assesses against, ahead of formal certification.
Namenot shared
Date of birthnot shared
Addressnot shared
ID photonot shared
Age requirement met✓ Yes

Ready to see it working?

Register your business and your first location is ready to verify customers today.

Get in touch

Questions, support, anything else — we read every message.

Talk to us about integration

Tell us about your POS or platform and we'll follow up about API access.