Cookie Policy

Cookies are small text files that sites store on a user's device to make the site work or to remember preferences. Some are strictly necessary for technical operation (technical cookies) and require no consent; others collect statistics, recognise who is visiting, or serve advertising, and require prior consent. The same applies to equivalent technologies that store or read information on your device, such as localStorage and sessionStorage, which this page describes alongside cookies.

We use Snitcher, a tool that works out which company or organisation you are visiting from, based on the IP address you visit from. We use it to understand which companies are interested in our services. Snitcher is provided by Snitcher B.V. (Netherlands), and the data it collects is stored primarily in the European Union (AWS, Frankfurt). A few of its technical sub-processors, used for error logging and content delivery, operate outside the EU under standard contractual clauses.

Our footer also shows a Snitcher partner badge, which is served from Snitcher's own systems rather than ours. Because your browser loads it directly, your IP address, your browser details and the address of the page you are viewing are visible to Snitcher whenever a page loads, whatever you chose in the banner. The badge itself is a picture and a link: it carries no identification script and does not switch on the tool described above. Loading the badge also runs Cloudflare's automated-traffic check inside that frame. It reads characteristics of your browser, sends them to Cloudflare, and sets a cf_clearance cookie on the snitcher.com domain that lasts one year. That cookie is partitioned, which means it is tied to your visit to this site and cannot be used to recognise you elsewhere.

With consent active, Snitcher collects the pages you visit, how long you stay, the page you arrived from, campaign parameters, and a set of technical details about your device and browser that together form a device fingerprint (described in the next paragraph), along with the IP address the visit comes from.

That fingerprint is a set of measurements that together tell one browser or device apart from another. Once the script has loaded, it reads how your browser draws a hidden test image, the make and model of your graphics hardware, and the number of processor cores and the memory your device reports. It reads your screen resolution, colour depth, pixel ratio and the maximum number of simultaneous touches your screen recognises. It reads the timezone set on your device, your browser language, and the plugins and fonts you have installed. It reads how many audio and video devices are attached: the number only, never their names, and with no access to your camera or microphone. It reads which methods of storing data your browser supports, whether an ad blocker is present, and your Do Not Track setting. Finally, it reads the identifying line your browser sends about itself and the platform it runs on, and signals suggesting that the browser is being driven by software rather than by a person. These values are combined into a single code, sent with the rest of the visit data, and held in the radar_sn_* entries listed above. That code is a device-level identifier. It does not by itself attach a name to anyone, and we do not combine it with any tool that would. Snitcher provides no setting that turns it off: we searched the code the tool ships and found none.

Snitcher also offers features that would make it possible to identify an individual person, most directly the automatic reading of what you type into form fields. That feature is switched off in our configuration, as are the automatic capture of clicks, of downloads and of browser errors. The device fingerprint described above is the part we cannot switch off, so the only control we have over it is consent itself: decline, or make no choice, and the script never loads, so no fingerprint is taken. If you consented and later withdraw, the script is no longer loaded, and what it stored is deleted and stays deleted. We use the tool to see which companies visit us, not to build profiles of named individuals. The tool is additionally capable of reading cookies set by other analytics and advertising platforms that may be present on a site: we use none of those platforms, so there are no such cookies on our site for it to read.

To understand how the site is used in aggregate, we use Vercel Web Analytics, a measurement solution that sets no cookies and no persistent identifiers and collects no identifying personal data. Because it sets no cookies, it requires no consent. Vercel Web Analytics uses a daily technical identifier, derived pseudonymously from IP address and user-agent, refreshed every day, which cannot recognise you across days or across sites.

From here you can check the choice you made about visitor identification and change it. Withdrawing consent is as easy as giving it: withdrawal takes effect immediately and deletes what the tool had stored on your device.

You can also block or delete cookies, including technical ones, through your browser settings. Note that disabling technical cookies may break some site features, such as the booking widget. Instructions are available in the support pages of the main browsers (Chrome, Firefox, Safari, Edge).

How we process personal data collected through the site, your rights as a data subject, and international data transfers are described in our Privacy Policy (/privacy).

If we introduce further analytics or profiling cookies in the future, this page will be updated and consent will be requested again before any such cookie is set.