Privacy Policy
This policy describes what personal information TravelMindsAI ("we", "us") collects when you use our website, API, and related services, why we collect it, how we share it, and the choices you have. We aim to keep this short, plain, and accurate.
1. What we collect
- Account information: name, email, password hash, organisation name (if provided), billing country, and the plan you picked when you signed up.
- Sign-in with Google: when you connect an AI assistant (for example Claude or ChatGPT) to our MCP connector at mcp.travelminds.ai, you sign in with Google. We ask Google only for your email address and basic profile (the openid, email and profile permissions). We save your email address and name in your account. Our sign-in server also keeps the access and refresh tokens Google issues, so you stay signed in. If no account exists for that email, signing in creates a free account automatically, and we record the IP address it was created from. Website login uses email and password only.
- API marketplaces: if you use our API through a marketplace that resells it, we receive the marketplace's identifier for you, not your name or email.
- Billing information: when you pay, the payment provider sends us messages about your payment and subscription, and we store each message in full. These can include your name, email, phone number, billing address, tax ID, the amount, and card details such as the card type and last four digits. Full card numbers never reach our servers; they are handled by the payment provider.
- API usage: request timestamps, endpoint paths, response codes, byte counts, response times, the API key used, and rate-limit counters. Apart from what this page lists, we do not store the content of your API requests.
- Concierge questions: the trip planner (concierge) and its public demo are not offered at present, so we take no question text now. Question text that the earlier public demo stored (the first 400 characters of each question, a one-way hash of the IP address, the time and the result) is kept as described in section 5.
- IP address and browser details: when you log in, we store your browser's user agent and the network address of the request with your login session, to keep you signed in and to spot misuse. For the sign-up, login, password reset and newsletter forms (and, before they were removed, the public demo and the partner form), we store a one-way hash of your IP address, not the address itself, to apply per-address limits. Our server logs record each request's path and connecting address.
- Newsletter and partner forms: if you subscribe to our newsletter, we store your email, the page you subscribed from and any campaign tags in the link. Partner inquiries sent through the earlier partner form are stored with the name, email, company and message entered.
- Site analytics: our pages load an analytics script, but it is not switched on, so it sends nothing. We do not run third-party advertising trackers.
- Communications: emails you send to us and any support tickets you open.
2. Why we collect it
- To provide and operate the Services and your account.
- To bill you, calculate taxes, and detect fraud.
- To enforce rate limits, terms, and acceptable-use rules.
- To respond to support requests.
- To send account email (email confirmation, password reset, and a one-time getting-started email the day after you confirm your email) and, if you subscribe and confirm, our newsletter.
- To comply with our legal obligations.
3. Payment processing
Paid plans are started by email for now. When card payment opens, we will use two payment providers, chosen by the billing country on your account: Razorpay for India and our online reseller Paddle.com for everyone else.
For Paddle orders, Paddle will be the Merchant of Record, and independently responsible for processing your payment, calculating and remitting taxes, and handling refunds. Your payment details are submitted directly to Paddle and are governed by Paddle's Checkout Buyer Terms and Privacy Notice. For Razorpay payments, your payment details are submitted directly to Razorpay and are governed by Razorpay's Privacy Policy.
When you start a payment, we send the provider your email address and our account and plan IDs. The provider then sends us messages about your payment and subscription, which we store as described in section 1. We do not receive your full card number.
4. Sub-processors and infrastructure
Our API and database run on our own server, which takes outside traffic only through a Cloudflare Tunnel. The vendors we rely on:
- Website hosting and network — Cloudflare serves this website and carries all traffic to our API and MCP connector, so it processes your IP address and request details.
- Sign-in — Google, when you sign in to the MCP connector, as described in section 1.
- AI model: the trip planner (concierge) is not offered at present, so we send no question to an AI model. When the trip planner is switched on, it sends your question, and the travel data it looks up, to an AI model to write the answer: Anthropic's Claude through Anthropic's API, or a model on our own server, in which case the question does not leave it.
- Email delivery — an email-sending service delivers our account email.
- Payment processing — Paddle and Razorpay, as described above.
- Public file services — some pages load code, fonts or map images from unpkg, Google Fonts and CARTO. These services see your IP address when your browser fetches the files.
The current list of sub-processors is public at /legal/sub-processors.
5. Data retention
Account and billing records are retained for as long as your account is active and for the period required by tax, accounting, and anti-fraud laws after closure.
API usage records, login session records, payment provider messages, copies of the emails we send, newsletter and partner-form entries, and the public-demo question text described in section 1 are kept until they are deleted. Server logs are capped in size, and the oldest entries are overwritten as new ones arrive.
6. International transfers
We are based in India, and our own server, including our database, is run by us. Some of our vendors process data in other jurisdictions, including the European Economic Area, the United Kingdom, and the United States. Cloudflare runs a worldwide network, and Google processes data in the United States; when the trip planner is switched on with Anthropic's model, Anthropic does too.
7. Your rights
Depending on where you live, you may have rights to:
- Access the personal data we hold about you;
- Correct inaccurate data;
- Delete your account and associated personal data;
- Object to or restrict certain processing;
- Receive a portable copy of your data;
- Withdraw consent for marketing communications at any time.
To exercise these rights, write to [email protected]. There is no self-service button to delete your account or download your data. You may also lodge a complaint with your local data-protection authority.
8. Security
We protect personal data with encryption in transit (HTTPS), passwords and API keys stored only as Argon2id hashes, and database access for the data endpoints through a role that cannot bypass row-level security. No system is perfectly secure.
9. Children
The Services are sold to businesses and developers. Sign-up does not ask for anyone's age.
10. Cookies
Our own website and API code does not set cookies, and our analytics script is switched off. When you sign in to the account dashboard, your sign-in tokens and account details are kept in your browser's local storage, not in cookies; signing out removes them. The site also keeps a few small settings there, such as whether you dismissed a notice, and the plan you chose before checkout. Checkout pages are run by Paddle or Razorpay under their own cookie rules. You can clear cookies and local storage through your browser settings.
11. Changes to this policy
We will update this page when our practices change. The "Last updated" date at the top reflects the current version.
12. Contact
Questions about this policy or how we handle your data: [email protected].