Data Safety
Data Safety
A plain-language summary matching the Google Play Data safety draft.
Collection and sharing
- Developer-operated account data: none.
- Developer-operated referral data: optional hashed referral identifiers and promo-code counters when referral codes are used.
- Data processed locally: game progress and settings.
- Account required: no.
- Real-money purchases: yes, optional one-time creature and wardrobe cosmetic unlocks through Google Play Billing.
- Ads: yes, optional rewarded ads through Google Mobile Ads SDK and Yandex Mobile Ads SDK.
- Developer-operated analytics SDK: yes, optional Firebase Analytics gameplay events controlled by Settings.
- Crash diagnostics SDK: yes, optional Firebase Crashlytics controlled by Settings.
- Google Mobile Ads SDK may collect and share ad-related data.
- Yandex Mobile Ads SDK may collect and share ad-related device identifiers for advertising when the advertising ID permission is granted. Yandex location tracking is disabled by the app.
- Internet permission in the release app: yes, provided through SDK manifests.
Data types to review in Play Console
- Approximate location: may be derived from IP address by Google Mobile Ads SDK.
- App activity / app interactions: ad views, taps, app launches, and related interactions may be processed by Google Mobile Ads SDK.
- App activity / gameplay analytics: app opens, shift starts and completions, reward claims, settings changes, cosmetic actions, and coarse progress counters may be sent to Firebase Analytics when enabled.
- App info and performance / diagnostics: app and SDK performance information may be processed by Google Mobile Ads SDK; crash and ANR diagnostics may be processed by Firebase Crashlytics when enabled.
- Device or other IDs: advertising ID, app set ID, and similar identifiers may be processed by Google Mobile Ads SDK. Yandex Mobile Ads SDK may process device or other IDs when the advertising ID permission is granted. Firebase may process app instance, installation, and crash reporting identifiers for analytics and diagnostics.
- Yandex location data: not enabled by the app.
- Purchase history: Google Play processes one-time purchases. The app stores purchased product identifiers locally to grant creature and cosmetic access.
Purposes to review in Play Console
- Advertising or marketing.
- Analytics.
- Fraud prevention, security, and compliance.
- App functionality for optional one-time product entitlements.
Security and deletion
- Google Mobile Ads SDK states that collected data is encrypted in transit.
- Yandex Mobile Ads SDK states that collected SDK data is encrypted in transit over HTTPS/TLS.
- Firebase SDK traffic is encrypted in transit.
- The in-app progress reset deletes gameplay progress but keeps one-time purchase entitlements. Clearing app data in Android settings or uninstalling the app removes the local entitlement cache.
- Firebase Analytics collection can be disabled and reset from Settings.
- Advertising ID controls are managed in Android and Google settings.