Privacy on this website

What these pages do, and do not do

Every page on this domain is a plain file. There is no application behind it, no database and no account session. In practice that means:

• No cookies are set by this site.
• No analytics or measurement script runs. Pages are not counted, and reading is not attributed to a person or a session.
• No advertising or tracking pixels are embedded.
• There are no forms, no input fields and no sign-in. There is nowhere on this site to type anything.
• No third-party video players, social widgets, chat widgets or comment systems are embedded.
• Nothing is stored in your browser by these pages — no local storage, no session storage.

You can check most of this yourself: view the page source, or open your browser’s developer tools and look at the storage and network panels. There is not much to see, which is the intended result.

The one outbound request

Honesty is more useful here than a clean claim. The typefaces used on these pages are loaded from a third-party web font service, which means your browser makes a request to that service when a page opens. That request is made by your browser, not by us, and what the font service does with it is governed by that service rather than by this page.

The pages are built so that this is optional: if the font request is blocked — by an extension, a network filter or a privacy setting — the text falls back to fonts already on your device and everything remains readable. Nothing on this site depends on it.

Beyond that, the only requests a page makes are for its own files on this domain.

If you contact the team

This site has no contact form and no mailbox of its own. Reaching the team happens elsewhere — from inside your account, or through the support channel on the official casino site — and it is worth being clear about what that means.

Whatever you send that way is handled under the privacy terms of that service, not by these pages. The message and anything you attach are held there so that it can be read, answered and kept as a record of the correspondence, which is what makes it possible to look back at what was agreed. A message also passes through whichever providers carry it, in the ordinary way.

If you would rather a piece of correspondence were not kept, or you want to know what correspondence exists for you, ask through that same service — it is the one that holds it, and the account it is tied to is what identifies you.

Sending documents

Identity documents are the most sensitive thing anyone sends, so two practical points. First, where an upload area exists in the account, it is the better route — see identity documents. Second, whichever way you send them, cover what does not need to be readable first: a card’s middle digits and the code on its back, and transaction lines on a statement that the request does not concern.

If you sent them as an attachment, a copy usually stays in your own sent items as well. That copy is worth deleting when it is no longer needed, since it is the one you control.

Links to other sites

Some pages link outward — to the independent support organisations, for example. Those sites are run by other people, do their own thing with cookies and measurement, and have their own privacy practices. Once you follow a link, nothing on this page applies any more. Opening them in a separate tab and reading their own notices is the sensible habit.

Changes and questions

If the way this site works changes — if anything is ever added that does collect something — this page is where it will be described, and the description will be specific rather than a general permission. The version published here is the one that applies.

Questions about anything on this page can be raised with the team from inside your account.