# Cloaked > Your payments, your business. A wallet that doesn’t broadcast your every move. Set up in seconds. ## Cloaked ### The Problem Most crypto users eventually create a new wallet because their old wallet accumulated too much history. A single address gradually reveals your balances, your counterparties, the apps you use, and the transactions that connect them all together. Once an address becomes tied to your identity, many users start over. The workaround is familiar: move funds through an exchange or privacy tool, create a new wallet, withdraw to a fresh address, and try not to reconnect it to the rest of your activity.
Before

Send to an exchange, withdraw to a new address, then do it again later. Create another wallet every time you need a fresh start.

MetaMask Used address
Coinbase Kraken Binance KYC exchange hop
New wallet
Rainbow Fresh address
Then do it again later. Getting a fresh start onchain shouldn't require multiple hops and another wallet. ### What Cloaked Does Cloaked gives you the benefits of a fresh wallet without creating a new one. Every time you receive funds, they can land at a fresh self-custodial address that only you control. Cloaked tracks those addresses for you, shows them in a single balance view, and lets you decide which funds to use later. Instead of managing a growing collection of wallets, you keep one account while maintaining separation between different parts of your onchain life. Fresh addresses. One balance view. No wallet resets.
After

Use one account while each receive can start at a fresh address and move into Incognito when you review it.

MetaMask Rainbow Cloaked Used address
Cloaked Cloaked Powered by Privacy Pools
Cloaked Fresh address
### Benefits * **Fresh receive workflow** — receive at a fresh address, then review and move eligible funds into your Incognito balance before spending * **One wallet view** — Cloaked aggregates balances across generated addresses so you do not have to manage them manually * **Full wallet actions** — send, swap, bridge, and cash out from the same account while fresh receive addresses work in the background * **Advanced address control** — where enabled, choose the specific address-held balances used for a send * **ENS-native** — receive funds at the `username.clkd.eth` name Cloaked gives you, or link your own ENS name * **Self-custody** — Cloaked never holds your funds or private keys; everything is recoverable via the [recovery tool](https://recovery.clkd.xyz/) * **Passkey or wallet** — register with a biometric passkey or connect an existing wallet ### What Cloaked Isn't Cloaked doesn't make you invisible. It helps you stop broadcasting your financial life to everyone else. Cloaked is not a mixer, exchange, or custodial wallet. You always control your funds. Fresh receive addresses reduce address reuse. Incognito balances use compliant privacy pools to break the direct link between receiving and spending funds. Cloaked improves your privacy, but it does not guarantee anonymity, erase blockchain history, or make public blockchains private. To provide a smooth experience, Cloaked helps coordinate your account activity and balances. Cloaked can see the activity it coordinates, but that activity does not have to be broadcast to everyone else. ### How It Works See [How It Works](/docs/how-it-works) for the technical model behind fresh addresses, key separation, and sends. ### Safety See [Safety & Bug Bounty](/docs/safety-and-bug-bounty) for Porto audit and bug bounty information for the account contracts Cloaked uses. ## How It Works Cloaked gives users fresh receive addresses while keeping one usable wallet experience. Cloaked is self-custodial. It can generate addresses, scan the chain, track balances, and prepare transactions for you, but only you can sign and move funds. This is achieved using a capability-based key derivation model. ### Key Derivation Model When you register, a high-entropy secret is produced on your device — either from a passkey (via biometric prompt) or from a wallet signature protected by a [PIN](/docs/faq#what-is-the-pin). On the client, this secret is deterministically transformed into two **scoped cryptographic capabilities**: * **Viewing capability**\ Shared with the service. Allows detection of which stealth addresses belong to you, enables balance tracking, and allows the service to derive new stealth addresses. * **Spending capability**\ Retained entirely by the client. Required to authorize and sign transactions from stealth addresses. These capabilities are not wallet private keys. They are derived, scoped, and re-derivable from your original secret (passkey or wallet signature). Only you can authorize spending. The spending capability never leaves your device. This separation allows the service to coordinate stealth addresses on your behalf without custody or signing authority. ### Receiving Funds When someone sends you funds, they can use the Cloaked [ENS](https://ens.domains/) name you choose during setup, a linked ENS name you own, or a payment address generated through the app or API. Behind the scenes, the service: * Derives a unique stealth address for each payment * Monitors the blockchain for funds sent to that address * Aggregates balances across all stealth addresses associated with you Each payment lands at a distinct onchain address. That keeps different receives from automatically sharing one reused public address. Senders never see your other stealth addresses, past or future.

Advanced

##### Stealth Address Derivation Stealth addresses are derived using elliptic-curve Diffie–Hellman (ECDH), following the principles described in [ERC-5564](https://eips.ethereum.org/EIPS/eip-5564) and related implementations (e.g. Umbra). Address creation requires only public data derived from your spending and viewing keys. No private keys are shared with senders. In Cloaked’s architecture, address derivation and scanning are handled off-device for performance and UX, while spending authority remains entirely client-side.
### Sending Funds Stealth addresses fragment your balance across many independent addresses. Sending funds requires safely recombining those balances. At a high level, the service: * Selects funds from one or more stealth addresses * Constructs a transaction covering the send amount and fees * Routes any change to a newly derived stealth address to avoid reuse Your self-custody wallet authorizes and signs all transactions. If one send uses multiple addresses, that transaction links those addresses onchain. Cloaked normally optimizes automatically, but where Advanced Control is enabled, users can choose exact address-held balances before requesting a quote.

Advanced

Cloaked uses [EIP-7702](https://eips.ethereum.org/EIPS/eip-7702) to upgrade stealth EOAs into [Porto](https://porto.sh/) smart accounts, imbuing Cloaked stealth addresses with the flexibility of smart accounts such as in-kind gas sponsorship and support for operations like swaps and bridging. This makes it practical to combine funds from many stealth addresses into a single send while preserving privacy and avoiding address reuse. All execution is explicitly authorized by the user’s wallet, while the service handles transaction coordination without requiring the user to deploy or manage smart contracts.
### What Is Visible Onchain Fresh receives do not hide every blockchain event. They avoid building everything on one address. | Visible event | What it means | | --------------------------- | ------------------------------------------------------ | | Receive to a fresh address | Funds arrived at an address generated for your account | | Balance at that address | That address holds funds until you spend or move them | | Send from one address | That address paid the destination | | Send from several addresses | Those addresses are linked by the transaction | | Change output | Leftover funds are routed to a new generated address | The privacy boundary is practical separation. Fresh addresses help keep unrelated activity apart until user behavior or a later transaction connects it. ### Privacy Pools Cloaked integrates [Privacy Pools](https://docs.privacypools.com/) to offer an additional layer of privacy. By depositing funds into a compliant privacy pool, your balance is grouped with other deposits. After compliance approval, you can send or swap from your Incognito balance. Note that while the on-chain link to your original deposit is broken, Cloaked's relay service has visibility into both sides of the transaction. See [Privacy Pools](/docs/privacy-pools) for a full explanation of how pooling works, the balance tiers, and the trust model. {/* Auto-generated by scripts/generate-api-reference.ts — DO NOT EDIT */} import { ServerSelector, BearerTokenInput } from '../../components/api-reference/AuthPanel'; import { EndpointCard } from '../../components/api-reference/EndpointCard'; ## API Reference Download OpenAPI Spec ### Authentication The API accepts two types of Bearer tokens: * **JWT** — Obtain one instantly by completing the Sign-In with Ethereum (SIWE) flow below (GET /nonce → POST /verify). JWTs are short-lived session tokens. * **API Key** — Long-lived platform keys for server-to-server integrations. Contact us at [support@clkd.xyz](mailto\:support@clkd.xyz) to request one. Pass either token in the `Authorization` header — the server auto-detects the format. **Important:** The address used for authentication must be the address derived from your private spending key (`privateKeyToAccount(p_spend)`), NOT your connected wallet address. The server identity is this derived auth address — your wallet address never touches the server. Endpoints marked with 🔒 require a valid Bearer token. #### Get HPKE public key #### Get nonce #### Verify sign-in #### Logout ### Account Management Account creation, signers, subdomains, and setup #### Check subdomain availability #### Create account #### Get account #### Get funded addresses #### List account tokens #### Import account token #### Get account token detail #### Claim subdomain #### Generate subdomain ### Receive Payment address generation and ENS resolution #### Create payment address ### Balance & Activity Balance queries, transaction history, and supported tokens #### List supported chains #### Get token catalog #### Lookup token #### Get balances #### Get chain balances #### Get token balance #### Get activities #### Get pending activities #### Get deposit review #### Mark deposit review seen ### Transact Sending, swapping, bridging, converting to incognito, and cashing out all follow the same flow: get a quote, then submit. #### Get quote signer public key #### List supported pools #### Get spendable addresses #### List provenance address tags #### Set provenance address tags #### Get address balances #### Get cashout market #### Create quote #### Submit transaction #### Get relay status #### Unlock quote #### Get max spendable #### Create swap preview #### Recover conversion prepare #### Get pool state #### Get pool commitments ### Cloakie Cloakie NFT verification and withdrawal #### Verify cloakie deposit #### Withdraw cloakie ### Relayer #### Relayer details #### Relayer quote #### Relayer request ### Send #### Resolve send destination avatar #### Classify send recipient address ### Account #### Get contact email #### Set contact email #### Delete contact email ### Simulation #### Simulate transaction ### Utilities #### Lookup function signatures ## Careers Cloaked doesn't have any open roles right now. We're grateful for your interest in what we're building. That said, we're always glad to hear from people who care deeply about privacy, security, and great product design. If that's you, feel free to introduce yourself at [support@clkd.xyz](mailto\:support@clkd.xyz) — we keep an eye on these messages, and we'll reach out if a role opens up that fits. Thanks for thinking of us. Check back here as the team grows. ## Developers Cloaked provides API access for integrating Cloaked into your application or automating operations for teams. This page covers account types, authentication methods, API access, and signing flows. ### Account Types #### Individual Created automatically on registration. One signer, threshold of 1. Everything described in [How It Works](/docs/how-it-works) applies — an individual account is the default. #### Team Multiple signers with k-of-n threshold signing. Team accounts are created via the API and support: * Configurable signer count and threshold (e.g. 2-of-3) * API-key authenticated operations (payment address generation, quotes) * Async signature collection — signers don't need to be online simultaneously * Auto-relay when the signing threshold is met ### Authentication Methods Cloaked's key model requires a single high-entropy secret to derive viewing and spending capabilities. That secret can come from any source that produces a deterministic, reproducible value. #### Wallet Signatures Sign a deterministic message with any EOA wallet (MetaMask, Rabby, hardware wallets, etc.). The signature is transformed into scoped capabilities via the same derivation described in [Key Derivation](/docs/how-it-works#key-derivation-model). A [PIN](/docs/faq#what-is-the-pin) is also required when using wallet connect — it is combined with your wallet address to construct the message your wallet signs, adding an explicit confirmation step that protects against blind signing. Passkey users do not need a PIN since the biometric prompt itself serves as the confirmation step. #### Passkey PRFs The [WebAuthn PRF extension](https://w3c.github.io/webauthn/#prf-extension) allows passkeys to return a deterministic secret bound to a relying party. No wallet required — biometric authentication (Face ID, fingerprint, Windows Hello) produces the entropy directly. Browser-native, phishing-resistant, and works on any device with a platform authenticator. #### Embedded Wallets & Agents For programmatic and agent use cases, embedded wallet providers (Privy, Turnkey, Fireblocks, etc.) can supply the signing entropy. This enables: * Automated payment address generation * Server-initiated sends via API keys * Agent-driven operations without human-in-the-loop signing ### API Access Team accounts authenticate via API keys for server-to-server integration. The API supports: * **Payment addresses** — generate stealth addresses programmatically * **Quotes** — coin selection and fee estimation * **Sends** — build transactions, collect signatures, auto-relay Individual accounts can also use API keys for the same operations. ### Signing Flow #### Individual The client signs the transaction directly, and it is relayed immediately. #### Team 1. A quote locks the stealth addresses needed to cover the send amount 2. A transaction intent (the unsigned transaction details) is created from the quote, producing a digest 3. Each signer retrieves their derived key material and signs the digest 4. When the threshold is met, the transaction is assembled and relayed automatically Signers can submit signatures independently and asynchronously — no coordinated online session is required. ## ENS Names Your Cloaked identity is an [ENS](https://ens.domains/) name. When someone sends funds to that name, Cloaked resolves it to a **fresh stealth address** for each payment, so a single shareable name never turns into a single reused public address. There are two ways to receive at an ENS name: * **Your Cloaked subdomain:** a free `yourname.clkd.eth` name you pick during registration, with nothing to set up onchain. * **A custom ENS name you own:** link an existing `.eth` name (e.g. `alice.eth`) so people can pay you at the name you already use, while you keep receiving at fresh stealth addresses. You can use both at once. Linking a custom name does not disable your `clkd.eth` subdomain. ### Bring Your Own ENS Name Linking a custom name points its resolver at Cloaked. You stay the owner of the name the whole time. Cloaked only becomes the **[resolver](https://docs.ens.domains/resolvers/quickstart/)**, the contract that answers "what address does this name point to?", and you can change it back at any point. Once linked, anyone resolving your name (in a wallet, an explorer, or a dApp) is sent to a freshly derived stealth address, exactly like your `clkd.eth` subdomain. #### How It Works 1. **Enter your name.** Type the ENS name you want to use (e.g. `alice.eth`). Cloaked checks that it's a valid `.eth` name and not already a `.clkd.eth` name. 2. **Connect the owning wallet.** Connect the wallet that owns the name, or owns its parent so it can create a [subname](https://docs.ens.domains/web/subdomains/). Cloaked reads the name's ownership and current resolver onchain to confirm you can manage it. 3. **Point it at Cloaked.** Approve a transaction that sets Cloaked's resolver for the name. If you'd rather dedicate a subname (e.g. `pay.alice.eth`), Cloaked creates that record instead and leaves your root name untouched. 4. **Confirm the link.** Cloaked verifies onchain that its resolver is now set, then stores the link to your account. From then on, the name resolves to fresh stealth addresses. The resolver-change transaction is a normal ENS transaction on Ethereum mainnet, so you pay network gas for it. After that, resolution is handled by Cloaked at no onchain cost to senders. #### Using a Subname You don't have to commit your main name. If you want to keep `alice.eth` pointed wherever it is today, link a subname like `pay.alice.eth` or `clkd.alice.eth` to Cloaked instead. The subname resolves to stealth addresses while your root name keeps its existing resolver. ### Keeping Ownership Linking is non-custodial in both directions: * **You keep the name.** Cloaked is set only as the resolver, never the owner. Your ENS registration, expiry, and ownership are unchanged. * **You can unlink anytime.** Set the name's resolver back to your previous choice (or any other resolver) and the link is removed. Cloaked never controls whether you can move your name elsewhere. See [Unlinking a Custom Name](#unlinking-a-custom-name) for the steps. ### Unlinking a Custom Name Unlinking is the link in reverse: point the name's resolver away from Cloaked, then remove the name from your account. Your `clkd.eth` subdomain keeps working the whole time, and funds you've already received are unaffected. 1. **Open the unlink flow.** In the app, find your custom name under **Your ENS names** and choose **Unlink from Cloaked** from the menu next to it. 2. **Enter a new resolver.** Paste the resolver address the name should use from now on, such as the [ENS Public Resolver](https://docs.ens.domains/resolvers/public). It must be a resolver contract; a plain wallet address can't answer ENS queries. 3. **Connect the managing wallet and approve.** Connect the wallet that manages the name and approve the resolver-change transaction on Ethereum mainnet. Like linking, this is a normal ENS transaction, so you pay network gas. 4. **Cloaked removes the link.** Once the transaction confirms, Cloaked verifies onchain that its resolver is no longer set, then removes the name from your account. The name stops resolving to fresh stealth addresses. **Already changed the resolver yourself?** If you've pointed the name at another resolver in the [ENS app](https://app.ens.domains/), or transferred the name to a new owner, choose **I manually updated ENS** in the unlink flow instead. Cloaked checks the change onchain and removes the link without another transaction. If you made the change moments ago, verification can briefly lag behind the chain; wait a minute and retry. After unlinking, the name resolves to whatever its new resolver says, so set its address records if you want it to keep pointing at a wallet. You can link the name to Cloaked again at any time. ### Requirements & Limits | Requirement | Detail | | -------------------------- | ------------------------------------------------------------------------ | | **An ENS name you manage** | You must own the name, or own its parent so you can create a subname. | | **Ethereum mainnet** | The name and the resolver-change transaction live on Ethereum mainnet. | | **Not a `.clkd.eth` name** | Those are reserved for Cloaked subdomains and can't be linked as custom. | | **One custom name** | An account has one active custom ENS name at a time. | ### Privacy The privacy benefit is the same as the rest of Cloaked: each payment lands at a distinct stealth address, so receives to your name don't pile up on one reused public address. Senders see only the address derived for their payment, never your other addresses. Your custom name is stored on Cloaked only in encrypted form, under a key derived from your account that the server can't read. The name itself is public on Ethereum and anyone can resolve it, so the protection is in the fresh addresses behind it, not in hiding the name.

Advanced

Cloaked resolves names through an [offchain resolver](https://docs.ens.domains/resolvers/ccip-read/) that uses [CCIP-Read](https://eips.ethereum.org/EIPS/eip-3668). When you link a name, the onchain transaction sets that resolver as the name's address provider. A query for the name (`addr()`) is then deferred to Cloaked's gateway, which derives a fresh stealth address for your account and returns a signed response that the resolver verifies. This is the same mechanism that powers `clkd.eth` subdomains, so custom names and Cloaked subdomains resolve identically. Linking requires a signature from the name's manager so Cloaked can confirm the request comes from the controller, and Cloaked re-reads the resolver onchain before storing the link. Ownership reads use a configured RPC endpoint rather than the connected wallet's default provider, which avoids the rate-limited public endpoints that previously caused linking to fail in the browser.
### Further Reading * [Using Cloaked](/docs/using-cloaked): registration and choosing your `clkd.eth` subdomain * [How It Works](/docs/how-it-works): stealth address derivation and the receiving flow * [ENS](https://ens.domains/): the Ethereum Name Service ## Frequently Asked Questions ### What is a stealth address? An Ethereum-compatible address that only the recipient can recognize and control, generated using the recipient's public keys. A stealth address is still visible onchain, but it is not the same reused public address for every payment. [Learn more](https://eips.ethereum.org/EIPS/eip-5564). ### What happens after I receive at a fresh address? Funds land at a fresh address controlled by your Cloaked account. That address is separate from your usual wallet address and from other fresh receives. Deposit Review highlights the new receive so you can add a private tag, or move eligible balances into Incognito. Funds at a fresh address stay separate until you use them. The address is still visible onchain, and if you later spend those funds together with funds from another source, that action can link the sources. [Learn more](/docs/tagging-and-deposit-reviews). ### What happens if I spend from multiple receive addresses? Those addresses become linked by that transaction. This is how public blockchains work: a transaction that spends from multiple addresses reveals that those addresses were controlled together for that action. Cloaked chooses the address-held balances needed to fund the action you are taking, whether you are sending, swapping, bridging, or cashing out. If you want more control, click **Select tags** before approving so you can choose which tagged balances to use. ### Can other people see my tags? No. Tag names are encrypted before they are saved, and they are not written onchain. Cloaked stores encrypted tag data for your account, not readable tag names. ### Do tags make funds private? Tags help you understand and control which balances you use together. They do not change transactions that are already visible onchain. ### Why did my `Incognito receive` tag disappear? Cloaked carries the `Incognito receive` tag forward as long as those funds are not associated with any other visible history. If you receive Incognito funds and then swap them, the tag can stay with the swapped balance. If you later send those funds together with funds from a different source, that action links the sources. At that point, Cloaked stops treating the whole balance as an Incognito receive, and the tag drops away. ### What happens to tags when I deposit into Incognito? Tags from funds that enter Incognito do not carry through the privacy pool. The pool breaks the visible onchain history between the address that entered and the funds that later come out, so earlier address tags no longer apply. ### What is ENS? A decentralized naming system that maps human-readable names (like `username.eth`) to Ethereum addresses and other resources. Cloaked uses ENS as a public entry point for generating stealth addresses. [Learn more](https://ens.domains/). ### What is the PIN? A 4-digit PIN required only if you register with a connected wallet (MetaMask, Rabby, etc.). Passkey users do not need a PIN — the biometric prompt itself serves as the confirmation step. The PIN is combined with your wallet address to construct a Cloaked-specific message that your wallet signs. That signature is then used to derive your viewing and spending capabilities. You will be prompted for your PIN whenever an action requires authorization. The PIN never leaves your device and is never stored by Cloaked. The primary purpose of the PIN is to interrupt mindless signing by requiring an explicit confirmation step for sensitive actions. Being prompted to enter your PIN is a signal that you are authorizing a sensitive Cloaked action. This makes accidental or blind signing much less likely and helps protect against phishing attempts that rely on tricking users into signing messages without understanding why. **Important**: Cloaked does not store your PIN. Make sure to store your PIN securely. ### Does Cloaked custody my funds? No. Cloaked never custodies your funds or private keys. Your funds remain fully under your control and are held onchain at stealth addresses derived from your keys. Only you can authorize and sign transactions. Cloaked provides coordination services (address derivation, balance tracking, and transaction construction) but cannot move funds independently. ### What happens if Cloaked goes offline? Your funds remain safe and accessible onchain. Since Cloaked does not custody funds, your stealth addresses and their balances are unaffected by service downtime. However, while offline, you won't be able to: * View your aggregated balance through Cloaked * Generate new stealth addresses through Cloaked's service * Construct and send transactions through Cloaked You can always access your funds independently using the [recovery tool](https://recovery.clkd.xyz), which lets you rederive spending capabilities and stealth addresses without relying on the Cloaked service. Cloaked is designed to pass the “walkaway test”: the system should continue to work even if the service becomes unavailable or the original developers disappear. This reflects a commitment to decentralization and user financial sovereignty. > “We’re building decentralized applications. Applications that run without fraud, censorship or third-party interference. Applications that pass the walkaway test: they keep running even if the original developers disappear.” - [Vitalik](https://x.com/VitalikButerin/status/2006737662942871574) If you send transactions from stealth addresses outside of Cloaked, Cloaked may not be aware of those transactions. This can cause your displayed balance to be incorrect or transactions to appear missing until the system re-syncs. ### What is a privacy pool? A privacy pool is a smart contract where multiple users deposit funds together. After a compliance approval step, you can withdraw or spend from the pool using a zero-knowledge proof — which breaks the direct on-chain link between your deposit and withdrawal. This gives you an "Incognito balance" that on-chain observers cannot link back to your original deposit. [Learn more](/docs/privacy-pools). ### What is the Incognito balance? Your Incognito balance is made up of funds in privacy pools. After a compliance approval step, pooled funds can be used for private sends or swaps at any time. Privacy grows as more people deposit into the pool. [Learn more](/docs/privacy-pools#balance-tiers). ### Can Cloaked see my privacy pool activity? Yes. Cloaked's relay service submits transactions on your behalf, which means the Cloaked server can observe the link between your deposits and withdrawals. On-chain observers cannot. This is a trade-off of using Cloaked's managed experience versus interacting with privacy pool contracts directly. If you want to withdraw from a privacy pool without Cloaked's relay involvement, you can use [recovery.clkd.xyz](https://recovery.clkd.xyz) to export your private key and then withdraw with a different relayer through [privacypools.com](https://www.privacypools.com/). Note that recovery.clkd.xyz runs entirely client-side — it re-derives your keys locally and does not communicate with Cloaked's servers. This way Cloaked has no visibility into the withdrawal. However, withdrawing outside of Cloaked means your Cloaked wallet will not be aware of the withdrawal — your displayed balances and transaction history may be incorrect or show unexpected behavior. [Learn more](/docs/privacy-pools#trust-model). ## How It Works Cloaked gives users fresh receive addresses while keeping one usable wallet experience. Cloaked is self-custodial. It can generate addresses, scan the chain, track balances, and prepare transactions for you, but only you can sign and move funds. This is achieved using a capability-based key derivation model. ### Key Derivation Model When you register, a high-entropy secret is produced on your device — either from a passkey (via biometric prompt) or from a wallet signature protected by a [PIN](/docs/faq#what-is-the-pin). On the client, this secret is deterministically transformed into two **scoped cryptographic capabilities**: * **Viewing capability**\ Shared with the service. Allows detection of which stealth addresses belong to you, enables balance tracking, and allows the service to derive new stealth addresses. * **Spending capability**\ Retained entirely by the client. Required to authorize and sign transactions from stealth addresses. These capabilities are not wallet private keys. They are derived, scoped, and re-derivable from your original secret (passkey or wallet signature). Only you can authorize spending. The spending capability never leaves your device. This separation allows the service to coordinate stealth addresses on your behalf without custody or signing authority. ### Receiving Funds When someone sends you funds, they can use the Cloaked [ENS](https://ens.domains/) name you choose during setup, a linked ENS name you own, or a payment address generated through the app or API. Behind the scenes, the service: * Derives a unique stealth address for each payment * Monitors the blockchain for funds sent to that address * Aggregates balances across all stealth addresses associated with you Each payment lands at a distinct onchain address. That keeps different receives from automatically sharing one reused public address. Senders never see your other stealth addresses, past or future.

Advanced

##### Stealth Address Derivation Stealth addresses are derived using elliptic-curve Diffie–Hellman (ECDH), following the principles described in [ERC-5564](https://eips.ethereum.org/EIPS/eip-5564) and related implementations (e.g. Umbra). Address creation requires only public data derived from your spending and viewing keys. No private keys are shared with senders. In Cloaked’s architecture, address derivation and scanning are handled off-device for performance and UX, while spending authority remains entirely client-side.
### Sending Funds Stealth addresses fragment your balance across many independent addresses. Sending funds requires safely recombining those balances. At a high level, the service: * Selects funds from one or more stealth addresses * Constructs a transaction covering the send amount and fees * Routes any change to a newly derived stealth address to avoid reuse Your self-custody wallet authorizes and signs all transactions. If one send uses multiple addresses, that transaction links those addresses onchain. Cloaked normally optimizes automatically, but where Advanced Control is enabled, users can choose exact address-held balances before requesting a quote.

Advanced

Cloaked uses [EIP-7702](https://eips.ethereum.org/EIPS/eip-7702) to upgrade stealth EOAs into [Porto](https://porto.sh/) smart accounts, imbuing Cloaked stealth addresses with the flexibility of smart accounts such as in-kind gas sponsorship and support for operations like swaps and bridging. This makes it practical to combine funds from many stealth addresses into a single send while preserving privacy and avoiding address reuse. All execution is explicitly authorized by the user’s wallet, while the service handles transaction coordination without requiring the user to deploy or manage smart contracts.
### What Is Visible Onchain Fresh receives do not hide every blockchain event. They avoid building everything on one address. | Visible event | What it means | | --------------------------- | ------------------------------------------------------ | | Receive to a fresh address | Funds arrived at an address generated for your account | | Balance at that address | That address holds funds until you spend or move them | | Send from one address | That address paid the destination | | Send from several addresses | Those addresses are linked by the transaction | | Change output | Leftover funds are routed to a new generated address | The privacy boundary is practical separation. Fresh addresses help keep unrelated activity apart until user behavior or a later transaction connects it. ### Privacy Pools Cloaked integrates [Privacy Pools](https://docs.privacypools.com/) to offer an additional layer of privacy. By depositing funds into a compliant privacy pool, your balance is grouped with other deposits. After compliance approval, you can send or swap from your Incognito balance. Note that while the on-chain link to your original deposit is broken, Cloaked's relay service has visibility into both sides of the transaction. See [Privacy Pools](/docs/privacy-pools) for a full explanation of how pooling works, the balance tiers, and the trust model. ## Off Ramp Cloaked integrates [Peer](https://peer.xyz/) to let you sell crypto for fiat through a peer-to-peer escrow flow. Peer is operated by P2P Labs Inc. and provides an app and interface for accessing a peer-to-peer escrow protocol. Your crypto is deposited into an onchain escrow, a matched buyer sends fiat to your payment handle, and the escrow releases the crypto once the payment is proven. The buyer never receives custody of your crypto before payment, and Cloaked does not custody your funds. Cloaked coordinates the quote, routing, signatures, and onchain submission so you can cash out from visible balances or from your Incognito balance. ### How It Works 1. **Choose payment details** — Select a supported payment method and enter the fiat destination details required by Peer. 2. **Preview the cash out** — Enter the asset and amount you want to sell. Cloaked estimates the fiat amount, route, network costs, and service fee. 3. **Confirm** — Sign with your passkey or wallet. Cloaked submits the transaction that moves the selected crypto into the Peer escrow. 4. **Settlement** — A buyer sends fiat through the selected payment method. Once the payment is proven, the escrowed crypto is released to the buyer. ### Routes Cloaked automatically chooses the simplest route for the funds you want to sell. | Route | When it applies | What happens | | ------------------------ | -------------------------------- | ---------------------------------------------------------------------------------------------------- | | **Direct** | USDC on Base | Funds are deposited directly into the Peer escrow. | | **Swap** | Non-USDC token on Base | Cloaked swaps the token into USDC, then deposits USDC into escrow. | | **Bridge** | Funds on another supported chain | Cloaked bridges or swaps the funds to USDC on Base before escrow deposit. | | **Incognito withdrawal** | Privacy pool balance | Cloaked withdraws from your Incognito balance, bridges to Base if needed, then deposits into escrow. | The escrow currently settles in USDC on Base. If your source funds are on another chain or in another token, the quote includes the required swap or bridge steps. ### Payment Details Cloaked uses Peer to access a peer-to-peer escrow flow with payment proof and verification. Supported fiat destinations depend on Peer availability, buyer activity, and selected payment methods, and may include payment methods such as Venmo, Revolut, Wise, PayPal, Zelle, or Cash App. Cloaked stores a hashed reference to your payment details for the cash-out flow. Raw payment details are handled through the Peer integration rather than stored as plain text by Cloaked, and may be processed by Peer or made available as needed for buyers to complete payment. Peer's [Privacy Policy](https://www.peer.xyz/pp) and [Terms of Service](https://www.peer.xyz/tos) apply to Peer's handling of the off-ramp flow. ### Statuses After you confirm a cash out, the order can move through several statuses: * **Pending** — Cloaked is waiting for the escrow deposit transaction to confirm. * **Awaiting fill** — The escrow deposit is open and waiting for a buyer. * **Filling** — A buyer has locked the order and is completing fiat payment. * **Completed** — The order was filled and the fiat payment was sent. * **Recoverable** — Funds from a canceled or expired order can be claimed back. * **Cancelled or failed** — The order closed without completing. Partially filled orders can happen when only part of the escrow amount is matched. In that case, the filled portion settles normally and the remaining amount can be canceled or recovered when it becomes available. ### Cancels and Recovery You can cancel an open cash out before it completes. If no buyer has locked funds, cancellation can return the remaining escrowed crypto quickly. If a buyer has already locked an order, those funds may need to wait until the buyer's payment window expires before they become recoverable. Cloaked tracks this state and shows when recovery is available. Recovery sends claimable funds back to your Cloaked balance. ### Fees * **Network fee** — Gas and routing costs for swaps, bridges, escrow deposits, cancellations, or recovery transactions. * **Cloaked fee** — A service fee shown in the quote before you confirm. * **Route costs** — Swap slippage or bridge costs may apply depending on the route. All applicable fees and estimated proceeds are disclosed before transaction execution. ### Trust Model Off ramping involves three distinct systems: * **Cloaked** coordinates account selection, routing, transaction construction, and relay submission. Cloaked cannot move funds without your authorization. * **Peer** provides the app and interface for accessing the peer-to-peer escrow protocol, including payment proof and verification flows. * **The buyer** sends fiat through the selected payment method. When cashing out from an Incognito balance, the privacy pool still breaks the public onchain link between your original deposit and withdrawal. However, as with other managed privacy pool actions, Cloaked's relay service can observe the relationship because it coordinates the transaction. ### Further Reading * [Peer](https://peer.xyz/) — peer-to-peer cash-out protocol * [Privacy Pools](/docs/privacy-pools) — Incognito balances and privacy pool trust model * [Swaps & Bridging](/docs/swaps) — routing assets across tokens and chains ## Passkey Safety If you registered with a passkey (instead of connecting an external wallet), your passkey is the primary way to access your account. There is no password reset or seed phrase. You can create a **backup** — a password-encrypted file containing your keys — as a safety net. If you lose your passkey, the backup lets you recover your funds at [recovery.clkd.xyz](https://recovery.clkd.xyz). See [Account Recovery](/docs/recovery) for full details. Even with a backup, keeping your passkey synced is important — it's your primary access method for day-to-day use. Before signing out or switching devices, make sure your passkey is **synced to a cloud-backed password manager** so it's available on all your devices. ### Checking your passkey is synced #### Apple (iCloud Keychain) 1. Open **Settings** on your iPhone, iPad, or Mac. 2. Tap **Passwords** (or search for it). 3. Search for **Cloaked** or your Cloaked domain. 4. Confirm you see a passkey entry — if it's there, it's synced across all your Apple devices signed into the same iCloud account. iCloud Keychain syncs passkeys automatically. If you registered your passkey on an Apple device and iCloud Keychain is enabled, you're all set. #### Google (Google Password Manager) 1. Go to [passwords.google.com](https://passwords.google.com) or open **Settings > Passwords** on your Android device. 2. Search for **Cloaked**. 3. Confirm you see a passkey entry — if it's there, it's synced across all your devices signed into the same Google account. Google Password Manager syncs passkeys across Android devices and Chrome on desktop. #### Other password managers Some third-party password managers (1Password, Dashlane, etc.) also support passkeys. Check your password manager's passkey section to confirm the Cloaked entry is stored there. ### What if I can't find my passkey? If you're currently signed in but can't find your passkey in any password manager, your passkey may be stored only on your current device. This means it won't be available if you lose the device or factory reset it. If you're unsure, **stay signed in** until you can confirm your passkey is backed up. If you need help, contact support at [support@clkd.xyz](mailto\:support@clkd.xyz). ### Tips * **Don't disable cloud sync** for your password manager — this is what keeps your passkey available across devices. * **Stay signed in** if you're unsure whether your passkey is synced. You can always check later. * **Test on another device** — the most reliable way to confirm sync is to try signing in from a different device. ## Privacy Pools Cloaked integrates [Privacy Pools](https://docs.privacypools.com/) to give you an **Incognito balance** — funds that have no direct on-chain link to your original deposit. Privacy Pools were introduced in the [original research paper](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4563364) by Buterin, Jacob, et al. and implemented by [0xbow](https://www.0xbow.io/). ### How It Works 1. **Deposit** — Move visible funds into a compliant privacy pool. Your deposit is grouped with other users' deposits. 2. **Approval** — An [Association Set Provider (ASP)](https://docs.privacypools.com/layers/asp) reviews the deposit for compliance with network policies. Once approved, your funds are ready to use. 3. **Send or swap** — Spend from your Incognito balance. A [zero-knowledge proof](https://ethereum.org/en/zero-knowledge-proofs/) authorizes the withdrawal without revealing which deposit is yours. ### Balance Tiers Your Incognito balance is made up of funds sitting in the privacy pool after ASP approval. They can be used for private sends or swaps at any time. Privacy grows as more people deposit into the pool. ### Trust Model Privacy pools break the **on-chain** link between your deposit and withdrawal. No external observer can connect the two by analyzing the blockchain. However, Cloaked's [relay service](/docs/how-it-works#sending-funds) submits transactions on your behalf. This means **the Cloaked server can observe the association** between your deposit and withdrawal, because it coordinates both sides of the transaction. This is a trade-off of using Cloaked versus interacting with privacy pool contracts directly. The benefit is a seamless UX — you don't need to manage proofs, gas, or contract calls yourself. The trade-off is that Cloaked, as the relay operator, has visibility into the link. For users who need stronger privacy guarantees, the underlying [Privacy Pools protocol](https://docs.privacypools.com/) is open and can be used independently with different relayers. You can use [recovery.clkd.xyz](https://recovery.clkd.xyz) to export your private key and withdraw through [privacypools.com](https://www.privacypools.com/) directly. See the [FAQ](/docs/faq#can-cloaked-see-my-privacy-pool-activity) for details. ### Fees * **Network fee** — Gas for the deposit or withdrawal transaction, displayed before you confirm. * All applicable fees are disclosed before transaction execution. ### Compliance Privacy pools are designed to be compatible with regulatory expectations. The [ASP approval](https://docs.privacypools.com/layers/asp) step ensures that deposits meet network compliance policies before funds can be used privately. This distinguishes privacy pools from [mixing services](https://ethereum.org/en/privacy/#mixers) — privacy is achieved within a compliant framework. ### Further Reading * [Privacy Pools documentation](https://docs.privacypools.com/) * [0xbow](https://www.0xbow.io/) — Privacy Pools implementation * [How Cloaked Works](/docs/how-it-works) — key derivation, sending, and receiving ## Privacy Policy **Last Updated:** June 24, 2026 *** ### About Us Cloaked Technologies, Inc. ("Cloaked", "we", "us") operates services through clkd.xyz, app.clkd.xyz, recovery.clkd.xyz, api.clkd.xyz, clkd.id, and related domains. We serve as the data controller for personal data processed through our services. This policy applies to all users of Cloaked's web application, mini-apps, and APIs. ### 1. Personal Data We Collect #### 1.1 Information You Provide * **Passkey / WebAuthn credential metadata** — credential ID and public key (used for authentication) * **Backup data** — encrypted and held by you; we do not retain a copy * **ENS names or subdomains** you register through the service * **Off-ramp payment information** — payment method selection and payment destination details you provide when using cash-out features, such as publicly identifiable payment handles or similar identifiers. Cloaked stores only the hashed payment-detail reference needed to coordinate the off-ramp flow; raw payment destination details are handled through the Peer integration and may be processed by Peer. * **Contact details** — email address, if you provide one in-app to receive account updates and product news, subscribe to updates, join a waitlist, or contact us. An in-app contact email is optional, kept in its own table separate from your stealth/address data, and can be removed at any time from Settings, which deletes it from our servers. #### 1.2 Information Collected Automatically * **Device and browser information** — user-agent, platform, screen size * **IP address** — used transiently for rate limiting, abuse prevention, and sanctions/geographic access controls; not stored long-term * **Session and authentication tokens** — for maintaining your authenticated session * **Usage data** — pages visited, features used, error logs (for debugging and service improvement) #### 1.3 Blockchain and Relay Data * **Public wallet addresses** — including stealth addresses associated with your account * **On-chain transaction data** — publicly available on supported EVM-compatible blockchains * **Token balances and transaction history** — indexed from public blockchain data * **Relay transaction data** — signed transaction payloads submitted through our relay service, including transaction hashes, destination addresses, token amounts, and gas parameters. This data is retained temporarily for relay processing and monitoring, and becomes publicly available on-chain upon confirmation. * **Off-ramp data** — when you use cash-out features, we process quote, route, escrow, payment-method, hashed payee reference, fee, conversion-rate, and lifecycle status data needed to move your authorized crypto transaction into a Peer escrow and track completion, cancellation, or recovery. On-chain escrow deposits, withdrawals, swaps, and bridge transactions become public blockchain data. * **Privacy pool data** — when you use privacy pool features, the relay service processes both deposit and withdrawal transactions. Because Cloaked coordinates both sides, we can observe the association between your deposit and withdrawal. This data is retained to track balances and construct future transactions on your behalf. Blockchain data is publicly accessible by nature. Our indexing of this data does not change its public status. #### 1.4 Information We Do NOT Collect * **Private keys** — your spending capability never leaves your device * **PRF secrets or raw biometric data** — processed entirely on your device by the platform's WebAuthn implementation * **PINs** — PINs are handled entirely on your device and are never transmitted to or stored by Cloaked There is no obligation to provide personal data. However, the services cannot function without the data strictly necessary for their operation (e.g. passkey credentials for authentication). ### 2. How We Collect Information We collect information through: * Account creation and service usage * Website and application interactions * Transaction relay processing * API usage * Off-ramp quote, escrow, cancellation, and recovery processing * Electronic correspondence with us * Blockchain indexing (publicly available data) ### 3. Legal Basis and Purposes We process your personal data on the following legal bases: **Contract Performance** — To provide and operate the services, including authentication, stealth address management, transaction construction, balance tracking, and customer support. **Consent** — For service analysis, personalization, newsletters, product updates, support outreach, understanding why people stop using the service, and promotional communications. You may withdraw consent at any time, including by removing your contact email in Settings. **Legitimate Interests** — To maintain and improve our infrastructure, develop new features, detect and prevent security threats, and ensure service reliability. **Legal Compliance** — To comply with applicable laws and regulations, respond to legal requests, and enforce our Terms of Service. ### 4. Data Retention We retain personal data for as long as it is needed for the purposes for which it was collected and in accordance with legal and regulatory requirements. When personal data is no longer necessary, it is deleted or anonymized. Blockchain data is permanent by nature and cannot be deleted from public blockchains. ### 5. Data Recipients We may share personal data with third-party service providers who assist in operating the services. These include: * **Cloud infrastructure providers** (e.g. AWS, Hetzner) — for hosting and data storage * **Blockchain RPC providers** (e.g. Alchemy) — for blockchain network access * **Third-party protocols** (e.g. Uniswap) — for swap routing (only public blockchain data) * **Peer-to-peer escrow services and interfaces** (e.g. [Peer](https://www.peer.xyz/), operated by P2P Labs Inc.) — for peer-to-peer cash-out flows, payment proof, verification, and escrow settlement. Information needed for the off-ramp flow may be processed by Peer as described in its [Privacy Policy](https://www.peer.xyz/pp). Peer may process payment identifiers you choose to provide and may make them available as needed for buyers to complete payment. Depending on the selected payment method, information may also be processed by the relevant fiat payment platform. These third parties process information under their own terms and privacy practices. Cloaked does not control Peer, fiat payment processing, buyer behavior, trade execution on the protocol, or third-party payment platform data handling. * **Privacy pool protocols** (e.g. 0xbow Privacy Pools) — for pool deposits and withdrawals. Deposit data is submitted to on-chain smart contracts and reviewed by an Association Set Provider (ASP) operated by a third party (0xbow Ltd.) for compliance approval. The ASP may collect and process data in accordance with its own [privacy policy](https://docs.privacypools.com/privacy-policy). Cloaked does not control the ASP's approval decisions or data handling practices. * **Analytics providers** — for usage analytics (if applicable) Service providers receive access only to the data necessary for their specific function and are bound by confidentiality obligations. ### 6. Data Transfers Personal data may be transferred to and processed in the United States, the European Union/EEA, and other jurisdictions. For transfers to jurisdictions that lack an adequacy decision, we implement appropriate safeguards, which may include standard contractual clauses or other approved transfer mechanisms. ### 7. Data Security We implement reasonable technical and organizational security measures to protect your data against unauthorized access, manipulation, loss, or disclosure. These include encryption at rest and in transit, access controls, and regular security assessments. Our passkey-based authentication model means there are no passwords to be compromised. Employees and service providers with data access are bound by confidentiality obligations and must comply with applicable data protection laws. ### 8. Cookies and Local Storage We use: * **Session cookies** — to maintain your authenticated session * **Local storage** — for wallet state, preferences, and application data * **Analytics cookies** — only with your consent We do not use third-party tracking cookies. ### 9. Your Rights Depending on your jurisdiction, you may have the following rights regarding your personal data: **Right of Access** — Request a copy of the personal data we hold about you. **Right to Rectification** — Request correction of inaccurate or incomplete personal data. **Right to Erasure** — Request deletion of your personal data when it is no longer necessary or was unlawfully processed. **Right to Restriction** — Request that we limit processing of your personal data in certain circumstances. **Right to Data Portability** — Request that your personal data be provided to you or another controller in a structured, commonly used, machine-readable format. **Right to Object** — Object to processing of your personal data based on legitimate interests. **Right to Withdraw Consent** — Withdraw consent at any time for processing based on consent, including marketing communications. **Right to Lodge a Complaint** — File a complaint with a supervisory data protection authority in your jurisdiction. To exercise any of these rights, contact us at [dev@clkd.xyz](mailto\:dev@clkd.xyz). We may need to verify your identity before processing your request. ### 10. Third-Party Links and Services Our services may contain links to or integrations with third-party websites, protocols, or services (e.g. ENS, Uniswap, Porto, [Peer](https://www.peer.xyz/), 0xbow Privacy Pools). We have no control over the content, privacy policies, or practices of these third-party services and assume no responsibility for them. ### 11. California Privacy Rights (CCPA) If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA): * **Right to Know** — You may request the categories and specific pieces of personal information we have collected about you. * **Right to Delete** — You may request that we delete your personal information, subject to certain exceptions. * **Right to Opt-Out** — You have the right to opt out of the "sale" or "sharing" of your personal information. **Cloaked does not sell or share your personal information** as defined under the CCPA. * **Right to Non-Discrimination** — We will not discriminate against you for exercising any of your CCPA rights. To exercise these rights, contact us at [dev@clkd.xyz](mailto\:dev@clkd.xyz). ### 12. Children's Privacy The services are not intended for users under the age of 18. We do not knowingly collect personal data from children. If we become aware that we have collected data from a child, we will take steps to delete it promptly. ### 13. Email Notifications If you provide a contact email — in-app or by subscribing to our newsletter or updates — we will send account, product, support, and related communications based on your consent. These communications may contain tracking pixels to measure open rates and engagement. You can remove your email at any time in Settings, unsubscribe via the link in any email, or contact us. ### 14. Changes to This Policy We may update this Privacy Policy from time to time. Changes become effective upon posting to our website. Where changes are material, we will make reasonable efforts to notify you (e.g. via email or an in-app notice). ### 15. Contact Us For questions or requests regarding this Privacy Policy, contact us at: **Cloaked Technologies, Inc.** [dev@clkd.xyz](mailto\:dev@clkd.xyz) ## Account Recovery Cloaked is self-custodial — your funds are secured by cryptographic keys that only you hold. How you back up and recover those keys depends on how you registered. ### Passkey users Your spending and viewing keys are derived from your passkey via a biometric prompt. The keys only exist in memory during active use and are never stored. **Two layers of protection:** #### 1. Keep your passkey synced Your passkey is your primary access method. Make sure it's synced to a cloud-backed password manager (iCloud Keychain, Google Password Manager, 1Password, etc.) so it's available across devices. See [Passkey Safety](/docs/passkey-safety) for detailed instructions. #### 2. Create a backup A backup is a password-encrypted file containing your spending and viewing keys. If you lose your passkey, you can use the backup and your password to recover your funds at [recovery.clkd.xyz](https://recovery.clkd.xyz). **How to create one:** * **After registration** — you'll be prompted to create a backup immediately after setting up your passkey. * **From Settings** — open the account menu, go to **Settings > Backup**, and follow the prompts. You'll verify with your passkey, then set a backup password. **What the backup does:** * Lets you recover your funds if you lose access to your passkey * The backup file is encrypted with your chosen password (min 12 characters) * Decryption and fund recovery happen at [recovery.clkd.xyz](https://recovery.clkd.xyz) **What the backup does NOT do:** * It does not reinstate a lost passkey — you would need to create a new passkey and re-register * It does not give Cloaked access to your keys — the file is encrypted on your device before export **Tips:** * Store the backup file somewhere safe (cloud drive, USB, password manager) * Use a strong, unique password and store it separately from the backup file * You can create a new backup at any time from Settings ### Wallet + PIN users Your spending and viewing keys are derived from a signature produced by your connected wallet, combined with your 4-digit PIN. Every time you authorize an action, Cloaked asks your wallet to sign a deterministic message (incorporating your PIN) and re-derives your keys from the result. **What you need to back up:** | What | Why | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | | **Wallet seed phrase / private key** | Your wallet produces the signature that derives your Cloaked keys. If you lose your wallet, you lose access. | | **PIN** | The PIN is combined with your wallet address to construct the signing message. Without the correct PIN, the derived keys will be different. | Cloaked does not store your PIN or your wallet's private key. Both must be backed up independently. **Tips:** * Follow your wallet provider's backup instructions (seed phrase, hardware wallet, etc.) * Store your PIN securely — a password manager is a good option * If you forget your PIN, there is no reset mechanism; your funds would only be recoverable if you can guess the correct 4-digit combination ### What if Cloaked goes offline? Your funds remain safe onchain regardless of Cloaked's availability. You can always recover your keys independently and access your stealth addresses using the [recovery tool](https://recovery.clkd.xyz). See [FAQs](/docs/faq#what-happens-if-cloaked-goes-offline) for more details. ### Summary | | Passkey | Wallet + PIN | | ------------------ | ---------------------------------------------- | ------------------------------------------- | | **Primary access** | Passkey (biometric) | Wallet + PIN | | **Backup method** | Backup (encrypted file) | Wallet seed phrase + PIN | | **Recovery tool** | [recovery.clkd.xyz](https://recovery.clkd.xyz) | Re-connect wallet, enter PIN | | **Risk if lost** | No passkey + no backup = permanent loss | No wallet + no seed phrase = permanent loss | ## Safety & Bug Bounty Cloaked's onchain account execution builds on Porto/Ithaca account contracts. Porto publishes its audit statement, bounty scope, and reporting process here: [Porto Security & Bug Bounty](https://porto.sh/contracts/security-and-bug-bounty) ## Swaps & Bridging Cloaked lets you swap tokens and bridge assets cross-chain directly from your stealth addresses, powered by [Uniswap](https://docs.uniswap.org/). ### How It Works 1. **Preview** — Enter a token pair and amount to see expected output, minimum received (after slippage), and estimated fees. No funds are locked. 2. **Quote** — Cloaked selects stealth addresses to fund the swap, locks those funds, and returns a time-limited quote. 3. **Confirm** — Sign with your passkey or wallet to submit the transaction. ### Supported Operations | Operation | Description | | ----------------- | -------------------------------------------------------------------------- | | **Swap** | Exchange one token for another on the same chain (e.g. USDC → ETH on Base) | | **Bridge** | Move tokens across chains (e.g. ETH on Ethereum → ETH on Base) | | **Wrap / Unwrap** | Convert between ETH and WETH | ### Fees * **Network fee** — Covers gas for the swap. Varies by route complexity and gas prices. Like sends, fees can be paid in-kind (e.g. pay with USDC when swapping USDC → ETH). * **Cloaked fee** — 0.85% of the input amount, included in the quoted price. Both fees are displayed before you confirm. ### Slippage Slippage is the difference between the quoted price and the execution price. Prices can move between when you submit and when the transaction confirms. By default, Cloaked uses automatic slippage. The route provider calculates the lowest tolerance expected to execute successfully, and the quote returns the effective max slippage used for the transaction. You can turn automatic slippage off and choose a manual tolerance up to 5%. Higher tolerance means the swap is more likely to succeed in volatile conditions but you may receive fewer tokens. Lower tolerance protects your price but the swap may fail if the market moves. The **minimum received** amount in the quote reflects the effective slippage for the final quote. ### Bridging When input and output tokens are on different chains, Cloaked automatically routes through a bridge (e.g. [Across](https://across.to/)). The same fees apply — network fee plus 0.85% Cloaked fee. The UI shows estimated fill time; bridge transactions may take a few minutes to arrive on the destination chain. ## Tagging & Deposit Reviews Traditional wallets reuse one address, so your wallet slowly turns into a public financial profile. Anyone who knows that address can inspect what came in, what stayed there, which apps you used, and where funds went next. Even someone you pay can look back at the address you paid from and see the rest of its history. Cloaked changes the default by giving each receive a fresh address controlled by your account. One receive does not have to expose the rest of your wallet. But fresh addresses only stay separate until they are used together. When you send, swap, bridge, or cash out, Cloaked defaults to using the addresses it needs to construct a transaction for the amount you chose. If an action uses several addresses, those addresses become linked onchain. Deposit Review is the command center for managing that trade-off. It highlights new inbound funds, lets you add private tags like `Payroll`, `Cold storage`, or `Ledger`, and helps you recognize what each balance represents before you spend or move it into Incognito. Tags are a privacy-preserving way to keep granular control over your fresh-address funds. ### The Workflow #### 1. Receive New receives are highlighted in Cloaked. The Review page badge shows how many receives need attention, and the amber dot marks a specific receive that needs review.
Review page icon in Cloaked with one pending item
The Review page badge means there are receives waiting for review.
Activity list showing received funds with amber review indicators
A fresh receive can be separate onchain, but it still needs a decision from you.
#### 2. Review Your Inbound The Review page collects new inbound funds in one place. From there, you can add a tag, or if eligible, move funds directly into Incognito from the fresh address they landed at.
Deposit Review page showing received assets that need review
Review is the inbox for inbound funds.
#### 3. Choose Funding Tags When you take an action, Cloaked chooses the addresses needed to fund the amount. The **Select tags** button gives you more granular control before you approve.
Send form showing the Select tags button
Select tags opens the funding controls for the action.
Choose the tagged balances you are comfortable using for that action.
Select tags sheet showing balances tagged Salary and Cold storage
Each balance lives at a different address. Selecting more than one can publicly link those addresses.
#### 4. Approve Onchain Action With Context Before you approve, Cloaked surfaces the tag being used for the transaction. This keeps the address-linking choice visible at the moment you sign.
Bridge review showing the Salary tag used for the transaction
Tags stay visible before approval, so you know what source context you are using.
#### 5. Understand Activity Later After the transaction confirms, Activity keeps the associated tag visible. That gives you a running view of how your onchain footprint is forming over time.
Activity history showing a bridged transaction tagged Salary
Activity shows the tags associated with completed actions.
### Tags and Associations Tags are not just a simple note on one deposit. Cloaked surfaces tags connected to a balance you hold when that connection can be proven. That includes the receive address that directly funded a balance, and it can also include other tagged sources publicly associated with that balance. For example, addresses can become associated when they are used together in one action, when funds were previously combined, or when receives share the same address. The goal is to show the onchain footprint around a balance, not just the first deposit that created it. A tag is attached to the Cloaked receive address where funds originally landed. If several receives land at the same address, they share that tag because the chain already links them through that address. When Cloaked can prove that current funds came from a tagged receive address, the tag can follow those funds through actions you take in Cloaked, such as sends, swaps, bridges, and cash-out flows. If you combine funds from two tagged sources, Cloaked can show both tags for that balance, helping you keep track. For example: 1. Alice receives payroll at one fresh address and tags it `Payroll`. 2. She receives funds from Cold storage at another fresh address and tags it `Ledger`. 3. If she spends from only the payroll address, Cloaked can show that source as `Payroll`. 4. If she spends from both addresses together, those sources are now linked by that transaction, so Cloaked can show `Payroll + Ledger`. ### Tag Privacy Tag names are encrypted before they are saved. The readable text stays protected by keys from your Cloaked account. The server stores encrypted tag data, not the readable tag. Cloaked can still see the addresses, transactions, and encrypted tag records it stores for your account. The private part is the tag text itself. You can clear or edit a tag later. Editing a tag updates the tag for that receive address, not for one individual token row. ### Review States **Needs review** means Cloaked found new received funds that can be tagged but do not have a user tag yet. This is the normal first state for a new fresh receive. **In progress** means an Incognito deposit is underway, waiting for approval, or needs attention after a rejection. Until that process finishes or funds are recovered, the review item stays active. **Done** means the receive has been tagged or the Incognito deposit has been approved. Older tagged receives may also appear as done so you can still see their tags in context. ### Incognito Tags Cloaked may show an `Incognito receive` tag when funds came out of a supported privacy pool. It means those funds do not carry visible onchain history back to your Cloaked account's fresh receive addresses.
Balance row showing an Incognito receive tag
Incognito receive means the funds came out of a supported privacy pool.
Cloaked carries the `Incognito receive` tag forward as long as those funds are not associated with any other visible history. If you receive Incognito funds and then swap them, the tag can stay with the swapped balance. If you later send those funds together with funds from a different source, that action links the sources. At that point, Cloaked stops treating the whole balance as an Incognito receive, and the tag drops away. ### Depositing Into Incognito and Tags This is separate from the `Incognito receive` tag. It is about what happens to tags you added before funds enter Incognito. Depositing into Incognito creates a privacy boundary. The privacy pool breaks the visible onchain history between the address that entered the pool and the funds that later come out. Earlier address tags do not carry through the pool because that link is no longer visible onchain. ### What Tags Are Not Tags are for your own wallet control. They are not public claims. Tags do not: * make tag names public; * prove what a tag means to anyone else; * change what already happened onchain; * stop public blockchains from showing transactions and balances. If you spend from several receive addresses in one transaction, those addresses become linked onchain. Tags make that easier to see before and after it happens, but they do not erase the link. ### How It Fits Fresh receives start with address separation. Deposit Review helps you decide what happens next. Use tags when you want to keep fresh-address funds understandable. Use Incognito when eligible funds should move through a privacy pool before later spending. Together, they make the receive workflow easier to manage without creating a new wallet every time you want a fresh start. See [Privacy Pools](/docs/privacy-pools) for how Incognito balances work. ## Terms of Service **Last Updated:** May 1, 2026 *** ### 1. Scope Cloaked Technologies, Inc. ("Cloaked", "we", "us") offers services through clkd.xyz, app.clkd.xyz, recovery.clkd.xyz, api.clkd.xyz, clkd.id, and related domains. By accessing or using any Cloaked service, you agree to be bound by these Terms. If you do not agree, you must stop using the services immediately. ### 2. Services Cloaked provides a non-custodial wallet application and developer infrastructure for stealth address payments on supported EVM-compatible networks. Our services include: * Sending and receiving tokens via stealth addresses * Transaction relay — submitting signed transactions to blockchain networks on your behalf * Stealth address generation, scanning, and balance tracking * Address selection controls * Passkey-based (WebAuthn / PRF) and PIN-based authentication * Token swaps and cross-chain bridges via third-party protocols (e.g. Uniswap) * Off-ramp features — selling crypto for fiat through third-party peer-to-peer escrow interfaces and protocols, including [Peer](https://www.peer.xyz/) * Privacy pool deposits and withdrawals via third-party protocols (e.g. 0xbow Privacy Pools) * ENS subdomain registration and management * Encrypted backup generation * Developer APIs for stealth address integration Your funds and access keys are self-custodial — only you can access and control them. Automated or bot-driven account creation is prohibited. You are responsible for securing your account credentials and all activity conducted through your account. You must be at least 18 years old to use the services. ### 3. Rights and Obligations of Cloaked We provide the services using reasonable care and skill and maintain our infrastructure free from known malicious software. We perform regular maintenance but do not guarantee that the services are error-free or available without interruption. We may suspend or restrict access to specific accounts if we reasonably suspect illegal or fraudulent activity, or if required by applicable law. Because we do not collect personally identifiable information, restrictions apply to accounts, not individuals. We reserve the right to modify these Terms and the services. Where reasonably possible, we will notify you of material changes before they take effect. **Cloaked explicitly does not:** * Offer custody of your funds or access to your private keys * Provide key recovery services (recovery is your responsibility via your backup) * Verify, endorse, or guarantee any transaction * Provide financial, investment, accounting, tax, or legal advice * Engage in regulated financial activities ### 4. Rights and Obligations of the User You must comply with all applicable laws and regulations when using the services. You may not: * Circumvent or attempt to bypass any security or access controls * Use the services for any unlawful purpose, including money laundering, terrorist financing, or sanctions evasion * Access the services via automated systems, bots, or scrapers without our written permission * Reverse engineer, decompile, or derive the source code of any proprietary part of the services * Engage in data mining or data harvesting of non-public service data * Sublicense, resell, or redistribute the services without written permission * Interfere with the services or other users' use of the services You acknowledge the inherent risks of blockchain technology, including but not limited to smart contract vulnerabilities, network congestion, and potential complete loss of funds. ### 5. User Representations By using the services, you represent and warrant that you: * Are not subject to economic or trade sanctions administered or enforced by the United States, including those maintained by the Office of Foreign Assets Control (OFAC), or any other applicable jurisdiction * Are not located in, organized in, or ordinarily resident in any jurisdiction subject to comprehensive economic or trade sanctions under applicable law * Have fully read and understood these Terms * Are of legal age in your jurisdiction and have the capacity to enter into a binding agreement ### 6. Non-Custodial Nature Cloaked is a non-custodial service. We never hold, control, or have access to your private keys or spending capability. The spending capability never leaves your device. Transactions are executed on-chain and are irreversible once confirmed. You are solely responsible for: * Securing your passkeys, PIN, and backup * Verifying all transaction details before signing * Maintaining copies of your backup in a safe location Lost passkeys or backups may result in permanent, irrecoverable loss of access to your funds. We cannot recover your account or funds. ### 7. Supported Networks and Tokens The services currently operate on supported EVM-compatible networks. Network and token availability may change without notice. We do not endorse any specific token or project. ### 8. Swaps and Bridges Token swaps and cross-chain bridges are routed through third-party protocols (e.g. Uniswap). Slippage, price impact, and third-party protocol fees apply. Cloaked charges a service fee on swaps and bridges (currently 0.85%), which is disclosed before transaction execution and may be updated from time to time. We do not guarantee swap or bridge execution, pricing, or availability. ### 8A. Off-Ramp Services Cloaked integrates third-party peer-to-peer escrow interfaces and protocols (including [Peer](https://www.peer.xyz/), operated by P2P Labs Inc.) that allow you to sell crypto for fiat through peer-to-peer escrow flows. Off-ramp features are subject to the following: * **Third-party provider.** Peer-to-peer off-ramp flows, payment proof, verification, and escrow settlement are provided by third parties, not by Cloaked. Peer provides an app and interface for accessing a peer-to-peer escrow protocol; the interface is distinct from the protocol, and Cloaked does not control Peer, buyers, fiat payment platforms, payment proof review, trade execution on the protocol, or third-party escrow contracts. Use of off-ramp features may be subject to Peer's [Terms of Service](https://www.peer.xyz/tos), Peer's [Privacy Policy](https://www.peer.xyz/pp), and the terms and policies of the selected payment platform. * **Peer-to-peer payments.** A cash-out order may be filled by one or more third-party buyers who send fiat through the selected payment method. Cloaked does not send the fiat payment, custody fiat funds, operate the fiat payment platform, or guarantee buyer performance. * **Payment details.** You are responsible for entering accurate payment destination information, including any payment handles or similar identifiers, and selecting a payment method you are legally permitted to use. Payment identifiers may be processed by Peer and made available as needed for buyers to complete payment. Incorrect, unavailable, suspended, or restricted payment accounts may delay or prevent settlement. * **Availability and completion.** Off-ramp availability depends on third-party liquidity, buyer activity, supported payment methods, supported jurisdictions, network conditions, and third-party service availability. Quotes, estimated fiat amounts, fill times, and conversion rates are estimates only and are not guaranteed. * **Cancellations and recovery.** Off-ramp orders may be cancellable or recoverable depending on escrow state and buyer activity. Funds locked in an active buyer intent may not be immediately recoverable and may require expiration or additional recovery steps. * **Third-party and smart contract risk.** Off-ramp flows may use smart contracts, swaps, bridges, third-party payment systems, wallets, and proof-generation or verification systems. You acknowledge the risk of delay, failed execution, partial fills, payment disputes, inaccurate or misleading information from counterparties, smart contract vulnerabilities, payment platform limitations, and partial or total loss. * **Compliance and taxes.** You are solely responsible for complying with laws and regulations that apply to your use of off-ramp features, including sanctions restrictions, payment platform rules, reporting obligations, and any tax consequences of selling crypto for fiat. * **Fees.** Off-ramp transactions may include network fees, route costs, third-party fees, and Cloaked service fees. Applicable fees and estimated proceeds are disclosed before transaction execution. ### 8B. Privacy Pools Cloaked integrates third-party privacy pool protocols (e.g. 0xbow Privacy Pools) that allow you to deposit funds into on-chain smart contracts and later withdraw or spend from those deposits. Privacy pool features are subject to the following: * **Third-party protocol.** Privacy pools are operated by third parties, not by Cloaked. Cloaked does not control the privacy pool smart contracts, the Association Set Provider (ASP), or the compliance approval process. Use of privacy pools is subject to the terms and policies of the respective protocol operators. * **No privacy guarantee.** Privacy pool features are designed to reduce the traceability of on-chain transactions but do not guarantee anonymity or privacy. The degree of privacy depends on factors outside Cloaked's control, including pool size, the number of participants, on-chain analysis techniques, and the behavior of third-party protocol operators. Cloaked makes no representation or warranty regarding the effectiveness of any privacy feature. * **User behavior.** You have total control over your funds. Your actions before or after using privacy pool features may reduce or eliminate any privacy benefits. For example, depositing and withdrawing similar amounts in close succession, reusing addresses, or publicly associating your identity with wallet addresses can allow third parties to link your activity. Cloaked has no control over how you use your funds and is not responsible for any loss of privacy resulting from your own actions. * **Relay visibility.** Because Cloaked's relay service submits both deposit and withdrawal transactions on your behalf, Cloaked can observe the association between your deposits and withdrawals. Users who require that Cloaked not have this visibility may interact with privacy pool contracts independently using their exported keys. * **ASP approval.** Deposits into privacy pools require approval by an ASP. Approval is not guaranteed and is determined solely by the ASP operator. Cloaked is not responsible for deposits that are declined or delayed by the ASP. * **Smart contract risk.** Privacy pool smart contracts are developed and maintained by third parties. Cloaked does not audit, endorse, or guarantee the security or correctness of these contracts. You acknowledge that depositing funds into a privacy pool carries the risk of partial or total loss due to smart contract vulnerabilities, bugs, or exploits. * **Fees.** Privacy pool deposits are subject to an on-chain vetting fee charged by the pool protocol and a Cloaked service fee. Both fees are disclosed before transaction execution. The Cloaked service fee may be waived for certain users. ### 9. Transaction Relay Cloaked operates a transaction relay service that submits your signed transactions to blockchain networks on your behalf. The relay transmits transactions you have already authorized and signed on your device — Cloaked cannot initiate, modify, or reverse transactions on your behalf. * **Best-effort delivery.** We use commercially reasonable efforts to relay transactions promptly but do not guarantee that any transaction will be included in a block, confirmed, or executed. Transactions may fail, be delayed, or be dropped due to network conditions, gas pricing, or other factors outside our control. Cloaked is not liable for any loss arising from unconfirmed or failed transactions. * **Fee guarantee.** The network fee quoted before transaction approval is a conservative estimate that serves as the maximum you will be charged. At relay time, Cloaked recalculates the fee based on current network conditions and reduces your payment accordingly; actual charges are typically lower than the quoted maximum. Gas estimation is inherently imprecise — estimates may exceed the actual network cost incurred, and Cloaked may retain the difference. If actual network costs exceed the quoted maximum, Cloaked absorbs the difference. * **Availability and refusal.** The relay service may be temporarily unavailable due to maintenance or network issues. Cloaked reserves the right to refuse to relay any transaction that we reasonably believe may violate applicable law or these Terms. ### 10. Fees * Network (gas) fees are paid by the user for all on-chain transactions (sends, swaps, etc.). The network fee displayed before transaction approval is a conservative estimate that represents the maximum amount you will be charged. Actual charges are typically lower due to relay-time fee adjustment based on current network conditions * Third-party protocol fees (e.g. Uniswap) are determined by those protocols * Cloaked charges service fees on swaps, bridges, privacy pool deposits, and off-ramps. Fee rates vary by transaction type, are disclosed before transaction execution, and are subject to change. Off-ramp quotes may also include third-party fees, route costs, or estimated fiat conversion amounts. No separate service fee is charged on sends; however, network fee estimates include an operational buffer to account for gas estimation variance, and Cloaked may retain the difference between estimated and actual network costs * All fees are disclosed before transaction execution * On-chain gas market conditions may cause any transaction to fail; failed or reverted transactions may still incur gas fees * Except where prohibited by law, all fees are non-refundable ### 11. API Usage Access to Cloaked's APIs requires an API key issued by Cloaked. By using our APIs, you agree to the following: * API keys are issued at our sole discretion and are non-transferable. You may not share, publish, or embed your API key in client-side code or publicly accessible repositories. * All API endpoints are subject to rate limits. You must not attempt to circumvent, exceed, or abuse these limits. * We reserve the right to revoke, suspend, or restrict any API key at any time, for any reason, including but not limited to suspected abuse, violations of these Terms, or excessive usage. * You are responsible for all activity that occurs under your API key and for ensuring that your integration complies with these Terms and all applicable laws. * If you build products or services that use Cloaked's APIs, you are responsible for your end-users' compliance with these Terms. You must not use the APIs to facilitate activity that would violate these Terms if performed directly. * We may modify, deprecate, or discontinue API endpoints at any time. Where reasonably possible, we will provide advance notice of breaking changes. * API availability is provided on an "as is" basis. We do not guarantee uptime, latency, or throughput for any API endpoint. ### 12. Termination Either party may terminate the relationship at any time. You may stop using the services at any time. We may suspend or terminate your access for violations of these Terms. Due to the non-custodial nature of the service, your funds remain accessible on-chain regardless of termination. You can always access your stealth addresses using your backup and our open-source tools. Termination does not affect any rights or obligations that have accrued prior to termination. ### 13. Intellectual Property All intellectual property rights in the services remain with Cloaked. Open-source components are governed by their respective licenses. Cloaked owns the clkd.eth ENS domain and all subdomains issued under it. We reserve the right to revoke, suspend, or discontinue any subdomain at any time, including if the associated account violates these Terms. ### 14. Disclaimers The services are provided "as is" and "as available" without warranties of any kind, whether express or implied, including but not limited to implied warranties of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that: * The services will be uninterrupted, timely, secure, or error-free * Blockchain networks will be available or function correctly * Any information provided through the services is accurate or complete Nothing in the services constitutes financial, investment, tax, or legal advice. Nothing in the services constitutes a guarantee of privacy, anonymity, or untraceability. Privacy features, including privacy pools, are provided on a best-effort basis and may not prevent all forms of transaction analysis or identification. Manual address selection controls are wallet management features. They may help you control which address-held funds are used together, but they do not alter public blockchain data or guarantee that activity cannot be linked. ### 15. Limitation of Liability To the maximum extent permitted by applicable law, Cloaked is liable only for damages caused by gross negligence or willful misconduct. Neither party may recover any amount with respect to loss of profit, data, goodwill, or other indirect, incidental, consequential, or punitive damages. This includes, without limitation, losses arising from: * Failed, delayed, or misdirected transactions, including those submitted via the relay service * Smart contract bugs or vulnerabilities * Blockchain network outages or reorganizations * Third-party protocol failures (e.g. Uniswap, bridge providers) * Off-ramp failures, delays, payment disputes, partial fills, buyer non-performance, payment platform restrictions, or errors by third-party peer-to-peer escrow services or interfaces such as Peer * Privacy pool deposits that are declined, delayed, or lost, including due to ASP decisions or third-party smart contract failures * Any loss of privacy or anonymity, whether resulting from on-chain analysis, user behavior, relay visibility, or any other cause * Loss of access due to lost passkeys or backups Force majeure events (including but not limited to natural disasters, war, pandemic, government action, or blockchain network failures) exempt performance obligations. ### 16. Indemnification You agree to indemnify, defend, and hold harmless Cloaked and its officers, directors, employees, and agents from and against any claims, damages, losses, liabilities, costs, and expenses arising from your use of the services or violation of these Terms. ### 17. Privacy Your use of the services is also governed by our [Privacy Policy](/docs/privacy), which describes how we collect, use, and protect your information. ### 18. Governing Law and Dispute Resolution These Terms are governed by and construed in accordance with the laws of the State of Delaware, United States, without regard to its conflict of laws principles. **Mandatory Arbitration.** Any dispute, claim, or controversy arising out of or relating to these Terms or the services ("Dispute") shall be resolved exclusively by binding arbitration administered by the American Arbitration Association (AAA) under its Commercial Arbitration Rules. The arbitration shall be conducted by a single arbitrator in Wilmington, Delaware. The arbitrator's decision shall be final and binding and may be entered as a judgment in any court of competent jurisdiction. **Class Action Waiver.** You agree that any Dispute shall be brought in your individual capacity only, and not as a plaintiff or class member in any purported class, consolidated, or representative action. The arbitrator may not consolidate more than one person's claims and may not preside over any form of class or representative proceeding. **Exceptions.** Either party may seek injunctive or other equitable relief in any court of competent jurisdiction to prevent the actual or threatened infringement of intellectual property rights. Claims eligible for small claims court in Delaware may be brought there instead of arbitration. **Opt-Out.** You may opt out of this arbitration and class action waiver provision by sending written notice to [dev@clkd.xyz](mailto\:dev@clkd.xyz) within 30 days of first accepting these Terms. If you opt out, Disputes shall be subject to the exclusive jurisdiction of the state and federal courts located in Delaware. ### 19. Miscellaneous * If any provision of these Terms is found to be unenforceable, the remaining provisions continue in full force and effect. * You may not assign your rights or obligations under these Terms without our prior written consent. * These Terms constitute the entire agreement between you and Cloaked regarding the services. * Our failure to enforce any right or provision does not constitute a waiver of that right or provision. * Links to third-party websites or services do not imply endorsement or responsibility for their content or practices. ### 20. Contact For questions about these Terms, contact us at [dev@clkd.xyz](mailto\:dev@clkd.xyz). ## Using Cloaked import { APP_URL } from '../../lib/constants'; Cloaked is a self-custodial wallet for fresh receive addresses and controlled sends. Cloaked lets you receive funds at new addresses, see them in one wallet, and decide later which address-held balances should be used together. You always retain direct control of your funds. * **Web app** — The primary Cloaked client. Register with a passkey or existing wallet, then send and receive with fresh stealth addresses from any browser. * **API** — Programmatic access for server-to-server integrations, agents, and automated operations. * **Farcaster mini-app** — Use Cloaked directly inside Farcaster, where onchain balances are publicly visible. { e.currentTarget.style.backgroundColor = '#6B3DEF'; }} onMouseLeave={(e) => { e.currentTarget.style.backgroundColor = '#7B4DFF'; }} > Open Cloaked App ↗ ### Registration Registration takes three steps: 1. **Create a passkey or connect a wallet** — A biometric prompt (Face ID, fingerprint, or Windows Hello) creates a passkey bound to Cloaked. Alternatively, you can connect an existing wallet (MetaMask, Rabby, etc.) and sign a message. Either way, this produces the secret used to derive your stealth address keys. See [Authentication Methods](/docs/developers#authentication-methods) for more on supported options. 2. **Authenticate** — Cloaked performs [Sign-In with Ethereum](https://login.xyz/) (SIWE) using an address derived from your private spending key. This happens automatically — your identity and your original passkey or wallet address are never sent to the server. 3. **Choose your ENS subdomain** — Pick a unique subdomain (e.g. `username.clkd.eth`) that others will use to send you funds. ### Receiving Funds Each time someone sends funds to the `username.clkd.eth` name Cloaked gives you, or to a custom ENS name you linked to Cloaked, Cloaked can generate a fresh stealth address for that payment. You can also share a direct payment page at `.clkd.id` when you want a QR-code page. Developers can generate payment addresses through the API.
Receiving funds interface showing QR code and address
Example of the shareable payment page for `satoshi.clkd.id`
Your aggregated balance across all generated addresses is displayed automatically, so you always have a single view of your total funds. ### Sending Funds To send funds: 1. **Enter amount and destination** — Select the asset and chain, enter the amount, and provide the destination address. 2. **Choose sources if needed** — By default, Cloaked selects address-held balances automatically. Where Advanced Control is enabled, you can choose exact addresses before quoting. 3. **Review the quote** — Cloaked selects enough address-held funds to cover the amount, calculates the required fees, and routes any change to a new stealth address. 4. **Confirm** — Authenticate with your passkey (biometric prompt) or wallet to sign the transaction. 5. **Transaction submitted** — Once signed, the transaction is relayed onchain. ### Fees Cloaked calculates transaction fees that include onchain gas costs. Fees are automatically calculated and displayed before you confirm any transaction, so you always know what you'll pay upfront. #### How Fees Work Fees include the cost of executing transactions on the blockchain. Cloaked uses [Porto](https://porto.sh/) smart accounts, which require gas to execute actions. Fees can be paid in-kind. For example, if you're sending an ERC20 token and your account doesn't have ETH, the token itself can be used to pay the transaction fee. This makes it easier to send tokens without needing to maintain a separate ETH balance for gas. #### Transaction Complexity When you send funds, Cloaked may need to combine balances from multiple stealth addresses. Transactions that require combining funds from more addresses will have higher fees due to the additional onchain operations needed. Cloaked automatically optimizes the selection of addresses to minimize fees while ensuring you have sufficient funds to cover both the send amount and fees. Any leftover funds after covering the send amount and fees are automatically routed to a new stealth address. This avoids reusing the sending address for change. Combining addresses is visible onchain. If you spend from several receive addresses in one transaction, those addresses become linked by that transaction. Advanced Control is meant to make that trade-off visible before you sign. #### What You See Before confirming any transaction, Cloaked shows you a quote that includes: * **Send amount** — The amount you're sending to the destination * **Fee** — The estimated transaction fee * **Total required** — Send amount + fee This gives you full transparency into the costs before you commit to the transaction. ### API Cloaked exposes a REST API for programmatic access to stealth address payments, including generating payment addresses, fetching quotes, and sending transactions. This is useful for server-to-server integrations, autonomous agents, and automated operations. See the [API Reference](/docs/api-reference) for endpoints and the [Developers](/docs/developers) page for details on API keys, team accounts, and authentication. ### Farcaster Mini App Cloaked is also available as a Farcaster mini-app. Crypto social platforms associate usernames and social graphs with onchain addresses, making balances and transaction history easy to inspect. The mini-app gives you the same stealth address privacy, accessible directly within Farcaster.