We use the data described below for three narrow purposes: to serve the pages on this site, to show which outbound links were clicked by which operator, and to answer messages sent to our editorial inbox. We do not profile readers, we do not build advertising audiences and we do not sell data on to third parties. Analytics are aggregated at the country level and cannot be traced to an individual visitor.
A short note on what we deliberately do not do: we do not run retargeting scripts, we do not share e-mail addresses with any third party, we do not place pixels from social networks on the review pages and we do not sell any form of mailing list. The three narrow purposes listed above are the only use of visitor data on this site.
Under UK GDPR you can ask us for a copy of any data we hold about you, ask us to correct it, or ask us to delete it. Requests go to [email protected] with 'Data request' in the subject line. We respond within thirty days. If you are not satisfied, you can complain to the Information Commissioner's Office at ico.org.uk — the UK supervisory authority for data protection.
To make a UK GDPR request specific enough for us to action it, please include the e-mail address you have written to us from, the dates of any correspondence and (if the request is for deletion) a note of which messages you would like removed. Without those details we cannot find the thread and will have to come back for more information. We treat requests from readers who have not previously written to us as a formal confirmation that we do not hold data on them, which we answer in writing within thirty days.
Three third parties see visitor data in a limited form: our hosting provider (page requests), our analytics provider (aggregated page views and country) and the operator we link out to (the fact that the click came from Kongslots). None of them receive a name, an e-mail or an account identifier from us because we do not collect any of those on this site.
The hosting provider is a UK-registered company with servers in London. The analytics provider is EU-based and processes data under standard contractual clauses. The operator at the end of the /play/ redirect is the only party that receives a referral token identifying this site; it does not receive any data about who the reader is because we do not have that data to share.
On a standard page view we store the request time, the page requested, the country derived from the IP address and the user-agent string reported by the browser. We do not store the full IP address, we do not run cross-site trackers and we do not place advertising cookies. Readers who write to the editorial inbox provide the e-mail address they chose to write from; that address is held only as long as the thread is open.
We do not run any form of fingerprinting, do not combine data across sites and do not store a visitor identifier for longer than it takes to produce the daily traffic count. Our analytics implementation runs server-side and uses the first segment of the request IP (truncated to the /24 for IPv4 or /48 for IPv6) only long enough to resolve the country code — the full IP never reaches disk. The analytics cookie is renewed at the start of each session with a fresh random identifier.