THE TABLE IS
YOUR BUSINESS.

The short version

You can play Bleach without an account. We use the information needed to run private rooms, remember your browser, prevent abuse, and show your game results. Voice audio is not recorded. Optional Google Analytics loads only after you allow it. Basic visit alerts go to a private operational Telegram channel and include the requested path, referrer or campaign parameters, IP address, approximate IP-based location, and a saved player name when available. Our custom Google Analytics events never contain names, room codes, cards, chat messages, or voice audio.

Information Bleach processes

• Room and game data: display names, private room identifiers, seats, moves, finishing order, messages, emotes, settings, and timestamps needed to run the game.
• Browser identity: random session and supporter identifiers stored in cookies so the server can return you to the correct seat, results, and purchases, plus a saved display name stored locally and mirrored into a first-party cookie.
• Optional account data: email address, sign-in session details, public handle, leaderboard choice, and stats linked after email verification.
• Security and visit data: IP address, approximate IP-based city, region, country, and timezone, requested path and query string, referrer, campaign parameters, user agent, request timing, and rate-limit records used for operational traffic monitoring, sign-in security, reliability, and abuse prevention.
• Purchase data: Stripe checkout and payment identifiers, product, status, and entitlement. Bleach does not receive your full payment-card number.

Voice chat

Voice is optional and starts only after you choose to join and approve microphone access. Browser voice uses encrypted WebRTC connections between participants. A relay may carry encrypted audio when a direct connection is unavailable. Bleach handles short-lived connection signals and presence, but does not record or store voice audio.

Analytics and privacy choices

When a page is visited, Bleach sends an operational alert to a private Telegram channel with the requested path and query string, referrer, common campaign parameters, IP address, and the approximate city, region, country, and timezone supplied by our hosting provider. If the browser has a saved player name, the alert includes that name. Values for common secret, session, authentication, and account query fields are redacted. The private channel also receives deduplicated operational alerts when a join fails because a room is closed, started, or full; when a room waits without a guest; and when repeated voice, checkout, or email-code sign-in problems occur. These alerts use sanitized categories and do not include email addresses, sign-in codes, payment-card data, room credentials, voice audio, WebRTC signaling payloads, or application error details. Aggregate daily counts are used for a private funnel and reliability digest. This happens independently of the Google Analytics choice and helps us understand and monitor traffic to the service.

If you allow analytics, Google Analytics receives page and interaction data such as successful room creation, joining, invite sharing, game starts, completed rounds, solo practice, and voice activation. Events include only coarse context such as player count or whether a game was practice. Google may process device, browser, network, and approximate-location information under its own privacy terms.

If you decline, the Google tag is not loaded. Bleach stores the choice in your browser so it does not ask on every visit. You can reopen Privacy choices from the footer or the button above.

Cookies and browser storage

Necessary cookies and local storage remember room membership, a guest stats profile, saved player name, game preferences, sign-in, purchases, and your analytics choice. These are used to provide features you request. Analytics cookies are separate and are enabled only after consent.

Retention

Visit and operational alerts remain in the private Telegram channel until they are deleted by the operator. Deduplication windows and aggregate daily operational counts may remain after individual alerts are suppressed. Active rooms expire after six hours without a refresh. Retired room and in-room game data are scheduled for deletion after seven days. Short-lived voice signals, presence, messages, and emotes expire sooner. Aggregate operational counts may remain without the original room record.

Completed-round stats, account records, public handles, and purchase entitlements are retained so those features continue to work. They remain until they are no longer needed or a valid deletion request is completed, subject to security, fraud, tax, payment, and legal record obligations.

Bleach may publish anonymous aggregate summaries of completed rounds, such as totals by table size or whether a table included computer players. Public research excludes names, room codes, cards, messages, voice, email addresses, and browser or account identifiers.

Service providers

Bleach uses service providers for hosting and database infrastructure, optional Google Analytics, email delivery, payment processing through Stripe, voice connectivity, and private operational monitoring through Telegram. They process only the information needed to provide their service under their own terms and data-protection commitments.

Your choices and requests

You may play as a guest, keep voice off, decline analytics, keep your handle private, or avoid the optional account and store. For access, correction, deletion, objection, or another privacy request, email play@bleach.city. We may need to verify that the account or browser profile belongs to you before acting.

Changes to this notice

This page will be updated when Bleach changes what it collects or how a service works. Material changes will be reflected in the date at the top.