> ## Documentation Index
> Fetch the complete documentation index at: https://docs.privacyboost.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Privacy Boost
> A privacy SDK for any EVM chain. Regulatory-friendly, highly performant, composable, and self-custodial.
Privacy Boost enables applications to integrate private transfers and privacy-preserving DeFi workflows into public blockchains while keeping the data private from the public, viewable by the sponsoring app, and auditable by regulators.
Deposit, transfer, and withdraw ERC-20 tokens with amounts, counterparties, and balances fully hidden onchain.
Understand the protocol, cryptographic foundations, and architecture
Integrate private payments into your app with our multi-platform SDKs
***
## Who is this for?
On public blockchains, every transfer, every balance, and every counterparty relationship is visible to anyone. For applications handling real financial flows, this creates immediate business, competitive, and regulatory risk.
User balances and transaction history must remain private and never be broadcast onchain.
Payment and settlement flows require confidentiality between counterparties.
Institutional positions and counterparty identities are commercially sensitive.
Privacy must align with financial regulatory frameworks, not conflict with them.
***
## Why Privacy Boost?
Server-side ZK proof generation inside hardware-isolated enclaves. With no client-side proving, Privacy Boost works instantly on any platforms, including mobile devices.
Proof aggregation batches hundreds of transfers into a single onchain transaction, reducing gas costs by orders of magnitude.
Authorized auditors can query specific accounts. Every audit access is logged immutably onchain. Privacy for users, accountability for regulators.
Your keys, your funds. Forced withdrawal lets you exit directly through the smart contract, even if every server goes offline permanently.
A TEE-secured indexer decrypts and serves your balance and transaction history in real time. No blockchain scanning required.
Works with MetaMask, WalletConnect, any EOA account and smart accounts. TypeScript, React, React Native, iOS, Android, and CLI SDKs, with no new wallet software needed.
Earn without publicly revealing your wallet. Deposit into approved vaults and redeem back to your shielded balance, with your wallet identity hidden throughout the flow.
***
## Demo
[Try the live app →](https://app.privacyboost.io)
***
## How It Works
**1. Deposit**: Tokens move from a public wallet into the privacy layer and become encrypted private notes.
**2. Transfer Request**: The user signs a transfer with their auth key and submits it to the TEE Prover.
**3. ZK Proof Generation**: The TEE generates a zero-knowledge proof in \~500ms, batching many transactions into a single epoch proof for higher throughput.
**4. Onchain Verification**: The smart contract verifies the proof and records the result. Amounts, balances, and counterparties remain hidden.
**5. Encrypted State Indexing**: The TEE Indexer reads onchain state and indexes encrypted metadata, giving sender and recipient instant access to their balances and history.
**6. Auditability**: When required, authorized auditors can query specific accounts' balances and history through a [scoped disclosure mechanism](/product/auditability). Every query is logged immutably onchain.
***
## Why ZK + TEE?
Most privacy protocols force a tradeoff: client-side proving is trustless but costs 5–30+ seconds per transaction, can't serve balance queries, and has no auditability.
Privacy Boost combines both:
* **ZK proofs** provide the privacy guarantees: sender, recipient, amounts, and token types are all hidden onchain. The smart contract verifies every proof and holds all funds. This is the cryptographic foundation.
* **TEE** handles what ZK alone can't deliver: sub-500ms proof generation, instant balance and transaction history queries, and auditability through scoped audit access, all inside a hardware-isolated enclave.
The result: a privacy protocol with the speed and UX of a centralized system, the trustlessness of ZK, and the custody guarantees of a smart contract.
**Self-custody is unconditional.** Even if the TEE goes offline permanently, users can exit directly through the smart contract via forced withdrawal, using their own keys and public onchain data.
How the TEE works, what it can and can't see, forced withdrawal, and the full threat model
***
## Preview Features
Available now in the SDKs, pending external security audit.
A reusable public deposit address, similar to an exchange deposit address. Anyone can send supported ERC-20 tokens to it, and the protocol sweeps the funds into your shielded balance without revealing which shielded account was credited.
Send privately to a wallet address, even if the recipient has not registered with Privacy Boost yet. The recipient can claim the funds by registering with that address, and any unclaimed transfers are refunded after a set deadline.
***
## Coming Soon
Swap between tokens straight from your shielded balance, private DeFi trading with your wallet never exposed, just like Earn already puts your funds to work privately.
***
## Explore the Docs
TEE guarantees, self-custody, forced withdrawal, and threat model
How auditors query data with onchain accountability
UTXO model, notes, nullifiers, Merkle trees, transaction lifecycle
Key hierarchy, dual-path ECDH encryption, privacy addresses
Get started with the Privacy Boost SDK
Build a private payment flow in 5 minutes
Add private payments to your React app
Scripting and automation via command-line