Pandadoku Privacy Policy

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

Developer and contact

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

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

Configured Android versions from 0.1.5 automatically try 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. 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. During development, compact v2 saves do not read old v1 cloud saves. Version 0.1.3 retains its backup switch; turning it off does not delete an existing cloud save.

Gameplay analytics

Current development and closed-test builds enable gameplay statistics by default, without a statistics switch in Settings. Development packages only log local diagnostic events and do not send them to Firebase. Configured Android release packages use 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 for your name, email address, contacts, photos or precise location. This version does not use the advertising ID, display ads or offer in-app purchases. If you email us, we receive the address and message you provide.

Sign-in, analytics controls and feedback

Distributions requiring consent ask before collection; declining does not affect gameplay or cloud backup. Versions through 0.1.3 default analytics to off and retain the settings choice. Disabling it stops collection and asks Firebase to clear local analytics data, but does not immediately delete data already uploaded. 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.

Processor, retention and deletion

When enabled under the applicable distribution configuration and consent state, 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.

For a standard Google Analytics property, user-level and event-level detailed data retention is set to either 2 or 14 months; Google periodically deletes data when that period expires, and new activity may reset the retention period for a user identifier. Before the first app release, we will verify the project's actual setting and state the specific period here. 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 ads, purchases 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.