Privacy

This site is used by people who may be questioned about what they read and write. The privacy design follows from that, and it is enforced in the code rather than promised in prose.

What we never store

• IP addresses — no table in the database has a column that could hold one.
• User agents, screen sizes, or any browser fingerprint.
• Accounts, email addresses, or any way to contact you.
• Cookies. The site sets none, for any purpose.
• Analytics of any kind, first- or third-party.

What we do store

• The structured answers you chose and the text you wrote.
• The checkpoint and the date of your crossing — never a time of day.
• The hour, not the minute, at which the report was submitted.
• A hash of your retraction token, so the token itself is not recoverable from our data.

Spam protection without a third party

Instead of a hosted captcha, your browser solves a small proof-of-work puzzle served by this site. No request leaves for any other domain — no captcha vendor, no CDN, no fonts, no telemetry. The page works over Tor and VPNs, and the content security policy blocks any external origin outright.

Rate limiting

Rate limits need some notion of "the same sender". We derive one by hashing the address block your request arrived from together with a secret that rotates daily, and we keep it only in memory. It is never written to disk, never logged, and cannot be linked across days or joined against any stored report.

Writing safely

The largest remaining risk is what you type. A detail like an exact time, a car model and a route can identify you even without a name. Reports containing phone numbers, emails, document numbers or names of individuals are held for review automatically — but please do not rely on that filter.