Plain language.
Small data footprint.

Information stored on your device

CardFuzz stores the settings you choose, including sound, haptics, bot pace, AI difficulty, board theme, view mode, and player display name. It also stores custom rulesets, active local game state where supported, and finished-game history used for local points and scorekeeping.

You can reset settings and erase local history from the app. Removing the app may also remove device-local CardFuzz data, subject to your device and backup settings.

Information used for multiplayer

Online friend tables use Supabase for guest authentication, game storage and server-side game processing. The app keeps session credentials in device secure storage. Online data includes:

• Your guest account identifier and chosen display name.
• Table membership, game state, moves, results and table scores.
• Operational information such as IP addresses and service logs used to operate and protect the service.

Other table members receive the game information needed to play, not your authentication credentials or opponents’ unrevealed hands. Cloud turn notifications and daily summaries are not active; saving a notification preference does not mean alerts are being delivered.

Private table chat

When table chat is enabled, seated players may send plain-text and emoji messages to their table. The service stores the message, author’s guest identifier and table display name, timestamp, and an operation identifier to prevent duplicate sends. It also stores chat-rules acceptance, per-table read position and mute preference, blocked players, and reports of inappropriate content. Chat is not public and has no direct messages, attachments, typing indicators or read receipts shown to other players. Chat does not send push notifications, play sounds or trigger vibration.

Messages are available for 30 days. A reported message and its moderation record may be retained for up to 90 days to investigate abuse. Read positions and block/preferences remain until account deletion. Deleting your online account removes your authored chat, chat preferences and associated report records; friends’ messages and anonymized shared game scores may remain. Closing a table makes its chat read-only rather than deleting it. Blocking a player filters their chat for you; it does not remove their seat or alter game turns. Authorized operators may inspect reports and remove messages or suspend chat access. Chat is not end-to-end encrypted; Supabase processes and stores it.

Why that information is used

Multiplayer data is used to create and restore rooms, enforce game rules, reconnect players, preserve friend-group scores, provide private table chat when enabled, prevent abuse, diagnose failures, and operate the service. CardFuzz does not use game history or chat for cross-app advertising profiles.

Retention and deletion

Device-local information remains until you erase it or remove it through your device, subject to device backup settings. Removing the app, clearing local history or closing a table does not delete your Supabase guest account or online game records. In Settings → privacy & support → delete online account, you can confirm deletion of your guest account. The service removes private-only tables, closes affected shared tables, and keeps completed shared scores under “Deleted player.” Local solo history remains on your device.

The online service currently has no scheduled backup or proven restore process; online tables and scores may be lost. If you no longer have the app, see the web deletion-request instructions. Ownership must be verified; a display name alone is insufficient. Never send passwords, access tokens or reconnect credentials. Operational logs may remain for their configured retention periods.

Sharing and service providers

CardFuzz does not sell player data. Supabase processes online account and game data. Cloudflare serves this website and routes support email. Google Play and Apple distribute the mobile apps; Expo provides build services. Google AdMob processes ad-related data only when advertising is enabled and requested. Support correspondence is processed by our email providers. These providers may process technical information needed to operate their services.

Advertising

CardFuzz may show Google AdMob banner ads on the home screen only to players who choose “18 or older.” Under-18, skipped and unknown age choices do not request ads. The coarse age choice is stored on the device, not a date of birth. Google’s consent form offers consent, decline, and manage-options choices before ads load. You can change your age choice and available ad privacy choices in Settings.

Ad requests are set to non-personalized, but AdMob and its advertising partners may still collect and share device or account identifiers, IP-derived approximate location, app-interaction information and performance diagnostics for advertising, measurement and fraud prevention. CardFuzz does not request precise-location permission. Google’s form lists its partners and possible additional purposes, including location-related processing; you can decline or manage these choices there. Production Android releases use the real CardFuzz banner unit; ad availability also depends on consent, region, inventory and AdMob review. Test builds may use demo ads instead.

Texas Hold’em

Texas Hold’em uses play-money chips only. CardFuzz does not offer wagering, cash-out, prizes, or items of real-world value.

Questions and requests

Contact Adeptus Labs Inc. at support@cardfuzz.com. See support for reporting problems and online-data requests. In-app local-history controls affect this device only.