Privacy Playbook

Last updated: 2026-07-09

Privacy is not about hiding from everyone. It is about not handing strangers a neat file with your name, home address, balances, wallet clusters, and daily routine.

What is the Bitcoin privacy order of operations?

The Bitcoin privacy order of operations is: stop talking about holdings, avoid address reuse, label coins, separate KYC and non-KYC history, run your own node when ready, use Tor for wallet traffic, reduce home-address exposure, and keep wallet metadata private. Do the simple habits first.

Habit	Protects against	Start here
New address every time	Public balance linking	Use your wallet’s receive button once per payment
Labels	Self-inflicted coin merges	Label every deposit source
Coin control	Linking unrelated coins	Choose coins manually for larger sends
Own node	Address queries leaking to strangers	Connect Sparrow to Bitcoin Core or Electrs
Home-address privacy	Physical targeting	Remove yourself from easy databases

Shut Up About Amounts

Do not post balances. Do not hint at stack size. Do not tell strangers at meetups what you hold. Do not make your social identity “rich Bitcoiner with home address somewhere on the internet.”

This sounds obvious until the market is up and everyone wants to flex. Do not flex.

Use Fresh Addresses

Use a new receive address for every payment. Modern wallets do this automatically. Let them.

Address reuse lets a payer or observer connect payments that should have stayed separate. One reused address can turn a private wallet into a public account statement.

Label Everything

Labels are not decoration. They are memory.

Good labels look like this:

River withdrawal 2026-07
salary from client A
gift from uncle, no KYC
conference sale, do not merge

Six months later, you will not remember. Label now.

Do Not Merge Coins Blindly

If you spend coins from two sources in the same transaction, you often link those sources on-chain. That might connect your exchange identity to a private payment or connect two parts of your life you meant to keep apart.

Use coin control for larger sends. Pick the coins you intend to spend. If you do not understand the labels, wait.

Keep KYC Coins in Their Lane

Coins bought from a KYC exchange are already linked to your identity at that exchange. You can still hold them safely, but do not pretend they are private.

Use separate wallet accounts for different histories:

KYC exchange withdrawals
Earned bitcoin
Peer-to-peer purchases
Long-term cold storage
Spending wallet

Separation will not fix past leaks. It prevents new ones.

Run Your Own Node When Ready

If your wallet asks someone else’s server about your addresses, that server can learn your wallet cluster and IP address. A personal node removes that leak.

The practical setup: Bitcoin Core plus Sparrow, or a node package such as Start9 or Umbrel if you want a guided path.

Do this after your seed backup and restore drill are solid. Privacy upgrades should not break basic custody.

Use Tor for Wallet Traffic

Tor hides your IP from the servers you contact. Sparrow supports Tor. Many node packages route services over Tor.

A VPN is not the same thing. A VPN moves trust from the destination service to the VPN company. That may still be useful on hotel WiFi, but know the tradeoff.

Your COLDCARD does not need Tor. It is offline. The networked wallet and node are what matter.

Reduce Home Address Exposure

Physical attackers need a name, a target, and a place. Do not make the place easy.

Practical moves:

Use a P.O. box or mailbox service for Bitcoin-related shipments when possible.
Remove yourself from data broker sites.
Blur your home on street-view services if available.
Do not post photos that reveal your house, car plate, school, office, or routine.
Keep exchange and tax documents out of shared cloud folders.

This is not paranoia. It is cleanup.

Keep Metadata Private

An xpub, output descriptor, wallet file, or watch-only export may not spend coins, but it can expose your addresses and transaction history.

Do not upload wallet files to random services. Do not paste xpubs into portfolio trackers unless you are comfortable giving that company your full wallet view.

Private keys steal money. Metadata steals privacy. Both matter.

PayJoin and CoinJoin

PayJoin can break simple transaction assumptions when both sides support it. Use it when available.

CoinJoin is more advanced and has changing liquidity, tooling, and legal pressure. Learn the tradeoffs before using it. Do not send mixed coins straight to an exchange and expect no questions.

A Simple Starting Plan

This week:

Stop reusing addresses.
Label every UTXO you can identify.
Stop posting about holdings.
Remove obvious home-address exposure.
Keep KYC coins separate from other histories.

Next month, set up your own node. Then learn coin control well enough that you can explain your next transaction before you sign it.