Open source is the only way
Privacy systems that ask you to trust them have already failed. We publish everything so you never have to.
Trust through transparency
A closed-source privacy product is a contradiction. You are trusting that the company did what it said it did. That the encryption is real. That the data paths are actually absent. That the proofs are actually zero knowledge.
We do not ask for that trust. Our cryptographic libraries, verification and issuance services, mobile applications, SDKs, and the protocol specification are published at github.com/provii. Read the code. Run it yourself. Find a bug and tell us.
Everything.
Cryptographic core
Rust crates for zero knowledge proof generation and verification, Pedersen commitments, constant-time operations. Compiles to native and WASM.
Backend services
Verification and issuance services. Rust and TypeScript. Deployed on Cloudflare Workers.
Mobile applications
Native iOS (Swift) and Android (Kotlin) wallet apps. Shared Rust cryptographic core via UniFFI bindings. Hardware-backed storage integration.
Protocol specification
A standalone, implementation-independent spec. Wire formats, state machines, error codes. Anyone can build a compatible implementation.
Integration SDKs
Client and server libraries for multiple platforms and languages. Demo implementations covering every integration scenario.
Security documentation
Our ISMS documentation is published alongside the code. Threat models, risk registers, data processing records, security policies. Not behind a sales call.
SLSA Level 3 provenance
Every build artefact we release can be traced back to its exact source commit and the build environment that produced it. Signed with Sigstore. You do not need to trust that we built what we say we built. The provenance chain proves it.
CI pipelines use SHA-pinned dependencies. Automated licence compliance scanning. Automated vulnerability scanning. No surprises in the supply chain.
- Every release traced to exact source commit
- Sigstore-signed provenance attestations
- SHA-pinned CI dependencies
- Automated licence compliance checks
- Automated vulnerability scanning
Built for the community, with the community
Privacy infrastructure should not be proprietary. The people whose data is at stake deserve to understand the systems that handle it. Parents, educators, regulators, developers. They should all be able to look under the hood.
We publish a standalone protocol specification so that anyone can build a compatible implementation. We are not building a walled garden. We are building a standard that others can adopt, extend, and improve.
Data ownership
The credential belongs to the holder. It lives on their device, protected by their biometrics or passcode. We cannot access it, revoke it, or monitor how it is used. If the holder deletes the app, the data is gone. Permanently. There is no cloud backup, no admin panel, no recovery mechanism.
This is not a limitation. It is the design. When we say the user owns their data, we mean the user is the only one who has it.
What we believe
Privacy is architectural
Not a toggle, not a policy, not a promise. When data paths for personal information do not exist in the system, there is nothing to breach, subpoena, or sell.
Surveillance is not safety
You cannot make children safer by building databases of their online activity. You make them safer by building systems where that data never exists.
Regulation needs better tools
Age verification mandates are coming. The question is whether compliance requires mass surveillance or whether cryptography offers a better path. The answer is obvious.
Openness is non-negotiable
Closed-source privacy systems ask you to take their word for it. We think that is an unreasonable ask. If you cannot read the code, you cannot verify the claim.
Get involved
Report bugs, review cryptography, suggest improvements, or build something new on top of the protocol. We are building this for everyone, and we welcome contributions from anyone who shares that goal.