This notice explains what slot-rave-australia.com knows about you, how it came to know it, and what you can make us do about it. It covers one website, this one, and it stops at the edge of the domain. The moment you click through to a casino, a different company with a different policy takes over, and nothing written here binds them.
Last updated: 4 August 2026. Every revision resets that line, so it tells you which version of this notice you have in front of you. Copies held anywhere else may be out of date.
We publish a guide. We do not run a casino, a payment gateway or an account system. That single fact shapes the whole of this SlotRave privacy policy: the volume of personal information involved in reading a static guide is genuinely small, and pretending otherwise would be theatre. If you arrived from the brand overview at SlotRave Casino Australia, hold onto the contrast. That page describes an operator collecting identity documents and bank details. This one describes a website whose usual haul is a server log line.
What this policy governs
Scope first, because almost every privacy question that reaches our inbox is aimed at the wrong company.
This document applies to slot-rave-australia.com and to the email address published at the bottom of it. It covers what happens while you are reading these pages and what happens if you write to us. It applies whether you arrive from a search result, a bookmark, a forum link or a shared message, and whether you read on a laptop, a phone or a screen reader.
It does not apply to your casino account. If you have registered with the operator, TechSolutions Group N.V., running under a Curaçao licence, then the operator holds your name, date of birth, address, payment credentials, identity documents and complete betting history. We hold none of that, cannot see any of it, and cannot amend or delete a single field of it on your behalf. Requests to erase a casino account, unsubscribe from operator marketing or recall a verification document have to go to the operator's own support desk. Sending them here achieves nothing except a delay.
Two documents sit close to this one and are worth reading alongside it. The first sets out what is stored on your device rather than on a server, covered in detail on the page describing which cookies this site sets and how long they last. The second is the site usage agreement that sits alongside this notice, which governs what you may do with the content rather than what we do with your data.
What personal information we collect
The complete list sits in one table below, with nothing held back for a summary somewhere else.
| Category | Example | How it reaches us | Why it exists |
|---|---|---|---|
| Technical connection data | IP address, browser and version, operating system, screen dimensions, referring URL, timestamp of the request | Sent automatically by your browser to the web server on every page request — this is how the web works, not a choice either of us made | Serving the page, diagnosing errors, blocking automated abuse and scraping |
| Approximate location | Country, and sometimes state or city — "Queensland, Australia" rather than a street | Derived from the IP address by the analytics layer; never from device GPS, which we do not request | Confirming the guide is reaching an Australian audience and deciding which payment rails to prioritise in our coverage |
| Page interaction data | Which URLs were opened, in what order, how long each was on screen, whether an outbound link was clicked | Recorded by the analytics layer while you browse | Working out which guides are useful and which sections readers abandon halfway down |
| Local consent flag | A single stored value, sr_cookie, recording that you dismissed the cookie notice | Written by your own browser into its local storage; never transmitted to us | Stopping the notice reappearing on every page load |
| Correspondence | Your email address, your name if you sign one, and whatever you choose to write | Only if you email [email protected] yourself | Reading your message and replying to it |
| Server access logs | Standard host-level log lines: IP, request path, response code, bytes served, user agent | Generated by the hosting infrastructure automatically | Security, uptime monitoring and abuse investigation |
Two characteristics of that list matter more than its contents. First, there is no account. This site has no registration, no login, no profile and no password field, so there is no persistent record with your name attached to it. Second, everything except the correspondence row arrives passively. You are never asked to type personal information into this website, because there is nowhere to type it.
Is an IP address personal information? Under Australian law it can be, depending on whether the person holding it can reasonably identify you from it. We treat it as though it is, which is the cautious reading and the one that produces better behaviour. That means IP data stays in short-retention logs, is not used to build a profile, and is never combined with anything else to work out who a particular reader is.
What we deliberately do not collect
This section exists because the gambling sector has trained people to expect intrusive data collection, and it is worth being explicit about the things that are simply absent here.
- No payment details. No card numbers, no expiry dates, no CVVs, no bank account or BSB numbers, no PayID identifiers, no crypto wallet addresses. This site has no cashier, no checkout and no payment processor. There is nothing here that could take a payment even if someone tried to make one.
- No identity documents. No passport or driver licence scans, no Medicare cards, no selfies, no proof-of-address utility bills. Those belong to the operator's verification process, and what the operator's identity checks collect is a separate subject with a separate page. None of it passes through us.
- No gambling history. Not a single spin, stake, win, loss, deposit, withdrawal or bonus claim of yours is visible to this site. We have no feed from the casino, no reporting dashboard and no player-level access of any kind.
- No account credentials. We never ask for a casino username or password, and we will never email to request one. Anyone who does is not us, regardless of what the sender address appears to say.
- No sensitive information in the statutory sense: health data, racial or ethnic origin, political opinions, religious beliefs, sexual orientation, criminal record, biometric or genetic data. None of it is requested, and none of it is inferred.
- No sold or brokered data. Reader data is not sold, rented, licensed, traded or supplied to data brokers, list builders or advertising networks. There is no commercial arrangement of that kind and there will not be one.
Two companies, two privacy obligations
If you register at the casino, you enter a second and much larger data relationship. That one is governed by the operator's own privacy policy, its own retention schedule and the rules of its licensing jurisdiction. Read that document before you upload a single identity file. It decides how long your passport scan sits on somebody's server, and no undertaking we give here has any effect on it.
Legal bases and purposes for handling your information
Australian privacy law does not use the "legal basis" framework that European law does. The Privacy Act 1988 (Cth) and the Australian Privacy Principles work on purpose limitation instead: information may be collected where it is reasonably necessary for a function or activity, and it must then be used for the purpose it was collected for, or for a directly related purpose you would reasonably expect. We set out both frameworks below because a share of readers are covered by each.
| What we do | Purpose under the APPs | Equivalent GDPR basis |
|---|---|---|
| Serve pages and keep the site online | Reasonably necessary to deliver the website you asked for | Legitimate interests |
| Keep security and access logs | Protecting the site against attack, scraping and fraud | Legitimate interests |
| Measure aggregate traffic | Improving and prioritising the content we publish | Consent where the measurement uses cookies; legitimate interests for aggregate server-side counts |
| Remember your cookie-notice choice | Directly related to giving effect to a preference you expressed | Necessary for a service you explicitly requested |
| Reply to your email | You contacted us and expect an answer | Legitimate interests, and consent by the act of writing |
The gaps in that table say as much as the rows do. There is no row for advertising profiles, no row for cross-site tracking, no row for lookalike audience building and no row for enriching reader records with data bought elsewhere. Those activities do not happen on this domain, which is why no basis is claimed for them.
Analytics and traffic measurement
We measure readership, and the detail matters here, because "we use analytics" is the phrase most sites reach for when they would rather not say anything.
What the analytics layer produces are aggregate reports. A typical view tells us that a page received a certain number of sessions in a week, that most arrived from organic search, that a majority read on mobile, that the median time on the page was some number of seconds, and that a proportion of readers went on to open a second page. Those numbers describe a crowd. They do not resolve to individuals, and we have no interface that would let us look up one reader's path even if we wanted to.
| Metric we can see | What it looks like in practice | What it cannot reveal |
|---|---|---|
| Sessions and pageviews | "The withdrawals guide had roughly 1,400 sessions last month" | Which specific people opened it |
| Traffic source | "Most arrivals came from search; a smaller share from direct visits" | The exact search phrase for every visitor — search engines withhold that |
| Device and browser mix | "Around two thirds mobile, mostly Chrome and Safari" | Your device identifier or any hardware fingerprint we could re-recognise |
| Geography | Country and broad region, weighted heavily to Australia | Street-level location, home address or GPS position |
| Scroll depth and dwell time | "Half of readers stop before the bonus maths section" | What you typed, what you copied, or anything outside this site |
| Outbound clicks | A count of clicks on links leaving the domain | What you did after you left — that visibility ends at our boundary |
The practical use is unglamorous. If half of readers abandon a page at the same point, the section is written badly and gets rewritten. If a comparison table gets read to the bottom on mobile, it stays. That is the entire purpose of measurement here: deciding what to fix. The reasoning behind those editorial decisions is set out further in the notes on the editorial team behind this SlotRave guide.
If you would rather not be counted at all, that is achievable and the methods are covered in the cookie documentation. Browser controls, tracker blockers and private windows all work, and none of them degrade your ability to read anything published here.
Who your information is shared with
The list of recipients runs to three, and it stops there.
The hosting provider. Every website runs on somebody's infrastructure, and that infrastructure necessarily processes the connection data described above, since it cannot deliver a page to you without knowing where to send it. The host acts on our instructions, keeps standard logs, and does not use reader data for its own purposes.
The analytics provider. The measurement layer processes page interaction data to produce the aggregate reports described in the previous section. It works as a processor under contract, not as an owner of the data.
Anyone the law compels. If a valid legal demand arrives (a court order, a statutory notice, a lawful request from an Australian regulator or law enforcement body), we comply with what it requires and nothing more. For ordinary readers this has no bearing at all, since the material available to hand over amounts to short-lived log lines.
What does not happen: no sale of data, no rental of lists, no sharing with advertising exchanges, no transfer to the casino operator. To be blunt about the last one, since it is the question people actually want answered: clicking an outbound link on this site does not send the operator your reading history, your email address or a dossier of the pages you looked at. The operator sees an ordinary web visit, exactly as it would if you had typed its address into your browser bar yourself.
How long we keep things
The Australian Privacy Principles require that personal information be destroyed or de-identified once it is no longer needed for the purpose it was collected for. Indefinite retention "just in case" is not a purpose, so nothing here is held on that basis.
| Type of data | Retention period | What happens afterwards |
|---|---|---|
| Server access logs (IP, request path, user agent) | Up to 30 days in the ordinary course | Overwritten by log rotation; nothing is archived to long-term storage |
| Aggregate analytics reports | Up to 26 months | Retained only as totals and averages with no individual-level records behind them |
| Individual-level analytics events | Short-lived; typically weeks rather than months | Aggregated into the totals above, then discarded |
The sr_cookie consent flag | Until you clear your browser storage | Never leaves your device, so we cannot delete it for you — clearing site data removes it instantly |
| Email correspondence | Up to 24 months from the last message in the thread | Deleted from the mailbox, or sooner if you ask us to remove it |
| Security records of blocked abuse | Up to 12 months | Deleted; kept only where an incident is unresolved |
One caveat worth stating plainly: a log line that has already been overwritten cannot be produced later. If you ask for access to data that has passed its retention window, the honest answer will be that there is nothing left to give you, and that is a feature of short retention rather than an evasion.
Your rights under the Australian Privacy Principles
The APPs give you enforceable rights over information about you. Here is each right that realistically applies to a website like this one, and the exact route to using it.
| Right | What it means here | How to exercise it |
|---|---|---|
| Access (APP 12) | Ask what personal information we hold about you and receive a copy | Email us with enough detail to locate it — the approximate date of your visit and the IP address you were using, if you know it |
| Correction (APP 13) | Have inaccurate, out-of-date or misleading information corrected | Email us describing the error; in practice this applies almost exclusively to details inside correspondence |
| Deletion | Have your correspondence and any associated records removed | Reply to the thread asking for deletion, or write fresh naming the address you used |
| Anonymity (APP 2) | Deal with us without identifying yourself | Already the default — reading requires no identification at all, and you can email from an address that names nobody |
| Opt out of measurement | Stop your visit being counted in analytics | Use browser settings, a content blocker or a private window, as set out in the cookie documentation |
| Complain (APP 12.9) | Raise a formal complaint about how we handled your information | Email us first with "privacy complaint" in the subject line; escalate to the OAIC if unsatisfied |
Our service standard: acknowledgement within two business days, substantive answer within 30 days, which is the timeframe the Privacy Act sets for access requests. Access and correction are free. There is no verification hoop to jump through in most cases, because there is no account to verify against. Where a request would reveal information about somebody else, though, we will ask for enough detail to be confident the data is yours before releasing anything.
If we get it wrong. Complain to us first; it is faster and we can usually fix the problem the same week. If our response does not satisfy you, the Office of the Australian Information Commissioner accepts privacy complaints from the public and can investigate. The OAIC will normally expect you to have raised the matter with us and given us a reasonable chance to respond before it takes the complaint on. Its details are published at oaic.gov.au, and nothing in this policy limits your right to go there.
Readers in the European Union
Most of this audience is Australian, but a share of readers open these pages from Europe, and the General Data Protection Regulation may apply to them. The short version: the same minimal data handling described above, with a few additional rights layered on top.
- Access, rectification and erasure. The European equivalents of the Australian rights above, exercised through the same email address.
- Restriction and objection. You can object to processing carried out on a legitimate interests basis, including analytics measurement. Say so and we will exclude what can be excluded.
- Portability. A copy of what we hold in a machine-readable format. Given the volume involved, this is usually a short text file.
- Withdrawal of consent. Where processing rests on consent, withdrawing it is as easy as giving it, and clearing site data does most of the work instantly.
- Complaint to a supervisory authority. You can lodge a complaint with the data protection authority in your own country, in addition to or instead of contacting us.
Nothing on this site is directed at the European market. The currency is Australian dollars, the payment rails are Australian and the regulatory commentary addresses Australian law. A right does not disappear because a page was written for somebody else, though, so we honour these requests when they arrive.
Children and the 18+ requirement
This site is for adults. Every Australian state and territory sets the legal gambling age at 18, and that is the floor for reading these pages too.
We do not knowingly collect information from anyone under 18, and we do not market to minors. No content here is styled, illustrated or written to appeal to children. If we became aware that a minor had sent us personal information by email, we would delete it rather than reply.
Age verification on a public web page is not technically possible in any meaningful sense, so we do not pretend to perform it. What we can do is state the rule clearly and repeat it where it matters. Parents and guardians concerned about gambling content reaching a young person should look at device-level filtering software, which works where a website's self-declared age gate does not, and at the family-focused material published by Australian gambling help services.
Cross-border disclosure of information
Web infrastructure is global, and honesty requires saying so. The servers delivering this site, and the analytics layer measuring it, may be located outside Australia, commonly in Europe, Singapore or the United States, depending on the provider's network. Content delivery caching means a page may also be served from an edge node in a country you did not expect.
Australian Privacy Principle 8 governs this situation. Where personal information is disclosed to an overseas recipient, the disclosing entity must take reasonable steps to ensure the recipient handles it consistently with the APPs, and in general remains accountable for what that recipient does with it. Our approach to meeting that obligation is to use established providers with published privacy commitments and contractual data-protection terms, to keep the volume of information crossing any border as small as possible, and to hold nothing offshore that is not already covered by the short retention periods above.
What actually crosses a border is a connection log line and an analytics event. A payment record, an identity document or a gambling history never crosses one, because none of them exist here to begin with.
How the information is protected
APP 11 requires reasonable steps to protect personal information from misuse, interference, loss and unauthorised access. Concretely, that means the following on this site.
- Encrypted transport. The whole site is served over HTTPS, so the pages you request and the data your browser sends cannot be read in transit by whoever operates the network you are on.
- A minimal attack surface. The site is static. There is no login, no user database, no comment system, no file upload and no form submission, which removes the majority of the routes by which reader data typically leaks from a website.
- Data minimisation as the primary control. The most reliable protection for a piece of personal information is not holding it. That principle is doing most of the security work here.
- Restricted access. Server logs and analytics dashboards are reachable only by the people who maintain the site, through authenticated accounts.
- Short retention. Data that has been rotated out of the logs cannot be stolen in a breach, because it no longer exists.
No system is beyond compromise, and any policy claiming otherwise is overstating its case. If a breach occurred that was likely to result in serious harm to an identifiable person, the Notifiable Data Breaches scheme under the Privacy Act would require notification to affected individuals and to the OAIC, and we would meet that obligation. Given the categories of data described in this notice, the realistic worst case is exposure of short-lived connection logs rather than anything that could be used to impersonate or defraud a reader. The obligation stands regardless of how likely the scenario is.
Changes to this policy
This page will be revised, most likely because a provider gets swapped out or the law moves underneath it.
When that happens, the "last updated" date at the top changes with it. There is no mailing list for privacy updates, because there is nobody on file to notify: no account, no subscriber list, no stored addresses beyond live correspondence. Anyone tracking this page will have to come back and read the date.
A material change means a new category of collection, a new recipient, or a longer retention period. Those get a dated note on this page setting out exactly what moved. Minor edits, such as a corrected address or a clearer sentence, are covered by the updated date alone. What will not happen is a silent expansion of collection dressed up as a formatting tidy.
How to contact us
Privacy correspondence goes to [email protected]. Access requests, corrections, deletions, objections, complaints and general questions about this notice all land in the same mailbox, and there is no autoresponder sitting in front of it.
Tell us which right you are exercising, give us enough detail to find the data (dates, the address you emailed from, the IP you were using if you know it), and say what outcome you want. Requests aimed at the casino get redirected to the operator with an explanation, which costs you days you may not have if a payout is sitting in the balance.
Two final signposts. If your concern is less about data and more about the amount of time or money a gambling habit is taking, the relevant material sits on the page covering gambling help services and account limits for Australians, including the national helplines that operate around the clock. And if a statement on this page does not match what you see happening in your own browser, tell us. A privacy notice that describes a site incorrectly is worse than no notice at all, and we would rather rewrite a paragraph than defend one.