Small controls.
No tracking layer.
The browser state used by this edition’s controls, with page-code behaviour distinguished from technical delivery services.
The website package
The guide does not include an analytics or advertising integration.
The menu, FAQ and arithmetic calculator use browser-side JavaScript. The website code does not set cookies, create an account identifier or save calculator values to local storage. The page controls operate without an advertising-consent prompt.
This description is limited to this website’s page code. It does not claim to describe the current public website, its Cloudflare services, the browser itself or unrelated extensions.
Delivery services have their own technical scope
A statement about page scripts is not a claim about all network processing.
The host and delivery network can handle request information outside JavaScript running on the page. This guide does not invent a cookie inventory or retention period for those systems. The distinction is especially important when comparing editions: the absence of an optional tracking script does not imply that an IP address is never processed during page delivery.
The privacy page explains the website’s narrow feature set and its limits. A third-party casino, social service, browser extension or unrelated site can have a different configuration. The guide does not treat a familiar brand word as evidence that those systems share the same storage or privacy behaviour.
Calculator inputs
Illustrative values remain in the current page.
The arithmetic calculator does not send its inputs to a casino or publisher endpoint. It is an explanation of a hypothetical formula, not a personalised gambling recommendation. Leaving or reloading the page resets the fields to their displayed defaults.
The calculator does not create a payment or request a credit-card number, account balance or identifying information.
Menu and FAQ state
These controls do not require a visitor account.
The mobile menu changes its expanded state within the current page, and Escape closes it. FAQ items use the browser’s standard disclosure mechanism. The site code does not save those choices as an advertising profile or transmit them to a casino. Reloading or navigating can change the visible state without implying that a reader account exists.
These controls support reading and navigation. They do not record a gambling choice, accept an offer or activate account protections on another service. Keeping the interaction limited means the website can explain what the controls actually do without adding an unrelated consent screen or asking readers for private account information.
A new integration needs a new description
Do not apply this edition’s feature inventory to changed code.
If optional analytics, advertising, third-party media or account features are added later, their actual behaviour needs to be reviewed. The description should identify the implemented purpose and controls rather than inherit a claim that no tracking exists from an older file. Technical configuration and public information should be checked together.
Likewise, a cached page or screenshot from the previous website can describe different scripts. This guide does not certify that earlier configuration. The relevant question is which files and services deliver the current edition, not whether a similar design or name appeared in the past. A visible cookie banner alone would not demonstrate that the rest of the description is accurate.
Questions, answered.
Does the page code set tracking cookies?
The site package does not include a tracking integration or set an account identifier for its menu, FAQ or calculator. Those controls operate without a visitor account or an advertising-consent prompt. This is a statement about the code supplied with this edition, not every aspect of the browser or network infrastructure. A delivery service can handle technical requests independently of page scripts. The privacy page explains that distinction, and the guide does not infer another casino’s cookie policy from the behaviour of this domain.
Are calculator values stored between visits?
The website’s calculator does not save inputs in cookies or local storage, send them to an account or submit them to a casino. Reloading the page restores the displayed hypothetical defaults. Browser-level form restoration or an extension can have separate behaviour outside this package, so the site does not claim control over all software on a device. The calculator is intended to show how assumptions affect arithmetic, not to retain a personal gambling profile or recommend a future transaction. No player profile is created.
Why is there no advertising-consent banner?
This edition has no optional analytics, advertising pixel or third-party embedded game in its page code. It therefore does not display a consent choice for features it has not installed. That does not certify the legal position of every hosting service or assert that technical access information is absent. If optional tracking is added in a future version, its actual processing and controls need a new review rather than inheriting this description unchanged. A banner alone would not establish that undisclosed tracking is acceptable.
Does this cookie information apply to the previous website?
The description is for the code and features delivered in the current edition, not a retrospective audit of earlier scripts or a separate operator. An old page or cached screenshot can contain a different configuration. The guide does not claim that another website using a similar name has the same storage or tracking behaviour. When checking a change, identify the actual domain and version rather than relying on shared branding. Public privacy information should describe the implemented features, not copy an assumed inventory from an unrelated site.