Ask for the predicate
The site asks for over 18, over 21, or another eligibility claim. It does not ask for a birth date.
PROOFGATE proves over 18 or eligible without the host touching a name, DOB, ID number, or image. It runs as a native browser prompt in Chrome 141 and Safari 26 (the W3C Digital Credentials API), so there is no app install and no redirect. The verifier checks the wallet presentation and returns a yes/no signal plus an audit token.
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.
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.
The site asks for over 18, over 21, or another eligibility claim. It does not ask for a birth date.
The wallet returns the presentation over OpenID4VP through the browser Digital Credentials API. The verifier checks it against the server nonce, audience, issuer key, and disclosure binding.
The host receives pass or fail plus a non-reversible audit token. No identity record is stored.
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.
Teams selling age-gated goods need a durable age signal without making checkout feel like a document upload.
Hosts can gate participation and keep a zero-PII audit token for disputes, reporting, and operator review.
Platforms can reduce underage access risk without asking every user to hand over identity records.
The shipped path is SD-JWT VC, presented over OpenID4VP through the browser Digital Credentials API. That is the remote, online flow, distinct from in-person proximity checks. mDL acceptance is the fast-follow. EUDI wallets are the expansion lane as adoption grows through 2026 and 2027, not a claim of full coverage today.
Selective disclosure lets a wallet reveal only the required predicate while the verifier checks cryptographic binding.
The verifier runs through the W3C Digital Credentials API, enabled by default in Chrome 141 and Safari 26. The wallet prompt is native to the browser, so there is no app install and no redirect.
Online mobile driver license acceptance is the fast-follow path, using the 18013-7 remote profile through a maintained reader library, not hand-rolled COSE or CBOR. Proximity (18013-5) is a separate in-person flow.
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.
For regulated retail and age-gated platform pilots.
Pilot pricing for design partners. Final production rates depend on issuer coverage, volume, and retention needs.
For higher-throughput platforms with issuer policy, reporting, and onboarding needs.
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.
Best fit now: regulated retail and age-gated platforms that want an age-assurance signal without storing identity documents.