Privacy
Reading the site does not require an account or the submission of personal details. The interactive play-exposure explorer processes its inputs inside the browser.
Reading the guides does not require a personal profile
The reference is designed for reading and comparison. It does not ask a reader to create a site account or provide personal information in order to access the BitKingz overview or the individual guides.
- Reading accessNo site account required
- Interactive inputsProcessed in the browser
- Input retentionNot stored by the explorer
There are no forms, analytics or reader accounts on the reference. That keeps ordinary use focused on the content itself rather than a profile or tracking layer.
The play-exposure explorer keeps entered values on your device
The play-exposure explorer on the home page calculates turnover, theoretical expected loss and bankroll exposure from the values entered by the reader. Those values are handled locally in the browser, are not transmitted by the explorer and are not saved between visits.
- What you enter
- Stake, number of bets, an illustrative house-edge percentage and a starting bankroll.
- Where calculation happens
- Inside the browser on the device you are using.
- What the explorer sends
- No entered values are sent elsewhere by the explorer.
- What it retains
- No entered values are stored for a later visit.
The related cookie and storage note explains the same point from the browser-storage side.
Standard server logs can exist at the hosting layer
As with ordinary web hosting, the hosting service may maintain standard server logs needed to deliver and protect the site. Those logs are separate from the play-exposure explorer and from the content-reading experience.
Page delivery
A hosting server has to receive a request in order to return the requested page and supporting files to the browser.
Interactive calculation
The play-exposure calculation itself stays on the device and does not create a separate transmission of the values entered.
Reader controls
Browser privacy and site-data controls remain available through the browser you use to access the reference.
For broader context on the purpose and scope of the reference, see About this BitKingz reference.
Privacy questions are easiest to separate by where data is handled
- Content reading happens through normal web requests. The browser requests a page and the hosting service returns it.
- Explorer inputs stay in the browser. The numbers entered for a scenario are used locally for the result shown on screen.
- Browser storage is a separate question. The cookie note explains the site-wide approach to cookies and local storage.
The privacy model keeps the interactive calculation on the reader’s device
The main privacy distinction is between ordinary hosting requests and the play-exposure explorer itself. The explorer uses the values entered in the browser without transmitting or retaining them.