[ privacy ]

Plain language.
Small data footprint.

This notice describes the current Android internal test and the data the planned friend-table service needs to make multiplayer work.

Current solo build: no advertising, no cross-app behavioral tracking, and no traditional player account. Solo settings, custom variants, and completed-game history stay on the device.

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

Multiplayer is not enabled in the current solo-first Play build. When friend tables are enabled, CardFuzz sends the following information to the match server selected by the app:

Your display name and a device-generated member identifier.
Friend-group membership, room state, turns, game results, and table scores.
Preset reactions and reconnect credentials.
A device identifier and Expo push token if you enable turn alerts.
IP addresses and operational logs that infrastructure providers may process to run and protect the service.

Why that information is used

Multiplayer data is used to create and restore rooms, enforce game rules, reconnect players, preserve friend-group scores, deliver requested turn alerts, prevent abuse, diagnose failures, and operate the service. CardFuzz does not use this information for cross-app advertising profiles.

Retention and deletion

Device-local information remains until you erase it, reset the app, or remove it through your device. A friend-group owner can delete the group from CardFuzz, which removes that group’s server rooms, scores, push registrations, and matching local history. Infrastructure backups may retain an encrypted or access-controlled copy for the provider’s configured snapshot window.

Before public multiplayer release, this page will be updated with the production hosting provider, region, and exact backup-retention window.

Sharing and service providers

CardFuzz does not sell player data. Information may be processed by infrastructure needed to distribute and run the app, including Google Play, Expo services used for builds or optional notifications, and the future match-server host. Their handling is governed by their own terms and privacy notices.

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

For the internal test, use the feedback channel supplied with your Google Play tester invitation. Data-deletion controls are also available inside CardFuzz under Settings → privacy, terms, support & data deletion. A public support mailbox will be added before public release.