Privacy policy / evidence only
Privacy policy
Good Trouble Resistance aims to minimize data collection. This policy states only what we can support from the public application and current operations. Unsupported retention, subpoena, and encrypted-inbox claims have been removed.
Last updated
Policy rewritten around verifiable behavior.
Visitor accounts
No signup or identity vault exists here.
Secure contact
Channel registry is unpublished / unavailable.
Core principles
- Collect as little as practical to publish guides and aggregate public RSS.
- Do not sell visitor data.
- Prefer browser-local tools for quizzes and planners.
- Label unavailable contact channels as unavailable or coming soon.
Data handling ledger
| Data class | Status | Note |
|---|---|---|
| Server / reverse-proxy logs | Possible | Hosting and nginx may retain standard access logs. Retention is controlled by server operations, not by a visitor account UI. |
| Contact forms / tip inbox | Coming soon | No contact form submits identity to this project today. Secure intake is coming soon. |
| Browser local storage | Local only | Optional preferences such as feed filters or threat-model progress may stay on your device. |
| Third-party analytics | Not used in app | The public client does not ship Google Analytics, ad pixels, or social tracking scripts. |
What we do not collect through this app
- No advertising cookies or marketing pixels from this codebase.
- No cross-site behavioral profiles created by Good Trouble Resistance scripts.
- No participation identity — /join stays on-device.
Third parties
External links (EFF, Tor Project, news publishers, tool vendors) have their own policies. RSS requests may pass through this site’s allowlisted proxy to configured publishers. Infrastructure providers (hosting, reverse proxy, TLS) can see standard connection metadata.
Your choices
- Browse with Tor or a hardened browser if you need stronger anonymity.
- Clear site data in your browser to remove local preferences.
- For privacy questions about this project: contact channels are coming soon. Check /secure-contact for status.
- Practical hardening guidance remains on /privacy.
Changes
Material updates to this policy should appear in the public repository history. Continued use after an update means you have had an opportunity to review the revised text.