TZM-PRV · policy & OPSEC

Privacy & anonymity — torzonmarket.link and Torzon access

This page has two jobs. First, it states what torzonmarket.link does and does not collect as a clearnet directory. Second, it explains how to configure anonymity in practice before you touch mirrors, wallets, or market login — because reading a guide on the normal internet is not the same as staying private inside Tor.

We are not lawyers; laws differ by country. Nothing here encourages illegal activity. Anonymity tools reduce exposure — they do not grant immunity.

Scope

Market passwords, escrow, and vendor mail never belong on this domain. For hosts use Links; for Tor install use Access; for BTC/XMR timing use Wallet.

Publisher · data on this site

What torzonmarket.link collects

Torzon Market runs torzonmarket.link as a static guide hub. We do not operate Torzon market accounts, do not see your Torzon login, and do not receive deposits sent to market addresses.

Data	Where	Purpose
Optional client prefs	Browser `localStorage` / `sessionStorage` if you use them elsewhere	We no longer store a blocking age-gate flag; mirror tables render without a modal
Mirror table JSON	Downloaded from `/data/mirrors.json` on Home/Links only	Render the published trio in your browser; no account required
Verifier paste	Processed in your browser only	Compare paste to our index; we do not receive the paste on a server we control unless your host logs client-side requests (static site — no form POST to us)
BTC/XMR spot prices	Your browser calls public APIs (CoinGecko, Binance, Kraken fallback)	Topbar reference pills; those providers see your IP and may log requests
Web fonts	Google Fonts may load if enabled in CSS	Typography; Google may see IP and referrer
Hosting / CDN logs	Your hosting provider or CDN	Typical access logs: IP, user-agent, URL, time — governed by your host’s policy, not ours in code

No accounts. We do not offer registration, newsletters, or comment boxes on torzonmarket.link.
No market cookies. Session cookies for Torzon exist only on .onion services inside Tor Browser — not here.
No selling data. We do not run ad pixels or analytics packages in main.js as shipped in this repository.
Last updated. Policy text reflects the site as of 2026-10-11. Material changes should bump this date in prose when you deploy.

Anonymity · basics

Threat model — who are you hiding from?

“Anonymous” is not one switch. List who you worry about: ISP or mobile carrier, employer or school network, cloud sync on your PC, phishing sites, blockchain analysts, law enforcement with legal process, or casual deanonymization via reused usernames and photos.

Tor Browser mainly protects against local network observers and remote sites learning your home IP when you browse .onion services. It does not fix reused passwords, KYC exchanges tied to your name, or you posting the same nickname on clearnet social media and a market profile.

Reading torzonmarket.link on Chrome without Tor reveals to your ISP that you visited this domain. That is separate from loading Torzon on an onion. Treat clearnet research and onion sessions as different compartments (see below).

Tooling · Tor Browser

Configure Tor Browser correctly

Install only from the official Tor Project site — verify signatures or installer hashes when your OS supports it. Reject “Tor VPN” bundles from ads or Telegram.
Keep Tor Browser updated — outdated clients fail on v3 onions and miss security fixes.
Security level: use Safest (or the strictest practical level) for market access. Accept broken video, scripts, and some UI glitches — that is the trade-off.
Do not install extra extensions in Tor Browser (password managers, ad blockers, “privacy” add-ons). They fingerprint you and widen attack surface.
Full screen: avoid maximizing to exotic resolutions if you are paranoid about fingerprinting; default Tor window sizing is intentional.
Bridges / censored networks: if Tor is blocked, use built-in bridge configuration from Tor Project — not random bridge lists in chat.
System clock: large skew breaks Tor; sync time before blaming mirrors.
Downloads: open files only after you understand the risk; malware loves “Torzon installer.exe” on clearnet.

Step-by-step install and first-load habits: Access.

OPSEC · separation

Compartmentalize clearnet, Tor, and money

Use separate contexts so a mistake on the normal web does not burn your onion identity.

Dedicated Tor Browser profile or machine for market activity — not the same Firefox/Chrome profile where you read Gmail and Twitter.
Never log into personal Google, Apple, or Microsoft accounts in the same Tor Browser session you use for sensitive onions.
Separate email created and accessed only over Tor if the market requires mail — do not forward to your real inbox.
Unique usernames and passwords per service; a password manager is fine on clearnet for random sites, but do not sync market credentials into cloud accounts tied to your real name.
Bookmarks: bookmark onions only inside Tor Browser after your anti-phishing phrase looks correct — see Access · login & phrase.
Clearnet directory use: if you must read torzonmarket.link on a normal browser, accept that your ISP sees the visit; do not type market passwords here or paste deposit addresses from this domain (we never publish them).

Clearnet · while researching

Habits on the normal internet

Do not use “Tor gateways” or Tor2web proxies for login — they see traffic and URLs; use Tor Browser end-to-end.
Telegram / Discord / Reddit pastes are untrusted until they match Links and your phrase after login.
Search ads for “Torzon login” often lead to phishing on .com — see anti-phishing notes on Links.
Cloud clipboard sync (iPhone/macOS Handoff, Google Clipboard) can exfiltrate onion strings you copied — disable or isolate before copying v3 hosts.
Screen sharing and remote desktop during Tor sessions expose windows you meant to keep local.

Onion · session discipline

Staying anonymous on the market host

Once Tor Browser loads a verified v3 from our table, anonymity becomes mostly about behavior and payment choice.

URL bar every time — read all 56 characters before password entry; clipboard malware swaps the middle of strings.
Personal phrase + PIN — if phrase missing or wrong, close tab and restart from Links; do not “try anyway.”
PGP for high-volume or sensitive mail — learn key handling on clearnet first, then use keys only in your Tor compartment.
Do not reuse market photos or writing style on clearnet social accounts if unlinkability matters to you.
Support mail to torzonmarket.link (if you use it) is clearnet — do not include order IDs, tracking, or real name unless you accept that exposure.

Verifier semantics (index match ≠ online): Links · verifier.

Money · traceability

Payments and financial anonymity

Coin choice and sourcing matter as much as Tor. Full confirmation tables: Wallet · deposits.

Asset	Privacy note	Practical habit
Bitcoin (BTC)	Public ledger — addresses and flows can be linked over time	Use fresh addresses per deposit; avoid reusing wallets tied to KYC exchanges; send from non-custodial wallets you control
Monero (XMR)	Stronger default privacy on-chain; still not magic if you KYC at entry/exit	Prefer for unlinkability when policy allows; still wait for required confirmations
Exchanges	Know-your-customer links real identity to withdrawal addresses	Assume any KYC exchange can tie you to outbound TX; plan accordingly
Walletless invoices	One-time addresses still visible on-chain (BTC) or in your wallet history	Pay only on verified onion; never pay an invoice screenshot from chat

Withdrawal PIN separate from login — set before large balances. Details: Wallet · withdrawals.

Leaks · beyond Tor

Metadata and side channels

Screenshots may include onion URLs, usernames, or EXIF GPS from phone camera rolls — scrub before sharing.
Phone backups (iCloud, Google Photos) can copy Tor Browser data if you misconfigure mobile — desktop Tor Browser is the usual path for this hub’s readers.
DNS on clearnet — visiting torzonmarket.link leaks the domain to resolver/ISP; using DoH in Chrome does not hide intent from the site you hit.
File metadata in dispute uploads — strip documents before uploading inside market disputes.
Wi‑Fi — untrusted hotspots plus HTTP (not applicable to .onion market TLS inside Tor) still risky for clearnet browsing; prefer trusted networks or offline reading of exported guides.

VPN · common question

VPN plus Tor — when it helps and when it hurts

VPN → Tor (connect VPN first, then Tor Browser): hides Tor use from local ISP; VPN provider sees you use Tor. Choose a provider you trust more than ISP, or do not use one.

Tor → VPN (generally discouraged for most users): exit from Tor into a VPN adds complexity and can reduce Tor’s threat model benefits unless you know exactly why you need it.

Free VPNs often monetize traffic — avoid for sensitive work.

For many readers, Tor Browser alone on Safest plus compartmentalization beats a random VPN marketed on YouTube.

Advanced · optional

Stronger anonymity setups

Tails (amnesic live OS) — boots from USB, routes traffic through Tor, leaves minimal local traces when shut down.
Whonix — isolates Tor gateway from workstation VM; good for persistent workflows with careful discipline.
Dedicated hardware — cheap laptop used only for Tor market access, never for personal browsing.
Physical OPSEC — shoulder surfing, unlocked devices, and shared PCs defeat software anonymity.

These add maintenance cost. If you are new, finish Access and Links · checklist before jumping to live OS tooling.

Failures · patterns

Mistakes that deanonymize people

Logging into Torzon from a “Tor browser” app that is not official Tor Browser.
Using the same password as clearnet email or banking.
Paying a deposit address from a screenshot without matching the URL bar v3 to Links.
Assuming BTC is “private enough” because the market accepts it.
Pasting from an old Telegram message without re-verifying against today’s table.
Contacting “support” on random .com domains that ask for mnemonic or PIN.

Your control · EU / UK readers

Choices and contact

Because we do not operate user accounts, there is no profile to export or delete on our servers. Clearing localStorage for torzonmarket.link only affects any optional client-side prefs your browser still holds — not mirror data, which is public in HTML and JSON-LD.

Hosting access logs may exist at your CDN — retention depends on infrastructure you choose when deploying this static site.

Questions about this policy or mirror paste hygiene: use directory support channels referenced on Links (editorial section). We cannot access Torzon escrow or accounts.

Continue to Tor access guide