Bitz.io Privacy Note
Bitz.io
Privacy and local processing
Reading the Bitz.io reference does not require a reader account and does not ask you to submit personal data. The interactive wagering gap explorer on the home page also keeps its scenario inputs inside your browser.
Reading without an account
The reference is designed for ordinary reading without a registration flow. You can move between the review, payments, games, bonus and other sections without creating a profile for this reference.
- Reader accountNot required
- Personal-data formNot used for reading
- Interactive input handlingLocal in your browser
The reference has no forms, analytics or reader accounts in normal use. That statement is about the reference itself; it does not describe what may happen if you leave it and use another service.
For the editorial scope and independence of the reference, see About. For storage-specific details, the cookie and browser-storage note explains what the site does with cookies and local storage.
The wagering gap explorer processes inputs locally
The wagering gap explorer lets you enter a deposit scenario, a comparison wagering multiple and an illustrative house-edge percentage. Those values are processed by the page in your browser so the result can update immediately.
Inputs stay local
The values you enter are used only to calculate the displayed scenario in the current browser session. They are not sent to a remote endpoint by the explorer.
Nothing is saved by the explorer
The explorer does not save your inputs for later visits. Reloading the page returns the interface to its built-in scenario values rather than restoring a personal history.
The output is informational
The result describes turnover exposure under the values you choose. It does not create a user profile, predict gambling results or make a recommendation to gamble.
Hosting logs can still exist
As with any website delivered through hosting infrastructure, standard server logs may be kept by the hosting environment. These logs commonly support security, reliability and basic delivery functions at the infrastructure level.
- Page content
- Delivered to your browser when you request a page.
- Explorer inputs
- Processed locally by the browser and not sent or saved by the wagering gap explorer.
- Hosting activity
- Standard server logs may exist as part of routine website delivery.
Because the reference does not ask readers to create accounts, normal use does not depend on building an identity around the articles you read or the values you test in the explorer.
Browser controls remain in your hands
Your browser gives you controls for site data, history and cached content. The precise menus differ by browser, but the basic principle is the same: you can inspect or clear data associated with a site from your own device.
- Use private browsing when appropriate. A private window can reduce local history retained after the session, depending on your browser.
- Clear site data from browser settings. This is useful when you want to remove cached or stored site information from your device.
- Review browser privacy controls. Built-in settings can limit cross-site tracking or other browser-level behaviours independently of this reference.
Crypto transactions also carry their own privacy and financial considerations outside the reference. Blockchain transfers are generally irreversible, and transaction activity can remain visible on public ledgers depending on the network.
Local calculations keep scenario inputs on your device
Routine reading does not require an account or personal-data submission, and the wagering gap explorer handles its scenario values locally without sending or saving them. Standard hosting logs may still exist at the infrastructure level, while browser settings remain the main place for controlling data stored on your own device.
