Privacy

What the plugins send, what is public, how to turn it off, and what this site stores in your browser.

What CS2AC sends by default

With the default setting cs2ac_telemetry_enabled "1", a CS2AC server sends this to my report service:

  • Each detection: a random report ID, a coded ID for the license or install, the time (UTC), the CS2AC and CS2 versions, the player’s name and SteamID64 (when known), the check, its evidence in English, the action asked for and what happened, the map, the server name and the server tick.
  • With the chat filter on (the default), each hidden hate message, swearing warning and gag, including the hidden message.
  • 3D replays (on by default on Linux servers): positions, aim and body boxes of the players around the detection.
  • From CS2AC 2.5.0, behaviour data for every player: see "Behaviour data" below.

Never sent: other chat, voice, the server’s full settings, license keys, partner tokens, Discord links, GSLTs, or player activity unrelated to a detection (except the behaviour data below).

CS2FOW and CS2SC check their license with my license server and download updates. They send no player reports. On a server that also runs CS2AC, CS2FOW tells CS2AC which players can see and hear each other, inside the server only. Discord and JSON webhooks you set up go to your own addresses, not to me.

Behaviour data (CS2AC 2.5.0 and later)

With cs2ac_telemetry_enabled "1" and cs2ac_behaviour_enabled 1 (both the default), CS2AC also sends:

  • Per player and per 10 minutes of play: counts and histograms of how the player aims (how the crosshair moves onto enemies and follows them, mouse steps), shoots (reaction, accuracy per bullet, hits by body part, kinds of kills, flashes), times button presses, moves (jumps, strafes, movement keys), turns the view, and of the connection (loss, choke, ping, command timing), with the round’s setting (game mode, time in warmup, headshot-only, share of bots among the enemies). No stream of positions or inputs. From CS2AC 2.6.0, each record also says which match it belongs to (a number made from the time the match started on the server), and reaction is measured also while the Triggerbot check is off.
  • In each of those 10-minute records, a few single aim movements onto enemies, picked at random: their size, steps, the speed of every step and how each step compares with the one before, how straight they were, how far off they ended, and whether a damaging shot or a headshot followed.
  • Whether enemies near the crosshair were visible, spotted by the game, or could be heard, and how the view follows a moving enemy that is visible or hidden, so that wall-hack checks can be tested. From CS2AC 2.6.0, the view following is also split by whether the game had spotted that enemy for the player.
  • About 5 seconds of a player’s raw input (view angles, mouse movement, buttons, movement values and the timing inside each tick), with the direction to the nearest enemy and the player’s hits and kills in those seconds, when a check fires on them, or when a new check under test would have, or nearly would have.
  • Once an hour on each server, at a random moment, one clip like that of normal play from a living player picked at random (never a bot, and only a player who already saw the chat line), so new checks can be tested on how real players play. It is stored under that player’s code like any clip. Being picked says nothing about that player.
  • What a new check under test would have done about a player, with its numbers. It never acts.
  • Anonymous map totals: where players stand, fight, shoot and plant on each map, with no player or code attached.
  • With each batch: the player’s SteamID64, the map, the CS2AC version, the server’s player limit and game mode, and whether CS2FOW runs. The service also stores which license or partner platform the batch came from. Batches are sent once an hour, and from CS2AC 2.6.0 also when a match ends or the map changes.

Why: To test every check on real play before it acts, so that cheats which stay under today’s limits can be caught without banning real players by mistake.

Linked to you by a code: The SteamID64 is replaced the moment it arrives by a code made with a secret key only the service knows (HMAC-SHA256). The SteamID64 itself is never stored. Without that key the code cannot be turned back into a SteamID64; with it, the service can find the code of a SteamID64 it is given, which is how copies, deletions, objections and detection reports are matched. A clip taken at a detection also points to that detection’s report. The same code is made from detection reports and from my own Cheater, Clean or Unsure labels, so the data is pseudonymous personal data, not anonymous.

Comparing accounts: I compare the play statistics of players on all servers with those of players I confirmed as cheaters, to find new accounts of returning cheaters, and I flag accounts whose play suddenly changes (for example a shared or sold account). For this the service keeps a play profile per code, deleted with that code’s data. Only I look at the results. No server is told, nothing happens automatically, and a match alone is never the reason for a ban. Because this tells accounts apart by how a person plays, it may count as biometric data under the GDPR.

How long: Summaries (counts and histograms per player and day, and from CS2AC 2.6.0 per player and match) are kept 180 days, then deleted. The full records and input clips are kept as long as a fixed storage limit allows, at most 180 days; when the limit is reached, the oldest are deleted first. The records of players I confirmed as cheaters, of players banned by CS2AC, and of my own cheat tests are kept 2 years and are deleted last. The service stores the hour a batch was made and the hour it arrived, not the exact time. Until a game server sends its batch, the records wait on that server with the SteamID64, readable by its owner and host. If the owner turns behaviour data off, CS2AC deletes the records still waiting.

Who sees it: Only I see the records once they reach the service. A server owner sees totals for their own server, a partner platform for its own servers, and network-wide totals may be shown without any server or player. Used only for karola3vax products (CS2AC, CS2FOW and later ones), never sold or given to anyone.

How players are told: Each player gets one private chat line, at most once every 30 days: "Your gameplay is recorded. Type !privacy." Typing !privacy shows what is recorded, why, how long it is kept and where to ask for deletion. A server owner can point the link to their own privacy page.

Your behaviour data: copy, deletion or correction

You can ask for a copy of your behaviour data, for its deletion, or for it to be corrected (for example a wrong Cheater label). Message me on Discord with your SteamID64; I first ask you to show that the Steam account is yours. I answer within one month. A deletion removes your records, clips, labels and play profile from the service, and for 30 days it also drops records of yours that were still waiting on a game server. After that, new play is stored again unless you also object.

Discord: karola3vax

Your right to object

You can object to this processing at any time. Once I record your objection, the service drops your new behaviour data when it arrives and deletes what it has stored, unless I confirmed you as a cheater: then I keep that data while I look at your objection, and I tell you the outcome.

To object, message me on Discord: karola3vax.

What is public

  • Detection reports are public on the reports page with the player’s name and SteamID64, the check, the evidence, map, server name and server address.
  • A 3D replay is public with its report. The reported player stays named; other players’ names and SteamIDs are removed.
  • Chat filter entries are public on the chat filter page with the player’s name and SteamID. The hidden message stays covered until a visitor chooses to show it.
  • Servers on private partner platforms are left out of all public reports, totals and replays.
  • Reports are kept for 180 days. Replays are deleted after 180 days, or sooner to free space.

See them on the public reports and the chat filter pages.

Turning it off (server owners)

Change these in cs2ac.cfg, save, then run cs2ac_reload.

cs2ac_telemetry_enabled "0"
Stops new public reports, chat filter reports, replay uploads and behaviour data. Detections, punishments and your own webhooks keep working. Reports already waiting on the server stay there and are sent only if you turn this back on; behaviour data still waiting is deleted.
cs2ac_behaviour_enabled 0
Stops behaviour data only, and deletes what still waits on the server. Public reports, chat filter reports and 3D replays keep working.
cs2ac_replay3d_enabled 0
Stops 3D replays only.
cs2ac_chat_filter_enabled 0
Turns the chat filter off, so it hides and reports nothing.

Asking for a change (players)

If a public report or chat filter entry is about you, you can ask for a correction, a redaction (for example, hiding your name) or a removal. I read every request myself. The report change form sends what you type: the request type, the report reference, your reason, and a contact only if you give one.

Request a report change

What this site stores

k3v-themeCookie and local storage
Your light or dark theme choice, shared across karola3vax.com sites. Kept for one year.
Game and demo settingsLocal storage
The Mirage game’s mouse sensitivity and the CS2SC menu demo’s sound setting, if you change them.
Replay viewerSession storage and IndexedDB
The report you opened a replay from, for this tab only, and a cache of public map files (up to 512 MB) so replays load faster next time.
Visit countsCloudflare Web Analytics
Counts page visits without cookies.

Questions? Message me on Discord: karola3vax.