Data and privacy
Written plainly, because “what does it collect” deserves a straight answer rather than a policy document.
What the plugin sends
Section titled “What the plugin sends”From each server running CerebRUST:
| Category | Detail |
|---|---|
| Sessions | Connects, disconnects, display name, IP address |
| Positions | Every ~2 seconds while awake, every 60 seconds while sleeping |
| Combat | Deaths, kills, per-hit combat log (weapon, damage, distance, hit area, health) |
| Raids | Structure damage, destruction, explosives used, whether defenders were present |
| Building | Tool cupboards, their positions, upkeep and auth lists |
| Resources | Wood, stone, metal and sulfur gathered |
| Activity | Time active vs AFK |
| Chat | Global, team and server messages |
| Teams | Membership and changes |
| Reports | F7 player reports |
| Signs | Sign images and who painted them |
| Bans | The server’s ban list |
| Server | FPS, player counts, name, description, map, monuments |
What CerebRUST holds about your account
Section titled “What CerebRUST holds about your account”- Steam: your Steam ID, display name, avatar, and Steam’s public ban flags
- Steam friends list, where your profile allows it — see your network signal for the one place this is read
- Discord, only if you link it: your user ID and display name
Signing in uses Steam OpenID, so CerebRUST never sees your Steam password. Linking Discord grants identity only — CerebRUST cannot read your messages or act as you.
Who can see it
Section titled “Who can see it”| Signed out | Signed-in player | Server staff | CerebRUST staff | |
|---|---|---|---|---|
| Public server pages, player counts | ✓ | ✓ | ✓ | ✓ |
| Public player profiles, name history | ✓ | ✓ | ✓ | ✓ |
| Leaderboards | Owner’s choice | Owner’s choice | ✓ | ✓ |
| Your own bases and notifications | ✓ | ✓ | ||
| Live map, positions, sleepers | ✓ | ✓ | ||
| Chat, including team chat | ✓ | ✓ | ||
| Raids, combat log, signs, reports, bans | ✓ | ✓ | ||
| IP addresses | ✓ | ✓ | ||
| Derived network signal (opt-in) | ✓ (about self) | ✓ | ✓ |
“Server staff” means staff of that particular server. Server access does not extend across servers, with one narrow, opt-in exception: if your server’s organisation and at least two others have all turned on cross-network player signals, admins on those other organisations’ servers can see an arithmetic summary of your play — percentiles and counts, never your raw telemetry, never which server it came from, and never a note, a flag or a ban. See your network signal for exactly what that is and how to appeal it.
The two that surprise people
Section titled “The two that surprise people”- Team chat is archived and readable by that server’s staff.
- Positions are recorded continuously, not sampled when something happens.
Neither is new capability — a server owner could already extract both from server logs. CerebRUST makes them legible. But play under the assumption that server staff can see where you are and what you typed.
Retention
Section titled “Retention”- Most telemetry is scoped to the current wipe and does not carry over
- Position history is purged on a rolling schedule; the map is live, not an archive
- Notifications are purged automatically after a period
- Accounts and cross-wipe player history persist until removed
What is never collected
Section titled “What is never collected”- Steam passwords or credentials
- Discord message content
- Anything from servers not running CerebRUST
- Anything outside Rust
Removal requests
Section titled “Removal requests”To have your data removed, ask in the CerebRUST Discord.
Note that a server owner’s own operational records — bans, and the moderation history attached to them — are theirs, and a removal request does not oblige a server to forget that it banned you.