Privacy and data use

Updated November 19, 2026

Browser location

When you choose “Use my location,” your browser asks for permission if needed and provides a one-time location to find nearby permits. We do not continuously track you or save your search location to our database. Browser location can be approximate; you can always search by address instead.

Browser-location searches send coordinates to this site. For locations in our search area, our server also sends those coordinates to Photon, a service run by komoot using OpenStreetMap data, to fill the search box with a nearby street address. The address can be approximate; permit distances and the map always use the original browser coordinates. Photon receives the coordinates and our server's request, which are subject to its service practices. We do not send it your browser cookies or client IP address. If an address cannot be found, the coordinate search still works.

Coordinates and any returned address appear in the search link and can remain in browser history or be seen by anyone you share the link with. Opening a shared link searches that saved point without requesting the recipient's location. Editing or submitting the address form starts a normal Census address search.

The request-logging qualifications below also apply to browser-location searches.

Address searches

Your entered address is sent to the U.S. Census Geocoder to find coordinates. Search links contain the entered address, coordinates, filters and search timestamp so you can share or revisit results. These links can remain in browser history and can be seen by anyone you share them with.

Rails request logging filters the address and coordinate parameters. This does not remove older logs or guarantee that hosting or proxy access logs omit URLs. Operational logs may include IP addresses, request times and errors. We do not promise a fixed deletion period for all operational logs.

Geocoding rate-limit counters use a keyed hash of the client IP address, rather than the raw address, and expire as later searches clean up old counters.

Analytics and cookies

When enabled, Google Analytics measures page visits, search attempts, result counts and search outcomes. It uses analytics cookies and browser/session measurement. Our event payloads omit entered addresses, coordinates, contact details, URL queries and address-bearing page titles. Permit-page events identify the public permit by its page path and ID.

Advertising personalization and Google Signals are disabled in this integration. The site does not currently provide a cookie-consent interface. You can use browser privacy settings or analytics-blocking tools; search remains available when analytics is blocked.

The application also uses session cookies for features such as request security and temporary messages.

Maps and public records

Your browser requests basemap resources from OpenFreeMap, which can receive your IP address and the map tiles requested. Ward boundaries and the map software are served by this site.

Permit details, including contact information supplied in the source record, come from public City datasets. The site stores original source records and may send permit information to an AI provider to generate summaries. Entering an address search does not itself generate an AI summary.

Contact

For privacy questions or concerns about information displayed here, view our contact details.