Cookies and your consent
The briefest policy possible, with one exception: the transfer search 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, refuse them, or withdraw them later. What follows explains what the browser stores and how to check it yourself.
Cookies this site sets itself
This site installs no session or identification cookies, because it has no user account or shopping cart. Preferences — the language, the state of a panel or your answer to the banner — go into the browser's local storage, which never travels to the server: there 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's script sets them, and they are detailed separately.
Three purposes, each approved separately
Two purposes make up usage measurement, and the banner approves each of them individually: analytics, with Google Analytics, and the heat map, with Microsoft Clarity. A third sits beside them — link attribution, with Travelpayouts, which records clicks on flight and accommodation links so that a booking you go on to make pays us a commission. All three, only one or none may be accepted; the "Configure" option opens the panel where they are ticked. The advertising signal opens for that last purpose alone, and is denied otherwise, with or without consent. The transfer search is not one of these three purposes: it is neither approved nor refused, and the next section explains why.
The transfer search, always present
350 of the site's 385 pages carry a Travelpayouts transfer search, and it always loads: before your answer, asking nothing of you, and with the panel unable to switch it off. Its script writes two cookies, measured on 19 October 2026, both secure and sent only over a secure connection: _sp_id.a763, with a visitor identifier that lasts 400 days, and _sp_ses.a763, with the session, which renews every 30 minutes while you keep browsing. Both are the search provider's session analytics, not ours, and this site declares them mandatory because the search works with them from the moment it opens. They also apply to the whole domain and not only to 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 keep opening normally.
Which cookies are installed after you allow them
Allowing analytics makes Google Analytics store two cookies for this domain: _ga, which tells browsers apart, and _ga_<id>, which keeps the session, both expiring after two years. Allow the heat map and 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 Travelpayouts purpose adds nothing to this inventory: its script writes no cookie into your browser, and were it to begin doing so, that would be its own script changing rather than anything this site installed. None of these is created before you accept — the search'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 search's two also apply to the whole domain, with any subdomain, and not only to www.
Pages you have visited are kept on your own device
This site may be installed as an application, and once installed it keeps the pages you have visited on your own device, so that they continue to open when you have no internet connection. The mechanism is a service worker — a script the browser holds in the background — and it answers only requests for this domain: it never stores or serves third-party content, so the transfer search script, the Google Tag Manager container and the map's tiles are excluded by construction, with or without your consent. This is technical, first-party storage, in the same class as the fonts: it identifies nobody, it never travels to the server, and it requests no permission because it measures nothing. What it keeps is only what you have read, not the whole site. Should you prefer not to have it, clear this site's data in your browser settings or uninstall the application; for as long as it is there, the site behaves in exactly the same way whenever a network is available.
Third parties, and what reaches them
No advertising or social media is embedded here. Our fonts and styles are our own, served from the same domain. Before your answer, no measurement request leaves for third parties: the browser does not even request the Google Tag Manager container. The one request that does leave without your permission is the transfer search's, which asks tpwidg.com for its script and tpemb.com for its data on every page that carries it. The other two are features you ask for and they set no cookie — the map's tiles when it opens, and, only if you press "My location", the walking-route calculation. It is only when you allow a purpose that the container loads — with measurement denied by default — and requests Google Analytics, Microsoft Clarity or Travelpayouts, whichever it is.
Taking your consent back whenever you like
The "Manage cookies" link in the footer reopens the same panel with your choice already ticked. Untick and save, and the revoked purpose's cookies are deleted immediately, with the page reloading so the change applies from its very first load; one purpose or any number of them may be revoked. Withdrawing counts as much as accepting: no reason is needed and you can accept again later. What you withdraw are purposes; the transfer search's two cookies are not withdrawn from the panel because they are not a purpose, and they are deleted from your browser settings.
Checking it for yourself
In the browser's developer tools, open storage and inspect the list: you will see the transfer search's two cookies — there from the first load — alongside those of the purposes you accepted, and the latter disappear as soon as you withdraw them. You may 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
May I block the cookies this site sets? ＋
Yes, with no consequences for reading. Sessions do not exist and there is no personalisation you cannot do without, so blocking them does not stop you opening any page.
What cookies does this site install? ＋
Two from your first visit, the transfer search's: _sp_id.a763, at 400 days, and _sp_ses.a763, a 30-minute session that renews while you browse. The others 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.
Is it possible to accept only one of the three purposes? ＋
Yes. Analytics, the heat map and link attribution are ticked separately in the banner's "Configure" panel: accept only one and only what that purpose needs is installed — and were it anything but analytics, not even cookies.
What happens if I take my consent back? ＋
The revoked purpose's cookies are deleted and the page reloads; from that moment the site stops sending measurement data. It may be done whenever you like, and as many times as you like.
So why have a cookie policy at all? ＋
Because the rules require you to be informed of an absence exactly as much as of a presence, and because we would rather you checked for yourself than took our word for it.