Private identity proof

Prove the fact. Keep the document private.

LEO Identity lets a person prove eligibility, age, income, or a signed credential without sending the raw document to the company asking for verification.

Run the demoSee the flow
SimpleOne proof, one result.
PrivateRaw fields stay in the vault.
VerifiableSignatures and receipts are checked in browser.
LEO.IDENTITY / RECEIPTNo raw document
Company seesAge is 18 or older
HiddenExact age, income, and document file
IssuerCredential signature verified
ZKF receipt5 verification nodes signed the proof hash
Trust without over-collection.

The company gets the answer it needs, not the private file behind it.

Live product demo

A cleaner flow investors understand in seconds.

Edit the private identity, choose one claim, then generate and verify a proof. The demo uses browser cryptography, signed credentials, SHA-256 fingerprints, and a ZKF-style verification receipt.

Ready. Crypto starts when you run the demo.
LEO Identity · Kadropic Labs
1

Private vault

This is the data the user controls. It is used locally to create a proof.

2

Choose the proof

The company receives only this claim and the cryptographic verification result.

Credential fingerprintCreated after you run the demo.
3

Generate and verify

One button creates a signed proof, anchors it to five ZKF verification nodes, and verifies what the company can trust.

Waiting for a proof

Press “Run proof” to create and verify the private claim.

View proof packet
Company can seeNo proof verified yet.
Company cannot seeExact age, exact income, private identity fields, and the original document.
ZKF verification nodes
N1
N2
N3
N4
N5
No receipt yet.
How it works

Three layers. One simple user experience.

LEO Identity keeps the investor story short: a private vault creates a signed claim, the proof is fingerprinted, and a ZKF-style receipt makes tampering visible.

Private vault

The user starts with raw data locally. The proof packet contains commitments and claims, not the underlying document.

Signed proof

The browser uses ECDSA signatures and SHA-256 fingerprints so the verifier can detect changes.

ZKF receipt

Five independent verification nodes sign the proof hash. A quorum is required before the result is accepted.

Investor view

The product is trust without over-collection.

Hiring, housing, lending, education, and access control all need verified facts. LEO Identity turns sensitive documents into small, checkable answers.

What the demo proves

It shows a clear flow: private data enters once, a claim is generated, and the company verifies a result without receiving the raw fields.

  • Age eligibility without exposing exact age.
  • Income threshold without exposing exact income.
  • Credential verification without sending the document file.

Why it matters

The business value is straightforward: companies reduce sensitive data exposure while users keep control over what they reveal.

  • Less data collection.
  • Faster trust decisions.
  • A product story that can be demonstrated live.