{
  "version": "v1",
  "slug": "everyday-spending-privacy",
  "title": "Privacy for everyday spending",
  "description": "Coffee, groceries, subscriptions, online purchases. The four rails (cash, prepaid card, Lightning, USDT) that handle 95% of daily spending without leaking your crypto wallet history at every point of sale.",
  "intro": "Most privacy guides assume you're moving large balances. Most spending is small + boring. The challenge isn't hiding a $20 coffee from a state adversary — it's not feeding your full transaction history into the payment processors that increasingly aggregate consumer data across merchants. Below: the four rails that work for daily life + which fits where.",
  "body_plain": "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). Picks for the everyday stack",
  "body_html": "\n      <section>\n        <h2 class=\"section-h\">What you're actually defending against</h2>\n        <ul class=\"bullet-list\">\n          <li><strong>Card-network aggregation.</strong> Visa / Mastercard sell aggregated spending data to retailers + brokers. Your card is the cross-merchant tracker.</li>\n          <li><strong>Bank monitoring.</strong> Your bank sees every transaction + flags patterns. \"Lots of crypto-on-ramp activity\" makes future banking harder.</li>\n          <li><strong>Merchant-side data leaks.</strong> The retailer you bought from gets breached; your name + card + email + purchase history end up on a forum.</li>\n          <li><strong>Targeted advertising.</strong> The \"personalization\" that makes you feel watched.</li>\n        </ul>\n        <p class=\"dim small\">If your threat model includes a targeted adversary, this guide is too light — see <a href=\"/guides/privacy-threat-models\">threat models</a>. For the 95% case, below works.</p>\n      </section>\n\n      <section>\n        <h2 class=\"section-h\">Rail 1 — Cash (boring, effective)</h2>\n        <p>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.</p>\n      </section>\n\n      <section>\n        <h2 class=\"section-h\">Rail 2 — Prepaid card</h2>\n        <p>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 <a href=\"/guides/no-kyc-prepaid-card\">prepaid-card guide</a>.</p>\n        <ul class=\"bullet-list\">\n          <li><strong>Pros:</strong> Visa-network compatibility means it works everywhere; no merchant sees your real card; card-network aggregation captures only the prepaid balance, not you.</li>\n          <li><strong>Cons:</strong> issuer is a single point of failure (lose the issuer, lose unspent funds); some merchants block prepaid; large purchases or recurring subscriptions can flag.</li>\n          <li><strong>Pick:</strong> <a href=\"/cards/kyc-rip-cards\">kyc.rip cards</a>, <a href=\"/cards\">other no-KYC virtual cards</a>.</li>\n        </ul>\n      </section>\n\n      <section>\n        <h2 class=\"section-h\">Rail 3 — Bitcoin Lightning</h2>\n        <p>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 <a href=\"/guides/lightning-anonymously\">Lightning anonymously</a> for setup; default to Phoenix or Mutiny.</p>\n        <ul class=\"bullet-list\">\n          <li><strong>Pros:</strong> sub-cent fees, instant settlement, non-custodial, no card-network involvement at all.</li>\n          <li><strong>Cons:</strong> merchant acceptance is narrow (growing but spotty). Refund flows can be awkward.</li>\n        </ul>\n      </section>\n\n      <section>\n        <h2 class=\"section-h\">Rail 4 — USDT direct</h2>\n        <p>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 <a href=\"/guides/usdt-off-ramp-privacy\">USDT off-ramp</a>.</p>\n        <ul class=\"bullet-list\">\n          <li><strong>Pros:</strong> $-denominated, low fees on TRC20, supported by most crypto-aware SaaS.</li>\n          <li><strong>Cons:</strong> Tether can blacklist addresses; the freeze risk is non-zero for any address that touches volume.</li>\n        </ul>\n      </section>\n\n      <section>\n        <h2 class=\"section-h\">Which rail when</h2>\n        <ul class=\"bullet-list\">\n          <li>Coffee, groceries, transit, in-person services → <strong>cash</strong>.</li>\n          <li>Online retail (Amazon-style aggregators) → <strong>prepaid card</strong>.</li>\n          <li>Crypto-native online merchants (VPN renewals, hosting, SaaS that accepts crypto) → <strong>USDT direct</strong> or <strong>Lightning</strong>, depending on what the merchant prefers.</li>\n          <li>Subscriptions in unfriendly jurisdictions → <strong>prepaid card</strong> from a privacy-respecting issuer; less likely to get caught by merchant geo-blocking than direct crypto.</li>\n          <li>Recurring privacy-tool spend (VPN / hosting / mail / no-KYC SIM) → either USDT or directly the provider's preferred rail. Most accept multiple.</li>\n        </ul>\n      </section>\n\n      <section>\n        <h2 class=\"section-h\">The \"save your wallet history\" rule</h2>\n        <p>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.</p>\n      </section>\n\n      <section>\n        <h2 class=\"section-h\">Recurring spend — set it once</h2>\n        <p>Subscriptions are the most-leaky spending category — same merchant, same time of month, same amount. If you can't avoid them:</p>\n        <ol class=\"bullet-list\">\n          <li>Pay annually instead of monthly when allowed (single transaction vs 12).</li>\n          <li>Use a single dedicated prepaid card or Lightning channel for recurring; don't mix with one-off spend.</li>\n          <li>For high-value subscriptions, vary the amount slightly (most merchants let you tip the prepaid balance).</li>\n        </ol>\n      </section>\n\n      <section>\n        <h2 class=\"section-h\">Picks for the everyday stack</h2>\n      </section>\n    ",
  "picks": [
    {
      "category": "cards",
      "id": "kyc-rip-cards",
      "name": "kyc.rip cards",
      "url": "https://xmr.club/cards/kyc-rip-cards",
      "markdown_twin": "https://xmr.club/llm/cards/kyc-rip-cards.txt",
      "why": "USDT/XMR → prepaid card balance. No identity at issuance. Online-everywhere Visa."
    },
    {
      "category": "wallets",
      "id": "cake-wallet",
      "name": "Cake Wallet",
      "url": "https://xmr.club/wallets/cake-wallet",
      "markdown_twin": "https://xmr.club/llm/wallets/cake-wallet.txt",
      "why": "Mobile XMR for cash-style in-person payments + subaddress per merchant."
    },
    {
      "category": "exchanges",
      "id": "kyc-rip-aggregator",
      "name": "kyc.rip aggregator",
      "url": "https://xmr.club/exchanges/kyc-rip-aggregator",
      "markdown_twin": "https://xmr.club/llm/exchanges/kyc-rip-aggregator.txt",
      "why": "Top up the spending wallet from main via XMR detour, no markup."
    },
    {
      "category": "exchanges",
      "id": "sideshift",
      "name": "SideShift",
      "url": "https://xmr.club/exchanges/sideshift",
      "markdown_twin": "https://xmr.club/llm/exchanges/sideshift.txt",
      "why": "USDT ↔ XMR for the regular rotation step."
    }
  ],
  "url": "https://xmr.club/guides/everyday-spending-privacy",
  "markdown_twin": "https://xmr.club/llm/guides/everyday-spending-privacy.txt"
}