PRIVACY POLICY
A transparent inventory of the data this build uses
Privacy statements should describe the actual code and services in use. They should not promise controls that the project owner has not verified.
SUPPLIED WEBSITE FILES
No analytics, advertising pixels, accounts or forms
As reviewed on 11 August 2026, this static build does not include analytics tags, advertising pixels, first-party account registration, comments, newsletter collection, contact-form submission or document uploads. Its JavaScript controls navigation, table-of-contents state and FAQ disclosure only.
The site does not intentionally set a first-party cookie or use browser storage in the supplied code.
INFRASTRUCTURE
Hosting and network providers may process technical logs
A web host, content-delivery network, domain provider or security service may process IP addresses, request times, requested URLs, user-agent data and security events to deliver and protect the site. Those systems are outside the supplied static files.
The project owner must identify the actual providers, retention periods and applicable agreements before making a complete organisation-level privacy statement.
EXTERNAL WEBSITES
Official sources and operator links have their own privacy practices
WagerMark links to ACMA, legislation, BetStop, Gambling Help Online and third-party operator sites. Following a link sends a request to that organisation, which may process data under its own policy. Operator CTAs use sponsored/nofollow attributes, but WagerMark does not control the destination, tracking or data handling.
DO NOT SUBMIT
Do not send gambling account or identity documents
This website has no verified channel for receiving personal cases. Do not send passwords, one-time codes, licence documents, passports, bank statements, payment cards, account balances, medical information or cryptocurrency recovery phrases to anyone claiming to represent WagerMark.
For a gambling-provider complaint, use the relevant regulator, bank, payment provider or support service through independently verified contact details.
FUTURE FEATURES
Update the policy before collecting data
If analytics, advertising, forms, email subscriptions or user accounts are introduced, the owner should first document the purpose, legal basis where applicable, data fields, recipients, retention, security controls, user choices and contact route. Consent controls should match the actual technology.
KNOWN GAP
No verified privacy contact was supplied
A monitored domain-based privacy contact and accountable business identity still require human input. The build does not invent them. Until they are added, the policy is a code-level inventory rather than a complete statement for every hosting or business process.
WagerMark Editorial Team
The team publishes research-based guides and separates official records, independently checkable evidence and operator-controlled statements. No individual reviewer or professional qualification was supplied with this project, so none is claimed.
Read the team profile