Retention
Server logs are kept for 30 days and then purged. Analytics data is kept for 14 months in aggregated form. Contact-form messages are kept for 12 months. If you request earlier deletion, we will action it within one working day; the request itself is kept as a record for 12 months.
You have the usual UK GDPR rights: access, rectification, erasure, restriction, portability and objection. Write to the editorial address with 'data request' in the subject line, and we will walk you through the identity-verification steps.
Where a request involves data held by a third-party processor (for example, Cloudflare log entries older than 30 days), we pass the request on with a reasonable identifier and keep you updated. Each processor publishes its own retention policy, and we link to those policies at the foot of this page so you can read them in full.
We audit retention quarterly. If a log, cookie or form submission is still on disk past its stated lifetime, the automated job that should have purged it is treated as a bug — reported, fixed, and documented in a short internal note. The next audit confirms the fix.
Third parties
Three third parties process data on our behalf. Cloudflare serves the site and acts as a reverse proxy; its logs are governed by Cloudflare's own privacy terms. Our analytics provider processes aggregated page-view data in the EU. Our email host processes contact-form messages.
We do not sell data to advertisers, data brokers or third-party affiliates. When you click an outbound link to the operator we pass only the referrer header that any browser would send — no further data is attached by this site.
A short list of processors used for operational reasons: a backup provider that holds encrypted site snapshots in the United Kingdom, a transactional-email provider for replies to the contact form, and the UK-based registrar that holds the domain record. None of these processors accesses reader data beyond what is strictly necessary to deliver the service they are contracted for.
If a new processor is added, the entry appears in this list and the change date goes at the foot of the page. If an existing processor is removed, data held by them is deleted or returned, as the UK GDPR requires.
How we use
Server logs are reviewed only for security purposes — detecting abuse, blocking bots, and investigating suspected scraping. They are not used for marketing or combined with analytics data.
Analytics data is aggregated and used to decide which review pages to update, which hall listings to expand, and which payment methods to test next. Contact-form messages are used to reply to you and, where relevant, to action corrections or takedown requests.
If you write to us about a specific review page — a factual correction, a request to update a licence number, a question about a bonus term — the message is also used as a reference while we update the page. The connection between your email address and the page change is removed once the correction is live.
What we collect
This site collects three categories of information. Server logs record the IP address, user-agent, time, and URL requested by every visitor — the standard web-server access log. Analytics cookies, if you accept them, record the pages you view, the referrer that brought you to the site, and anonymised device information (operating system, screen size, country). The contact form collects any message you choose to send and the email address you supply.
We do not collect: your real name (unless you give it to us in a message), payment details, bingo card numbers, or anything you do on the operator's own website after clicking an outbound link.