Privacy and Local Storage

Where wheel choices, media and results are stored, what sharing exposes, and which optional requests leave your browser.

Your wheel data stays local by default

Wheel titles, entries, weights, round progress, history and uploaded wheel images/audio are stored in IndexedDB in your browser. The app does not upload them to a product database. Local preferences include language, the last active wheel and mappings to customized templates. No account is required.

Wheel links, result links and files

Sharing is explicit. A wheel link encodes choices and portable settings in its URL fragment, the part after #. A result link encodes the selected result snapshot. The browser does not include the fragment in the ordinary HTTP request, but anyone receiving the full link can read its contents. A link is not a secret or authenticated certificate, and this app cannot centrally revoke copies.

Large wheels and uploaded media use backup files instead of wheel links. Export Wheel Backup includes the wheel content and history, including embedded media. CSV exports contain the choices or history you select. Result JSON/PNG exports contain the chosen snapshot. Import reads a file you choose; it does not upload that file.

Scores, teams, overlays and simulations

Score credits and generated team boards are stored separately on this device. Ordinary wheel backups do not include them; team boards have their own exports. Overlays use independent local copies. An OBS browser source has its own browser storage.

Embedding a wheel shares its content with the viewer. Configured parent pages can receive result events from the embed message interface. Only embed a wheel where you intend those results to be visible. Probability simulations do not write real spin history; the methodology example does not read or write your saved wheels.

Hosting, fonts and diagnostics

Loading pages and assets sends ordinary requests to the hosting service, which can receive your IP address and requested URLs. Stylesheets request fonts from Google Fonts; wheel labels are not added to font requests. Avoid placing personal information in ordinary URL paths or query parameters.

The current application keeps a bounded, in-memory list of predefined event types, selection modes and entry-count ranges. It does not record titles, entry labels, raw error payloads or share tokens in that list. No external analytics transport or session recording is configured. Hosting logs are separate from these local diagnostics.

Backups, deletion and recovery

Local storage is not permanent cloud backup. Clearing site data, losing a device or changing browsers can make your work unavailable. Export a backup before clearing browser storage.

Clearing visible history retains round participation and transaction records used to prevent replay. Deleting a wheel retains local recovery information for undo. Use the browser’s site-data controls to remove all local application records, including saved wheels, media and recovery data. Copies already exported or shared remain wherever recipients stored them.

Public pages and your private version

Search metadata, social images, structured data and sitemaps describe the product and approved public templates. They do not use your saved titles, choices or results. Returning to a template can reopen your local edited version while the public explanation continues to describe its starter purpose.