Cookie use on the BitKingz reference

Cookie and browser-storage information for the BitKingz reference, including the play-exposure explorer and browser site-data controls.

Cookie

Cookies and browser storage

The site does not set advertising, analytics or third-party cookies. Its play-exposure explorer also works without saving a cookie or local-storage value between visits.

The site-wide setup avoids advertising and analytics cookies

Reading the reference does not depend on an advertising profile or analytics identifier. The browser can load the guides and navigate between sections without a third-party cookie layer.

What this means in normal use

  • Guides can be read without accepting an advertising cookie.
  • Navigation between the BitKingz sections does not depend on an analytics cookie.
  • The home-page explorer does not need a saved browser identifier.

Browser and hosting layers remain separate

  • Your browser still handles ordinary cached files and site controls according to its own settings.
  • The hosting layer can still receive the normal request needed to deliver a page.
  • Clearing site data remains available through the browser even when the site itself is not setting tracking cookies.

The broader handling of ordinary web requests is described in the privacy note.

The play-exposure explorer does not remember a previous session

The play-exposure explorer on the BitKingz home page uses stake, bet count, an illustrative house-edge percentage and bankroll values to update the result on screen. It does not use cookies or local storage to keep those entries for the next visit.

Advertising cookies
Not set by the site.
Analytics cookies
Not set by the site.
Third-party cookies
Not set by the site.
Explorer local storage
Not used to retain scenario values between visits.

Your browser remains the place to inspect or clear site data

Modern browsers provide their own controls for cookies, local storage, cached files and site permissions. Those controls remain available for this site just as they do for other websites.

  1. Open the browser’s site settings. This is where the browser lists data and permissions associated with the current site.
  2. Review stored site data. Browser-managed cache or other site data can be inspected according to the browser’s own interface.
  3. Clear data when you want a fresh browser state. This is a reader-controlled browser action and does not change the underlying BitKingz guides.

For the purpose and independence of the wider reference, see About this BitKingz reference.

Advertising, analytics and third-party cookies are not part of the site-wide setup, and the play-exposure explorer does not store its inputs in cookies or local storage between visits.

↑