Privacy policy

What we process, and why

• Account: your email address if you sign in (with Google, also your name and profile picture), or an anonymous ID if you’re a guest. To provide your account (Art. 6(1)(b) GDPR).
• Your tripps: what you enter, such as travellers’ names and home cities, journeys, stays, activities, booking references and notes. To run the tripp for you and those you share it with (Art. 6(1)(b); for other people you add, our legitimate interest in running the tripp you plan, Art. 6(1)(f)). Only add people who are happy for you to.
• AI features: images you upload, and the text of PDFs and emails you send to smart import, are sent to an AI model with the tripp’s dates and travellers’ names, so it can match bookings to people. They’re deleted once the bookings are read. Forwarded emails can include other people’s details, such as fellow passengers. Activity names and links are also sent to an AI model to pick their icon (Art. 6(1)(b); for other people’s details, our legitimate interest in running the tripp you plan, Art. 6(1)(f)).
• Place search: what you type, and roughly where your tripp is, is sent to Google to find places. Your IP address isn’t (Art. 6(1)(b)).
• Map: the Map tab loads its map from Mapbox, which sees your IP address and the area shown, and counts the map being opened. Your journeys are drawn on your device and aren’t sent to Mapbox (Art. 6(1)(b)).
• Security: a bot check (Cloudflare Turnstile, see Cloudflare’s Turnstile privacy addendum) when you visit and when you sign in by email, rate limits by IP address, and server logs (IP address, requests and errors, never what you import). To keep the service safe and working (Art. 6(1)(f)).
• Visit statistics: Umami records the pages you open (without tripp or link IDs), where you came from, your browser, device, language and country, how fast pages load, and which features you use (never their content), including which partner links you open (only the partner, the kind of link and where it was). It uses no cookies. Once you’ve used the app, visits are linked to the random ID of your account or guest session (never your email or name), so we can count returning people; we only look at totals. To see how people find and use tripps.io (Art. 6(1)(f)).
• Invitations: when you invite someone by email, we keep their address, who invited them and when we emailed them, to send the invitation, let only that address join, and limit how many invitations anyone gets. The email shows your address as who invited them, and lets them decline or ask for no more invitations from anyone. Joining without an account makes one with that address. For the limits, and for addresses that asked for no more invitations, we keep only a code made from the address with a key only we hold. Our legitimate interest in letting you share tripps, and theirs in not getting unwanted email (Art. 6(1)(f)).
• Reminder emails: with an account, we email you two weeks before each of your tripps starts and the day before, with anything still to book. We keep your time zone to send them in the morning, and a note of each one sent. Turn them off in your account or from any reminder email, or mute one tripp from its menu (Art. 6(1)(f)).
• Partner links: links marked Ad lead to things to do on partners such as GetYourGuide. They go through tripps.io, which passes the partner only the city, your days there and where on tripps.io the link was, never your name, your tripp or where you came from. The partner then sees your IP address and browser like any site you visit, may set its own cookies, and its own privacy policy applies. If you book, we may earn a commission. To fund tripps.io (Art. 6(1)(f)).
• Support: emails you send to us, to answer them (Art. 6(1)(b) or (f)).

What you have to give

Nothing is required by law. You can use tripps.io as a guest; to keep your tripps across devices, sign in with an email address or Google.

Who sees your tripps

• People you share a tripp with, by link or by email invitation: everything, or chosen travellers’ plans, as you choose. People with an edit link can make links of their own, and see how many people opened each link (not who). Only a tripp’s owner sees the addresses of the people they invited. While you have a shared tripp open, the others with it open see your username (the start of your email address until you change it in your account; a guest is given a travel name in each tripp) and what you’re looking at or editing.
• Apps that show link previews (such as messaging apps), when a share link is pasted into them: the tripp’s name and dates.
• The providers below, which run tripps.io for us.

If someone added you to a tripp

Travellers are often added by someone else planning the tripp. Then we hold what they entered about you (your name, home city, and the bookings and notes they added you to) and use it only to run that tripp, our legitimate interest in running the tripp they plan (Art. 6(1)(f)). We don’t have your contact details, so this page is how we inform you. You have the rights below, and can ask them or us to remove you.

Signing in with Google

If you use “Continue with Google”, this is what happens with your Google user data:

• Access: only your basic profile: email address, name, profile picture and Google account ID. Nothing else in your Google account (no Gmail, Drive, contacts or calendar).
• Use: only to sign you in and show which account you’re using. Never for advertising or profiling.
• Storage: with your account, in Supabase (EU), until your account is deleted.
• Sharing: none, except with the providers below that run tripps.io, or where the law requires it. People you share tripps with don’t see it.
• Control: remove tripps.io’s access any time at myaccount.google.com/connections, and ask us to delete your account at support@tripps.io.

tripps.io’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Providers

These companies process data for us, under data processing agreements:

• Supabase: database (tripps, accounts, smart import counts), sign-in and sign-in emails, with data stored in the EU (Ireland).
• Cloudflare: hosting, link previews for share links, the AI models, the bot check, receiving booking emails, and forwarding support email.
• Resend: sending sign-in, reminder and invitation emails.
• Umami: visit statistics.
• Google: place search, and our support inbox (Gmail).
• Mapbox: the map on the Map tab.

Some of these companies are in the US or may process data there; transfers are covered by the EU–US Data Privacy Framework or the EU’s standard contractual clauses. Ask us at support@tripps.io for a copy of the safeguards that apply.

On your device

Your browser keeps your sign-in session in local storage, and while you sign in, a note that you’re signing in (to confirm it worked and count sign-ups) and a code to move a guest’s tripps to your account. As a guest, it remembers whether we’ve asked you to sign in or offered you reminders. So tripps open without a connection, it also keeps a copy of your tripps list and each tripp you open, the app’s own files, and the map areas you’ve viewed (up to 30 days, as Mapbox allows). The copies are refreshed when you’re online, and deleted when you sign out or a tripp is deleted or its link stops working (once the app is next online). All of this is needed for what you asked for, so there’s no consent banner, and none of it is used for advertising or to follow you.

How long we keep it

• Account, tripps and smart import counts: until you delete them or your account.
• Guest accounts: deleted after 30 days unused, if they have no tripps.
• Images, PDFs and emails sent to smart import: deleted as soon as the bookings are read.
• Bookings smart import found but hasn’t added yet, and why a forwarded email couldn’t be imported (its subject and the reason): until you add, finish or dismiss them, at most 30 days.
• Notes of reminder emails sent: 90 days.
• Invitations: while the person invited is on the tripp, or until 30 days after the last email if nobody joined. Notes of invitation emails sent (pseudonymised): 30 days. An address’s link to stop invitations: 90 days after its last invitation. Addresses that asked for no more invitations (pseudonymised): for as long as we send invitations.
• Server logs: a few days.
• Visit statistics: kept by Umami under that random ID, which no longer leads to anyone once your account is deleted.
• Support emails: as long as we need them to answer you.

Your rights

You can ask to see, correct, delete or take a copy of your data, to restrict its use, and object to uses based on legitimate interests: write to support@tripps.io. You can also complain to a data protection authority, such as the one where you live.

Changes

We’ll update this policy when what we do with data changes; the date at the top shows when.