Skip to content
Night· 0 playingPlay free

Cookie Policy

Effective 13 November 2026Last updated 5 November 2026Version 1.0

This Cookie Policy explains how Zaos Entertainment S.A ("we", "us" or "our") uses cookies and similar technologies on the website at https://zaos.global (the "website"). It explains what each one does, how long it lasts and how you can control it. It forms part of our Privacy Policy, which explains how we handle personal data more generally.

1. What cookies and similar technologies are

1.1 Cookies

A cookie is a small text file that a website stores in your browser when you visit it. Each time you return, your browser sends the cookie back, so the website can recognise your browser and remember information, such as that you are signed in. Cookies set by the website you are visiting are "first-party" cookies. Cookies set by another service whose content is embedded in the page are "third-party" cookies.

Some cookies are deleted when you close your browser ("session" cookies). Others stay for a set period or until you delete them ("persistent" cookies).

1.2 Local storage

Local storage is a feature of your browser that lets a website store information on your device. Unlike a cookie, it is not sent to the website with every request. We use it, for example, to remember your cookie choice. In this policy, "cookies" includes local storage and similar technologies unless we say otherwise.

2. Categories of cookies we use

We group cookies into four categories:

  • Strictly necessary: cookies without which the website cannot work or cannot be kept secure, such as those that keep you signed in, protect forms and verify that you are human. They do not need your consent, and you cannot switch them off in our cookie settings.
  • Functional: cookies that remember choices you make so the website behaves as you expect, such as not showing you the landing page every time.
  • Analytics: cookies that help us understand how visitors use the website, so we can improve it. We only use them with your consent.
  • Third-party content: cookies set by services whose content we embed, such as the Discord server widget and the YouTube trailer. They are set by those providers, under their own policies, when their content loads.

We do not use advertising cookies.

3. The cookies we use

3.1 Strictly necessary

Name Kind Purpose Duration
laravel_session First-party cookie Keeps your visit and your sign-in working Session, or 2 hours of inactivity
XSRF-TOKEN First-party cookie Protects forms against cross-site request forgery Session
zaos_td First-party cookie Remembers a device you have marked as trusted for two-step verification 30 days
zaos_dt First-party cookie and local storage Device token used for the closed-beta one-account check and for account security Up to 5 years
zaos_intro_hop First-party cookie Stops the home page from sending you to the landing page twice in a row 2 minutes
zaos-consent Local storage Remembers your cookie choice Until you clear it
Cloudflare Turnstile Third-party (Cloudflare) Human verification on forms, to protect them against bots and abuse Short-lived

3.2 Functional

Name Kind Purpose Duration
lead First-party cookie (necessary / functional) Remembers the campaign link you arrived from, so that a sign-up is attributed to it Session
zaos_intro First-party cookie Remembers that you have seen the landing page, so the home page opens directly 1 year
Name Kind Purpose Duration
_ga Cookie set through Google Analytics Distinguishes visitors Up to 2 years
_ga_<id> Cookie set through Google Analytics Keeps the state of your session Up to 2 years

We load Google Analytics 4 through Google Tag Manager (container GTM-T3R34Q6C). These cookies are only set after you accept analytics in the cookie banner. They help us see, in aggregated form, which pages are visited, roughly where visitors come from and which devices they use.

3.4 Third-party content

Name Kind Purpose Duration
Discord widget cookies (__dcfduid, __sdcfduid, __cfruid) Third-party (Discord) Set by Discord when its server widget loads, for its own security and request handling Set by Discord
YouTube (youtube-nocookie.com) Third-party (Google) Set by YouTube only when you play the trailer Set by YouTube

Discord widget. The website embeds the official Discord widget for the Zaos server, showing members online and an invitation link. When it loads, Discord receives your IP address and browser details and may set the cookies listed above.

YouTube trailer. The trailer is embedded in YouTube's privacy-enhanced mode (youtube-nocookie.com). Nothing loads from YouTube until you press play. Once you do, YouTube may set its own cookies and process data under Google's privacy policy.

For the cookies these providers set, please see the privacy and cookie policies of Discord and Google.

3.5 Error monitoring

We monitor website errors with Sentry (EU data region) so we can fix problems quickly. It is configured not to collect personal data.

4.1 Nothing non-essential before you choose

When you first visit the website, a cookie banner asks for your choice. Until you make it, only strictly necessary cookies are used. We use Google Consent Mode: before any tag runs, consent for analytics and advertising storage is set to "denied" by default. Google Analytics does not set cookies unless you choose to accept them. If you decline, those tags stay off.

4.2 Changing or withdrawing your choice

You can change your choice at any time by selecting "Cookie settings" in the footer of any page of the website. This reopens the choice so you can accept or decline again. Withdrawing your consent is as easy as giving it. When you withdraw consent, we stop using analytics cookies from that moment. Withdrawal does not affect the lawfulness of anything that happened before it. To remove analytics cookies already stored in your browser, you can also delete them in your browser settings (see section 5).

4.3 Where your choice is stored

Your choice is stored in your browser's local storage under zaos-consent. If you clear your browser's storage or use a different browser or device, we will ask you again.

We use strictly necessary cookies because they are essential to provide the website you have asked for and to keep it secure. We use functional cookies to provide the website as you expect. We use analytics cookies only on the basis of your consent. See section 4 of our Privacy Policy for more on our legal bases.

5. Controlling cookies in your browser

Besides our cookie settings, most browsers let you:

  • see which cookies are stored and delete them, one by one or all at once;
  • block third-party cookies;
  • block all cookies from a particular website or from all websites; and
  • delete all cookies and local storage when you close the browser.

These settings are usually found in your browser's "Settings", "Privacy" or "Security" menu. If you block strictly necessary cookies, parts of the website, such as signing in, two-step verification and forms, will not work.

6. Changes to this policy

We may update this Cookie Policy when we add, change or remove cookies, or when the law changes. The version number and the "updated" date at the top of this page show when it last changed. If a change affects the cookies we use with your consent, we will ask for your consent again where required.

7. Contact

If you have any questions about our use of cookies, please contact us:

Back to top

Play free