Privacy Policy

Last updated 17 September 2026

This policy explains what WantToGo stores about you, what leaves our servers, and what you can ask us to do about it. It describes the product as it works today — not as it might work later.

Who operates WantToGo

WantToGo is operated by an individual entrepreneur (FOP) registered in Ukraine. The servers that run the service are hosted in the European Union, in Germany and Finland.

For anything in this policy — your data, your account, a question or a complaint — write to i@wanttogo.app.

Our full registered details — legal name, registration number and postal address — will be published on this page before WantToGo begins charging for subscriptions.

What we store about you

  • Your account: email address, display name, a hashed password we cannot read, and the time you last signed in.
  • Your preferences: the interests, food and travel style WantToGo picks up as you plan, and a home base if you set one.
  • Your journeys: destinations, dates, the itinerary generated for you, the edits you make to it, and any planning notes you write.
  • The waitlist: if sign-ups are waitlist-only when you apply, we store your email address and name, and send you one confirmation email.

We do not ask for your postal address, phone number or date of birth, and there is nowhere in the product to enter payment details.

What your own browser stores

Three things live on your device rather than on our servers, and all of them disappear when you clear the site's data in your browser:

  • Sign-in tokens, kept in your browser's local storage rather than in cookies. Clearing them signs you out.
  • An offline copy of the app, your current journey and the place photographs in it, so your plan stays readable when the connection disappears while you're travelling.
  • Your analytics choice, so we don't ask you again. If you allow analytics, Google Analytics sets its own cookies in your browser as well; declining — or changing your mind later — clears them.

Who else processes your data

WantToGo cannot build an itinerary alone. These providers act for us, each receiving only what its job needs, and some of them process data outside the EU and EEA under their own terms:

  • OpenAI generates the itinerary. It receives the trip description — the destination, the dates and the preferences you chose. It does not receive your email address, your display name or your account identifier.
  • Google supplies the real places: their addresses, opening hours, ratings, reviews and photographs. These lookups are made by our servers, not by your browser, so Google does not receive your IP address through this. Responses are cached on our servers briefly so the same place is not looked up repeatedly.
  • Mapbox draws the map, and only if you open the map view for a place. It loads in your browser, so at that moment Mapbox receives your IP address and the map request.
  • An email provider delivers the waitlist confirmation — the only email the product sends today.
  • Error monitoring (Sentry), when it is switched on for our servers, receives technical reports about failures. It is configured not to include personal request data.
  • Google Analytics — but only if you choose to allow it, and nothing at all reaches it if you don't. The next section explains exactly what it does and does not receive.

Analytics, only if you allow it

WantToGo can use Google Analytics to understand how the product is actually used — which screens people open, and which steps of planning a journey they finish — so we can improve it. It is optional, and it is off until you say otherwise.

  • Nothing loads until you choose. Before you allow analytics, no Google script is fetched, no analytics request is sent, and no analytics cookie is set.
  • You can decline. “No thanks” is a single tap, the same size and in the same place as allowing it, and we don't ask again.
  • You can change your mind. “Analytics preferences”, in the footer of our public pages and in the Account group on your You screen, reopens the choice at any time. Turning it off stops collection and clears the analytics cookies from your browser.

What we deliberately keep out of analytics: your email address, your display name, your account identifier, your journey titles and identifiers, destinations, place names and addresses, planning notes, anything else you have written, and the text you type into a search box. Page addresses have their identifiers removed before they are sent — a journey is recorded as “/journeys/:id” — so analytics can show that someone opened a journey, never which journey or whose. Query strings are dropped rather than passed on, and we never build an analytics identity out of your account.

WantToGo carries no advertising and does no ad tracking, so there is no advertising consent to give. Google's own advertising features are switched off in our configuration rather than left at their defaults.

What we don't do

  • No advertising, no ad tracking, and no profile built about you. The optional analytics described above is the only measurement in WantToGo, and it stays off unless you allow it.
  • We do not sell your data, or share it for anyone's marketing.
  • We do not publish your journeys. What you plan is visible to your account and to nobody else.

Why we are allowed to store it

  • To provide what you asked for — your account, your preferences and your journeys — which we need in order to perform our agreement with you.
  • To keep the service working and secure: diagnosing failures and preventing abuse, which is our legitimate interest in running it.
  • To answer you when you write to us.

Where the law where you live requires your consent for something, we will ask for it rather than assume it.

Server logs

Our servers keep operational logs so we can run and secure the service. These normally identify an account by an internal identifier rather than by name. Two events record an email address: joining the waitlist, and a failed sign-in attempt.

Deleting your account

You can delete your account yourself, at any time, from the You screen. It asks you to type DELETE first, because it cannot be undone.

Deleting removes your account, your preferences, your journeys and your planning notes from the live service immediately, and invalidates the sign-in tokens issued to you.

We do not yet publish a retention schedule for operational backups and logs. Where copies of deleted data remain in them for a period, they are used only to restore or secure the service — never to reconstruct a deleted account.

There is no self-service export today. If you want a copy of your data before you delete it, write to i@wanttogo.app and we will put it together by hand.

Your rights

Depending on where you live, you may have the right to access the data we hold about you, to correct it, to have it deleted, to object to or restrict how we use it, to receive a copy in a portable form, and to complain to your local data protection authority.

Write to i@wanttogo.app to exercise any of them. Nothing in this policy limits a right you have under the law where you live.

Age

WantToGo is for people aged 16 and over. If the law where you live requires a parent or guardian to consent for someone of your age, you need that consent before using it. If you believe someone under 16 has an account, tell us at i@wanttogo.app and we will remove it.

Changes to this policy

When this policy changes, we update this page and the date at the top of it. If a change materially affects you, we will make that clear here before it takes effect.

See also our Terms of Service.