Gemduck gameplay analytics

Effective 3 October 2026 · GEMDUCK LIMITED

Games using this service send optional gameplay analytics while analytics is enabled in the game settings. Events include a random installation identifier, session and attempt identifiers, game/platform/version/language, level number, aggregate moves, mistakes, hint use, active play duration, completion and ad callbacks. Android diagnostics also include startup stages and timing, bounded error codes, Android/WebView versions, device model and memory capability, reward-delivery receipts and SDK-estimated ad revenue (amount, currency and precision). The startup diagnostic identifier is separate from the gameplay identifier; a startup or ad request identifier can link the corresponding events. We do not upload saved move histories, names, TikTok profiles, advertising IDs or precise location.

Android 1.6.17 adds a random native-install identifier, first-observed timestamp, new/existing-install scope and a category from Play Install Referrer. Gemduck does not receive raw referrer URLs or raw click identifiers. Source hints cannot cover every view-through installation and unknown does not mean organic. Source profiles and linkage expire after 365 days without updates. This version also uses Google Analytics for Firebase for first-open and level-completion conversion measurement; both analytics services follow the game statistics switch. See the Clear Path privacy policy for the app and Google SDK disclosures.

Crystal Dozer 0.4.19 adds opt-in runtime fault events linked to the game’s random installation and session identifiers, including foreground frame-heartbeat interruptions, WebView responsiveness, ad/shipping stages and OS-confirmed exit reasons. Raw messages, stacks and logs are not uploaded. OS exit reasons may be delivered on the next launch under the original session. Backgrounding, missing heartbeats, forced stops and OS-confirmed crashes are kept distinct.

The application and PostgreSQL database run on Railway. Network providers necessarily handle IP addresses to deliver and protect requests; our analytics database does not store IP addresses. A coarse country code may be supplied by our edge provider or the device’s mobile network; its source is retained, it is approximate, and unknown countries remain unknown. Events are retained for 90 days; pseudonymous player, session and attempt summaries for up to 365 days since activity. There is no cross-game or cross-platform identity matching. A reinstall may be counted as a new player.

Declining or disabling analytics does not remove game features. Disabling clears unsent events and stops future collection. It does not erase data already received. For access or deletion requests, contact hello@gemduck.com with the game's local analytics identifier; never send passwords or verification codes. Administrators verify their email on first sign-in, then set a password. Once a password is set, email-code sign-in is disabled. Resend delivers initial verification emails; codes expire after 10 minutes. Passwords are stored as salted scrypt hashes. A secure, HttpOnly first-party cookie keeps administrators signed in for 90 days, including across browser restarts, unless they sign out or clear cookies.

TikTok mini-game privacy policy · Administrator sign-in