What this site sets
Three cookies, all first-party, none of them shared with anybody:
- PHPSESSID — the session. It is what holds a booking together across the checkout pages, and what My bookings recognises you by. It carries no data itself, only an identifier. Gone when you close the browser.
- tb_recent_searches — the last few searches you ran, so the search form can offer them back. It holds the search addresses and nothing else. Lasts a year.
- tb_saved_flights — the flights you starred, which is what saved flights lists. Written by this site’s own script in your browser rather than by the server, and sent back with every request so the pages can mark what you saved. Lasts a year.
All three are limited to this site, and the first two cannot be read by scripts at all. None of them is used for advertising.
What the analytics vendors set
Two scripts, and neither one loads unless you have allowed it. Until you answer the notice, nothing below runs and none of these cookies exists:
- Google Analytics — counts pages and visits.
- Yandex Metrika — counts the same things, and is configured here with Webvisor on, which records movement, scrolling, clicks and typing on the page and plays them back.
Those cookies belong to Google and Yandex, not to this site. What they are called, how long they last and what is done with them is set by those companies under their own policies.
Your answer, and changing it
You have not answered yet, so no analytics is running. The answer is kept in a cookie of its own, tb_cookie_consent, and in nothing else — so clearing this site’s cookies also clears the answer, and the notice comes back.
Turning off the rest
The three above are not covered by that answer, because the site stops working without them. Every browser can block or clear cookies for one site. Doing that to Trip Builder costs you the session — the checkout will not hold together, and My bookings and saved flights will be empty — but the rest works, and search, the place pages and the fare calendar need no cookie at all.