You can read every page of this site and use the trip planner without an account. This policy lists what is stored or sent when you do, and what changes if you sign in. It follows what the software actually does.
Who is responsible
The controller of your personal data is Sustainate. Contact us at admin@sustainate.com for anything in this policy.
What we collect and why
Each item below says what the data is, what we use it for and the legal basis under the GDPR (see the section on legal bases).
- Trip searches. When you search, your origin, destination, dates, number of travellers and options are sent to our server to work out routes. The search-box text is also sent to an AI provider (see below). We use this to give you the result you asked for.
- Saved history. To bring back your last searches, we store on our server your last 20 searches (origin, destination, dates, options and the search-box text), your last 20 search-box phrases, your quick locations (such as Home), your preferences (home station, currency, theme, CO₂ budget) and the trips you save. This data is stored under an identifier: your account email address if you are signed in, otherwise a random guest ID made in your browser and kept in its localStorage (it looks like guest_ followed by random letters and digits). When you sign in, the guest data is merged into your account and the browser gets a new guest ID.
- Account. Sign-in uses Firebase Authentication (Google), if it is switched on for the site: with an email address and password, or with a Google account. Firebase holds the sign-in data. Our server receives your email address and uses it as the identifier above. We never see your password.
- Planned-trip counts. When a search finishes, your browser tells our server which two places were planned, so the public route page can say that people planned it. We store the pair of places and counters (how many times, on how many days, when first and last). We do not store your IP address, your identifier or anything else about you with it. To count one visitor once per route per day, the server compares a salted hash of a random daily secret, your network address and the route. The secret is random, changes every UTC day, is kept only in the server’s memory and is never written to disk, so the hashes cannot be traced back to you and are gone at the latest after a day or a restart.
- Looking up unknown places. If you name a place we do not know, the server looks it up in our reference data and, if needed, asks an AI model with web search. Only the place name is sent. To keep the service within its limits, the server counts requests per network address in memory for an hour. These counters are not written to disk.
- Carbon offsets. If you buy a carbon offset, the payment is handled by Stripe. Card details go to Stripe and never reach our server. We receive the amount, the kilograms of CO₂ offset and the payment status.
- Server logs. The server writes operational logs: errors, and API requests such as which saved data was loaded. These can include the identifier from your saved history (email address or guest ID) and place names from searches. The hosting provider also keeps standard connection logs, which include IP addresses.
- Requests your browser makes to others. Photos in the planner are loaded from Wikimedia (Wikipedia) servers, and the planner’s world map outlines are loaded from the jsDelivr CDN. Those services see your IP address and browser details, as any website you visit would. Pages on this site serve their own photos from our server.
- Links to partners. If you follow a link to a booking site, that site receives your visit, and you are subject to its own privacy policy. See the terms for how affiliate links work.
Pages load an affiliate tracking script from Impact (impact.com); see the cookie page. The site has no analytics or advertising network, and we sell no personal data.
Searches sent to an AI provider
The planner uses language models to read the free-text search box and to write summaries, hotel and activity suggestions. These requests go from your browser to our server and from there to OpenRouter, which passes them to the model provider it routes to. The API key stays on our server. A request contains the search text and the trip details (places, dates, travellers) needed for the answer. It does not contain your email address or guest ID. Please do not type personal details into the search box. Lookups of unknown places use the same route, with web search.
Legal bases
- Providing the service you ask for (GDPR Article 6(1)(b)): trip searches, saved history, your account and, if you buy one, a carbon offset.
- Our legitimate interests (Article 6(1)(f)): keeping the service secure and within its limits, fixing errors from logs and counting how often routes are planned, in a way that identifies nobody.
- Legal obligation (Article 6(1)(c)): keeping payment records that the law requires, if you buy an offset.
- Affiliate tracking by Impact runs on our pages; see the cookie page for what it stores.
Who else handles your data
| Railway | Hosts the server, the database and the logs. |
|---|---|
| Google (Firebase Authentication) | Sign-in, if switched on. |
| OpenRouter and the model providers behind it | Reading search text and writing trip text. |
| Stripe | Payment for carbon offsets. |
| Impact (impact.com) | Affiliate tracking on every page: it counts how often partner links are shown and credits Sustainate for bookings made through them. It receives your IP address and browser details, and may set cookies or store identifiers. Impact may share data with the advertisers (partners) involved, as described in Impact’s own privacy notice. |
| Wikimedia and jsDelivr | Photos and map outlines your browser loads in the planner. |
Some of these providers are in the United States or process data there. Where data leaves the EU or EEA, the transfer rests on an adequacy decision or standard contractual clauses.
How long we keep it
- Last searches and search-box phrases: the latest 20 of each; older ones are deleted automatically as new ones are saved.
- Preferences, quick locations and saved trips: until you delete them in the app or ask us to. We do not delete idle accounts automatically at the moment.
- Guest IDs and their data: until they are merged into an account, or until you ask us to delete them.
- Planned-trip counts: kept as plain counters with no personal data. The oldest unpromoted planned routes are removed once a fixed number is exceeded.
- Daily hash secret and request counters: in memory only, gone after at most a day or at a restart.
- Sign-in data at Firebase: until you ask to delete your account.
- Logs: for the period the hosting provider keeps them under our plan, and the last 100 lines in the server’s memory.
Your rights
You can ask us for a copy of your data, to correct or delete it, to limit or object to its use, and to receive it in a portable format. You can object at any time to processing based on our legitimate interests. Email admin@sustainate.com from the address your account uses. If you were not signed in, send the guest ID, which is stored in your browser under the name ecotrek_guest_id (see the cookie page). We answer within one month.
Children
Sustainate is not meant for children under 16 and we do not knowingly collect their data.
Complaints
If you think we have handled your data unlawfully, you can complain to the data protection authority in the EU or EEA country where you live or work. We would like the chance to put it right first, so please write to us.
Changes to this policy
When what we collect changes, we change this page and its text first. The page is part of the site, so what you read here is current.