Sign in with Steam

Privacy policy

Updated 29 August 2026

What this site knows about you, where it came from, who else sees it, and how to make it stop. It matters more here than on most sites: your totals are public at the source with or without us, but the record of how they moved over time exists only because we keep it.

The short version

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 advertising and no third-party trackers.

Pages are counted, ours counts them. Every page here, signed in or not, reports its address and title to an analytics instance we run ourselves. It sets no cookie and stores nothing in your browser, which is why there is still no consent banner to click. To switch it off for yourself, set umami.disabled to true in your browser’s local storage.

Nobody is tracked without asking. The only two ways into the member list are signing in yourself and accepting a team invite. There is no page about anyone who has done neither.

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

Who is responsible

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.

What signing in gives us

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.

How you end up here

There are two ways, and only two. You sign in with Steam, which starts the recording for your own account. Or you accept an invitation to a team, which does the same thing: the acceptance is the ask.

Both are choices you make yourself, and that choice is the legal basis for the recording. Nothing is collected about anyone who has made neither, and there is no way for someone else to add you: an invite you never answer stores your SteamID and nothing more, and it disappears if it is cancelled or declined.

What we record about players

From then on we poll the community’s public stats 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 tracking started, which polling cadence you are on, whether the one-off onboarding sweep has run, and your visibility setting. 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.

What we do not collect

  • Nothing that ties a page to your account

    Pages are counted, but never together with who you are: no SteamID, no session, no identifier from your sign-in is ever sent with a page view. What we keep about players is described below and is not joined to the counting.

  • No analytics vendor

    No third-party analytics, no session recording, no heatmaps, no fingerprinting, no A/B tests, no cross-site tracking, no advertising identifiers. Pages are counted by software we run ourselves, and what it receives is written out under who gets what.

  • No advertising

    No ad network, no conversion pixels, no audiences shared with anyone. Your data is not for sale and there is no arrangement under which it could become someone else's.

  • Nothing from inside the game

    No plugin, no server access, no chat, no logs, no voice. If it is not in the community's public stats, we do not have it and cannot get it.

Cookies

Your session
__Host-rs_session, 30 days
A sign-in in progress
__Host-rs_login, 10 minutes
Anything else
None

The session cookie holds your SteamID, your Steam name and avatar, and an expiry. It is signed so that nobody can edit it into somebody else’s account, and it is deliberately not encrypted: every field in it is already on your public Steam profile, and hiding them would be theatre rather than protection. Your browser never lets a script read it.

The second cookie exists only between leaving for Steam and coming back, and it is what stops someone from handing you a link that signs you in as them.

Both are there to run a sign-in you asked for, so neither is a tracking cookie and there is nothing here to consent to. Signing out clears the session cookie with a response carrying the same attributes that set it.

Your IP address

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.

Who else sees any of it

  • Steam (Valve)

    The sign-in itself, a lookup of your public profile for your name and avatar, and your friends list when you open the friends page. The friends list is read on request, held in memory for 10 minutes and never written down.

  • The communities we read

    To ask for your numbers we have to send your SteamID to the community that publishes them, so they can see which IDs we ask about. They publish those numbers under their own name already, which is how this site can exist.

  • Cloudflare

    Hosting, the database and the rate limiting at the edge. Everything stored here lives on their infrastructure, so treat the storage as global rather than as sitting in one country.

  • Our own page counting

    Every page sends its address, its title, the page you came from, your screen size and your browser language to an analytics instance we run ourselves. It sets no cookie and writes nothing to your browser. This includes the signed-in pages: on a team page the address contains the team slug and the title is the team name, so a private team's name reaches it too. Nothing is shared with anyone, and no other service is connected to it.

  • Nobody else

    No third-party analytics, no ad network, no data broker, nothing sold and nothing traded. A binding legal order is the only thing that could add a name to this list, and no back door has been built for one.

How long it is kept

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.

The switch you have

Profile visibility covers one thing: whether your row and your numbers appear on team pages that are shared by link. It is public unless you set it otherwise, and setting it to private takes one click and takes effect everywhere at once. Your teammates always see your row, your feed and your AFK meter: that is what joining a team means, and leaving the team is how you stop it.

The switch stops the publishing, never the recording, and it cannot freeze your totals: they are public at the source with or without us. The way to stop the recording itself is deletion.

Deleting your data, and your other rights

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.

A deletion also stands: your SteamID is remembered as deleted, and nothing else, so nothing quietly brings you back. That single entry is the only way to keep the promise, and it is why it stays.

What survives it

The community you played on keeps its own copy of your stats, which was public before we read it and is theirs, 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.

If this changes

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 29 August 2026.

At a glance

Controller
One person, Sweden
Identity
SteamID64
Who is tracked
Members only, by their own choice
Profile
Public by default
Analytics
None
Advertising
None
Cookies
Two, both necessary
Data sold
Never
Deletion
By mail, by hand

Your controls

Your visibility setting lives on one page and takes effect immediately and everywhere. Nobody is asked first, not even the people in your teams.

Contact

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

The rest of it

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