Privacy for everyday spending

What you're actually defending against

Card-network aggregation. Visa / Mastercard sell aggregated spending data to retailers + brokers. Your card is the cross-merchant tracker.
Bank monitoring. Your bank sees every transaction + flags patterns. "Lots of crypto-on-ramp activity" makes future banking harder.
Merchant-side data leaks. The retailer you bought from gets breached; your name + card + email + purchase history end up on a forum.
Targeted advertising. The "personalization" that makes you feel watched.

If your threat model includes a targeted adversary, this guide is too light — see threat models. For the 95% case, below works.

Rail 1 — Cash (boring, effective)

For in-person spending under $1,000, cash still works in most jurisdictions. Trade-offs: ATM withdrawal is bank-monitored, so use larger less-frequent withdrawals. Cash dies above thresholds (varies by country) where retailers refuse it or banks won't accept deposits without source-of-funds questions. For groceries, restaurants, transit, small services — cash is the default privacy answer.

Rail 2 — Prepaid card

Best for online spending where cash doesn't work. Pay USDT or XMR to a no-KYC card issuer, get a virtual or physical card, spend it where any Visa works. Privacy depends on the issuer's KYC posture — see prepaid-card guide.

Pros: Visa-network compatibility means it works everywhere; no merchant sees your real card; card-network aggregation captures only the prepaid balance, not you.
Cons: issuer is a single point of failure (lose the issuer, lose unspent funds); some merchants block prepaid; large purchases or recurring subscriptions can flag.
Pick: kyc.rip cards, other no-KYC virtual cards.

Rail 3 — Bitcoin Lightning

Best for crypto-native online merchants + tip jars + small recurring payments. Settlement on Lightning is fast and small-fee; non-custodial wallets keep keys local. See Lightning anonymously for setup; default to Phoenix or Mutiny.

Pros: sub-cent fees, instant settlement, non-custodial, no card-network involvement at all.
Cons: merchant acceptance is narrow (growing but spotty). Refund flows can be awkward.

Rail 4 — USDT direct

For crypto-native merchants or recurring B2B subscriptions priced in dollars. Pay direct in USDT (preferably from a non-exchange wallet to break the source-of-funds link). Rotate the originating wallet quarterly per USDT off-ramp.

Pros: $-denominated, low fees on TRC20, supported by most crypto-aware SaaS.
Cons: Tether can blacklist addresses; the freeze risk is non-zero for any address that touches volume.

Which rail when

Coffee, groceries, transit, in-person services → cash.
Online retail (Amazon-style aggregators) → prepaid card.
Crypto-native online merchants (VPN renewals, hosting, SaaS that accepts crypto) → USDT direct or Lightning, depending on what the merchant prefers.
Subscriptions in unfriendly jurisdictions → prepaid card from a privacy-respecting issuer; less likely to get caught by merchant geo-blocking than direct crypto.
Recurring privacy-tool spend (VPN / hosting / mail / no-KYC SIM) → either USDT or directly the provider's preferred rail. Most accept multiple.

The "save your wallet history" rule

Don't spend from the same wallet you receive payroll / large balances into. Keep a small "spending" wallet you regularly top up from your main wallet (preferably with an XMR-detour hop). When the spending wallet's history accumulates linkable patterns, retire it + start fresh. The cost is two transactions per quarter; the benefit is permanent.

Recurring spend — set it once

Subscriptions are the most-leaky spending category — same merchant, same time of month, same amount. If you can't avoid them:

Pay annually instead of monthly when allowed (single transaction vs 12).
Use a single dedicated prepaid card or Lightning channel for recurring; don't mix with one-off spend.
For high-value subscriptions, vary the amount slightly (most merchants let you tip the prepaid balance).