Cookie Policy — Cookies and Tracking on donbet-australia.com

What cookies actually are

A cookie is a small text file that a website asks your browser to store, and which your browser hands back on later requests to that same site. That is the entire mechanism. It is not a program and it executes nothing. It cannot read your hard drive, see your other tabs, or reach your camera and your files. Think of it as a note the site leaves for itself, kept by your browser and returned next time you visit.

Cookies exist because HTTP is stateless. Every request your browser makes lands on a server with no memory of the one before it. Without some way to carry a small amount of state between requests, a website could not remember that you dismissed a banner thirty seconds ago, never mind that you refused analytics last week. Cookies are the oldest and most widely supported answer to that problem, which is why they are still everywhere in 2026.

Cookies, localStorage and the rest

Cookies are not the only form of browser storage, and the distinction matters, because clearing one does not clear the other.

• Cookies carry an expiry date and get transmitted to the server with every matching request. They are tiny, a few kilobytes at most, and the server can read them.
• localStorage stays in the browser and never travels to the server on its own. There is no expiry on it. It persists until the site deletes it or you clear site data, and it holds considerably more than a cookie can.
• sessionStorage behaves like localStorage, except that closing the tab wipes it.

This comes up because we use a small amount of local storage for interface state, such as remembering that you expanded a particular FAQ item, and a browser setting labelled "block cookies" will not always clear it. Choosing "clear site data" or "clear cookies and site data" in your browser removes both. Throughout this page, where we say cookies we mean cookies and equivalent browser storage together, since the practical effect on you is identical.

Categories of cookies we use

Cookies on this site fall into three groups, and the third is a good deal smaller than you would expect on a gambling-adjacent website. Two of the three are entirely optional, which is the part most cookie notices bury near the bottom.

Strictly necessary

These make the site work. They record your consent choice so the banner does not reappear on every page. They carry security tokens protecting against cross-site request forgery, and they hold load-balancing information so your requests reach a consistent server. Browsing a modern website with these switched off is not really possible, which is why consent law treats them as exempt. Refusing them amounts to refusing to load the site.

Analytics

These tell us which guides get read and which get abandoned halfway. They record a page view, an approximate location at country or state level derived from your IP, a device class and a traffic source. We read them in aggregate: does the payments guide outperform the bonus guide, is a table causing people to bounce on mobile. Optional, and they load only if you accept them.

Preferences

These remember small choices you have made: an expanded section, a dismissed notice, a display setting. They exist so the site behaves the way you last left it. Optional, and refusing them costs you nothing beyond the site forgetting.

What we do not use

There are no third-party advertising cookies on this site. No ad network pixels, no retargeting tags, no social media tracking widgets, no data-broker beacons, and no fingerprinting scripts trying to identify you without storage at all. That was a deliberate editorial decision rather than an accident of configuration, and it removes the single largest category of tracking found on most sites in this sector. Cross-site profiling does not happen here either, and reader data is neither sold nor shared. The terms of that undertaking are set out in our website terms.

The cookie banner and your choice

On your first visit you get a banner. There is no dark pattern in it: accepting and declining are equally reachable, declining takes a single click, and nothing sits pre-ticked in our favour. Until you choose, no analytics or preference cookies load at all. Strictly necessary cookies load regardless, since they are the mechanism delivering the page and storing your answer.

Your answer is recorded for twelve months. After that we ask again, on the reasonable assumption that consent given a year ago has gone stale. Clearing your browser cookies clears the record too, which is why the banner reappears after a clean-out. That is the system working as designed.

Changing your mind

Consent you cannot withdraw is not really consent, so there are two routes back:

1. Use the cookie settings link in the site footer to reopen the banner and change your selection. Your new choice takes effect on the next page load.
2. Clear cookies for this domain in your browser. That deletes the stored consent record along with everything else, so the banner greets you fresh on your next visit.

Withdrawing consent stops future collection. It will not retroactively delete aggregate analytics already recorded, because those records are not tied to an identifiable person and there is no individual row to pull out of them. For what is retained and for how long, the retention table in our privacy policy is the definitive answer.

Managing cookies in your browser

Your browser is the authoritative control, and it outranks any banner on any website. Every major browser lets you block cookies wholesale, block only third-party cookies, delete cookies for a single site, or clear the lot. The menu paths below were accurate at the time of writing. Browsers reorganise their settings constantly, so if a label has moved, searching the settings page for "cookies" gets you there in one step.

Google Chrome

1. Open the three-dot menu and choose Settings.
2. Go to Privacy and security, then Third-party cookies.
3. Choose your blocking level, or open See all site data and permissions to manage individual sites.
4. To wipe this site alone, find donbet-australia.com in that list and hit the delete icon.

Safari

1. Open Safari, then Settings from the Safari menu.
2. Select the Privacy tab. Prevent cross-site tracking is on by default; leave it on.
3. Click Manage Website Data to see stored data per site.
4. Search for donbet-australia.com, select it and choose Remove, or use Remove All to clear everything.

Mozilla Firefox

1. Open the hamburger menu and choose Settings.
2. Select Privacy & Security and pick Standard, Strict or Custom protection.
3. Under Cookies and Site Data, click Manage Data to work site by site.
4. Clear Data wipes everything at once; Manage Exceptions lets you allow or block specific domains permanently.

Microsoft Edge

1. Open the three-dot menu and choose Settings.
2. Go to Cookies and site permissions, then Manage and delete cookies and site data.
3. Use See all cookies and site data to search for a specific domain.
4. Tracking prevention, in the Privacy, search and services section, offers Basic, Balanced and Strict modes.

One warning covers all four. A global block on every cookie breaks a great many websites, usually in ways that are hard to diagnose, because the site simply misbehaves instead of explaining itself. Blocking third-party cookies while allowing first-party ones is the setting most people actually want, and it costs almost nothing in day-to-day browsing.

Cookies on mobile devices

Phones run on the same principles with different menus, plus one extra layer worth understanding. The settings are also easier to lose track of, because half of them live in the operating system rather than in the browser you were using at the time.

On iOS, Safari's controls live in the system Settings app rather than inside the browser: Settings, then Apps, then Safari, where you will find Prevent Cross-Site Tracking, Block All Cookies and Clear History and Website Data. Other browsers on iOS keep their own separate settings, so clearing Safari leaves them untouched.

On Android, Chrome keeps its controls in-app under the three-dot menu, then Settings, then Site settings and Cookies. Samsung Internet and the other Android browsers each hide an equivalent under their own privacy settings.

Private or Incognito mode is the blunt instrument that works everywhere. Cookies set during a private session live in memory and get discarded when you close the window, so a private tab visits this site with no memory of any previous visit and leaves nothing behind. You will see the consent banner every single time, because the record of your last answer is thrown out with everything else. Plenty of readers share a device, common enough in this context, and a private window is the simplest way to keep your browsing off the device's history and storage. Worth adding: private mode hides your activity from other people using the device. It hides nothing from your internet provider or your employer's network.

What happens if you block cookies

Because nothing editorial on this site depends on cookies, blocking them costs you far less here than on a typical site. The full picture:

The headline: no article, table, figure or guide on this domain sits behind a cookie wall. Content is not gated on consent, the reading experience is not quietly degraded to punish a refusal, and the nagging stops at that one banner. Refuse everything optional and you get exactly the same site as somebody who accepted.

Do Not Track and Global Privacy Control

Two browser signals deserve a direct answer, because most cookie policies mention them and then manage to say nothing.

Do Not Track (DNT) was a header your browser could send to request no tracking. It failed, for the plain reason that it was voluntary and the industry declined to volunteer. Most browsers have since removed the setting. Where a DNT header does still arrive, we treat it as a refusal of analytics. Please do not rely on it, though. The standard is dead and almost nowhere else honours it.

Global Privacy Control (GPC) is the successor, and a genuine improvement: machine-readable, legally recognised in a growing number of jurisdictions, and supported natively or through an extension in several browsers. When a GPC signal reaches us we treat it as a valid opt-out of all non-essential cookies. You never have to touch the banner, and we will not prompt you to override it.

Neither signal affects strictly necessary cookies, which is standard practice: without the consent record there is nowhere to store the fact that you opted out. Neither one travels with you off this domain either. Follow a link to an operator's site and whether that site honours GPC is entirely its own business. Most gambling platforms do not.

Third-party services that may set cookies

Being straight about this matters more than keeping the list short. Two categories of external provider can result in storage landing on your device. They are described generically because providers get swapped, and a policy naming a specific product goes out of date the day we change one.

Content delivery network. The site is served through a CDN, so pages load quickly from a server near you and malicious traffic gets filtered before it reaches the origin. A CDN may set a strictly necessary cookie for routing, caching or bot mitigation. It sees the technical metadata of a request (IP address, URL, browser string) because it cannot deliver the page otherwise. It is not building an advertising profile out of your visit here.

Web analytics. Our measurement provider sets the analytics cookies described above, and only once you have accepted them. It receives page-view data and returns aggregate reports. We configure it that way and never use it to identify individual readers.

Both act as processors on our instructions, for the purpose we specify, under contract. Neither is free to repurpose the data. What is missing from the list tells you as much as what is on it: no advertising networks, no social embeds phoning home, no comment platforms, no tag managers pulling in unknown third parties, no chat widgets. Every script running on this site is there because we put it there for a reason we can explain, and the shorter that list stays, the less of your data ever leaves the page. Spot something on this domain that looks like an undisclosed tracker? Tell us and we will investigate it as a bug. The invitation to get in touch is genuine, and these reports do get acted on.

How long cookies live

Cookie lifespan splits cleanly in two. A session cookie has no expiry date and dies when you close the browser, existing only to hold state across a handful of page loads. A persistent cookie carries an explicit expiry date and survives restarts until that date passes or you delete it. Both are ordinary text files. The only difference is whether an expiry got written into them.

Nothing on this site sets a cookie with a multi-year expiry. Thirteen months is the ceiling, picked so that year-on-year comparison stays possible without keeping anything around longer than it earns its place.

Updates to this policy

This page changes when the site changes. Swap an infrastructure provider, adjust a lifespan, add or retire a script, and the policy gets updated alongside it, with the byline date moving to match.

Wording fixes and clarifications go in quietly, and the revised date serves as the notice. Anything material gets flagged on the site: a new category of cookie, a new third party, a genuinely new purpose for data we already hold. Where consent is the legal basis, we reset the banner and ask again rather than stretching your previous answer over something you never agreed to. We do not backdate. The version you are reading applies from the date shown, and continuing to use the site after an update indicates acceptance of it.

Contact

Questions about cookies, tracking or anything on this page go to [email protected]. That address also handles corrections, accessibility problems, security disclosures and privacy requests. There is no separate queue, which means fewer hops and a faster answer.

For something useful back on the first reply, tell us your browser and version, the page you were on, and what you actually saw. Screenshots help enormously with banner and consent issues, since a great many of them turn out to be a browser extension interfering rather than the site misbehaving.

What that inbox cannot help with, however the message is framed: anything involving a gambling account. Account access, deposits, withdrawals, bonus disputes, verification documents, self-exclusion at an operator. All of it sits outside our reach. We hold none of that data and have no access to any operator's systems. Those messages go to the operator's own 24/7 live chat and email support.

FAQ