A regulated reviewer checks you, once.
Add your details and a photo of your ID. A KYC reviewer at a registered bank compares them and approves. The approval is recorded on Ethereum as a salted hash, never your data.
Get verified once by a regulated reviewer. Then prove what a hotel, bank or venue needs with a QR code that works once, and keep everything else sealed.
Add your details and a photo of your ID. A KYC reviewer at a registered bank compares them and approves. The approval is recorded on Ethereum as a salted hash, never your data.
Add your details and a photo of your ID. A KYC reviewer at a registered bank compares them and approves. The approval is recorded on Ethereum as a salted hash, never your data.
Only registered organisations appear. Your location comes from your connection and theirs from their registration, so the right rule applies without you choosing a country.
Verity signs a credential with ML-DSA-87 inside AWS KMS. It holds only the facts the law requires plus what you add, and expires after the time you choose.
The verifier scans it from their account. The signature is checked on the server, the code is spent, and the check appears in your history.
Add your details once. For every hotel, bank or venue you choose what to show, see the law behind it, and get a code that works once.
Create an accountSign in as a registered organisation, scan the code and receive a signed answer with only the approved facts. Every check is logged.
Verifier sign-inEach fact becomes a salted hash inside a signed credential. What you don’t reveal stays unreadable, even to the verifier.
Proofs are signed with ML-DSA-87 (NIST FIPS 204) by a key that lives inside AWS KMS and can’t be exported.
India, the EU, the US and the UAE each have cited rules. If two laws conflict, Verity shares nothing and says why.
Free to start. You approve every proof, and every code works once.