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 verifies age or eligibility without asking your site to store a name, date of birth, ID number, or document image. The verifier checks a wallet presentation and returns the answer your gate needs: pass or fail, plus a non-reversible audit token.
Most gated flows only need to know whether a user is old enough or eligible. PROOFGATE checks the credential presentation and keeps raw identity material out of your host system.
Your team receives a narrow result for access decisions and a minimal audit token for review. The user is not pushed through another document-upload funnel.
PROOFGATE sits between your site and a wallet presentation. It validates the requested claim and returns the result your gate needs. Your system does not become an ID warehouse.
The site asks for over 18, over 21, or another eligibility claim. It does not ask for a birth date.
The wallet returns a credential presentation through a supported browser flow. The verifier checks the nonce, audience, issuer key, and disclosure binding.
The host receives pass or fail plus a non-reversible audit token. No identity record is stored.
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.
PROOFGATE is designed for selective disclosure: the wallet presents the claim needed for the gate, and the verifier checks the cryptographic proof. Credential and issuer coverage is reviewed during pilot setup.
Selective disclosure lets a wallet reveal only the required predicate while the verifier checks cryptographic binding.
Where supported, the verification prompt can run through the browser Digital Credentials API. The goal is a direct wallet flow, not another hosted document upload.
Mobile driver license support depends on issuer, wallet, and browser availability. Pilot scope should define which credential types are accepted before production traffic.
Each completed verification is one unit. Monthly minimums keep pilots serious while giving teams room to test the flow before a larger rollout.
For regulated retail and age-gated platform pilots.
Pilot pricing for teams ready to test a real gate. Final production rates depend on issuer coverage, volume, and audit 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. To run the real flow against the live verifier, open the live sandbox.
Best fit now: regulated retail, eligibility platforms, and age-gated communities that want an age-assurance signal without storing identity documents.