Cookies

The short version

A cookie is a small file that a site hands to a browser and reads back on a later visit. This site never makes that request. Nothing is stored, so nothing needs consent, and a banner asking for permission to do nothing would be theatre.

Why there is nothing to consent to

Consent requirements exist because most sites store information on a visitor's device or allow another company to do so. Neither happens here. There is no analytics platform, no advertising network, no social media widget, no embedded video and no font service. Every file needed to display a page comes from this domain.

Local storage and session storage

These are the other common ways a site keeps information in a browser, and neither is used. The travel checklist ticks boxes within the page and deliberately saves nothing, which is why reloading that page clears it. That is a design decision rather than an oversight: a list of that kind is not something worth leaving on a shared device.

What the browser does on its own

Browsers cache files such as the stylesheet so that pages load faster on a second visit. That is standard browser behaviour, controlled by the browser rather than by this site, and clearing the cache removes it. It contains no information about a reader.

If that changes

It is not expected to. Should anything ever be stored in a browser, this page would say what it is, why it exists and how long it lasts, before it was introduced. The wider position is set out on the privacy page.