Privacy Policy

To calculate a meeting point, the app needs the starting locations you type in. That processing happens in your browser. To turn what you type into coordinates and driving times, your browser sends those locations directly to the mapping and routing services described below.

We do not run a server that receives, logs, or stores the addresses or places you enter, and we do not keep a history of your searches. When you close or reload the tab, that information is gone unless you have saved a share link yourself (see Sharing a result below).

Two external services do the mapping and routing work, and your browser talks to them directly:

• Google Maps Platform. Used to draw the map, suggest addresses as you type (Places Autocomplete), turn addresses into coordinates (Geocoding), measure driving times (Distance Matrix), and find nearby towns (Places). The locations you enter and the map area you view are sent to Google to provide these features. Google's handling of that data is governed by the Google Privacy Policy.
• OpenStreetMap-based routing (OSRM). For some trips the app measures driving times through an OpenStreetMap routing service instead of Google. Only the coordinates of the points being measured are sent — not the address text or place names you typed. Routing, town, and place data is © OpenStreetMap contributors, used under the Open Database License.
• Google Analytics (GA4). Used to understand how the tool is used — for example which features are tapped, how many starting points are in a search, and coarse buckets such as a drive-time range. To do this, Google sets first-party analytics cookies and receives standard technical data (your IP address, device and browser type, and a randomly-assigned analytics identifier). We never send Google Analytics the addresses, place names, or coordinates you enter — only coarse, non-identifying usage signals. This data is handled under the Google Privacy Policy. You can opt out with the Google Analytics Opt-out Browser Add-on or by blocking cookies in your browser.

We don't control these providers' own logging. We send the mapping and routing services only what's needed to answer "how long is this drive" and "what's near here", and we send analytics only coarse usage signals — never your locations.

When you create a share link, the full details (your exact starting points and the result) are packed into the part of the URL after the # symbol. By web standards, browsers never send that fragment to a server — it stays on the devices of whoever has the link.

So that a shared link can show a preview card in chat apps and social media, a coarse summary is also included in the normal part of the URL: the general meeting area, each side's drive time, and the city-level names of the starting points (for example "Fort Worth", never a street address). This summary is the only location-related information that can appear in ordinary web server request logs, and only for links that are actually opened.

We use Google Analytics (GA4) to understand how the tool is used. It sets first-party analytics cookies and records coarse usage events — such as which features you tap, how many starting points are in a search, and coarse buckets like a drive-time range. It never receives the addresses, place names, or coordinates you enter. We use no advertising cookies and run no ad or cross-site tracking networks. You can opt out of Google Analytics with the opt-out browser add-on or by blocking cookies in your browser settings.

Separately, the site stores a single technical value in your browser's local storage only if you enable an internal "routing lab" developer feature via a special link; it holds a feature-flag key and no personal information. It never leaves your browser and can be cleared at any time through your browser settings.

The site is served through a hosting provider (Cloudflare) that, like all web hosts, may record standard technical request logs — such as IP address, timestamp, and the URL requested — to deliver the site securely and reliably. As noted above, the only location-related data that can appear in those logs is the coarse summary of an opened share link. We do not combine this with any other information to identify you.

Because we don't store the locations you enter, there is nothing for us to retain or delete on your behalf. Standard hosting request logs are kept only as long as our hosting provider's normal operational retention allows.

If you are in the UK, EU, or a similar jurisdiction, you have rights over personal data a service holds about you — including access, correction, erasure, restriction, and objection. We do not maintain accounts and do not store the locations you enter, so we hold no directly identifying records tied to you. The main personal data associated with your visit is the analytics data collected and processed by Google Analytics (see above) — for example your IP address and an analytics identifier stored in a cookie. You can limit or opt out of that at any time using the opt-out add-on or your browser's cookie controls, and Google's own tools govern access to and deletion of analytics data it processes. If you want to exercise any of these rights or believe we hold data about you, contact us using the details below and we will respond. You also have the right to lodge a complaint with your local data protection authority.

Split the Drive is a general-audience tool and is not directed at children, and we do not knowingly collect personal information from anyone.

If the app's data handling changes, we will update this page and revise the "last updated" date above.

Questions about privacy? Reach us at contact@splitthedrive.com.