Searches and address processing
When you submit a city, ZIP code, or address, the browser sends the text in a same-origin POST request to this site. If a Geoapify server credential is configured, the server forwards that query to Geoapify for geocoding and returns a bounded set of U.S. suggestions. The raw query is not placed in the page URL, and application code does not write it to analytics or error metadata. Without a configured provider, the product shows that search is unavailable rather than sending the query elsewhere.
Browser location
The site asks the browser for your location only after you press Use My Location. A successful coordinate is used in memory to request nearby public records. It is not automatically written to the URL, analytics, or issue reports. The explicit Share map view control can create a URL fragment containing a city slug or a map-center coordinate rounded to at most three decimal places. Fragments are not sent to the server in an HTTP request, and the share value represents the viewport center, not retained GPS history.
Maps and third-party providers
When a MapTiler browser token is configured, the browser requests map style and tile resources directly from MapTiler. Those requests can expose ordinary connection information, such as IP address and browser headers, to that provider under its own policy. Without a token, the site displays a local fallback surface and keeps public camera records usable. Links to OpenStreetMap, nearby Street View, source documents, or other external sites take you to services with their own privacy practices.
Analytics, advertising, and replay
The current application does not enable analytics, advertising, session replay, marketing pixels, or consent-dependent tracking. If any of those services are added later, this policy and the consent behavior must be updated before activation. Infrastructure may still process normal HTTP request information needed to deliver and secure the service, but application logging must not intentionally record raw address queries, exact user coordinates, or raw IP addresses.
Rate limiting and security
Public endpoints use short-lived rate-limit keys derived with a server-side HMAC secret. This lets the service limit abuse without storing a raw network address in the rate-limit table. Security and hosting providers may independently process connection data needed to operate their systems. Secrets for geocoding, rate limiting, and databases are server-side and are not intended to appear in public responses.
Issue reports
If you report a problem with a map point, we store the camera record identifier, selected issue type, optional comment, status, and timestamps in a private database table. The report is not an automatic public edit. A comment for a pending or in-review report expires no later than 365 days after submission. Once a report is resolved or rejected, its remaining comment retention is limited to 180 days from review, subject to the database cleanup process and lawful preservation needs. The browser cannot read the report table directly.
Your choices and contact
You can browse without granting location permission, use city or ZIP search instead of an exact address, avoid the share action, and follow OpenStreetMap sources without submitting a report. This prelaunch site does not yet publish a production contact address. A verified contact channel must be added before public launch; until then, the global noindex setting remains in place.