Privacy overview
The public MelSpin site separates product information from sensitive account data entry. Reading promotion, payment, game or mobile pages does not require identity documents or payment details.
Data categories
| Category | Examples | Player control |
|---|---|---|
| Account | Name, email, login settings | Keep details accurate. |
| Payment | Method ownership and transaction records | Use methods in your own name. |
| Device | Browser, session and security signals | Use private updated devices. |
| Support | Messages and account enquiries | Share only relevant details. |
Cookies and similar technologies
Cookies may support preferences, site performance and commercial routing. Browser settings can usually limit or clear cookies, although some site functions may become less convenient.
Affiliate routing
The site uses a start route for commercial actions. Public HTML, CSS, service files and schema do not contain the direct external destination.
Continue with privacy in mind
Use the official route only when you are comfortable proceeding from public information to account access.
Continue to MelSpinPublic-site privacy choices
Visitors can read MelSpin product pages without submitting account documents. The main public privacy choices are practical browser choices: whether to accept cookies, whether to continue through the start route, and whether to use a private device when moving into account access.
When personal data is requested inside the account environment, review the live notice attached to that action. Payment verification, identity review and support contact can each involve different data categories. Share only the information needed for the request and avoid sending passwords, card secrets or unrelated documents.
| Choice | Where it appears | Suggested action |
|---|---|---|
| Cookies | Browser and site preferences | Manage through browser controls. |
| Commercial route | Start page buttons | Continue only when ready for account access. |
| Identity documents | Live account verification | Upload only through official account screens. |
| Support messages | Contact or help channels | Keep the request focused and relevant. |
Sharing and verification
Data may be shared with payment providers, identity services, support tools or compliance partners when required for account operation. Live account notices provide the most specific details.
Security and account privacy
Privacy is connected to account security. Keep passwords private, use current contact details and avoid sending sensitive information through informal channels. If support asks for identity or payment evidence, use official account or support routes and submit only the requested documents.
Public pages can explain general categories, but account-specific privacy depends on the live action. A withdrawal review, bonus dispute or identity check may require different records. Read the message attached to the request before uploading anything, and keep copies of documents only where you can store them safely.
| Data moment | Why it appears | Safer habit |
|---|---|---|
| Login | Account access and session security | Use a private browser and strong password. |
| Cashier | Payment processing and ownership review | Use methods that match your identity. |
| Support | Issue resolution and account notes | Share only relevant details. |
| Responsible tools | Limits, breaks and account controls | Keep settings aligned with your budget. |
Retention and rights
Retention can depend on account status, legal requirements, security review and payment records. Australian visitors can use the listed contact details for privacy or account questions.
Cookie and routing examples
A preference cookie may remember a market selection, while an analytics signal may help understand whether public pages load correctly. Commercial routing is separate: public buttons use the start route, and the external destination is managed by the shared script rather than repeated across HTML files.
Players who want tighter control can clear cookies, use private browsing, or review browser permissions before moving into account access. These choices may make the site less convenient, but they can reduce stored browsing data on shared devices.
Account data requests
Inside the account environment, data requests should be read in context. A payment ownership check is different from a password recovery email, and a responsible gambling limit is different from a marketing preference. Use the official screen connected to the request and keep copies of submitted documents only in secure storage.
Contact details
Address: 80 Pyrmont St, Pyrmont NSW 2009, Australia. Phone: +61 29 657 1388.