Privacy policy

Last updated: May 18, 2026

Overview

Govia helps you build driving routes and explore sights along the way. This policy describes what information is processed when you use the app, how cookies and local storage work, and which third-party services may receive data.

Information you provide

When you search for places, import GPX files, or plan routes, that content is sent to our servers so we can geocode locations, calculate directions, and (when enabled) find points of interest. We use this data only to respond to your requests in the session; we do not sell your search or route data.

Storage on your device

With your consent, functional storage saves routes, GPX imports, and related preferences in your browser's localStorage so your work persists between visits. If you reject non-essential cookies or withdraw functional consent, that local data is cleared.

A necessary consent cookie (govia_cc) remembers your cookie choices.

If you opt in to analytics on a Vercel-hosted deployment with Web Analytics enabled, aggregated page views may be sent to Vercel. Withdraw analytics consent in Cookie settingsto stop new collection. Analytics stay off unless you enable that category or choose "Accept all."

Analytics (optional)

When this app is deployed on Vercel with Web Analytics enabled and you opt in, we use Vercel Web Analytics to collect aggregated page-view information — for example which pages are visited and referrer. We do not send your route searches, GPX file contents, or place names as part of default page tracking.

Vercel processes this data under its own Privacy Policy. You can withdraw consent at any time via Cookie settings in the Govia menu; that stops new analytics collection.

Third-party services

Depending on configuration, the app may send requests to:

  • Google — Maps JavaScript API (map display); Places API (search and sights) when configured
  • Vercel — Web Analytics when you opt in to analytics on a Vercel deployment (see Analytics)
  • OpenRouteService or OSRM — driving directions
  • OpenStreetMap / Overpass — sights when Google Places is not configured
  • Wikimedia — optional ranking signals for OSM sights

Each provider has its own terms and privacy practices. See COMPLIANCE.md in the project repository for attribution and compliance notes.

Your choices

You can open Cookie settings from the menu in Govia at any time to accept, reject, or change non-essential categories. You can also clear site data in your browser to remove stored routes and consent state.

Changes

We may update this policy as the product changes. The date at the top reflects the latest revision.

Contact

Questions about privacy can be directed to the site operator listed in the Govia footer, or via the contact details published with this deployment.