Privacy policy

One identity, and it is your SteamID. Signing in with Steam returns your SteamID64 and nothing else: no password, no token, no email address.

We keep counters, not conversations. What is stored is the public numbers we polled for you and how they moved. Nothing from inside the game, nothing you type, nothing from anywhere else on the internet.

Two cookies, both necessary. One carries your session, one lives for ten minutes during a Steam sign-in. No analytics, no advertising, no third-party trackers, which is why there is no consent banner to click.

You can have it all deleted. That removes every reading we ever took of your counters. It is the only way to stop the recording, and it is meant to be used.

Ruststats.co is run by one person in Sweden, and that person is the controller for everything described here. There is no company, no privacy department and no form to fill in. Mail is the way in, and it reaches a human.

Steam’s OpenID answers exactly one question: does this browser control this SteamID64. It hands over no password, no token and no email address, and it gives us no access to your Steam account or your library.

Your persona name and avatar come from a separate lookup of your public Steam profile. They live in the session cookie rather than in the database, because there is no column for them: the site reads them from Steam again every time you sign in, which is also why a name change on Steam turns up here on its own.

You need a Steam account for any of this, and Steam sets its own rules about who may hold one. If a child’s account has ended up here, mail me and it goes.

Becoming a member is what starts the recording. From then on we poll the public leaderboards for your SteamID every 15 minutes while your counters are moving, and about once an hour while they are not.

The record itself

Each reading is the difference since the one before it, stored per server and per wipe, alongside a running total and a summary that is frozen when a wipe ends. That record is the site. A leaderboard says where you stand; only our own history says how you got there, which is the whole reason it is worth protecting.

The account row

Next to it we keep when you joined, which polling cadence you are on, whether the one-off onboarding sweep has run, and your two privacy settings. Team membership is one row per team you are in, and an unanswered invitation is a row that disappears the moment it is answered either way.

Server level totals

Readings are also added up per server and per fifteen minutes, with nobody named. A bucket that had fewer than five tracked players in it is never published, because a total covering one player is that player’s data with a different label on it.

The public routes that cost something, the search field and the sign-in, are rate limited per address. The counting happens in Cloudflare’s edge, where your address is the key in a counter that lives for seconds. It never reaches our database and we never write it to a log of our own.

Cloudflare, as the host, keeps its own request logs under its own terms. That is true of every site behind them, and it is the one piece of this we do not control.

Nothing here expires on a clock. We hold your record for as long as you are a member, which is exactly what makes a chart covering a year possible at all, and it stays until you ask for it to go.

Fine grained readings are meant to be thinned: once a wipe has been over for a week, its fifteen minute rows become hourly ones and the detail is dropped. That thinning is not running yet, so today everything we have ever polled is still stored at full resolution. The hourly series and the per wipe summaries are kept indefinitely, because they are the history the site exists to show.

Sign in once and never return and the polling drops to hourly, then finds nothing moving. The record still stands until it is deleted, so if you want it gone, ask.

Profile visibility covers your performance: whether your player page may be indexed by search engines, and whether your row and your numbers appear on public team pages.

Online activity covers your presence: whether anyone holding the link can tell that you are at your computer right now. It is a separate switch because it is a separate question. Your totals are public at the source with or without us, but the timestamps only exist because we poll every 15 minutes, so they are ours to stop publishing.

Neither switch stops the recording, and neither can freeze your totals. Someone reloading your page often enough, or reading the source’s own leaderboard, can still tell that something changed. What goes away is being able to read it off in a single glance. The way to stop the recording itself is deletion.

You can ask for a copy of what we hold, ask for it to be corrected, ask for it to be deleted, and object to us holding it at all. Under the GDPR those are your rights, and this is a site run by one person, so there is no process to fight through: ask, and it happens.

The delete button is not live yet

It is drawn on the settings page and switched off, because the code behind it has not been written. Until it exists, mail me with the SteamID you want removed. I will check that the account is yours before anything is deleted, run it by hand, and write back when it is done.

What deletion removes

Every reading we ever took of your counters, your per wipe summaries, your running totals, and your membership, so the polling stops on the next cycle. It is permanent, and there is no backup copy to restore you from later.

What survives it

Server level totals stay as anonymous statistics with nobody named, and only where enough tracked players were in them to stay anonymous. The community you played on keeps its own copy of your stats, which is theirs and never ours to delete.

If you think this was handled badly

Mail me first, because one person can usually fix it the same week. You can also complain to the Swedish Authority for Privacy Protection (IMY), which supervises us, or to the data protection authority in the EU country where you live.

A new version gets a new date at the top, and a change that means we store something new is written out in plain words instead of being folded into a sentence that was already there. This version is from 22 August 2026.

Both privacy settings live on one page, and both take effect immediately and everywhere. Nobody is asked first, not even the people in your teams.

Deletion requests, questions about anything on this page, or a correction: same address, same person.

The terms cover what you may do with the site. About covers where the numbers come from and how often we read them.