TRUTH OR DARE WHEEL

Privacy Policy

The current game works without a player account. Names, custom prompts and session progress are designed to remain in the browser where they were entered.

Reviewed August 3, 2026EnglishTruth or Dare Wheel Editorial Desk
01

Scope of this policy

This page describes the current Truth or Dare Wheel MVP. It covers the public wheel, question library, Blog and local browser storage. A future analytics, advertising, account or cloud feature would require this page and any necessary consent controls to be updated before release.

02

Browser-only game data

The keys tod_session_v1, tod_custom_prompts_v1, tod_import_draft_v1 and tod_preferences_v1 may store player names, custom prompts, selected prompt IDs, filters, game statistics and preferences on the current device.

This data supports session restoration, private custom prompts, temporary question imports and preferences. The public game does not intentionally send those values to the application server.

03

How to clear local game data

Use Reset session to clear active game progress. Remove custom prompts from the custom list, or clear site storage through the browser when you want to remove all local keys for this domain.

Clearing browser storage cannot be undone and may also remove preferences and temporary selected decks.

04

Security and functional cookies

The application may set a functional CSRF cookie named tod_csrf_cookie to protect POST requests. It is not an advertising identifier. Administrative pages also use browser Basic Auth behavior configured by the server.

Cookie security settings depend on the environment; production is configured to require Secure cookies over HTTPS.

05

Ordinary web requests and server logs

Like other websites, the hosting and web-server layer may process request information such as an IP address, timestamp, requested path, status code, referrer and browser user agent to deliver and secure the service.

The current application does not add a public analytics or advertising integration, but hosting-provider or server logging must be reviewed in the actual production environment.

06

What the current MVP does not provide

There is no player account database, cloud deck storage, answer collection, public user submission system or advertising profile in the current code. The Blog manager is a private server-admin function and is not a public player account.

07

Third-party links and communication

The public site may link to an email client through a mailto link. Your email provider handles messages under its own privacy terms. If future articles link to external sites, those sites control their own processing.

08

Questions and future changes

Send privacy questions to [email protected]. Include the page or feature involved but do not email private game answers or unnecessary player information.

Material privacy changes should update the visible policy date and the implementation before the affected feature is launched.

PRIVACY POLICY FAQ

Clear answers about this page

Are player names uploaded to the server?

The current public game stores player names in browser storage and does not intentionally upload them to the application server.

Where are custom prompts stored?

They are stored under a versioned local-storage key in the current browser when browser storage is available.

Does the site use advertising trackers?

The current application does not include an advertising or public analytics integration. Production hosting logs must be verified separately.

How can I delete local game data?

Reset the session, remove custom prompts or clear this site’s storage through browser settings.

Does the site collect Truth answers?

No answer-entry or answer-collection feature exists in the current MVP.