Legal
Privacy policy
What data tripbot processes, what for, for how long, who receives it and what your rights are.
Last updated: November 19, 2026
The short version
- We do not sell data, show no ads and use no analytics or tracking tools from other companies. We count visits and steps in tripbot ourselves, without a cookie and without storing your IP address. That is why there is no cookie banner.
- So tripbot can answer, your messages, photos and links go to AI models in the US. Only write what you want to share for the trip.
- tripbot only remembers what you say about yourself if it also holds for your next trip, health or religion never without your tap. Ask tripbot what it knows about you; you switch remembering off in your profile.
- We never see your card details: you pay in the form of our partner Nuitée.
- In your profile you delete your account with all trips, chats and preferences. Questions go to legal@trytripbot.com.
01
Who is responsible
The controller under the General Data Protection Regulation (GDPR) is:
We have not yet appointed a data protection officer; we are doing so now, and their contact details will then appear here. Until then, write to legal@trytripbot.com with any question about data protection.
02
When you open tripbot
tripbot runs on a server of IONOS SE (Elgendorfer Straße 57, 56410 Montabaur) in Germany. In front of it sits Cloudflare (Cloudflare, Inc., USA): every request first passes through Cloudflare’s network, which delivers the site encrypted and fends off attacks. This processes your IP address, the address you open, the time and details about your browser and device.
Our own server writes no access logs with your IP address (for sign-in see “Account and sign-in”). To stop anyone from flooding tripbot with requests, it counts the requests of an IP address in memory for at most ten minutes.
From your IP address, Cloudflare derives your country and a rough location, such as the city, and passes them on to our server with the request. We use them in that moment: the country for the market hotel prices are calculated for, the location to suggest the nearest airport to leave from. Whether you take the suggestion is up to you. We never store the exact location, and the country and city only for the count in the next paragraph.
How many people visit tripbot and where they come from, we count ourselves, without a cookie and without tools from other companies. On the first page view of a day, our server makes a checksum from your IP address, your browser’s name and a random number. The random number lives only in memory and is replaced by a new one every night; after that the checksum can no longer be tied to any address, and we cannot recognise you on another day by it (if you are signed in, the next paragraph applies). We store the checksum, the day with the time of the first page view, the country and city Cloudflare derives from your IP address, with their rough position (rounded to about 10 km), whether you come on a phone, tablet or computer, your browser’s first language, the first page you open and where you came from (the page that linked to you, or the campaign in the link, such as “tiktok”). If you open more pages that day or use the app, our server sees those requests anyway; at most every 30 seconds it notes when your last one came, how many pages you opened and which one last. That tells us how many people are here right now and how long a visit lasts. Of every page we store only which page it is, never the identifier of a booking or a shared link in it. We do not store your IP address. With each request, Cloudflare also tells us the network it comes from (the network operator’s number); if a page view comes from a data centre’s network, such as Amazon’s, Google’s or Alibaba’s, we do not count it, because programs rather than people come from there. We do not store the network either. We delete the entries after 90 days. If your browser sends the “Global Privacy Control” signal, we do not count you at all.
To see where tripbot helps and where it does not, we also note which steps people take: signing in, writing in the chat (only what the message does, such as “plan a trip” or “question”, never its text), asking for destinations, planning the days, searching hotels or flights, opening a hotel’s list of rooms, opening the checkout for a hotel or a flight and how far you get in it (such as whether the payment form loaded, never your details) and tapping a link to Viator, Tiqets or Agoda (with the experience or the hotel). This includes what you look at of a trip: whether you open it and which of its parts (such as the day plan, the hotel, the flight or the costs), whether you unfold a folded day in the chat, open a day’s page or a place, and whether a day plan in the chat stood on your screen for about 5, 20 or 60 seconds. The app tells our server so; which trip, day or place it was is not part of it, and we store nothing on your device for this. Each step is stored with its time, with your account when you are signed in, and with the day’s checksum from the paragraph above; that shows us which source leads people to an account. We delete the steps after 90 days. After that only sums per day remain, with no link to a person, such as how many people got ideas on a day. If you delete your account, your steps lose their link to you. With “Global Privacy Control” we note none.
The legal basis is our legitimate interest in a secure and available site, in fitting suggestions and in knowing how many people find tripbot, from where and how far they get with it (Art. 6(1)(f) GDPR). You can object (see “Your rights”).
03
Account and sign-in
To chat with tripbot you need an account. You sign in with Google or with your email address; there are no passwords.
- With email: we send you a link and a six-digit code. We store your address and, if you enter it, your name.
- With Google: Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) confirms your address to us and sends your name and profile photo. Our server fetches the photo from Google and passes it on to your browser, so Google does not learn when you open tripbot.
Each time you sign in and each time your sign-in is renewed (about once an hour while you use tripbot), our sign-in service Supabase receives your IP address so it can limit sign-in attempts per address, and stores it with your browser’s details (name and version) for your session. Both go when you sign out, delete your account or the session has not been used for a year. The legal basis is our legitimate interest in a secure sign-in (Art. 6(1)(f) GDPR).
If you choose a design in your profile (Light, Sunset, Aegean, Lagoon, Deep sea, Dusk or Automatic), we store it with the moment of your choice with your account, so your other devices take it over. From this we count how many accounts use which design on a day, only as a daily total with no link to a person; the legal basis is our legitimate interest in seeing which designs people like (Art. 6(1)(f) GDPR). We do not read the design’s cookie for this.
Accounts and all data in tripbot are stored with Supabase (Supabase Pte. Ltd., Singapore) in a data centre in Frankfurt am Main. Supabase staff may access it from outside the EU for operations and troubleshooting (see “Data outside the EU”). The legal basis is the contract for using tripbot (Art. 6(1)(b) GDPR). We keep your account until you delete it.
So that nothing is lost in an outage, we back this data up every night, encrypted, with Cloudflare (Cloudflare, Inc., USA) in storage that keeps it in the EU. Only tripbot holds the key. We delete every nightly backup after 30 days, so whatever you delete is also gone from the backups 30 days later at the latest (for the one-off copy of the previous tripbot see “Moving from the previous tripbot”). The legal basis is our legitimate interest in being able to restore your data after an incident (Art. 6(1)(f) GDPR, Art. 32(1)(c) GDPR).
04
Chat and AI
What you write in the chat, the photos and links you attach and the state of your trip go to OpenRouter (OpenRouter, Inc., USA). Along with it go, while “Use and remember preferences” is on in your profile, your saved travel preferences and your answers to “How was it?”, so that tripbot plans to fit. The AI never gets your first name; when you greet it, our server puts it into its answer. Your browser shrinks photos first and removes where they were taken and camera details; we do not store them. OpenRouter passes everything to the data centre that writes the answer: currently Microsoft (Azure) for the model GPT-6 Luna and DeepInfra (DeepInfra, Inc., USA) for the model gpt-oss-120b, both models by OpenAI. With every request we require data centres that neither store the texts nor use them for training, and never ones run by Chinese providers. Since 31 October 2026 OpenRouter itself keeps no content; it only records when which model used how many tokens and what that cost, without any text. Requests and answers from before that OpenRouter kept for troubleshooting; they stay there for OpenRouter’s own period, at least three months.
For current facts (such as entry rules or opening hours) tripbot searches the web through Exa (Exa Labs, Inc., USA) and, once its allowance is used up or Exa does not answer, through Linkup (Linkup Technologies SAS, France). They only receive a search phrase made of place and question, never your name or your booking. Links you send are read by our server itself, where the site allows it in its robots.txt; the site then sees our server's address, not yours. Only what it cannot read (a PDF, a page that only takes shape in a browser or turns it away) is read by Linkup or Exa, which receive the link for it. Exa and Linkup may store search requests and use them to improve and train their services. Linkup says it processes data in the EU, but depending on load it may also handle requests in the US, Canada or the Asia-Pacific region.
We keep your chats with the trip until you delete the trip or your account. The legal basis is the contract of use (Art. 6(1)(b) GDPR). Please do not write anything in the chat that you do not want to share for the trip, and no data of other people without their consent.
To make tripbot better, we read chats anonymously: only the wish and what tripbot answered, without name, email address or account. We also play your messages again with the newest version of tripbot; for that they go to OpenRouter again as described above. What comes of it stays with us and is deleted after 90 days. The legal basis is our legitimate interest in a service that plans correctly (Art. 6(1)(f) GDPR). You can object (see “Your rights”).
Feedback: Once, tripbot asks you in the chat how you like tripbot, and you can rate its answers in the chat with a thumb. If you tell tripbot in the chat what you think of tripbot, or ask it to pass something on to us, it shows you your words to check and send; nothing is sent until you tap. What you tap and write there we keep with your account: the rating, what could be better, your words, the chat it comes from and, for a thumb, the start of the answer you rated. When you send it, it goes to our mailbox as an email right away, through Resend or Mailjet as under “Emails”; if you stop after a tap, a little later. The email contains your name and email address so that we can reply to you. That tripbot asked you we keep even if you do not answer, so that we do not ask again. What you write in the chat for it goes to OpenRouter like every message (see above); your answer itself and the email to us do not. The legal basis is our legitimate interest in improving tripbot from your experience and in replying to you (Art. 6(1)(f) GDPR). We delete your answer one year after you gave it, and at once with your account; the email in our mailbox we delete as under “When you write to us”.
So that the daily limit applies (see the Terms, “AI answers”), we count with your account how many messages you write in a day: only the number per day, never what you write. We delete it after eight days. Whether you have the tripbot Pro subscription from the previous tripbot, our server checks against the list of running subscriptions it fetches from Stripe once an hour, with the user ID and email address of the subscribers; your address does not go to Stripe for this. The legal basis is the contract of use (Art. 6(1)(b) GDPR).
The answers are generated by AI and can contain mistakes. tripbot makes no decisions about you that have legal effect or similarly significantly affect you (Art. 22 GDPR): it suggests, you decide.
05
Travel preferences
tripbot remembers what also holds for your next trip, such as who travels with you, how you eat or where you usually fly from, and plans your next trips with it. To do so, an AI model reads every message you type a second time, through OpenRouter. Each line is stored with where it came from and when, a line from the chat also with the words of your message it comes from. What was remembered appears right below your message, where you can undo it. Under “Travel preferences” in your profile you see all of it, say a line anew in your own words or delete it. If you ask tripbot in the chat what it knows about you, it tells you all of it with where it came from; if you ask it to forget something, it deletes it at once.
What you enter yourself or keep with a tap we store because you ask for it (contract of use, Art. 6(1)(b) GDPR). That tripbot derives preferences from your messages by itself and plans your trips with them is profiling (Art. 4(4) GDPR). Its legal basis is our legitimate interest, and yours, in planning trips that fit you without you repeating yourself in every chat (Art. 6(1)(f) GDPR). We weighed it like this: you see every line remembered right away and can undo it, say it anew or delete it; tripbot never remembers specially protected information on its own (see below); your preferences serve only your trips, never advertising; and tripbot decides nothing with them that has legal effect (Art. 22 GDPR): it suggests, you decide. What you say about your travel companions, such as your children’s ages, tripbot only remembers so your trips fit everyone, and deletes it like everything else.
Objection: If you switch off “Use and remember preferences” in your profile, tripbot remembers nothing more and plans at once without your preferences and without your answers to “How was it?”, without you having to give a reason (Art. 21(1) GDPR). What is already stored stays in your profile until you delete it; if you switch it back on, tripbot plans with it again.
Information about health, disability, pregnancy, allergies, religion or sexual orientation is specially protected. tripbot never stores it on its own; it asks “Remember for next time: …?” and stores it only after you tap “Remember”. That is your explicit consent (Art. 6(1)(a), Art. 9(2)(a) GDPR). You withdraw it at any time by deleting the line or asking tripbot to forget it; what happened until then remains lawful.
Preferences stay stored until you delete them or your account. Deleted means deleted, not hidden: the line is gone at once and from the backups after 30 days at the latest (see “Account and sign-in”). tripbot does not learn it again from earlier chats, only when you say it again. What you wrote in the chat stays there until you delete the chat.
06
Trips, hearts and your device
We store trips, hearts and plans with your account until you delete it; you use the app signed in only. What tripbot writes about the hotels of a search we keep for two weeks, tied to no account, so a chat opened again shows it without asking the language model anew; as it comes from your wish, it may contain words of it. It stays if you delete your account earlier and goes by itself after the two weeks.
tripbot sets these cookies, all only for what you yourself want (§ 25(2) no. 2 TDDDG):
- tripbot_at and tripbot_rt: your sign-in; the first lasts about an hour, the second a year or until you sign out.
- tripbot_pkce: a few minutes during sign-in with Google, so nobody can redirect it.
- theme: the design you chose, with the moment you chose it; one year. Without a choice it does not exist. If you chose it in your profile while signed in, our server brings it to your other devices too (see “Account and sign-in”).
- tb_refresh_token: only if you were signed in to the previous tripbot and moving your sign-in did not work just then: the key of that old sign-in, so a later visit tries again; 30 days at most, and it goes as soon as you are signed in here or sign out.
- tripbot_bridge_later: in the same case, ten minutes, so not every visit tries to move your sign-in again at once; it goes like tb_refresh_token.
- gate: only until the launch and only for testers with an access key; 60 days.
In your browser’s storage, too, tripbot keeps only what you are doing (§ 25(2) no. 2 TDDDG):
- the state of open trips (entries starting with “tripbot.”), your first wish while you sign in (used for 30 minutes at most, deleted on your next visit, without photos), which hints you have already seen and short-lived technical markers that go when you close the tab;
- in live mode, which stop is next (“tripbot:live”), and which days you saved for the road (“tripbot:offline”);
- when you follow a shared day and send your location back, a random identifier (“tripbot:follower”);
- so a day of your trip works without a connection: when you open it, a service worker keeps the app’s files, your trip’s pages and their places, the weather and the map style, and with “Save for the road” the map tiles of that day as well. It never keeps your sign-in, account, bookings, payments, the chat or anyone’s location.
None of it leaves your device on its own. tripbot empties the service worker’s storage when you sign in or out, and everything when you delete your account.
08
Booking hotels and flights
When you book a stay, the guest’s first name, last name and email address, together with hotel, room, dates and travellers, go to Nuitée Travel Limited (Dublin, Ireland), the company behind LiteAPI. Nuitée sells the stay, passes the booking on to the hotel and receives the payment. If you have a request for the hotel, such as your arrival time, a cot or a sentence of your own, it goes along too, also when you tell tripbot in the chat. Only write there what the hotel needs to know.
When you book a flight, each traveller’s first name, last name, date of birth, sex, nationality and travel document (type, number, valid until), together with email address and mobile number, go to Nuitée and from there to the airline. It needs them for the booking, to reach you about changes, and for the passenger lists it must send to the authorities of the countries of departure and destination before the flight. If the airline is based outside the EU or you fly to a country outside the EU, Nuitée and the airline pass the data on there because your flight contract requires it (Art. 49(1)(b) GDPR) and the authorities there demand it; tripbot itself only passes them to Nuitée in Ireland. We receive your fellow travellers’ details from you; tell them they can find this policy here. tripbot does not store date of birth or travel document; of a flight booking we keep the travellers’ names and types, the flights, price, contact email and the numbers of Nuitée and the airline.
You pay in Nuitée’s payment form, which appears within our page and runs on the payment service Stripe. You enter your card and account details there; tripbot never sees or stores them. When you open the payment, your browser loads the form from Nuitée (payment-wrapper.liteapi.travel) and Stripe (js.stripe.com); both see your IP address and details about your browser and device. To detect fraud, Stripe checks the device and how the form is used, stores its own cookies for this and may load a check by hCaptcha; which cookies these are and how long they last is set out in Stripe’s cookie policy (stripe.com/cookies-policy/legal). This is strictly necessary for the payment you start (§ 25(2) no. 2 TDDDG). If you pay with Apple Pay or Google Pay, their terms apply as well.
We store each booking with guest, hotel, dates, price, cancellation terms and the numbers of Nuitée and the hotel, so you find it in your profile, can cancel it and get reminders. The legal basis is the contract (Art. 6(1)(b) GDPR).
- Attempts that were not completed (not paid, sold out, payment declined) are deleted after 30 days.
- Bookings are kept as long as tax law requires: eight years from the end of the year in which the trip ends (§ 147(3) and (4) AO, Art. 6(1)(c) GDPR). If you delete your account earlier, the booking stays stored until then, but separated from your account.
Travel companions: If you enter the email address and, if you like, the first name of people travelling with you, at checkout or on the booking page, we send them the confirmation, the reminder and, for a flight, the check-in notes and the airline’s changes, without the price and without a way into your booking. Only add people who agree. The legal basis is the legitimate interest that everyone travelling knows what is booked (Art. 6(1)(f) GDPR). Each of these emails tells them who gave us the address and what we use it for; anyone who wants no more replies to it, and you remove them on the booking page at any time. tripbot also knows their first names in your trip’s chat. We delete addresses and names a week after the trip ends.
Offers: Whether an offer applies to you we check from your account: whether it would be your first booking, since when you get travel tips, and the hotel, dates and price of the stay. If a booking uses an offer, we store with it which one and what it took off; at checkout we create a voucher for exactly that amount at Nuitée, with no details about you. Where bookings with an offer came from (a campaign, a search engine, direct) we only count in total, through the visit of the same day (see “When you open tripbot”). The legal basis is the contract (Art. 6(1)(b) GDPR) and, for the counting, our legitimate interest in seeing which offer works (Art. 6(1)(f) GDPR).
09
Searching hotels, flights and experiences
For prices and availability our server asks LiteAPI (Nuitée) for hotels and flights, and Viator (Viator, Inc., USA) and Tiqets (Tiqets International B.V., Amsterdam, Netherlands) for experiences and tickets. Place, dates and the number and ages of travellers go along, but no name and no address.
With every hotel search, our server also asks Agoda (Agoda Company Pte. Ltd., Singapore) for hotels and their prices, with place, dates, number and ages of the travellers, without name or address. Our server fetches the photos of these hotels (see "Maps and images from other services"). Only when you open a link to Agoda do you reach Agoda's site; the link goes through our server, which counts the tap as a step (see “When you open tripbot”), and carries our partner ID and your trip's dates, so Agoda shows the hotels for your trip and pays us a commission for a booking. Agoda's privacy policy applies there.
You book experiences and tickets on the sites of Viator and Tiqets. The link there goes through our server, which counts the tap as a step (see “When you open tripbot”), and carries our partner identifier so that we receive a commission for a booking; they learn nothing about you from us. Their privacy policies apply on their sites.
10
Maps and images from other services
Maps and photos that come from other services are fetched by our server and passed on to your browser. Those services only learn that our server is asking, not your IP address and nothing about your browser:
- Map images from OpenFreeMap (openfreemap.org)
- Photos of places from Wikimedia Commons, along with who took them and under which licence
- Hotel photos and airline logos from Nuitée’s servers
- Hotel photos from Agoda for the hotels Agoda sells
- Photos of experiences from Viator and Tiqets
- Photos of restaurants from the restaurant’s own website
So that pages load quickly, Cloudflare and your browser keep a copy of these maps and photos, photos for a few days, parts of the map for up to a month. The copy is the same for every visitor and contains nothing about you. Your request itself is processed by Cloudflare and our server as described under “When you open tripbot”.
Our server likewise fetches place details, routes, weather and price indications without any link to you, among others from OpenStreetMap (Nominatim, QLever and Overpass), Wikidata, Wikipedia and Wikivoyage, openrouteservice (HeiGIT gGmbH, Heidelberg), MET Norway, NOAA and NASA POWER; they only learn the trip’s places and dates. What you type at “Where are you staying?” or “Where?”, and where you set a place on the map, it looks up as addresses at Photon by komoot (komoot GmbH, Potsdam), with the rough location of the trip, without your IP address and without your account.
11
Emails
We send sign-in codes, the codes for changing your address, booking confirmations, cancellations, the reminder one or two days before arrival and, for a flight, the check-in notes and the airline’s changes through Resend (Plus Five Five, Inc., USA). Resend receives the address and the content of the email. When Resend has already sent as many emails in a day as our plan there allows, such an email goes through Mailjet (Sinch Mailjet SAS, France), which likewise receives the address and the content. These emails are part of signing in and of the booking (Art. 6(1)(b) GDPR). The one-off email “Your tripbot account has moved” to accounts that moved over from the previous tripbot goes through Mailjet. It only tells you what the move means for your account: how you sign in, what was taken over, that your bookings stay valid and how you delete your account; it contains no advertising. The legal basis is the continued contract of use (Art. 6(1)(b) GDPR) and our legitimate interest in telling you about the move of your account (Art. 6(1)(f) GDPR). Which email went to which address when, with its subject (none for emails that carry a code), and what Resend or Mailjet reports about its delivery (delivered, rejected, marked as spam), we keep for 400 days: so we can check when you ask whether something arrived, and we send no travel tips to an address that does not accept email (Art. 6(1)(f) GDPR). We do not measure whether you open an email, and links in our emails carry nothing that identifies you. Links in travel tips carry the name of their campaign; if you come to tripbot through one, we count your visit with that campaign as described under “When you open tripbot”. These records go with your account.
When you write to us: Cloudflare receives emails to support@, legal@ and hello@trytripbot.com for us and passes them on to our mailbox at Google (Gmail, Google Ireland Limited, Ireland); we send our replies from there through Resend. Emails not about a booking we delete there one year after the last exchange, emails about a booking after six years (§ 147(1) no. 2 AO). If an email comes from the address one of your bookings sends its emails to, and Cloudflare confirms that it really comes from there (DMARC), we also keep it with that booking: sender, subject and your new words, without the quoted email and without attachments. That way we see what has been said when we help. There we also record what we do with the booking (asking LiteAPI, cancelling, sending an email again, writing to you) and when its address was changed. The legal basis is the contract for the booking (Art. 6(1)(b) GDPR). We delete your messages after six years (§ 147(1) no. 2 AO), everything else with the booking.
When you write to us through Help: The help’s search and assistant run in your browser: what you type there does not leave your device. Only a request you send is stored, with its number (TB and six digits): the topic, your message, your email address, your name if you give it, the language, which of the help’s answers you were already shown, and the booking or booking number it is about if you pick or name one; if you are signed in, also your account. The request goes to our mailbox as an email, and you get a confirmation with the number, both through Resend or Mailjet as above. Your name and message appear in the confirmation only when it goes to your account’s address, so nobody can use the form to send something to others. If you reply from the same address and name the number, we keep your new words with the request, as above for a booking; there we also record what we answer and when we close it. The legal basis is the contract for your booking or for using tripbot where the request belongs to it (Art. 6(1)(b) GDPR), otherwise our legitimate interest in answering your question (Art. 6(1)(f) GDPR). One year after its last change we delete the request with everything recorded with it, and at once with your account. The emails about it we delete in our mailbox as under “When you write to us” above.
“How was it?”: The day after check-out we ask you once by email how the hotel was, if the booking went to your account’s address; if you booked for someone else, we do not ask. We store your answer (one of three ratings and, if you like, a sentence) with your account: while “Use and remember preferences” is on in your profile, it shapes your next hotel suggestions, and tripbot knows it in the chat. The legal basis is our legitimate interest in suggesting better hotels to you (Art. 6(1)(f) GDPR; § 7(3) UWG). You can object to this question at any time, with the link “No more questions like this” in every such email or by writing to legal@trytripbot.com. tripbot deletes an answer when you ask it in the chat to forget it; all of them go when you delete your account.
Travel tips: Only if you agree do we send you ideas and tips for your trips and news from tripbot, through Mailjet: with the “Travel tips by email” box when you sign in (never ticked for you), the switch in your profile, or with “Yes, please” when tripbot offers it under a finished plan. If there is an offer for newcomers with travel tips, it applies from the day you agreed, for as long as the offer says; agreeing again later does not move that day. The legal basis is your consent (Art. 6(1)(a) GDPR; § 7(2) no. 2 UWG). As proof we store when you gave it and to which wording. Which tips you get we choose by what you did on tripbot: whether you are planning, a trip is coming up or just ended, where your trips go, since when you have an account, when you last used tripbot and in which language you booked. You can object to this, as to the advertising itself, at any time (Art. 21(2) GDPR, see “Your rights”). You withdraw the consent at any time with the switch in your profile, with the unsubscribe link in every such email (in many mail apps also with one tap next to the sender; Mailjet receives that unsubscribe and passes it on to us) or by writing to legal@trytripbot.com; switched off, we delete the time and the wording. If you unsubscribe through the link, we also store when, so tripbot does not offer the tips again. If you answer the offer with “No, thanks”, we store when, so we do not ask again (Art. 6(1)(f) GDPR); it goes when you delete your account. Apart from travel tips and the “How was it?” question, we send no advertising.
12
Moving from the previous tripbot
If you already had an account in the previous tripbot, you will find it here: we take over the user identifier, email address, sign-in method (Google or email) and name, but no passwords, and your hotel bookings with hotel, dates, room, price, cancellation terms, booking numbers and the guest’s name and email address. The controller is the same provider as before. The legal basis is the continued contract of use, for bookings the booking contract (Art. 6(1)(b) GDPR), for past bookings the duty to keep records (Art. 6(1)(c) GDPR, § 147 AO). If you were signed in to the previous tripbot, our server reads its sign-in cookie on your first visit, has the previous sign-in service (Supabase) confirm it and signs you in here with the same account; the old cookie is deleted at the same time. If our sign-in service does not answer at that moment or does not know your account yet, the confirmed old sign-in stays in the cookie tb_refresh_token, for at most 30 days, and the cookie tripbot_bridge_later holds the next try back for ten minutes. This is strictly necessary for the sign-in you chose (§ 25(2) no. 2 TDDDG). If you signed in there with a password, that sign-in cannot be moved: we only delete its old cookie, and you sign in once by email (link or code). You can delete the account at any time. If you delete a moved account here, we keep only its user identifier, so a later sync with the previous tripbot does not bring it back (Art. 6(1)(c) in conjunction with Art. 17 GDPR); it goes as soon as the previous tripbot is deleted.
Cancelling tripbot Pro: If you subscribed to tripbot Pro in the previous tripbot, you cancel it here under “Cancel contracts here”, also without signing in. You give the email address of the contract, the type of cancellation (for an extraordinary one, its cause) and the date. With the address we look up your contract at the payment service Stripe (Stripe Payments Europe, Ltd., Ireland), through which the subscription runs, and note the cancellation there with its type, date and cause. The confirmation with date and time goes to that address (see “Emails”). An extraordinary cancellation, and one Stripe did not take just then, we also file as a request so we can handle it and answer you (see “When you write to us through Help” under “Emails”). The legal basis is our duty under § 312k BGB (Art. 6(1)(c) GDPR) and the contract (Art. 6(1)(b) GDPR). If you have no contract with us, only the address entered learns so, never the page. Until your subscription ends, Stripe keeps billing it; we keep payments and invoices as long as tax law requires (§ 147 AO).
Withdrawing from the contract: Under “Withdraw from contract here” you withdraw from the contract for using tripbot, also without signing in. You give your name and your account’s email address. The acknowledgement of receipt with content, date and time goes to that address (see “Emails”). At the same time we file the withdrawal as a request, so we can check that it comes from you and then delete your account (see “When you write to us through Help” under “Emails”); the page itself deletes no account, so nobody can delete someone else’s. The page never shows whether an address has an account. The legal basis is our duty under § 356a BGB (Art. 6(1)(c) GDPR). The request stays for one year after its last change, also if we delete your account before, so we can show that and when your withdrawal arrived (Art. 6(1)(f) GDPR).
What remains of the previous tripbot: Until we have taken the previous tripbot down, by 31 January 2027 at the latest, its data stays in its database at Supabase (data centre in Ireland) and, as an encrypted full copy of 31 October 2026, in our storage at Cloudflare in the EU, so we can switch back should the new generation fail (Art. 6(1)(f) GDPR). We delete its error and usage logs at Sentry and PostHog (both in the EU) and at Cloudflare in the same step. After that we keep from the copy only what tax law requires: bookings and payments with the bookers’ names and email addresses, eight years from the end of the year in which the trip ends (§ 147 AO, Art. 6(1)(c) GDPR). If you delete your account before then, we also delete everything there that no such duty covers when we take it down.
13
Data outside the EU
OpenRouter, Exa, Resend, Cloudflare and Viator are based in the US, as are Microsoft (Azure) and DeepInfra, which write the answers through OpenRouter; Supabase is based in Singapore. Stripe passes data on to Stripe, Inc. in the US, Google may process our mailbox’s emails outside the EU too, and Linkup (France) may handle requests in the US, Canada or the Asia-Pacific region too. There is no level of data protection there like in the EU; authorities can access data without you having an effective remedy.
For companies certified under the EU-US Data Privacy Framework (currently Cloudflare, Resend, Stripe, Microsoft and Google), the European Commission’s adequacy decision of 10 July 2023 applies (Art. 45 GDPR). For the others, the European Commission’s standard contractual clauses apply (Implementing Decision (EU) 2021/914, Art. 46(2)(c) GDPR), which are part of our contracts with them; DeepInfra receives the data through OpenRouter, whose contract with us contains these clauses. We are concluding the data processing agreements with Exa and Linkup right now; until then both only receive what “Chat and AI” describes. You find the wording of the clauses in the Official Journal of the EU (L 199 of 7 June 2021); we send you a copy of our contracts on request to legal@trytripbot.com.
14
Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and to withdraw consent with effect for the future (Art. 7(3)).
Objection (Art. 21(1) GDPR): where we rely on our legitimate interest, you can object at any time on grounds relating to your particular situation. You object to remembering and using your travel preferences without giving reasons with the switch “Use and remember preferences” in your profile.
Objection to advertising (Art. 21(2) GDPR): you can object to advertising by email (travel tips and the “How was it?” question) and to choosing tips by what you did on tripbot at any time without giving reasons; we then no longer use your data for it. The link in the email, for travel tips also the switch in your profile, or an email to legal@trytripbot.com is enough.
Global Privacy Control: if your browser sends this signal, that counts as an objection to counting visits and steps.
You download a copy of all your account’s data (account, your sign-ins with IP address and browser, trips with chats, hearts, preferences with where they came from, bookings with their travel companions, your messages about them and what we did with them, your requests through Help with our answers, your answers to “How was it?”, your feedback on tripbot, your steps and visits of the last 90 days and how many messages you wrote on the last few days) yourself under “Download my data” in your profile, as a JSON file other programs can take over. You delete your account with all trips, chats, hearts, preferences, requests, answers and feedback yourself under “Delete account” in your profile. For everything else write to legal@trytripbot.com.
Do you have to give us data? You are under no legal obligation. For an account we need your email address or your Google sign-in; without it you cannot use tripbot. For a booking we need what the checkout marks as required; for a flight, the airline and the authorities require date of birth, sex, nationality and travel document, and without them no flight can be booked. Everything else (name, preferences, travel companions, photos, location) is voluntary; without it tripbot just plans less precisely.
You can lodge a complaint with a data protection authority. Ours is the Bavarian Data Protection Authority (Bayerisches Landesamt für Datenschutzaufsicht), Promenade 18, 91522 Ansbach, Germany.
15
Changes
When what tripbot does changes, we update this policy. The version on this page applies; the date at the top says since when.