This page explains what happens on a technical level when someone visits this site. It covers the mechanisms that were verified as part of the site's build, and it does not go beyond what that verification supports.
What A Visit Triggers
When a page loads, a first-party visit beacon can fire. This is a small signal sent to this domain, and it is what allows a page view to be counted. Alongside it, a session view flag is set in the browser for the current session only, so that a single page view is counted once rather than multiple times while the visitor stays on the site. The flag exists for the length of that session and is not designed to identify a person; it simply prevents duplicate counting.
These mechanisms are triggered by ordinary page loading and by clicking an outbound button. The path of the page, the type of event, the name of a referring search engine, and the text of a clicked outbound button are the kinds of details this counting mechanism is built to register. The stated purpose of this activity is traffic counting for this site's own use.
How Pages Are Built And Served
Every page on this site is self-contained: the fonts used in the design are embedded locally rather than pulled from an outside font service, and the page does not reach out to other domains to load the elements needed to display it. The whole site is a set of static files served through a content delivery network, which is standard infrastructure for distributing files quickly. That network necessarily handles the technical details of each request as part of serving the pages, in its role as the hosting layer.
How Outbound Links Work
Some links on this site point to third-party sites, such as operators or partners discussed on the page. These outbound links use a first-party redirect: clicking one first passes through a path on this domain before sending the browser onward to the destination. Once the browser leaves for that destination, the third-party site receives the request directly and is a separate environment with its own practices. This page describes only the redirect step that happens on this domain, not what any linked site subsequently does.
What Isn't Present
There are no forms anywhere on this site, so there is no field where a visitor is asked to type in a name, an email address, or any other personal detail. There is no third-party analytics tool embedded in the pages — the counting described above is limited to this domain. There are no external subresources loaded from other domains while a page displays. There are also no contact channels built into the site, such as an email link or a message form.
Together, these absences mean the site is not built to gather personal details through the page itself, and there is no mechanism here that asks a visitor to hand over identifying information in order to browse.
Why This Setup Needs No Consent Step
Because the visit beacon and session flag are limited to counting page views and outbound clicks, and because there are no forms, no third-party analytics, no external subresources, and no contact channels, this site does not present a cookie banner, a sign-up step, or an account system. There is nothing on the page asking a visitor to accept tracking beyond what is described above, and nothing asking for personal identification to read the content.
Keep This Page Separate From Linked Sites
This privacy page describes only the mechanisms built into www.96back.co.uk itself. It cannot speak for the destinations reached through outbound links, since those are independent sites that receive requests directly from a visitor's browser once the redirect completes. Anyone following a link off this domain is entering a different environment, and should treat any request for personal information there as a matter for that separate site, not for this one. Readers should avoid submitting personal data through any channel unless they have first checked what that specific destination does with it.