Cookies

Two cookies on the domain are set by our analytics provider. One is a short-lived session identifier used to group page views from the same visit into a single report row. The other is a longer-lived anonymous visitor identifier that lets the provider count unique people over a week or a month. Neither cookie contains your IP address, your name, your email or any sign-in state; the data lives on the analytics side under a pseudonymous ID. When you follow a link from one of our promotional buttons to the Betano operator, the operator's own cookies take over and we have no control over them from that point on.

A cookie is a tiny text file saved in your browser by the websites you visit. It contains a short identifier and sometimes a preference flag — nothing more. The next time you open the same site the browser sends the identifier back, which is how a site can tell a returning visitor apart from a brand-new one without asking you to log in. Cookies cannot read files on your device, they cannot see other tabs, and they cannot run arbitrary code. They are a way to remember a tiny amount of state, and most of what you consider a 'logged in' experience on the web is really a chain of cookies plus a server-side session. Cookies are set with a name, a value, an expiry date, a path and a domain; the most important of these is the domain, because it decides which site the cookie belongs to and which site is allowed to read it. A cookie set on this domain is readable only by this site; an operator domain cannot read what we set, and we cannot read what the operator sets after you follow an outbound link.

We set four cookies that originate on this domain. A consent cookie remembers that you dismissed the cookie banner so we do not nag you on every page. An age cookie remembers that you confirmed you are over eighteen. A theme cookie holds a single letter — L or D — so the site opens in the colour scheme you prefer. A visit counter holds an anonymous integer that increments on each new session; we use it to tell new readers from returning ones without storing anything that could identify you. Three of the four expire in a year; the theme cookie lives for ten years because colour preference is a long-term thing.

The analytics report we look at tells us which pages are read most, which pages are closed in the first few seconds, how readers reach the install guide and which steps inside it they bounce from. The report is aggregated at the country, device and page level; we never try to pivot it to an individual reader, and the tool we use does not let us even if we wanted to. Reports live on our side for one year and are then deleted. Nothing in them is shared with the operator.

Every cookie listed above can be removed from your browser in two clicks — look for 'Clear site data' or 'Clear cookies for this site' in the browser menu. If you prefer a blanket solution, every modern browser has a 'do not accept third-party cookies' switch, and most support private-browsing windows that forget everything on close. The site keeps working with cookies disabled; you just get the banners on every visit and the theme defaults to light mode. If you want us to delete a message you sent through the contact form, write to the editors and we will remove it from the archive.