Most cookie policies are written to be survived rather than read. This one tries to answer the question people actually open it with: what exactly is this website putting on my device, how long does it stay there, and how do I get rid of it? None of that needs a law degree.
Last updated: 4 August 2026. A new tool, a different lifetime or an extra identifier in the storage described below would each move that date.
Before the detail, the outline. slot-rave-australia.com is a static guide with no login and no shopping basket, so the storage footprint is genuinely small: one local entry remembering that you dismissed the cookie notice, plus whatever the traffic measurement layer needs to count a visit. Nothing here follows you across the web, and nothing here can see inside a casino account. If you want the brand coverage rather than the plumbing, that lives on the SlotRave Casino Australia site homepage; this page is strictly about what happens in your browser while you read.
What a cookie actually is
A cookie is a small text file, usually a few hundred bytes and sometimes less, that a website asks your browser to save. The next time you request a page from the same site, your browser sends that file back automatically. That is the entire mechanism. It is not a program, it cannot run code, it cannot read your hard drive, it cannot switch on your camera and it cannot see files belonging to any other application.
Cookies exist because the web has no memory of its own. Each request your browser makes is a fresh introduction: the server has no way of knowing that the person asking for page four is the same person who asked for page three ninety seconds ago. A cookie is the sticky note that connects the two.
Every cookie carries a handful of properties, and knowing them makes the table in the next section readable:
- Name. The label the site uses to find it again, such as
_gaorsessionid. - Value. The stored content, usually a random string rather than anything meaningful to a human.
- Domain. Which site it belongs to. This determines whether it is a first-party cookie (set by the site in your address bar) or a third-party one (set by a different domain whose content is embedded in the page).
- Expiry. Either a fixed date, or "session", meaning it disappears when you close the browser.
- Flags. Technical switches such as
Secure, which stops the cookie being sent over an unencrypted connection, andSameSite, which limits when other sites can trigger it.
A cookie by itself is neutral. What makes one intrusive is scope: a first-party cookie counting your visit to a single site is a different object entirely from a third-party advertising cookie present on ten thousand sites, stitching together a behavioural profile across all of them.
What this site stores on your device
The full inventory. Two things deserve a note before you read it. The first is that our own consent record is not a cookie at all; it is a localStorage entry called sr_cookie, a technically different mechanism explained further down. The second is that the entries marked "analytics" are set by the measurement layer, and if you block that layer they never appear on your device at all.
| Name | Type | What it does | Lifetime | Party |
|---|---|---|---|---|
sr_cookie | localStorage entry (not a cookie) | Records that you dismissed the cookie notice, so the banner stops reappearing on every page you open | Until you clear site data — it has no expiry date of its own | First party |
| Analytics visitor identifier | First-party cookie | Distinguishes a returning reader from a new one so the traffic figures are not wildly inflated. A random string; it contains no name, email or account reference | Commonly up to 13 months, depending on the tool's configuration | First party |
| Analytics session identifier | First-party cookie | Groups the pages you open in one sitting into a single session, so five pages read in a row count as one visit rather than five | Typically 30 minutes of inactivity, or until the browser closes | First party |
| Analytics throttling flag | First-party cookie | Limits how often measurement requests are sent, reducing the load on your connection | A few minutes | First party |
| Host security cookie | First-party cookie | Set by the hosting or content-delivery layer to filter automated traffic and absorb attack patterns. Standard infrastructure hygiene rather than anything editorial | Session, or up to 30 days depending on the provider | First party (set by our infrastructure provider on our domain) |
| Advertising or retargeting cookies | — | None. No advertising pixel, no retargeting tag, no social widget and no cross-site audience script runs on these pages | Not applicable | Not applicable |
| Cookies from an embedded video or map | — | None. There are no embedded players, iframes or third-party widgets on this site, which is why no third-party cookie set appears in this table | Not applicable | Not applicable |
You do not have to take that on trust, and you should not. Open your browser's developer tools on this page (F12 on Windows, or Command-Option-I on a Mac), go to the Application or Storage panel, and look at what is listed under this domain. Everything present should match a row above. If you find something that does not, that is a genuine discrepancy and we want to hear about it, because a policy that misdescribes its own site is worthless.
Strictly necessary, analytics and marketing
Regulators, browsers and consent tools all sort cookies into roughly the same three buckets, under a handful of different names.
| Category | What it covers | Used here? | Can you refuse it? |
|---|---|---|---|
| Strictly necessary | Storage a site cannot function without: security filtering, load balancing, remembering a preference you actively expressed, keeping a logged-in session alive | Yes, minimally — the host security cookie and the sr_cookie consent flag | Yes, by clearing or blocking site data. Nothing on this site breaks if you do, because there is no session to lose |
| Analytics / performance | Counting visits, measuring which pages are read and where readers stop, in aggregate | Yes — the identifiers listed in the previous table | Yes. Browser settings, a content blocker or a private window all prevent it, and the site works identically without it |
| Marketing / advertising | Building a profile across multiple sites, retargeting you with adverts, measuring ad campaign conversions, sharing an audience with an ad network | No. None of it, on any page | Nothing to refuse |
| Personalisation | Reordering content, remembering preferences, showing different material to different readers | No. Every reader sees the same page — there is no A/B system and no dynamic content layer | Nothing to refuse |
The third and fourth rows are the ones worth pausing on. A large share of gambling-adjacent sites run a stack of advertising tags: a pixel from one network, a conversion tag from another, a social widget that phones home whether or not you click it. This site does not, and that is a design decision rather than an oversight. Fewer scripts means faster pages, fewer moving parts and a much shorter list of companies who learn that you were reading about pokie bonuses on a Tuesday night. If that ever changes, this table changes first and the date at the top changes with it.
localStorage and sessionStorage: related, but not cookies
The consent flag on this site is a localStorage entry, and the distinction matters enough to spend a paragraph on because it changes how you clear it.
Cookies are transmitted. Every cookie belonging to a domain is attached to every request your browser makes to that domain, which is a small tax on bandwidth and the reason cookies are capped at about 4KB. localStorage is not transmitted. It sits in your browser, the page reads it with JavaScript when it wants to, and the server never receives it unless the page deliberately sends it. Ours never does.
| Property | Cookie | localStorage | sessionStorage |
|---|---|---|---|
| Sent to the server automatically | Yes, on every request | No, never | No, never |
| Typical size limit | About 4KB | Around 5–10MB per site | Around 5–10MB per site |
| Survives closing the browser | Only if it has a future expiry date | Yes, indefinitely | No — cleared when the tab closes |
| Survives closing one tab | Yes | Yes | No; each tab has its own separate store |
| Readable by other sites | No — scoped to its own domain | No — scoped to its own origin | No — scoped to its own origin |
| Used on this site | Analytics and host security only | Yes: the single sr_cookie consent flag | No |
The practical consequence is a trap people fall into regularly. Deleting cookies alone does not remove sr_cookie, because it is not a cookie. You need to clear site data or local storage specifically. In Chrome that means "Cookies and other site data" rather than just cookies; in Safari it is "Manage Website Data"; in Firefox it is "Cookies and Site Data". Clear only the cookie list and the consent notice will stay dismissed, which puzzles people who have just spent five minutes trying to make it reappear.
Third-party cookies and what happens when you follow a link out
No third-party cookies are set while you are on this domain. The interesting moment is the one immediately after you leave it.
When you click an outbound link, whether to the casino, a game studio or a help service, you make a fresh request to a different company's server. From that instant, this policy no longer applies to anything happening in your browser. The destination sets its own storage under its own rules, shows its own consent notice if it uses one, and answers to its own privacy documentation. Nothing we have written obliges them to behave in any particular way, and we have no visibility into what they store.
What can be said with confidence is what the click does not carry. No list of the pages you read here goes with it, no identifier ties your reading history to a casino session, and your email address cannot travel because we do not have one. From the destination's side an outbound click looks like an ordinary web visit with a referring page attached, which is the same information it would receive from any link on any site.
Storage on this site and your casino account never touch
The analytics identifier in your browser has no connection to any account you hold with the operator. The two systems share no key, no login, no database and no lookup. If you want the boundary drawn from the other direction, meaning what the operator collects and how long it keeps it, that is set out in the notes on how personal information is handled under the Privacy Act, and in the operator's own policy, which is the document that governs your account.
One habit worth adopting regardless of which site you are on: check what the destination's consent notice actually offers. A "reject all" button that leaves twenty advertising cookies in place is common, and the developer tools trick described earlier works just as well on somebody else's site as it does on ours.
Managing cookies in your browser
Every browser lets you view, delete and block storage. The controls are buried at slightly different depths, so here are the current routes on desktop and on mobile.
| Browser | Where the setting lives | What you can do there |
|---|---|---|
| Chrome (Windows / macOS) | Settings → Privacy and security → Third-party cookies, and Settings → Privacy and security → Delete browsing data | Block third-party cookies entirely, clear existing data by time range, or add per-site rules that always block or always allow |
| Chrome (Android) | Tap the three dots → Settings → Site settings → Cookies; delete via Settings → Privacy and security → Delete browsing data | Same blocking options as desktop, plus per-site exceptions |
| Safari (macOS) | Safari → Settings → Privacy, then "Manage Website Data" for the per-site list | Block all cookies, remove data for one site, or clear everything at once. Intelligent Tracking Prevention is on by default |
| Safari (iPhone / iPad) | The iOS Settings app → Safari → Block All Cookies, or Safari → Advanced → Website Data | Note this lives in the system Settings app, not inside Safari itself — the single most common reason people cannot find it |
| Firefox (desktop) | Settings → Privacy & Security → Enhanced Tracking Protection, plus Cookies and Site Data | Choose Standard, Strict or Custom protection; clear data on every close; manage exceptions per site |
| Firefox (Android / iOS) | Menu → Settings → Enhanced Tracking Protection, and Delete browsing data | Strict mode blocks most cross-site trackers; optional automatic deletion when you quit |
| Edge | Settings → Cookies and site permissions → Manage and delete cookies and site data | Block third-party cookies, clear on close, set per-site allow and block lists |
| Samsung Internet | Menu → Settings → Sites and downloads → Cookies, plus Personal browsing data | Block cookies, clear storage, enable Smart Anti-Tracking |
Menu labels shift between versions, so treat the paths above as a strong hint rather than a permanent map. Two shortcuts survive most updates: on desktop, Control-Shift-Delete (or Command-Shift-Delete on macOS) opens the clear-data dialog in Chrome, Firefox and Edge; and clicking the padlock or tune icon at the left of the address bar shows what the current page has stored, usually with a one-click way to remove it.
Blocking storage on this site costs you nothing functional. Every guide, table and comparison renders identically with all cookies refused. That is not true everywhere. The operator's platform genuinely needs session cookies to keep you logged in, and blocking them there breaks the login rather than merely annoying it. The same applies to the installable version of the casino covered under the SlotRave PWA and what it keeps on your phone, which relies on browser storage to hold its session between launches.
Private browsing and blockers: what actually changes
Incognito mode is widely misunderstood, so here is the accurate version.
A private window gives you a fresh, empty storage container. Cookies set inside it work normally for the length of the session, and when you close the last private window the whole container is discarded, taking cookies, localStorage, history and cached files with it. What it does not do is make you invisible. Your IP address is unchanged, so the site still sees a request from your connection. Your network operator, employer or school can still see which domains you contacted. The site itself still counts the visit; it simply counts it as a brand-new reader every time, because the identifier from your last session was thrown away.
Content blockers work differently and, for the specific goal of not being measured, work better. An extension such as uBlock Origin, or a browser with tracker blocking built in, stops the analytics script from loading at all: no request, no cookie, no measurement event. On this site that means your visit is invisible to the analytics dashboard entirely, and the pages still render exactly as intended because nothing visual depends on that script.
| Approach | Stops analytics counting you | Hides your IP address | Effect on reading this site |
|---|---|---|---|
| Private / incognito window | Partly — you are counted as a new reader each session | No | None; everything works |
| Blocking cookies in settings | Partly — measurement may still register a hit | No | None |
| Content blocker or tracker-blocking browser | Yes, completely | No | None |
| VPN | No | Yes, replaces it with the VPN's address | None, though a non-Australian exit may look odd in aggregate geography |
| Clearing site data afterwards | Retrospectively resets your identifier | No | The cookie notice reappears on your next visit |
Do Not Track and Global Privacy Control
Two browser signals attempt to express a privacy preference automatically, and they have had very different fortunes.
Do Not Track (DNT) was a header added to browser requests from around 2011, asking sites not to track the visitor. It failed for a structural reason: nothing obliged anyone to honour it, and most large ad networks simply did not. Browsers have been quietly removing the setting since. If your browser still sends DNT, this site does nothing that would contradict it, since there is no cross-site tracking here to switch off. Treating DNT as meaningful protection anywhere else on the web would still be a mistake.
Global Privacy Control (GPC) is the more serious successor. It is a signal your browser or extension sends expressing an opt-out of the sale or sharing of personal information, and unlike DNT it has legal weight in some jurisdictions. We do not sell or share reader data with anyone, so a GPC signal reaching this site asks us to stop doing something we were never doing. It is honoured by default and by design.
Neither signal reaches the operator's platform through us, and neither has any effect on what a casino does with account data. If that is your concern, the controls that matter are inside the account itself, alongside the deposit caps and reality checks described under the self-exclusion and limit tools worth knowing about.
What breaks if you block everything
An honest answer, split by site type, because the claim that a site cannot run without cookies is usually an overstatement and occasionally true.
On this site: nothing. Block every cookie, clear all storage, run a blocker in strict mode, and every page still loads with its tables and internal links intact. The only visible consequence is that the cookie notice greets you on each visit, because the flag recording your dismissal is exactly the thing you deleted. Slightly irritating and entirely harmless. If you find any other broken behaviour, that is a bug worth reporting rather than a policy position.
On the casino platform: quite a lot. A gambling account is a stateful thing. Session cookies keep you logged in between pages; blocking them typically means being ejected at every navigation, or being unable to sign in at all. Deposit flows bounce through payment providers that use cookies to maintain the transaction. Some responsible-gambling settings and session timers depend on browser storage to work correctly. Blocking storage there is not a privacy win so much as a functional wall.
- Login sessions that drop on every click, or refuse to establish in the first place.
- Deposit and withdrawal flows that fail partway through a redirect to a payment provider.
- Session timers and reality-check prompts that lose their state and stop firing.
- Bonus claims that do not register because the promotional state was held in the browser.
- Live dealer tables that fail to reconnect after a network interruption.
The workable middle ground for most people: block third-party cookies globally, allow first-party cookies, and add an exception only for the platforms where you genuinely need a session to persist. That configuration removes cross-site tracking, which is the part worth removing, while leaving ordinary site functionality intact.
Withdrawing consent on this site
Consent here is a one-bit affair, which makes withdrawing it straightforward.
- Clear the site's data. Open the padlock or tune icon in the address bar while on this domain, choose the option to clear or reset site data, and both
sr_cookieand any analytics cookies for this domain are removed. The notice will reappear on your next visit, which is the confirmation that it worked. - Block the domain outright. Add slot-rave-australia.com to your browser's block list for cookies. The pages continue to work; nothing further is stored.
- Install a content blocker. The most complete option, because it prevents the measurement script from loading at all rather than deleting its traces afterwards.
- Use a private window. Everything is discarded when you close it, with no manual clearing required.
- Write to us. If you want a request recorded formally, email the address at the bottom of this page. Be aware that we cannot reach into your browser to delete a localStorage entry. That action is yours alone by design, since the entry never leaves your device.
There is deliberately no account-based preference centre here, because building one would require creating exactly the kind of persistent reader record this site does not keep. A consent tool that stores your preferences on a server, keyed to an identifier, collects more about you than the storage it claims to be managing. The trade is not worth it at this scale.
Changes to this policy
Storage changes when tooling changes. If we add a measurement tool, swap providers, alter a retention period or introduce any category not listed above, this page is updated before the change goes live rather than after, and the date at the top moves accordingly.
There is no notification list to join, and nobody is emailed about a cookie policy revision, because no reader addresses are held for that purpose. A new third-party script, a new category of cookie, or a lifetime extended significantly would each get a short dated note here spelling out what changed, left up long enough to be read.
How this page is maintained and why it carries a review date at all is described alongside the rest of the editorial process on the page covering the people who maintain and date this guide. The wider rules covering use of the site sit separately in the rules that apply to reading these pages.
Contact
Send questions about any of this to [email protected]. Useful things to include: which browser and version you are using, what you found in the storage panel, and what you expected to find instead. A screenshot of the developer tools view is worth several paragraphs of description.
Two kinds of message we cannot help with, flagged early to save you the wait. The first is a request to delete something from your own device, since browser storage is under your control rather than ours and the steps above are genuinely the whole answer. The second is anything concerning cookies, sessions or logins on the casino platform, which belongs to the operator's support desk; we have no access to that system and no ability to inspect what it stores.
Everything else is fair game, and a discrepancy between this page and what your browser actually shows is the report we most want to receive.