Private payments. Non-custodial.
Send, receive, and swap USDC and USDT privately with a signing key split into three independent shards.
Why choose Privatum for private self-custody?
A 2-of-3 wallet architecture built for private stablecoin payments, graceful recovery, and open developer tooling.
Single-Key Hot Wallet
Stores the complete private key in one browser or device, so one compromise can authorize every transaction.
Hardware Wallet
Improves offline key isolation but adds hardware cost, firmware trust, shipping friction, and seed backup burden.
2-of-3 Threshold Wallet
Splits signing authority across desktop, co-signer, and passkey shards so no single party can move funds.
Private stablecoin payments built for real financial activity
Privatum delivers non-custodial USDC and USDT payments with threshold security, passkey recovery, and a privacy focused roadmap.
Build and launch private payment flows with confidence
Create threshold-secured payment workflows for users, teams, and developers using a native desktop app and open SDK.
Reliable custody that continuously verifies itself
Continuously monitor shard readiness, policy checks, activity, and recovery paths before funds move.
Shard health monitoring
Check client, co-signer, and passkey readiness before a transaction reaches the signing pipeline.
Co-signer policy enforcement
Validate session, transaction intent, spending limits, velocity, and anomaly signals before the second signature.
Activity and recovery visibility
Track settlement history, export activity, rehearse recovery, and rotate a lost client shard without a seed phrase.
Discover the full potential of Privatum Live
See how threshold custody coordinates private send, stealth receive, swaps, policy checks, and recovery in one operational flow.
Research driving the Privatum product thesis
What wallet drainers, custodial collapse, hardware recovery, and privacy infrastructure reveal about modern custody.
Connect every payment touchpoint effortlessly
Private Send
Transfer stablecoins through a two-shard signing flow with policy checks.
Stealth Receive
Share one handle while incoming payments arrive at one-time addresses.
In-Wallet Swaps
Swap supported stablecoins with route, quote, and slippage visibility.
Open SDK
Embed threshold wallets into applications with a Viem based TypeScript SDK.
Enterprise security for every private payment
Data Protection
Protect local shards with encrypted storage, OS keychains, isolated environments, and strict session controls.
Policy Controls
Enforce daily limits, velocity checks, anomaly detection, and transaction intent validation before co-signing.
High Availability
Maintain co-signer availability with monitored infrastructure, failover planning, and operational alerts.
Secure Access Control
Use passkeys, session checks, and quorum rules to manage access without giving any one party custody.
Reach users across every payment surface
Privatum connects desktop, SDK, Robinhood Chain, stablecoin swaps, stealth receive, and recovery surfaces in one custody model.
$24,806.42
Roadmap to native privacy.
Robinhood Chain Custody MVP
ERC-4337 smart accounts, 2-of-3 threshold sharding and passkey recovery, live on Robinhood Chain mainnet with a Tauri v2 desktop client.
Open SDK launch
A public, typed TypeScript toolkit built on viem, with guides, sample apps and audit-ready threshold primitives under MIT licensing.
DEX swap aggregation
Low-slippage USDC and USDT routing with transparent quotes, slippage controls and policy-checked execution across desktop and SDK.
Privacy Plane One
Threshold ECDSA and blind co-signing with ZK policy proofs, so signatures look standard and policy runs without profiling.
Privacy Plane Two
ERC-5564 stealth addresses, receiver unlinkability and screened privacy pools with association-set proofs for compliance-aware privacy.
Multichain expansion
Additional EVM adapters and new L2 networks with one shard model, a portable co-signer and a consistent desktop experience everywhere.
Security and custody research
No single party, not even Privatum, can move user funds.
Security and custody research
"Compromise of one shard gives an attacker zero spend authority. Loss of one shard still allows complete recovery."
Security and custody research
"The private key is never assembled or stored in one location. Spending requires cooperation from any two shards."
Common Questions
Privatum lets users and developers manage, send, receive, and swap USDC and USDT on Robinhood Chain with threshold security and privacy focused design.
The signing key is split into desktop, co-signer, and recovery passkey shards. Any two can approve or recover. One shard alone cannot spend.
The desktop client signs with Shard A, the co-signer validates policy and signs with Shard B, then partial signatures combine and settle through ERC-4337 infrastructure.
The recovery passkey and co-signer can rotate the lost client shard and restore access without exposing a seed phrase.
No. Privatum operates only the co-signer shard. Because every transaction requires two shards, Privatum cannot unilaterally move assets.
Privatum is built first for Robinhood Chain, an Ethereum-compatible Layer 2 with ETH gas, ERC-4337 support, and chain ID 4663.
The roadmap moves from custody MVP and SDK launch to swaps, invisible setup, confidential activity, and multichain expansion.
Build private payments on Robinhood Chain
Read the developer docs, explore the architecture, and follow the roadmap to native privacy.
