Privacy Policy — Zenith Defense: Idle TD

Last updated: October 9, 2026

CWB Digital operates Zenith Defense: Idle TD. Contact us at cwbdigitalco@outlook.com about privacy, safety or your account.

Information used by the game

• Account and progress: Firebase account identifiers, linked sign-in details, username, game saves, purchases and reward receipts help us authenticate players, restore progress and prevent duplicate or fraudulent rewards. Apple and Google process store payments; we do not receive your payment-card number.
• Social features: your chosen name, public profile and rankings are visible to other players. Global chat is public to players; clan chat is available to clan members. We store messages, friend relationships, invitations and moderation reports to operate these features and investigate abuse. Do not post private or sensitive information.
• Analytics and diagnostics: Firebase Analytics and Crashlytics process gameplay events, installation/device identifiers, app/device information and crash diagnostics. Gameplay analytics may be associated with your game account identifier. These records are not necessarily anonymous.
• Advertising: Google AdMob and its advertising partners may process identifiers, IP addresses (which can indicate approximate location), ad interactions and diagnostics to serve and measure ads and prevent fraud. Processing depends on your privacy choices, device permissions and applicable settings.

Service providers and choices

We use Google Firebase for account, database, analytics and diagnostic services, and Google AdMob for advertising. Information is processed by these providers to deliver the features described above. See Firebase privacy information and how Google uses information from apps.

Where required, the app presents advertising consent choices. In version 3.5.6 and later, Settings provides Ad privacy choices when Google's privacy form is available. You can also manage advertising/tracking permissions through your device settings. Declining personalized advertising does not prevent ordinary gameplay; ad availability and reward offers can vary.

Optional advertising measurement

Version 3.5.24 and later offers optional Meta advertising measurement. If you allow it, the Meta App Events SDK reports app activation and foreground activity, verified purchase events (product, transaction reference, catalogue amount and currency), and rewarded-ad revenue events (amount, currency and placement). Meta also processes app and device information, installation identifiers and connection information such as IP address to attribute installs, measure campaign results and improve advertising. Advertising ID collection follows your measurement choice and device permissions; on iOS this measurement also requires App Tracking Transparency permission. We do not pass your game account ID, email address, username or chat messages to Meta.

You can decline the measurement prompt or turn off Advertising measurement in Settings without losing ordinary gameplay. Turning it off stops future measurement events from this feature and disables advertising ID collection; it does not erase information already received by Meta. The SDK may initialise and contact Meta for configuration independently of manually logged measurement events. See Meta's Privacy Policy for its handling of information, retention and privacy rights. Advertising measurement permission is separate from Google's ad privacy choices.

Retention and deletion

We retain gameplay and account records while needed to operate your account. You can request deletion in Settings in version 3.5.6 and later, or contact our support email. See the account and data deletion policy for the 14-day manual processing period and records retained only where needed for transaction security or legal obligations. Provider diagnostic retention follows the provider's policies.

Children and updates

The game is not intended for children under 13. Contact us if you believe a child has provided personal information so we can investigate and remove it. We update this page when our practices change and identify the revision date above.