Privacy information

Use my location

DriveLocally does not request device location automatically. If you choose Use my location in the planner, your browser may ask permission to share its current location with the page.

The returned latitude and longitude are compared in your browser with static DriveLocally city and approach reference points. The coordinates are not stored in local storage or session storage, are not included in DriveLocally analytics, are not sent to a DriveLocally application server, and are not added to the Google Maps URL. If switching cities requires a reload, only the inferred city and approach are carried across that navigation.

When you later open Google Maps with the starting field blank, DriveLocally still omits the Maps origin parameter. Google Maps may independently use your current location under Google's own permissions and privacy practices.

Google Analytics

DriveLocally uses Google Analytics 4 with measurement ID G-C614HRER6Y for page views and a small set of allowlisted interface interactions. Google Signals and ads-personalization signals are disabled in the site configuration. Google Analytics may use first-party cookies or similar identifiers and receives ordinary technical request information under Google's own terms and privacy practices.

DriveLocally's custom analytics events are limited to page type, CTA label, route ID, form name, city ID, city status, experiment ID and variant ID. They do not include browser geolocation coordinates, user-entered starting places, route destinations or waypoints, Google Maps export URLs, route-report free text or email content. Automatic outbound-link measurement must remain disabled in the Google Analytics web-stream settings so generated Google Maps URLs are not collected as link_url values.

External services

Opening a Google Maps link sends the route locations and any optional manually entered origin to Google Maps under Google's own terms and privacy practices. When the origin is omitted, Google Maps may request or use device location independently. Standard web-server logs may record technical request data such as IP address, user agent, requested path and timestamp for security and operations.

Route issue reports

The route issue form is processed in the browser and opens an email draft. The website does not upload or store the report text. Nothing is sent until the reporter presses Send in their email application.

A sent report shares the sender address, report content and ordinary email metadata with DriveLocally and the email providers involved. The form does not request a name, phone number, precise home location, vehicle identifier, licence information or payment information. Source emails are removed within 90 days after the report is closed unless a documented operational, security or legal reason requires longer retention; the route issue summary may be retained without the sender address.

Last updated: August 12, 2026.