Privacy Policy

What we store to run a game

To host live multiplayer games, the service stores session state on the server. That includes game codes, player nicknames, seat order, current hands, discard and draw piles, laid-down card groups, scores, and game history snapshots after a game is completed.

The apps and web client also send a device token so a player can reconnect and keep the same seat. The backend stores a one-way hash of that token rather than the raw token value.

What personal data we do not ask for

3 to 13 does not require account registration, email addresses, phone numbers, profile photos, or direct payment details to create or join a standard game session.

Purchases and Pro entitlements

If you buy a Pro upgrade in the iOS or Android app, the service may store your platform, product identifier, purchase reference, entitlement status, expiry date, and the hashed device token tied to that entitlement. Payment processing itself is handled by Apple or Google, not by this site.

Advertising

The current iPhone app integrates Google Mobile Ads for supported ad placements such as lobby banners and round-end interstitials for non-Pro users. The web experience does not currently serve live third-party ads, and Android ad monetization is not yet configured with production ad identifiers.

Third-party ad SDKs may process device and usage data under their own policies in order to deliver, measure, or limit ads. If advertising behavior changes materially in a future release, this policy will be updated.

Analytics and logs

Operational server logs may record technical events such as requests, game lifecycle events, and errors so the service can be monitored and debugged. This is used for reliability and abuse prevention, not for building advertising profiles.

3 to 13 also records product analytics events to understand how players use features such as AI setup, upsell flows, paywalls, restores, and purchases. These events may include the platform, current screen, whether Pro was active, selected AI difficulty, selected AI opponent count, a hashed device token, and limited event properties such as which locked feature triggered an upsell.

We use these analytics for internal product measurement, conversion analysis, debugging, and service improvement. We do not use them to build third-party advertising profiles, and the backend stores a one-way hash of the device token rather than the raw token value.

Internal reporting may aggregate these events by platform, screen, locked feature, and distinct hashed devices so we can compare funnel performance over time and evaluate product changes without storing the raw device token itself.

Completed game history

Finished games may appear in the public history page with the game code, winner nickname, winner score, number of players, and date played. Do not use sensitive personal information as your nickname.

Children

This game is designed for family play, but players should avoid entering personal information in nicknames or chat-like fields. Parents and guardians should supervise younger players when choosing public-facing nicknames.

Retention and requests

Live game state is retained only as long as needed to run the session and support reconnecting players. Completed game records, Pro entitlement records, analytics events, and operational logs may be retained longer for gameplay history, fraud prevention, debugging, financial reconciliation, and product measurement.

Because 3 to 13 does not use a traditional account system, requests related to privacy, deletion, or support should be sent to support@familycardgame.net. Include any relevant game code, platform, approximate purchase date, or device context so the request can be matched to stored records.

Changes

If data handling changes materially, this page will be updated and the date at the top will change to reflect the revision.