What is recorded
When a page loads, a request goes to a counter on this same domain carrying the address of the page, the referring page if there is one, the language your browser reports and the width of the window. A second, smaller request is sent the first time a visit shows any sign of being a person rather than a crawler: a scroll, a tap, a key or a pointer moving. It carries nothing but a random identifier.
That identifier is generated fresh for each page view, lives only as long as the page is open and is discarded when the tab closes. It is not stored on your device, it is not linked between pages, and it cannot be tied back to you.
Why the second request exists
Because a large share of what arrives at a site like this is automated, and nothing a server can see distinguishes a scraper from a reader. Headers can be forged and addresses can be borrowed. Scrolling cannot. Separating the two is the difference between knowing how many people read a page and knowing how many programs fetched it.
What is not recorded
No name, no email address, no account, no payment detail, and nothing that identifies a device between visits. Nothing is sold and nothing is shared with the bookmakers described on this site.
Clicking through to a bookmaker
A link to a bookmaker passes through a page on this domain that records which brand was clicked and then forwards you. That record is the brand and the page you came from, not you. Once you arrive at the bookmaker you are on its site under its own privacy policy, which is a different document with different rules, and it is worth reading if you are about to open an account.
Third parties
A general-purpose analytics tag may be loaded on this domain in future and would be named here before it was. At present the counter is on this domain and nothing else is loaded from anywhere else, which is also why nothing here needs a consent banner to sit in front of it.
Corrections
There is very little held here to ask about. What is worth raising is a wrong figure about a bookmaker, and how those are handled is set out on the page about how this is built: a correction goes into the fact base once and lands on every page that reads it.