fuckyc.org

guide · published

Privacy stack for activists in 2026

A practical privacy stack for activists, organizers, and protesters in 2026 — device, network, messenger, file handling, and meeting coordination. Threat-model-first.

The “activist” persona covers a wide spectrum — from a climate-org volunteer organizing a march to someone working in a context where state-level adversaries are the binding threat. This guide assembles tools for the mid-to-high end of that range. Calibrate down if your threat model is lower; calibrate up (and seek operational training) if it is higher.

Threat model#

The default threat model:

The defensive posture is to minimize what each compartment can leak and to keep the group small enough to be auditable. Tool choice matters; tool discipline matters more.

The stack#

Communications#

The right messenger depends on what threat is binding:

Avoid: WhatsApp (Meta operator and phone-number identity), Telegram (default chats not E2E and phone required), Slack/Discord/Teams (operator-readable everything), iMessage (Apple ID).

Network#

Device#

For users in higher-threat environments, two practical options:

For desktop, full-disk encryption (native FDE or VeraCrypt) is non-negotiable. KeePassXC for credentials. Don’t leave the dedicated device logged in.

Files and coordination#

Avoid: Google Docs (subpoenable), Notion (operator-readable), email attachments for sensitive plans (transit metadata visible).

Email and accounts#

Mobile data and account creation#

Movement infrastructure#

If the collective runs public infrastructure (a campaign site, an action archive, a tip-line for sources) the hosting layer needs to match the threat model:

Bulletproof-style hosting is the right fit when mainstream takedown pressure is a recurring risk; the trade-off is shorter operator track records than privacy-leaning hosts like Njalla or 1984.

Operational hygiene#

The single most important practice is compartmentalization. Keep activist accounts, activist phone, activist messenger contacts strictly separate from your real-name identity. Don’t log into your real Twitter from the dedicated device. Don’t carry the dedicated phone alongside your real-name phone unless you have to — co-location across multiple sessions is identifying.

For group coordination:

For physical actions:

What this stack does NOT protect#

See also#

FAQ

What's the single biggest mistake activists make?
Treating private messengers like public Slack channels — admitting too many people to a group, never reviewing membership, never deleting old context. A 200-person Signal group is metadata-leaky and operationally porous. Three-to-six-person tight groups with explicit roles is the durable pattern. Audit membership periodically.
Should I use a burner phone for activism?
Often yes, especially if your real-name phone is tied to your identity in a way that matters in your jurisdiction. For SIM-registration jurisdictions, use a Silent.link or other anonymous eSIM on a separate device. For non-SIM-registration jurisdictions like the UK, a cash-prepaid SIM works.
What about meeting coordination across cities?
Use Signal with disappearing messages on (1 day max). For meeting-prep documents, use OnionShare for transient sharing or CryptPad for collaborative editing. Never use Google Docs or Notion for sensitive plans — both are subpoenable and operator-readable.
How do I keep notes from a protest planning meeting?
KeePassXC for short text-and-credentials. VeraCrypt container on a USB drive for documents. Both decrypt only with a key you hold. Don't sync to cloud unless the cloud is end-to-end encrypted and you accept the operator-trust posture.
Is using Tor or a VPN suspicious by itself?
In some jurisdictions, yes — using Tor places you in a smaller cohort and may attract additional scrutiny under traffic-analysis regimes. The mitigation is to use Tor habitually for routine browsing too, so that Tor use is not anomalous for you specifically. Mullvad Browser used with a regular VPN is a lower-friction alternative when Tor's anomaly cost is too high.
What about the legal side?
This guide is operational, not legal. For protest and activist legal questions, retain or consult a movement-lawyering organization in your jurisdiction (NLG in the US, Bindmans / Liberty in the UK, etc.). Privacy posture is not legal armor.

Sources

  1. EFF — Surveillance Self-Defense · accessed
  2. AnarSec — guides for anarchists · accessed
  3. Privacy Guides · accessed

Referenced by

Topic hubs

Other guides

Quick answers