Privacy

Applies to the OddsHUD public build (zero-configuration version). Last updated: 2026-10-15.

1. Collection and use

The plugin collects battle data the client can access in the current battle, structured as meta/raw/query. The raw battle roster may contain in-game nicknames, numeric account IDs, clan tags and vehicle states; these fields may be linked to a game account. The random install ID contains no account information, but that does not make the battle data anonymous.

Collected data is used for win-chance model research, quality evaluation and service operation; the final battle result is never mixed into the time-slice inputs.

2. Storage and transmission

The public build does not store local battle sample JSONL. The plugin stores a random install ID, upload credentials generated locally on this machine and the state it needs to run; dev/replay builds additionally store local battle samples for operator use only and must not be distributed publicly.

Uploads use WSS with CA and hostname verification. The public build ships no shared operator token, so players never enter a key or run a launcher. The first authentication registers the install identity automatically, and the server stores a hash of the credentials rather than the plaintext. That identity isolates installs and enforces quotas; it is not real-name verification of a game account, and public registration cannot prove the data came from a genuine client. Do not share your credentials; the local credential file is not a promise of DPAPI encryption.

3. Risks, quotas and revocation

Automatic registration is subject to quotas on connections, registrations, message size, install identities and source addresses; an install identity can be revoked by the server. Creating a new identity may bypass the per-identity limit, so source quotas and operator monitoring remain necessary, and no abuse-free guarantee is made.

4. Disabling and deletion

Closing the game and removing the plugin stops further collection. Deleting the local %LOCALAPPDATA%/oddshud/ directory loses the install identity and runtime state; if the plugin is still present, the next launch creates a new identity, which does not count as disabling it. Server-side history is deleted on manual request to the operator; there is currently no self-service deletion console, automatic credential rotation or retention-based auto-cleanup.

5. Site analytics

Analytics here is first-party: no third-party analytics SDK, advertising or tracking script is embedded, and no Cookie is used for cross-site tracking. When you open a page, your browser sends the site server one small request that carries no page content and records: visit time, page path and interface language, referring page (Referer), browser User-Agent, screen size and timezone offset, plus a random visitor id generated by this site and kept in browser localStorage (you can clear it at any time). The server also records the request IP address, used for country/region statistics and abuse prevention.

Two kinds of interaction are counted as well: clicks on the plugin and localization-pack downloads (including file name and version), and events of the demo video on the home page (play, pause, progress, completion). This data is used only to understand site usage and improve the content; it is not used for advertising, is not merged with the battle data collected by the plugin, and is not sold or shared with third parties. Clearing site data in your browser resets the random visitor id, but server logs already written are retained as described in the next section.

6. Contact

For privacy questions or requests to delete server-side history, reach the operator through the OddsHUD community QQ group 1129048784.