What this privacy policy covers

This privacy policy covers the whole of Prize Winners UK: the guides, the worked sums, the pages that read a promotion’s small print and price it, and the housekeeping pages around them. It says what the site collects when you read, why it keeps that much and no more, and what you can ask for under UK GDPR. It does not cover the operators the guides discuss, because each of them runs its own policy on its own domain; the handover is described in the section on outbound links.

There are no accounts to open, no newsletter to join and no comment forms on the guide pages, so the site never asks for a name, an email address or a postal address in the first place. What it holds is the residue of any web request: the standard line a server writes when a browser asks for a page, and nothing volunteered on top of it.

Why anything is kept at all

Server lines exist for two dull reasons. Security comes first: a log is how an unusual flood of requests, a malformed address or a scanner probing the pages gets noticed, and the standard line carries just enough detail to tell a curious reader apart from a script. Aggregate counts come second: knowing that one guide drew far more readers than another in a given week is a total, read as a number on its own, and it shapes which guides get written next. Neither reason needs a profile of you, so neither is built.

Cookies, in plain terms

One anonymous analytics cookie runs on the site. It holds a random string that lets a week’s visits be counted without counting any person: no name, no email address, nothing that profiles the reader. There are no advertising cookies, no cross-site trackers and no fingerprinting, because a page that models terms has no use for them and passes nothing on to advertising networks.

Clear the cookie in your browser and the pages read exactly the same. The counts lose a little accuracy; the reader loses nothing.

Outbound links and the redirect

Some links to operators are cloaked: the address points at this site first, then forwards your browser on to the operator’s page. Following one passes through the site’s redirect, and that redirect logs nothing about the reader beyond the standard server line, the same short record any page request leaves. The counts drawn from such records are totals, not trails.

Once your browser lands there, the operator’s own privacy policy takes over. What you read, deposit or win from that point is never visible to this site. The cloaking exists so the ledger can keep honest totals of interest, not so it can follow anyone.

How long records are kept

Server lines are short-lived. They are kept for a few weeks while they remain useful for security, then rotated off the disk, and the aggregate counts survive only as bare totals with no personal detail attached. A question sent to the desk through the contact page is kept until it is answered, then deleted with the thread. Nothing is archived into a lasting profile, because there is no profile to archive.

Your rights under UK GDPR

UK GDPR gives you rights over personal data even when the holder is a small comparison site. You can ask for access, meaning a copy of whatever relates to you; you can ask for deletion, meaning it is erased rather than kept in a shadow copy; and you can object to processing or ask that it be restricted. Because the site holds so little, most requests are answered quickly and in full.

Use the contact page to make a request. If the answer disappoints, you can complain to the Information Commissioner’s Office, the ICO, the British regulator for data protection, whose own site carries the complaint route. A complaint there costs nothing and needs no solicitor.

Changes to this policy

The policy changes when the site’s plumbing changes, and the modified date on the page moves with it; this version is dated 20 November 2026. A clarification of wording happens quietly. Any change to what is collected, how long it is kept or who it is shared with would be stated plainly on this page rather than buried in a paragraph like this one. Reading the page after a change means the changed version is the one that applies, so the date is the thing to glance at first.