Privacy policy

ParseGo is run by [Your name] (“we”, “us”). We decide how your data is used, which makes us its controller under UK data protection law (the UK GDPR and the Data Protection Act 2018). Write to us about anything on this page at [contact email].

ParseGo is a private beta: free, invite-only and still changing.

Your Google account

You sign in with Google. Google gives us your name, email address and profile picture, and our sign-in provider keeps them with your account. ParseGo uses your name and email, for example to greet you and to match the bookings you forward. It doesn't show your picture, and we never see your Google password.

Your trips

Everything you put into a trip: destinations, dates, days and activities, notes, flights and hotel bookings (including booking references and confirmation links), the text you paste in to create a trip, your conversation with the planner while it builds one, and who you share it with.

Saved places

The places you save, with their links and notes, including links you share to ParseGo from other apps.

Your conversations with ParseGo

On a trip, we keep your chat with ParseGo (the latest 60 messages) so you can pick it up later, and the changes it offers you for two hours. Chats on Home aren't kept. ParseGo also keeps a short note of your travel preferences, such as pace and budget, drawn from your answers and your trip chats; Settings shows them and lets you change them.

Booking emails you forward

When you forward a booking confirmation to our import address, our email provider receives the whole email and passes it to us. We send its subject and the first 6,000 characters of its text to OpenAI to read the booking, and keep only the subject and the booking details: the flight or hotel, dates, booking reference and confirmation link. We don't keep the email itself. We check the sender's address against our accounts to know whose booking it is, and don't store it.

Links you share from your iPhone

When you share a link to ParseGo, we keep the link and look for places in it: we read the page and its caption, and ask OpenAI to pick out the places. For a video, our video service downloads it, sends Anthropic's Claude its caption and stills from it and OpenAI its sound, to find the places shown or mentioned, then deletes the download; it receives only the link, not who you are. We remember what we found for each link, without any account details, so the same link isn't processed twice.

Your globe and shared trips

The cities you pin on your globe and when you went. On a trip someone shares with you, the suggestions you make, shown with your name to the people on it.

How you use ParseGo

A few planning events, such as accepting a suggestion or adding an activity yourself, with your account, the trip and its destination. When you accept a suggested activity, its title is added to what ParseGo knows about that destination, to improve suggestions for everyone.

We also count how ParseGo is used with PostHog. Our servers, not your browser, send it five events, each with your account's id and the time:

• Starting a plan: whether you named a place or asked for ideas, whether it has dates, and how many days.
• A trip being built: the trip's id, how many days and confirmed flights it has, and whether it came from a suggested destination.
• Saving a place: whether you saved it in ParseGo or shared it from another app, and the kind of place (food, activity, stay or other) or the app it came from (TikTok, Instagram, 小红书, another website, or text only).
• Signing in: whether your account is new.
• Turning on a trip's view-only link: the trip's id.

Never your email, your name, a trip's name or destination, or anything you typed, and PostHog keeps no profile of you.

Keeping things running

We use your IP address briefly, in memory, to limit how often the public parts of ParseGo can be called; we don't store it. We count each account's requests and its use of paid services each day, to keep ParseGo fair and affordable. When error monitoring is on, error reports go to Sentry with personal data taken out (no IP address, email or trip text). Our hosting provider sees your IP address when it delivers pages, as any website's does.

The waitlist

If you join the waitlist, your email address, so we can invite you.

We don't collect your location, contacts or photos. The iPhone app doesn't send us a notification token: its reminders are set on your phone.

• To run ParseGo for you: keeping, planning and editing your trips, importing bookings and links, and sharing trips with the people you choose. This is necessary to provide the service you asked for.
• To keep it safe and working: rate limits, daily spending limits, error reports and stopping misuse. These are our legitimate interests in running a secure, affordable service.
• To make it better: the planning events and usage counts above. Also a legitimate interest; you can object, and we'll stop.
• To invite you from the waitlist: with your consent, which you can withdraw by writing to us.

We don't sell your data or use it for advertising, and nothing about you is decided by a machine in a way that has legal or similarly significant effects.

We share data only with services that do work for us, and each gets only what its job needs. In particular, to plan and edit trips we send trip details to AI providers. Anthropic and OpenAI don't use what we send through their APIs to train their models unless a customer opts in, and we haven't.

• Supabase: sign-in, your travel preferences and the waitlist.
• MongoDB Atlas: the database for your trips, saves, chats and the rest of the above.
• Vercel: hosts the website and its servers.
• Anthropic (Claude): ParseGo's chat and the trip planner. It receives your messages, your trips, your saved places and your travel preferences, and searches the web for questions that need a live answer (it gets the question). It also finds places in videos you share (it gets the caption, stills from the video and what's said in it).
• OpenAI: reads pasted itineraries, forwarded booking emails and the captions of links you share; gets your questions to ParseGo, to find our notes on the destination; gets the sound of videos you share, to write down what's said; sums up your travel preferences from your trip chats; and indexes the titles of activities you accept.
• Google Maps Platform: maps, place search and details, addresses and travel times. Your browser loads Google Maps directly, so Google sees your IP address and what you type into its search.
• AeroDataBox: flight schedules and status (flight numbers, airports and dates).
• Apple (Apple Weather): weather forecasts for your trip's days. It gets the place rounded to about 10 km and the dates, never your name or account.
• Unsplash and Wikipedia: destination photos (they get the place's name).
• OpenStreetMap and CARTO: finding the cities on your globe, and the map tiles your browser loads (CARTO sees your IP address).
• Postmark: receives the booking emails you forward, and keeps them for a limited time under its own policy.
• Railway: runs our video service for links you share.
• Upstash: keeps the request and spending counts, by account id.
• Sentry: error reports with personal data taken out, when switched on.
• PostHog: usage events, hosted in the EU, sent from our servers with your account's id and without your email, your name or anything you typed. It sets no cookies.
• Google Fonts: the fonts for a shared trip's preview card. Our server asks for the font files and, for characters they don't have, sends those characters of the trip's name or its owner's first name.

People you share a trip with can see it, and editors can change it. We may also disclose data when the law requires it, or to protect someone's safety or our rights.

When a trip's owner turns on “Anyone with the link can view”, anyone who has the link can see the trip, without signing in, and so can the link-preview services of apps like WhatsApp, iMessage and Slack, which fetch the link to show a preview. They see the trip's name, its day plans with their places, times and notes, flight numbers and times, the names of its stays, its cover photo and the owner's first name (“Planned by”), on the page and in the preview card. Not the trip notes, booking references or links, addresses, or who else is on the trip. Turning the link off stops it working, for every copy of it.

The preview card is drawn on our server. For characters our fonts don't have, such as Chinese, Japanese or Korean script and emoji, our server asks Google Fonts for them.

Several of these services are based in, or store data in, the United States and other countries outside the UK. When data leaves the UK, we rely on the safeguards UK law provides, such as the UK–US data bridge or the standard data protection clauses in each provider's terms.

ParseGo sets only the cookies that keep you signed in, from our sign-in provider. They're strictly necessary, so there's no cookie banner, and there are no advertising or analytics cookies.

The website also keeps a few small things in your browser so screens work smoothly, such as whether you've answered the welcome questions and a question you're passing from one screen to ParseGo's chat. The iPhone app keeps your sign-in in the phone's keychain and a few settings on the phone.

So your trips open without a signal, the iPhone app also keeps a copy of the trips you've opened, the one you're on and any starting in the next three weeks, with their bookings and cover photos. The copy stays in the app's own storage, protected by your phone's passcode, and isn't included in backups. It leaves out your chats with ParseGo, any text you pasted to import a trip, the planner's notes, invite and share links, and friends' answers about dates. Signing out deletes it.

We keep your data while you have an account, and delete it when you ask.

Delete all my data, in Settings, removes straight away: every trip you own (including trips you've shared, for everyone on them), your globe pins, your saves, your chats with ParseGo on any trip and the changes it had offered you.

It doesn't yet remove your account itself (your name, email and picture), your travel preferences, your planning events, planner chats you didn't finish, suggestions you made on other people's trips, your place on trips other people own, or a waitlist entry. To remove those too, or everything if you can't open Settings, write to [contact email] and we'll delete them within a month.

Some things expire on their own: changes ParseGo offered after two hours, request and spending counts within two days, and saved place details (which aren't linked to you) within 30 days.

Under UK data protection law you can ask us to show you the data we hold about you and give you a copy; correct it; delete it; limit how we use it or object to it; and give you the data you gave us in a form you can take elsewhere. Where we rely on your consent, you can withdraw it at any time.

Write to [contact email]. We'll answer within a month, and may ask you to confirm it's you.

If you're unhappy with how we've handled your data, you can complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113. We'd like the chance to put it right first.

Your data travels encrypted and is stored with the providers above. Only the people who run ParseGo can reach it, and only to run and fix the service. No system is perfectly secure: if a breach puts your data at risk, we'll tell you, and the ICO, as the law requires.

ParseGo is for people aged 18 and over. We don't knowingly collect data about anyone younger. If you think a child is using ParseGo, tell us and we'll delete their account.

When this policy changes, the date at the top changes with it. If a change matters, such as a new kind of data or a new service that sees what's in your trips, we'll tell you in the app or by email before it takes effect.