It can't get you banned.

StarStats never touches the game. It reads a text file the game already writes to your own disk, and — only if you set it up — it reads your own RSI profile page using your own login. That's the whole surface.

It does not, by design and not by policy:

• inject a DLL, overlay, or anything else into the game
• attach to the game process or read its memory
• sniff or modify game network traffic
• run macros or automate any in-game action

Those are the things anti-cheat actually watches for, and they are the things a log reader has no reason to do. If you want the long version — including which Windows APIs it uses, in plain terms, and how it compares to tools that do get people banned — it's written up in EAC-SAFETY.md.

We keep whole log lines, not just the bits we read.

Nobody volunteers this, so here it is second. StarStats never goes looking for other players. No rule in the parser reads them — there's nothing that records who was in your instance, who you fought, or who was flying next to you. And your killer's name isn't in a modern log to begin with: CIG stopped writing that line, which is why StarStats has to infer your death from your ship blowing up and you respawning.

Here's the part that isn't flattering. When a line matches a rule, we upload the whole line, exactly as the game wrote it — not just the fields we parsed. We do that so we can re-read old events when the parser gets smarter, without asking you to upload anything again. It also means that if a log line ever happens to name someone else, that text is kept, whether or not anything reads it. We don't search it for handles. We also don't strip them out.

So: no profile of anyone, no way to look up a player who never crossed your path, and nothing that treats another person as data. What there is, is verbatim retention — and we'd rather write that down than let you find it out.

The full detail, including how long it's kept and how to have it removed, is in the privacy policy, section 2.2. It is the section worth reading rather than skimming.

Nothing, until you pair it. Then two locks, both yours.

Install it and it is a local program. It parses your logs on your machine, keeps the result there, and has never spoken to this website about you. There is no account, no upload, nothing to opt out of.

Pairing is the moment that changes. You generate a code on this site and type it into the tray — nothing pairs by accident. From then on the tray does start sending your parsed events. We'd rather say that plainly than let you find out: a paired tray uploads.

What it can't do is make them land. Your account holds a second lock — Cloud sync, off by default — and while it's off the server rejects every batch the tray sends and stores none of them. Two gates: one on your PC, one on your account, and the server-side one is the authority. Turning Cloud sync off later stops the data at the door even if the tray keeps knocking.

What goes up, once both locks are open: the parsed events — logins, deaths, missions, jumps, locations, what you were flying. What never goes up: your chat, your inventory, your currency, your screen. Not as a promise — the parser has no code that can read those things.

Who can see it once it's up is yours to set, per category, from your sharing settings. A public profile is a thing you choose, not a default you have to find and disable.

The one that deserves a straight answer.

To read your RSI profile — your handle, your org, your hangar — StarStats asks you to paste your RSI session cookie. Let's be blunt about what that is: it's the thing that proves to the RSI website that you are you. Anything holding it can act as you on that site.

So: it's stored in your operating system's credential store, not in a config file, and it never leaves your machine — StarStats uses it to talk to RSI directly from your PC, and the result is what syncs, not the cookie. You can revoke it any time by logging out of RSI in your browser, which invalidates the session.

If that trade doesn't sit right with you, don't make it. StarStats works without the cookie; you just lose the RSI-side detail. That's a real option, not a dark pattern with a hidden skip link.

You can take it all back.

Export your whole manifest whenever you like from Settings — the actual data, in NDJSON, CSV or ZIP, not a screenshot of a dashboard. Delete your account and it goes, on the schedule set out in the privacy policy.

The client can re-parse your local logs from scratch, so leaving costs you nothing you can't rebuild. That's deliberate: the point is a record you own, and a record you can't take with you isn't one.

Check my work.

Everything above is a claim. Here's how to stop taking my word for it:

• The whole thing is public, under MPL-2.0. The client, the server, the site. Read the parser and see for yourself what it can and can't touch.
• EAC-SAFETY.md — the long answer to section 01, including the Windows APIs used.
• SECURITY.md — how to report a vulnerability privately. It commits to acknowledging within 7 days and triaging within 30.
• The privacy policy names every sub-processor individually, and gives a retention period per item rather than a vague “as long as necessary”.
• The terms say what happens to your data during the beta, in words rather than lawyer.

One thing that number deserves context on: there is no security team. There is one person, and that 7-day clock is his, around a job and a life. It is a real commitment and it has been kept so far — the issue history is public, so you can check that too rather than believing it. If something looks wrong, email [email protected] and you will get a human, because there is only one.