What NearbyCheck sends, and why.

Phone location

If you allow browser location access, NearbyCheck uses the latitude and longitude supplied by your browser to find nearby source-backed places. Those coordinates are sent to NearbyCheck API endpoints when needed to query connected municipal sources. NearbyCheck’s product-event analytics do not include your exact coordinates.

Place search

When you submit a destination search, the search text is sent to NearbyCheck’s geocoding endpoint, which uses OpenStreetMap Nominatim to resolve a Canadian place or address. Search text is not included in NearbyCheck’s coarse product-event analytics.

Maps and directions

The in-page map loads OpenStreetMap tiles. When you choose Directions, NearbyCheck hands the route origin and selected destination coordinates to Google Maps so Google can provide street routing.

Product analytics

NearbyCheck sends a deliberately small set of coarse events so the pilot can identify product gaps without turning location searches into an advertising profile. Allowed event fields include:

• the type of product action, such as a check, map view, evidence view, feedback or directions handoff;
• selected need identifiers such as washroom or parking;
• result count, Now/Later mode, broad source mix and coarse outcome.

Exact latitude/longitude, destination search text, place names and free-text comments are not accepted as product-event fields.

Infrastructure and source providers

Web hosting, mapping, geocoding and municipal-source providers may process technical request logs under their own operational policies. NearbyCheck does not claim that ordinary internet infrastructure produces zero logs. The product instead minimizes what it intentionally sends in its own analytics and avoids user accounts for basic checks.

Pilot status

NearbyCheck is a GTA pilot. Data sources and infrastructure may change as coverage expands. If the data flow changes materially, this notice should change with it.