Cake Wallet

What Is Cake Wallet?

You don’t need a “crypto privacy tool” until you try to use a normal wallet and realize how much metadata leaks the moment you check a balance, look up prices, or swap coins. Cake Wallet is built for people who want self-custody while keeping network-level and transaction-level privacy under tighter control—especially if you use privacy-focused assets like Monero.

At its core, it’s a non-custodial wallet (your keys stay on your device) that can store, send, receive, and swap multiple cryptocurrencies, with a clear emphasis on privacy controls rather than a “finance app” vibe. The documentation positions it as a set of privacy tools plus cross-chain swaps, buy/sell integrations, and hardware wallet support.

What makes it distinctive in the wallet space is the combination of: (1) strong Monero support (Cake Labs’ ecosystem also ships a Monero-only sibling app, Monero.com), (2) explicit privacy settings around network calls (including Tor-related options), and (3) privacy-focused Bitcoin features such as Silent Payments support.

Cake Wallet Features and Performance

Cake Wallet’s feature set is bigger than “send/receive.” The project’s own docs describe a non-custodial wallet with storage and transfers, plus in-app exchange/swap and buy/sell through third parties.

Multi-chain support (one app, multiple chains). Cake Wallet documents support for “sixteen separate chains,” spanning privacy coins, Bitcoin and forks, the EVM ecosystem, and other networks. The same page also calls out wallet organization features like multiple accounts and subaddresses, a choice of seed types (Polyseed, 25-word, or BIP39), and “full coin control.” It also notes that Haven support has been removed (useful context if you’re coming from older guides).

In-app swaps (but not run by Cake). Swaps are integrated into the app, but Cake Wallet explicitly states it doesn’t operate the exchange itself; each swap is executed by a third-party provider. Their FAQ names examples spanning centralized swap services (ChangeNOW, Exolix, Trocador) and also mentions decentralized options (Chainflip and NEAR Intents). Practically: if a swap goes wrong, you’re depending on a provider—Cake support can help escalate, but they are not the counterparty.

Buy/sell integrations (provider rules apply). Buying and selling are also provided by third parties, and Cake’s docs are blunt that providers set rates, fees, limits, supported regions, and verification requirements. That means “KYC/no KYC” isn’t a wallet-level promise here; it’s a provider-by-provider reality depending on your country, amount, and payment method.

Privacy controls that actually change network behavior. Cake Wallet’s privacy settings documentation describes granular toggles for things like exchange-rate lookups: enabled, Tor-only, or disabled. It also describes a setting for broadcasting signed transactions through Blink’s private relay (instead of directly to the public mempool), with fallback behavior if the relay can’t be reached. Those details matter because they affect what third parties can observe while your transaction is waiting to confirm.

Tor support: evolving and a bit nuanced. Cake’s documentation includes guidance around using Tor/Orbot and also describes “built-in Tor support.” Separately, Cake’s own blog post about v5.1.0 describes “experimental Tor integration,” initially Android-only at release time. In other words: Tor-related privacy is supported, but you should read the current docs and understand what’s truly routed via Tor in your specific platform/version.

Hardware wallet workflows (including air-gapped devices). Cake Wallet’s docs include hardware wallet restore/setup guidance and explicitly mention air-gapped devices like COLDCARD and Cupcake, stating they are never connected and instead exchange data via QR codes. That’s a serious privacy/security capability if you want an offline signing workflow without juggling multiple apps.

Pricing and Plans

Cake Wallet’s pricing model is free. (This is also consistent with your provided, verified spec.)

That said, “free app” doesn’t mean “zero cost to use.” If you use swaps, buying, or selling, Cake Wallet’s own documentation states those flows are handled by third-party providers who set their own fees, exchange rates, limits, regional availability, and (where applicable) verification requirements. Expect provider fees and spreads when you use those services.

I did not find a reliable, source-backed statement of a refund policy specific to Cake Wallet itself (as distinct from a third-party provider’s refund rules), so I’m not going to invent one. For purchases/sales/swaps, you should assume refunds (if any) are governed by the provider and the transaction’s status, not by the wallet app.

Privacy and Security Assessment

Non-custodial design (baseline security posture). Cake Wallet’s GitHub repository description explicitly calls it “noncustodial,” which implies you control your keys and funds are not held by Cake. That’s the minimum bar for a privacy-first wallet.

Open-source posture. Cake Wallet’s core code is published on GitHub as an open-source repository. That’s important for auditability in principle (even if most users will never review the code).

What data may hit Cake infrastructure (per their policy). Cake Wallet’s public privacy policy states that personal data sent through Cake Labs nodes can be limited to items such as your device IP address, the block height your wallet is synchronized to, and transactions/channels you submit via their node to supported networks. A separate privacy document in the GitHub repo also explains that IP-derived location may be used to redirect you to a geographically close node for faster sync when using Cake Labs-maintained nodes. This is a key trade-off: using their infrastructure can improve UX, but it can also create metadata exposure (IP address and timing).

Tor and “Tor-only” settings (privacy upside, usability risk). Cake’s privacy settings documentation describes the ability to put certain lookups (like swap/exchange-rate lookups) into “Tor-only” mode or disable them. That’s good for privacy hardening, but it also creates failure modes—GitHub issues and discussions show that users can run into confusion or breakage when expecting Tor-only to “just work,” especially depending on how Tor is configured on-device. Expect to spend time validating your own setup if Tor is a hard requirement.

Third-party partners are part of the threat model. Cake Wallet’s own docs repeat the same reality across swaps and buy/sell: those are third-party providers. From a privacy standpoint, this is the biggest caveat. Even if the wallet itself is privacy-minded, a fiat on-ramp/off-ramp or swap provider can introduce account-level identity checks, analytics, and data retention outside Cake’s control.

Audits / incidents. I did not find a clearly documented, independent “no-logs audit” or comparable third-party audit statement for Cake Wallet in the sources reviewed. I also did not find a well-sourced public security incident write-up that I can cite confidently here. So: open source and privacy-forward, yes; independently audited claims, not something I can substantiate from the cited sources.

Strengths and Limitations

Strengths

• Strong privacy tooling focus (Tor-related controls, privacy settings) rather than pretending privacy “just happens.”
• Open-source, non-custodial foundation (better baseline trust than closed custodial apps).
• Serious Bitcoin privacy feature support (Silent Payments support is explicitly documented).
• Swaps are integrated with multiple providers, including named options in their docs, so you’re not locked to a single swap backend.
• Hardware wallet support includes air-gapped QR workflows for devices like COLDCARD/Cupcake.

Limitations

• Swap/buy/sell flows rely on third parties; privacy and KYC depend on providers.
• Using Cake Labs nodes can expose IP address and sync metadata per policy.
• Tor features can be confusing in practice; user reports indicate setup pitfalls.
• The docs note removed asset support (e.g., Haven), so coin support can change over time.

Who Should Use Cake Wallet?

Good fit

1. Monero-centric users who still need BTC/EVM access. If you primarily care about XMR-style privacy but occasionally handle BTC or other chains, Cake Wallet is built with that reality in mind and documents broad multi-chain support.
2. People who want privacy knobs, not promises. If you actually want to disable price lookups, force certain traffic through Tor, or otherwise reduce metadata leakage, Cake’s privacy settings and Tor-related guidance are more explicit than most wallets.
3. Users who want an air-gapped signing workflow without buying into a single ecosystem. If you already use (or plan to use) air-gapped hardware like COLDCARD/Cupcake, Cake’s QR-based workflow support is a practical advantage.

Not a great fit

1. Anyone who wants “one-click swaps” with guaranteed outcomes. Cake can help escalate issues, but swaps are executed by third-party providers and failures/disputes are ultimately provider-dependent.
2. Users who require audited “no-logs” claims. I couldn’t verify an independent audit claim in the sources reviewed, so if audited logging/privacy assurances are your gating item, Cake Wallet won’t meet that standard on evidence alone.
3. People who don’t want to think about network privacy. Tor modes and privacy settings are powerful, but they add complexity. If you won’t configure or test, you can end up with broken lookups or a false sense of privacy.