Privacy

What is measured

Two things. A page load, and a click on a link that leaves for a bookmaker.

The page load sends the address of the page, the address you arrived from where your browser supplies it, the language your browser reports, the width of the window and a random identifier. The identifier is generated when the page loads, is thrown away when the tab closes, and is never written to storage on your device. It exists so that two requests from one page load can be recognised as one visit rather than two, and it cannot connect one visit to another.

A second, tiny request follows the first if you scroll, tap, type or move a pointer. It says that something on the page was done by a person and carries the same short-lived identifier and nothing else. It exists because a machine reading this site looks identical to a person reading it from the server’s side, and the difference matters to us and to nobody else.

A click on an exit link records which bookmaker it was for and which page it came from. That is how this publication is paid, and it is disclosed above every table and every entry that carries such a link.

What is not measured

• No name, no email address and no account, because this site has no accounts and no forms.
• No advertising identifier and no cross-site profile.
• No cookie set by this site for measurement. The identifier described above lives in memory only.
• No precise location. A request carries an address that indicates a country and this site does nothing with it.

Things that are not this site

When you follow a link to a bookmaker you are on that company’s site and its own terms and its own measurement apply. The same is true of the outward links on the lottery page and of the regulator’s site. This publication has no control over any of them and does not receive anything they collect.

A visitor-counting service may be added to this domain when it goes live. If it is, it will be named here before it is used.

Hosting

These pages are static files served from a content network, which necessarily sees the request in order to answer it. Its own logs are kept by that provider under its own policy and are not merged with anything described above.