Decentralized PII Storage
Decentralized, customer-held PII storage. No honeypot to breach.
"Decentralized, customer-held key" means one thing: your customers' identity data is encrypted, split across a distributed network, and unlockable only with a key the person being verified holds. There's no master key, not even Zyphe's. You keep the verification result and the audit trail; you never hold the raw PII a breach could expose.
Trusted by those who trust no one.
“Zyphe has made a big difference in how we approach attendee verification and data security. With decentralized storage for greater privacy, AI-driven identity verification for global check-ins, and audit-ready KYC, we have managed to reduce how much PII we need to handle while having a better user experience. It is easier for us to comply with regulations like GDPR and CCPA.”
Security that comes from architecture, not promises
Distributed nodes each record is sharded across, so no single node holds a complete, readable copy.
Master keys. Zyphe cannot read, reconstruct, or hand over your customers' data on its own.
Threshold scheme: shards are stored so that a minimum number are needed to reassemble stored data, and the user unlocks with their face.
Comply with global data residency rules
Our decentralized platform ensures that all data is fully geo-located in the user's region for unrivaled compliance with global data residency requirements.
What "customer-held key" actually means
Your customers' data is encrypted, split into fragments, and reassembled only with a key the person being verified holds. Here is what that means in practice, and why it never costs you your audit trail.
The user holds the key, not you
The person being verified controls the key that unlocks their record. There is no master key and no back door, not even for Zyphe. We can't read the data, so we can't lose it, sell it, or surrender it in a breach.
Split across 60,000+ nodes
Every verified record is encrypted and sharded across a decentralized network. No single node holds a complete record, and a stolen fragment decrypts to nothing. There is no central database to steal.
You stay fully audit-ready
Each record is encrypted and split into shards, and a minimum threshold of shards, for instance 29 of 100, is needed to reassemble stored data. The user unlocks with their face. Zyphe cannot access the data, and you still hold the verification results, audit logs and proofs an examiner asks for.
Data stays in its home region
Records are geo-located to the user's region, so data-residency rules under GDPR, MiCA and local law are met by the architecture itself instead of manual, per-market configuration.
No central honeypot, by construction
Personal data is never assembled in one place. It is encrypted, sharded, and distributed across a global node network, so there is nothing for an attacker to steal and nothing for you to defend. Your servers stay clean, your liability list gets shorter, and your customers keep control of their own data, while your compliance team keeps a complete, examiner-ready trail.
Where data is stored, what is retained, and the audit status: the security and trust pageIntegrate in as little as 15 minutes
curl -X POST https://verify.zyphe.com/v1/login_sessions \
-H 'Authorization: Bearer <API_KEY>' \
-H 'Content-Type: application/json' \
-d '{"auth_type": "email"}'
Frequent Questions
It means the person being verified holds the key that unlocks their own identity record, and that record is encrypted and split across a distributed network rather than sitting in one database. Zyphe never holds a master key or a back door, so we cannot read, reconstruct, or expose your customers' personal data. You keep the verification result and a full audit trail; you never hold the raw PII.
No. Zyphe cannot access the user's data. The vault is unlocked with the user's face, through a passkey, so there is no key to mislay in the way a USB stick is mislaid. The 29-of-100 scheme is how shards are stored, not a way for Zyphe or a regulator to open a vault. You still hold the verification results, audit logs and proofs.
Your audit trail is always available to you, because it is not the vault. You keep the verification results, the audit logs and the proofs, exported as a complete, per-region, examiner-ready trail. You meet the same five-to-seven-year record-keeping standard regulators already expect, without keeping the central store that turns one intrusion into a mass breach.
No. Self-custody wallets fail closed: lose the key, lose the asset. Zyphe's threshold model is built so that authorized reconstruction never depends on a single key holder, which is exactly what makes it safe for regulated record-keeping. Customers control access to their data, but a lost key does not destroy the compliance record.
Each record is geo-located to the user's region and sharded across the node network, so data-residency requirements under GDPR, MiCA and local law are satisfied by the architecture. No single node, and no single region, holds a complete, readable copy.
Unlike traditional providers (Jumio, Onfido, Sumsub), Zyphe decentralizes identity storage, providing unmatched security, lower compliance overhead, and faster onboarding through reusable credentials and data ownership.
Zyphe offers robust Know Your Business (KYB) services, enabling quick and reliable verification of business legitimacy, ownership, and regulatory compliance.
KYC Readiness Score
Score how mature your Know Your Customer programme is across verification, automation, fraud defence and audit-readiness.Explore more Zyphe products
Decentralized KYC
agents on a substrate where users own their identity
Decentralized KYC verifies users with AI agents on a substrate where customers own their credentials. Users reuse identities across platforms; you never become the honeypot.
Learn more →Know Your Customer
Verify people without keeping their documents
Document and liveness verification against 4,000+ identity document versions from 213 countries and territories, with injection detection and sanctions, PEP and adverse media screening.
Learn more →KYC Passport
Onboard once, reuse everywhere
A verification the person carries with them, so a customer who has already been checked can be recognised by the next platform without uploading their documents again.
Learn more →