Cette page est disponible en anglais.
Privacy
There are no accounts on this site. Google Analytics sets two cookies of its own to count visits, described under Analytics below, and we set none. Browsing is not tied to a name, an email address or a profile, because none of those exist. The one time you give us either is when you write to us, and what happens to a message is set out below.
Who runs this site
This site is run by Ticket Hall, an independent online guide to tours, tickets and activities. It is responsible, as the controller, for the handling of information described on this page. To ask about any of it, or to make a request about information we hold, use the contact page.
What stays on your device
Your browser's own storage keeps the choices the interface offers, so the next page looks the way the last one did: the light or dark theme; the currency prices are shown in; the answer to the location lookup described below, for a day; whether you have dismissed the offer to add the site to your home screen, and whether you added it; and, for the length of one visit, how many pages you have opened, whether you closed the home page's note about the city you are in, the loading line you last saw and, if you came from one of our own guide sites, the label of the link you followed. None of it names you, and all of it is yours to clear.
If you check availability for an experience, this browser keeps your last choices (the experience, date, travellers, option, time and language) for up to 30 days so you can continue later; it never leaves your device. Closing the prompt that offers to continue deletes it, and so does starting over on the experience's own page.
If you use the trip planner, this browser keeps the conversation and your latest plan for up to 14 days, so you can come back to the list after opening one of its experiences. It stays on your device; "Start a new plan" in the planner deletes it. What you type into the planner is sent to our server and on to an AI service that writes the reply; we keep a count of what was asked (the city, the number of days and the travel styles), never what you wrote and never your address.
Two of those leave the browser, because they have to for the feature to work: the currency is sent to our server with each live price lookup so the price comes back in it, and it is added to the link to the booking partner when you click through, though the partner's page does not use it and shows prices in its own currency until you change it there; and a guide-site link label is sent to our own server with the click it led to, as described below. The rest is never sent anywhere.
What the server records
The web server keeps the ordinary access log every web server keeps. For each request it notes the address it came from, the time, the method and the path asked for including any search terms in it, the response status and size, how long it took, the page that linked to it where the browser says, and the browser's own description of itself. The log is kept in the system journal and expires after 30 days. It is used to keep the site up and to see it being attacked; nothing else is done with it.
When you click through to book, we record the time, the page you left from and the campaign label attached to that link. That tells us which pages lead to bookings. Your address is not part of that record.
When you open an experience from a link on one of our own guide sites, we record the time, the page you landed on, the label that link carried and the name of the site you came from, but not the address of the page you were reading there. Your browser keeps that label for the rest of the visit, and if you then click through to book, it is added to the record of that click. Your address is not part of either record.
Messages you send us
The form on the contact page is the one place the site asks for anything about you. When you send it, our server writes down the time, the language of the page you wrote from, your name if you gave one, your email address and your message. It is kept on our own server: it is not sent on by email and it is not passed to anyone else. We use it to read your message and to reply to you, and for nothing else.
The network address your message came from is not stored with it. The server reads that address only to limit how many messages one connection can send in a quarter of an hour, holds it in memory for that quarter of an hour without ever writing it down, and then discards it; the access log above notes the request itself, as it does every request.
Messages are deleted automatically twelve months after they arrive. To have yours deleted sooner, or to ask what we hold about you, write to us through the same form from the same email address and say so.
Approximate location on the home page
After the home page has loaded, your browser asks our own server to look your address up against a database of address ranges, to suggest a currency and, if you are in one of the cities the site covers, to offer a link to it. The answer is a country and a rough area rather than a place, and your address is not stored as a result of it. The lookup happens on our own machine; your address is not sent to anyone for it.
IP geolocation data by DB-IP, used under the Creative Commons Attribution 4.0 licence
Analytics
Every page loads Google Analytics, a service of Google. It sets two cookies in your browser, named _ga and _ga_ followed by an identifier, which last up to two years, and it sends Google the pages you view, your approximate location, your device and browser type and how you arrived, so that we can see which pages are used. Google processes that data and may do so outside the European Economic Area; Google's own privacy policy governs what it does with it. We do not combine it with anything else we hold.
To avoid it, block cookies or the Google Analytics script in your browser or with a content blocker, or use Google's opt-out browser add-on. Nothing on the site stops working if you do.
What is loaded from elsewhere
The photographs originate from our booking partner's image service. Most are served from this site's own copy; where a page still requests one of those directly, your browser contacts that service and its own policies govern that request. The typefaces are served from this site, so reading a page asks nobody else for them. The one exception is Google Analytics, described above. No advertising script runs on any page.
Once you click through to book, you are on the booking partner's site and their privacy policy applies to everything that happens there, including the booking itself. It is worth reading before you pay.