SKIP TO CONTENT

Security dossier / evidence only

Security practices

This page describes what the project can honestly claim today. It does not invent encryption-at-rest, zero-knowledge architecture, warrant canaries, or live secure intake channels.

Last reviewed

2026-09-13 Current

Claims trimmed to repository-visible behavior.

Secure intake

Coming soon Unavailable

No verified tip channel is live.

Independent audit

None published Unverified

Do not assume pen-test coverage.

Threat context we design against

Readers may face commercial tracking, workplace scrutiny, police interest, or hostile private actors. Guidance on this site prioritizes practical privacy and organizing hygiene. It is not a guarantee of anonymity or safety.

Security evidence ledger

ControlStatusEvidence / note
Transport encryptionIntendedTLS is expected in production reverse-proxy configuration; exact cipher and HSTS details depend on the live nginx/TLS setup.
Client analyticsNot shippedNo first-party analytics, advertising pixels, or fingerprinting scripts are part of the public app code.
Account systemNot presentThis site does not create accounts or store visitor identities for participation or tips.
Sensitive intakeComing soonSecureDrop, PGP, and Signal destinations are not configured. See /secure-contact.
Independent auditNot claimedNo verified third-party penetration-test or audit report is published for this project.

What visitors can do now

  • Prefer hardened browsers and compartmentalized accounts when reading organizing material.
  • Treat category labels on Resistance Wire as feed metadata, not verification.
  • Use the local participation planner at /join — nothing is transmitted.
  • Check /secure-contact for channel status. Intake is coming soon.

Vulnerability reports

A dedicated security intake channel is coming soon. Until then, do not assume this site can receive encrypted vulnerability reports. Prefer established disclosure paths for affected upstream projects when relevant.