Privacy Policy

PvP - Tower Defense! · Last updated 18 October 2026

PvP - Tower Defense! (Irongate) can be played against the computer or online without creating a game account. Mobile releases with monetization enabled include advertising and optional purchases. Gameplay analytics helps us improve the game; you can turn it off at any time and still play.

Turning analytics off

Analytics is on by default. To turn it off, tap the Privacy button in the lobby and choose “Don’t share”; choose “Share” to turn it back on. Turning it off stops future gameplay analytics collection and discards pending analytics statistics; it does not automatically delete data already sent. This setting does not disable public leaderboards or remove their records. Your choice is stored on this installation or browser, so choose separately on each device.

What analytics collects

We use Google Analytics for Firebase and Google BigQuery to understand how the game is used. Unless you turn analytics off, information may include:

• App launches, sessions, engagement, returning visits and how you reached the game where available.
• Mode, map and difficulty choices; matchmaking waits and failures; match duration, waves, results, quits and rematches.
• Tower builds, upgrades, sales and board cells; troops sent; gold earned and spent; summaries of damage, kills and castle health.
• App version, device and operating-system information, language, approximate region, loading time, frame timing, memory usage and connection latency.
• Counts of software errors. Our game events exclude raw error messages, player-entered names and room codes.
• Ad placement, loading, impressions and completed rewards; SDK-reported revenue amounts and currency; purchase offers and verified Remove Ads conversions. Test ads are identified separately.

Google Analytics uses an app installation identifier or browser cookies to distinguish visits. Match identifiers relate events from a single game. These identifiers are pseudonymous, not a promise of anonymity. We do not ask for precise location or send your player name to Analytics. Advertising storage and personalisation remain disabled in our Firebase Analytics integration; AdMob has separate privacy choices.

Mobile advertising and choices

Ad-supported Android and iOS releases use Google AdMob. Its SDK can process network addresses, approximate location inferred from an IP address, available device or advertising identifiers, ad interactions and diagnostics to deliver and measure ads and prevent fraud. Processing depends on platform restrictions, audience settings and your choices. See how Google uses information from apps that use its services.

Google’s User Messaging Platform checks which privacy message applies before we request ads. When privacy options are required, open Privacy in the main menu and choose “Ad privacy options” to review them. This is separate from the gameplay analytics switch. Irongate does not request iOS permission to track activity across other companies’ apps.

The tutorial and first unguided Survival run have no automatic ads. Remove Ads disables automatic interstitials and pause banners; optional turret-trial rewarded videos remain available. A rewarded unlock is granted only after confirmed video completion.

Purchases and saved unlocks

Apple or Google processes purchases through your store account; we do not receive your payment-card details. Remove Ads and its mode access can be restored using the same store account. Apple verifies iOS transactions. On Android, the app sends its purchase token over HTTPS to our purchase-verification service, which checks ownership with Google Play before granting access. Purchase tokens and receipts are excluded from game analytics and application logs.

Settings, progress, rewarded mode unlocks, queued turret trials and previously verified purchase access are saved on your device. Local transaction fingerprints prevent repeated purchase callbacks from being counted as new purchases. Rewarded mode unlocks do not have an account-based cross-device restore. A turret trial is consumed when its equipped Survival run starts and expires when that run ends or is quit.

Playing offline

Games against the bot run on your device. If analytics is disabled, the game sends no gameplay analytics. If enabled, the mobile Analytics SDK may store events locally and send them when a connection is available. A small local checkpoint can identify an unfinished match on your next launch; it does not establish whether the app crashed or was closed intentionally.

Playing online

Online play sends your chosen display name, moves and connection information to our match server so it can run the game. The other player can see your display name. Avoid using a real name. Live rooms are held in memory and removed after players leave.

When neither player has turned analytics off, the server can also retain structured gameplay statistics and match results in Google Cloud Logging and BigQuery. These records exclude player names, room codes and IP addresses. If either player turns analytics off during a match, further server analytics for that match stops.

Public leaderboards

Survival records and Versus or Co-op results can be sent to shared leaderboards stored in Google Cloud Firestore. Records can include your display name, another player’s display name, a random installation identifier or match/team identifier, the mode and map, waves or match results, and record timestamps. These records are publicly accessible, and names and results appear on the game’s leaderboards. Avoid using a real name or other personal information.

Leaderboard records remain stored until removed. Leaving a match or turning gameplay analytics off does not delete them or stop future leaderboard submissions. Results saved while offline can be sent when a connection is available. Contact us to request removal, including the display name, mode, map and approximate record date so we can locate the relevant entries.

Service providers and retention

Google operates Firebase Hosting, Cloud Firestore, Cloud Run, Google Analytics and BigQuery. Hosting providers process network information, including IP addresses, to deliver and secure the service. Google Analytics is configured to retain event and user data for 14 months; standard aggregate reports may remain longer. Server analytics exported to BigQuery expires after 365 days. Those analytics retention periods do not apply to public leaderboard records. Other exported records follow the retention settings of the respective services. We use the records to improve gameplay, balance and reliability. We do not sell this data.

See Google’s privacy policy for information about its processing. Contact us about access or deletion requests. Since there are no accounts and analytics excludes display names, a display name alone cannot identify your analytics records.

Children

The game does not require analytics to play. Parents and guardians can turn analytics off using Privacy. Children should not use their real names as online or leaderboard display names.

Changes and contact

Changes will be published here with a new date. Questions about privacy can be sent to Emre Can Akcan at emrekcn@gmail.com.