Rust Legacy Browser is an unofficial fan project that brings Rust Legacy to the web browser. This notice explains what the website (rustlegacy.co.uk), the desktop launcher and the game servers listed here collect about you, why, how long we keep it, who can see it, and what you can ask us to do. It only describes what the service actually does.
Who runs this site
The site is run from the United Kingdom, and the people who run it are the "controller" of your personal data under UK data protection law (UK GDPR and the Data Protection Act 2018). To reach us, see Contact.
What we collect and why
Your account
- Username and email address, to run your account and send account emails (confirming your email, resetting your password).
- Your password, stored only as a one-way hash (scrypt). We never see or store the password itself.
- If you sign in with Steam: your Steam ID, which we need to sign you in, and the display name it sends us. We never see your Steam password.
- If you link a desktop character to your account: a one-way hash of that character's game ID on that server, never the ID itself.
- Your sign-in sessions (a random token, stored hashed) on the website and in the desktop launcher, so you stay signed in.
- Short-lived codes for confirming your email, resetting your password and linking a launcher or desktop character.
- A count of failed sign-in attempts, held in memory, to lock out password guessing.
- If a server asks you to verify a phone number: a one-way keyed hash of it, so one number fits one account. The number itself is held in memory only while the code is valid and is never written to our database.
Keeping banned players out
Anyone can play, with or without Steam, so we need another way to stop banned players coming straight back on a new account. For this we keep a one-way fingerprint of each identifier below, not the identifier itself: a keyed hash (HMAC-SHA256) made with a secret key that is kept apart from our database. A fingerprint can tell us "this is the same one as before", but can't be turned back into the original.
The identifiers we fingerprint:
- your email address in a simplified form, your Steam ID, and your phone if you verified one;
- a random device token this browser keeps (a cookie and a copy in local storage), set once you're signed in;
- a few browser signals (browser and version, screen size, time zone, language, graphics card name), combined into one hash;
- a hash of your IP address, and the name of the network if it belongs to a known hosting or VPN provider;
- if you use the desktop launcher, a hardware ID: the launcher sends a hash of your PC's identifiers and we hash it again before storing it;
We also note when you were on each server (not hashed), so we can tell whether two accounts were ever online at the same time. Server staff see "possible alt" notes (for example "same browser device"), never the hashes or the values behind them. Browser device, signal and IP matches never ban anyone on their own: a person reviews them. A ban on an account also covers its email, Steam, phone and hardware ID, so a new account using one of them is refused. We also refuse sign-ups from known throwaway email services.
When you play
- Joining. Which servers you join and when, so a join ticket works only once, and your in-game names on each server. A server marked as Steam-verified is told your Steam ID when you join it.
- Leaderboards. The server's gateway reports what you do in game: time online, animals and players killed, deaths, resources gathered, items crafted, pieces built and distance travelled, per server and day. Your username and these totals are public on the leaderboard and your profile page. You can hide yourself from every board and your profile on your account page; the counts are then kept but not shown.
- Moderation. Bans (with the reason and who set them), reports you file or other players file about you (with the text written), and a log of admin actions.
- Anti-cheat. A flag, a score and a short record of your movement or shots around the flagged moment, kept as evidence, and the item transfers the server sees between players.
- Screenshots for anti-cheat. When server staff ask, or automatically when the anti-cheat raises a serious flag, the game takes a picture of what it shows you: the game view with its menus and chat, never anything outside the game's tab. There is no prompt when it happens. That server's owner, admins and moderators can ask for one and look at it, and our staff can too; admins can delete one. Every request, view and deletion is logged. Screenshots are deleted automatically after 30 days. A screenshot is evidence for a person to judge, not an automatic verdict.
- Holds. If your account shares an identifier with a banned account, we note the match and which kind it was, so staff can review it and clear it.
- Voice chat (hold V) goes only to players near you while you hold the key. We don't record it. Text chat isn't sent to this website.
IP addresses
What: the IP address you join a server from, kept in that server's IP history. Why: to enforce bans and prevent abuse. How long: 90 days. Who can see it: server admins and our staff.
Admins can ban an IP address or a small range of addresses, which stops anyone joining from it, so people who share a connection with a banned player may be blocked too. Every IP ban is logged with who set it and why, and you can ask us to review one.
The forum and wiki
Threads and posts you write on the forum, with your username and when you posted or edited, are public. Staff edits to the wiki are kept with who made them.
The opening-day list
If you leave your email on the launch page, we keep that address, when you signed up and a random code for your unsubscribe link, and a record of whether the opening-day email reached you. We use it only to tell you when the servers open.
If you run a server
Your account, your server's name, region and address, your listing (description, tags, Discord and website links), and what your host app reports: whether the server is up, its backups list, its last wipe date and its live log. The live log can name players as they join, leave, die or are flagged; we keep only the newest 2,000 lines per server, in memory, never in our database.
Technical data
- Your IP address is used to limit how often one connection can sign in, sign up or send forms. For that it is held in memory for about a minute. Our web server keeps no access logs.
- Cloudflare sits in front of the site for security and speed, so it handles your IP address and requests (see "Who sees it").
What we don't do
No adverts, no analytics, no tracking cookies, and we never sell your data or share it for marketing.
Our lawful bases
- Running the service you asked for (your account, sign-in, joining servers, launcher, account emails, forum): necessary for our agreement with you.
- Keeping the game fair and safe (anti-cheat, screenshots, bans and IP bans, the IP history, reports, audit logs, rate limits, the hashed identifiers, and the server tools owners use): our legitimate interest, and other players', in a game without cheating, fraud or abuse. We keep it light: hashes where a hash is enough, no automatic bans from device signals or IP addresses, and set retention periods. You can object (see "Your rights").
- Public leaderboards: our legitimate interest in showing who plays and how, with a switch to hide yourself.
- The opening-day email: your consent, which you can withdraw at any time with the unsubscribe link or by asking us.
- Legal requests: where the law requires us to keep or share something.
How long we keep it
| What | How long |
|---|---|
| Website sign-in sessions | 7 days, or until you sign out |
| Launcher sign-in sessions | 30 days, or until you sign out |
| Email, password and link codes | Until used or expired (24 hours at most) |
| Failed sign-in count | 15 minutes, in memory |
| Your account | Until you ask us to delete it |
| IP addresses you join from | 90 days |
| IP bans | Until they expire or are lifted |
| Browser device records (hashed) | 12 months after last seen |
| Time on servers and in-game names | 6 months after last seen |
| Anti-cheat screenshots | 30 days, then deleted automatically |
| Server live logs | Newest 2,000 lines per server, in memory, until the website restarts |
| Hashed identifiers (email, Steam, phone, hardware ID) | While the account exists, and while a ban on it is in force |
| Join ticket records | 1 hour after the ticket expires |
| Linked desktop characters (hashed) | Until the link is removed |
| Leaderboard counts | While your account exists |
| Bans, holds, reports, anti-cheat records, item transfers and the admin log | As long as they're needed to keep servers fair |
| Forum posts | Until you or staff delete them |
| The opening-day list | Until you unsubscribe, or we close the list after opening day |
| Rate-limit counters | About a minute, in memory |
Who sees it
| What | Who can see it |
|---|---|
| Your username, leaderboard totals, profile and forum posts | Everyone (hide the leaderboard and profile on your account page) |
| Your email, Steam ID and sign-in details | You and our staff |
| In-game names, time played, bans, reports, anti-cheat records, "possible alt" notes, item transfers and screenshots on a server | That server's owner, admins and moderators, and our staff |
| IP addresses you join a server from | That server's admins, and our staff |
| The admin log of a server | That server's owner and admins, and our staff |
| A server's live log | That server's owner, and our staff |
| The opening-day list | Our staff |
Services that handle data for us:
- OVH (OVHcloud), which hosts our server in the United Kingdom.
- Cloudflare, which protects and speeds up the site. It may handle traffic outside the UK under its own safeguards.
- Steam (Valve), only if you choose to sign in with it. If a server asks for a Steam account of a certain age, level or ban record, we ask Steam about your Steam ID when you join it.
- An email provider, once we connect one, to send account emails and the opening-day email.
Server owners. Some game servers are run by other people. Their game server and its gateway see your connection and what you do in game, and may keep their own logs. They see the moderation data above for their own server, and they're responsible for what they do with it. We don't share your data with anyone else unless the law requires it.
Cookies
We only use cookies that sign-in and account security need: no tracking, no adverts, no analytics. The full list, and what the site keeps in your browser, is on the Cookies page.
Your rights under UK GDPR
You can ask us to:
- see the data we hold about you and get a copy (access);
- correct anything that's wrong (correction);
- delete it (deletion);
- stop or limit how we use it, including anything we do for our legitimate interests (objection and restriction);
- give you a copy in a form you can take elsewhere (portability);
- take back your consent to the opening-day email at any time.
Deleting your account removes your username, email, password hash, linked Steam ID and sessions. We may keep a ban record, with the hashed identifiers it covers, so a ban can't be dodged by deleting the account. You can also ask what "possible alt" notes or screenshots exist about you, and object to them.
If you're unhappy with how we handle your data, you can complain to the Information Commissioner's Office (ICO) at ico.org.uk. We'd like the chance to put it right first.
How to ask
Open a ticket in #open-a-ticket on our Discord (see Contact). It's free, and we'll reply within one month. We may ask you to show the account is yours, for example by signing in to it.
Children
You must be 13 or older to create an account. If you think a child under 13 has given us their data, tell us and we'll delete it.
Changes to this notice
If we change what we collect or how we use it, we'll update this page and the date at the top. Big changes will be announced on the site and on Discord.