Privacy Policy

Effective date: October 20, 2026

This policy applies to the mobile game Prism Defense (the "Service"), provided by Dongmin Yu (the "Developer"). This policy also describes how the Developer processes information when you visit the official Prism Defense website at prism-defense.donminzzi.kr (the "Website").

1. Overview

The Service requires no game account registration, and the Developer operates no server of their own. The Developer does not sell your personal information.

The Service does use Google's Firebase, and through it the information listed in section 3 is collected and processed on Google's infrastructure. Google processes that information on the Developer's behalf. In apps that support in-app purchases, RevenueCat also processes purchase history and Premium access status. See section 4 for details. For the mini app inside Toss, see section 8.

2. Information stored on your device

The following game records and settings are stored on your device. As described in section 3, selected gameplay summaries and settings state are also sent to Firebase for statistical purposes.

• Game records (best wave, kills, daily challenge records, achievements, Prism balance)
• Settings (sound/music mute, language, tower strategy modes, equipped palette, and similar)

Uninstalling the app deletes these game records and settings from your device. It does not delete a platform cloud-save copy described below.

2.1. Platform cloud save

Store app versions that include cloud save can also send selected progress to Google Play Games saved games on Android or Apple's iCloud key-value storage on iOS. This saves progress for synchronization and restoration after reinstalling or changing devices within the same platform account; it is separate from Firebase analytics and Premium purchase restoration. Android uses the signed-in Play Games account; iOS uses the available iCloud account when iCloud is enabled for the app. The game remains playable locally and offline when cloud storage is unavailable.

The saved data includes best scores, waves and kills; daily challenge records, streaks, streak shields and your daily signature; Prism earnings and spending records; the equipped palette; and unlocked achievements. Reward records include installation-specific identifiers and run sequence values used to distinguish earned Prisms when saves merge. This does not synchronize every setting: sound, reminder, tutorial and ad-consent settings are not part of this cloud-save document. The app does not transfer this save between Play Games and iCloud, and the mini app inside Toss does not use this feature.

Google and Apple store this copy through the respective platform account services. Their handling follows the Google Privacy Policy or Apple Privacy Policy. See sections 9 and 11 for retention and requests about cloud data.

3. Information collected through Firebase

Google Analytics for Firebase — collected for statistical purposes, to improve the Service:

• App instance ID (a device identifier assigned automatically per installation)
• Advertising identifier (Android Advertising ID, iOS IDFA — on iOS, only where you have permitted tracking)
• Coarse location derived from your IP address
• Usage records, including screen views, run starts, end-of-run summaries (mode, wave reached, kills, per-tower strategy modes, revive use, and play time), runs left before they end (mode, wave reached, and play time), daily result share taps (date), tutorial outcomes (completion, skip, or storage failure), ad placement and lifecycle status (offer, display request, impression, reward, dismissal, failure, suppression, or unavailability), related reasons, and whether a reward was accepted
• First-day usage records, for 24 hours from when the tutorial is first opened: the tutorial steps shown and its outcome (completion, skip, or leaving it, with the step skipped or left on), each with the time since the tutorial was opened, the waves reached in the first run (waves 3, 5, 10, 15 and 20, with the play time to each), each time the app goes to the background or returns during the first run (including a screen lock or an app switch, not only closing the app, with the wave reached and play time at that moment; a return to a first run that went to the background within the 24 hours is recorded even after they end), a first run left before it ends, and the first day's run starts, run ends and returns to the app Run starts, end-of-run summaries and runs left before they end also record whether the run took place on the first day.
• Settings state (equipped palette, whether the extended speed option is unlocked)
• Device and app information (model, OS version, app version)

This information is not collected to identify you personally, and the Developer does not attach a user account identifier to analytics data.

Firebase Crashlytics — collected to diagnose crashes and errors:

• Stack traces and application state at the time of the error
• Device and operating system information
• A record of the screens visited immediately before the error
• Crashlytics installation identifier

Firebase Authentication (Play Games sign-in) — processed only if you use Play Games sign-in:

• The user identifier issued by Firebase
• The IP address of the sign-in request (to prevent abuse)

Sign-in is optional for local gameplay; platform cloud save requires the account described in section 2.1.

For details on Google's processing, see the Google Privacy Policy.

4. In-app purchases (RevenueCat)

The Service uses RevenueCat to verify Prism Premium purchases, manage access, restore purchases, prevent purchase fraud, and provide purchase analytics. When purchases are enabled in the app, RevenueCat initializes and checks access and product information even before a purchase is made. This may involve processing:

• An anonymous app user identifier generated by RevenueCat
• Purchased products, transaction identifiers, purchase times, and Premium access status
• Purchase verification information, such as Apple receipts or Google Play purchase tokens
• Device type, operating system, locale, and currency information

The app does not send names, email addresses, or Play Games user identifiers to RevenueCat. Apple App Store or Google Play handles payment; the Developer and RevenueCat do not receive payment card details. Restoring a purchase checks Premium access and does not restore game records or Prism balances stored on your device.

RevenueCat processes purchase information on the Developer's behalf, and this information may be processed and stored on infrastructure in the United States. For details about RevenueCat's practices, see RevenueCat's privacy information. Store processing follows the Apple Privacy Policy or Google Privacy Policy, respectively.

5. Advertising (Google AdMob)

Rewarded ads and interstitials are served through Google AdMob, and Google may collect and process:

• Advertising identifiers (Android Advertising ID, iOS IDFA)
• IP address and coarse location
• Device information (model, OS version, and similar)
• Ad-interaction data (impressions, clicks)

For details, see Google ad technology providers.

6. Ad consent

• In regulated regions (EEA, UK, and similar), the Google UMP (User Messaging Platform) consent form appears, and you can choose whether to receive personalized ads.
• On iOS, the App Tracking Transparency (ATT) prompt may be requested. If you decline, ads are served without the app having access to the advertising identifier (IDFA), so they are less relevant to your interests. The app does not itself select a non-personalized ad mode; what is actually served is decided by Google from your consent state and your ATT response.
• Gameplay is never restricted by your consent choice. Consent gates ads, not play.
• When Google UMP requires it, you can change or withdraw consent through Ad privacy options in the app settings.
• You can reset or delete the advertising identifier in device settings.
• You can also change iOS tracking permission in device settings.

7. Website analytics (Vercel Web Analytics)

The Website uses Vercel Web Analytics to measure aggregate traffic and improve the Website. Vercel processes the following information on the Developer's behalf:

• Event timestamp
• Page URL and route
• Referrer
• Filtered query parameters
• Country, region, and city derived from the request
• Browser, operating system, and device type
• Web Analytics script version

Vercel Web Analytics does not use third-party cookies. Vercel identifies a visitor through a hash created from the incoming request. The hash is valid for one day and is then reset. Vercel provides the Developer with aggregated statistics that are not tied to an individual or an IP address.

For details, see Vercel Web Analytics Privacy and Compliance.

8. The mini app inside Toss (Apps in Toss)

The Service is also offered as a mini app inside the Toss app, operated by Viva Republica (Apps in Toss). That version does not use Firebase, RevenueCat or Google AdMob from sections 3 to 6, and processes information as follows:

• The game records and settings in section 2 are stored in the mini app storage that Toss provides, not on your device. The game user key Toss issues for this game is stored in the same storage and is not sent to the Developer.
• The play, tutorial, ad lifecycle and first-day records among the usage records in section 3 are sent to Toss's Apps in Toss analytics for statistical purposes. Screen views and settings state are not sent.
• Where ads are offered, they are Toss in-app ads, and Toss handles showing them and granting their rewards.
• Review requests are shown through a feature of the Toss app.

Toss's privacy policy applies to the information Toss processes for your Toss account, the mini app storage, its analytics and its ads. If you go from the Toss app to Prism Defense on the App Store or Google Play and install it, the rest of this policy, apart from this section, applies to the installed app. Game records from the mini app are not carried over to the installed app.

9. Retention

Game records and settings stored on your device are deleted when you uninstall the app. The platform cloud copy in section 2.1 can remain after uninstalling, signing out or disabling synchronization; these actions do not request its deletion. Its storage and retention follow the relevant Google or Apple account service's policies and data controls, rather than the lifetime of the local installation. Retention of information collected through Firebase follows Google's policies and the retention period configured by the Developer. Purchase information processed through RevenueCat is retained as needed to verify and restore purchases, subject to applicable legal retention requirements. Uninstalling the app does not automatically delete purchase records held by RevenueCat or the store. Retention of information collected through Vercel Web Analytics follows Vercel's policies. Game records and settings in the Toss mini app storage are kept and deleted under Toss's policies.

10. Children

The Service is not directed at children, and the Developer does not knowingly collect personal information from children.

11. Your rights

• Uninstalling the app deletes all information stored on your device.
• For the separate cloud copy in section 2.1, use Google's Play Games data controls, or contact Apple Support about iCloud. The app has no cloud-save deletion button; contact the Developer below if you need help identifying the relevant platform service.
• You can reset or delete your advertising identifier at any time in your device settings.
• To request access to or deletion of information collected through Firebase, contact the Developer below.
• To request access to or deletion of purchase information processed through RevenueCat, contact the Developer below. Deleting information and requesting a store refund are separate processes.
• To ask about information processed through Vercel Web Analytics, contact the Developer below.
• For information Toss processes in the mini app inside Toss, request access or deletion as Toss's privacy policy describes.

12. Changes to this policy

If this policy changes, the revised policy and its effective date will be posted on this page.

13. Contact

• Developer: Dongmin Yu
• Email: ydm2790@gmail.com