Crazy8 Countdown
Beta privacy notice

Updated 12 November 2026

Responsible operator

Crazy8 Countdown is operated by an individual using the studio name TrincoGamesStudio in Ontario, Canada. For privacy questions, access, correction or removal requests, email trincogamesstudio@gmail.com.

Your choices

This beta is intended for teens and adults. Practice does not require an online guest: its saves, progress and settings stay on your device. Clearing app/browser data or uninstalling may remove them. Before creating a new online guest, the game explains the processing and asks you to choose. You may decline and keep using Practice. The Cloudflare beta starts fresh online guests. Its new recovery cookie restores only the new guest created on this service. Earlier online profiles and records are preserved separately; they are not automatically linked to a new guest or erased. Local Practice saves and settings remain on this device. Friend online-status sharing starts off. Privacy-conscious website analytics are enabled as described below. Advertising and purchases remain disabled in the public website beta. The iOS version is described in the advertising and purchases section below.

Website analytics

We use Cloudflare Web Analytics on eligible visits to the game homepage to understand page views, visits and performance. Reports can include country, browser, device and referring-site information. This optional analytics does not use analytics cookies, and our loader does not send player names, guest IDs, room codes, saves or gameplay events. It does not measure button clicks.

The loader excludes test and preview pages, addresses with query strings or fragments, embedded or detected automated browsers, and browsers signaling Do Not Track or Global Privacy Control. It runs only after successful game startup on the canonical homepage. Cloudflare automatic injection is disabled. Analytics may therefore undercount use; blocking it does not prevent gameplay. Hosting and security processing described below still applies.

Advertising and purchases on iOS

In iOS version 1.0.2 and later, players in Canada and the United States who have not purchased Avatar Reactions may see a Google AdMob banner in menus or lobbies. Version 1.0.1 and earlier do not show advertising. The app checks the country of the internet connection using our Cloudflare-hosted site. The check sends no guest cookie and the app does not retain the result. We request age-appropriate, non-personalized ads and use Google's restricted data processing setting. The app does not ask for your age, device location or Apple tracking permission. It does not share your guest profile, room codes or gameplay with Google.

Google may process IP addresses and approximate area inferred from the connection, device or app-scoped identifiers, ad activity, app interactions and diagnostics to serve and measure ads, operate its services and prevent fraud. We turn off publisher personalization, publisher first-party ID and the SDK's coarse-location collection control. See Google's SDK disclosure and Google's Privacy Policy. The game's guest removal feature does not automatically delete data held by Google.

Use the banner's AdChoices icon for information about an individual ad, or open Settings and choose the reactions and purchase options to report an ad to us or review available privacy choices. The same optional one-time Apple purchase unlocks reactions and removes banners, including for players who bought it in earlier versions. Use Restore Purchases with the original Apple Account if needed.

Online information

Online features use a random guest ID and recovery cookie. We store a hashed authentication token, generated nickname, avatar/settings, expiry, room membership and game state, results and online progress. Social features store the friend requests, connections, block choices, optional presence and preset emoji interactions you choose to use. Players see relevant names, avatars, moves and shared results. Public room listings show participants; private rooms are not publicly listed. Friend presence is shown only to accepted friends when enabled. There is no configured email/password or social-provider signup, free-text chat or photo upload. Gameplay does not request phone contacts, camera, microphone or precise location.

Hosting and support

Network requests and technical information are processed to deliver and protect the service, even without an online guest. Anti-abuse controls use IP-derived hashes and rate counters. The game uses its own guest recovery cookie. Cloudflare also processes technical connection and security information to operate its infrastructure. Workers application observability, logs, traces and Logpush are disabled; this does not mean the provider keeps no operational or security records. A cookie lifetime does not establish a server-log or backup deletion deadline. The home count sends a network request but does not create a guest; existing guests may send aggregate activity heartbeats.

Cloudflare directly hosts the game and active guest database. Earlier records remain preserved in the original OpenAI ChatGPT Sites database and a separate private Cloudflare archive while migration and retention decisions are reviewed. The active game cannot use archived profiles to authenticate new guests. Support email uses Gmail. Emailing us provides your email address and message content. Read-only automated checks assist the operator with the monitored support inbox and both the current Cloudflare and legacy Sites removal-request queues. These checks are periodic, not real-time or uninterrupted; queue checks may be delayed if dashboard sign-in expires or access is unavailable. The operator reviews and handles flagged requests. These monitoring checks do not automatically reply, forward in-app requests by email, or authorize deletion. Hosting, support and assisted request processing may occur outside Canada; Canadian-only storage is not established.

Purpose and retention

We use information to operate games, recover access, maintain progress and social choices, prevent abuse and handle support/privacy requests. Guest access expires under the current 30-day session rules; expiry does not erase server records. No general guest or match cleanup is active. The receipt-only cleanup described below is separate. Records are retained for these purposes, request/dispute handling and applicable obligations, and email or archived-record removal requests require individual review while protecting other players' records. Pending requests remain for review and follow-up; successful current-guest deletion replaces its request with the minimal completion receipt described below. Provider logs and backups are handled separately under applicable provider arrangements; no project-specific fixed deletion period has been established. Proposed future guest and match cleanup periods are not active.

Access, correction and removal

With your current guest session, open Profile > Privacy and removal requests. Confirm permanent departure and type PERMANENTLY LEAVE AND DELETE MY GUEST. This permanently forfeits your active seats, including private matches, and deletes your current online guest data in the same transaction. Unlike ordinary Leave, no bot holds your seat for a return. Other players keep their cards, progress and results; a last remaining player may win under the existing forfeit rules. Local Practice saves and old archived profiles are excluded. Successful deletion creates a minimal completion receipt and removes any pending request: a random request reference, a fingerprint of the affected records and completion time, plus complaint-review status and resolution time where applicable. It contains no guest ID, name, email, IP address or authentication token. The fingerprint remains potentially linkable and is not anonymous.

Receipts are kept for the initial 30 days, then deleted at the next hourly cleanup unless a complaint remains open. A complaint resolved during those first 30 days does not shorten that period. If a complaint is still open at the end of the 30 days, its receipt is held until resolution, then deleted at the next hourly cleanup, within seven days. Only the operator can mark a complaint open or resolved through the hosting dashboard. If guest access is lost, contact the privacy email above. A nickname, friend code or receipt alone cannot prove ownership; we may be unable to identify the records safely. Never send session cookies or passwords. Archived records and provider backups require separate handling.

If access is lost, contact support without reinstalling. A safe ownership check may be needed; a nickname or reference alone cannot guarantee recovery/removal. Never send passwords, cookies, sign-in codes, government ID or another player's private information. Stopping online play or disabling friend presence does not erase existing records. Ask us if you need help understanding your choices.

Security and updates

The service uses HTTPS and session-based access controls. We update this notice when practices change, including before advertising or materially different data use is enabled.