Cometdive
Effective date: 2026-11-08
| Controller | Willee Project |
|---|---|
| Privacy contact | Willee Project, hanworld@willee.net |
| App | Cometdive (net.willee.cometdive) |
| Contact | hanworld@willee.net |
| What | Details |
|---|---|
| Game records | Unlocked sectors; your best score for each sector; sectors cleared and sectors cleared without being hit; Daily records (today's best, best ever, days played, current and longest streak, the day's boss); totals (runs finished, clears, no-hit clears, enemies destroyed, Comet Dives and enemies destroyed by them, bosses destroyed, ships lost, best combo, play time); the hangar (cores held and cores earned, the upgrade level of each branch, the move speed used in play, the ship forms you have seen); the Codex (enemies, bosses, cards and enemy shots found, and how many of each enemy you destroyed); whether you finished the tutorial |
| Settings | Sound effects, vibration, reduce effects, menu music, game music, music volume, sound effect volume, screen shake, the menu track played last, language |
| Ad spacing | The total time you have spent playing and when the last full-screen ad was shown. Used only to keep full-screen ads from appearing too often |
This data is never sent to us. It is deleted when you uninstall the app.
Device backup. If you have turned on your device's Google backup (Android Auto Backup), the data in the table above is included in that backup, so it comes back when you switch devices or reinstall the app. The backup is stored in your Google account; we cannot see it. You can turn it off in the backup menu of your Android settings.
Separately, the ad SDK and Firebase store consent records (such as your choice in the EEA) and the identifiers listed below on your device.
We receive only what we need to improve the app. There is no personal information such as your name or email. We see the data below as statistics in the Firebase console.
| What | Examples | Why |
|---|---|---|
| App instance ID | A random ID created when the app is installed | Counting whether the same device comes back the next day (retention) |
| Game events | Starting a sector (mode Classic or Daily; sector and zone number, or Daily day number; rule version and attempt number); how a run ended (cleared or failed) with the score, hits, enemies destroyed by Comet Dives, time, the stage reached, the number of Comet Dives by method (flick up or tap the strip below), cores earned, the total hangar upgrade level and ship form, rerolls used and whether you chose a card before wave 1; the card you chose between waves (the offered cards, your choice and its level); defeating a boss (which boss, how long it took); buying a hangar upgrade (branch, level, cost in cores, total upgrade level and ship form, sector, time spent playing); the ship changing form; changing the move speed used in play; finishing the tutorial on first launch and how long it took; the button you pressed on the result screen and whether a full-screen ad was shown (and if not, why), with the total time you have spent playing (in minutes) | Tuning sector difficulty to real play, improving cards, the hangar and modes, spacing full-screen ads |
| App usage | App launches, time spent, app updates | Understanding retention and play time |
| Device and app info | Device model, Android version, app version, language, country (estimated from the IP address; the IP address itself is not stored) | Finding device-specific problems, understanding use by language |
| What | Why |
|---|---|
| Where in the code the error happened (stack trace), time of the error | Fixing the error |
| Device model, Android version, app version, memory and storage status | Finding which devices are affected |
| Crashlytics installation ID (a random ID) | Counting how many devices hit the same error |
Crash reports are deleted after 90 days.
Google processes this data on our behalf. For details, see Privacy and Security in Firebase.
Usage statistics are linked to the ads in section 4 (Google AdMob), so we can see ad revenue together with usage metrics (number of users, return visits, etc.). Google may use the linked usage statistics to improve AdMob features and the app's ad revenue. The advertising ID is not used here either.
There are two kinds of ads.
Ads are served by Google AdMob, and Google and its advertising partners process the following.
| What | Why |
|---|---|
| Advertising ID (Android advertising ID), app set ID, and where applicable identifiers related to the account signed in on the device | Serving ads, frequency capping, measuring performance, analytics, preventing fraud and abuse, and personalization if you consent |
| IP address | Delivering ads, approximate location estimated from the IP address (country or city level) |
| Device and app info (model, OS version, language, screen size, app version) | Choosing ads that fit the screen, preventing fraud and abuse |
| Interactions with ads (impressions, clicks) | Measuring performance, preventing invalid clicks |
| App usage (interactions such as app launches and taps) | Ad delivery and measurement, analytics, preventing fraud and abuse |
| Diagnostics (performance information such as launch time and hang rate) | Ad delivery, analyzing app and ad SDK performance, preventing fraud and abuse |
We do not receive this data. We only receive aggregate reports such as ad revenue. Google also processes this data as an independent controller. For details, see Google's documents:
If you are in the EEA, the UK or Switzerland, a consent window appears the first time you open the app. We ask through a Google-certified consent management tool (UMP), and your choices apply to both ads and usage statistics.
| Where | How |
|---|---|
| In the app | Top right of the home screen: Settings (gear) → General → Privacy options — reopen the consent window and change your choices at any time (shown only in regions where consent is required) |
| On your device | Android settings → Privacy → Ads → reset or delete your advertising ID |
| To stop entirely | Uninstalling the app deletes the records and the app instance ID on your device |
| What | Legal basis |
|---|---|
| Personalized ads | Consent (Art. 6(1)(a)), obtained in the consent window above |
| Non-personalized ads, fraud and abuse prevention, ad delivery | Consent or legitimate interests (Art. 6(1)(f)), depending on local law |
| Usage statistics, crash reports | Legitimate interests (Art. 6(1)(f)): fixing errors in the app and tuning sector difficulty. It also covers viewing ad revenue together with usage metrics, to keep this free app running on ads. In the EEA, storage for statistics is limited according to your choice in the consent window. |
| Game records on the device | Not processed by us, since they are never sent to us |
Usage statistics, crash reports and ad data are processed on Google's servers, including outside Korea and the EEA (for example in the United States). Google states that it uses legally recognized transfer mechanisms such as the EU Standard Contractual Clauses (SCCs).
If you are in the EEA or the UK, you have the following rights under the GDPR (Articles 15–22):
Where to send a request. We do not know your name or contact details, so we cannot find a specific person's records in the usage statistics. When you uninstall the app, its app instance ID is removed, so later data cannot be linked to earlier data, and the remaining data is deleted after the retention periods above. Requests about ad data must go to Google, which actually holds it (see the Google Privacy Policy). If you are not sure what to ask or where, write to hanworld@willee.net and we will help as best we can.
Complaints. EEA residents may complain to the data protection authority in their country, and UK residents to the Information Commissioner's Office (ICO). In Korea, you can report to the Personal Information Infringement Report Center (privacy.kisa.or.kr, dial 118).
This app is not directed at children. It will be listed on Google Play for users aged 13 and over. We do not knowingly collect personal information from children.
If you are the parent or guardian of a child under 16 (13 to 16 depending on the member state) and are concerned about their use of this app, please contact hanworld@willee.net.
If we change this policy, we will post it on this page with a new effective date. For significant changes, we will also let you know through an app update notice.