Privacy
Section element
Privacy for readers
This information reference can be read without creating an account or supplying personal details. The interactive provably fair exposure checker on the homepage processes the values you enter locally in your browser, so its stake, bet-count, illustrative-edge and bankroll inputs are not transmitted or saved by the checker.
Reading the site does not require a reader profile
The core experience is ordinary informational reading. You can move between the Sportsbet.io overview, payment guides, game guides and other sections without opening a reader account or entering personal data into the site.
There are no forms, analytics accounts or reader-login features collecting information while these pages are read. Any Sportsbet.io account activity takes place on the operator’s own service rather than on these pages.
The provably fair exposure checker calculates locally
The homepage provably fair exposure checker accepts reader-entered values for stake per bet, number of bets, an illustrative house-edge percentage and session bankroll. Those inputs are used to calculate turnover, theoretical expected loss and the expected-loss share of the entered bankroll.
- You enter scenario values. They describe the example you want to examine.
- Your browser performs the calculation. The result updates from the values on the page.
- The inputs are not sent elsewhere by the checker. It does not make a network request to calculate the result.
- The checker does not retain the values. Reloading or leaving the page does not create a stored user profile from those entries.
This local-processing design matters because the checker is a scenario tool rather than an account service. It does not need a name, email address, wallet address or casino login to show the relationship between stake volume, an illustrative edge and bankroll exposure.
The calculation is informational rather than predictive. Its privacy behavior does not change the gambling risks described on the homepage: expected value and actual short-run results are different, and crypto transfers remain generally irreversible.
Hosting infrastructure can create ordinary server records
As with any website, the hosting service may maintain standard server logs needed to deliver requests and operate the service. Such records can include routine technical information associated with a web request, depending on the hosting environment.
This is separate from the provably fair exposure checker. The checker does not transmit its input values to a remote calculation service, and it does not save them for later visits.
- Reading the site
- No reader account is required.
- Checker inputs
- Processed locally in the browser and not stored by the checker.
- Server delivery
- Hosting may create standard technical logs as part of serving web requests.
- Site storage
- See the separate Cookie page for site-wide cookie and local-storage behavior.
Keep casino-account data separate from reference-site use
On this reference
- Read guides without a reader account.
- Use the exposure checker without transmitting its scenario inputs.
- Move between pages without creating a reader profile.
On a casino account
- Casino registration, payments and identity checks belong to the operator’s own account environment.
- Do not paste account credentials, identity documents or wallet secrets into unrelated web pages.
- Keep recovery phrases and private keys outside casino and information-site input fields.
The account guide explains Sportsbet.io’s withdrawal-stage and risk-trigger verification context. That subject is distinct from the privacy behavior of this independent information reference.
Privacy stays simple when reading and calculation stay local
You can read the site without a reader account, and the homepage provably fair exposure checker performs its scenario calculations locally in the browser without transmitting or storing the values entered into it. Standard hosting logs may still exist at infrastructure level, as they can for ordinary website delivery.
