How we handle visitor data

The near-me lookup uses your browser’s built-in geolocation API to compute the distance from your current position to nearby ALPR cameras. All of this math runs in JavaScript on your device. We never see, log, transmit, or store your coordinates. There is no server endpoint on this site that accepts location data, because we deliberately did not build one.

If you decline the permission prompt, or your device blocks it (Safari on iOS will silently refuse after two denials), the page falls back to a city / ZIP lookup. That path also runs without sending the raw text to any external service - it just matches against our internal metro list.

When you subscribe to a city dossier, we collect the email address you typed and the city you subscribed to. We use Loops.so to send transactional and notification email. We do not sell, share, or rent email addresses. You can unsubscribe from the footer of any email we send.

When you submit a tip via the tip form, we collect the alias you typed, your optional email (hashed with SHA-256 before storage), the message, and any source URL. The hash means we can recognize repeat submissions without ever storing the email in plaintext. Tips go into a moderation queue and are not published until a human reviews them.

Cloudflare Pages records standard request logs (IP address, user agent, request URL) for security and abuse detection. These are retained by Cloudflare under their standard data retention policy; we do not have a separate log store.

We do not use third-party analytics, advertising trackers, or session replay tools. The site has no advertising network integration and no Facebook / Google / TikTok pixel.

The camera locations and tags we surface come from OpenStreetMap, a public, openly-edited map. Every claim on this site links back to the original OSM record so you can verify it yourself and, if needed, dispute it through OSM’s standard community process.

This site is not directed at children under 13 and we do not knowingly collect information from children.

We will update this page if our practices change. The git history of this page is public at github.com/chaifly/flocktracker.

Questions, corrections, or privacy concerns: contact@flockfinder.online