Understand what this site records when you arrive from a search engine
Read this before you assume the site tracks you in the way many other sites do. If you land on this site by clicking a result on a search engine, a first-party visit beacon sends a small piece of information to an edge analytics endpoint on this same domain: the path of the page you opened, the type of event (such as a page view or a click on an outbound button), the name of the search engine you came from, and the text of any outbound button you click. This only fires for search-engine arrivals — browsing here directly or from a bookmark does not trigger it. The edge analytics endpoint also notes the country your request is reported from by the content delivery network that hosts these files; nothing more precise about your location is captured. All of this is used for one purpose only: counting page views and outbound button clicks. It is kept in the operator's own logs on this domain and is not passed to any outside analytics service, advertising network, or data broker.
Know what the cookie and session flag do, and what they don't
One first-party cookie is set only when you arrive from a search engine. It holds nothing but the name of that search engine, lasts up to one hour, and exists so that if you later click an outbound link, the click can be tied back to the search engine you originally came from. Alongside it, a session view flag is kept in your browser for the current visit only, so a single page view is counted once rather than multiple times as you browse. Neither of these is a persistent identifier, and no other browser storage is set. The pages themselves are self-contained: every file a page needs — including locally embedded fonts — comes from this domain, so nothing loads from an outside host while you view a page.
See what happens when you follow an outbound link, and where this page's authority ends
Outbound links to third-party sites, such as skip hire partners, first pass through a first-party outbound redirect on this domain before sending you onward. That redirect step is how a click gets attributed to the search engine you arrived from, using the one-hour cookie described above. Once you land on the partner site, your browser talks to that site directly — this site does not share any stored visitor data with the partner, and it has no control over what the partner site does with your request or what records it keeps. That is a separate destination with its own practices, not something this page can describe.
This site has no forms, no third-party analytics, no external subresources loading from other domains, and no contact channels. It collects no names, e-mail addresses, account identifiers, or payment details, and it runs no login or registration system. The content delivery network that serves these static files processes the technical details of each request as part of hosting the site, but that is separate from the counting described above. Because there is no form and no contact channel on this site, there is no place here to submit personal data — treat any linked destination as its own site with its own separate handling of whatever you enter there.