DamulPrivacy Policy
Damul has no sign-up or login, and sends no user information to any server run by the developer. To stay free, Damul uses Google's advertising service (AdMob) and its mediation bidding partner Unity Ads, and Google and Unity process the information below in order to show ads. Damul also uses Google's Firebase Crashlytics to diagnose crashes. It also uses Google's Firebase Analytics for usage statistics, with automatically collected items only and no custom events.
1. Information the developer collects
None. The app never asks for your name, email, phone number, contacts or photos, and does not communicate with the developer's servers. If the app crashes, however, the error information in 2-1 below is sent to Google's Firebase Crashlytics and used by the developer to fix the error.
2. Information Google processes for ads
The Google Mobile Ads SDK and the User Messaging Platform (consent) SDK included in the app collect the following and send it to Google over TLS:
- IP address, which may be used to estimate your approximate location;
- device identifiers — on Android the advertising ID and app set ID; on iOS the advertising identifier (IDFA, only if you allow it — see 3) or app/developer-scoped identifiers;
- app interactions such as app launches and ad views, taps and video views;
- diagnostics about app and SDK performance (launch time, hang rate, energy use) and, on iOS, crash logs not linked to you.
This is used for advertising, ad measurement (analytics) and fraud prevention. Google's handling is described in How Google uses information from sites or apps that use our services and the Google Privacy Policy.
Unity Ads is included in the app as an AdMob mediation (bidding) partner. When an ad is served through Unity, Unity Technologies may process the same kinds of information (advertising identifiers, approximate location, ad interactions, device and diagnostic information). Handling follows the Unity Privacy Policy.
2-1. Crash diagnostics — Firebase Crashlytics (Google) — when the app crashes, the stack trace, device state, device model, OS and app version, and an installation identifier are sent to Google and used only to find and fix the cause. Game progress and saved data are not sent. Firebase privacy and security
2-2. Usage analytics — Firebase Analytics (Google) — the app instance ID, automatically collected events such as screen views and sessions, device model, OS, app version and language, and an approximate region inferred from the IP address are sent to Google and used to understand app usage and improve quality. On iOS, the advertising identifier (IDFA) may also be processed if you allow tracking. No custom events or user ID are used, and game progress and saved data are not included. Retention: according to the Google Analytics data retention setting, at most 14 months; aggregated statistics that do not identify individuals may remain.
3. Consent and tracking
- Firebase Crashlytics is off by default and turns on once the ad consent (UMP) flow finishes. It turns on whatever you choose on the consent screen, and in regions where no consent screen is needed (such as Korea) it turns on as soon as the consent status check completes after launch.
- Firebase Analytics also starts with storage and advertising signals all denied, and is switched on only after the ad consent (UMP) flow finishes, according to the choices you make on the consent screen (Google consent mode v2: analytics_storage, ad_storage, ad_user_data, ad_personalization). In regions where consent is required (EEA, UK and others), no analytics data is stored unless you consent; in regions where no consent screen is needed (such as Korea), it turns on once the consent status check completes. You can change your choice again with "Manage ad privacy choices" below.
- Where the law requires consent (for example the EEA and the UK), Google's consent screen is shown on first launch. You can decline and still play.
- On iOS, Apple's App Tracking Transparency prompt follows the consent screen. If you do not allow tracking, the IDFA is not sent, and the game still works.
- To change your choice, open the "Manage ad privacy choices" button on the game's Settings screen (shown only where Google determines privacy options are required). On iOS you can change tracking under Settings → Privacy & Security → Tracking; on Android you can reset or delete the advertising ID under Settings → Privacy → Ads.
4. Where ads appear
- Rewarded ads — only when you choose to watch one for a battle bonus, a recruit refresh or a daily supply.
- Interstitial ads — between campaigns, with frequency and time caps.
- App-open ads — when you come back after being away.
5. Stored on your device only
- Save slots (automatic and manual)
- Whether you have seen the first-run guide, and sound settings
- When the app last asked you to rate it
- A record that stops an ad reward being granted twice in the same save
These are never sent to the developer and are removed when you delete the app. Values the ad SDK keeps on the device are managed by Google.
6. Third parties
Apart from the information in 2 being sent to Google and Unity Technologies to provide ads, and the crash information in 2-1 being sent to Google through Firebase Crashlytics, and the usage information in 2-2 being sent to Google through Firebase Analytics, the developer shares nothing with third parties.
7. In-app purchases
None.
8. Rating prompts
The Android version may show the Google Play in-app review and the iOS version the App Store review prompt. Ratings and reviews are handled entirely by those stores; Damul does not receive them.
9. Children
Damul is not designed for children under 14 as its primary users and has no intent to knowingly collect children's personal information. If we learn of such a case, we take reasonable steps under applicable law and provider procedures.
10. Your rights
The developer keeps no personal information about you, so there is nothing to access, correct or delete. Deleting the app removes the locally stored game data immediately. Crashlytics crash reports are kept by Google for 90 days, and Firebase Analytics user- and event-level data for at most 14 months, and then deleted. Rights over information Google and Unity process can be exercised through their privacy policies and the device settings in 3.