Age & Sale-Eligibility Verification

Hide date of birth and ID documents
Prove meets the age / eligibility to purchase

For age-restricted sales of alcohol, tobacco, or pharmaceuticals, prove only that a customer meets the age and eligibility to sell — without disclosing their birth date or ID document — at the point of sale or online, so you can meet age-verification obligations without retaining unnecessary personal data.

Retail & convenience · E-commerce · Alcohol, tobacco, pharmacy · Unmanned stores & vending 3 min read
🔔 Plan · Lemma Compliance →
01 · WHO IT'S FOR

For age-restricted sales teams

Verify age without taking a birth date or ID at every check — removing the storage that turns into a leakage surface.

  • Retail, convenience, and e-commerce handling age-restricted goods

  • Unmanned stores, vending, self-checkout where in-person checks are hard

  • Teams needing an evidence trail for age-verification obligations

02 · THE SHIFT

Hand over the source, or just the facts?

Change what reaches the AI, and the leakage risk goes with it.

Without Lemma
Hand over the original
name:
Taro Yamada
dob:
2006-04-12
address:
Tokyo…
id_type:
driver's license
purchase_item:
alcohol
↓ all of it goes to the AI / outside
With Lemma
Hand over just the facts
holder:
did:lemma:user-customer-002
issuer:
did:lemma:authority-jp-npa
jurisdiction:
JP
licenseType:
age-attestation
disclosed:
[age_20+]
hidden:
[name, dob, address, id_no]
attestation:
age >= 20
ZK verified:
✓ VALID
↓ only the necessary facts to the AI

Pass only a proof that the customer "meets the age/eligibility to sell to." The birth date and ID are not disclosed. From issuer-signed attributes (public ID or eKYC), only predicate satisfaction (e.g. "20+") is shown. Stores, e-commerce, and auditors verify without seeing the contents.

(A lawful age-verification process is assumed; issuer and retention design are handled separately.)

See the technical details ↗
03 · HOW TO CHOOSE

Choose on three criteria.

Only work that needs all three at once — pass without exposing, independent verification, tamper-proof — is Lemma's domain.

Method Pass without exposing Independent verification Tamper-proof
Access control only△✗✗
Masking / anonymization△✗✗
Encryption only✓✗✗
Lemma (ZK proof)the only one with all 3 ✓ ✓ ✓
04 · HOW IT WORKS

What's next

We enter through AI-adoption and data-governance support and a PoC, and stay alongside you through to operations.

  1. A 30-minute review — identify checks where document-storage burden / leakage surface concentrates.
  2. Narrow to 1–2 decisions to prove — e.g. "20+," "eligible to sell." Not the birth date.
  3. Design issuer and retention — connection to public ID / eKYC issuers, retention/renewal (with legal).
  4. Prove one path via a (quote-based) PoC.
  5. Hands-on support from rollout through operations — existing plan tiers (Civic / Critical / Compliance) serve only as a cost reference; setup and pricing are designed together.

Tell us the one path with the heaviest ID-storage burden, in the first 30 minutes. No disclosure of sensitive data required.

05 · RELATED

Related

Still have questions? See the FAQ →

The bigger picture

The bigger picture this use case belongs to.

We map use scenarios across industries and workflows by the four axes.

See use scenarios for Regulatory Attribute in Solutions →

TRY LEMMA

Run it yourself.

No sales call needed — start hands-on with Lemma's products.

Try Seal → Trust402 reference implementation →
Learn how it works — Regulatory Attribute Proof →