Stroll Routes is a walking-tour planning app. This policy explains what data is collected and how it is used.
Data we collect
Location data. If you grant permission, your device's GPS coordinates are used to set a route start point and to show distance to nearby places. When you plan or compute a route, the relevant coordinates (your start/end points and the stops on the route) are sent to our server and on to Google Maps Platform (Routes API) to calculate walking directions, and — for AI route planning — may be included in the request sent to OpenAI. Our server does not retain these coordinates after the response is returned. Your current in-progress route — including your chosen stops, start/end points, any AI route-editing conversation for that route, your recent edit history (used for undo), and in-progress navigation state — is saved in your device's own browser storage so it survives a page reload (on your device only, up to 30 days); the calculated route line itself is not stored, but recomputed when needed. If you sign in and save a route, see "Saved routes". This happens whether or not you are signed in.
Route requests. When you plan a route, your prompt text, the selected city, and the coordinates described above are sent to our server. AI planning is processed by OpenAI's API; walking directions are computed by Google Maps Platform (or, if that is unavailable, straight lines calculated on our own server, which involves no third party). Our server does not retain the request after the response is returned.
Place Q&A and city chat. If you ask a question about a specific place, or use the Chat feature to ask about a city or plan a trip, your question (and, for city chat, the ongoing conversation) is sent to our server and on to OpenAI's API to generate an answer. Our server does not retain these conversations after the response is returned; the conversation history is kept in your device's own browser storage so you can see it again later. All of your place Q&A and city chat history is deleted together after 30 days without any place Q&A or city chat activity — using any one of them resets that 30-day period for all of them, so an older conversation can be kept alongside a more recent one. The city Chat feature also has its own "Clear chat" option to delete that conversation immediately.
Saved routes, favourites, and history. Your current in-progress route is kept in your device's browser storage (see "Location data"). If you sign in, your saved routes, favourite places, and view history are also stored in our database (Supabase) so they sync across your devices. Saved routes store your chosen stops, place identifiers, and start/end points — not the calculated route line, which is recomputed when you open the route. You can delete this data at any time from within the app.
Account and usage records. If you sign in, we store your account (via Supabase) and a record of each metered action you take — generating a guide, planning or editing a route, asking a question. These records exist to enforce the fair-use limits on a pass and to monitor what the service costs to run. If you buy a pass, we store which pass it was and when it starts and ends.
Feedback. If you send feedback from within the app, we receive your message, your email address if you are signed in, and a short note of the context it was written in: the city you were viewing, which screen you were on, whether you were using a phone or a desktop, the size of your window, and which version of the app you were running. Your message and that context are stored in our database (Supabase), and a copy is delivered to our team chat (Slack) so that someone sees it. Nothing else is attached — no screenshot, and no location.
Third-party services
Google Maps Platform. The app uses Google Maps for map display, walking route calculation, and address lookup. Google's use of this data is governed by the Google Privacy Policy.
OpenAI. Route suggestions, place guides, place Q&A answers, and city chat responses are generated using the OpenAI API. Prompts are subject to OpenAI's Privacy Policy.
Supabase. Your account, saved lists, saved routes, place history, preferences and usage records are stored in a database and file storage operated by Supabase. Generated guide text and audio are kept there too. See Supabase's Privacy Policy.
Stripe. Payments are handled by Stripe. Card details are entered on Stripe's own systems and never reach ours; we receive only the fact that a payment succeeded and which pass it was for. See Stripe's Privacy Policy.
Railway. The app and its server are hosted on Railway, which processes requests on our behalf. See Railway's Privacy Policy.
Slack. Feedback you send from within the app is delivered to a private channel in Slack that we read, together with your email address if you are signed in. See Slack's Privacy Policy.
Your rights
If you are in the UK or EU, you have the right to access the personal data held about you, to have it corrected, to have it deleted, and to receive a copy in a portable format. You can exercise the deletion right yourself at any time: Profile → Settings → Edit profile → Delete account. Deleting your account removes your saved lists, routes, place history, preferences, and the records of what you have used.
For a copy of your data, or for anything else in this section, write to support@strollroutes.com. We respond within one month.
How long data is kept
Your saved lists, routes, place history and preferences are kept until you delete your account, and are deleted with it — as are the records of metered actions that exist to enforce fair-use limits. Three things deliberately outlive the account. Records of passes purchased are kept because accounting and tax rules require them, with the link to your account removed. And so that the one-time free trial cannot simply be taken again, we keep a note that a given email address has had one, stored in a normalised form (lower-cased, with any +tag and, for addresses where it is interchangeable, any dot removed) and nothing else. Feedback you have sent is kept after the account is deleted, with your email address and the link to your account removed, because a report describes the app rather than the person who wrote it; the copy in our team chat is removed on that service’s own schedule. Payment records are also retained by Stripe for as long as tax and accounting law requires.
Cookies
The app does not use tracking or analytics cookies. A session cookie is used only for the admin interface, if accessed.
Children
The app is not directed at children under 13 and does not knowingly collect data from children.
Contact
Questions about this policy, and any request under the rights described above, can be sent to support@strollroutes.com. There is no separate privacy address — this is the one mailbox, and it is monitored.