Information practices behind our Goldex reading site
An information site runs on very little data, and ours is built to keep it that way. Our systems hold only what readers send us and what page analytics count; an information site sits outside the account, payment and balance world of a casino, so those categories never reach us.
That short list is the whole policy in miniature: each category has a purpose, the cookies come with their own rules, and the rights of the reader cover all of it.
Information that reaches us, and why
| Data | Where it comes from | What we use it for |
|---|---|---|
| Contact details | Messages sent through our form | Answering the question or correction sent |
| Message content | The text a reader writes to us | Handling the request it contains |
| Usage data | Analytics on page visits | Understanding which guides get read and improved |
| Affiliate clicks | Commercial links a reader follows | Attributing visits so our coverage can stay independent |
Cookies and analytics in brief
- Essential cookies keep the pages working; analytics cookies count visits and reading patterns in aggregate
- Affiliate cookies may record that a reader arrived through one of our commercial links
- Our cookie policy carries the full breakdown of types, purposes and browser controls
- Reader rights extend to this data as to any other we hold
The rights readers keep
- A request can ask what information about a reader we actually hold
- A request can ask for a correction or a deletion of stored contact data
- A request can withdraw consent to analytics where the browser consent applies
- Requests travel through the same contact routes as everything else on our site
- A reply confirms what was found, changed or removed, without formality or forms
- Exercising a right costs nothing and needs no reason stated
How information is used, purpose by purpose
Answering readers
Contact messages are used to reply, to apply a correction where one holds, and to keep a short record of the exchange so a follow-up does not start from zero.
Improving the guide
Aggregate usage data shows which pages get read and which get abandoned; it never gets tied to an identified reader.
Security, retention and links out
Message records are kept only as long as they serve the exchange they belong to, then removed; access to them stays with the editorial desk. Aggregate analytics age out on the schedule set in our cookie policy. Our pages link to coverage of the brand and, plainly marked, to commercial routes; those destinations run their own privacy practices.
Changes to these practices
When our practices change, the pages carry the updated version and the date line below moves with it; continued reading after a change means the updated version applies.
Last updated: 9 November 2026