Cookie information
This cookie policy describes the baseline behaviour of these static website files. The generated static files do not set cookies by themselves. They contain no analytics scripts, advertising scripts, consent platform, account login, shopping cart, comment system or embedded third-party widget that would require a cookie for the site’s own operation.
A site can change that situation by adding services before or after launch. Hosting platforms, analytics tools, advertising systems, embedded media, consent tools and affiliate tracking can introduce cookies or similar browser storage. If any of those are added, this policy must be updated to describe the real implementation before going live.
What a cookie is
A cookie is a small piece of data that a website or connected service can ask a browser to store. Cookies can support functions such as remembering a preference, maintaining a login session, measuring traffic or supporting advertising. Similar technologies can use local storage, session storage or other browser mechanisms to remember information.
This explanation is general context. It does not mean that this site currently uses any of those mechanisms. The supplied static website does not include code that sets first-party cookies, and no cookie names should be inferred or invented where none exist.
No analytics or advertising cookies in the generated build
The current files do not include generated analytics or tracking scripts. They also do not include an advertising network, behavioural profiling tool or marketing pixel. As a result, this policy does not name analytics vendors, advertising networks, cookie identifiers or retention periods that are not actually present.
If the site later installs an analytics platform, advertising service or affiliate tracking system, the live site may begin storing identifiers or sending event data to another service. The policy should then identify the relevant categories and providers based on the actual configuration rather than copying generic cookie language.
Hosting and infrastructure
A hosting provider may use technical mechanisms needed to deliver or protect a website. Whether those mechanisms involve cookies depends on the provider and configuration used on the live site. The static files do not determine that behaviour.
If hosting, content-delivery, firewall or security services add cookies or browser storage, this page should be updated to describe them along with any required consent controls.
External websites have their own cookie practices
Information pages can link to external sites. Following a link does not cause this site to control the destination site’s cookies. Once a visitor reaches another website, that site’s own technologies and policies apply.
This distinction matters for gambling-related services because a casino operator may use account, security, payment, fraud-prevention or preference technologies that are not part of this website. Those external cookies are separate from cookies, if any, set by this site.
When consent controls may become necessary
The current static build does not include a consent banner because it does not include generated analytics, advertising, affiliate tracking or embedded services. A future implementation may require different treatment depending on the technologies added, the users reached and the applicable legal requirements.
If non-essential cookies or similar technologies are added, this page and any consent controls should be updated so they match the live configuration and the choices available to visitors.
How to check the live site after changes
When the site’s technical setup changes, browser storage and network activity should be checked for new cookies or identifiers. The policy and any consent interface should then be updated to match the live setup.
Cookie names, analytics vendors and ad networks should never be added to this page merely as examples. They should appear only if they are actually used on the published site.
Relationship with the Privacy Policy
The Privacy Policy explains the broader data-handling baseline for this site, including the distinction between the static files and any hosting logs processed after the site goes live. The two policies should be maintained together if the site’s technical stack changes.
As long as the site remains in its current static form, the central point is straightforward: the site files do not set cookies by themselves. Any later addition of analytics, ads, embeds, consent tools or affiliate tracking requires this cookie policy to be reviewed and updated before going live.