Privacy Policy

1. Who we are

Rustalytics is operated as a sole proprietorship in Sweden. For the purposes of the EU General Data Protection Regulation (GDPR) and the UK GDPR, the data controller is:

We do not operate at the scale that requires a dedicated Data Protection Officer under Article 37 GDPR, but legal@rustalytics.com is monitored and is the right place to send any privacy request, complaint, or question.

2. What information we collect

We collect only what we need to operate the Services. Below is a complete list, grouped by where it comes from.

From Steam (when you sign in)

• Your Steam64 ID.
• Your public Steam profile as returned by Steam Web API (display name, avatar URL, profile URL, country code, account creation timestamp, last-online state). This is the same data anyone visiting your Steam profile can see.
• Authentication metadata from Steam OpenID (assoc_handle, signed claims). We use this to verify the sign-in and then discard it.

We never see your Steam password. Authentication happens entirely on Steam's servers and Steam only tells us the resulting Steam64 ID.

From Facepunch / Rust+ (when you pair)

• Your Rust+ auth token issued by Facepunch — a long opaque string the Rust+ companion API uses to authenticate requests on your behalf.
• A set of FCM push credentials we register on your behalf with Google (Android ID, security token, GCM token, ECDH public/private key pair). These let Google deliver Rust+ push notifications to us, the same way the official Rust+ mobile app receives them.
• Each Rust+ pairing notification Facepunch sends through Google FCM: server name, description, banner image URL, server IP, server port, Rust+ port, BattleMetrics-style server identifier.
• Each smart device pairing (smart switches, smart alarms, storage monitors): entity ID, entity name, entity type, the player token tied to that device.
• Each smart-alarm fire / raid notification: title, message body, timestamp, the server it came from.

See Section 3 for exactly how the auth token reaches us.

From the desktop app and Pro bot

• The Rustalytics config created on first launch (a JSON blob containing your FCM credentials and Rust+ token, scoped to your Steam ID).
• Your synced app settings (chat command prefix, message delay, language, tracker preferences, notification preferences, etc.).
• In-game chat messages seen on a server while the bot is connected: sender Steam ID, message text, whether it's a bot reply or a chat command, the command name (if any), the wipe timestamp it belongs to, and the language. These are stored so you can see your team's chat history and so the bot can answer commands contextually. They are linked to your account as the bot owner.
• Tracked teammates you've added: their Steam64 ID and public Steam profile data, plus whether you've granted them access to your panel.
• Server data we cache for performance: server name, map image, monument positions, helicopter / cargo / chinook / oil-rig timings. This is server data, not personal data.

From Discord (only if you use the bot)

• Your Discord user ID and username.
• The Guild (server) ID, the notifications channel ID, the category ID, and the @everyone role ID for any guild where you ran /install.
• Verification session metadata: the temporary session ID used to link your Discord and Steam accounts during /verify.
• Messages typed in the Rustalytics notifications channel — these are read by the bot and forwarded to your in-game team chat as if you typed them yourself. They may be logged together with your Discord username and a timestamp for chat-history, debugging, and abuse-prevention purposes (see Section 4).

From Stripe (if you pay us)

• The Stripe payment / subscription ID, the plan type (basic / pro, one-time / subscription), the renewal or end timestamp, and whether the plan is active, will end, or has ended.
• The Steam ID the payment was made under.

Card numbers, CVCs, billing addresses and similar are entered on Stripe's hosted checkout and stored by Stripe. Rustalytics never sees them. Stripe's privacy notice: stripe.com/privacy.

Server logs and diagnostics

• Standard HTTP request logs (path, status code, response time, IP address, user-agent), kept for short-term debugging and abuse prevention.
• Aggregate process metrics (memory usage, request counts) — these are not tied to individual users.
• Exception traces produced by the app, which may incidentally contain a Steam ID or a Rust+ token if that's what triggered the error.

What we do not collect

• We do not collect your real name, postal address, or phone number.
• We do not collect any "sensitive personal information" as defined by the GDPR or CCPA (race, religion, biometrics, health data, sexual orientation, exact geolocation, etc.).
• We do not run third-party advertising trackers.
• We do not sell or rent personal information to anyone.

3. How we get your Rust+ key from Facepunch

The "Rust+ key" (also called the Rust+ auth token, player token, or pairing token) is the credential that lets a third-party app talk to Rust+ on your behalf. Here is exactly how it reaches us — you can verify every step in our open desktop source.

1. You click "Connect with Rust+" in the Rustalytics desktop app or on rustalytics.com.
2. We open Facepunch's official Rust+ login page in a sandboxed browser window: https://companion-rust.facepunch.com/login. You sign in with your Steam credentials directly on Facepunch's site. We never see your Steam password.
3. Facepunch's page is built for the official Rust+ mobile app and posts the resulting auth payload back to the host app via a JavaScript shim called window.ReactNativeWebView.postMessage. We expose only that single, narrow channel into the third-party page (no other Electron or Node APIs), and we validate the payload before doing anything with it.
4. The payload contains exactly two fields: SteamId and Token. Nothing else from the Facepunch page is read or stored.
5. Independently of that, we register a fresh set of FCM push credentials with Google so that Facepunch's notification servers can push raid alarms and pairing data to us. Those credentials (Android ID, security token, GCM token, ECDH key pair) are tied to your Rustalytics account.
6. The auth token and FCM credentials are stored encrypted at rest in our database, scoped to your Steam ID. They are used only to make Rust+ API calls on your behalf and to receive Rust+ push notifications for you.

You can revoke the token at any time by clicking Sign out of Rust+ in the desktop app or by deleting your Rustalytics account. Facepunch also provides a "Re-register" button in the in-game Rust+ menu that invalidates all previously issued tokens, including ours.

4. Discord bot data and chat logging

Inviting and using the Rustalytics Discord bot is optional. If you do, please read this section carefully — some of what the bot does involves storing message content.

Linking accounts (/verify)

Running /verify creates a short-lived verification session storing your Discord user ID, the guild ID where the command was run, and (after you sign in with Steam) your Steam64 ID. Once verified we store the Discord ↔ Steam mapping on your Rustalytics account so the bot knows which Rust+ session belongs to you.

Installing in a guild (/install)

Running /install stores: the guild ID, the notifications channel ID, the category ID, the @everyone role ID, your Steam ID, and your Discord ID. We use these to deliver smart-alarm fires, raid pings, and pairing events to that channel. Running /uninstall removes the binding and clears the stored credentials for that guild.

Why the bot reads Discord messages

The headline reason: to bridge your Discord channel to your in-game team chat. When you type "raid in 10" in the Rustalytics notifications channel, the bot reads that line and immediately writes it into your team's chat in Rust, as if you'd typed it from your keyboard. Without the ability to read messages, the chat bridge can't exist.

To make this possible, the Rustalytics bot is registered with Discord using the Message Content Intent — the privileged Discord permission that lets a bot see the text of messages, not just metadata. Discord audits bots with this intent, and we declared the chat bridge as the reason.

In practice this means:

• The bot receives a message event for every message in any channel where it has been invited and granted "Read Messages" — that's how Discord works for any bot in a guild.
• The bot only acts on a message if the channel matches a notifications channel that you bound to a Rust+ session via /install. In any other channel — random off-topic chat, a #general room you happen to have invited the bot to — the message is discarded immediately and not stored.
• The bot does not read messages in channels it has not been added to, does not read messages in other guilds, and does not read direct messages between users.
• The bot's slash commands (/verify, /install, /serverstats, etc.) are processed by Discord and only the command name plus its parameters reach us; Message Content Intent isn't used for those.

What happens to messages on the chat bridge

Once a Rustalytics notifications channel is bound to a Rust+ session, the bridge runs in both directions:

• Messages typed in that channel are forwarded to your in-game team chat. They may be logged together with the sender's Discord username and a timestamp.
• In-game team-chat messages on the connected server are mirrored back into the Discord channel and may be stored in our chat-message database so the chat-history feature can show them later (see Section 2 — In-game chat messages).

You should assume that any message you send in the Rustalytics notifications channel, or in the in-game team chat of a server connected to a Pro Rustalytics bot, may be stored against the Steam account that owns the Rust+ session — not against every individual sender. Where we do store messages, we use them to power the chat-history feature, debug bot behaviour, and investigate abuse reports. We don't sell these messages or share them for advertising. We may use aggregated, de-identified statistics about them to improve features; if we ever want to use individual messages for any other purpose (for example, to train a model), we'll update this policy and notify you first.

Other slash commands

Commands such as /serverstats and /ruststats hit public Steam and community-server APIs; they don't store anything beyond standard request logs.

5. How we use your information

We process the data above for the following purposes:

• To create your account and authenticate you.
• To talk to Rust+ on your behalf — pairing servers and smart devices, sending team chat, running chat commands, receiving smart-alarm and raid notifications.
• To deliver notifications you've asked for, both in the desktop app and into your Discord guild.
• To process payments, manage subscriptions, and remember which plan you're on.
• To sync your settings between devices.
• To answer your support questions and investigate bugs you report.
• To detect and prevent fraud, abuse, and Terms of Service violations.
• To comply with legal obligations (tax, accounting, valid law-enforcement requests).

6. Legal bases (GDPR / UK GDPR)

If you're in the European Economic Area, the United Kingdom, or Switzerland, we process your data on the following legal bases:

• Performance of a contract (Article 6(1)(b)) — to deliver the Services you signed up for, including running the bot, processing payments, and storing data needed to make those features work.
• Consent (Article 6(1)(a)) — for cookies you opt in to, and for connecting your Rust+ and Discord accounts. You can withdraw consent at any time.
• Legitimate interests (Article 6(1)(f)) — to keep the Services secure, prevent abuse, debug failures, and improve features. We balance our interests against your rights and freedoms.
• Legal obligation (Article 6(1)(c)) — for tax, accounting, and lawful disclosure requirements.

7. Who we share data with

We share data only with the following processors, all under written terms:

• Facepunch Studios Ltd (Rust+) — your Rust+ auth token is sent to Facepunch's API every time we make a Rust+ call on your behalf. Facepunch is the source of every Rust+ notification we receive.
• Google LLC (Firebase Cloud Messaging / GCM) — we register push credentials with Google so it can deliver Rust+ notifications to us. Each notification passes through Google's infrastructure.
• Stripe, Inc. — handles all card processing.
• Discord Inc. — handles all messaging via the bot. Any message the bot sends or receives is processed by Discord.
• Steam (Valve Corporation) — for OpenID sign-in and public profile lookups.
• Our hosting and infrastructure providers — the servers that run the website, the bot, and the database.
• Other users — if you add a teammate to your panel, they can see your Rust+ panel for that server. If you post anything in a public area of the Services, that content is public.
• Acquirers — if Rustalytics is ever sold or merged, your data may be transferred to the buyer; we will tell you before that happens.
• Authorities — if we receive a valid legal request (subpoena, court order, etc.), we will comply, while pushing back on requests we consider overbroad.

We do not sell your personal information, share it for cross-context behavioural advertising, or use it to train AI models.

8. International data transfers

Rustalytics is based in Sweden, but Stripe, Discord, Google, Steam, and most of our hosting partners are headquartered in the United States. When data leaves the EEA / UK, the transfer relies on the GDPR's standard mechanisms — typically Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework. By using the Services you acknowledge these transfers.

9. Cookies and tracking

We use a small number of cookies that are strictly necessary to keep you signed in and to remember your cookie consent. Full details are in our Cookie Policy. We do not currently run third-party advertising trackers.

10. How long we keep your data

• Account data (Steam ID, Rust+ token, FCM credentials, settings, Discord links): for as long as your account exists. When you delete your account, we delete this data within 30 days.
• Notifications and chat messages: kept for the lifetime of your account, but in-game chat messages are scoped per server-wipe and may be pruned as servers wipe.
• Payment records: kept for at least seven years as required by Swedish bookkeeping law (Bokföringslagen).
• Support emails and abuse reports: kept for up to two years.
• Server logs: rotated within 30 days unless we need to keep specific lines for an open security investigation.

11. How we keep it safe

We use HTTPS for all traffic, encrypt the database at rest, scope credentials to the minimum privileges they need, and review access regularly. No system is perfectly secure though; if you spot a vulnerability please email legal@rustalytics.com so we can fix it.

12. Your privacy rights

Under the GDPR, UK GDPR, Swiss FADP, and similar laws, you have the right to:

• Access the personal data we hold about you and receive a copy.
• Correct inaccurate or out-of-date data.
• Erase your data ("right to be forgotten").
• Restrict or object to certain processing.
• Receive your data in a portable format.
• Withdraw consent (where consent is the legal basis).
• Lodge a complaint with your local data-protection authority. For Sweden that's the Integritetsskyddsmyndigheten (IMY); you can also complain to the authority in your own EEA country or the UK ICO.

To exercise any of these rights, email legal@rustalytics.com from an address we can tie to your account, or include your Steam64 ID in the message so we can verify you. We will respond within 30 days (extendable by a further 60 days if your request is complex, in which case we'll tell you).

13. US state-specific rights

If you are a resident of California, Colorado, Connecticut, Utah, Virginia, or another US state with a comprehensive privacy law, you have rights similar to those above — including the right to know what we collect, to delete it, to correct it, and (where applicable) to opt out of "sale" or "sharing" for targeted advertising.

We do not sell or share personal information for cross-context behavioural advertising, and we have not done so in the previous twelve months. We do not knowingly process the personal information of consumers under 16. To exercise a state-law right, email legal@rustalytics.com. If we decline a request, you may appeal by replying to that email; if your appeal is denied you may contact your state attorney general.

California "Shine the Light": California residents may ask once per calendar year for a list of categories of personal information disclosed to third parties for direct-marketing purposes. We do not disclose any personal information for that purpose.

14. Do-Not-Track

Most browsers offer a "Do Not Track" (DNT) signal. There is still no industry consensus on how to interpret DNT, so we do not currently respond to it. We don't track you across other websites either way.

15. Children

The Services are not directed at children under 13 (or under 16 in the EEA), and we do not knowingly collect data from them. Rust itself is rated PEGI 16 / ESRB Mature. If you believe a child has given us personal data, email legal@rustalytics.com and we will delete it.

16. Updates to this policy

We may update this policy as we add features or as the law changes. The "Last updated" date at the top will always reflect the current version. If we make material changes we'll announce it in the app and on our Discord before the change takes effect.

17. How to contact us

For anything privacy-related, email:

legal@rustalytics.com

Or write to us at:

18. How to access, change, or delete your data

• Change your settings or teammates: sign in to /app and update them directly.
• Disconnect Rust+: sign out of Rust+ from inside the desktop app, or click "Re-register" inside Rust to invalidate every token Facepunch has ever issued you (including ours).
• Remove the Discord bot: run /uninstall in your guild and the channel binding plus stored credentials for that guild are deleted.
• Cancel your subscription: sign in to /app and click Manage Subscription to open Stripe's customer portal.
• Full account deletion / data export: email legal@rustalytics.com from the email tied to your Stripe purchase or include your Steam64 ID. We'll confirm, process the request within 30 days, and tell you what (if anything) we have to retain for legal reasons (e.g. invoices for tax purposes).