We Should Go is built so there is almost nothing to have a privacy policy about. We do not run accounts, we do not have a database of users, and your plan never touches our servers. This page spells out exactly what that means.
Everything you create in the app, bug-out locations, family and medical details, checklists, comms plan, and saved quiz results, is stored locally in your browser/app storage on your device. It is not uploaded anywhere. If you export an encrypted plan file, that file is yours to store wherever you choose; we never receive it.
Your sensitive plan data is encrypted at rest using Argon2id + AES-256 with a key derived from your passphrase/PIN. We cannot read it, and neither can anyone who only has the file.
The optional address lookup in the Bug-Out planner is the only feature that contacts the network with anything you typed. When you tap "look up," the single address or coordinates you entered are sent through our own Cloudflare Worker to OpenStreetMap services (Nominatim, OSRM, Overpass) to fetch coordinates, drive times, and nearby points of interest.
The app and that Worker are hosted on Cloudflare (Pages and Workers). As with any website, Cloudflare may process standard technical request data (such as IP address and request metadata) to deliver the site, run its CDN, and protect against abuse, under Cloudflare's own privacy terms. We do not add our own analytics or logging on top of that, and we do not receive a feed of who visits.
The app links out to third-party sites that have their own privacy policies, including:
We do not control those sites and are not responsible for their practices.
We Should Go is a general-audience preparedness reference and is not directed at children under 13. It collects no personal information from anyone, including children.
If this policy changes, we will update it here and change the "Last updated" date above. Material changes will be noted in the app.
Questions about privacy? Email [email protected].
The protections described here are built on audited, open-source cryptography libraries. See the Security & how it works page for the technical details.