Privacy policy

Privacy policy. Last updated 6 September 2026. This document forms part of the site documentation.

The short version

There are no reader accounts, no advertising, no analytics and no third-party tracking scripts. Nobody here knows who you are, and there is no profile of you to build. What the site does keep is listed below, in full, with how long it keeps it.

1. Who is responsible

Operator details are not configured on this installation. The site owner sets SITE_OPERATOR, SITE_ADDRESS and SITE_JURISDICTION in the server environment, and they appear here. Until then this document names no company, because inventing one would be worse than a blank.

2. What the site stores, and why

Everything in this list is stored because a feature needs it. Nothing is stored to measure you.

• Your choices, in your browser. Language, sport, country and chosen bookmaker, kept in cookies on your own device. They never identify you. Full detail, including how to refuse the optional ones, is in the cookie policy.
• Booking codes you paste. When you ask the site to read, check or convert a bookmaker's code, the code and the selections on it are stored, so the result can be shown again and so the site can learn that bookmaker's fixture and market identifiers. A code identifies a slip, not a person, and the site holds no bookmaker account or login of yours.
• Questions you type into the assistant. The question, the reading the site made of it, how long it took, and a truncated one-way hash of your IP address — sixteen characters of a SHA-256, which cannot be turned back into an address and exists only so that one client flooding the box can be spotted. Questions are kept so the assistant can be taught the phrasings it failed to understand.
• Ratings. If you mark an answer good or bad, that mark is stored against the question.
• "Notify me" requests. The bookmaker asked for and the country the request appeared to come from. Nothing else — there is no email field, because none is asked for.
• Bookmaker link clicks. A count: which bookmaker, from which kind of page, the country, and when. No identifier for you, and nothing that can be joined into a profile. See the affiliate disclosure.
• Server logs. The ordinary request logs the hosting provider keeps, for security and error diagnosis, for the short period that provider keeps them.

3. Your country, and your IP address

The site orders bookmakers, streams and prices by where you are, so it needs a country — not an identity. It finds one in this order:

1. The country you picked yourself in a "Betting from" or "Watching from" control.
2. A country hint the hosting network or CDN attaches to the request, where there is one.
3. Failing both, a lookup on your network rather than on you.

That third step is the one worth explaining. Your address is truncated before anything is stored: the first three parts of an IPv4 address, or the first three groups of an IPv6 one — the neighbourhood, not the house. Only that truncated prefix and the country it maps to are written down, with the date, and the answer is reused for thirty days, so the lookup happens roughly once per network per month rather than once per visit. The full address itself is never stored by this site.

To perform that lookup the untruncated address is sent to a public geolocation service — ipwho.is, or ip-api.com if the first does not answer within two seconds. Those services have their own privacy policies. Private, local and reserved addresses are never sent anywhere. If you would rather this never happened, pick your country yourself: an explicit choice is checked first and no lookup is made.

4. What the site does not do

• No reader accounts, sign-ups, passwords or newsletters.
• No advertising cookies, no analytics cookies, no tag manager, no tracking pixel.
• No selling, renting or sharing of data with anybody for marketing.
• No profiling, no cross-site tracking, and no automated decision-making about you.
• No special-category data — the site holds nothing about your health, beliefs or anything of that kind, because it never asks.

5. Lawful basis

Where data-protection law such as the UK/EU GDPR applies, the bases are: your consent for preference cookies kept between visits, which you may withdraw at any time on the cookie policy page; legitimate interests for keeping the site working, secure and improvable — reading a code you asked to be read, keeping a count of bookmaker clicks, and spotting abuse; and necessity for the essential cookies without which the page you asked for cannot be served.

6. Who else sees anything

• The bookmaker. When you ask the site to read a code, the code is sent to that bookmaker's own public endpoint, because that is where the answer is.
• The geolocation services named in section 3, and only for an address on a network the site has not seen in the last thirty days.
• The hosting provider, which necessarily handles the traffic and keeps request logs.
• Sites you leave for. Opening a bookmaker link or a stream takes you off this site, and that site's own policy applies from then on.

Nobody else. There is no data broker, no ad network and no analytics vendor in this list because there is none in the code.

7. Where it is kept, and for how long

Data is held in the site's own database at its hosting provider. Because a request can come from anywhere, a lookup may involve a service outside your country; only the items described above are involved, and never an identity.

• Cookies — as tabled in the cookie policy; at most a year, and only this session if you decline.
• Country-by-network cache — refreshed after 30 days.
• Pasted codes, questions, notify requests and click counts — kept while they are useful to the feature that stores them, and removed on request.
• Server logs — the hosting provider's own short retention.

8. Your rights

Where the law gives them to you, you have the right to ask what is held, to have it corrected or erased, to object to or restrict its use, to receive it in a portable form, and to withdraw consent. Withdrawing cookie consent takes one click on the cookie policy page.

For everything else, ask through the contact page: pasted codes, questions and notify requests are removed on request. Because the site holds no identity for you, please say which item you mean — the code you pasted, for instance — so it can be found. You also have the right to complain to the data-protection authority where you live.

9. Children

This site is for adults. It is not directed at children, it asks for no personal details, and its betting content requires you to be 18 or over, or older where the law where you live says so.

10. Security

The site is served over HTTPS, the admin area is separated from the public site and protected by two-factor authentication, and the public site holds no credentials of yours because it never asks for any. No system is perfect; a suspected problem should be reported through the contact page.

11. Changes

This page describes the site as it is built, and is updated when the code changes. The date at the top is when it last changed. Where a change affects cookies, the cookie policy's version is raised and everyone is asked again rather than assumed to agree.