Privacy & Cookies

Privacy Policy

Effective 9 October 2026 · Version 2026.6

1. Who we are

1.1 Plantripr ("Plantripr", "we", "us") runs plantripr.com, an AI travel-itinerary service operated from London, United Kingdom. We are the controller of your personal data under the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations (PECR) and, for people in the European Economic Area, the EU GDPR.

1.2 Contact us about privacy at support@plantripr.com. This policy also explains how we use cookies and should be read with our Terms of Service.

2. The personal data we collect

Account
What it includes
Email address, username, display name, profile and cover photo, account ID, sign-in method (email or Google). Optional: first and last name, date of birth, phone number, bio, website, preferences (language, currency, units, dietary needs)
Where it comes from
You, or Google if you sign in with Google
Guest identifier
What it includes
A random guest ID our server gives your browser after the bot check, and how many guest trips it has generated
Where it comes from
Our systems, stored in your browser
Trip planning and saved content
What it includes
Destinations, dates, trip length, travellers, budget, pace, style tags, dietary notes, your prompts, the itineraries we generate, search history, favourite places, visited places and achievements.
Where it comes from
You and our AI
Tripr AI chats
What it includes
Your messages to Tripr AI and its replies, the places, events and tours it found for you, changes it proposed and whether you accepted them, the support requests it drafted, and (for long chats) a short summary of the older messages
Where it comes from
You and our AI
Tripr AI memory (only if you turn it on)
What it includes
What you asked Tripr AI to keep in mind about you or a trip: diet, allergies, kinds of place you avoid, pace, travelling with children, things you like or dislike, short notes
Where it comes from
You, with your approval
Location for "Near me" (only when you tap it)
What it includes
Your device's approximate position (rounded to about 100 m), used for that one search
Where it comes from
Your device, with your permission
Public profile, community and sharing
What it includes
Public profile, trips and travel guides you publish (including images), followers, likes, comments, reports, trips you unlock and trips others unlock from you, people you share a trip with, and their votes and notes
Where it comes from
You and other users
Plan, credits and usage
What it includes
Your plan (Guest, Free, Trial, Premium), monthly allowance used, credit purchases, bonus and creator-reward credits, what credits were spent on, balances and expiry dates
Where it comes from
Our systems
Free-trial record
What it includes
Your email address in a normalised form (for Gmail, dots and +tags removed) and a scrambled (hashed) form of a random device ID from your browser
Where it comes from
You and your browser
Payments
What it includes
Stripe customer ID, subscription status, amounts, currency, dates, card type and last four digits. We never see or store your full card number or security code
Where it comes from
Stripe
Purchase and contract records
What it includes
What you agreed to at checkout and when, cancellation and withdrawal requests (name, email, which purchase, date and time) and the service emails we sent you
Where it comes from
You and our systems
Country for pricing
What it includes
The country your IP address belongs to, used to show prices in pounds, euros or dollars (not stored), and the currency of your first purchase (stored)
Where it comes from
Your IP address, via ipinfo
Google Calendar (optional)
What it includes
Event times, titles and locations, read only, processed and kept in your browser (section 6)
Where it comes from
Google, with your permission
Technical and security
What it includes
IP address (kept by us only as a salted hash for rate limits; our hosting providers keep raw request logs, including IP addresses, for a few days for security), browser and device type, language, error logs, bot-check results
Where it comes from
Your device, Cloudflare
Analytics
What it includes
With your consent: pages viewed, features used, approximate location, device details, and PostHog session replays (typed text hidden, IP addresses anonymised). If you decline: anonymous cookie-free counts only. Also anonymous monthly counts of what people do with places in plans (kept, swapped, removed, favourited, booked), never linked to an account or a trip
Where it comes from
Google Analytics, PostHog; Plantripr (anonymous counts)
Support
What it includes
Emails and requests you send us
Where it comes from
You

Please don't put sensitive information (for example about health or religion) into trip prompts unless you want it used for that trip. We don't need it and don't use it for anything else.

Diet and allergy details you give Tripr AI can be health information. Tripr AI keeps them in its memory only after you have turned memory on (one approval, which you can withdraw at any time in the Tripr AI panel or in Settings → Preferences), and uses them only to make its suggestions fit you.

3. Why we use it and our lawful basis

Create and run your account
Data used
Account
Lawful basis
Contract
Generate, save, edit and share itineraries
Data used
Trip planning, account, sharing
Lawful basis
Contract
Answer your Tripr AI messages, find real places, events and tours, propose changes to your trips, and draft support requests
Data used
Tripr AI chats, trip planning, account (plan and allowance)
Lawful basis
Contract
Remember your preferences across chats and pre-fill the trip form
Data used
Tripr AI memory
Lawful basis
Consent (explicit consent for health details such as allergies); you can withdraw it at any time
Find places near you
Data used
Location for "Near me"
Lawful basis
Consent (your device asks each time)
Apply plan limits and credits
Data used
Plan, credits and usage; guest identifier
Lawful basis
Contract; for guests, legitimate interests (fair use)
Count daily messages and searches, and charge credits only after you tap a button that shows the price
Data used
Plan, credits and usage
Lawful basis
Contract
Allow the free trial once per person
Data used
Free-trial record
Lawful basis
Legitimate interests (preventing abuse of a free offer)
Run public profiles, publishing, likes, comments, reports and unlocks
Data used
Public profile and community
Lawful basis
Contract
Show prices in your currency and stop people paying a cheaper regional price
Data used
Country for pricing
Lawful basis
Legitimate interests
Take payments, give refunds, keep accounts
Data used
Payments, plan and credits
Lawful basis
Contract; legal obligation (tax and accounting)
Record what you agreed at checkout and your cancellation or withdrawal requests
Data used
Purchase and contract records
Lawful basis
Legal obligation (consumer law); legitimate interests (proving what happened)
Send service emails (order confirmations, renewal reminders, cancellations, refunds)
Data used
Account, payments
Lawful basis
Contract; legal obligation
Show Google Calendar conflicts
Data used
Google Calendar
Lawful basis
Consent (you connect it and can disconnect at any time)
Keep the service secure and stop bots, fraud and abuse
Data used
Technical and security, guest identifier
Lawful basis
Legitimate interests
Measure and improve the site
Data used
Analytics
Lawful basis
Consent; for anonymous cookie-free counts when you decline, legitimate interests
Track affiliate referrals
Data used
Outbound link parameters
Lawful basis
Legitimate interests
Handle complaints, disputes and legal claims
Data used
Any relevant data
Lawful basis
Legitimate interests; legal obligation

Where we rely on legitimate interests, we have weighed them against your rights. You can object (section 11).

4. Guests

4.1 You can try Plantripr without an account. Guests can generate 1 one-day trip in total. After a quick bot check, our server gives your browser a random guest ID and counts the trips made with it. The ID doesn't contain your name or email.

4.2 To stop the limit being bypassed by clearing the browser, we also limit guest trips to 10 a day per internet connection. For this we keep your IP address only in a scrambled (salted hash) form.

4.3 If you create an account, trips you saved as a guest on that device are moved into it.

5. AI processing

5.1 We use two AI providers. Google's Gemini models generate itineraries from the trip form. Anthropic's Claude models power Tripr AI, our chat concierge, including trips planned in the chat. We send each provider only what's needed: your messages, trip details and the relevant itinerary, and for Tripr AI also what it remembers about you (if memory is on) and the booking text, screenshot or PDF you choose to share. We never send your password or payment details, and Claude is never sent your location: for "Near me" our server uses your location for that one search and only tells Claude that a location was shared.

5.2 We use the paid Gemini API and Anthropic's commercial API. Under their terms, neither Google nor Anthropic uses our requests to train their models.

5.3 Itineraries are suggestions. We don't make decisions about you by automated means that have legal or similarly significant effects (Article 22 GDPR).

5.4 When you ask Tripr AI what's trending, it searches the web through Anthropic's web search. Only the topic and the city are searched, never your name or account details. The answer shows the websites it comes from; those results are not checked by Plantripr.

5.5 When you use "Add my booking", the text, screenshot, PDF or email you choose is sent once to Claude to read the flight, train or hotel details. We don't store the file or its text; only the booking card you accept is saved in your trip.

5.6 In long planner chats, Tripr AI writes a short summary of the older messages so it can keep following the conversation. You still see every message; the summary is kept with the chat and deleted with it.

6. Google user data (Google Calendar)

6.1 Plantripr's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

6.2 If you connect Google Calendar, we ask for read-only access (calendar.events.readonly). We use it only to show your events next to your itinerary and point out clashes.

6.3 Calendar data and the Google access token are processed and kept in your browser's storage on your device until you disconnect. We don't store calendar events or Google access tokens on our servers, don't use them for advertising, don't sell or transfer them, and don't use them to train AI models.

6.4 You can disconnect in Plantripr's calendar settings or at myaccount.google.com/permissions.

7. Who we share data with

We don't sell your personal data. We share it only with these providers, for the purposes shown:

Supabase (database hosted in London, UK)
What they do for us
Database, sign-in and file storage
Data involved
Account, trips, community, credits, records
Google Firebase Hosting
What they do for us
Hosts the website
Data involved
Technical (IP address, requests)
Stripe
What they do for us
Payments, subscriptions, refunds, receipts, failed-payment emails, fraud checks
Data involved
Payments, email, IP address
Resend (EU region)
What they do for us
Sends our service emails
Data involved
Email address, name, email content
ipinfo
What they do for us
Tells us which country an IP address belongs to, to choose the price currency
Data involved
IP address
Google Gemini API
What they do for us
Generates itineraries from the trip form
Data involved
Trip planning
Anthropic (Claude API)
What they do for us
Tripr AI chat replies, trips planned in the chat, reading bookings you share, web searches for trends
Data involved
Tripr AI chats, trip planning, Tripr AI memory (if on), bookings you share (not stored)
Google Maps and Places
What they do for us
Maps, place details and photos in itineraries
Data involved
Places in your trip, places Tripr AI searches for you (and, for Near me, the rounded location for that one search), IP address
Google Analytics
What they do for us
Site statistics, only with your consent
Data involved
Analytics
PostHog (EU servers)
What they do for us
Product analytics and error tracking. If you accept analytics: usage statistics and session replays (typed text hidden; Tripr AI requests are never recorded in replays). If you decline: only anonymous, cookie-free counts. Tripr AI events are counts and yes/no facts (for example a message was sent, a search ran, a change was accepted), never your messages, files or location
Data involved
Analytics
Google Calendar API
What they do for us
Read-only calendar view, only if you connect it
Data involved
Google Calendar (in your browser)
Cloudflare Turnstile
What they do for us
Checks you're not a bot
Data involved
Technical and security
OpenStreetMap, Nominatim and Photon
What they do for us
Map tiles, place and address search
Data involved
Place names, search terms, coordinates, IP address
OpenRouteService (HeiGIT gGmbH, Germany)
What they do for us
Route lines on travel-guide maps, requested by our server
Data involved
Coordinates of the guide's stops only (no personal data)
Ticketmaster API and Viator API
What they do for us
Event listings and tours for your destination and dates, and searches you ask Tripr AI for
Data involved
Destination, dates and what you searched for
Content and media providers: Google Fonts, cdnjs (Cloudflare), Wikimedia, Unsplash, Tripadvisor's image service, flagcdn
What they do for us
Fonts, icons and images shown on pages
Data involved
IP address (when content loads)
YouTube, Instagram and Trustpilot
What they do for us
Videos or posts a guide author embeds; our Trustpilot reviews widget. Only loaded after you accept them in Cookie Preferences
Data involved
IP address, their cookies

We may also share data with professional advisers, where the law requires it (for example with HMRC or the police), or with a buyer if Plantripr is sold, under this policy.

9. Cookies and similar technologies

We use cookies and browser storage. Embedded content (YouTube, Instagram, Trustpilot) only loads if you agree. For analytics, nothing is recorded until you choose: if you accept, Google Analytics and PostHog use cookies to measure how the site is used, and PostHog may record session replays (anything you type is hidden). If you decline, they only count visits without cookies, without storing anything on your device and without linking the count to you. Change your choice at any time with "Cookie Preferences" in the footer.

Necessary
Name
sb-*-auth-token
Provider
Supabase
Purpose
Keeps you signed in
How long
Until you sign out
Necessary
Name
plantripr_cookie_consent_v2
Provider
Plantripr
Purpose
Remembers your cookie choices
How long
12 months
Necessary
Name
plantripr_guest_id, plantripr_guest_pass
Provider
Plantripr
Purpose
Applies the guest trip limit; the pass lasts 30 minutes
How long
Until you clear your browser (pass: 30 minutes)
Necessary
Name
plantripr_device_id
Provider
Plantripr
Purpose
Prevents repeat free trials from the same browser
How long
Until you clear your browser
Necessary
Name
plantripr_active_trip, trip and form caches
Provider
Plantripr
Purpose
Keeps your itinerary and form if the page reloads; guests' saved trips
How long
Until you clear your browser
Functional
Name
plantripr_ai_conversations, plantripr_tripr_fab_hidden, language, currency and unit preferences, calendar keys
Provider
Plantripr
Purpose
The list of Tripr AI chats on this device (guests; cleared when you sign out), whether you hid the Tripr AI button, display preferences and connected calendar
How long
Until you clear them or disconnect
Necessary
Name
__stripe_mid, __stripe_sid
Provider
Stripe
Purpose
Fraud prevention at checkout
How long
30 minutes to 1 year
Necessary
Name
Turnstile
Provider
Cloudflare
Purpose
Bot protection
How long
Session
Analytics (consent)
Name
_ga, _ga_LN5P573H5H
Provider
Google Analytics
Purpose
Site statistics
How long
Up to 2 years
Analytics (consent)
Name
ph_phc_…_posthog
Provider
PostHog
Purpose
Site statistics and session replays
How long
1 year
Embedded content (consent)
Name
Set by YouTube, Instagram, Trustpilot
Provider
Those providers
Purpose
Showing embedded videos, posts and reviews
How long
Set by the provider

Affiliate partners may set their own cookies on their own websites after you click through.

10. How long we keep data

Account, trips and saved content
How long
While your account is open
Closed accounts
How long
Deactivated and restorable for 30 days, then deleted or anonymised
Invoices, payment records, checkout consents, cancellation and withdrawal records
How long
6 years after the end of the financial year they relate to
Credit and usage records
How long
While your account is open, then as for closed accounts; records tied to a payment are kept with payment records
Tripr AI chats (signed in)
How long
Until you delete the chat or close your account
Tripr AI chats (guests)
How long
30 days after the last message, unless you sign up and they move to your account
Tripr AI memory
How long
Until you remove an item, turn memory off and clear it, or close your account; a trip's memory is deleted with the trip
Booking files you share with Tripr AI
How long
Not stored (read once)
Location for "Near me"
How long
Not stored (used for one search)
Daily message and search counts
How long
120 days
Free-trial record
How long
3 years after the trial, to stop repeat trials
Guest identifier
How long
In your browser until you clear it; our trip count for 12 months
Service email log
How long
2 years
Analytics
How long
Google Analytics up to 14 months; PostHog session replays 30 days, other PostHog data up to 1 year
Anonymous place statistics
How long
Up to 400 days (monthly counts that can't identify you)
Support emails
How long
2 years
Security and rate-limit records (hashed IP)
How long
30 days

Anonymised data can't identify you and may be kept for statistics.

11. Your rights

You have the right to: access your data; correct it; have it erased; restrict how we use it; object to uses based on legitimate interests; receive your data in a portable format; and withdraw consent at any time (this doesn't affect what we did before).

Email support@plantripr.com to use these rights. We'll reply within one month and may ask you to prove who you are. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or the data protection authority where you live in the EEA. Please contact us first so we can try to help.

12. Deleting your account

12.1 You can close your account by emailing support@plantripr.com. It is deactivated straight away and can be restored for 30 days. After 30 days we delete or anonymise your data, except payment and contract records we must keep for 6 years. Your Tripr AI chats and memory are deleted with your account.

12.2 Trips and guides you published are removed from public view when your account is deactivated. Copies that other users unlocked belong to their accounts and stay there. Your comments are deleted with your account.

13. International transfers

Our database is hosted in London (UK) and our email provider sends from the EU. Some providers (including Google, Stripe, Cloudflare and ipinfo) process data outside the UK and EEA, including in the United States. We protect these transfers with adequacy regulations or decisions (including the UK Extension and the EU–US Data Privacy Framework where the provider is certified), or with standard contractual clauses and the UK International Data Transfer Addendum.

14. Security

We use HTTPS encryption, encryption at rest by our database provider, access controls and bot protection. No online service is perfectly secure; if a breach puts you at risk, we'll tell you and the regulator as the law requires.

15. Age limit

Plantripr is for people aged 18 or over. When you sign up you confirm you are 18 or over. If we learn an account belongs to someone under 18, we'll close it and delete its data.

16. Changes to this policy

We'll post changes here with a new effective date. If a change materially affects you, we'll email you before it applies.

17. Contact

Plantripr, London, United Kingdom · support@plantripr.com