Privacy Policy
Tripsora Dining is operated by Tripsora Capitals Ltd. First come the details specific to Tripsora Dining, then the privacy policy of Tripsora Capitals Ltd, which covers all Tripsora services.
Tripsora Dining: guests
When you book a table, we collect your name, email, optional phone number, the restaurant, date, time, number of people and any note you write. We pass them to the restaurant so it can expect you, we email you a confirmation (and one reminder about a day before, for bookings made more than a day ahead) with a link to view or cancel, and we tell the restaurant if you cancel. We charge nothing and never see your card number: any payment is between you and the restaurant. Our legal basis is performing the booking you asked for, and our legitimate interest in keeping the service secure and preventing abuse. The restaurant that receives your booking becomes responsible for that data and may use it only to serve and manage your booking.
Notes. Please do not put health details in the notes box unless you need to, for example an allergy. If you do, you are choosing to share it with the restaurant so it can look after you, and we pass it on only for that purpose.
Booking details are anonymised automatically about 12 months after the booking date. To have your data removed sooner, contact privacy@tripsora.com. The cancel link in your emails is private to you: anyone who has it can view and cancel the booking.
We count presses of a restaurant's website or phone link, so we can see what is useful; this count is not linked to you unless you are signed in.
Our own visitor statistics. We count page views on our own server with no cookie and no local storage. For each view we store the page address, the website you came from, whether your device is a phone or computer, and a short one-way code made from your IP address and browser type that changes every day, so it cannot follow you from one day to the next. We do not store your IP address in these statistics. Visits from signed-in admins are not counted, and we skip the count if your browser sends Do Not Track or Global Privacy Control. This data is deleted after 90 days. Our legal basis is our legitimate interest in knowing whether the site is being used.
Booking reminder. If you create a guest account and, two days after confirming your email, have not pressed a restaurant link while signed in or made a booking, we send you one reminder email. Every reminder has a link to stop it, and we send no second reminder. Our legal basis is our legitimate interest in helping you finish what you started.
Searches. When you use a search box we store the words you typed (in lower case), how many results they found, the day, and the same short one-way daily code as above, so we can see what visitors look for and which places we do not cover yet. We do not store your IP address with it, and we skip it if your browser sends Do Not Track or Global Privacy Control. Please do not type personal details into a search box. Searches that look like an e-mail address, a web address or a long number are not stored. This data is deleted after 12 months. Our legal basis is our legitimate interest in improving the service.
Restaurants listed from OpenStreetMap
Listings of restaurants that have not joined Tripsora Dining come from OpenStreetMap, a public community map (© OpenStreetMap contributors, ODbL). For each we hold what the map publishes about the business: its name, address, location, phone number, website, opening hours, cuisine and sometimes a business email address. For a sole trader this can be personal data. We use it to show a useful listing and, where an email is published, to tell the business about Tripsora Dining. The email address is never shown on the site. Our legal basis is our legitimate interest in helping people find restaurants. If you run one of these businesses you can ask us to correct or remove the listing, or object to its use, at any time: write to privacy@tripsora.com or cs@tripsora.com.
Tripsora Dining: restaurant owners
We store the details you give us: your name, email, password (as a one-way hash), phone number, languages, city, business name, team members, and your restaurants, descriptions, photos, addresses and map locations, contact details, tables, opening times and closed days (the opening hours and closed days you set are used to show guests free times), and the bookings you receive. We also keep billing records from Stripe (plan, invoices, any verification payment) but never your card number. Your restaurant pages, including the name, address, photos, description, hours and the contact details you choose to publish, are public; your account email and password are not. Guests' names, emails, phone numbers and notes are shared with you when they book.
When you ask to claim a listing we hold your name, email, phone, role and message so that we can check the claim. We use this data to run your account and listings, to bill you, and to email you about bookings and your account. Our legal bases are performing our contract with you, our legitimate interests (security, preventing abuse, improving the service) and, where the law requires it, legal obligation (accounting records are kept for up to 7 years). You can download all of your data or delete your account at any time from Dashboard → Privacy. Deleting removes your profile, restaurants, photos and team accounts; bookings are anonymised about 12 months after the booking date, and invoices and audit records may be kept as required by law.
Prospective restaurant owners (outreach)
If you run a restaurant, we may email you once or twice to invite you to claim or list it on Tripsora Dining. Who: Tripsora Capitals Ltd, 124 City Road, London EC1V 2NX. What we hold: your business name, the business email address and website published by your business or on the public map, the place and country you operate in, and a record of what we sent you, whether you replied, joined or opted out. We only use email addresses that your business publishes. Where we got it: your own public website, public web search results and OpenStreetMap; each email says where. Why and legal basis: our legitimate interest in telling relevant businesses about a service for them (UK PECR permits business-to-business email to corporate subscribers if there is a clear way to opt out; sole traders are only contacted at a business address). Who sees it: our staff and our email provider; we do not sell or pass it on. How long: we delete a prospect's record when they ask us to, and routinely remove prospects who have not replied after about 12 months. The sign-up link in our email carries a reference code, so that if you create an account we know it came from our email. Every email has an unsubscribe link, and you can also write to privacy@tripsora.com; we then add you to a suppression list so you are not contacted again.
Tripsora Dining: cookies and partners
Cookies that Tripsora Dining needs to work (sign-in) are always on. Everything else, including Google AdSense advertising, ShareThis share buttons and cookie-based Google Analytics, starts only if you choose Accept all in the cookie banner; Reject non-essential keeps it off. You can change your choice at any time with Cookie settings in the footer, and a browser Global Privacy Control signal counts as Reject. The full list is in the Cookie Policy.
Maps showing where a restaurant is come from OpenStreetMap. The map loads only when you press its button (or have chosen Accept all), and then OpenStreetMap receives your IP address and may set cookies; its own privacy policy applies from then on.
Who we share data with and transfers abroad
We use providers to run Tripsora Dining: our web hosting and backups; email delivery (our mail server at mail.tripsora.com); Stripe (owner payments); Google (AdSense and Analytics, only if you accept cookies); ShareThis (share buttons, only if you accept cookies); and OpenStreetMap (maps and listing data). Some of these are outside the UK/EEA, including in the United States. Where they are, we rely on adequacy decisions, the UK/EU data-transfer safeguards or standard contractual clauses. We share data with authorities where the law requires it. We do not sell personal data.
How long we keep data
Prospective owners: as set out above. Bookings: anonymised about 12 months after the booking date. Accounts: until you delete them. Owner billing and invoice records: up to 7 years. Server and security logs: a short period, then deleted.
Your rights
Under UK and EU GDPR you can ask for access to, correction of, or deletion of your personal data, and you can object to processing. Contact privacy@tripsora.com.
Privacy Policy of Tripsora Capitals Ltd
This policy covers all Tripsora services, including Tripsora Dining. For Tripsora Dining, the details above apply first.
Summary
- Controller: TRIPSORA CAPITALS LTD is responsible for your personal data.
- What we use: your email address and first name (to verify you), your chat messages and travel preferences (to plan your trip), your route requests on routeplanner.ai (to plan your drive), payment confirmations and billing details (for question packs), and technical data.
- Map and routing services: on routeplanner.ai, the place names and coordinates of your stops are sent to map and routing services (Photon, Nominatim, OSRM, Mapbox) – without your name or email address.
- AI providers: your messages are processed by Groq and Google (Gemini API) to generate answers. We do not send them your email address. We do not use your data to train AI models, and under the terms that apply to our use, Google does not use it to improve its products.
- How long: conversation context 7 days after your last message; chat records 30 days; saved preferences until you delete them; shared plans 180 days; payment records 7 years. Route conversations on routeplanner.ai are not stored on our servers.
- Your rights: access, correction, deletion, restriction, portability and objection – email privacy@routeplanner.ai.
1. Who we are
TRIPSORA CAPITALS LTD (Company Number 16549250), 124 City Road, London EC1V 2NX, United Kingdom, is the controller for personal data processed through tripsora.com, routeplanner.ai, trip-planner.ai and tripbuilder.ai. Contact: privacy@routeplanner.ai.
2. What we collect
2.1 Information you give us
- Email address and first name; account password if you create an account
- Chat messages to our AI services and the travel details they contain (destinations, dates, who travels, budget, interests)
- Route requests to the RoutePlanner.ai route assistant: start, destination and stops, travel days, route wishes (for example avoiding tolls) and vehicle details you mention (for example an electric car's range)
- Travel preferences the AI agent saves for you (home airport or city, number of adults and children, children's ages, budget style, interests, currency)
- Itinerary requests and support enquiries
- Billing name, email and address entered at Stripe checkout (we do not receive full card details)
2.2 Information collected automatically
- IP address (used for rate limiting and security), browser language, device and browser type
- Usage data and server logs (requests, errors, which tools the AI agent used)
- If you accept analytics cookies: anonymous events in Google Analytics that show which steps of our services are used (for example opening the chat, reaching the sign-in screen, sending a question, receiving a plan, clicking a booking link, seeing or using the payment screen), together with the language of the page. These events never contain your messages, email address or name.
- Approximate location derived from your IP address where our analytics use it; precise location only with your consent
- Cookies and similar technologies – see our Cookie Policy
2.3 Payment information
Payments are processed by Stripe. We receive confirmation of the payment (amount, currency, date, Stripe session reference) and the email address used; we never receive or store full card numbers. See Stripe's privacy policy.
Trip Pack. If you buy a Trip Pack, Stripe takes the payment and e-mails you a receipt. We do not keep an order database: we look up your payment at Stripe each time the pack is opened (using the payment reference in your link, the plan it was bought for and the e-mail address you paid with), and we e-mail you the link to your pack using that address. We store a one-way hash of the payment reference so that we send that e-mail only once automatically.
2.4 Sponsors
If you apply to sponsor our websites we collect your company name, website, contact name and email address, any message you send, the tier and sites you choose, the display name, short description, link and logo you provide for your listing, and the date and time you accepted our Terms. We store a one-way hash of your IP address with your application to prevent abuse. Signing in to the sponsor dashboard uses a strictly necessary session cookie that ends when you close your browser. We count clicks on sponsor links as daily totals per sponsor, without identifying the visitor. Your display name, description, link and logo are published on our websites (and your name may appear in our posts on X) once we approve them.
2.5 Creators
If you apply to be a creator on trip-planner.ai we collect: your name, e-mail address, chosen handle, a password (stored only as a one-way hash) and your country; the profile information you add (photo, bio, social media handles); the Trips you write, including text, photos, links and embedded clips; the date you accepted the Creator Terms; sign-in times, security and activity records (including IP address); and the content moderation decisions we make. If you add a tips link or a full-guide link, we store the web address you enter.
Creator account fee. A creator pays a one-off £5.00 account set-up fee (no VAT) by card through Stripe. Stripe collects and holds the card details and the billing name and address, and e-mails the receipt; we never see or store a card number. We receive and keep confirmation of the payment: the amount, currency, date, the Stripe reference and the status, together with the version of the Creator Terms the creator accepted, when they accepted it, and a scrambled (hashed) form of their IP address, so that we can answer a payment dispute. We keep that payment record for 7 years (accounting law), also after an account is deleted, but not linked to the creator's name or e-mail address. We do not pay creators for sales or commissions. If we agree a fixed fee with a creator for a commissioned Trip, we use the bank details they give us only to pay that fee, and keep the payment records for 7 years (accounting).
Deleting a creator account. A creator can delete their account themselves at any time from their dashboard (or ask us to, at cs@tripsora.com). It takes effect immediately: we delete the profile, photo, bio, all Trips and their cover photos, copies in readers' Remix results, the visit, click and rating totals, the e-mail address, the password hash and the security log. We keep only the payment record described above and any complaint record (section 2.8). Search engines and other sites may keep copies of public pages for a while; we cannot control that, and we will help you ask for removal.
Your name, handle, photo, bio, country, social handles and published Trips are public on your creator page and can be found by search engines.
If you use the AI import, the text you paste is sent to our AI providers to produce a draft itinerary. We do not store the pasted text; we only record that you used the feature and its length.
2.6 Readers on creator pages
If you rate a Trip with the stars, we add your rating to an anonymous total for that Trip (for example "one more 5-star rating"). We do not store who rated, and creators see only the totals. To stop ratings being stuffed, we keep a scrambled (hashed) form of your IP address for up to two days to count how many times you rated; we do not keep the IP address itself for this.
When you visit a creator page, or click a booking, full-guide or tips link on it, we add one to a daily total for that creator and Trip. Links go through our own address (trip-planner.ai/go/...) which counts the click and sends you on to the partner or creator's site. The totals do not include your IP address, a cookie or any identifier, so we cannot tell who visited; automated visits and creators' own visits are not counted. We do not set a cookie to remember which creator you visited, and creators do not receive your personal data: they see totals only.
If you use "Remix", we process the dates, number of travellers, budget, pace and interests you enter (and any note you type), and the Creator Trip you chose, to generate your plan. We send these to our AI providers (Groq and Google). We keep your answers and the plan for 30 days at a private web address (a long random link that only people you share it with can open), together with a scrambled (hashed) form of your IP address that we use to limit abuse; we do not store your IP address itself, your name or your e-mail. Please do not put personal details in the note.
2.7 Itinerary emails, pre-trip tips, newsletter and accounts
On TripBuilder itineraries and Trip-Planner trip pages you can ask us to email you a link to the itinerary. We first send a 6-digit code to the address to confirm it is yours (the same code check as the Tripsora AI agent). We keep a record that the address was verified, and your browser keeps a signed confirmation for up to 30 days so that you do not need a new code each time.
Pre-trip tips (optional). If you tick this, we keep your email address (encrypted), the itinerary link and title, the destination and your travel date, so that we can send you one email with a practical checklist a few days before you travel. That email may contain partner links, for example to tours or an eSIM, on which we may earn a commission. We delete these details as soon as that email has been sent, once your travel date has passed, or straight away when you use the cancel link in our email. In the Tripsora AI agent you sign up with the “Pre-trip tips by email” button after emailing yourself a plan, and we send you a short notice with a cancel link.
Plan reminder (optional). In the Tripsora AI agent and on TripBuilder, a new plan is followed by a “Your plan is saved” card with a button to email the plan to yourself and an unticked box to be reminded. If you tick it, we keep your email address (encrypted), the link and title of the plan, the destination, the language you use on the site and the reminder date, so that we can send you one reminder about three days later, unless you click a booking link in the chat before then. The reminder may contain partner links, for example to tours or an eSIM, on which we may earn a commission. We send you a short notice when you set the reminder, with a cancel link. We delete these details as soon as the reminder has been sent, as soon as you click a booking link while signed in, straight away when you use the cancel link, and in any case after 14 days. Your browser remembers which plans you asked a reminder for, so that it can cancel them if you book.
Newsletter (optional). If you tick this, we add your address to our newsletter list with our email provider, Brevo. You can unsubscribe at any time with the link in every newsletter.
Account (optional). If you tick this, we create a Tripsora account for your verified address, with the password you choose or a temporary password that we email to you and that you should change. Accounts are also added to our accounts list with Brevo, for service emails about your account.
The legal basis for the tips, the plan reminder and the newsletter is your consent, which you can withdraw at any time. For the account it is our contract with you to provide it.
2.8 Copyright and content complaints
If you send us a complaint through trip-planner.ai/report or by e-mail to copyright@tripsora.com, we collect your name, e-mail address, company (if any), your connection to the work, the addresses of the pages you report, your description of your work and where the original is, the statements you tick and your typed signature, the date, and a scrambled (hashed) form of your IP address to stop abuse. We use this to review the complaint, to act on it (for example removing content), to reply to you and to deal with disputes. We may share your name and the details of your complaint with the person who published the content so they can respond, but not your e-mail address. We keep the complaint record, our decision and what we did for up to 6 years after we close it. The creator's handle is kept on the record even if they later delete their account.
3. The Tripsora AI travel agent in detail
| What | Why | Where it goes |
|---|---|---|
| Email address and first name, verified with a 6-digit code | To identify you, count your free and paid questions, and address you by name | Our servers; verification codes are sent by email |
| Your messages and the last messages of the conversation | To understand your request and keep the conversation coherent | Our servers; sent to our AI providers (Groq, Google) with your first name and saved preferences – never your email address |
| Saved travel preferences | So you don't have to repeat them in later conversations | Our servers; included in requests to our AI providers |
| Trip details needed for searches (cities, airports, dates, number of travellers, hotel and activity names) | To find recent flight fares, create booking links, check the weather and place your stops on a map | Travelpayouts (fares and links), Open-Meteo (weather), Mapbox (map locations). These requests contain no name or email address. |
| Booking links you click | To take you to the Partner with your trip details filled in | The Partner receives the destination, dates and number of travellers in the link, plus whatever you enter on their site |
| Shared plans | So you can open, email or share a plan | Our servers; anyone with the share link can view the plan |
| Question balance and payments | To provide free and paid questions and handle refunds | Our servers; Stripe for payments |
| Plan emails you request | To send the plan to your own verified address | Our email server; the email includes a map image loaded from Mapbox |
The agent also detects the language you write in, to answer in that language. This uses only the text of your messages.
3A. The RoutePlanner.ai route assistant in detail
| What | Why | Where it goes |
|---|---|---|
| Email address and first name, verified with a 6-digit code | To identify you and count your free and paid route questions | Our servers; verification codes are sent by email |
| Your message, up to the last 12 messages of the conversation and your current route (stop names, coordinates, route wishes) | To plan or change your route | Our servers; sent to our AI provider Groq – never your name or email address |
| Place names of the stops | To find their coordinates | Photon (Komoot) and, if needed, Nominatim (OpenStreetMap Foundation). These requests come from our server and contain no name, email or IP address of yours. |
| Coordinates of the stops and route wishes (avoid tolls, motorways, ferries) | To calculate roads, distances and driving times | The OSRM routing service run by FOSSGIS e.V. Requests come from our server and contain no personal details. |
| Coordinates along your route (points on the road) and, for electric cars, that you want charging stops | To find real charging stations and fuel stations near your route | Open Charge Map and, as a fallback and for fuel stations, the Overpass API (OpenStreetMap data). Requests come from our server and contain no name, email or IP address of yours. |
| The route shown on the map | To draw the map and the road line in your browser | Mapbox, which receives the stop coordinates and your IP address |
| Hotel and Google Maps links you click | To show hotels at an overnight stop or open the route in Google Maps | Stay22 and its hotel partners, or Google, receive the place or route in the link, plus whatever you enter on their site |
| Question balance and payments | To provide free and paid route questions and handle refunds | Our servers (email address, free and paid questions, number of questions, Stripe payment reference, amount); Stripe for payments, invoices and receipts |
The route assistant does not save travel preferences and does not keep a record of your conversations on our servers. Our server logs keep a short excerpt of each request and the stop names for troubleshooting (see section 7).
4. Purposes and legal bases
| Purpose | Legal basis (UK GDPR) |
|---|---|
| Providing the AI travel agent, the route assistant, itineraries and other services you request; email verification; counting questions | Contract (Art. 6(1)(b)) |
| Reviewing sponsor applications, managing sponsorships, publishing approved listings, billing, and sending sponsor emails and click reports | Contract or steps before entering a contract (Art. 6(1)(b)); legitimate interests in running our sponsor programme (Art. 6(1)(f)) |
| Payments, refunds, accounting and tax records | Contract and legal obligation (Art. 6(1)(b), (c)) |
| Saving travel preferences for later conversations | Legitimate interests in a convenient service (Art. 6(1)(f)) – you can delete them at any time |
| Security, preventing abuse (rate limits, one allowance per person), troubleshooting | Legitimate interests (Art. 6(1)(f)) |
| Keeping chat records for support, quality and improving our service | Legitimate interests (Art. 6(1)(f)) |
| Analytics, advertising and non-essential cookies | Consent (Art. 6(1)(a)) |
| Marketing emails | Consent, or soft opt-in for customers (PECR) |
| Pre-trip tips and one-off plan reminder emails that you ask for | Consent (Art. 6(1)(a)) |
| Running creator accounts, publishing Trips, approving and moderating creators, and showing creators their totals (account and profile data, Trips, activity records) | Contract; legitimate interests (safe, accurate content) |
| Generating Remix plans and draft itineraries from pasted notes (Remix answers, pasted text, the Trip used) | Contract (the feature you asked for) |
| Taking the one-off creator account set-up fee and keeping the payment record (Stripe reference, amount, date, terms accepted, hashed IP), including to answer payment disputes | Contract; legal obligation (accounting records) |
| Selling a Trip Pack: taking payment through Stripe, opening your pack after payment and e-mailing you the link (payment reference, plan reference, e-mail address) | Contract; legal obligation (accounting records, held by Stripe) |
| Handling copyright and content complaints, taking content down, counter-notices and strikes (reporter and creator details, decisions) | Legitimate interests (protecting rights holders and ourselves); legal obligation where a court or authority requires it |
| Rating Trips and preventing abuse such as fake accounts or rating stuffing (scrambled IP counters for readers; IP address in creators' security log) | Legitimate interests |
Please do not include special category data (for example health information) in your messages. If you do, we process it only to answer your request, on the basis of your explicit choice to share it.
5. Who we share data with
| Recipient | Role and data |
|---|---|
| Groq, Inc. (GroqCloud, USA) | Processor – generates AI answers from your messages, conversation context, first name and saved preferences (Tripsora AI); and from your messages, conversation context and current route, without name or email (RoutePlanner.ai) |
| Google (Gemini API) | Processor – generates AI answers (same data as Groq) when used; under the Gemini API terms that apply to our use, Google does not use prompts or responses to improve its products and logs them only for a limited time for abuse prevention |
| The public and X (x.com) | Sponsor display name, description, link and logo that you submit and we approve, shown on our websites; sponsor names may be named in our posts on X |
| Stripe | Payment processing (independent controller for its own regulatory purposes) |
| Travelpayouts | Recent flight fares and creation of tracked booking links (routes, dates, number of travellers – no name or email) |
| Mapbox (USA) | Map display in your browser (receives your IP address), drawing routes on roads on routeplanner.ai (stop coordinates) and finding the locations of places in plans (place names only) |
| Komoot (Photon, Germany) and OpenStreetMap Foundation (Nominatim, UK) | Finding the coordinates of route stops (place names only, sent from our server) |
| FOSSGIS e.V. (OSRM routing service, Germany) | Calculating roads, distances and driving times (stop coordinates and route wishes only, sent from our server) |
| Open Charge Map (United Kingdom) and the operators of public Overpass API servers (OpenStreetMap data) | Finding charging and fuel stations near your route (coordinates of points on the road only, sent from our server). Charger data is licensed CC BY 4.0 (Open Charge Map and its data providers) and ODbL (OpenStreetMap contributors). |
| Cloudflare (cdnjs) | Delivers the map software used on routeplanner.ai to your browser (receives your IP address) |
| Open-Meteo | Weather data (destination and dates only) |
| Hosting and email providers | Store our databases and send verification codes and plan emails |
| Booking Partners (e.g. Trip.com, hotel sites via Stay22, GetYourGuide, Kiwitaxi, Ubigi) | Only when you click a link: trip details in the link; their own cookies and terms apply |
| Google Analytics and advertising partners | Only with your consent – see the Cookie Policy |
| Authorities | Where required by law |
| The public | Creator name, handle, photo, bio, country, social handles and published Trips, shown on trip-planner.ai |
| Groq, Inc. and Google (Gemini API) | Processors – generate draft itineraries from creators' pasted notes and Remix plans from readers' inputs (see the existing entries) |
| Ko-fi, Buy Me a Coffee, Patreon, Gumroad, Lemon Squeezy (links chosen by creators) | If you click a creator's tips or full-guide link you go to that website, which receives what your browser sends. Any purchase or tip is between you, the creator and that website; we do not receive your payment details or data. |
| Stay22 and GetYourGuide (partners) | When you click a booking link on a creator page you go to their website; they receive what your browser sends and the campaign tag (which identifies the creator page, not you) |
| TourRadar (group tours widget) | Trip pages on trip-planner.ai include a widget from TourRadar that lists guided group tours. When you scroll to it, your browser loads TourRadar's script and content from TourRadar's servers (assets.api.b2b.tourradar.com), so TourRadar receives your IP address and browser details and may set cookies or use similar technologies, under its own privacy policy. If you click a tour and book, TourRadar tells us about the booking so that we can be paid a commission. No cookie of ours is involved in loading the widget. |
| Pexels (photos of destinations) | Trip pages show free photos of the destination, loaded from Pexels' servers (images.pexels.com) with the photographer credited. Pexels receives your IP address and browser details when the photos load, under its own privacy policy. No cookie of ours is involved. |
| YouTube, Instagram, TikTok and X | If a creator embeds a clip, your browser loads it from that service only after you press "Load video"; that service may then receive your IP address and set its own cookies (see the Cookie Policy) |
We do not sell your personal data.
6. International transfers
Some recipients are outside the UK (for example in the USA). We rely on UK adequacy regulations, the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, together with appropriate security measures.
7. How long we keep data
| Data | Retention |
|---|---|
| AI agent conversation context (last messages of a conversation) | 7 days after your last message |
| RoutePlanner.ai route conversations | Not stored on our servers; kept only in your open browser page |
| AI agent chat records (questions, answers, email, first name, language, tools used) | 30 days |
| Saved travel preferences | Until you delete them ("Forget my preferences") or ask us to |
| Shared plans | 180 days, or earlier on request |
| Question balances (Tripsora AI and RoutePlanner.ai) | While the assistant is offered, or until you ask us to delete it (unused paid questions are then refunded where applicable) |
| Payment records | 7 years (tax and accounting) |
| Sponsor records (company and contact details, listing content, click totals) | While the sponsorship lasts plus 2 years, or earlier on request (payment records follow the 7 year rule above) |
| Sponsor applications that are not approved | 12 months |
| Earlier chatbot history and Message Boost session data | 90 days |
| AI-generated itineraries | Until the trip date, then deleted within 30 days |
| Account information | For the life of the account plus 2 years |
| Map location cache (place names and coordinates only) | No personal data; kept to speed up maps |
| Server and security logs (including short request excerpts and route stop names) | For a limited period needed for security and troubleshooting |
| Support communications | 3 years from last contact |
| Analytics data | 26 months |
| Plan reminders (opt-in): email address (encrypted), plan link and title, destination, language | Until the reminder is sent (about 3 days), you click a booking link or you cancel; 14 days at most |
| Marketing preferences | Until you withdraw consent |
| Creator account and profile | While the account is open. Deleted immediately when the creator deletes the account (or when we do so on request). Public pages may remain in search engines for a while. |
| Creator account fee payment record (amount, date, Stripe reference, terms version accepted, hashed IP; no name or e-mail after deletion) | 7 years (accounting) |
| Trip Pack payment record (held by Stripe; we keep only a one-way hash of the payment reference) | Stripe keeps payment records as its policy and the law require (accounting: up to 7 years). The link e-mail is not stored by us. |
| Copyright and content complaints and our decisions | Up to 6 years after the complaint is closed |
| Creator Trips and uploaded images | While the account is open. Deleted at once when the account is deleted (copies in Remixes already created are deleted at the same time; copies may remain in backups for a limited time). An unpublished Trip is kept as a draft until the creator or we delete it. |
| Payment records for commissioned Trips (if any) | 7 years (tax and accounting) |
| Creator sign-in and security records | 90 days, then deleted automatically |
| Daily visit and click totals (no personal data) | 400 days, then deleted automatically |
| Pasted notes for AI import | Not stored |
| Remix answers and generated plans (with hashed IP) | 30 days, then deleted automatically |
Itinerary emails and pre-trip tips: a plain itinerary email is not stored. For pre-trip tips, we keep your details until the tips email is sent, for at most 7 days if you do not confirm, and never beyond your travel date (see 2.7). For plan reminders, we keep your details until the reminder is sent (about three days), until you click a booking link or cancel, and for no more than 14 days.
8. Data stored on your device
The AI travel agent stores in your browser's local storage: your verified email address, first name and verification time; a copy of your recent conversation (up to 30 messages, including plan and map data); your conversation reference; the time until you can send the next question; and whether you accepted the notice. This data stays on your device; "Sign out" and "New trip" remove parts of it, and clearing your browser data removes all of it. Details are in our Cookie Policy.
The language picker stores the language you choose (ts_lang) in your browser's local storage on tripsora.com, tripbuilder.ai, routeplanner.ai and trip-planner.ai. If you ask for a plan reminder, the AI agent also stores the references of those plans (tsa_remind, up to 10) so that it can cancel the reminder if you click a booking link.
On routeplanner.ai, the route assistant stores in your browser's local storage your verified email address, first name, a signed sign-in token and the verification time, for up to 30 days. Your route conversation is not stored on your device; it is lost when you close or reload the page. A strictly necessary session cookie connects your browser to our service and limits the number of messages per hour. "Sign out" removes your details from your device.
9. AI and automated processing
- We use AI to generate answers, plans, routes and itineraries. AI suggestions are recommendations only – you decide what to book.
- We make no decisions based solely on automated processing that have legal or similarly significant effects on you. Automated limits (free questions, waiting times, rate limits) apply equally to all users.
- We do not use your personal data to train AI models.
- You can ask for an explanation of how a recommendation was made, or for a human to review a concern, at privacy@routeplanner.ai.
- Creators' pasted notes and readers' Remix inputs are processed by AI to produce drafts and plans. These are suggestions you review; no decision with legal or similarly significant effect on you is made by AI alone. Creator applications are decided by our team.
10. Security
We use encryption in transit (TLS), access controls, signed tokens for verified email addresses, separation of secrets from website files, and monitoring. If a personal data breach is likely to result in a risk to you, we will notify the ICO within 72 hours and inform you without undue delay where required.
Creators' e-mail addresses are stored encrypted (AES-256-GCM) and passwords are stored only as one-way hashes. Sign-in and security records are deleted after 90 days.
11. Your rights
Under the UK GDPR you can ask to access, correct, delete, restrict or port your data, object to processing based on legitimate interests (including saved preferences and chat records), and withdraw consent at any time. Some rights you can use directly: "Forget my preferences" deletes saved preferences; "Sign out" removes your details from your device. For everything else email privacy@routeplanner.ai or write to our address. We reply within one month (extendable by two months for complex requests) and may ask you to verify your identity.
12. Children
Our services are only for people aged 18 or over, and we ask users to confirm this before using our AI assistants. We do not knowingly collect data from children. Travellers may tell the agent their children's ages to plan a family trip; we use this only for that purpose. If you believe a child has used our services, contact us and we will delete the data.
13. Marketing
We send marketing emails only with your consent or, for customers, about similar services (soft opt-in). You can unsubscribe in any email or by contacting us. Service emails (verification codes, plans you request, payment confirmations) are not marketing.
14. Complaints
Please contact us first. You can also complain to the Information Commissioner's Office (ICO), Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF – ico.org.uk, 0303 123 1113.
15. Changes to this policy
We will post updates here and change the date above. For material changes we will notify you by email (if we have your address) or on the website, and ask for consent again where the law requires it.
Related documents: Terms of Service · Privacy Policy · Cookie Policy · Disclaimer & Affiliate Disclosure · Digital Product Purchase Agreement · Creator Terms
Contact: privacy@routeplanner.ai (privacy and general) · support@tripsora.com (technical) · billing@tripsora.com (payments and cancellations)