Browser extension
Approve it in the browser. Reveal only what you tick.
Most verification still happens on someone else's page — a hosted form, an upload widget, a wait. The IDNTT extension moves that moment into your browser, where you can see exactly what is being asked for and exactly what you are handing over before anything is sent.
Coming at launch
One click, in context
A site requests a claim, the extension raises a prompt, you approve or deny. No redirect to a third-party verifier, no new account, no re-upload.
Claim-by-claim disclosure
Every request is itemised. Tick “unique human” and “over 18” and leave your name, birthdate and documents untouched — the site receives a proof, not a copy of your file.
Keys stay in the browser
Your encrypted pack and its keys live in local extension storage. Requests are signed on-device; plaintext never reaches our servers because it never leaves your machine.
A flow you already know
If you have ever approved a transaction in a crypto wallet, the pattern is familiar — an explicit prompt, a clear diff of what is being shared, and a deny button that costs you nothing.
Why an extension rather than a hosted page
A hosted verification page has to receive your documents to check them. That is the whole architecture: you upload, they inspect, they retain. Every additional site that does this is another copy of your identity sitting in another company’s database, and another entry in someone’s future breach notification.
An extension inverts it. The checking has already happened once, when you built your pack. From then on the site is not asking for your documents — it is asking whether a claim about you holds. The extension answers that question with a zero-knowledge proof and nothing else crosses the wire.
What a request looks like
The prompt always shows two lists: what the site will receive, and what is being withheld. Nothing is shared implicitly and nothing is remembered on your behalf — a site that asked for age verification last month has to ask again, and you can answer differently.
Denying a request is a first-class action. The extension sends a refusal, not a partial disclosure, and the site is told only that the request was not granted.
Planned browser support
Chromium-based browsers first — Chrome, Edge, Brave and Arc — followed by Firefox and Safari. Join the waitlist and we will tell you which one ships first.
Want the extension first? Say so on the waitlist.
Verify once. Reused on your terms. No data we can read.