Privacy Policy — Gambajack

What we collect

Gambajack.co.uk is a static informational site. There is no reader account, no comment box that stores an email address, and no purchase flow. When a page loads the server records the standard access log: IP address, request path, timestamp, user agent, referrer. If a reader emails the editorial address we keep that email until the exchange is finished, plus a short retention window in case of follow-up. Analytics is served through a first-party endpoint that stores an anonymous session identifier and the page path — no third-party cookies are set for tracking. See the Cookie Policy for the full list of technical cookies and how to switch them off. Under the UK GDPR, the lawful basis for the access log is legitimate interest in running a functioning website (Article 6(1)(f)); the lawful basis for email correspondence is the necessity of answering the reader's own question (Article 6(1)(b)). We do not process special-category data and we do not ask readers to submit any.

How we use

The access log is used for two purposes only: debugging (finding pages that error out or load slowly) and detecting abuse (crawlers hammering the site, credential-stuffing attempts against the fake wp-login stub). We do not build a reader profile, we do not target advertising, and we do not sell traffic to third-party ad networks. Analytics data is aggregated to page level — how many visitors read a review, how long they stayed, which section they scrolled to — and never joined with an email or an IP. Email correspondence is used to answer the question and, where relevant, to publish a correction on the affected page. If a reader asks us to remove a message from the archive after the exchange has closed, we do so on request within one working week; nothing on our side depends on holding old email threads indefinitely. Aggregated reading numbers are published in a public transparency note once a quarter.

Changes

The policy on this page is versioned. Any change — a new analytics provider, a new retention period, a new legal ground for processing — is added with a date at the bottom of the page and a short note describing what moved. Material changes (anything that expands what we collect or how long we keep it) are also flagged at the top of the page for thirty days after they go live so returning readers see them without hunting. If you cannot find the change log or a particular version you were reading, email the editorial address and we will send you the archived text. Previous versions of the policy are kept in a signed archive for at least three years so a reader can check under what terms they were reading at a given point. Where a change is required by a regulator or a court order, the change note names the source so readers can follow the reasoning back to its origin.

Third parties

The site is hosted on Cloudflare Pages, so the edge network sees every request; Cloudflare's own privacy notice applies to that layer. Outbound links to the Gambajack operator handoff readers to a separate legal entity — once you cross that link you are on the operator's site and its privacy policy governs what happens next. We do not embed Facebook pixels, Google Ads conversion tags, TikTok pixels or any advertising trackers on our pages. The only external assets loaded are web fonts served from the same domain, so no third-party font provider sees your IP by visiting our pages. Search engines that crawl the site (Google, Bing, DuckDuckGo, Yandex) see the same public pages any reader sees; the site is not gated behind a login and there is no separate content served to crawlers. To exercise a UK GDPR right of access, rectification or erasure against gambajack.co.uk, email the editorial address with the word Data in the subject line.