Cookie Policy.

A cookie is a small text file — usually no more than a few kilobytes — that a website asks your browser to store on your device. The next time you visit that site, the browser sends the cookie back, which lets the site remember you without making you log in again from scratch.

Cookies have been around since the mid-1990s. They're not malware, they can't access your files, and they can't carry viruses. But they can be used to track behaviour across sites — which is why modern privacy laws give you control over the non-essential ones.

Two related technologies behave the same way: local storage (data the browser keeps on your device until you clear it) and session storage (data the browser keeps until you close the tab). Where this policy says “cookies”, the same rules apply to both.

We use cookies for four reasons, in order of priority:

• Run the site. Keep you logged in, remember your language and currency, protect against fraud and bots.
• Remember your preferences. Recently-played games, default payment method, layout choices.
• Understand how the site is used. Anonymous traffic measurement so we know which pages load slowly, which features are popular, and where people drop off.
• Run our advertising, but only if you opt in. Match ad clicks to sign-ups so we know which campaigns work, and reach similar audiences on Facebook, Google, or TikTok.

The first two are essential — turning them off breaks the site. The last two are optional and require your consent under the GDPR and equivalent rules.

We group every cookie into one of four categories. Sections 4 through 7 list the actual cookies in each category, with their names, purposes, and durations.

These cookies are essential for aulegiano.com to work. They handle authentication, security, and core preferences. They cannot be disabled — if your browser blocks them, most parts of the site will fail to load.

Functional cookies remember small preferences that make the site easier to use the second time around. They're always set on a logged-in account because they're tightly tied to your gameplay history.

Analytics cookies help us count visitors, measure page-load times, and find broken bits. We use Google Analytics 4 with IP anonymisation enabled, which means the last octet of your IP address is dropped before any data leaves your browser. You stay anonymous in the data — we see numbers, not individuals.

These are opt-in. If you decline through our cookie banner, none of them are set.

Marketing cookies link your visit to a click on one of our ads, and let us measure whether the ad worked. They also help us find similar audiences on Facebook, Google and TikTok — so the ads we run are shown to people more likely to be interested in what we offer, and not to people who have no use for it.

These are strictly opt-in. If you decline, we don't set them. If you accept and later change your mind, you can withdraw consent through the cookie banner or by clearing them from your browser.

Some of the cookies above are set by third parties — usually because they're needed to run a service we've embedded. The main third parties are:

• Cloudflare — fronts our site for DDoS protection and global delivery. Sets the __cf_bm bot-management cookie.
• Google Analytics 4 — anonymous traffic measurement. Sets _ga and related cookies. Privacy info at policies.google.com/privacy.
• Google Ads — conversion tracking from paid Google search ads. Sets _gcl_au.
• Meta (Facebook) — Pixel for ad-conversion tracking. Sets _fbp.
• TikTok — Pixel for ad-conversion tracking. Sets tt_pixel_id.

We don't allow third parties to use the cookies they set on our site for any purpose other than the one we engaged them for. They're bound by data-processing agreements that prohibit reuse for their own marketing.

Under the GDPR and equivalent rules elsewhere, we ask for your consent before setting any analytics or marketing cookies. Strictly necessary and functional cookies don't require consent because they're essential to the service you're actively using.

We may update this policy from time to time, usually because we've added or removed a service. The version date at the top of the page tells you when the current version took effect. For substantive changes — adding a new analytics or marketing partner, for example — we'll trigger the cookie banner again so you can review and re-consent.

For any questions about this Cookie Policy — or to exercise your data-protection rights — email us:

[email protected]

For everyday account help, the 24/7 live chat is much faster.