IsleGames — Data Safety summary
Plain-language mirror of the Google Play Data safety form. Use these answers when filling the Console form; the privacy policy is authoritative.
Data collected / shared
| Data type | Collected | Shared | Purpose | Source |
|---|---|---|---|---|
| Device IDs (advertising ID) | Yes — only while ads are active (Pro Unlock not purchased) and after UMP consent where required (EEA/UK/CH) | Yes — AdMob/Google | Advertising | AdMob |
| Approximate location (IP-based) | Yes — only while ads are active (Pro Unlock not purchased) | Yes — AdMob/Google | Advertising, fraud prevention | AdMob |
| App activity / analytics events | Yes | No | Analytics, app functionality | Firebase Analytics |
| Crash logs & diagnostics | Yes | No | Crash diagnostics | Crashlytics |
| Purchase history | Yes — Pro Unlock purchase events (auto-logged by Firebase Analytics); payment details are never received by the developer | Yes — Google Play processes the payment | App functionality (entitlement), analytics | Google Play Billing / Firebase Analytics |
| Game data (saved games, stats) | Stored on device only | No | App functionality | You |
Practices
- No accounts, no sign-in, no cloud sync — all game data stays on-device.
- Data encrypted in transit (HTTPS) for all third-party SDK network calls.
- Users can erase all local data via Settings → Apps → IsleGames → Clear data, or by uninstalling. For analytics/crash data deletion requests, email support@klincksoftware.com.
- No data sale. Ads — and advertising ID collection — are gated by UMP consent in EEA/UK/CH and stop entirely once you purchase Pro Unlock.
- Independent security review: self-assessed.