Verify once.Stay private.
Your proof moves, your data stays encrypted.
Zama FHE anchors the proof. Crivacy Credential carries no personal data. Identity Verified - you stay in control.
- Zero-knowledge proof
- No personal data stored
- Self-custodial identity
- Auditable on-chain

“One KYC to rule them all.”
How Crivacy Works
Three steps between you and a reusable, encrypted identity you own.
- Step 01
Verify Once
Complete KYC once through our real verification pipeline.
- Step 02
Encrypted On-Chain
Your credential is written on-chain with FHE, keyed to your wallet. No PII.
- Step 03
Use Everywhere
Any firm you approve reads a yes or no. Your data stays yours.
Encrypted On-Chain
Level, score, and flags stored as FHE ciphertext.
Reusable Credential
Verify once, reuse at any Crivacy-integrated firm.
User-Owned
Keyed to your wallet. Only you can decrypt your data.
You Control Access
Grant or revoke each firm's access anytime.
Firms Read Yes/No
A granted firm decrypts only the eligibility verdict.
No PII On-Chain
Documents never touch the chain. Ever.
Crivacy, Live On-Chain
Community signals on one side. Encrypted credential activity flowing live on the other. Both in real time.
Network at a Glance
Built with FHE
Every credential is a confidential record on the CrivacyKYC contract. The sensitive fields are encrypted with FHE, keyed to the user's wallet, decryptable only by the owner and the firms they allow.
- FHE-encrypted credential fields
- Issued by operator, owned by holder
- Per-firm access grants over the verdict
@@ -1,12 +1,16 @@- 11
struct Credential { - 22
bytes32 userRefHash; - 33
bytes32 proofHash; - 4
uint8 level; - 5
bool identityVerified; - 4
euint8 level; // encrypted - 5
ebool identityVerified; // encrypted - 6
ebool eligible; // encrypted verdict - 67
} - 78
- 89
function grantAccess(address user, address firm) external { - 10
FHE.allow(_verdict(user), firm); // firm reads yes/no only - 911
}
Q1 2026
Q1 2026
Production on Sepolia
ShippedCrivacyKYC + soulbound NFT contracts live. Real KYC pipeline issuing encrypted credentials.
Q2 2026
Q2 2026
Open SDK Release
Shipped@crivacy-fhe/credential + adapter-didit + js-sdk. Any firm can issue and verify confidentially.
Q3 2026
Q3 2026
Investment Round & Growth
ActiveScaling the team and partner integrations. Onboarding relying firms onto the encrypted credential layer.
Q4 2026
Q4 2026
Multi-Chain Support
PlannedExtending the confidential credential beyond Sepolia to additional FHE-capable and EVM networks.
2027
2027
Global Compliance Coverage
PlannedBroader KYC vendor adapters and jurisdiction coverage, so one encrypted proof works worldwide.
Start verifying. Stop sharing.
One proof to rule them all. Encrypted with FHE, kept by you.


