Privacy
The short version: we store the trips you build so share links keep working, we ask for an email address only if you want one, and we do not sell anything about you.
Last updated:
What we store, and why
Trips you build
Every generated itinerary is saved so that share links and trip pages keep working. A trip page is unlisted rather than private: it is not indexed by search engines and its address is unguessable, but anyone you send the link to, and anyone they forward it to, can open it. What you type into the trip brief is never shown on that page and is not returned by our public API, and the written summary is instructed to describe the journey rather than the people taking it. Even so, treat a share link as public. It contains the choices you made, route, dates, pace, interests, and any free text you typed into the trip form or the tweak box. Anonymous trips are deleted automatically after 180 days. Trips you explicitly save to an account are kept until you delete them.
Your account, if you make one
Accounts are email-only and passwordless: we send a one-time code to sign you in. We store your email address and the trips you have saved. There is no password to leak because there is no password.
Signals you send
Thumbs up or down on a stop are stored against that stop. We collect them so that we can one day improve which places get recommended, but nothing reads them yet: no itinerary you have ever been shown was changed by anyone’s vote. They are kept indefinitely rather than expiring after 180 days, because a vote deleted before anything reads it is a signal we never really collected. A per-route counter tracks how many trips were built this week, and that one does run — it is what orders the "trending" strip on the home page. Neither is tied to advertising.
We store an email address in exactly two cases: you created an account, or you asked us to email you a copy of an itinerary. In both cases you asked first. We do not buy lists, we do not sell or rent addresses, and every message we send has an unsubscribe link.
Abuse prevention
We count requests per network address per day so that automated traffic cannot run up costs. That counter holds a hashed key and a number, not a browsing history, and it expires.
Who else sees your data
The service runs on Amazon Web Services in Singapore, and AWS processes data on our behalf as our infrastructure provider. To write the descriptive prose in a plan, the text of your trip brief is sent to a language model hosted inside that same AWS account; it is not used to train anyone's model. Map tiles are served by OpenStreetMap, and weather comes from NASA POWER and MET Norway, those requests reveal the coordinates being displayed, as any map does.
Outbound booking links point to third parties (accommodation, tours, car hire). Once you follow one, you are on their site under their privacy policy, not ours. Some of those links carry an affiliate marker so the partner knows the visit came from us, see affiliate disclosure.
Tracking
We use Google Analytics and Google Ads measurement to understand visits, journeys viewed and whether our ads lead to actions such as building a plan or opening a booking link. We do not enable personalised advertising. We do not send your email address or trip description as analytics event parameters.
In the EEA, UK and Switzerland we ask before enabling analytics and advertising measurement cookies. In our other recognised markets these are enabled automatically unless you have declined. If your location is uncertain, we ask. An earlier analytics-only acceptance stays analytics-only unless you make a new choice.
You can accept or decline from Cookie choice in the footer at any time. Declining disables analytics and advertising cookie storage and advertising-data consent; Google may still receive cookieless measurement pings. This is not the same as switching off every network request. Google processes measurement data under its privacy policy.
We also use browser storage for your language and unit preferences, sign-in session, trip in progress, allowance display and cookie choice. Those functional features continue to work if you decline measurement cookies.
The mapping library is served from this site, not from someone else's CDN, so displaying a map does not announce your visit to a third party. The map tiles themselves come from OpenStreetMap: panning a map requests those tiles from their servers, which reveals your network address to them, as using any map does.
Who is responsible for your data
Odycairn is run by an independent sole proprietor based in Singapore, who is the data controller for everything described on this page. Personal data is processed in Singapore on Amazon Web Services. Where you are in the UK or the European Economic Area, that is a transfer outside your region; it is covered by AWS's standard contractual clauses as our processor.
Why we are allowed to hold it
Your account and saved trips are held to provide the service you asked for. Abuse counters are held because we have a legitimate interest in not being billed for automated traffic. Marketing email is sent only with your consent, which you can withdraw from any message.
Your rights
You can ask for a copy of what we hold, ask us to correct it, ask us to delete it, or object to how we use it. You can use the planner without an account at all, and anonymous trips age out on their own after 180 days. If you are in the UK or the EEA you also have the right to complain to your local data protection authority.
To ask for a copy of what we hold, to correct it, or to have it deleted, write to privacy@odycairn.com. We will respond within 30 days.