Privacy Policy
This page explains what happens to information while you read our Class777 game library review. In short: we run no player accounts, take no payments and collect only what a working website needs.
Who is behind this site
This is an independent review of the Class777 catalogue: its pokies, live tables, scratchies, crash games and the cashier that sits around them. We are not the operator and have no access to your Class777 account. Nothing you do on these pages signs you up for anything at the casino.
What a visit leaves behind
Like almost every website, ours is served from a host that keeps routine technical logs: the IP address making the request, the browser and device type, the page requested and the time. We use those logs to keep pages loading, repair broken links in the game guides and filter out automated traffic. We make no attempt to tie them to a name or to build a profile of any reader.
Cookies on a review site
Reading a review needs no login, so there is no session cookie tied to you. Where cookies are used, they either keep the site working or count visits in total, for example how many readers open the pokies section compared with the live casino section. You can block or clear cookies in your browser and every page will still load.
Clicking through to Class777
Buttons and game tiles here lead to class777.co. Some of those links carry a referral tag that lets the operator see the visit came from us, which is how this site pays its way. From the moment you land on the casino's pages, its own privacy policy governs what happens, including anything you type in during registration, verification or a deposit.
Storage, sharing and deletion
We do not sell or rent information about readers. Technical logs are visible only to us and to the hosting company that stores them, and they are cleared on a rolling basis once they stop being useful for security or fault-finding. We would hand anything over only where the law required it.
Your choices
You can read every page with cookies switched off or in a private window. If you can give us the date and time of a visit, we can tell you what the logs hold about it. Should our handling of data change, say because a feature ever needs an account, this policy will be rewritten before that feature goes live.
