Privacy
Privacy Policy
SickMap is designed to reveal patterns without revealing people. Here’s exactly what we store, what we never do, and the controls you always have.
We share insights, not identities
Exact GPS never leaves your device. Reports are fuzzed, snapped to a neighbourhood hex, and only surfaced publicly once at least three distinct reporters share the same hex.
What we collect
Account basics
Your email and a chosen username, used only for authentication and managing your account. These are never shown next to your reports.
Your symptom reports
The symptoms you select, a 1–5 severity, when they started, any free-text "something else" description, and a fuzzed location captured at submission time.
Remedies
Any remedies you share or upvote inside a cluster, so other people with the same symptoms can see what worked in your area.
What we never do
Sell identifiable health data
Aggregated, de-identified insights may inform public-health research; individually identifiable records never leave our database.
Share your exact GPS
Your precise coordinates stay on your device. We randomize by ~300 metres before anything is stored, then snap to a neighbourhood-level hex grid (H3 res 8).
Attach your identity to public clusters
Usernames, emails, and avatars never appear on the map or inside cluster detail views. Other users see anonymized cards only.
Post on your behalf
SickMap has no "share to social" surface. Nothing you report goes anywhere except our database under your row-level-security-protected account.
Your rights
Export everything
Pull a full copy of your reports, remedies, and account data as structured JSON, self-serve from Profile.
Delete everything
Permanently remove your account and every associated report in one click. Deletion cascades across related tables — no orphaned data.
Revoke consent or lodge a complaint
Under Washington’s My Health My Data Act, the California Consumer Privacy Act, and the EU GDPR you can revoke consent at any time and escalate to your regulator if we fall short.
Security
Data is encrypted in transit (TLS) and at rest. Row-level security in Postgres means you can only read and modify your own records — aggregate cluster counts are the only thing other users can see.