Route AI ("the service") is a route-planning tool available at
route-ai.app. This page describes what data the service handles, why, and
for how long. The short version: we keep the minimum needed to run the
service and improve it, we don't sell anything to anyone, and most of the
heavy lifting happens in your browser.
What we collect
Account details — if you sign in with Google we store
your name, email address and profile picture URL, as provided by Google.
Signing in is optional; planning routes works without an account.
Your trips — routes you explicitly save, and routes you
share via a link. Shared links are public snapshots: anyone with the link
can view them.
Chat messages — the trip descriptions and follow-up
messages you type are sent to our AI provider (see below) to produce the
plan. We do not store your conversation on our servers after the request
completes; it lives in your browser for the duration of your session.
Usage analytics — anonymous event records such as
"a route was built", "a GPX file was downloaded" or "geocoding failed",
each tied to a random session identifier, and, if you are signed in, your
account, together with an approximate location (city and country,
derived from your IP address). These records contain no chat text and
no precise location.
They are kept for up to 90 days and are used solely to find and fix
problems in the service.
Feedback — if you send feedback, we store your message,
the optional contact you provide, and technical context (the current plan,
recent chat excerpts, app version) so the problem can be reproduced.
Server logs — standard web-server access logs (IP
address, requested URL, browser identifier), rotated after a few days,
used for security and rate limiting.
Your location
If you use the "Around me" feature or refer to your own position in a
message, your browser will ask for permission to share your location. The
coordinates are converted to a nearby place name in your browser and only
that place name is used in the plan. Your precise coordinates are never
stored on our servers. Declining permission leaves everything else working.
Third parties the service relies on
OpenAI — your trip description and the current plan are
sent to OpenAI's API to generate route suggestions, subject to
OpenAI's policies.
OpenStreetMap / Nominatim — place names are geocoded
directly from your browser.
BRouter — routes are calculated directly from your
browser using the public BRouter service.
Map tile providers — OpenStreetMap, CyclOSM,
OpenTopoMap, Waymarked Trails and Esri serve the map images your browser
displays, and receive standard web requests (including your IP address)
when tiles load.
Google — used only for optional sign-in
(and Google Analytics, below).
Google Analytics — standard, aggregated usage
measurement. Most content blockers block it; the service works fine
either way.
Cookies and local storage
A session cookie keeps you signed in. Your browser's local storage holds
your unsaved draft plan, interface preferences (map layer, panel size) and a
random session identifier. No advertising or cross-site tracking cookies are
set.
Retention and deletion
Usage analytics: deleted automatically after at most 90 days.
Server logs: rotated after a few days.
Saved trips, shares and your account: kept until you delete them or ask
us to. Deleting a saved trip removes it immediately; a shared link can be
deleted by its owner.
To have your account and all associated data removed, send a request
through the in-app feedback form from the signed-in account, and it will be
deleted.
What we don't do
No selling or renting of data, to anyone, ever.
No advertising, no ad networks, no cross-site tracking.
No storing of your precise GPS coordinates.
Changes
If this policy changes materially, the date above will be updated. The
current version always lives at this address.
Contact
Questions about this policy: use the feedback button in the app.