Why there is no consent banner
Because there is nothing to consent to. A banner asking permission to do nothing would be pure theatre, and the specific harm of that theatre is that it trains people to hit Accept without reading — so that the next banner, the one that actually matters, gets waved through by reflex.
If this site ever adds something that needs consent, it will ask properly, and this page will say so before it ships.
The word cookie is not what the law is about
This is the part worth knowing, because it is used against you regularly. European ePrivacy rules do not regulate the word cookie. They regulate storing information on your device, or reading information already stored there, whatever the mechanism is called. Local storage sits squarely inside that. So does session storage, so does an IndexedDB entry, so does a cache trick invented next year.
Which means a site can fill your browser with local storage identifiers, announce in large friendly letters that it uses no cookies, and be telling you the truth in the same way a man standing on your foot can truthfully say he is not sitting on it.
So this page names the one thing this site stores, even though a narrower reading of the title would let it stay quiet. If we are going to point at that trick on other people's sites, we do not get to use it here.
The one entry, in full
The Responsible Gaming button in the bottom corner draws attention to itself once, on a first visit, with a brief ring animation that runs three times and stops. So that it does not do this at you on every page for the rest of time, the browser records that it has happened.
The record is a single local storage entry under the key joker8:rg-widget-seen, holding the value 1. That is the whole of it. There is no identifier in it, nothing about you, nothing about what you looked at, and nothing that could be joined to anything else. It never leaves your browser, because nothing on this site is listening for it and there is no server on this side to listen with.
It gets written about six seconds after your first page loads, when the animation has finished, or the moment you open the panel, whichever happens first. On every later visit it is read once, the code sees that the animation has already run, and nothing else happens.
What that entry is not
It is not an identifier. It cannot distinguish you from anybody else who has visited, because every browser that has seen the animation stores the identical value: the number 1. Two million visitors produce two million copies of the same character.
It is not analytics. Nothing counts it, nothing reports it and nobody learns that it exists. It is not shared, because there is nobody to share it with. It does not follow you to another site, because local storage is bound to this domain and cannot be read from anywhere else.
How to get rid of it
Clear site data for this domain in your browser settings and it is gone. Private or incognito browsing never keeps it in the first place, so every visit gets the animation. Blocking storage for this site entirely also works.
Nothing breaks either way. The only consequence is that the button winks at you once more, which is a cost you are welcome to accept.
What Joker8 sets is a different question entirely
This page describes this site. The moment you click through to Joker8, you are on the operator's platform under the operator's rules, and what happens to your device from there has nothing to do with anything written here.
Expect a real cookie policy over there, with real cookies in it: an account has to remember you are logged in, and that is not something a casino can do without storage. Read theirs. It will be a longer document than this one, and it will have more in it, because they actually run a service and this is a set of pages.
Fonts, scripts and everything else the page loads
Every asset on this site comes from this domain. The two fonts are served from here rather than from Google Fonts, which matters more than it sounds: a Google-hosted font hands your address to Google on every page load, before you have clicked anything and without any cookie being involved. There is no CDN, no analytics script, no embedded video, no map and no chat widget.
The practical result is that opening a page here does not tell any third party that you exist. That is unusual enough to be worth stating plainly rather than leaving you to infer it.
If this ever changes
If a cookie, an analytics tool, an embedded third-party widget or any other form of storage is ever added, this page has to be updated before that ships, and the date at the top has to move. A cookie policy that quietly stops matching the code is worse than none, because silence is at least honest and a stale claim is not.