Privacy note

Privacy on This TrustDice Reference

Reading the site does not require a reader account or the submission of personal details. The main interactive feature, the bonus playthrough checker, also works locally in the browser so its scenario inputs stay on the reader’s device rather than being sent elsewhere by the tool.

Reading stays separate from account identity

The site is an informational reference. Reading an article does not require creating an account here or submitting personal details through the reference. That keeps ordinary use straightforward: a reader can move between the review, payment, game, bonus and account explanations without creating a second identity layer on top of any casino account they may already have.

This separation also helps distinguish the reference from TrustDice itself. Casino account activity belongs to the casino; reading this reference is a separate browsing activity. For more context on the editorial role of the site, see the About page.

Reading

Article access is not tied to a reader profile on this reference.

Interactive scenario

The home-page wagering tool processes the values you enter locally in your browser.

Hosting

Standard server logs may still exist at the hosting layer, as they can for websites generally.

Privacy is clearest when these three layers are kept separate: reading, local tool use and ordinary hosting infrastructure.

The bonus playthrough checker stays in your browser

The bonus playthrough checker on the home page is designed as a local scenario tool. The deposit amount, illustrative match percentage and illustrative RTP you enter are processed in the browser. The tool does not send those inputs away and does not store them for later visits.

That local design matters because the checker is meant to answer a temporary question: how a 40× wagering requirement scales under a reader-defined scenario. Once the page is closed or reloaded, the tool does not maintain a personal history of those scenario values.

Input processing

Local in the browser.

Input transmission

The checker does not send scenario values elsewhere.

Input persistence

The checker does not save scenario values between visits.

Purpose

Temporary wagering and theoretical-cost scenarios.

Enter a scenario deposit, match percentage and illustrative RTP.
The browser calculates the scenario bonus, turnover and theoretical cost.
The result updates on the page without a network request from the checker.
Leaving the page does not create a stored scenario history in the tool.

Hosting logs sit outside the checker

Like any website, the hosting layer may create standard server logs. That possibility is separate from the bonus playthrough checker: local scenario processing does not mean the underlying web host is incapable of recording ordinary request logs.

The reference does not use reader forms, analytics or reader accounts. That statement describes the site’s interaction model in one place rather than turning the privacy note into a catalogue of missing features.

Local tool activity

Scenario inputs are processed in the browser.
The checker does not send or save those values.
The tool has no stored reader profile to reconnect to later.

Hosting context

Standard server logs may exist at the hosting layer.
Those logs are separate from the checker’s local calculation state.
Reading the site does not create a reader account on the reference.

The privacy model is intentionally simple

The practical model is easy to remember: articles are read directly, the wagering checker calculates locally, and hosting may keep standard server logs. That division gives readers a useful answer without implying that every browser request is invisible or that local tool processing changes how the wider web works.

Cookie and storage behavior has its own focused note. The Cookie page explains the site-wide position on advertising, analytics and third-party cookies, along with the checker’s use of browser storage.

If you are testing different bonus scenarios, treat the checker as a scratchpad rather than a saved planning account: record any values you want to keep yourself before leaving the page.

Reader controls remain available

Browser controls remain available for managing site data on your device. The cookie note explains the site-wide storage position, while this privacy note focuses on what happens when you read the reference and use its one interactive scenario tool.

Use the home tool without entering real account credentials or private wallet data; it only needs scenario numbers.
Keep any scenario you want to retain in your own notes because the checker does not save it.
Use browser site-data controls whenever you want to clear data associated with a website on your device.

Privacy is easiest to understand by separating reading, the local checker and hosting

Reading does not require a site account or personal-data submission, and the bonus playthrough checker processes scenario values locally without sending or storing them. Standard hosting logs may still exist. Keeping those layers distinct gives a more accurate privacy picture than treating every part of a website as one data flow.

Published by the TrustDice team.