JUST ANSWER : NO, YOU DON´T NEED THAT INFORMATION! NEVER BE SO UNIQUE THAT YOU'RE EASY TO TRACK 

     ___                         ___           ___           ___     
    /  /\          ___          /  /\         /  /\         /  /\    
   /  /::\        /  /\        /  /::\       /  /::\       /  /::\   .....................sito....
  /  /:/\:\      /  /::\      /__/:/\:\     /  /:/\:\     /  /:/\:\  
 /  /:/  \:\    /  /:/\:\    _\_ \:\ \:\   /  /::\ \:\   /  /:/  \:\ 
/__/:/ \__\:\  /  /::\ \:\  /__/\ \:\ \:\ /__/:/\:\ \:\ /__/:/ \  \:\.....................hack....
\  \:\ /  /:/ /__/:/\:\_\:\ \  \:\ \:\_\/ \  \:\ \:\_\/ \  \:\  \__\/
 \  \:\  /:/  \__\/  \:\/:/  \  \:\_\:\    \  \:\ \:\    \  \:\      
  \  \:\/:/        \  \::/    \  \:\/:/     \  \:\_\/     \  \:\     
   \  \::/          \__\/      \  \::/       \  \:\        \  \:\    .....................sito...
    \__\/                       \__\/         \__\/         \__\/

OPSEC Rule #1

Do not open random links (especially Tor/onion links) without an isolated/disposable environment (e.g., Whonix VM or similar). Treat collaborative pads as untrusted.

Contents

General: Threat Modeling & OPSEC Privacy: Computer & Internet Systems: OS / Firmware / Encryption Software: Browsers / Messaging / Tools Private Services: VPN / Search / Hosting Real World: Money & Payments Logistics: Addresses & Numbers Travel Notes Further Reading Unsorted Links

General

Back to top

Threat Modeling

Define your adversary, capabilities, constraints, and what “loss” looks like. Then pick controls that match your reality, not someone else’s checklist.

  • Identify assets (identity, location, devices, money, relationships).
  • Map exposure points (accounts, metadata, habits, comms paths).
  • Decide acceptable risk and operational budget.

OPSEC Principles

Reduce correlation. Reduce uniqueness. Reduce persistent identifiers. Avoid routine patterns that allow easy clustering.

  • Never be so unique that you’re easy to track.
  • Never answer the phone; only call back (reduce unsolicited exposure).
  • Assume observation; choose defaults that minimize leakage.
OPSEC “Bible” onion references (as shared)

Treat onion links as untrusted and open only in isolated environments.

  • opbible7nans45sg33cbyeiwqmlp5fu7lklu6jd6f3mivrjeqadco5yd.onion
  • jqibjqqagao3peozxfs53tr6aecoyvctumfsc2xqniu4xgcrksal2iqd.onion
Personal Security Checklist (GitHub)

Privacy: Computer & Internet

Back to top

Phones: Practical Constraints

Modern society increasingly pressures proprietary, identity-linked mobile apps (health, banking, “exclusive discounts”, etc.). Your approach depends on threat model.

  • Banking app compatibility on custom ROMs: compat report
  • Consider whether living without a SIM is feasible for your use-case.
  • For mobile forensics resistance, Pixel + GrapheneOS was discussed as a pragmatic path.

Custom ROMs (Mobile OS)

Recommended

Notes / Caveats

  • LineageOS may improve privacy, but security defaults and patch cadence depend on device/port.

Systems: Firmware, OS, Encryption

Back to top

Software

Back to top
PrivacyGuides Tools Directory

Private Services

Back to top

VPNs (as discussed)

Common picks

The pad included debate and contested claims about some providers. Treat VPN choice as threat-model dependent.

Search Engines

  • DuckDuckGo Onion Service (get authentic link via DuckDuckGo’s official sources)
  • Kagi / Orion (mentioned for functionality, not privacy)
  • SearXNG (self-host)

Replace Common Trackers

Service Replace with
Spotify Jellyfin, Spotube, Navidrome
Google Maps OSM / osm.org

Real World: Money & Payments

Back to top

P2P & KYC-Reduction (as listed)

  • kycnot.me (directory)
  • Bisq
  • Haveno
  • Peach was mentioned as P2P for Bitcoin (verify availability in your region).

Logistics: Addresses & Phone Numbers

Back to top

Phone Numbers & SIM Notes (country-specific)

The pad listed non-KYC SIM availability by country, plus services for eSIM and SMS receiving. Treat this as rapidly changing; verify locally.

Recommended reading from the pad: “Kill the cop in your pocket” at anarsec.guide (see below).

PII Minimization: Basic Notes

  • Reduce unnecessary personal data in forms and accounts where legally and practically possible.
  • Be aware of name-recovery risks in payment rails (country-specific and evolving).
  • Separate identities by context; avoid reusing identifiers across contexts.

Travel Notes (Practical)

Back to top

Tickets & ID Checks

  • Buying tickets at cash desks is becoming rarer, but was suggested as a lower-data option.
  • Some operators require ID checks matching ticket name. Example reference from the pad:
  • SNCF travel documents policy

Cars & Connectivity

  • Modern cars collect and transmit data; older vehicles were suggested as simpler from a data-minimization standpoint.
  • Be mindful of embedded connectivity; understand implications before modifications.

Further Reading

Back to top

Books (as listed)

  • Shoshana Zuboff — The Age of Surveillance Capitalism
  • Cal Newport — Digital Minimalism
  • Byung-Chul Han — Transparenzgesellschaft
  • Bruce Schneier — Data and Goliath
  • JP Aumasson — Serious Cryptography (2nd ed)
  • Michael Bazell — Extreme Privacy (4th ed., 2022)

Unsorted Links

Back to top

Onion references (as listed)

Treat as untrusted; open only in isolated environments.

  • tortaxi2dev6xjwbaydqzla77rrnth7yn2oqzjfmiuwn5h6vsk2a4syd.onion
  • njallalafimoej5i4eg7vlnqjvmb6zhdh27qxcatdn647jtwwwui3nad.onion
  • kycnotmezdiftahfmc34pqbpicxlnx3jbf5p7jypge7gdvduu7i6qjqd.onion

Next Modules

Keep structure consistent across subpages (OPSEC, DARKWEB, RECON, etc.).

Threat Modeling Hardened OS Messaging Private Services Further Reading