MyProof is a zero-knowledge identity verification engine for proving facts from government IDs without collecting the ID data. It helps teams verify age, identity, residency, nationality, and eligibility while personal data stays on the user's phone.
Frequently asked questions
What is MyProof?
MyProof is an identity verification engine built on zero-knowledge proofs. A customer scans their government ID on their own phone, and the phone produces a cryptographic proof of specific facts, such as being over 21 or living in a particular state. Your business receives only the proof. During verification, the ID itself and the personal data on it never leave the customer's phone.
How is this different from uploading a photo of an ID?
An ID upload hands you a copy of everything: name, address, birth date, document number. You then have to store and protect all of it. MyProof inverts that model. Verification happens on the customer's device, and you receive a cryptographic answer to the exact question you asked, with nothing extra to store or protect.
What can MyProof verify?
Age thresholds, state residency, document validity, nationality from passports, and other facts readable from government-issued IDs. Verification policies are compiled at session time, so what gets proven adapts to what your business needs for each transaction.
Do customers need to install an app?
No. On iPhone, verification opens instantly as an App Clip, a lightweight experience that runs without installing anything from the App Store. The customer scans a QR code, verifies, and is done in seconds.
Is any personal data stored on your servers during verification?
No. During verification, personal data never leaves the customer's device. Our servers see cryptographic commitments, proof results, and signatures. They never see names, birth dates, addresses, photos, or document numbers from the ID.
What patent protection does MyProof have?
The dynamic zero-knowledge policy engine at the core of MyProof is protected by an issued provisional patent. The engine compiles your verification policy at runtime and proves compliance inside the cryptographic proof itself.