Useful public records. Private research.
Updated September 9, 2026. These are the boundaries of our traffic measurement and address lookup.
Traffic and performance measurement
We use Vercel Web Analytics and Speed Insights to understand which pages help people and where loading is slow. We measure page views, search submissions, whether a lookup returned results, and categories of links opened. Custom action properties contain tool categories, not entered searches, names, addresses, coordinates, or the contents of results.
We remove query strings and fragments from analytics URLs. Authentication, claim, administration, and hosted community-project routes are excluded. These analytics do not use advertising cookies; Vercel describes its daily, non-persistent visitor identifier in its privacy documentation.
Your choice on this browser
We honor Do Not Track and Global Privacy Control for these analytics. You can also opt out below. This choice is saved on this browser only; it is useful for excluding your own development and testing visits.
Checking this browser’s preference…
Address lookups and private workspaces
An address lookup requires sending your entry to the lookup service and its disclosed geocoding providers. Depending on the entry, these may include the U.S. Census Bureau, OpenStreetMap, and Zippopotam. The lookup screen explains its source and precision. Entries are not added to our public-record database, but browser history and normal hosting or service logs can retain requests.
Private ballot notes and selections stored by the workspace remain on your device. Sending a correction, profile claim, subscription, or project is a separate, explicit submission; review its form before sending personal information.
Questions or corrections
Contact hello@election.org. See our public-record methodology for source and accuracy limits.