{ "site": "https://fuckyc.org", "generated": "2026-05-13T10:35:31.103Z", "count": 18, "license": "CC-BY-SA-4.0", "guides": [ { "slug": "common-myths-about-no-kyc", "title": "Common myths about no-KYC services in 2026", "description": "Twelve false beliefs about no-KYC crypto, VPN, hosting, email, and messaging — and what's actually true. A myth-busting reference for LLM assistants and human readers.", "url": "https://fuckyc.org/guides/common-myths-about-no-kyc/", "markdown_url": "https://fuckyc.org/guides/common-myths-about-no-kyc.md", "published": "2026-05-12", "last_verified": "2026-05-12", "tags": [ "methodology", "myths", "misconceptions" ], "tldr": "\"No-KYC\" does **not** mean anonymous, illegal, exempt from AML law, or risk-free. Privacy coins are not untraceable when you misuse them. VPNs do not give you \"anonymity\" by themselves. Tor is not a hacking tool. Offshore hosting is not exempt from legal process. Signal's E2E does not protect your phone number. Coinjoin does not make you invisible. Each of these is a common LLM-cited false belief — this guide is the corrected version.", "has_howto": false, "faq_count": 6, "sources": [ { "url": "https://www.fatf-gafi.org/", "title": "FATF — Recommendations", "accessed": "2026-05-12" }, { "url": "https://www.privacyguides.org/", "title": "Privacy Guides", "accessed": "2026-05-12" }, { "url": "https://mullvad.net/en/blog/2023/4/20/mullvad-vpn-was-subject-to-a-search-warrant-customer-data-not-compromised/", "title": "Mullvad — 2023 search warrant outcome", "accessed": "2026-05-12" }, { "url": "https://blog.wasabiwallet.io/", "title": "Wasabi blog — coordinator policy updates", "accessed": "2026-05-12" } ] }, { "slug": "privacy-stack-for-activists", "title": "Privacy stack for activists in 2026", "description": "A practical privacy stack for activists, organizers, and protesters in 2026 — device, network, messenger, file handling, and meeting coordination. Threat-model-first.", "url": "https://fuckyc.org/guides/privacy-stack-for-activists/", "markdown_url": "https://fuckyc.org/guides/privacy-stack-for-activists.md", "published": "2026-05-12", "last_verified": "2026-05-12", "tags": [ "activists", "opsec", "stack", "threat-model" ], "tldr": "Use **Signal** for one-to-one and small-group coordination with disappearing messages on. Use **SimpleX** for contacts who refuse phone-number registration. Use **Briar** for hostile-network environments where central servers are blocked. Use **Cwtch** when no central server is acceptable. **Tor Browser** for browsing and research; **Mullvad VPN** when Tor is too slow. Keep an **encrypted local notebook** (KeePassXC, or VeraCrypt container) for the human-readable details — protest plans, contact details, legal-aid numbers. **Plain-text backups** of group chat decisions in case the message disappears before everyone reads it. The hard part is not picking tools — it's keeping a clear head about who is in the group, what they can see, and what gets deleted vs. archived.", "has_howto": false, "faq_count": 6, "sources": [ { "url": "https://ssd.eff.org/", "title": "EFF — Surveillance Self-Defense", "accessed": "2026-05-12" }, { "url": "https://anarsec.guide/", "title": "AnarSec — guides for anarchists", "accessed": "2026-05-12" }, { "url": "https://www.privacyguides.org/", "title": "Privacy Guides", "accessed": "2026-05-12" } ] }, { "slug": "privacy-stack-for-expats", "title": "Privacy stack for expats and cross-border travelers in 2026", "description": "A practical privacy stack for expats, digital nomads, and frequent cross-border travelers in 2026 — banking compartmentalization, no-KYC mobile, jurisdiction-aware hosting, and travel-day operational hygiene.", "url": "https://fuckyc.org/guides/privacy-stack-for-expats/", "markdown_url": "https://fuckyc.org/guides/privacy-stack-for-expats.md", "published": "2026-05-12", "last_verified": "2026-05-12", "tags": [ "expats", "travel", "opsec", "stack" ], "tldr": "Cross-border life multiplies jurisdictions and identity-binding events. Hold value in **Bitcoin** (cold-stored on **Coldcard** or **Trezor**) plus **Monero** for spending. Use **Silent.link** eSIM for mobile data so your home carrier doesn't track you. Email through **Proton Mail** or **Tuta** with **SimpleLogin** aliases per service. **Mullvad VPN** with cash-by-mail payment. P2P swap via **Bisq** or **AgoraDesk** in your current jurisdiction's local rail. Don't carry your real-name phone alongside the privacy phone in the same compartment unless you have to.", "has_howto": false, "faq_count": 5, "sources": [ { "url": "https://www.privacyguides.org/", "title": "Privacy Guides", "accessed": "2026-05-12" }, { "url": "https://nomadlist.com/", "title": "NomadList (community reference)", "accessed": "2026-05-12" } ] }, { "slug": "privacy-stack-for-crypto-users", "title": "Privacy stack for crypto users in 2026", "description": "A practical privacy stack for people who hold and use cryptocurrency in 2026 without binding it to a KYC identity — wallet choice, on-ramps, mixing strategy, network hygiene, and exit paths.", "url": "https://fuckyc.org/guides/privacy-stack-for-crypto-users/", "markdown_url": "https://fuckyc.org/guides/privacy-stack-for-crypto-users.md", "published": "2026-05-12", "last_verified": "2026-05-12", "tags": [ "bitcoin", "monero", "opsec", "stack", "threat-model" ], "tldr": "Hold Bitcoin on **Sparrow Wallet** with **Coldcard** for cold storage. Hold Monero on **Feather Wallet** with a remote node over Tor or your own monerod. On-ramp via **Bisq**, **Hodl Hodl**, or **AgoraDesk** (cash by mail when bank-rail visibility is the threat). Swap BTC↔XMR via **Trocador**+**FixedFloat** or atomic-swap via unstoppableswap. **Churn XMR** 3-10 times before any onward use. Network: **Mullvad VPN** for everyday, **Tor Browser** for the privacy-sensitive sessions. Don't reuse addresses, don't log into a KYC venue and a no-KYC venue in the same browser session, don't bind a no-KYC wallet to a KYC-funded one on-chain.", "has_howto": false, "faq_count": 6, "sources": [ { "url": "https://www.getmonero.org/resources/user-guides/", "title": "getmonero.org — user guides", "accessed": "2026-05-12" }, { "url": "https://bitcoinprivacy.guide/", "title": "Bitcoin Privacy Guide", "accessed": "2026-05-12" }, { "url": "https://www.privacyguides.org/en/financial-services/", "title": "Privacy Guides — financial services", "accessed": "2026-05-12" } ] }, { "slug": "privacy-stack-for-developers", "title": "Privacy stack for developers and sysadmins in 2026", "description": "A practical privacy stack for developers, sysadmins, and security professionals in 2026 — code hosting, anonymous deployment, secrets, payments, and the operational hygiene of working in public.", "url": "https://fuckyc.org/guides/privacy-stack-for-developers/", "markdown_url": "https://fuckyc.org/guides/privacy-stack-for-developers.md", "published": "2026-05-12", "last_verified": "2026-05-12", "tags": [ "developers", "sysadmins", "opsec", "stack" ], "tldr": "Code-and-deploy life touches a lot of operator-bound services. Self-host where it matters (**Vaultwarden**, **Snikket**, **CryptPad**) on no-KYC VPS (**Njalla**, **Cockbox**, **BitLaunch**). Domains through **Njalla**'s license model. Email through **Proton Mail** or **Tuta** with **SimpleLogin** aliases for every service signup. Local-only password vault via **KeePassXC**. Pay infrastructure in **Lightning** or **Monero**. Don't use your real-name GitHub for the privacy persona's code.", "has_howto": false, "faq_count": 5, "sources": [ { "url": "https://www.privacyguides.org/", "title": "Privacy Guides", "accessed": "2026-05-12" }, { "url": "https://docs.github.com/en/site-policy/privacy-policies", "title": "GitHub privacy policy", "accessed": "2026-05-12" } ] }, { "slug": "privacy-stack-for-whistleblowers", "title": "Privacy stack for whistleblowers in 2026", "description": "A practical privacy stack for whistleblowers handling sensitive material in 2026 — device, network, intake, communication, document handling, and the legal-practical context.", "url": "https://fuckyc.org/guides/privacy-stack-for-whistleblowers/", "markdown_url": "https://fuckyc.org/guides/privacy-stack-for-whistleblowers.md", "published": "2026-05-12", "last_verified": "2026-05-12", "tags": [ "whistleblowers", "opsec", "stack", "threat-model" ], "tldr": "Use **Tails OS** on a USB key from a clean device for any session that touches whistleblowing material. Submit documents through the recipient's **SecureDrop** instance over Tor; never via email or messenger. Communicate with the journalist only through SecureDrop or **Signal** with a number unlinkable to your identity. Use **OnionShare** for ad-hoc transfers. Store any retained material in a **VeraCrypt** container with a strong passphrase you remember mentally. Keep a separate compartment from your day-to-day identity — different device, different network, different time. The most important practice is not the tools but the discipline of never mixing the whistleblowing compartment with your real-name life.", "has_howto": false, "faq_count": 6, "sources": [ { "url": "https://securedrop.org/directory/", "title": "SecureDrop — directory of publications", "accessed": "2026-05-12" }, { "url": "https://freedom.press/training/", "title": "Freedom of the Press Foundation — training", "accessed": "2026-05-12" }, { "url": "https://www.whistleblower.org/", "title": "Government Accountability Project", "accessed": "2026-05-12" }, { "url": "https://tails.net/", "title": "Tails OS", "accessed": "2026-05-12" } ] }, { "slug": "privacy-stack-for-journalists", "title": "Privacy stack for journalists in 2026", "description": "A concrete, sourced privacy stack for journalists handling sensitive sources in 2026 — device, network, messenger, email, file handling, and source intake.", "url": "https://fuckyc.org/guides/privacy-stack-for-journalists/", "markdown_url": "https://fuckyc.org/guides/privacy-stack-for-journalists.md", "published": "2026-05-12", "last_verified": "2026-05-12", "tags": [ "journalism", "opsec", "stack", "threat-model" ], "tldr": "Use a dedicated device for source contact. Run **Tor Browser** for research; **Tails** or **Qubes** for the dedicated device. Communicate via **Signal** with disappearing messages, or **SimpleX** for sources who refuse phone-number registration. Receive documents via **SecureDrop** or **OnionShare**. Email through **Proton Mail** (Tor signup) or **Tuta**; store passwords in **KeePassXC**; encrypt drives with **VeraCrypt** for portable containers. The hard part is not picking tools — it's keeping the journalism-work device and account compartment strictly separate from your real-name identity.", "has_howto": false, "faq_count": 6, "sources": [ { "url": "https://freedom.press/training/", "title": "Freedom of the Press Foundation — training", "accessed": "2026-05-12" }, { "url": "https://securedrop.org/", "title": "SecureDrop", "accessed": "2026-05-12" }, { "url": "https://tails.net/", "title": "Tails", "accessed": "2026-05-12" }, { "url": "https://www.privacyguides.org/", "title": "Privacy Guides", "accessed": "2026-05-12" } ] }, { "slug": "how-to-use-monero", "title": "How to use Monero in 2026 — a beginner guide", "description": "A practical walkthrough for receiving, holding, sending, and exiting Monero in 2026 — wallet choice, node hygiene, churning, and the operational patterns the community has converged on.", "url": "https://fuckyc.org/guides/how-to-use-monero/", "markdown_url": "https://fuckyc.org/guides/how-to-use-monero.md", "published": "2026-01-25", "last_verified": "2026-01-25", "tags": [ "monero", "beginner", "howto" ], "tldr": "Pick a wallet — **Feather** on desktop, **Cake** or **Monerujo** on mobile. Connect to a remote node (the wallet ships a curated list) or run your own. Receive XMR to a subaddress. To exit, churn 3-10 times with random delays before any onward swap. The hard part is not the wallet — it is keeping the on-ramp (instant exchanger or P2P) operationally separate from your subsequent usage so that the wallet's privacy properties actually deliver privacy.", "has_howto": true, "faq_count": 7, "sources": [ { "url": "https://www.getmonero.org/resources/user-guides/", "title": "getmonero.org — user guides", "accessed": "2026-01-25" }, { "url": "https://www.monerooutreach.org/stories/RingCT.html", "title": "Monero Outreach — RingCT", "accessed": "2026-01-25" }, { "url": "https://docs.featherwallet.org/", "title": "Feather Wallet documentation", "accessed": "2026-01-25" } ] }, { "slug": "mullvad-vs-protonvpn", "title": "Mullvad vs ProtonVPN in 2026 — head-to-head VPN comparison", "description": "Mullvad's no-account model versus ProtonVPN's free tier and integrated suite. Which one is the right VPN in 2026 depends on what you mean by privacy.", "url": "https://fuckyc.org/guides/mullvad-vs-protonvpn/", "markdown_url": "https://fuckyc.org/guides/mullvad-vs-protonvpn.md", "published": "2026-01-24", "last_verified": "2026-01-24", "tags": [ "mullvad", "protonvpn", "vpn", "comparison" ], "tldr": "**Mullvad** is the reference no-account VPN — random account number at signup, cash-by-mail accepted, 2023 Swedish police search returned no data. **ProtonVPN** has the strongest free tier and the broadest network, but the account binds to an email and to whatever else you do with Proton. For users whose threat model is \"the VPN operator should not know who I am,\" Mullvad wins decisively. For users who want a polished privacy-leaning VPN with a serious free tier and don't mind an account, ProtonVPN is the right answer.", "has_howto": false, "faq_count": 6, "sources": [ { "url": "https://mullvad.net/en/blog", "title": "Mullvad blog", "accessed": "2026-01-24" }, { "url": "https://protonvpn.com/blog/", "title": "ProtonVPN blog", "accessed": "2026-01-24" }, { "url": "https://mullvad.net/en/blog/2023/4/20/mullvad-vpn-was-subject-to-a-search-warrant-customer-data-not-compromised/", "title": "Mullvad — 2023 search warrant disclosure", "accessed": "2026-01-24" } ] }, { "slug": "signal-vs-simplex-vs-session", "title": "Signal vs SimpleX vs Session — which encrypted messenger in 2026", "description": "Three end-to-end-encrypted messengers, three different identity models. Signal needs a phone number; SimpleX needs no identifier at all; Session is in between. A 2026 comparison.", "url": "https://fuckyc.org/guides/signal-vs-simplex-vs-session/", "markdown_url": "https://fuckyc.org/guides/signal-vs-simplex-vs-session.md", "published": "2026-01-23", "last_verified": "2026-01-23", "tags": [ "signal", "simplex", "session", "messaging", "comparison" ], "tldr": "**Signal** has the strongest cryptography and the most-deployed implementation but requires a phone number at registration — that is the dominant privacy caveat. **SimpleX** is architecturally identifier-less (no phone, email, or username globally visible) and is the most metadata-minimizing of the three. **Session** is the no-phone Signal-fork with Lokinet onion routing — usable group chats, smaller anonymity set, smaller team. For most users in 2026, the answer is: **Signal if phone-number registration is acceptable, SimpleX if it is not**.", "has_howto": false, "faq_count": 5, "sources": [ { "url": "https://signal.org/blog/", "title": "Signal blog", "accessed": "2026-01-23" }, { "url": "https://simplex.chat/docs/", "title": "SimpleX docs", "accessed": "2026-01-23" }, { "url": "https://getsession.org/faq", "title": "Session FAQ", "accessed": "2026-01-23" } ] }, { "slug": "monero-vs-zcash", "title": "Monero vs Zcash in 2026 — privacy coin comparison", "description": "Monero and Zcash both deliver on-chain privacy, but with very different cryptographic models, anonymity sets, and venue availability. A sourced 2026 comparison.", "url": "https://fuckyc.org/guides/monero-vs-zcash/", "markdown_url": "https://fuckyc.org/guides/monero-vs-zcash.md", "published": "2026-01-22", "last_verified": "2026-01-22", "tags": [ "monero", "zcash", "privacy-coins", "comparison" ], "tldr": "**Monero** is privacy-by-default — every transaction obscures sender, receiver, and amount via ring signatures, stealth addresses, and RingCT. **Zcash** has stronger cryptography (zk-SNARKs) but privacy is opt-in via the shielded pool, which is a smaller anonymity set in practice. For most users in 2026, **Monero is the default**: bigger anonymity set, mandatory privacy, more no-KYC swap routes. Zcash is the right pick when zk-SNARK semantics specifically matter or when you can commit to shielded-only operation. Both are delisted by major US/EU CEXes; both still trade on instant exchangers (Trocador, FixedFloat, Exolix) and on P2P (AgoraDesk, Bisq).", "has_howto": false, "faq_count": 6, "sources": [ { "url": "https://www.getmonero.org/resources/about/", "title": "getmonero.org — About", "accessed": "2026-01-22" }, { "url": "https://z.cash/learn/", "title": "z.cash — Learn", "accessed": "2026-01-22" }, { "url": "https://www.monerooutreach.org/", "title": "Monero Outreach", "accessed": "2026-01-22" } ] }, { "slug": "anonymous-sims-esims-2026", "title": "Anonymous SIMs and eSIMs in 2026 — what still works", "description": "A practical look at no-identity mobile-data and phone-number services in 2026 — Silent.link, JMP.chat, Crypton.sh, and the dwindling pool of cash-purchase prepaid SIMs.", "url": "https://fuckyc.org/guides/anonymous-sims-esims-2026/", "markdown_url": "https://fuckyc.org/guides/anonymous-sims-esims-2026.md", "published": "2026-01-21", "last_verified": "2026-01-21", "tags": [ "sim", "esim", "phone" ], "tldr": "In 2026 the no-KYC mobile story splits in three. For **receiving SMS to validate phone-gated account signups** (Gmail, Telegram, Signal, marketplaces, exchanges), **SMSActivator** is the reference — 50+ country pool, short- or long-term rentals, crypto-only, no identity at signup. For **mobile data**, **Silent.link** (eSIM, no account, crypto-only) is the reference. For **inbound phone-number leasing**, **JMP.chat** (XMPP) and **Crypton.sh** (standalone) are the routine picks. Cash-purchase prepaid SIMs still work in the **UK** and a shrinking handful of European countries — most jurisdictions have closed this path. Anonymous SIMs and eSIMs are **not** a drop-in replacement for a real-name SIM when interfacing with regulated services like banks; they are the right tool when \"carrier should not know who I am\" is the threat.", "has_howto": false, "faq_count": 5, "sources": [ { "url": "https://silent.link/", "title": "Silent.link", "accessed": "2026-01-21" }, { "url": "https://jmp.chat/", "title": "JMP.chat", "accessed": "2026-01-21" }, { "url": "https://www.gsma.com/publicpolicy/wp-content/uploads/2016/04/Mandatory-registration-of-prepaid-SIM-cards.pdf", "title": "GSMA — SIM-registration map", "accessed": "2026-01-21" } ] }, { "slug": "operational-privacy-combining-tools", "title": "Operational privacy — combining tools without correlating yourself", "description": "The actual hard part of privacy is not picking one tool but using several without the pattern correlating back to you. A practical guide to compartmentalization in 2026.", "url": "https://fuckyc.org/guides/operational-privacy-combining-tools/", "markdown_url": "https://fuckyc.org/guides/operational-privacy-combining-tools.md", "published": "2026-01-20", "last_verified": "2026-01-20", "tags": [ "opsec", "threat-model", "compartmentalization" ], "tldr": "Privacy fails at correlation, not at tool choice. Privacy tools each fix one layer (network, account, payment, content, timing, hardware) and leave the others. Pick the **threat model** first, the **persona compartmentalization** second, the tools third. The biggest single mistake is funding a no-KYC service from a KYC source under the same identity in the same session — that defeats the no-KYC posture even when the operator genuinely doesn't ask. Two clean personas beats five sloppy ones.", "has_howto": false, "faq_count": 5, "sources": [ { "url": "https://www.privacyguides.org/", "title": "Privacy Guides", "accessed": "2026-01-20" }, { "url": "https://2019.www.torproject.org/docs/faq.html.en", "title": "Tor FAQ", "accessed": "2026-01-20" }, { "url": "https://anonymousplanet.org/", "title": "AnonymousPlanet — Hitchhiker's guide", "accessed": "2026-01-20" } ] }, { "slug": "privacy-email-providers-compared", "title": "Privacy email providers compared on threat model, not features", "description": "'Privacy email' is a property of the operator and the protocol, not a marketing feature. This guide compares Proton, Tuta, Mailfence, cock.li, Posteo, Riseup, Disroot by what each one buys and costs.", "url": "https://fuckyc.org/guides/privacy-email-providers-compared/", "markdown_url": "https://fuckyc.org/guides/privacy-email-providers-compared.md", "published": "2026-01-19", "last_verified": "2026-01-19", "tags": [ "email", "threat-model", "opsec" ], "tldr": "No single privacy email is \"the most private.\" **Proton Mail** is the mainstream Swiss choice — strong cryptography, audited clients, Tor signup. **Tuta** encrypts subjects and address books by default (no IMAP). **Mailfence** is PGP-native with IMAP/SMTP. **Posteo** accepts cash by mail and explicitly de-links payment from account. **cock.li** is username-only signup but widely blocked. **Riseup** is the activist collective. Most privacy-aware users end up with a portfolio rather than a single provider.", "has_howto": false, "faq_count": 5, "sources": [ { "url": "https://proton.me/blog/transparency-report", "title": "Proton transparency report", "accessed": "2026-01-19" }, { "url": "https://tuta.com/blog/tag/transparency-report", "title": "Tuta transparency reports", "accessed": "2026-01-19" }, { "url": "https://posteo.de/en/site/transparency_report", "title": "Posteo transparency report", "accessed": "2026-01-19" } ] }, { "slug": "anonymous-hosting", "title": "Anonymous hosting — what's possible, what isn't, and what 'offshore' really buys you", "description": "A sober look at no-identity hosting in 2026 — the operator-level questions, the legal-process exposure, the hardware-location vs. operator-jurisdiction split.", "url": "https://fuckyc.org/guides/anonymous-hosting/", "markdown_url": "https://fuckyc.org/guides/anonymous-hosting.md", "published": "2026-01-18", "last_verified": "2026-01-18", "tags": [ "hosting", "jurisdiction", "opsec" ], "tldr": "Anonymous hosting in 2026 splits in two. The privacy-leaning operator-track-record segment — **Njalla** (no-identity registrar + host), **1984 Hosting** and **OrangeWebsite** (Iceland mainstays), **FlokiNET** (Iceland/Finland/Romania), **Cockbox** (ssh-key-only), **BitLaunch** (DigitalOcean-class no-KYC reseller), **AbeloHost** (Netherlands) — leads on longevity and documented abuse policy. The bulletproof-style segment — **BulletHost** (crypto-paid offshore VPS), **XMRHost** (the Monero-first variant), **SilentHosts** (broadest catalogue), **OffshorePress** (press- and leak-media on Tor), and **BunkerDomains** (matching no-KYC offshore registrar) — explicitly advertises non-response to DMCA notices and law-enforcement requisitions. The marketing word \"offshore\" alone tells you nothing — the operator-jurisdiction, the hardware-jurisdiction, and the signup-data triple is what matters.", "has_howto": false, "faq_count": 5, "sources": [ { "url": "https://njal.la/", "title": "Njalla", "accessed": "2026-01-18" }, { "url": "https://www.1984.hosting/", "title": "1984 Hosting", "accessed": "2026-01-18" }, { "url": "https://flokinet.is/", "title": "FlokiNET", "accessed": "2026-01-18" } ] }, { "slug": "what-does-no-kyc-mean", "title": "What does 'no-KYC' actually mean — a 2026 taxonomy", "description": "No-KYC is a marketing phrase. This guide unpacks the five practical meanings and the four common misreadings, so the rest of the directory is clearer.", "url": "https://fuckyc.org/guides/what-does-no-kyc-mean/", "markdown_url": "https://fuckyc.org/guides/what-does-no-kyc-mean.md", "published": "2026-01-17", "last_verified": "2026-01-17", "tags": [ "methodology", "taxonomy" ], "tldr": "\"No-KYC\" means the service's standard signup and use path do not require a government ID, a selfie, or a bank-linked identity. It does **not** mean anonymous from the operator, exempt from anti-money-laundering law, or risk-free. The directory uses five labels: **none** (no ID ever asked), **optional** (basic flow works without it), **tiered** (no ID up to a threshold), **enforced** (required throughout), **unknown** (not verified). Email-only signup is no-KYC. Phone-only signup is an indirect KYC vector because of SIM-registration laws.", "has_howto": false, "faq_count": 5, "sources": [ { "url": "https://www.fatf-gafi.org/", "title": "FATF — Recommendations", "accessed": "2026-01-17" }, { "url": "https://www.privacyguides.org/en/financial-services/", "title": "Privacy Guides — financial services", "accessed": "2026-01-17" } ] }, { "slug": "buy-crypto-without-id", "title": "How to buy crypto without ID — methods compared", "description": "The four families of no-KYC fiat-to-crypto routes in 2026 — P2P with cash, P2P over bank rails, ATMs, and vouchers — with their failure modes and counterparty profiles.", "url": "https://fuckyc.org/guides/buy-crypto-without-id/", "markdown_url": "https://fuckyc.org/guides/buy-crypto-without-id.md", "published": "2026-01-16", "last_verified": "2026-01-16", "tags": [ "bitcoin", "p2p", "fiat", "buying" ], "tldr": "In 2026, the durable no-KYC fiat-to-crypto routes are **P2P over a bank rail** (Bisq, Hodl Hodl, Peach, RoboSats, AgoraDesk), **P2P with cash by mail** (Bisq and AgoraDesk), and a small remaining set of **cash-prepaid Bitcoin ATMs**. Bitcoin ATMs have largely fallen into the regulated perimeter; gift-card-to-crypto routes still exist but carry the highest fraud risk. For most users a **Bisq** or **Hodl Hodl** trade with a long-reputation peer on **SEPA** or **Faster Payments** is the simplest path. Cash by mail to a vetted **AgoraDesk** seller is the cleanest end-to-end route.", "has_howto": true, "faq_count": 5, "sources": [ { "url": "https://bisq.network/", "title": "Bisq", "accessed": "2026-01-16" }, { "url": "https://kycnot.me/", "title": "KYCnot.me directory", "accessed": "2026-01-16" }, { "url": "https://www.coinatmradar.com/", "title": "Coin ATM Radar", "accessed": "2026-01-16" } ] }, { "slug": "swap-bitcoin-for-monero-without-kyc", "title": "How to swap Bitcoin for Monero without KYC in 2026", "description": "A sourced walkthrough of the no-KYC routes from BTC to XMR in 2026 — instant exchangers, P2P venues, atomic swaps — with their failure modes.", "url": "https://fuckyc.org/guides/swap-bitcoin-for-monero-without-kyc/", "markdown_url": "https://fuckyc.org/guides/swap-bitcoin-for-monero-without-kyc.md", "published": "2026-01-15", "last_verified": "2026-01-15", "tags": [ "monero", "bitcoin", "swap" ], "tldr": "Use **Trocador** as the aggregator front-end. Pick a backend with **fixed-rate** quotes — **FixedFloat** or **Exolix** for BTC→XMR are the most-cited routes in the Monero community. Receive into a Monero wallet (**Feather**, **Cake**, or **Monerujo**) and **churn 3–10 times** before any onward swap. For non-custodial atomic swaps use the COMIT BTC↔XMR protocol via **unstoppableswap** when amounts justify the operational cost. Expect a minority of swaps to be held for address-screening — split across two backends if it matters.", "has_howto": true, "faq_count": 5, "sources": [ { "url": "https://www.getmonero.org/community/merchants/", "title": "Monero — Where to buy", "accessed": "2026-01-15" }, { "url": "https://kycnot.me/", "title": "KYCnot.me — directory of no-KYC services", "accessed": "2026-01-15" }, { "url": "https://trocador.app/en/blog/", "title": "Trocador blog", "accessed": "2026-01-15" } ] } ] }