Privacy policy

What this covers

This policy covers the OverAnalyzer web app and its optional Windows capture companion. The companion takes ordinary screenshots only when you ask it to; it does not read the game process or draw an in-game overlay.

What we collect

• Your email address and sign-in identity, handled by Supabase when hosted authentication is enabled. If you use Google sign-in, OverAnalyzer receives your email address, not your Google password.
• The in-game name you enter during onboarding so the service can identify your row on a scoreboard.
• Game Report screenshots you upload, plus the match statistics, OCR results, and corrections extracted from them. A Game Report leaderboard includes the in-game names, heroes, and statistics of other players in the lobby.
• If you pair the optional companion, a device-key record. The plaintext key is shown once; the backend stores a SHA-256 hash rather than the usable key.
• Optional, scrubbed error reports if the deployment has error reporting configured. This is not enabled by default; the reporting code removes request bodies, tokens, user data, and exception messages before sending an event.

How we use it

• To process your screenshots, show your match history, and calculate the analytics you request.
• To retain the original screenshots as the source of truth so a match can be re-processed when OCR improves.
• To authenticate your account, operate paired devices, prevent abuse, and fix service errors.

What we do not do

• No advertising or ad network is part of the app.
• We do not sell your screenshots, match history, or extracted statistics.
• OverAnalyzer does not connect to your Battle.net account, read game memory, hook the game process, inject code, or render an in-game overlay.

Other players in your screenshots

Your scoreboard capture may contain other players' in-game names, heroes, and match statistics. That information is retained as part of your match record and is not linked by OverAnalyzer to a real-world identity. Do not upload screenshots you are not allowed to use, and do not use the service to harass other players.

Account match data is intended to be account-scoped. The public demo is a separate read-only showcase and may contain seeded fixture data with real in-game names; do not treat the demo as a private account.

Storage and retention

The app supports local filesystem storage for development or self-hosting and private S3-compatible object storage, including Cloudflare R2, for a hosted deployment. Match data is stored in SQLite or Postgres, depending on deployment configuration. Screenshots are retained until you delete the account or the deployment removes them under its own retention rules. Requests in a hosted deployment are served over HTTPS.

Deleting your data

Account owners can delete their account from Settings. The deletion removes the account's matches, raw screenshots, OCR history, corrections, rank calibrations, player and group records, and paired device keys from the configured database and object storage. It is permanent; keep your own copies of anything you want to preserve.