This page explains what happens on www.alanalake.co.uk itself, as distinct from any site a reader reaches by following an outbound link from it.
See What Visit Data Is Actually Collected
When a visitor arrives from a search engine, this site records a small set of details: the page path, the type of event, the name of the referring search engine, and the text of any outbound button that gets clicked. This happens only for search-engine arrivals — visits from other sources are not logged in this way. The data is stored in the operator's own logs on this domain and used only to count page views and outbound clicks. It is not used for anything beyond that traffic count.
Understand the Cookie and the Session Flag
One first-party cookie is set, but only when a visit arrives from a search engine. It holds nothing but the name of that search engine, lasts up to one hour, and exists so that a later click on an outbound link can be matched to the search engine that brought the visitor here. Separately, a session flag is kept in the browser for the current visit only, so that a single page view is counted once rather than multiple times. Neither of these is a persistent identifier, and no other browser storage is set.
Know What Location and Hosting Data Is Involved
The content delivery network that serves this site's static files reports the country a request came from, and nothing more precise. That network processes the technical data of every request as the hosting provider. The site itself consists of self-contained pages with locally embedded fonts, so nothing is pulled in from an outside host while a page is displayed.
See How Outbound Links Actually Work
Outbound links on this site go first to a path on this domain, which then redirects to the destination. This site does not pass any stored visitor data to the destination as part of that redirect. Once the redirect completes, the destination site receives the request directly from the visitor's browser and keeps its own separate record of it. This site has no influence over what that destination does with the visit, since it is a different site entirely.
Recognise What This Site Does Not Do
There are no forms on this site, so no name, email address, account detail, or payment information is ever typed in here. There is no third-party analytics service reading visit data, and no external subresources are loaded from other domains. There are also no contact channels on this site. Taken together with the mechanisms above, this is why the site asks for no consent banner, no account, and no personal detail: it simply has no channel through which to collect one. A table below summarises what is present against what is confirmed absent.
| Present on this site | Confirmed absent |
|---|---|
| First-party visit beacon, triggered on search-engine arrivals | No forms of any kind |
| Edge analytics endpoint feeding the operator's own logs | No third-party analytics |
| Session view flag, cleared at the end of the session | No external subresources |
| First-party outbound redirect path before third-party sites | No contact channels |
Because there is no contact channel here, readers should not attempt to submit personal data through this site expecting it to be received or handled. Any information a reader chooses to share happens only after leaving this site, on the separate destination reached through an outbound link, and that destination's own handling of the request is outside what this page can describe.