How our site handles reader information

The facts of our data handling, before anything else:

• We collect what readers send us through the contact form, and nothing a gambling account would need.
• We measure anonymous traffic through standard analytics, in aggregate, with names detached.
• Reader data stays with our editorial desk and serves the reply it was written for.
• Account matters belong to the casino’s own support, so balances, deposits and identity documents pass through our hands at no point.

How your data is protected

The small surface we keep

Because we run guides rather than accounts, the data we hold is limited to correspondence and aggregate statistics, and a smaller vault is easier to guard than a large one.

Access on our side

Only our editorial desk reads contact messages, and analytics reach us in aggregate form, without names or addresses attached to the numbers.

How long we keep things

Contact correspondence stays with us for as long as a conversation can reasonably continue; traffic statistics persist in aggregated form for trend purposes, and both expire on routine housekeeping cycles rather than pile up indefinitely.

How changes to the policy are announced

Our practice when the policy changes:

• The date line at the foot of the policy moves to the day of the change.
• Material changes, such as a new analytics provider, are noted in the relevant section rather than buried.
• The policy keeps describing only what the site actually does, so a re-read is always current.

Where affiliate and external links involve third parties

Some links in our guides are commercial (affiliate) links, and following one hands the reader to a third-party site governed by that party’s own privacy terms. Analytics providers may set their own cookies as a reader moves through our pages, and the cookie notice describes how those are managed. A reader’s data path through an external site is that site’s responsibility, not ours.

How information is used, purpose by purpose

Using messages to answer readers

Message content is read to answer the question asked, to fix a verified correction, or to improve a passage a reader found unclear, and for nothing else on our side.

Keeping the site useful

Aggregate traffic figures tell us which guides earn their length and which need rewriting, and they inform the editorial rhythm without ever identifying an individual reader.

What we may collect

Two kinds of information reach us. The first is what a reader chooses to send: a name or a pen name, an email address for the reply, and whatever context the message itself contains. The second is anonymous measurement: page views, reading depth and general device type, collected by standard analytics and never joined to a message or a name. Payment data, gambling account details and government identifiers sit outside our collection entirely.

Your rights over your data

What a reader can ask

A reader can ask what correspondence we hold, request its deletion, or correct a detail in it; UK data protection law underpins these rights, and we honour them without ceremony.

How to use the rights

One message through our contact form, naming the request, starts the process; the reply comes from our editorial desk and asks nothing beyond what the request needs to identify the material.
Last updated: 9 November 2026