Independent Australian consumer reference
Privacy practices for this CrownPlay reference
This notice describes limited technical processing, visitor choices, retention principles, and contact rights for this publication.
Evidence status: primary records checked 18 July 2026; unresolved claims are identified.
Dated primary evidence
: ACMA's NovaForge formal warning (PDF) says NovaForge Ltd provided the CrownPlay service through crownplay2418.com and crownplay6.com. ACMA found contraventions of subsections 15(2A) and 15AA(3) of the Interactive Gambling Act 2001 involving prohibited and unlicensed regulated interactive gambling services supplied to customers physically present in Australia.
: ACMA's enforcement report records CrownPlay and related domain disruption activity. The current investigations register lists CrownPlay among prohibited services. ACMA also explains the rules for affiliate services; the Interactive Gambling Act 2001 is the legislation source.
: CrownPlay is not licensed to provide online casino services in Australia. We could not verify the current operator as of 18 July 2026. We could not verify a current foreign licence as of 18 July 2026. These limits do not establish who controls every similarly named domain.
Practical procedure
Read the site without submitting personal information wherever possible. Routine hosting systems may process the IP address, request time, requested path, browser information, security events and similar technical records needed to deliver and protect the publication. Do not email passwords, one-time codes, complete bank statements, identity documents or detailed gambling histories. For a correction, provide a page address and authoritative source, redact unrelated details and use a fresh working copy rather than altering the original evidence. A privacy request should identify the contact address used and the specific action requested, but the publisher may need enough information to avoid disclosing data to the wrong person. External government and support links apply their own notices once opened. Browser controls can clear local history or restrict storage, but they do not delete a request already logged by a hosting provider.
Data not requested by the static publication
The public pages do not require a player account, deposit, gambling profile or identity verification. The publisher does not need an operator password, one-time banking code, passport, driver licence, selfie or complete statement to explain a correction. Avoid placing sensitive material in a URL, subject line or ordinary email. If a future form requests data, its purpose and handling should be explained at the point of collection rather than inferred from this notice.
Routine technical processing
Hosting, content delivery and security services may process technical request data such as an IP address, timestamp, requested path, response status, user agent and indicators of abusive traffic. These records help deliver pages, diagnose faults and protect availability. The publisher follows a minimisation principle and does not describe an exact retention period unless it can be verified for the active provider. Security, legal or operational needs may require different periods, after which records should be deleted or de-identified when no longer needed.
External links and visitor choices
Links to ACMA, legislation, Gambling Help Online, BetStop and Lifeline leave this publication. The destination controls its own logs, cookies, forms and privacy notice. Opening a support link can be important, so privacy concerns should not delay emergency help. Visitors can use browser privacy settings, clear history, block optional storage or open official resources directly. Those choices affect the device and browser but cannot guarantee anonymity from an internet provider, destination service or hosting security log.
Requests, corrections and sensitive evidence
A person may ask a privacy question or request correction or deletion of personal information held by the publisher, subject to applicable law and the need to verify the request proportionately. Describe the data and context rather than sending more sensitive proof than necessary. Editorial evidence may sometimes need to be retained to document a correction, legal obligation or abuse report, but unrelated personal details should be removed. The contact channel is not designed for operator disputes, financial records or urgent support, and forwarding such material can create avoidable exposure without producing a remedy.
Data handling decisions and incident response
Access to submitted personal information is limited to the people and service providers who need it for publication, security, legal compliance or the specific request. A service provider may process data under its own infrastructure terms, so the publisher should not promise storage locations or controls it cannot verify. Information is not sold as a CrownPlay lead and is not shared with an operator to pursue registration, deposits or account activity. If the publisher becomes aware of unauthorised access, it should contain the issue, determine what information and people are affected, preserve necessary security evidence and make notifications required by applicable law. A person reporting a possible incident should identify the page, message date and type of data without emailing another copy of the exposed document. Privacy rights can include access, correction, deletion or complaint rights depending on the law and context, but exceptions may apply for security, legal claims and required records. The publisher responds on the verified facts and does not promise a result before understanding the request. Children should not submit gambling or identity information to this publication. Anyone helping another person should avoid disclosing that person's history without authority. Data minimisation remains the central protection: if an editorial point can be proved with a public source, no private document should be collected at all.
| Context | Possible data | Safer visitor practice |
|---|---|---|
| Page request | IP address, time, path, user agent and security signals | Use browser controls and avoid sensitive URL parameters |
| Editorial correction | Contact details and submitted source material | Redact unrelated personal and financial data |
| External official link | Data described by the destination's notice | Open the official address directly and review its notice |
| Privacy request | Request details and proportionate verification | Describe the data precisely without oversharing |
Frequently asked questions
Do I need an account to read this site?
No. The static public pages do not require a player account or identity verification.
What technical data may hosting systems process?
They may process IP addresses, timestamps, requested paths, user agents, response information and security signals.
Does the publisher set a guaranteed log retention period?
No exact period is claimed here; retention should be limited to verified operational, security and legal needs.
Should I email an identity document for a correction?
No. Use a redacted source that supports the correction without exposing unnecessary identity data.
What happens when I open an external link?
The destination service applies its own logging, cookie, form and privacy practices.
Can browser settings erase hosting logs?
No. Browser controls affect the local device and optional storage, not records already processed by a host or destination.
How do I make a privacy request?
Identify the relevant data, contact context and requested action while providing only proportionate verification.
Can I send bank records through the contact route?
Do not send complete statements. Redact unrelated details and contact the financial institution directly for a dispute.
General information only; this publication is not CrownPlay and does not provide legal or financial advice.