Dev (TheCodeSaiyan) here. Solo project, been at it about a 5 months, and I've reached the point where I need people who aren't me to break it. Quick version: Star Citizen writes an absurdly detailed diary of everything you do into Game.log. Every session, jump, death, kill, loadout change, contract, purchase. Nobody reads it because it looks like engine vomit. StarStats is a little tray app for Windows and Linux that parses that file on your own machine and turns it into a timeline you'd actually want to scroll through, plus a web dashboard if you decide to sync. What's in it right now: a live timeline of your session as you play (readable events, not log lines), journeys showing where you went (system, station, moon), contracts folded into one run each with objectives and outcome and a page you can look back at, a loadout paperdoll of what you were wearing down to the mags, your hangar, sharing that's private by default with scoped slices you can revoke whenever, and a browsable catalogue of ships, items, weapons and locations. The hangar bit deserves a sentence on its own. Your tray app fetches it with your login. The server never sees your RSI credentials, and that's by architecture, not by policy. Now the question everyone asks first, and should: will this get me banned? StarStats never touches the running game. No overlay, no DLL injection, no process attach, no memory reads, no packet sniffing, no input automation. It opens a text file the game already wrote to disk (same syscalls as Notepad) and, only if you turn on hangar data, makes plain HTTPS requests to the RSI website you're already logged into. Everything EAC is looking for is stuff this app structurally doesn't do. There's a full writeup in the repo at EAC-SAFETY.md, and the whole thing is public under MPL-2.0, client, server and site, so you can go read it instead of taking my word: https://github.com/TheCodeSaiyan/StarStats-Platform Obligatory honesty footnote: only CIG can make guarantees about CIG's anti-cheat. What I can claim and prove is what the software does and doesn't do. On your data, since a tracker asking for trust should volunteer this stuff. It's local-first. Everything stays on your machine until you sign in and explicitly flip sync on, and it's off by default. The awkward details, like the fact that raw log lines can (Mostly not at the moment) mention other players' handles and what happens to those when sync is on, are spelled out plainly at https://starstats.app/trust rather than buried in a privacy policy. Deleting your account is a button in settings and actually deletes. Export isn't a button yet. The portability right is written into the privacy policy and I'll honour it by hand until it is. No ads, no selling analytics, it's free, there's a donate page and that's it. The beta is waitlist-gated while it's one guy and a homelab. First wave gets in automatically, then it queues. Windows (signed installer, .exe or .msi) and Linux (.AppImage or .deb). No macOS build yet, the tray is Tauri/Rust and I just haven't put it in the release matrix. SmartScreen might still grumble on Windows for a bit, new signing certs start with zero reputation. https://starstats.app/ Setup guide is at https://starstats.app/docs and it's honest about the steps you wouldn't guess (the pairing code, the RSI cookie, verifying your handle). What helps most from beta testers: events that parse wrong or don't parse at all, and any spot where the onboarding lost you. Come find me on the StarStats Discord, or if you'd rather, open a GitHub issue (there's a parser-rule-request template). o7