19 services built on one verification and one sealed-record format. Take a single one, or compose several — the person is checked once, and every service afterwards works from that same verified identity.
The primitives everything else is built on. Prove who someone is, prove they are live, prove they are old enough — once.
Document authentication, MRZ parsing against ICAO 9303 check digits, and biometric liveness. The full identity check, in seconds, for platforms, marketplaces and communities.
Learn MoreAge assurance mapped jurisdiction by jurisdiction — UK Online Safety Act, EU DSA Article 28, German JMStV, Swiss FADP and US state law. The platform receives a boolean, not a date of birth.
Learn MoreA drop-in login widget for the moments that carry risk. The person confirms a verified ProntoID account and the platform receives a durable, platform-scoped reference — enough to attach an order or a ban to, not enough to identify anyone.
Learn MoreProves a person is live, real, and the same person as a prior reference — without your platform ever receiving their government ID. One engine for takedowns, check-in, account recovery and data-access requests.
Learn MoreScores an email address for risk in under 400ms. Filters disposable, breached and high-risk addresses before they ever reach the ID gate — so you pay for verifications worth running.
Learn MoreAgreements between identified parties, sealed at the moment they are made, and provable afterwards without depending on us.
Bilateral, identity-verified consent for content. Tag a subject, they approve or decline from their own verified account, and the release is sealed. Withdrawal is appended as a new instrument, never a silent deletion.
Learn MorePortable model releases for any platform. The subject consents once from a verified account; the platform receives a signed release rather than a scan of a passport.
Learn MoreContracts anchored to a verified identity rather than a mailbox. Each signature is bound to a completed identity check and the document is hashed, so the signer and the text are both fixed at signing time.
Learn MoreThe sealed record itself. Canonical JSON, a detached signature and an append-only ledger, producing a digest any third party can check with nothing but the public key.
Learn MoreWhere the identity itself becomes the key. Not a password that can be forwarded, and not a link that works for whoever holds it.
Every download sits behind a live ID check and a liveness match. Files are encrypted at rest and decrypted only after the recipient proves who they are, with single-use signed URLs and a full audit trail.
Learn MoreReplaces the password with the person. Sensitive emails, documents and assets open only for a confirmed identity, so a leaked credential is no longer a leaked file.
Learn MoreA precise gate placed only where the law requires one. Restrict a single page or section rather than fencing an entire platform, and keep the rest of the site open.
Learn MoreTurns a verified ProntoID into a service wallet. Bookings, memberships and passes attach to the identity, so a single scan confirms both who someone is and what they are entitled to.
Learn MoreWhat the verified person carries with them. The deposit does not mean the person loses access to their own identity.
The person's own verified identity, held on their device in the secure enclave. Present a fact about yourself — age, nationality, verified status — without exposing the underlying document.
Learn MoreLive credentials for models, photographers, founders and creators. Each badge resolves back to a verification that can be checked at the moment it is shown, rather than an image that can be copied.
Learn MoreConfirms that mandatory cover is in force — liability, site or activity insurance — without circulating policy documents. The checking party sees a status, not the policyholder's paperwork.
Learn MoreApplications where the value of a result depends entirely on every participant being a distinct, real person.
Mutual verification before meeting in person. Both parties confirm they are meeting who they think they are, without either one handing the other a copy of their ID.
Learn MoreForensic watermarking that binds a verified recipient to the copy they received. Where a file later surfaces elsewhere, the marking narrows the question of which copy it came from.
Learn MorePetitions where each signature is tied to a verified, distinct person, with optional residency checks against the address on the document. What is handed over is consensus, not a mailing list.
Learn MoreEvery service on this page runs through the same four stages. That is why a person verified for one is already verified for the rest, and why the output of one service is checkable by anyone holding the next.
The document is authenticated, the MRZ is parsed against ICAO 9303 check digits, and a live face is matched to the portrait.
The evidence is held by ProntoID as an independent controller, encrypted under per-record keys, and is never transmitted onward.
The relevant facts are serialised to RFC 8785 canonical JSON and signed. The same facts always produce the same bytes, and therefore the same digest.
The platform receives the narrowest claim it needs — verified, over 18, matches this prior verification — plus a digest it can check later.
Verifiable without us. Sealed records use a detached JWS signature over a P-256 key. Checking one requires the public key and a standard ECDSA implementation — nothing else, and no call to ProntoID. A record retained today stays provable to a third party years from now.
No. Each service is usable on its own and most platforms start with one — usually KYC or age verification. The services share a single verification and a single sealed-record format, so adding a second one later does not mean re-verifying the same people or running a second integration.
An opaque reference and a digest. The identity document, the biometric reference and the underlying evidence stay with ProntoID as an independent controller. Your platform holds enough to prove a verification happened, and not enough to be a meaningful target in a breach.
No. A completed verification is reusable across the ecosystem. A person who has been verified for a KYC check can consent through ProntoTag, sign through ProntoSigned or receive a file through ProntoDeliver without repeating the document capture.
Yes, for the sealed instruments. Records use RFC 8785 canonical JSON with a detached JWS signature over a P-256 key, so verification needs only the public key and a standard ECDSA implementation. A retained record stays checkable by a third party regardless of what happens to us.
That depends on the obligation and the jurisdiction, and it is worth a conversation rather than a self-service answer. Age assurance under the UK Online Safety Act, closed-user-group requirements under the German JMStV, and record-keeping under 18 U.S.C. § 2257 each pull in a different combination of these services.
Tell us what you are required to know about the people using your service, and we will show you the smallest thing you need to hold in order to prove it.
One verification · Independent custody · Verifiable without us