Age & Sale-Eligibility Verification
For age-restricted sales, prove only "meets the age/eligibility to sell" — without disclosing the birth date or ID document — at POS or online.
Who this is for.
For those selling products gated by age or eligibility — alcohol, tobacco, pharmacy. Taking a birth date or ID at every check makes that storage a leakage surface. "Verified" and "handed over the birth date" are not the same.
-
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
Hand over the source, or just the facts?
Change what reaches the AI, and the leakage risk goes with it.
- name:
- Taro Yamada
- dob:
- 2006-04-12
- address:
- Tokyo…
- id_type:
- driver's license
- purchase_item:
- alcohol
- 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
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.)
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 | ✓ | ✓ | ✓ |
What's next
We enter through AI-adoption and data-governance support and a PoC, and stay alongside you through to operations.
- A 30-minute review — identify checks where document-storage burden / leakage surface concentrates.
- Narrow to 1–2 decisions to prove — e.g. "20+," "eligible to sell." Not the birth date.
- Design issuer and retention — connection to public ID / eKYC issuers, retention/renewal (with legal).
- Prove one path via a (quote-based) PoC.
- 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.
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.