Cookie policy
The briefest policy possible, with one exception: the transfer search widget loads without waiting for anyone and writes two cookies this site declares mandatory. Everything else still waits for your answer — no analytics or advertising loads before you allow a purpose — and you can accept them separately, reject them, or withdraw them later. What follows explains what the browser stores and how to check it yourself.
Own cookies
We install no session or identification cookies of our own, because there is no user account or shopping cart. Preferences — the language, the state of a panel or your answer to the banner — are stored in the browser's local storage, which never travels to the server: your answer is kept for 24 months and you can delete it from your browser settings. The two cookies that do appear on this domain from the start are not written by us: the transfer search widget's script sets them, and they are detailed separately.
Three purposes, approved separately
Usage measurement is split into two purposes approved individually in the banner: analytics, with Google Analytics, and the heat map, with Microsoft Clarity. A third joins them: link attribution, with Travelpayouts, which records clicks on flight and accommodation links so the booking you go on to make pays us a commission. You can accept all three, only one, or none; the "Configure" option opens the panel where they are ticked. Only that last purpose opens the ad signal, which otherwise stays denied, with or without consent. The transfer search widget is not one of these three purposes: it is neither approved nor rejected, and the next section explains why.
The transfer search widget, always present
350 of the site's 385 pages carry a Travelpayouts transfer search widget, and it always loads: before your answer, asking you for nothing, and with no way for the panel to switch it off. Its script writes two cookies measured on 19 October 2026, both secure and set only over a secure connection: _sp_id.a763, a visitor identifier that lasts 400 days, and _sp_ses.a763, the session, which renews every 30 minutes while you keep browsing. Both are session analytics from the widget's vendor, not ours, and this site declares them mandatory because the widget works with them from the moment it opens. They also go on the whole domain and not only on www, so they are shared with any subdomain of the site. As they are not a purpose of the panel, there is no box to untick: you can delete them whenever you like from your browser settings, and the pages still open normally.
Which cookies are installed once allowed
If you allow analytics, Google Analytics stores two cookies for this domain: _ga, which tells browsers apart, and _ga_<id>, which keeps the session, both expiring after two years. If you allow the heat map, Microsoft Clarity stores _clck, the visitor identifier, for a year, and _clsk, which joins the events of one session, for a day — whether or not analytics is also accepted. The third purpose, Travelpayouts, adds nothing to this list: its script writes no cookie into your browser at all, and were it ever to, that would be Travelpayouts changing its own script rather than this site installing one. None of these is created before you accept — the widget's two, which are there from the first load, are detailed in their own section — and all are first-party, with no identifier shared with any other site; the widget's cookies additionally go on the whole domain, shared with any subdomain, and not only on www.
The pages you have visited, kept on your own device
This site can be installed as an application, and it keeps the pages you have visited on your own device so they still open when you have no connection to the internet. What does this is a service worker — a script the browser runs in the background — and it only ever answers requests for this domain: it never stores or serves third-party content, so the transfer search's script, the Google Tag Manager container and the map's tiles stay out of it by construction, with or without your consent. It is technical, first-party storage, like the fonts: it identifies nobody, it never travels to the server, and it asks no permission because it measures nothing. Only what you have read is kept, not the whole site. If you would rather do without it, clear this site's data in your browser settings or uninstall the application; while it exists, the site behaves exactly the same whenever there is a network.
Third parties
There is no embedded advertising or social media. Fonts and styles are our own, served from the same domain. No measurement request leaves before your answer, with one exception: the browser does not even request the Google Tag Manager container. The only request that does go out without your permission is the transfer search widget's, which requests its script from tpwidg.com and its data from tpemb.com on every page that carries it. The other two are features you asked for and set no cookie — the map's tiles when it opens, and, only if you press "My location", the walking-route calculation. Only when you allow a purpose does the container load — with measurement denied by default — and request Google Analytics, Microsoft Clarity or Travelpayouts, whichever it is.
Withdraw consent whenever you like
The "Manage cookies" link in the footer reopens the same panel with your choice ticked. Unticking and saving deletes the revoked purpose's cookies immediately and reloads the page so the change applies from its very first load; you can revoke one purpose or any of them. Withdrawing is as valid as accepting: no reason is needed and you can accept again later. What you revoke are purposes; the transfer search widget's two cookies are not revoked from the panel, because they are not a purpose, and are deleted from your browser settings.
Check it yourself
Open the browser's developer tools, go to storage and inspect the list: you will see the transfer search widget's two cookies — they are there from the first load — alongside those of the purposes you accepted, and the latter disappear as soon as you withdraw them. You can also browse in a private window or block cookies outright: the site keeps working, because it depends on none of them to be read.
Frequently asked questions
Can I block this site's cookies? ＋
Yes, with no consequences for reading. There are no sessions and no mandatory personalisation, so blocking them does not stop you opening any page.
Which cookies does this site install? ＋
Two from your first visit, the transfer search widget's: _sp_id.a763, at 400 days, and _sp_ses.a763, a 30-minute session renewed while you browse. The rest appear only if you allow them: _ga and _ga_<id> (Google Analytics, two years) and _clck and _clsk (Microsoft Clarity, a year and a day), only in the purposes you tick.
Can I accept only one of the three purposes? ＋
Yes. The banner's "Configure" panel ticks analytics, the heat map and link attribution separately: accept only one and only what that purpose needs is installed — and unless it is analytics, not even cookies.
What happens if I withdraw consent? ＋
The revoked purpose's cookies are deleted and the page reloads; from that moment the site stops sending measurement data. You can do it whenever you like, as many times as you like.
Why a cookie policy, then? ＋
Because the rules require you to be informed of a presence exactly as much as of an absence, and because we would rather you checked than took our word for it.