Counter-Strike 2's Demo Chat Is Encrypted Now, But Your Old cstracker Log Isn't Going Anywhere

Valve shipped a Counter-Strike 2 update on September 9. Most of it was Cache housekeeping, patched gaps and a closed wallbang spot on B. The line people actually cared about sat lower down: "Chat is now encrypted in demo files using the same rules as CS:GO. Team chat is no longer readable when playing back demo files."

Global chat still exists inside demos, but only the in-game watch UI can render it. Anything parsing the raw file from outside the client now reads noise. One website's entire data pipeline died that afternoon, and that was the point.

That is Valve's own store art for CS2.

How a stats site ended up holding your match chat

On August 27 a post on r/GlobalOffensive told players their matchmaking text chat was publicly searchable. Dexerto's Calum Patterson wrote it up the next day. The site was cstracker.gg, which had been pulling chat out of processed CS2 demos and stapling it to public player profiles with the map and a timestamp attached. You did not need an account there for your messages to show up. Some profiles already held over 2,800 messages across 388 matches. s1mple was in it. So was Ludwig Ahgren, who ended up on X explaining the context behind a few of the lines people were screenshotting.

Then the site added a slur tracking tab with public leaderboards. Its own numbers: roughly 494,000 players analyzed, a slur in 17.6 percent of sampled matches, a bit over 7 percent of players using one at least once, and a projection of about 204 million per year.

The leaderboard is where it went sideways. Kotaku's Lewis Parker reported on September 4 that the top 25 had started out with fewer than 100 instances each. Within days, the minimum n-word count needed to make that board was 976. Nine hundred and seventy six. Creator Thour put it plainly: "People are becoming increasingly racist and abusive in CS2 just to climb a leaderboard that tracks the number of abusive messages they post in chat." One player sitting third wrote in chat that they "gotta get on the slur leaderboard number 1."

Five days later, Valve encrypted the chat.

The patch only works going forward

Nothing in that update reaches back and scrubs what cstracker already copied. Valve never said whether the change applies to demos recorded before the 9th, and I doubt it matters either way. The scraped copy lives in the site's database, on the site's servers, and Valve has no switch for it.

There is a natural limit on the collection side that is worth understanding. Per cstracker's FAQ, Valve keeps matchmaking demos for roughly 30 days, so the site could only ever harvest a rolling window. Its archive is therefore weighted toward August and the first week of September 2026. If you played competitive matchmaking in that stretch and typed something you would not want a team manager reading, it may still be on your profile page right now.

What to actually do about it this week

The one lever that touches the archive is a removal request. cstracker's privacy page takes requests by email to remove, correct or restrict profile data. That is a bad system, because it puts the work on the person whose messages were collected without anyone asking. It is also the only thing available. If you have a sponsor or a team that would care, send it now rather than after someone screenshots it.

Locking down your Steam profile is a weaker move than it sounds. Dexerto described the pipeline as public Steam information plus processed demos, and the demo half never depended on your privacy settings. Going private makes the identity link harder for future scrapes. I would not treat it as a fix for anything already indexed.

Valve's CS2 library artwork, via the Steam store.

Your rank and your ban risk did not move

Worth being clear, because I have watched people read this patch as amnesty. It is not. Valve's servers processed every one of those messages when you sent them. The demo is a recording, not the record.

CS2 handles abusive chat through reports, never through demos. Enough reports for abusive communications and you get a warning first, then a communication penalty that mutes you by default on every official server until someone unmutes you from the scoreboard. You clear it by earning XP on Valve servers, not by waiting it out. None of that involved cstracker and none of it changed on September 9.

Trust Factor is a separate system that people keep folding into this story. It weights cheating signals, which is why a genuinely unpleasant teammate can still sit in green trust while a quiet smurf sits in red. If you would rather check than guess, the nohax.club trust factor breakdown covers which signals actually feed it, and the reputation lookup covers how player reports land on an account.

One thing that still works: the in-game watch UI renders all-chat. Download the demo, watch it in the client, note the round, and file the report with a timestamp you can point at. The evidence path Valve acts on survived the patch intact. What died is the public scoreboard.

The board was the accelerant

Encrypting the chat was correct, and I do not think that is a close call. A leaderboard turns abuse into a score, and scores get farmed. Team Fortress 2 ran the identical cycle years ago with its own slur tracker. The jump from under 100 to 976 in a matter of days is about as clean a demonstration of that as you will get.

Where I get stuck is the 17.6 percent, which was never an artifact of the leaderboard. That figure came out of demos recorded before most players knew anyone was counting. Valve's response to a public measurement of its chat problem was to make the measurement impossible. The same patch shipped no moderation changes at all. Five days after Kotaku ran the story, chat went dark.

So Valve now holds the only complete copy of CS2 chat history. If the real rate is lower than one in six, they are the only ones who can show it.