Privy is built for verifiable security, using modern cryptographic primitives and battle-tested infrastructure to ensure there is no single point of failure.
Our team brings deep experience to security. We establish security requirements hand-in-hand with product requirements.
Accounts and counting
Processed monthly
Monthly signatures
Signature time
Privy’s security model is built from first principles and grounded in defense in depth. From TEEs to key sharding and programmable controls, every layer is designed to minimize risk and enforce secure access across the stack.
Cryptographically verifiable self-custody
All signing operations occur inside isolated, hardware-backed environments (TEEs). Enclave memory is inaccessible to Privy and the host, with cryptographic attestation ensuring code and data integrity at runtime.
Key sharding to improve security and trust
Private keys are split using Shamir’s Secret Sharing (SSS) — a more battle-tested scheme than TSS-based MPC. Shares are stored across isolated boundaries and only recombined inside the enclave, eliminating single points of compromise.
Authentication gates access to signing and keys
Signing is tied to short-lived, verified user sessions. Tokens expire quickly and cannot be reused, ensuring keys can only be accessed in the correct user context.
Programmable wallets, not static keypairs
Privy’s APIs expose fine-grained, provable controls over key usage and access. Define policy rules per user, including biometrics, asset limits, and trusted devices – all cryptographically attested at runtime.
As a Stripe company, Privy follows rigorous internal standards and controls—spanning production systems, key access, and developer workflows to ensure end-to-end integrity.
We monitor all production systems with real-time alerting, tamper-proof logs, and ongoing third-party review. Privy runs an active bug bounty and undergoes quarterly independent audits.
We enforce least-access across hardened infrastructure: standing permissions are disallowed, credentials are time-bound, duties are segregated, and all activity is fully auditable, even internally.
Cure 53
February 2023
Status: Complete
Zellic
June 2023
Status: Complete
SwordBytes
December 2023
Status: Complete
Doyensec
February 2024
Status: Complete
SOC 2 Type II
December 2024
Status: Complete
Hackerone
Bug Bounty Program
Status: Active
