pandadoku Privacy Policy

Applies to Pandadoku (Android package: com.shanmei.pandadoku)
Last updated: 21 October 2026

Developer and contact

Developer: shanmei. For privacy questions or deletion requests, email shanmeiyang89@gmail.com.

Current closed-test version and scope

This policy describes data handling in the current closed-test Android version. It enables Google Play Games sign-in and Google Saved Games cloud backups, gameplay analytics through Google Analytics for Firebase, and Google AdMob rewarded ads in a test environment. The following sections explain the data processed, purposes, storage and available choices for these services.

Data stored on your device

The game stores level progress, play history and settings on your device so that you can continue playing. Local play requires no separate account registration. Clearing app data or uninstalling deletes local data. Using the same Google Play Games identity can restore the last confirmed cloud backup; changes that have not synchronized cannot be recovered.

Automatic backup after connecting to Play Games

The current closed-test Android version automatically tries to connect to Google Play Games. If interactive sign-in is needed, you may cancel and keep playing locally, or sign in from home settings. After sign-in, progress backs up automatically; there is no backup switch or routine manual sync button. The game reads the player ID to associate saves with their owner and the display name for settings. Google Saved Games stores main progress, unfinished main and daily boards, lives, tool inventory, the latest daily result, the fastest daily time and streak state. In the current closed-test version, reward requests, settlement receipts and chest claim status are saved with tool inventory to prevent duplicate grants. A cloud save contains its version, player ID, save time, content checksum and progress data. It contains no random device/source ID or separate save ID.

Sound, language, analytics configuration and gameplay analytics identifiers are not uploaded with cloud saves. Cloud backup is independent of analytics controls. Offline or awaiting confirmation, the game continues with local progress and retries automatically; unsynced progress is not guaranteed to be recoverable. Uninstalling does not delete existing cloud saves. Contact the email above for deletion assistance.

Gameplay analytics

The current closed-test Android version enables gameplay statistics by default, without a statistics switch in Settings, and uses Google Analytics for Firebase to understand where players get stuck and how they use the game. Custom events cover level starts and ends, results, time, mistakes, restarts, tool use, tutorial progress, daily streaks, result views and actions, daily challenge entry, and periodic or background play checkpoints; user properties include the highest level and difficulty setting. Firebase may also collect app version, device model, operating system version, language, sessions and engagement time, and infer an approximate region from the network address. Analytics uses a random app instance identifier assigned by Firebase and a random ID for each board run to connect resumed visits. These are not linked to the Google Play Games player ID.

The game does not ask you to manually enter your name or email address, or provide contacts, photos or precise location. The player ID and display name obtained through Google Play Games are described above. Gameplay analytics does not collect the advertising ID. The current closed-test version offers optional rewarded ads in a test environment as described below. The game does not offer in-app purchases. If you email us, we receive the address and message you provide.

Sign-in, analytics controls and feedback

For current closed-test builds, contact the email above with privacy or deletion requests. Feedback opens a draft that you choose to edit and send. The draft includes app version, system and current level; it does not automatically include account identifiers, saves or diagnostic logs.

Optional rewarded ads and privacy choices

The current closed-test version uses Google AdMob rewarded ads in a test environment. Test ads do not mean that the advertising SDK processes no data. When a tool has no charges, you may choose an ad to receive one charge for that tool. The base reward for seven consecutive winning days is credited automatically; an optional ad can add two hints, two find-panda charges and one mark charge. Declining or not completing an ad does not remove existing tools or the base reward. Rewards settle only after a valid reward callback from the ad SDK.

Subject to applicable privacy choices, AdMob and its advertising partners process ad requests, impressions, interactions, completion and diagnostic information, and device and network information. The ad SDK may use the advertising ID, app set ID and, where applicable, identifiers related to signed-in accounts on the device, and infer an approximate location from the network address. The game does not request precise-location permission. Applicable Google UMP consent messages identify advertising partners and processing purposes.

Google UMP presents regional advertising privacy choices. Where required, Ad privacy choices in Settings lets you review these choices. Advertising choices are separate from gameplay analytics controls. Subject to the gameplay analytics distribution configuration and consent state, the game also records ad loading, display, rewards, estimated revenue and tool grants to check ad experience and reward settlement.

Reward requests, callback receipts and settlement records are stored locally and included with tool inventory in Google Saved Games cloud backups. This version has no custom reward-verification server. Clearing local app data does not delete existing cloud backups; contact the email above for deletion assistance. Google's advertising data practices are described in Google's advertising information and Google's Privacy Policy.

Processor, retention and deletion

In the current closed-test version, analytics is sent over an encrypted connection to Google's Firebase/Google Analytics service, which processes it for the developer. Cloud backups after connection are stored and processed by Google Play Games and Saved Games. We use aggregate reports to improve the game and do not sell gameplay analytics to advertisers.

User-level and event-level detailed analytics data in Firebase/Google Analytics is retained and processed according to the data-retention rules configured for this project in Google Analytics. Different rules apply to aggregate reports and Google's service operation data. Local progress and settings remain until you clear app data or uninstall the game.

Before a future version adds purchases, advertising partners or new data uses, we will update this policy, the in-app explanation and the Google Play Data safety declaration, and ask for your choice again where required.