Privacy Policy

Last updated: September 12, 2026

This policy explains the information What Is My Municipality collects when you use its location tools, browse the site, or contact us.

1. Location lookups

When you search by address, we send that address to Google Maps services to return municipality, township, time-zone, elevation, and related location information. If you choose the “Use my location” option, your browser asks for permission and sends coordinates to our server only to convert them into a location result. We do not store precise coordinates in our Supabase analytics records.

2. Supabase analytics

We use Supabase to host our private analytics database. For visits to the municipality, township, time-zone, elevation, and coordinate tool pages, we record the tool page, timestamp, a random per-tab session identifier, referrer hostname, and allowlisted UTM campaign parameters. The session identifier is kept in browser session storage and ends when the tab session ends; it is not used for cross-site tracking.

For a submitted lookup, we also record the search method (address or browser-geolocation), a normalized address and available returned location components (such as locality, county, state, postal code, and country), the returned tool result, and whether the lookup succeeded, had no result, or encountered a validation or provider error. This helps us measure whether the tools work and diagnose failures.

To detect aggregate abuse and separate likely automated traffic from likely human traffic, we store a keyed cryptographic hash of the request IP address, a coarse browser family and operating-system family, and an explainable likely-bot flag. We do not store raw IP addresses, full user-agent strings, precise coordinates, full referrer URLs, arbitrary request headers, or query strings other than the listed UTM parameters. Bot classification is an estimate based on missing, known crawler, or automation user-agent tokens; it can be wrong.

Analytics records are written server-side. The analytics tables have row-level security enabled and are not readable or writable by ordinary site visitors. Raw page-view and search-event records are automatically deleted after 90 days. Clearly marked development test records are excluded from reports and removed after verification.

3. Other analytics and service providers

The site also uses Google Analytics to understand general site usage. Google may use cookies or similar technologies under its own privacy practices. Google Maps services process lookup requests as described above. Supabase acts as our analytics database provider and processes only the records described in this policy on our behalf.

4. Contact form

If you use the contact form, we receive the name, email address, and message you choose to provide so we can respond. Do not include sensitive information in a contact message.

5. How we use and share information

We use the information above to provide the requested lookup, operate and secure the site, understand tool performance, improve the service, and respond to messages. We do not sell personal information. We share information only with the service providers needed to operate these functions, when required by law, or with your direction.

6. Your choices and questions

You can avoid sending an address by not using a lookup, decline browser location permission, and control Google Analytics through your browser settings or available opt-out tools. For privacy questions or requests concerning information you submitted through the contact form, please contact us.

7. Changes to this policy

We may update this policy as the service changes. The updated date above indicates when it was last revised.