TourScanner
API DocsMCPPlansGuides

Privacy Policy

Last updated: November 11, 2026

This policy explains how tourscanner ("we", "us") handles personal data when you use tourscanner.ai, the Partner API and the MCP server. It applies to visitors, account holders, API partners and the travellers whose bookings pass through the API. Contact for anything in this policy: [email protected].

1. Our role

  • Website, accounts and API access: we are the controller of the data described below.
  • Bookings: we process traveller details to place and manage the booking with the supplier. The supplier handles that data for delivering the activity under its own policy.
  • Partners: a partner that sends us traveller data is responsible for having a legal basis to do so and for telling its customers about it.

2. What we collect, why, and on what basis

Account and sign-in

Email address and sign-in data. You can sign in with an emailed magic link or with Google. Used to run your account and API keys. Basis: contract.

API and MCP usage

API key identifier, requested endpoint, timestamp, IP address, response status and errors. Query strings are not logged on the MCP endpoint, because a key can be passed there. Used for security, rate limiting, debugging and billing. Basis: legitimate interest in running a secure service, and contract.

Bookings

Traveller name, email address, phone number, party details, the activity, date and time, and any answers the supplier asks for. Used to hold, confirm, amend or cancel the booking and to send vouchers. Basis: contract.

Payments

Card details are entered on a Stripe page and go to Stripe. We receive the payment status, amount, currency and a reference. We do not store full card numbers. Basis: contract and legal obligation (accounting).

AI agent and chat

Messages you send to our AI agent, the tool calls it makes and its replies. If you share a location, we resolve it to the nearest city and round it to about 1 km before it is logged. Used to answer you, to debug and to improve the agent. Basis: legitimate interest, or consent where the browser asks for it.

Assistant connector (for example Claude)

If you connect TourScanner to an assistant, you sign in with your TourScanner account (emailed link or Google). The assistant then calls our MCP server for you. We receive your account id and email, and for each call the tool, what the assistant sent to it (search words, place or activity ids), a shortened copy of the result, the time, the IP address and whether it worked. We do not receive your chat. Used to run the service, to keep it secure, to enforce fair-use limits and to debug. Basis: contract and legitimate interest. The assistant itself is run by its provider under that provider's own privacy policy. See the guide TourScanner for Claude for how to connect and disconnect.

Website analytics

Pages viewed, clicks, device and browser data, and session recordings and heatmaps. Used to understand and improve the site. Basis: legitimate interest, or consent where the law requires it.

3. Who receives data

  • Suppliers of the activities you book, so they can deliver them.
  • Stripe, for payments.
  • Infrastructure: Railway (hosting), Supabase (database and sign-in) and Cloudflare (network protection). If you choose "Continue with Google", Google also receives the sign-in request.
  • AI model providers used by our agent: Google, OpenAI and Anthropic. Only the content of the AI conversation is sent to them.
  • Analytics: Mixpanel, Microsoft Clarity, Umami and Buzzwatch.
  • Operations: messaging and email tools we use to alert our team about a failed or stuck booking. These alerts can include a booking reference.
  • Authorities and advisers where the law requires it, and a buyer if we ever sell the business.

We do not sell personal data and we do not use it for third-party advertising.

4. International transfers

Some of these providers are based outside the European Economic Area, including in the United States. Where data leaves the EEA, we rely on an adequacy decision or on standard contractual clauses.

5. Retention

  • Account data: while your account is active, then deleted or anonymised on request or after it closes, except what we must keep.
  • Booking and payment records: as long as tax, accounting and dispute rules require.
  • Logs and AI conversations: only as long as needed for security, debugging and improvement, then deleted or aggregated.

6. Cookies and similar technologies

  • Essential: a sign-in session, and your light or dark mode choice in local storage.
  • Analytics: set by the analytics tools in section 3. You can block them in your browser or with a content blocker, and the site keeps working.

7. Your rights

Under the GDPR and similar laws you can ask to access, correct, delete or export your data, restrict or object to some processing, and withdraw consent at any time. Email [email protected] and we reply within one month. You can also complain to your local data protection authority. For a booking, we may also need to ask the supplier to act on your request.

8. Security

We use encrypted connections, access controls and keep API keys secret. No system is perfectly secure, so please protect your own keys and passwords.

9. Children

The Service is for businesses and adults. We do not knowingly collect data from children under 16.

10. Changes

We post changes on this page and update the date at the top. For material changes affecting account holders, we also email them.

TourScanner

The tours & activities API. 10 years of experience.

Product
API DocsChangelogStatusMCPPlans
Company
AboutGuidesFAQtourscanner.comFeatured onPrivacyTerms
© 2026 tourscanner. All rights reserved.