Privacy policy

Tourisma is the trip planner at tourisma.app. For your personal data we are the Data Fiduciary.

Contact for anything in this policy: support@tourisma.app

Your account. Your email address, a username and a password. The password is stored hashed by our sign-in provider; nobody at Tourisma can read it. You need an account to save and share trips.

Trips you save. Destinations, dates, group size, budget, the day-by-day plan, any notes, and whether you have made the trip’s link public.

Group trips. If you join someone’s shared trip or write in its chat, we store that you joined and what you wrote. Other people on that trip see your messages with your username.

Reminders and reservations. A season reminder you set on a destination guide (the destination and the month). Fare watches you turn on for a saved trip (the flight routes, the month, and the fares we have seen). If you reserved the early-access offer while it ran, we keep that reservation with your email address.

What you type into AI features. The sentence you type to describe a trip, a sentence asking to change a plan, and descriptions you search for on Explore. These are sent to our AI providers (section 4) to be understood. We don’t send your name, email or account with them.

Analytics. We use PostHog to see how the site is used: the pages you view, the buttons and features you use, errors your browser hits, your device and browser, and your approximate location worked out from your IP address. PostHog also records sessions — what the page looked like and where you clicked — with everything you type masked. PostHog gives your browser a random identifier, kept in a cookie and local storage on our domain, so visits from the same browser are linked across sessions. When you are signed in, that identifier is linked to your account id and username — never your email address. On the live site we may also use Google Analytics for traffic reporting, which sets its own cookies.

Technical data. Your IP address is used to rate-limit requests; it sits in short-lived counters that expire within about two days. When something breaks we keep an error log — what failed, on which page, your account id if you were signed in, and for AI errors up to 200 characters of what you typed. Rate-limit warnings in that log include the IP address.

• To run the service — signing you in, saving and sharing trips, and group-trip chat.
• To keep it running and affordable — rate limits stop any one visitor from exhausting our AI or upstream quotas, and error logs let us fix what breaks.
• To improve it — analytics show which features help and where people get stuck.

We do not sell personal data, and we do not use it for advertising.

Emails we send. A code to verify your email address when you sign up, and a link to reset your password if you ask for one. A “your trip is ready” email the first time you save a trip. If a saved trip has a departure date, a booking checklist 14 days before and a weather-and-packing note 2 days before. A season reminder you set on a guide — one email, in the month before the month you chose. If you watch fares on a saved trip, an email when a watched fare drops. We do not send marketing email without your consent.

These providers handle data on our behalf, only to do the job listed. Several are outside India, so your data may be processed abroad.

• Supabase

  Our database and sign-in system, including the verification and password-reset emails. Hosted in Supabase’s Singapore region.

• Vercel

  Hosts the website and runs our server code (USA).

• PostHog

  Product analytics and session recordings (USA), sent through our own domain. See “Analytics” above.

• Google Analytics

  Traffic reporting — which pages are visited and from where — when enabled on the live site.

• Upstash

  Redis used for rate limiting (short-lived counters keyed by IP address) and for caching AI answers (keyed by the text that was typed, not by who typed it).

• Resend

  Sends our emails. Receives your email address and the email’s content.

• DeepSeek

  The AI model behind typing a trip in a sentence, editing a plan with a sentence, Explore search, day notes and place tips. Receives the text you type and the names of the places and activities in your plan — not your name, email or account. DeepSeek is based in China.

• Anthropic

  A backup AI model (Claude) used when DeepSeek is unavailable for typed trips, sentence edits and place tips. Receives the same text (USA).

• Travelpayouts

  Live flight fares. Receives the two airports and the travel date — nothing about you.

• Open-Meteo

  Weather forecasts. Receives a destination’s coordinates — nothing about you.

• OpenStreetMap services

  Nominatim and Photon (place lookups) and OSRM (road distances). Called from our servers with place names or coordinates only.

• Wikipedia / Wikimedia

  Place descriptions and photos. Photos load straight from Wikimedia’s servers, so your browser connects to them as it would to any website.

• OpenFreeMap

  Map tiles, loaded by your browser when a map is on screen.

Plans link out to Booking.com, Klook and Aviasales with our affiliate tag, so we may earn a commission if you book — at no extra cost to you. Links to IRCTC and Google Flights carry no tag.

A link includes what that site needs to run your search — the place, dates and number of travellers. Once you click through, that site’s own privacy policy applies, and it may set its own cookies.

• Account — until you delete it.
• Trips — until you delete the trip or your account. We don’t delete trips automatically after you travel.
• Group-trip messages and memberships, season reminders, fare watches, early-access reservation — until you remove them or delete your account.
• Error logs — deleted after 30 days. Deleting your account also removes your account id from them straight away.
• Rate-limit counters — expire within about two days.
• Cached AI answers — up to 30 days, keyed by the text typed and not linked to you.
• Analytics — kept by PostHog (and Google Analytics, where used) under the retention limits of our account with them. Deleting your Tourisma account does not delete them automatically; email us and we will.
• Place details cache — OpenStreetMap and Wikipedia data about places, refreshed every 30 days. No personal data.

• Download your data — Account → Export gives you a file with your account, trips, group-trip messages and memberships, and season reminders.
• Delete your account — Account → Delete removes your account and, with it, your trips, group-trip memberships and messages, season reminders, fare watches and early-access reservation.
• Make a shared trip private — on Saved trips, switch a trip’s link back to private at any time.
• Your other DPDP rights — to a summary of what we hold, to correct it, to withdraw consent, to nominate someone to act for you, and to complain to the Data Protection Board of India.

For anything you can’t do from your account, email support@tourisma.app with the subject “Data Request”. We will respond within 72 hours.

• Signing in keeps your session in your browser’s local storage.
• PostHog keeps its random visitor identifier in a cookie and local storage on our domain.
• Google Analytics, where used, sets its own analytics cookies.

We set no advertising cookies. Booking sites you click through to may set their own.

Tourisma is not meant for anyone under 18, and we don’t knowingly collect their data. If you think a minor has made an account, tell us and we will delete it.

When the way we handle data changes, we update this page and the date at the top. For material changes we email registered users at least 7 days before they take effect.

Questions, requests or complaints: support@tourisma.app. The same address reaches our Grievance Officer under the DPDP Act; we acknowledge every request within 48 hours.