Privacy Policy
Release-candidate versions: Android 1.0.5 (11) and iOS 1.0.5 (11)
These two versions are release candidates. This notice describes how they are built to work; it does not mean they are published or installed on your device, and details may change before release.
- Android 1.0.5 (11) and iOS 1.0.5 (11): this notice takes precedence over the introduction and sections 1 to 6 and 10 below wherever they mention Google AdMob, Google's consent screen (UMP), when Firebase starts collecting, app-open ads, or Google as the recipient of advertising data. In section 6, advertising data goes to Unity (LevelPlay, ironSource and Unity Ads) instead of Google; Firebase data still goes to Google.
- Earlier versions that contain Google AdMob and UMP (Android 1.0.4 (10), iOS 1.0.4 (10) and earlier): the sections below apply as written.
In the candidate versions
- Ad services. Ads come from Unity LevelPlay (ironSource) with Unity Ads. The app contains no Google Mobile Ads and no Google UMP. These providers may process advertising or installation identifiers, IP address and approximate region, device and app information, ad impressions and interactions, performance and diagnostic information, and your privacy choices, for advertising, measurement and fraud prevention, including in the United States and other countries, under the Unity player privacy policy and ironSource privacy policy. Resetting your ad ID does not erase data a provider already holds.
- Your choices. The app shows its own choice screen instead of Google's. On the same screen you must confirm that you are 18 or older; until you do, no commercial ads, usage analytics or crash reports start. You also choose separately: device access for ads, personalized ads, usage analytics and crash reports (one choice covering both Firebase services), and, for US users, opting out of sale or sharing. You can refuse everything and keep playing, and you can change the choices in Settings at any time. On iOS, Apple's tracking prompt is separate and follows this screen, and personalized ads also require you to allow tracking.
- When ads are requested. The app requests an ad only if you confirmed you are 18 or older and allowed device access, and only if the developer has switched on ad delivery in the published build. Otherwise it makes no ad request. Ads are optional rewarded ads that you choose to watch, and interstitial ads at campaign transitions with frequency limits. App-open ads are not shown.
- Your choices are passed on. Your personalization and sale-or-sharing choices are passed to the ad SDKs as consent or opt-out settings, whether you accept or decline. Declining personalization does not stop the ad SDKs from processing device data for ads you allowed device access to, and it does not promise that a contextual ad will be shown.
- Firebase. Firebase Analytics and Crashlytics start switched off. They collect only in an official release build, after you confirm you are 18 or older and allow usage analytics and crash reports; finishing an ad step does not turn them on. Analytics uses automatically collected events only, with no custom events or user ID. Turning the choice off stops later collection but does not delete data already sent. The retention period set for the Analytics property has not been verified.
- Introductions to other apps. When no campaign ad is shown, the app may show a card introducing another app by the developer. It is built from information and images stored in the app and is not a rewarded ad. Showing it makes no advertising-network request and uses no advertising identifier; services you separately allowed, such as Firebase, work as described above. If you tap "View app", your device opens the store page, or gwangy.com if that fails, which handles data under its own terms.
- Developer server. These versions do not call any server operated by the developer, including its regional-policy service. The iOS app may look up its own App Store listing from Apple to check for updates. Opening this policy, the terms or gwangy.com in a browser connects to the developer's website like any web visit.
- Requests. That SDK providers process data does not remove your ability to ask the developer. The statement in section 10 that the developer keeps no personal information refers to data the developer holds. Send access, deletion or other requests about SDK data to gwangy.claw@gmail.com; the developer will answer or direct you to the provider's process.
Notice added November 1, 2026: this section adds version applicability. It does not change the effective date or grant any new permission.
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, the configured retention period; 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 the configured retention period, and then deleted. Rights over information Google and Unity process can be exercised through their privacy policies and the device settings in 3.