Ask for the predicate
The site asks for over 18, over 21, or another eligibility claim. It does not ask for a birth date.
Verify the gate without becoming the next breach headline.
PROOFGATE proves over 18 or eligible without the host touching a name, DOB, ID number, or image. The verifier checks the wallet presentation and returns a yes/no signal plus an audit token.
zero PII stored
trusted issuer checks
one unit per verify
Wallet predicate
age_over_18
Verifier proof
issuer + nonce + holder
Host signal
pass + audit token
SPRIME surface
One SPRIME, starting with the gate.
SPRIME.io becomes the first public face of the privacy verifier. Sprime.us stays useful while the shared backend hardens. PROOFGATE is the first narrow product in that unified surface.
The rule is simple: prove the claim, bill the verification, and keep identity material out of the host system.
Current surface
2026
SPRIME
Shared trust layer, billing, audit tokens, and verifier primitives.
unifying
PROOFGATE
Age and eligibility acceptance for hosts that do not want ID storage.
beachhead
Sprime.us
Existing tools and developer surface remain reachable during the transition.
stable
The acceptance layer. Not an ID warehouse.
PROOFGATE sits between a host site and a wallet presentation. It validates issuer signature, holder binding, nonce, and the requested predicate. The host gets the answer it needs and none of the raw identity material.
Verify the presentation
The verifier checks the wallet presentation against the server nonce, audience, issuer key, and disclosure binding.
Return the signal
The host receives pass or fail plus a non-reversible audit token. No identity record is stored.
Start where privacy pain is obvious.
The first customers should already feel the cost of storing IDs. PROOFGATE is strongest where the site needs an eligibility answer, not another database of sensitive documents.
Age-gated ecommerce
Vape, alcohol, and regulated retail teams need a durable age signal without making checkout feel like a document upload.
Sweepstakes and gaming
Hosts can gate eligibility and keep a zero-PII audit token for disputes, reporting, and operator review.
Dating and community access
Platforms can reduce underage access risk without asking every user to hand over identity records to the platform.
Built for wallet credentials, not ID uploads.
The first shipped path is SD-JWT VC. mDL and ISO 18013 acceptance follows through a maintained reader library. EUDI-ready is the expansion lane, not a claim of full coverage today.
SD-JWT VC
Selective disclosure lets a wallet reveal only the required predicate while the verifier checks cryptographic binding.
mDL / ISO 18013
Mobile driver license support is a fast-follow path. It uses a maintained library, not hand-rolled COSE or CBOR.
EUDI-ready lane
European wallets make standards-based verifier integrations more valuable as adoption grows through 2026 and 2027.
Revenue from customer one.
Metered billing keeps the product narrow: one verification, one unit. Volume customers carry a monthly minimum so the service is not a free compliance experiment.
Design partner
$250 / month minimum
For early age-gated ecommerce, sweepstakes, gaming, and dating pilots.
- Drop-in button
- Sandbox verifier
- Weekly implementation review
Metered production
$0.05 / verify
Per-verification usage with a monthly minimum and audit-token exports.
- Production verifier
- Issuer allowlist controls
- Zero-PII audit log
Volume
Custom
For higher-throughput platforms with issuer policy, reporting, and onboarding needs.
- Higher rate limits
- Contracted support
- Private integration review
Demo the host-side result.
This is a UI simulation of the drop-in result shape. It does not collect personal data and it does not call the cryptographic verifier from this marketing page.
Bring one real gate.
Best fit now: vape, alcohol, firearms ecommerce, online sweepstakes or gaming, and dating platforms that want an age-assurance signal without storing identity documents.