Current cookie position
The website code does not currently configure Google Analytics, advertising pixels, behavioural profiling cookies, Google Fonts or third-party CDN scripts. A hosting or security layer may still use a strictly necessary technical cookie where required to deliver or protect the website.
2. Current use on this website
This website is built as a lightweight static experience. The interactive slider, navigation menu, FAQ panels and responsible-gambling widget operate in the browser without needing to store a persistent tracking identifier.
At the date shown above, the website code does not intentionally set non-essential first-party cookies. It also does not include an external analytics package, advertising pixel, social-media tracking button or remote font service.
Server infrastructure can still receive ordinary request information such as an IP address, requested page, browser details and time of access. A security or content-delivery provider may also set a short-lived essential cookie to distinguish legitimate traffic from automated abuse. Server logs are addressed in the Privacy Policy.
3. Cookie categories and their status
| Category | Purpose | Current status |
|---|---|---|
| Strictly necessary | Security, traffic delivery and essential page operation where required by the hosting environment. | May be used only when technically required |
| Preferences | Remembering a visitor’s optional display or interface choice between visits. | Not currently set by the website code |
| Analytics | Measuring visits, navigation and performance across sessions. | No third-party analytics cookies currently configured |
| Advertising | Cross-site profiling, retargeting or personalised advertising. | No advertising cookies currently configured |
A cookie described as strictly necessary should be limited to an essential technical or security purpose. It should not be repurposed for behavioural advertising merely because it was originally labelled essential.
4. Similar browser and network technologies
Websites can recognise activity through technologies other than cookies. These can include local storage, session storage, tracking pixels, software development kits, device identifiers and server logs.
- Local and session storage can store information directly in the browser. The current responsible-gambling widget state is temporary and is not designed to build a persistent visitor profile.
- Tracking pixels are small resources that can report when a page or message was opened. No third-party advertising pixel is currently configured in the website code.
- Server logs record requests needed to deliver and protect the website. They are not browser cookies, although an IP address or other log field may still be personal information in context.
- Referral parameters can identify that a visitor arrived at an external destination from this website. They are part of a link and are not themselves stored as a cookie by this website.
5. Affiliate links and referral measurement
Some outbound links may contain an affiliate or campaign identifier. When the link is opened, the destination can receive that identifier together with the ordinary web request. The destination may then set its own cookie or use another method to attribute a later registration or qualifying action.
This website may receive an aggregated conversion record or commission. It does not need to receive a visitor’s complete payment-card information, gambling password or crypto private key for that purpose.
Following an affiliate link is optional. A visitor can decide not to open it. Once the destination loads, its own cookie settings, consent tools, privacy policy and account terms apply.
6. Cookies on external websites
The website links to independent destinations, including gambling information and responsible-gambling support services. Those websites may use essential cookies, analytics, personalisation or advertising technologies under their own policies.
Opening an external page in a new window does not prevent the destination from receiving the request or setting cookies for its own domain. Review the destination’s privacy and cookie information before changing its consent settings or entering personal details.
Account and payment pages are separate
If an external service provides registration, login, payment, identity verification or gambling features, its cookies are controlled by that service—not by the static public pages covered by this Cookie Policy.
7. How to control or remove cookies
Most browsers allow visitors to inspect, block or delete cookies through privacy or site-data settings. Controls vary by browser and device, but commonly include:
- Deleting cookies and site data already stored for a selected domain.
- Blocking all cookies or only third-party cookies.
- Clearing cookies automatically when the browser closes.
- Using a private-browsing window for a temporary session.
- Reviewing which websites have permission to store data.
- Blocking pop-ups, notifications and cross-site tracking where supported.
Blocking every cookie can prevent some security, login or preference features from working on other websites. Removing a destination’s cookies may also sign the visitor out of that destination. Browser controls do not cancel an account, stop marketing email or create a gambling self-exclusion.
For gambling protection, use stronger controls such as account closure, bank transaction blocks, device blocking software and BetStop where applicable. These options are explained in the Responsible Gambling Guide.
8. Consent and future optional cookies
Because the website does not currently configure non-essential analytics or advertising cookies, it does not display a consent banner merely for appearance. A banner that offers no real choice would not improve privacy.
If optional analytics, personalisation or advertising technology is introduced later, this policy will be updated and a consent control will be provided before non-essential storage is activated where required by applicable law. Rejecting optional cookies should not prevent access to ordinary informational content.
Consent should be specific and capable of being withdrawn. Changing a future consent setting will affect future processing but may not automatically delete data already lawfully retained by an external provider.
9. Cookie duration and retention
A strictly necessary cookie, if used by the hosting or security environment, should remain only for the period needed for its technical purpose. Session cookies normally expire when the browser closes, while security cookies may use a short fixed duration.
If the website introduces another category, the cookie name, provider, purpose and typical duration should be added to this policy or an accessible consent interface. Server-log retention is separate from cookie expiry and is described in the Privacy Policy.
10. Questions and policy changes
Questions about cookies or browser storage on this website can be sent to [email protected]. Include the browser, device and page involved, but do not send passwords, payment credentials or identity documents.
This policy may be updated when website technology, hosting arrangements or legal requirements change. The revision date at the top identifies the current version.