Cookies at Spin Winera
What happens when the site remembers your login, your language or the lobby view you left? Cookies: small files the browser stores, which the pages read on the next visit. We use them on our pages for the technical session, for preferences and for measurement, and this policy describes the types and the control you have over them.
The cookie types we use
| Type | Purpose | Typical examples |
|---|---|---|
| Essential | Keep the session and the account usable | Login state, security tokens, wallet session |
| Preference | Remember choices on the pages | Language, lobby view, display settings |
| Analytics | Measure how pages are used | Page views, feature usage, error rates |
| Affiliate | Attribute a visit to a partner link | Campaign and referral parameters |
How we use cookies, purpose by purpose
- Essential cookies hold the session that keeps you logged in between the lobby, the wallet and the sportsbook, and they carry the security tokens that 2FA and the payment flow rely on.
- Preference cookies store the language and the display choices so the pages open the way you left them.
- Analytics cookies measure which pages and features are used, which feeds maintenance and error fixing rather than advertising profiles.
- Affiliate cookies record the parameters of a partner visit so that an attributed registration can be processed correctly.
Managing cookies in your browser
Every current browser keeps cookie control in its settings: cookies can be blocked, deleted per site or cleared entirely, and a private browsing mode drops most of them when the window closes. Blocking essential cookies breaks the login and the wallet session, since those functions need their tokens; blocking analytics and preference cookies costs convenience rather than function. The browser help describes the steps for each platform, and after deleting cookies the next login rebuilds the essential ones.
Third-party cookies and their own policies
Third parties can set cookies through embedded content or partner links: a payment provider’s page in its own window, or an attributed partner visit. Those cookies follow the third party’s own policy, and the browser’s per-site view shows which domains have set what. Where a third-party service is involved, its own controls apply alongside ours.
How updates to this policy are announced
When this policy changes
A change in cookie usage, for example a new analytics tool or a change in the essential set, is published by us as an updated version of this policy. Our date line below moves with each update.
Checking what your browser holds
The browser’s site-data view is the practical place to see and control what is stored, and it always reflects the current state rather than a description of it.
A practical middle ground for most players: keep essential cookies enabled, allow preference cookies for comfort, and decide on analytics per conviction. Deleting all cookies before a shared device changes hands is worth the two minutes, since it drops both the session and any stored payment context. If a page behaves oddly after a deletion, a fresh login rebuilds the essential set, and the lobby returns to its default view until the preferences are set again.
Last updated: 2026-11-15
