Legal documents are provided in English; the English version is the controlling one.
Cookie Policy
Effective date: 21 October 2026 · Version 2026-10-21 · Replaces version 2026-10-15
This Policy explains what mariobets stores on your device and why. The short version: the Service itself needs only one sign-in cookie, a few preferences and conveniences, and one offline page. The cookies of Google Analytics and Google's advertising cookies are used only if you agree to them, only on our public pages and never on the pages for members. Our own visit counts set no cookie and keep totals only.
In this Policy, our public pages are the home page, the request for access, these legal pages and the contact page; the pages for members are the ones you reach once signed in.
1. What we store on your device
The sign-in cookie
| Name | Type | What it does | How long |
|---|---|---|---|
__Host-mb_session | Cookie, strictly necessary | Keeps you signed in. It is first-party, HttpOnly, Secure and SameSite=Lax, so scripts on the page cannot read it and it is not sent with requests that other sites make in the background. | Up to 7 days |
Preferences and conveniences in local storage (kept in that browser until you clear them)
| Name | What it does |
|---|---|
mb-lang | Remembers the interface language you chose. |
mb-theme | Remembers the colour theme you chose (light or dark); nothing is stored for Auto. |
mb-cookie-ack | Remembers that you have seen the notice about this Policy, so it is not shown again; when the notice asks you about optional cookies, it also keeps your answers (accepted or refused) and the day you gave them, so that you are not asked again for 6 months. |
mb.tips | Remembers whether you switched the glossary hints on or off. |
mb.experience | Remembers your experience level (beginner or expert), so pages open in the right mode before your settings arrive. |
mb.odds_format | Remembers the odds format you chose. |
mb-install-guide | Remembers that the guide to adding mariobets to your home screen has been shown. |
mb-onb-step | Remembers the question of the first-visit setup to come back to. |
mb-list-v1 | Keeps Your list: the selections you collected to study together. |
mb-rc-stake | Remembers the last stake you typed when logging a bet from a match page. |
mb.tips.filters | Remembers your filters and view in the Predictions section. |
mb-news-img | Remembers whether you turned news images on. |
mb-mp-howto | Remembers that you have seen the guide to reading a match page. |
mb.learn.v1 | Keeps your progress in Learn. |
mb.hm.head | Remembers what the top of your home page last showed (the name in the greeting and the status labels), so that nothing moves while the page loads. |
Conveniences in session storage (deleted when you close the tab)
| Name | What it does |
|---|---|
mb-onb-later | Remembers that you chose "Later" in the first-visit setup during this visit. |
mb-rc-logged | Remembers which prices you logged from a match page in this tab, so the button shows that they are logged. |
mb.tips.slip_keys | Keeps the selections you saved for the accumulator calculator in this tab. |
mb-lang-hop | Only when a page opened at an address without a language takes you to the same page in your language: keeps, for that move, the address of the page you came from, so that our visit counts (section 3.1) still see where the visit came from. It is read once, within 10 seconds, and then deleted. |
The service worker and its offline page
| Name | Type | What it does | How long |
|---|---|---|---|
/sw.js | Service worker | A small script registered on every visit. It shows browser notifications if you turn them on, and keeps one offline page (cache mb-offline-v3) shown when your connection drops; every page is always loaded from our server; it stores no personal data. | Until you clear it |
mb-offline-v3 | Cache storage | The offline page and its script, kept by the service worker. | Until you clear it, or until a new version replaces it |
If you turn on browser notifications, your browser asks for your permission first and then gives us a subscription for its push service (see the Privacy Policy, section 2.8).
All of the above are set by mariobets itself. None of them tracks you across sites, builds a profile of you or serves advertising. The cookies that Google sets, only if you agree to them, are listed in section 3.
2. What we do not use
- No advertising or analytics cookies unless you agree to them (section 3), and never on the pages for members.
- No personalised advertising: if ads are shown, they are not chosen from a profile of you.
- No tracking pixels.
- No device fingerprinting.
- On the pages for members, only our own scripts: every script there comes from mariobets itself. On our public pages, Google's scripts load only as section 3 describes.
- No external font services: our fonts are served from our own server.
3. Visit statistics, analytics and ads
3.1 Our own visit counts — always on, no cookie. When one of our pages is opened, it sends our server a short message with the page's address (without the part after a question mark, which can hold a code), the address of the site that linked to it and the campaign tags of the address, if any. Our server adds one to counts kept per day that record at most the page, where the visit came from, the type of device, the browser's language and the country it suggests, and whether the page was opened by a signed-in member or by a visitor. To estimate how many different visitors came each day, it computes, in its memory only, a code from your IP address and browser with a random key that is replaced every day and never written anywhere. It sets no cookie and uses no local storage; only when a page takes you to its version in your language is the address you came from kept in this tab for that move (mb-lang-hop, section 1). If you are signed in, your browser sends our sign-in cookie with the message, as it does with every request to our server; our server looks at it only to count the page as a member's, never which member, and to leave out the owner's own visits. Neither your IP address nor any identifier is stored for the counts, so the totals cannot tell visitors apart or follow anyone. Like every request, the message may also be recorded, with your IP address and the time, in our server's technical logs, which are kept apart from the counts and hold only their most recent 100 MB. Only the totals are kept (see the Privacy Policy, sections 2.1 and 2.18).
3.2 Google Analytics — only if you accept it. We may use Google Analytics 4, a service of Google Ireland Limited, on our public pages, never on the pages for members. Our cookie notice asks you first. Until you accept, and if you refuse, the Google Analytics script is not loaded: nothing is sent to Google and nothing is stored on your device for it. If you accept, the script loads and sets these cookies on our domain:
| Name | Type | What it does | How long |
|---|---|---|---|
_ga | Cookie, analytics (Google Analytics), only if you accept it | A random identifier that lets Google Analytics tell your browser's visits apart from those of other visitors. | 13 months |
_ga_<container-id> | Cookie, analytics (Google Analytics), only if you accept it | Keeps the state of your current visit; the end of its name is our Google Analytics measurement code. | 13 months |
Google Analytics 4 does not log or store IP addresses. We have turned off Google signals, the collection of granular location and device data, ads personalisation and the sharing of the data with Google for its own purposes; through Google's consent mode, Google's tag is told that you agreed to analytics only, never to advertising. Google keeps the data for 2 months. Details: Privacy Policy, section 2.18.
3.3 Google's ads — only on the home page and the request for access, and only as you choose. We may show ads served by Google AdSense, a service of Google Ireland Limited, on our home page and on the request for access, never on the pages for members, the legal pages or the contact page. Ads are off unless we switch them on. When they are on:
- Google's consent message. These pages first show Google's consent message, a consent management platform certified by Google under the IAB Europe Transparency & Consent Framework. To show it, the page loads Google's consent script from Google's servers before you choose, so Google receives your IP address and browser information, as with any request.
- No ads without your consent. Ads are loaded only after you have made your choice, and only if you agree to Google storing and reading information on your device. If you refuse, or close the message without choosing, no ad is loaded and no advertising cookie is set.
- Never personalised. We have turned off personalised ads: the ads are chosen from the content of the page and your general location, not from a profile of you. Google still uses its cookies, if you allowed them, to limit how often you see the same ad, to measure the ads and to prevent fraud.
- No ads for gambling. We block ads for gambling and betting.
| Name | Type | What it does | How long |
|---|---|---|---|
FCCDCF | Cookie, needed for Google's consent message | Keeps the choice you made in Google's consent message, a refusal included, so that it is respected and you are not asked again on every page. | 13 months |
FCNEC | Cookie, Google's consent message | Used by Google's consent tool for its own working; Google lists it among the analytics cookies of that tool. | 1 year |
__gads | Cookie, advertising (Google AdSense), only with your consent | Limits how often you see an ad and measures the ads. | 13 months |
__gpi | Cookie, advertising (Google AdSense), only with your consent | The same purpose as __gads. | 13 months |
__eoi | Cookie, security (Google AdSense), only with your consent | Helps Google detect fraud and abuse of ads. | 6 months |
When ads load, Google may also read or set cookies on its own domains, such as doubleclick.net, under its own policies. The names and durations above are the ones Google publishes in its list of cookies; Google may change them. For ads, Google uses these data as an independent controller: see Google's Privacy Policy and how Google uses information from sites that use its services.
3.4 Google Search Console — nothing on your device. We use Google Search Console to see how our public pages appear in Google Search: which searches showed them, how often they were clicked, their position, and which pages Google has indexed. These are aggregate figures from Google Search: nothing of Google's runs on our pages for it and nothing is stored on your device.
4. Content from other sites
4.1 News images. Images are off until you turn them on on the News page; your choice is remembered in that browser (mb-news-img). Once they are on, the image of an article is loaded directly from the publisher's server. When your browser loads it, that server receives your IP address and browser information, as with any request, and may handle them — and any cookies of its own — under its own policies, which we do not control. We send it nothing else: our pages tell your browser not to pass on which page of ours you were reading.
4.2 Share buttons. The buttons for sharing on WhatsApp or X are plain links. Nothing is sent to those services unless you click one.
5. When we ask for your consent
The EU ePrivacy rules (Article 5(3) of Directive 2002/58/EC; in Italy, Article 122 of the Personal Data Protection Code and the Garante's cookie guidelines of 10 June 2021; in the UK, the Privacy and Electronic Communications Regulations) require consent before storing information on your device or reading it, except when this is strictly necessary for a service you have asked for.
- No consent needed. The sign-in cookie is strictly necessary, and the other items of section 1 only remember choices you made in the interface — your answers in our cookie notice included — or keep what you asked the Service to keep. Our own visit counts (section 3.1) set no cookie, keep the address you came from only for a moment when a page takes you to its version in your language, look at the sign-in cookie your browser sends anyway only to tell members' pages from visitors' in the totals, and keep totals only. On the pages with Google's ads, Google's consent message keeps your choice, whatever it is, in its
FCCDCFcookie, which is needed to record that choice. We show a short notice so that you know. - Your consent first. The cookies of Google Analytics (section 3.2) and Google's advertising and security cookies (
__gads,__gpiand__eoi, section 3.3) are not necessary: they are used only if you agree to them. Google's consent tool also uses its ownFCNECcookie, which Google lists among the analytics cookies of that tool (section 3.3). Nothing is ticked in advance, refusing is as easy as accepting, closing a consent message without choosing counts as refusing, and the Service works the same whatever you choose. After you refuse, we do not ask you again for at least 6 months, unless what we use changes.
6. How to manage them and withdraw your consent
- Change your mind at any time. The link Privacy and cookie settings, here and at the foot of the home page, of the request for access and of the pages for members, opens your choices again: in our cookie notice and, on the pages with Google's ads, in Google's consent message. There you can withdraw a consent as easily as you gave it, without affecting what was done before. If you withdraw your consent to Google Analytics, its script is no longer loaded and we remove its cookies from our domain.
- In your browser. You can delete cookies, local storage, session storage and cached files, and remove the service worker, in your browser's settings at any time. If you block the sign-in cookie, you cannot stay signed in. If you clear the preferences, the Service returns to its defaults and our cookie notice appears again.
- Google's own tools. Google offers a browser add-on to opt out of Google Analytics and its own ad settings.
7. Changes
If we ever wanted to use anything else that is not strictly necessary, we would update this Policy first and ask for your consent before using it, with an option to refuse that is as easy as the option to accept.
Questions: privacy@mariobets.xyz.