Bitz.io Cookie and Storage Note
Bitz.io
Cookies and browser storage
The Bitz.io reference does not set advertising, analytics or third-party cookies. The wagering gap explorer also does not use cookies or local storage to carry scenario inputs from one visit to the next.
The site avoids advertising and analytics cookies
Normal use of the reference does not depend on advertising cookies, analytics cookies or third-party cookies. That keeps the reading experience focused on the editorial content rather than behavioural advertising or audience profiling.
- Advertising cookiesNot set
- Analytics cookiesNot set
- Third-party cookiesNot set
- Explorer local storageNot used
The broader handling of reader data is described in the privacy note. For the purpose and editorial scope of the reference, see About.
The wagering explorer does not keep a saved scenario
The wagering gap explorer on the home page accepts reader-selected values for deposit size, a comparison wagering multiple and an illustrative house edge. The calculation happens in the browser, and the explorer does not save those values in cookies or local storage between visits.
No persistent scenario history
The explorer does not restore your previous values when you return. A new visit starts from the interface’s built-in scenario values.
No cross-site tracking role
The explorer has no need to identify a reader across other websites. Its job is limited to calculating the scenario shown on the current page.
No account dependency
Using the wagering gap explorer does not require a reader profile or saved account state on the reference.
This local, stateless behaviour also means the displayed result is driven by the values currently visible in the controls rather than by an earlier session.
Browser controls remain available
Browsers provide their own controls for cookies, local storage, cached files and site permissions. Those controls remain available regardless of how little storage a particular site uses.
- Inspect site data. Most modern browsers let you view data associated with a specific domain.
- Clear data when you choose. You can remove cookies, storage and cached content from browser settings.
- Use stricter browser privacy settings if desired. Blocking or partitioning third-party cookies can add protection across the wider web.
Cookies and privacy are related but not identical
Cookies are only one way information can be handled online. A privacy view also considers account registration, forms, interactive inputs and hosting infrastructure. The reference therefore keeps a separate privacy note explaining that reading requires no account, the wagering explorer processes inputs locally, and standard hosting logs may still exist.
What browser storage covers
- Cookies stored for a site.
- Local storage retained between visits.
- Cached files kept to speed up loading.
What needs a wider privacy view
- Server logs created by hosting infrastructure.
- Data submitted to another service after leaving the reference.
- Public blockchain records created by crypto transactions.
Tax treatment depends on your country of residence. Seek qualified local advice where your own circumstances require it.
Routine use stays lightweight on browser storage
Advertising, analytics and third-party cookies are not part of the reference, and the wagering gap explorer does not store cookies or local-storage values between visits. Browser-level controls still give you the final say over site data kept on your own device.
