Effective date: 7 November 2026
This policy describes the Android app LockOn. It explains what information stays on your phone, what is sent only to a computer you choose on your local network, the public reference files the app may download, and the usage data and crash reports sent to Google. LockOn has no user accounts and no advertising.
LockOn is published independently. The publisher does not operate a login service or a server that stores your matches. For privacy questions, use the developer contact under App support on the LockOn Google Play listing.
The following is saved in the app’s private storage and is not uploaded to the publisher:
You can erase match history with Clear in History. That does not erase research marks. Uninstalling LockOn removes the app’s local storage, including settings, research marks, and the catalog cache. It does not delete a backup already stored in your device account.
When you enter a computer address, LockOn reads match data from the game's local web server over HTTP on your local network. This connection is not encrypted. It is read-only and does not carry the Bridge pairing token. The publisher does not receive these requests.
If you turn on LockOn Bridge, the app also talks to the Bridge program on that same computer over HTTPS. The app verifies the Bridge certificate against the fingerprint in your pairing code. Bridge can send match-result values to the phone. The pairing code’s access token is sent only to that Bridge computer to authenticate the phone. It is not sent to the publisher, the public vehicle catalog, the research-tree provider, or Firebase.
The optional Windows companion handles text recognition separately. If OCR.space is selected in Bridge, the Windows companion sends crops of the War Thunder results screen to OCR.space. With EasyOCR set up and selected, recognition runs on the PC. The Android app receives recognized results from Bridge and does not upload these screenshots. See Bridge data and privacy and the OCR.space privacy policy.
To show vehicle details, LockOn may request pages from a public catalog, currently https://wtvehiclesapi.duckdns.org, and then load vehicle images from the web addresses included in that catalog. Those requests include a technical User-Agent string and your network address, which any website sees when a phone connects to it. They do not include your name, a game password, your computer’s local address, or your match history. Replies are stored only on this phone. If the catalog is unreachable, the app keeps using data it already has or names from the local match.
The catalog is operated independently. Its own site policy applies to the connection logs it keeps.
To calculate remaining research, LockOn may download a public vehicle tree from https://wtgrind.app/data/vehicles.json, published by wtgrind.app. The file lists research costs, silver lion prices, and which vehicle must be researched first. The request includes a technical User-Agent string and your network address, which any website sees when a phone connects to it. It does not include your name, a game password, your computer’s local address, your match history, or which vehicles you marked. Your researched vehicles and chosen goals stay only on this phone. Research costs are provided by wtgrind.app. LockOn is not affiliated with that site.
LockOn uses Google Firebase Analytics and Firebase Crashlytics to understand how the app is used and to fix crashes. The app sends analytics events and crash reports to Google over encrypted connections for the LockOn Firebase project. Typical data includes:
LockOn does not include match history, your PC's local address, Bridge pairing codes or Gaijin account details in its analytics events or crash report metadata. The identifiers above identify an installation of LockOn and are separate from the Android advertising ID, which LockOn does not collect. See Privacy and Security in Firebase for details on Google's processing.
For LockOn, Google Analytics is configured to retain event data for 2 months and user-level data for 14 months. New activity resets the retention period for user-level data associated with that installation. These settings do not apply to standard reports based on aggregated data. Google automatically deletes expired data covered by these settings. See Google Analytics data retention.
Firebase Crashlytics keeps crash traces and associated identifiers for 90 days before beginning to remove them from live and backup systems. Removing LockOn or clearing its storage does not delete analytics or diagnostics already sent to Google. LockOn has no account and no in-app tool to request deletion of previously uploaded analytics or crash reports.
If you allow notifications, LockOn uses them only to show that a session is being recorded or that the app is checking whether your computer is reachable. They are not used for marketing.
Android backup and device transfer can include match history, research marks, and the vehicle-catalog cache. The settings file is excluded, so a restored phone does not receive the PC address, Bridge port, pairing code, or language. That copy is handled by the device maker or account provider, not by the publisher of LockOn. Turning backup off stops new copies. Copies already stored in that account remain until you delete them.
LockOn is not directed at children under 13, and the publisher does not knowingly collect personal information from children.
If this policy changes, the updated text will be posted at this address with a new effective date.