Compartmentalization is damage control decided in advance: separating your life's contexts so that exposure of one doesn't cascade into the others. It is how a breach of your gaming forum account doesn't reach your employer, and how a pseudonymous byline survives the author's coffee being subpoenaed.
Everyone already does this socially, you don't tell your boss what you tell your doctor. The digital versions just require more deliberateness, because platforms are engineered to join contexts.
The levels
Level 1: separate the logins from the browsing (everyone). One browser (or profile) for accounts that know your name; another for general browsing with stricter settings. Add email aliases per service. Cost: nearly zero. Defeats: most commercial cross-context profiling, breach cascade.
Level 2: separate the identities (pseudonymity). A persona with its own email, username, passwords, and accounts, never touching your real ones. Sufficient against doxxing by other users, casual investigation, and platform data sharing, the realistic adversaries for most people who need a name that isn't theirs (moderators, sex workers, people writing about their employer's industry).
Level 3: separate the infrastructure (anonymity). When the adversary can subpoena or breach providers, accounts aren't enough: dedicated browser sessions (Tor Browser), payment that doesn't chain back (prepaid, appropriately acquired crypto), no shared phone number, hardware or VM separation (Qubes OS exists for exactly this), and no cellular device that travels with the identity. This level is expensive to maintain honestly; claiming it while doing Level 2 is how people get hurt.
The linkage channels
Compartments fail at their joins. The known ways identities get connected:
- Direct reuse: an email, username, phone number, payment method, or password shared across compartments. The most common and most avoidable, see the Ulbricht and AlphaBay cases for the canonical , career-ending versions.
- Network identity: the same IP address serving both identities, one login without Tor or the VPN (Guccifer 2.0) is a durable, logged join.
- Fingerprints: the same browser fingerprint across sessions quietly links them for anyone with visibility into both.
- Content: writing style (stylometry is a real, published technique), repeated phrases, schedule patterns, skills, opinions, life details. The aggregate identifies you even when no single post does.
- Metadata: EXIF in shared images, timezone in timestamps, a contact graph that overlaps.
- Social spillover: the same friends in both compartments, one of whom links the accounts with a mention or a tag.
Making it sustainable
- Fewer, cleaner compartments. Two identities maintained perfectly beat five maintained approximately. Every compartment multiplies bookkeeping.
- Write it down (securely). Which email, which username, which payment, which browser for each compartment, ambiguity produces the fatal "just this once" improvisation. A password manager section per identity works.
- Never migrate anything across. A photo, a phrase you're proud of, a favorite username "just this once", cross-contamination is permanent, and history (archives, caches, breach dumps) never forgets the week your new identity reused the old handle.
- Decide the compartment's birth story. An identity created from your home IP with your everyday browser has a linked past from day one. Build Level 3 identities inside Level 3 infrastructure from the first keystroke.
The Darwin Awards section is, from one angle, a list of compartmentalization failures by people with far stronger incentives than you have. The lesson isn't their sophistication, it's that the joins are where everyone breaks.