> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/features/privacy-and-security/privacy-settings.md). # Privacy settings Cake Wallet is private by default, but it also hands you the controls. This page walks through every privacy-related setting so you can decide what fits your threat model — each one lists what it does, what it protects, and our recommendation. Settings live in two places: `Settings` → Wallet settings → `Privacy` (per-wallet behavior) and `Settings` → App settings → `Connections` (how the app reaches the network). ## Privacy settings (per wallet) ![Privacy settings screen](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/settings_privacy_01_top.png) * **Auto generate addresses** — hands out a fresh receiving address after each payment so observers can't tie your transactions together. *Recommended on* (the default) for Monero, Bitcoin, Litecoin, and other rotating-address coins. * **Save recipient address** — stores the addresses you send to in each transaction's local details. Handy for your own records, but it keeps data on your device; turn it off if you'd rather Cake Wallet remember nothing about where you sent funds. * **Use Payjoin** — improves Bitcoin transaction privacy by having both sender and receiver contribute inputs. See [Payjoin](https://docs.cakewallet.com/features/privacy-and-security/payjoin) (Bitcoin, mobile). * **Enable Lightning** — turns on the Bitcoin [Lightning](https://docs.cakewallet.com/features/basic/bitcoin-lightning) balance and address. * **Silent Payments**, **MWEB**, **Coin Control** — open their own screens; see [Silent Payments](https://docs.cakewallet.com/features/privacy-and-security/silent-payments), [Litecoin MWEB](https://docs.cakewallet.com/features/privacy-and-security/litecoin-mweb), and [Coin control](https://docs.cakewallet.com/features/advanced/coin-control). ## Connections settings (whole app) ![Connections settings screen](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/settings_connections_01_top.png) * **Enable built-in Tor** — routes the app's connections through Tor, hiding your IP from nodes and services. See [Built-in Tor](https://docs.cakewallet.com/features/privacy-and-security/built-in-tor). * **Fiat API** — controls how Cake Wallet fetches prices to show fiat values. Set to `Tor only` to fetch privately, or `Disabled` to stop fetching prices entirely (your balances then show only in crypto). * **Swap** — the same three modes for exchange-rate lookups: enabled, Tor-only, or disabled. * **Mempool API** — fetches accurate Bitcoin fees and confirmation times. Disabling it improves privacy slightly but makes fee estimates rougher. * **Disable Automatic Exchange Status Updates** — stops the app from polling providers for your trades' status in the background. * **Background sync** — keeps Monero wallets synced while the app is closed (Android). See [Background sync](https://docs.cakewallet.com/features/advanced/background-sync). ### Use Blink Protection Although it protects your transactions rather than your connections, the `Use Blink Protection` toggle lives on the `Connections` screen rather than the per-wallet `Privacy` screen. When it is on, Cake Wallet broadcasts your signed transaction to Blink's private relay instead of straight into the public mempool, so MEV searchers cannot see and front-run it while it waits to be mined; if the relay is unreachable the wallet quietly falls back to your normal node. The toggle is **on by default** and only appears for Ethereum and Base wallets, the two chains the relay supports. It is also offered on the `Privacy settings` screen shown while you create or restore a wallet. ### Block explorer history Also on the `Connections` screen, a set of six toggles controls whether Cake Wallet fetches transaction history from a third-party block explorer: `Etherscan history`, `PolygonScan history`, `BaseScan History`, `ArbiScan History`, `BSCScan History`, and `TronGrid history`. Each is **on by default**, and each appears only when the open wallet is on the matching chain. Querying an explorer means handing your addresses to that provider, so turn a toggle off if you would rather that operator not learn which addresses you hold — at the cost of a less complete history for that chain. ## Domain lookups `Connections` → `Domain lookups` lets you turn individual address-resolution services on or off — ENS, OpenAlias, Unstoppable Domains, and the rest. Each one, when enabled, sends the name you're paying to that service to resolve it into an address. Turn off any you don't use. See [Address lookup services](https://docs.cakewallet.com/features/advanced/address-lookup-services). ## Set privacy before a wallet ever connects When you create or restore a wallet, the `Privacy settings` screen lets you choose a custom node, Blink Protection, and fiat/exchange modes *before* the wallet makes its first connection — useful if you never want it touching default infrastructure. The [hardening guide](https://docs.cakewallet.com/tutorials/mobile-hardening) covers a full privacy-first setup. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cakewallet.com/features/privacy-and-security/privacy-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.