Privacy Policy
Sky Guardian: Bullet Hell
Android package and Apple bundle ID: com.emreozel.skyguardian
Last updated: 8 September 2026 · Effective: 30 August 2026
Sky Guardian: Bullet Hell ("the game") is developed and published by KUT Games, a sole proprietorship operated by Emre Özel ("we", "us"). This policy explains what data the game handles, why, and what rights you have over it.
Summary: the game has no accounts and no in-app purchases, and it does not ask for your name, email, location, contacts, photos, microphone, or camera. It is free and supported by ads (Google AdMob — full-screen ads between runs, an ad when you open the game, and optional rewarded ads you can watch for a bonus), with gameplay analytics (Firebase Analytics). The Android release also includes automatic crash reports (Firebase Crashlytics); the iOS release does not currently include Crashlytics.
The game also requests version information from kut-games.com to check for updates. Mobile updates use Google Play or the App Store; the web/PWA version can reload game files from its hosting server. To respond to these requests, the servers receive your IP address, requested URL and standard request information, such as the browser or app's user-agent. Our version-check request does not include your save data or an account identifier.
1. Data stored on your device
Your campaign progress, unlocked ships, upgrades, settings, records, daily streaks and achievements are written to local app storage on your device. This data stays on your device. We cannot see it and it is not backed up to any server we control.
You can erase all of it at any time from Android Settings → Apps → Sky Guardian → Storage → Clear data. On iOS, delete the app from Settings → General → iPhone Storage → Sky Guardian → Delete App. Uninstalling the game also removes its local save. No request to us is needed.
The game also keeps local play statistics (attempts, clears, session lengths) inside this same save data, on your device only. They are never transmitted; you can view them in a hidden diagnostics screen and share them manually if you choose to.
2. Ads (Google AdMob)
The game is free and supported by Google AdMob ads in three forms: full-screen (interstitial) ads that may appear between runs, an app-open ad that may appear when you launch or return to the game, and optional rewarded ads that play only when you tap a clearly labelled button to earn an in-game reward. There are no banner ads and no ads during active gameplay. To serve and measure these ads, Google AdMob may process your device's Advertising ID and coarse technical data (device model, OS version, IP-derived region).
- Consent: advertising privacy choices are presented through the Google UMP consent form where applicable, including in the EEA/UK. When available, you can revisit these choices in Settings → Privacy / Ad Settings inside the game.
- If you decline (or ads are unavailable), the game remains fully playable. No content, level, or reward is ever locked behind an ad.
- On iOS, the game explains why advertising permission is requested and then uses Apple's App Tracking Transparency prompt. You can deny the request or change it later in Settings → Privacy & Security → Tracking.
- On Android, you can reset your Advertising ID or opt out of ad personalization in Settings → Google → Ads.
Ad data is processed by Google under Google's Privacy Policy and Google AdMob policies.
3. Analytics (Firebase Analytics)
We log gameplay events — for example chapter started / failed / cleared, session length, and whether a rewarded ad was completed. We do not add names, email addresses, account IDs or free-text content to these events. Firebase Analytics may automatically process app-instance and device identifiers and technical app and device information alongside the events. Not adding a name or account ID does not make this data anonymous. We use the events to improve difficulty balance, retention and stability.
4. Android crash reporting (Firebase Crashlytics)
The Android release includes Google Firebase Crashlytics so that we can find and fix crashes and measure app stability. Its Firebase dependencies also collect installation and session metadata during normal app use, such as when the app enters the foreground. Collection is not limited to the moment of a crash. The iOS release does not currently include this SDK and does not send Crashlytics reports.
What a crash report contains
| Data | Description |
|---|---|
| Stack traces | The technical trace of where in the game's code the crash happened. |
| Application state | The state of the app at the moment of the crash — for example whether it was in the foreground and the screen orientation. |
| Device metadata | Device manufacturer, model, Android version, available memory and similar diagnostic values. This does not include your phone number, IMEI, or any account identifier. |
| Crashlytics installation UUID and Firebase installation ID |
A randomly generated identifier for this installation of the game. Google states that it "does not uniquely identify a user or physical device". It exists so that ten crashes from one phone are not counted as ten affected players. It is reset when you reinstall or clear the app's data. |
| Session and app metadata | Package name, SDK versions, OS information, network connection type and session-start timing, used by Firebase to measure app stability and associate diagnostics with a build. |
Purpose and legal basis
Crash reports are used for one purpose only: diagnosing and fixing stability problems in the game. Under the GDPR our legal basis is legitimate interest (Art. 6(1)(f)) — keeping the game functional and non-crashing — and the equivalent basis under Turkish KVKK Art. 5(2)(f) (legitimate interest of the data controller). No profiling and no automated decision-making is performed.
Who processes it
Crash reports are processed on our behalf by Google (Google Ireland Limited / Google LLC) as our data processor, under the Firebase Data Processing and Security Terms. Data is transmitted over HTTPS and is encrypted in transit. Processing may take place on Google servers outside your country, including in the United States, under Google's standard contractual clauses.
We do not sell, rent, or share crash data with any other third party, and we do not use it for advertising.
Retention
Google retains crash traces and their associated identifiers for 90 days, after which they are deleted automatically. We do not export or separately archive them.
5. What the game does not do
- No user accounts, no sign-in, no email address collected.
- No banner ads and no ads during active play — full-screen ads appear only between runs or when you open the game.
- No in-app purchases and no payment processing.
- No location, contacts, photos, files, microphone, or camera access.
- No social login and no sharing to social networks.
- Community levels are shared as a plain text code that you copy and paste yourself. There is no server, no account, no messaging between players, and nothing is uploaded.
The Android app permissions are INTERNET (ads, analytics
and crash reports) and com.google.android.gms.permission.AD_ID
(added by the AdMob SDK for the Advertising ID). The game itself is fully
playable with no network connection — offline, ads are simply unavailable.
6. Children
The game is not directed at children under 13. It contains no realistic violence, no purchases and no social features; ads appear only between runs or at app open and never during active play. We do not knowingly collect personal data from children. Crash reports may contain installation identifiers and technical metadata as described above. We do not add names, email addresses or account IDs to crash reports, or use them to build a profile of any user, child or adult. If you believe a child's personal data has somehow reached us, contact us and we will delete it.
7. Your rights
If you are in the EU/EEA or the UK, the GDPR gives you the right to access, rectify, erase, restrict or object to the processing of your personal data, and to data portability. If you are in Türkiye, KVKK Art. 11 gives you equivalent rights. To exercise any of them, write to the address below.
Deleting your data
- Local save data: you delete it yourself — clear the app's data or uninstall the game. Nothing is retained by us.
- Advertising data: withdraw or change consent in Settings → Privacy / Ad Settings (in-game), or reset your Advertising ID in Android settings, or manage iOS tracking permission in Settings → Privacy & Security → Tracking.
- Crash reports: email us at the address below. Because crash reports are not tied to a name or account, please include the device model and the approximate date of the crash so we can identify the record. We will request deletion from Firebase and confirm within 30 days. All crash data is in any case deleted automatically after 90 days.
You may also lodge a complaint with your local supervisory authority (in Türkiye, the KVKK Board; in the EU/EEA, your national data protection authority).
8. Changes to this policy
Version 2.19.0 added rewarded ads (AdMob) and analytics (Firebase Analytics); version 2.21.0 expanded advertising to include full-screen (interstitial) and app-open ads alongside the rewarded ads and added the iOS release with App Tracking Transparency. This page, the Google Play Data safety declaration, and the App Store privacy disclosure are kept aligned. If what the game collects changes again — for example if in-app purchases are ever added — we will update this page and the "Last updated" date above, and update the Data safety declaration before releasing that version. Material changes will also be noted in the store release notes.
9. Contact
Data controller: KUT Games (Emre Özel), Türkiye.
Email: eemree.ozeel@gmail.com