A closer look: review a round with the details close by.
Cookies and browser storage are different
The scope of this section is described here. A cookie may accompany requests to a matching website path, while local storage is read by code in the browser. This release mainly uses local storage for its game features. That distinction matters when using browser tools or clearing saved progress. Consult the related information pages for the other storage and contact functions.
The FAQ security cookie
The following statement describes the first-party implementation. The first-party cookie named slots_csrf supports the protected question-submission flow. Its lifetime is approximately one hour and its path is limited to the API endpoints. It is configured as HttpOnly and SameSite Strict, with Secure enabled for the configured public HTTPS address. The available local controls are described in Privacy & Cookie Settings. Additional context is available in the site’s related guides.
When the form cookie is requested
The distinction below is relevant to your choices. The browser obtains a form token and security cookie when a question is submitted through the page's script. The subsequent POST includes the signed token and matching cookie. The cookie is not a paid-player account, an advertising identifier or a record of spin outcomes. An independently changed deployment should be described by an updated policy. The visible interface identifies the feature currently in use.
Game data stored locally
The following statement describes the first-party implementation. The local storage keys beginning slots-v1:game- contain saved data for each mode when saving is enabled. A record can include balance, current wager, last outcome, pending feature values, statistics and recent history. Ordinary page requests do not transmit that storage as a cookie. The available local controls are described in Privacy & Cookie Settings. Keep the current domain in view when checking saved information.
The preference storage entry
The following statement describes the first-party implementation. The slots-v1:preferences record stores the saving and sound choices. It remains separate when game data is cleared so that the chosen settings can persist. If storage is blocked, the application can keep a temporary preference for the current page, but cannot promise to remember it later. The available local controls are described in Privacy & Cookie Settings. Keep the current domain in view when checking saved information.
Controls available to you
The following statement describes the first-party implementation. Privacy & Cookie Settings can turn off game saving and remove game records. Your browser can also delete cookies, local storage or all data for this domain. Removing the form-security cookie may require a new form token before a pending question can be accepted. The available local controls are described in Privacy & Cookie Settings.
Third-party scripts are outside these switches
The current release handles this area as follows. The stock package does not load a third-party advertising or analytics service. If the operator independently adds code or the visitor follows an external link, additional storage may be involved. The built-in game-saving switch does not automatically block code added outside its controls. The available local controls are described in Privacy & Cookie Settings. Additional context is available in the site’s related guides.
Contact about this policy
This information concerns the supplied website. For a question about the first-party storage described here, contact [email protected]. State the domain, the affected feature and any relevant browser behavior. Do not send authentication cookies, private tokens or a full browser profile with your message. An independently changed deployment should be described by an updated policy. The visible interface identifies the feature currently in use.