TornadoBet Lists All 14 Cookies by Name and Leaves Refusing Them to the Browser
Neutral for players
NeutralThe TornadoBet Cookie Policy lists 14 cookies by name and duration, 5 first-party and 9 third-party, the longest-lived being _ga at 730 days, used to identify users. Three cookies identify users, one checks for ad blockers, and a first-party cookie called bonus stays for 7 days to manage the registration bonus. The policy says nothing about consent: the only way it gives to refuse cookies is the browser's own settings, and it warns that blocking them may affect how the site works. A player can read exactly what is stored and for how long, and the policy leaves refusing it to the browser.
The record
-
Terms captured31 Aug 2026
-
Terms assessed31 Aug 2026
-
Human reviewed21 Nov 2026
-
Published21 Nov 2026
We capture tracked terms pages on a fixed schedule. Every assessment is scored for player impact and human-reviewed before it joins the public record.
Watch Tornadobet
Get an email when Tornadobet changes its terms. The clause, the date, the record. Nothing else.
Alerts go to your account email. Stop them any time.
You're watching Tornadobet.
What this means for players
The TornadoBet Cookie Policy uses the word "cookies" for cookies and for pixel tags, web bugs, web storage and similar technologies, and says a cookie can help the site recognise a device, give access to functions and register a visitor's "surf patterns". It then lists every cookie in two tables, with a name, a duration and a one-line description for each.
- Every cookie is named, with its lifetime. The first-party table lists JSESSIONID and PHPSESSID for one session each, bonus for 7 days, and osgCookiePolicyAccepted and lang for 365 days. The third-party table lists nine more, from _gat at 1 minute to _ga at 730 days. A player can check the list against the browser and see exactly what is stored and for how long.
- Three cookies identify users, the longest for 730 days. _ga (730 days), _gid (1 day) and _ym_uid (365 days) are each described as "used to identify users", and _ym_d keeps the date of the user's first visit for 365 days. A returning visitor can be recognised for up to two years from the day the cookie was set.
- Only one provider is named. The third-party table gives no company for any cookie, and the only provider the policy names is Yandex Metrika, in the description of _ym_metrika_enabled. A player can read the name of each third-party cookie but not, from the policy, who receives what it collects.
- Ad blockers are checked. _ym_isad lasts 2 days and is "used to check ad blockers". Whether a player blocks adverts is itself one of the things recorded.
- A bonus cookie sits on the device for a week. The first-party cookie named bonus lasts 7 days and is "used for management of registration bonus". Something about a registration bonus is held on the player's device for a week, and the policy does not say what.
- Refusing is left to the browser. The policy says: "Most web browsers allow you to manage your cookie preferences. You can set your browser to refuse cookies, or delete certain cookies." It adds: "Please note that if you choose to block cookies, the due functioning of the Webpage may be affected." Consent is not mentioned anywhere, so turning tracking off is the player's job, done outside the site, at the risk of the site working less well.
Nothing in the policy touches a balance, a bonus amount or a withdrawal. It is complete about what is stored and silent about permission, and the one cookie that records acceptance of the policy is described with the single word "Ok".
Evidence — full-page captures
Each exhibit is the full terms page exactly as it stood at that moment, archived by us. The originals are large images and open in a new tab.