Cookie policy

What this site places in your browser

At the time this page was last updated, TransferSelect itself does not set:

• analytics cookies;
• advertising cookies;
• preference or personalisation cookies;
• identifiers in local storage or session storage.

The site also uses no indexed databases, no service workers and no advertising pixels. There is no cookie banner because the current implementation does not intentionally place non-essential identifiers in your browser. That is a description of what the site does today rather than a general statement about when consent is or is not required.

Affiliate links

Affiliate links here are ordinary links. We do not set a cookie before you navigate, and no code runs in your browser between your click and your arrival at the provider. The referral is carried by parameters in the link's address, not by anything stored on your device.

Once you arrive at Viator or another external provider, that website may use its own cookies or storage under its own policies. We are not going to describe which ones, because that is theirs to state and ours to stay out of. See affiliate disclosure.

The external image

One route page shows a provider photograph served from an external host, media-cdn.tripadvisor.com. If you scroll far enough for the image to load, your browser makes a request to that host.

A request is not in itself a cookie. What matters here is that any cookie or storage behaviour on the part of that external host is governed by that host and is not controlled by us. The privacy policy describes what a request of this kind exposes.

Controlling browser storage

Your browser settings let you block or clear cookies and site data, including for the external hosts described above, and most browsers can also block third-party requests entirely. Because this site places nothing, blocking storage for TransferSelect will not change how it behaves.

If this changes

If TransferSelect later adopts anything that uses cookies or browser storage, this page will be updated to describe it, and any user controls needed at that point should be put in place then rather than retrofitted afterwards.