Privacy Policy

What this static site does not collect

The website does not include account registration, login, deposit, withdrawal, checkout, payment-card, identity-verification, newsletter, or contact-form functionality. The site therefore does not collect payment data, player credentials, verification documents, banking details, or contact details through forms.

The website also does not include analytics scripts, advertising scripts, behavioural tracking code, social-media pixels, or affiliate-tracking scripts. No visitor profile is created by the current HTML and CSS alone.

Editorial purpose and separation from BigClash

BigClash Australia Guide publishes editorial information about BigClash for readers in Australia. It is separate from the casino operator. Reading an article on this site does not create a BigClash account, submit information to BigClash, or start a deposit or withdrawal through this website.

Where editorial pages discuss casino features, payments, verification, promotions, games, responsible gambling, or Australian regulatory context, those articles are informational. This website does not receive or control information that a reader may separately choose to provide to a casino, payment provider, regulator, or other third party.

Server logs after publication

Although the site does not collect personal information through its own features, a hosting provider may process routine server or security logs after the site is published. Depending on the hosting setup, those logs can include technical information such as an IP address, request time, requested URL, browser or device information, referrer information, and error or security events.

The exact log fields, retention period, legal basis, access controls, and hosting location depend on the hosting provider and configuration. Those details are not specified here because they are not exposed by the public website itself.

Cookies and local storage

The website does not set cookies by itself and does not include code that writes browser local storage or similar identifiers. The separate Cookie Policy explains this in more detail.

If analytics, advertising, consent-management tools, embedded media, affiliate tracking, account features, forms, or other technologies are added later, this privacy policy and the cookie policy would need to reflect that changed data handling.

External websites and reader choices

Editorial content may refer to external organisations or websites for context. Once a reader leaves this site, the privacy practices of the destination are controlled by that third party rather than by this static editorial site. Readers should review the privacy information provided by the relevant external service before submitting personal or financial information.

This site does not control the information practices of BigClash, payment providers, regulators, support services, or other external organisations. Any data submitted directly to those services is handled under their own policies and systems.

Children and gambling-related content

This website is an editorial about an age-restricted gambling service and is not intended as a service for children. The site does not include account-creation or gambling functionality. Any future additions to the site should remain appropriate for the legal and regulatory requirements that apply to gambling-related content.

Changes to the website

This policy describes the website as it currently operates. If analytics, advertising, forms, newsletters, affiliate tracking, consent tools, personalisation, user accounts, embedded third-party media, or another service that processes visitor information is added, the privacy position would change.

Material changes to hosting, retention practices, or third-party integrations may also change what needs to be disclosed. This privacy notice is intended to describe the website as it actually operates rather than a generic setup.

Privacy position of BigClash Australia Guide

BigClash Australia Guide is a static editorial website that does not create player accounts, process deposits or withdrawals, collect payment data, run contact or newsletter forms, or include analytics or tracking scripts. Hosting infrastructure may still produce ordinary server logs. If the site later adds technology that changes this position, the privacy information would need to reflect the new behaviour.