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].
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 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.
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.
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).
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.
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.
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.
We do not sell personal data and we do not use it for third-party advertising.
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.
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.
We use encrypted connections, access controls and keep API keys secret. No system is perfectly secure, so please protect your own keys and passwords.
The Service is for businesses and adults. We do not knowingly collect data from children under 16.
We post changes on this page and update the date at the top. For material changes affecting account holders, we also email them.