Privacy
Plain-English notes on what we do (and don’t) collect.
Quick summary
- No accounts. No names. No emails. No ad trackers.
- Your post is stored with optional coarse location only.
- We keep a salted hash of your IP for abuse-prevention and rate limiting.
- Outputs are aggregated visualizations; we may share or license aggregate, de-identified insights in the future.
What we collect
- Your submission (“gripe”) — the text you type.
- Optional location — country and region/state/province codes, plus a coarse postal area:
- US: ZIP3 (first 3 digits)
- Canada: FSA (first 3 characters)
- Switzerland: first 2 digits of PLZ
- Abuse-prevention hash — a SHA-256 hash derived from your IP address, a server-side salt, and (in normal operation) the current day. This lets us enforce a “one submission per day” limit without storing your raw IP.
What we do not collect
- No names, emails, phone numbers, or precise addresses.
- No full postcodes. No raw IP addresses in the database.
- No third-party trackers or advertising beacons.
How the IP hash works
To prevent spam and keep the signal useful, we derive a hash on the server: sha256(IP + secret_salt + day). Because the salt is secret and the day rotates, this hash is not reversible and changes daily. During occasional testing we may temporarily use a non-rotating variant, but it’s still salted and hashed.
Cookies & analytics
- We don’t set tracking cookies.
- We don’t run third-party analytics that profile you.
Where your data lives
The app is hosted on Vercel and data is stored in Supabase (Postgres). Both use HTTPS in transit and encryption at rest. We apply database Row Level Security and server-side inserts to protect write paths.
How we use your data
- To display aggregate charts and counts (e.g., by region or day).
- To enforce rate limits and prevent abuse.
- To improve the service. We may share or license aggregate, de-identified insights in the future. If our practices change, we’ll update this page.
Retention
- Submission text and coarse location: kept indefinitely for aggregate analysis.
- Abuse-prevention hashes: stored with each submission; daily rotation in normal ops.
- Infrastructure logs (e.g., Vercel/Supabase) may briefly include IPs for security and debugging; retention is governed by those providers’ defaults.
Your choices
- You can post without location details.
- If you want a submission removed, email us with the text and approximate date/time so we can locate it. Because posts are anonymous, that information helps us find the correct entry.
Contact: admin@discontentindex.com
Children’s privacy
This project isn’t directed to children under 13 (or 16 in some regions). Please police your children's internet usage.
Changes to this policy
We may update this page as the project evolves. We’ll keep an updated date here and publish meaningful changes.
Effective date: 2025-09-01