Privacy Policy

Data the application stores

The application stores the account information you provide, one active route-criteria draft for your account, generated route proposals, and routes you choose to save. A proposal contains a snapshot of the selected Google Place IDs and criteria plus application-created descriptions, driving metrics, day divisions, and status data. Proposals become unavailable in the application seven days after completion or failure, although expired records may remain in the application database until they are removed separately. A saved route contains the selected Place IDs, copied criteria, and the application-created plan. Saved routes do not have an expiry time and are kept until your account is deleted.

Data sent to Google

When you use place search, your browser sends location queries and related technical request data to Google Maps Platform. After you submit the form, the application server sends selected Place IDs to the Google Places API (New) for verification and route review, and to the Google Routes API to calculate the journey. During review, place names and Google Maps links may be retrieved temporarily for display. Google processes this data under the Google Privacy Policy.

Google Places content

The application persistently stores only Place IDs from Google Places content. It does not persist Google place names, Google Maps links, formatted addresses, coordinates, autocomplete suggestions, or other Places display content. Names and links used in a generated proposal or saved route review are retrieved temporarily and are not written into the proposal, saved route, or application database. When an existing draft is opened, a formatted address may also be retrieved temporarily in your browser to label the saved Place ID; that label is not submitted with the form or saved in the application database.

How the data is used

Account data is used to authenticate you and keep your draft, proposals, and saved routes separate from other users. Route criteria are used to restore your choices and provide input for trip planning. A saved route is used to make an accepted plan available to you after you sign in again. Session and operational data may be processed to keep the service secure, diagnose failures, and prevent abuse. Provider API keys are configuration secrets and are not included in stored route criteria or saved routes.