Privacy Policy
Last updated: November 6, 2026
Mahjong Wait Duel processes information needed to provide multiplayer games, rankings, advertising, and service improvement.
Game service (Cloudflare)
- Information stored: An anonymous player ID, an automatically assigned display name (Player####), current rating and game count, a recent count of unusually fast correct answers used for fair matchmaking, and App Attest key ID, public key, and counter. Answers and game state are processed and held temporarily during a match; the server does not retain match or answer history.
- Daily challenge statistics: The server aggregates response counts and difficulty by question pattern to select the daily challenge. These aggregates do not store a player ID or individual answer history.
- Recipient and purpose: Cloudflare Workers, Durable Objects, and D1 use this information for authentication, matchmaking, gameplay, ratings, rankings, and service operations. The game server uses your IP address only for rate limiting. Cloudflare may also record the source IP address and request information in its platform logs. The game service does not store IP addresses in player records.
- Authentication challenges: App Attest registration and authentication challenges are used for verification. They are deleted after use; unused challenges expire after five minutes and become eligible for cleanup.
Sign in with Apple (optional)
If you link Sign in with Apple for account recovery, the server stores your Apple user identifier. It processes Apple authentication information and stores a refresh token for revocation when token exchange is available. The app does not request your name or email address from Apple. When you delete your account, the service requests token revocation if configured.
Usage analytics (Google Analytics for Firebase)
Google Analytics for Firebase is always enabled. The app sends Google events about gameplay, matchmaking queue activity, the purchase funnel (paywall views, purchase starts, and completed purchases), and the ATT choice, with relevant event details, to understand usage and improve the service. These events do not include the server player ID. The Firebase SDK separately generates an app-instance ID and may collect app, device, and usage information. There is no in-app setting to turn analytics off. See Google Analytics data collection for details.
Advertising (Google Mobile Ads / AdMob)
The Google Mobile Ads SDK may collect IP address, crash information, app performance data such as launch time, device identifiers (including advertising IDs and app- or developer-bounded IDs), ads viewed, ad and in-app interactions, and coarse location inferred from IP address or other permitted signals. Google and advertising partners may use this information to serve and measure ads and improve the SDK. See Google's data disclosure for details.
In regions where the App Tracking Transparency (ATT) flow applies, ads and the ad SDK remain off until you make an ATT choice. If you allow tracking, the advertising identifier (IDFA) may be used in ad requests. If you deny permission, ads may still be shown, but the Google Mobile Ads SDK does not include the IDFA in ad requests. Ads are not shown while ad removal is active.
Retention and account deletion
Player information, App Attest keys, Apple link information, and ranking information are kept until account deletion. The authentication token is stored in the device Keychain and expires no later than one year after issue. Live match state is temporarily stored in Durable Objects and deleted when the match ends. Your match history is stored on your device and is not sent to the game server.
When you select “Delete Account” in Settings and the request completes successfully, the server deletes your player information, App Attest keys and challenges, Apple link information, and ranking information. Any ongoing match is ended and its state is deleted. The device's game-service authentication credentials are cleared from the Keychain. Match and practice history stored on your device is not removed by this action. Daily challenge aggregates remain because they are not linked to an individual player. Data held by Firebase Analytics or advertising providers is managed by those providers and is not individually deleted through server account deletion.
For questions, visit Support.