Privacy Policy for Jet Wars

Last updated: October 17, 2026

Jet Wars is published by BESTAPPS LLC, Florida, United States. This policy explains the information processed by the game and its service providers. Contact us at support@jetwars.xyz.

The current public policy is jetwars.xyz/privacypolicy. Instructions for privacy choices and deletion requests are at jetwars.xyz/data-deletion.

1. Versions and platforms

This policy covers the iOS and Android editions. Features and SDK availability differ by platform and version. Meta measurement is available in iOS 1.3.4 and later, and Android 1.3.4 and later after release, subject to the choices described below. Posting this policy does not install an update or enable Meta measurement in an older build.

• iOS versions 1.2 and earlier did not include the advertising or analytics SDKs described below.
• iOS versions 1.3 through 1.3.3 include Google AdMob rewarded advertising and Google Analytics for Firebase. The earlier policy incorrectly described analytics as a future addition; this policy corrects that description.
• iOS version 1.3.4 adds Meta advertising measurement, additional gameplay and monetization events, and in-game privacy controls. Meta event sharing follows your iOS tracking authorization and can also be turned off independently inside the game.
• iOS version 1.3.8 and Android version 1.3.4 add measurement of how each visit to the game starts and ends, reminder and notification-permission events, screens viewed, app diagnostics, and install-source information, described in sections 3 and 6.
• iOS versions that include Survival leaderboards add optional Apple Game Center sign-in, score posting, and friends' scores, described in section 6.
• iOS version 1.3.9 adds iCloud progress sync through your own Apple account, described in section 2.

Jet Wars does not require a Jet Wars or Facebook account. We do not operate a cloud-save service for your game progress; on iOS 1.3.9 and later your progress can be copied to your own iCloud account, as described in section 2. This does not mean the game collects no data: analytics and advertising providers receive the information described below.

2. Game data stored on your device

The game stores progress, currency balances, aircraft and equipment, upgrades, mission results, settings, purchase-delivery records, daily rewards, offer history, and consent choices in the app's local storage. A callsign and profile icon are also stored locally if you choose them.

A subset of gameplay and purchase activity is sent as analytics or advertising events under the controls described below. Your complete saved game, callsign, typed text, Apple ID, payment-card details, contacts, photos, microphone recordings, and precise GPS location are not included in the game's custom telemetry events. We do not collect an email address or phone number through game registration because there is no game registration.

iCloud progress sync (iOS 1.3.9 and later). When you are signed in to iCloud on your device, the game copies your game progress to the iCloud key-value storage of your Apple account so it can follow you to your other devices and come back after a reinstall: currency balances, aircraft and equipment, upgrades, mission and ranked results, rewards, purchase-delivery records, and your callsign and profile icon. Apple stores this copy under its iCloud terms. We cannot access it, and it is not sent to our analytics or advertising providers; game analytics records only sync status, such as whether a device joined and how long the first download took, with no balances or device identifiers. Settings, consent and privacy choices, and analytics references stay on each device. You can delete the iCloud copy and stop syncing on a device in Settings → Privacy inside the game.

Deleting the app removes its local game data from that device. If iCloud progress sync is on, the copy in your iCloud account remains after the app is deleted; delete it first in Settings → Privacy on each device that syncs. Store-backed purchases, operating-system backups, and information already received by service providers have separate lifecycles; deleting the app does not erase them automatically.

3. Game analytics: Google Analytics for Firebase

We use Firebase Analytics to understand whether players can start and enjoy the game, find difficult missions, measure retention, diagnose gameplay funnels, and understand purchases and rewarded advertisements. Analytics is enabled by default. In iOS 1.3.4 and later you can change it in Settings → Privacy inside Jet Wars without losing game features or rewards.

The game's analytics events include:

• App opens and sessions, tutorial completion or skipping, first-mission completion, and first-time mission clears.
• Campaign mission starts and endings: authored mission name and index, chapter, objective, difficulty, selected aircraft, attempt count, outcome, failure or exit reason, duration, score, and enemy counts.
• Store visits and the in-game surface that opened the store, and checkout starts with the selected product, price, and currency.
• Completed rewarded advertisements and their in-game placement and reward; where available, impression and advertising-revenue information such as placement, value, and currency.
• Verified in-app purchases, including the product identifier, value, and currency. These are purchase records, not payment-card details.
• How each visit starts and ends: whether the game was opened from one of its own reminder notifications (and which kind of reminder), from a link (recorded only as a category, such as an advertising link or the Jet Wars website, never the link itself), or directly; which reminders were shown while you were away and how long before you returned; how long you were away and how long the visit lasted; and the screen in use when you left.
• Screens viewed in the game, choices made in the game's notification prompt and the system permission request, and later changes to notification permission in device settings.
• Broad segments used to compare groups of players: notification-permission status, graphics-quality tier, whether a purchase has been made, a campaign-progress range, and install source (see section 6).
• Additional fixed gameplay progression and monetization milestones supported by the installed version. The game sends predefined event names and structured values, not player-written text or recordings of gameplay.

App diagnostics. In iOS 1.3.8 and later, if you share analytics with app developers in iOS Settings, Apple's MetricKit gives the game daily summaries of how sessions ended (for example normal exits, memory or watchdog terminations, and crashes), launch and hang durations, and peak memory use, plus crash and hang reports. The game forwards counts, durations, exception and signal types, and code locations within the game's own program to Firebase Analytics. It does not forward memory contents, file paths, or error messages. On Android, the game records the reason Android reports for how its previous session ended (such as a crash, an unresponsive app, low memory, an update, or being closed by you) with approximate memory use at that time, and the level at which Android is currently restricting the game's background activity, which affects whether reminders are delivered.

Firebase also processes an app-instance identifier, app and device information, session and lifecycle information, and approximate location derived from network information. Its StoreKit and Google Play integrations can record purchase events automatically. Our custom event code does not supply a player's name, email, callsign, Facebook account, or a shared cross-service user ID. The Firebase configuration disables advertising-identifier collection.

An app-instance identifier lets events from an installation be grouped together. These records are pseudonymous, not necessarily anonymous. Google processes event-level records, and we use the available Google Analytics reports to understand game activity. If we export analytics records, including to Google's BigQuery service, those copies require separate retention and deletion handling. We do not use analytics to identify a player by their real-world name.

Turning game analytics off stops the game's Firebase analytics collection going forward. Resetting its analytics reference clears local analytics data and changes the local app-instance reference; it does not submit a request to erase historical server-side records. See section 8 before resetting if you want to request deletion of earlier data.

Provider information: Google privacy policy, Firebase privacy and security, and Google Analytics data collection.

4. Meta advertising measurement

Available in iOS 1.3.4 and later, and Android 1.3.4 and later after release. We use the Meta SDK to measure ads promoting Jet Wars on Meta services and understand which ads lead to installs, engaged players, and purchases. This integration does not add Facebook login to the game or display Meta advertisements inside it.

On iOS, Meta advertising measurement follows Apple's App Tracking Transparency permission by default. Allowing tracking enables Meta measurement unless you have turned it off in Settings → Privacy inside Jet Wars. Refusing or restricting iOS tracking keeps Meta measurement inactive. If you previously allowed tracking, that permission also applies when you install this update; a saved in-game Off choice remains off. Refusing tracking or turning measurement off does not prevent play, change prices, or reduce rewards. You can change iOS authorization in iOS Settings → Privacy & Security → Tracking.

On Android 1.3.4 and later, Meta measurement starts off. An optional choice after onboarding asks whether to share app activity, purchase information, and the device advertising identifier with Meta for advertising measurement and optimization. Only Allow enables it. You can also change this choice in Settings → Privacy → Meta advertising measurement. Game analytics must also be on. Declining does not affect gameplay, prices, or rewards. Android does not use Apple’s tracking permission. Automatic purchase logging is disabled; the Android app does not report purchase revenue without a verified production paid amount.

Android purchase verification, starting with build 10308 after release. When game analytics and Meta measurement are both enabled, the game can send a newly delivered Google Play purchase token, product identifiers, and a random installation-specific verification value over HTTPS to our purchase-verification service hosted by Cloudflare. The service checks the purchase with Google to obtain its actual paid amount, currency, and test or refund status. It does not request buyer addresses or payment-card information, grant game content, or process refunds. Network providers process connection information, including the IP address; we use a hash of the IP address for short-term abuse rate limiting. Purchase tokens are used for verification and are not retained in our service database or application logs. Hashed transaction and installation values and minimal verification receipts are kept for approximately 30 days to prevent duplicate reporting, with daily expiration. The app keeps pending tokens in private app storage for retries within a seven-day window and a local reporting ledger to prevent duplicates; expired queue entries and ledger entries older than 31 days are removed when the measurement service runs in the app. Turning either measurement choice off discards the pending queue. Already-started requests may complete, but their result is not forwarded after withdrawal. Meta receives only the permitted purchase product, value, and currency; it does not receive the purchase token or our verification identifiers. Provider information: Cloudflare privacy policy.

When enabled, the integration may send app activation and install-related signals, tutorial completion or skipping, mission starts and outcomes, first-time mission clears, and a milestone after five minutes of active use. It can also send store visits, checkout starts, rewarded-ad completion or impression value, and verified production purchase product, value, and currency events. Mission details include authored mission and chapter, selected difficulty and aircraft where applicable, attempt and outcome, duration, score, and enemy counts. Parameters are limited to the game's predefined event fields. We do not send callsigns, player-written text, contact details, payment-card details, or saved-game files in these events, and do not use advanced matching with names, emails, or phone numbers.

The Meta SDK may also process app and device information, network information such as IP address, SDK or app-instance identifiers, and the advertising identifier when the applicable permissions and your choices permit it. Meta may associate permitted event data with information from its own services for advertising attribution, campaign optimization, measurement, and related purposes described in its policies. This can constitute tracking, which is why the game requires iOS tracking authorization on iOS, a separate opt-in on Android, and honors the in-game measurement switch.

Turning the in-game choice off stops forwarding new game events to Meta. It does not undo data already sent, delete provider records, or guarantee that an already initialized SDK makes no further requests, such as completing a request already in progress. The game's privacy controls do not remove a Facebook or Instagram account.

Provider information: Meta privacy policy and Meta Business Tools Terms.

5. Rewarded advertising: Google AdMob

Jet Wars offers optional rewarded video advertisements supplied by Google AdMob. You choose whether to watch an advertisement for the stated reward. The game does not require you to accept personalized advertising to receive that reward.

After the applicable advertising choices and iOS tracking request have been handled, the advertising SDK can initialize and preload an ad before you press a Watch button. Data processing can therefore occur while preparing advertisements, as well as while showing them. Deciding not to watch an ad is different from withdrawing consent to data processing.

Depending on your choices and the applicable SDK configuration, AdMob may process:

• IP address and approximate location, device or app-scoped identifiers, and an advertising identifier where permitted.
• Device and app information, including operating-system and app version information.
• Ad requests, impressions, video views, clicks, completion and reward information, and related timestamps.
• SDK crash, performance, and other diagnostic information used to provide, secure, and improve advertising services.

Google uses this information for advertising delivery, measurement, fraud prevention, diagnostics, and, where permitted, personalization. We receive advertising reports and revenue information. Reward and impression events may also be included in game analytics or consented Meta measurement as described above.

The Google User Messaging Platform handles advertising consent messages where required. These messages and your iOS tracking choice serve different purposes. Refusing iOS tracking prevents access to the IDFA; it does not mean every contextual advertising or SDK diagnostic request stops. Advertising availability and the data used also depend on your other consent choices and Google's requirements.

Provider information: Google privacy policy, Google partner information, and AdMob data disclosure.

6. Other connections and services

Purchases. Apple processes iOS purchases through the App Store and StoreKit. The game receives signed transaction information to deliver purchases and prevent duplicate delivery. Analytics may include product, price, and currency. We do not receive your full payment-card number or Apple account password. Apple handles its own purchase records and refund decisions. Android store purchases are handled by the applicable store, including Google Play where used.

Apple aggregate install attribution. In iOS 1.3.4 and later, the production game asks Apple's SKAdNetwork to register a baseline install conversion value of zero. This can happen even when game analytics or Meta measurement is off or iOS tracking is refused. That registration does not initialize Meta, access the advertising identifier, or include gameplay or purchase details. Apple controls attribution eligibility, privacy thresholds, delays, and postback delivery. These privacy-preserving reports are separate from consented Meta app-event forwarding. We do not use device fingerprinting to work around a refused tracking choice.

Install source. In iOS 1.3.8 and later, while game analytics is on, the game asks Apple's AdServices service whether the installation came from an Apple Ads campaign, using a short-lived token issued by iOS. Apple returns whether it did and, if so, campaign, ad group, and keyword identifiers, the type of ad interaction, and the country or region, which the game records in analytics. This does not access the advertising identifier or require tracking permission. On Android, the game reads the referral information Google Play attaches to an install (such as campaign source, medium, and name) and which app store installed the game, and records shortened, sanitized values in analytics.

Game Center (iOS). In iOS versions that include Survival leaderboards, if you are signed in to Apple Game Center, the game sends each finished Survival score to Apple's Game Center leaderboards, together with a small number describing that run (helmet, aircraft, leg reached, kills, run length, and game build). Your scores, Game Center name, and Game Center photo are visible to other Game Center players under Apple's Game Center terms. To show the leaderboards, the game reads your Game Center name and photo and the Survival leaderboards and, only if you allow it, your Game Center friends list, so it can show friends' scores. Your in-game callsign is not sent to Game Center. We do not store Game Center data on our servers or send it to our analytics or advertising providers; analytics records only whether you are signed in and whether a score upload worked. You can sign out of Game Center or stop sharing your friends list in iOS Settings → Game Center.

Local multiplayer. When you use LAN multiplayer, devices on your local network exchange callsigns, profile icons, aircraft and match information directly. Local-network permission is required. Do not use your real name as a callsign if you do not want other local players to see it. This LAN traffic is not routed through a multiplayer server we operate.

Website and updates. Cloudflare hosts jetwars.xyz and serves public assets, including the app-version policy file requested by the game. Like other web hosts, it receives information needed to serve and protect requests, such as an IP address, timestamp, and request information. The version-check request does not include a game save or an account identifier. Any website operational or security processing is separate from game telemetry.

Notifications. Local reminders are scheduled on your device using operating-system notification permission. Game analytics records which kind of reminder was scheduled, shown, or tapped and when you next returned, so we can tell which reminders are useful; the reminder text itself is not sent. The analytics integration described here does not add Firebase Cloud Messaging or a remote marketing-notification service.

Support. If you contact us, we receive the email address, message, and attachments you choose to send. We use them to respond, investigate your issue, and handle privacy or purchase-support requests. Avoid sending unnecessary sensitive information.

Provider information: Apple privacy policy, Google privacy policy, and Cloudflare privacy policy.

7. Retention, access, and international processing

Local game data remains until you remove or reset it, subject to device backups and store purchase restoration. Analytics and advertising providers maintain their own service records and retention rules.

Google Analytics user and event data is subject to the property's configured retention period and Google's retention rules. That setting does not automatically delete separate exports or aggregate reports. If we export analytics records, including to BigQuery, we manage those copies separately and include identifiable exported records when handling a valid deletion request that we can associate with those records. Provider records may also be retained for security, fraud prevention, transaction requirements, or other permitted purposes.

We restrict access to analytics and support information to people who need it to operate and improve Jet Wars or respond to requests. Service providers may process data in the United States and other countries. Applicable transfer arrangements and provider security practices are described in their linked policies. No internet service or storage system can guarantee absolute security.

8. Your choices and deletion requests

In iOS 1.3.4 and later, open Settings → Privacy inside Jet Wars to control game analytics and Meta advertising measurement, view or copy your Firebase analytics reference, reset that reference, and open privacy information. Meta measurement remains subject to iOS tracking authorization even if you enable its in-game switch. A Firebase analytics reference is not a Facebook ID, Apple ID, or game account.

You can also change tracking and local-network permissions in iOS Settings. Withdrawing consent affects future processing; it does not automatically erase information previously received by providers.

To ask for access, correction, deletion, or other applicable privacy rights, email support@jetwars.xyz. If the request concerns game analytics, copy your analytics reference before resetting it or deleting the app, if possible. We may need limited additional information to identify the relevant records and verify the request. We will not ask for your account password, payment-card details, or an advertising identifier.

We cannot look up anonymous aggregate counts as if they were an individual account. Where data is held independently by Apple, Google, or Meta, we will explain the available provider request routes and assist within our capabilities. Depending on where you live, you may also have rights to object, restrict processing, withdraw consent, or complain to your data-protection authority. We aim to respond within 30 days, subject to applicable requirements and any needed verification.

Full instructions: Privacy choices and data deletion.

9. Children

Jet Wars is not directed to children under 13. We do not ask players to provide a birth date or create a personal profile with us. We do not claim that an age rating alone verifies every player's age. Operating-system restrictions, consent choices, and provider safeguards may affect tracking or advertising availability.

If you believe a child has provided personal information through Jet Wars, contact support@jetwars.xyz so we can investigate and take appropriate action.

10. Changes and contact

We will update this page when the game's data practices change and identify the versions affected. A privacy-policy update is not a substitute for a consent choice required by the game or operating system.

BESTAPPS LLC · Florida, United States

support@jetwars.xyz