Anti-Cheat

Privacy & Consent

The MoH Arena launcher collects a small amount of technical data so the anti-cheat can work. This page documents exactly what is collected, why, and how long it is kept.

What We Collect

Data Purpose Source
IP address Matching your launcher session to the game server you connect to; abuse detection. Launcher session start / server join
Hashed hardware identifier Detecting ban evasion and duplicate sessions. We store only a salted hash, never the raw hardware ID. Launcher
Launcher & client version Supporting the right rule profile and diagnosing launch failures. Launcher
Game install path + file check results Verifying the file whitelist. We store the MD5 results, not file contents. Launcher
Cvar & bind snapshot Comparing against the published rules. Only cvars/binds relevant to competitive play are inspected. Launcher
Violation events Admin review, automatic kick policy, published anonymised violation stats. Launcher
Player auth token Linking the session to your MoH Arena identity without a password. Website (issued to your account)

What We Do Not Collect

  • No screenshots or screen captures.
  • No keystroke or mouse-input logging.
  • No process list scanning beyond what the game itself exposes.
  • No files, file contents, or clipboard data from outside the game install directory.
  • No browsing history, personal documents, or other application data.

Consent

On first run, the launcher shows a consent dialog summarising the above. The dialog must be accepted before any session data is sent. Acceptance is recorded on the server with a timestamp and your account ID.

You can withdraw consent at any time by uninstalling the launcher. You may also request deletion of your stored session/violation history by contacting an admin on Discord.

Retention

  • Launcher sessions — kept for 90 days for diagnostic and dispute purposes, then purged.
  • Violation events — kept indefinitely when tied to a ban decision, otherwise purged at 180 days.
  • IP addresses — kept for 30 days then hashed or discarded.
  • Hardware ID hash — kept while the associated account is active.

Retention windows above are the current project policy and may change as the service evolves. Material changes will be announced on Discord and summarised here.