Privy

• Name: Privy
• URL: https://www.privy.io/
• Category: wallet-infrastructure company / embedded-wallet and identity operator / hosted signer workflow platform
• Tags: ethereum-ecosystem solana-ecosystem bitcoin-ecosystem
• Summary: Privy belongs as an entity note, not a protocol note. The useful cut is that a named company operates an app-owned wallet and identity control plane spanning onboarding, identity linking, embedded-wallet creation, session issuance, recovery, policy controls, and wallet automation. The practical leverage lives in the hosted auth-and-signing workflow rather than in any standalone account abstraction or key-sharding primitive.
• What it does:
  • Provides embedded-wallet infrastructure for onboarding users with email, SMS, social login, passkeys, or wallets
  • Offers key-management and signing infrastructure for fleets of programmable wallets
  • Exposes policy controls, approver quorums, transaction limits, allowlists / blocklists, webhooks, indexing, and user-management features
  • Supports multichain wallet use cases across EVM, Solana, Bitcoin, and other ecosystems mentioned in official materials
  • Packages identity, session, wallet, and policy workflow into a broad developer platform rather than only a narrow wallet SDK
• Key claims:
  • The homepage says Privy powers the complete wallet stack, from key management to user onboarding
  • Official materials describe hardware-isolated TEEs and distributed key sharding as core security primitives
  • Product pages emphasize TEE-enforced policy controls, approver quorums, transaction limits, allowlists / blocklists, and webhooks / indexing
  • Security materials describe cryptographically verifiable self-custody, short-lived verified sessions, regular third-party audits, and an active bug bounty program
  • Current site materials also note that Privy is now a Stripe company, which makes the operator and distribution boundary more legible rather than less important
• Whitepaper: No classic whitepaper or litepaper was found during this pass. The strongest primary materials were the homepage, product / security pages, and docs portal; snapshots were saved in ../whitepapers/privy-primary-sources-2026-04-22.md.
• Sources:
  • https://www.privy.io/
  • https://docs.privy.io/
  • https://www.privy.io/keys
  • https://www.privy.io/security

Internal linkages

• Alias / prior project-layer entry: privy.
• Best adjacent reads: turnkey, coinbase, and safe.
• Reusable lens: when a team sells embedded wallets, the real leverage often sits in identity linking, session issuance, recovery, approval policy, and which adjacent rails the company makes easiest to bolt on.

Protocol / company boundary

• There is no especially useful standalone Privy protocol boundary doing separate analytical work here.
• The practical dependency is the company-run auth, session, recovery, policy, and embedded-wallet workflow shell rather than a neutral lower-layer primitive.
• Keep privy only as an alias so legacy links keep resolving without pretending Privy is a protocol peer to more autonomous onchain systems.

Control surface

• Practical leverage sits in identity linking, session issuance, recovery workflow, approval policy, webhook visibility, user-management boundaries, and which wallet or payment actions Privy makes easiest to automate.

• The sticky dependency is the hosted auth, policy, and signer workflow around the wallets, not only the TEE-and-sharding story.

• Read Privy as a company-run signer-and-identity control plane, not as the durable account substrate itself.

• Last reviewed: 2026-08-10 UTC