Terms of Use
Last updated: September 28, 2026
Draft for legal review. PureProof is in development. The operator's legal identity, contact details, governing law, launch markets, and product-specific terms must be confirmed before publication as final. This draft is not legal advice.
1. Agreement
These Terms of Use govern your access to and use of the PureProof applications and related services. By using an application or service, you agree to these terms and any product-specific notice presented to you. If you do not agree, do not use the application.
2. Permitted use
You may use PureProof only for lawful identity or age-verification purposes supported by the product. You must provide accurate information and use only your own identity information. You must not impersonate another person, bypass verification, interfere with security controls, or misuse a verification result.
3. Self-custody and access recovery
PureProof is designed to keep control of wallet credentials with the user. You are entirely responsible for securing your device, PINs, passwords, recovery material, holder keys, and any seed phrase or equivalent credential made available by a future product. Do not share them with anyone.
Because PureProof does not store your wallet passwords, private keys, or seed phrases, account recovery may be mathematically and technically impossible if you lose the required device or access credentials. PureProof cannot reconstruct, reset, or recover keys that it does not possess. You may permanently lose access to credentials or proofs stored on your device.
4. Zero-knowledge and verification disclosures
Where a product uses a zero-knowledge proof, the proof is intended to show that a statement is true, such as "the user is over 21," without disclosing the underlying attribute, such as the user's birthdate, to the verifier. The exact data flow depends on the product and issuer. A zero-knowledge design does not make every part of the service anonymous or eliminate all technical metadata.
PureProof does not promise that a proof, credential, issuer, relying party, cryptographic library, validator network, revocation system, public ledger, circuit, or other protocol component will be uninterrupted, error-free, secure, or resistant to every present or future attack. Bugs, implementation errors, protocol changes, exploits, and mathematical or operational vulnerabilities may affect availability or correctness.
5. Verification results and identity parties
A verification result or digital proof is a technical signal based on the information and checks available at the time. It is not a government-issued identity document, a guarantee that information is correct, or a promise that every business or authority will accept it. A relying business remains responsible for its own eligibility decisions and legal obligations.
Depending on the flow, an issuer may create a credential, you may hold and present it, and a relying party may request or use a verification result. PureProof does not guarantee an issuer's source data or a relying party's use of a result. A relying party must not use a result beyond the purpose disclosed to you or applicable law.
6. Prohibited conduct
You must not reverse-engineer, copy, or attempt to extract PureProof's cryptographic circuits or security controls; forge, replay, alter, or fraudulently present a cryptographic proof or credential; probe or disrupt issuer, verifier, wallet, API, or validator infrastructure; distribute malware or malicious code through QR generation, credential presentation, or any other product feature; or use the service to impersonate another person.
7. Device, biometric, and hardware security
Supported applications may rely on operating-system security features such as Apple's Secure Enclave, Android Keystore, Face ID, Touch ID, or device biometrics. Biometric matching is intended to occur within the device operating system or hardware security boundary. PureProof does not receive biometric templates from those operating-system prompts. Device security, however, depends on your device, operating system, configuration, and enrolled users.
8. Relying-party responsibility
PureProof cryptographically validates a presentation or verification signal at the time of scanning using the configured issuer, holder, status, expiry, and replay checks. That validation does not make PureProof responsible for a relying party's products, services, access decision, legal obligations, staff conduct, or any real-world misconduct or false claim by a bad actor. Relying parties must independently determine whether and how to accept a result and must use it only for the disclosed purpose.
9. Availability, termination, and updates
PureProof is under development. Features may change, be unavailable, or be discontinued. We may suspend access when reasonably necessary to protect users, the service, or the rights of others, or to meet legal requirements. Updated terms will identify their effective date.
We may stop providing software updates, hosted services, APIs, or verification access. In a self-custodial design, we cannot delete a wallet from your device or revoke private keys that we do not possess. Stopping a service does not guarantee continued access to locally held credentials or proofs.
10. Privacy and sensitive information
The Privacy Policy explains the current website's limited data context and planned service data practices. Product flows will provide additional notices before collecting identity documents, face data, biometric information, or other sensitive information.
11. Intellectual property
PureProof's applications, website, branding, and original content are owned by or licensed to the operator. These terms grant you permission to use the service as intended; they do not transfer ownership or other intellectual-property rights.
12. Contact
The operator's legal name and working contact details must be published here before these terms become final. Questions about use of the service should be directed through the support contact provided in the application.
These Terms of Use supplement the Terms and Conditions for the public website. If the documents conflict, the applicable product-specific notice will identify which terms control.