Privacy policy
This guide explains how M9 works on a phone for readers in Australia aged 18 or older. The notes below cover what your device shares when these pages load, why we keep it and how you can switch it off.
Signals your phone sends
Every visit hands our server a few technical details: browser and operating system, screen width, a rough location worked out from your IP address, and the pages you open. We rely on them to confirm that tables and buttons render properly in portrait and landscape, and to count traffic in totals rather than person by person.
Nothing here asks you to open an account. We never request card numbers, PayID details, passwords or identity documents; those belong in the casino cashier, not in a reading guide.
Cookies and local storage
Your mobile browser may keep a few small files for us: one can remember choices such as a closed notice, others can measure visits without identifying you. Safari and Chrome both let you block or wipe them from their privacy menus, and every page still reads normally afterwards.
Notifications and outgoing links
We send no push alerts, and you will never see a prompt asking permission to show them. A Play now button hands you over to M9's own site in your browser; from there the operator's privacy rules cover whatever you type, and none of it reaches us.
How the data is protected
Pages load over an encrypted HTTPS connection, so a public Wi-Fi network at a café or airport cannot read what passes between your phone and this site. Access to our analytics is limited to the people who maintain the guide.
Keeping and removing data
Visit statistics are stored in summary form only for as long as they help us compare traffic, and then removed. You can ask what we hold about you, have it corrected or have it erased by writing to us through the contact details on this site, and we reply as soon as we reasonably can.
Readers under 18
These pages are not meant for anyone under 18. If we learn that a minor has contacted us, we delete the message and any details that came with it.
When this policy changes
If the way we handle data shifts, we rewrite this page, and whatever wording is published here when you read it is the wording that applies.
