Privacy Policy

We use the data we collect for three narrow purposes. First, to operate the site: serving pages, remembering whether a reader has accepted the cookie banner, logging bot traffic for security purposes. Second, to understand what readers find useful: aggregated page-view counts and referrer breakdowns, with IP addresses anonymised before the record is written. Third, to attribute referrals to Livescore Bet: when a reader clicks through to the operator from one of our pages, a short-lived identifier is passed so the commission is credited to us — the identifier is destroyed within 30 days and is never sold on to third parties. We do not run profiling of individual readers, we do not send marketing emails, and we do not build advertising audiences for resale.

We do not re-use the data for any other purpose. The analytics data is examined in aggregate — top pages, top referrers, mobile share — and never drilled down to an individual visitor. The correspondence data never leaves the editorial inbox; replies go only to the address that wrote in, and the thread is archived after the enquiry is closed.

When this policy changes, the date at the top of the page changes with it, and a short note is added at the bottom describing what moved. Material changes — adding a new processor, extending retention periods, introducing new tracking — are flagged in the site-wide banner for 30 days from the day they take effect. We do not email readers when the policy changes, because we do not hold an email list for marketing. Readers who want to be informed of changes can subscribe to the RSS feed, which carries a line for every policy revision.

History of material changes is kept for five years from the date of effect — readers who want to see how the policy evolved can request the archive by email. We treat the policy as a public document, not a sealed contract, and will explain any clause on request.

Three categories, and only these. Technical data: IP address (anonymised to the /24 subnet before storage), browser user-agent, referrer URL, and the UK region derived from the IP. Behavioural data: pages viewed on this site and the order in which they were viewed, time spent on each, whether the reader clicked a link to Livescore Bet. Correspondence data: if a reader emails [email protected], the email address and the body of the message are held with that thread. We do not collect names, dates of birth, payment details, or any other category of personal data; nothing on this site asks a reader to register.

The retention periods are: anonymised technical logs for 90 days, aggregated analytics for 24 months without any identifier, correspondence for 36 months from the last message in a thread. Shorter than that we cannot run the site; longer than that we have no business holding the data, so it is deleted automatically by the processor's own lifecycle rules.

Three third-party processors handle data on our behalf. Cloudflare routes traffic and provides bot protection — its logs record the IP and user-agent of every request and are retained for 30 days under Cloudflare's own privacy notice. A self-hosted Plausible instance records aggregated page analytics without cookies and without IP storage. The Livescore Bet affiliate programme receives the click identifier described above when a reader follows a CTA on our pages — nothing else is shared with them. We do not use Google Analytics, Meta Pixel, TikTok Pixel or any ad-tech beacon. The current list of processors is reviewed every six months; any change is logged in the "changes" section above.

Data-subject requests — access, erasure, portability — are routed to the editorial inbox and answered inside one calendar month, as the UK GDPR requires. For readers inside the European Economic Area, the same rights apply and the same timeline is observed; we do not operate a tiered policy by region.