OPSEC for online anonymity.

How to be anonymous online: start with an OPSEC plan

AnonGuide focuses on operational security, or OPSEC: the decisions and routines that help keep an activity separate from an identity. Use this hub as a reading path through threat modeling, anonymity operating systems, browser fingerprinting, and metadata removal. Each guide addresses one part of the same plan, with sources and limits you can inspect.

Begin with a concrete situation. Identify the information you want to keep private, who might obtain it, and the consequences of exposure. Those questions follow the EFF security-planning framework. A useful plan also records what you cannot control and how much effort each protective step requires.

1. Define the threat and the people affected

Read what a threat model is for the basic framework. The threat-modeling guide for journalists and activists extends that exercise to collaborators, sensitive communications, and physical access. Use the threat-model builder to organize your priorities, then read the linked explanations before adopting a recommendation.

2. Review the OPSEC mistakes that link identities

The OPSEC mistakes guide covers account mixing, reused identifiers, and other ways separate activities can become connected. Work through it alongside your own plan. Record which accounts belong together, which need separation, and what should happen if that separation fails. Revisit those decisions when your work, contacts, or devices change.

3. Choose an anonymity operating system for a specific job

The Tails, Whonix, and Qubes anonymity operating system comparison explains different approaches to persistence, network routing, and compartmentalization. Read the constraints as carefully as the features. Use the comparison to identify the problem an operating system addresses and the work that still depends on your accounts, files, and daily decisions.

4. Examine browser and document exposure

Continue with how to prevent browser fingerprinting and removing metadata before sharing files. These guides separate browser identity from network identity, and file contents from hidden properties. Follow the document checklist before sharing a copy, and read each tool's stated limitations before trusting its output.

5. Match communications to the same plan

Read anonymous communication channels by threat model for identifiers and server-visible metadata. The digital-footprint removal guide covers information already published. Treat both as parts of an ongoing process, and keep track of the assumptions each decision depends on.

For provider selection, our sister sites maintain the Tor versus VPN comparison and the no-phone encrypted-email guide. AnonGuide's focus is how those choices fit your anonymity plan. Consult the privacy and anonymity resources for official documentation and the editorial methodology for how these source-based guides are produced.