Privacy policy

1 · Who we are (data controller)

Inrust is a companion app for the game Rust, made up of a PC agent, a mobile app (under construction) and an online service (backend).

• Data controller: the publisher of Inrust, reachable at the address below. Full identity: to come with the release of version 1.0.
• Privacy contact : inrust@proton.me

2 · What we collect

• Account: your SteamID, your public Steam name and your preferences (favorites, tracked players, settings). Signing in happens through Steam only; we hold an e-mail address only if you choose to provide one.
• From Steam (when you sign in on Steam's page, and from Steam's public data — OpenID and Steam API): your SteamID, your public profile (name, avatar, level, account age) and your VAC / game ban status.
• From Rust+ (the official Rust+ connection operated by Facepunch, known as the companion API): the access key that lets the app use Rust+ on your behalf (authentication token), the identifiers used to deliver Rust+ notifications to you (FCM push credentials) and the details of the servers you have paired.
• App usage: servers launched, playtime per server, linked devices and the identifiers used to send you notifications (notification tokens).
• Reports and Radar: see section 4.
• Server sightings: when you copy a player's SteamID from the game, we record that a player was seen on that server — as a coded fingerprint, not as their SteamID (a pseudonymised form). These sightings feed aggregated per-server statistics; they are not an accusation and they name nobody. See sections 4 and 9.
• Clan: if you create or join a clan, your membership, your role and what you share in it — see section 4a.
• User feedback: the message you send through the dedicated button, the app version, the platform and the server the app is connected to. The technical log is attached only if you tick the box provided for it.
• Usage measurement: see section 8.
• Technical: connection logs — address requested, result, IP address and type of app or browser (HTTP logs: path, status, IP, user-agent) — for security and debugging.

We do not collect your real name, your postal address or your phone number, nor any sensitive data within the meaning of article 9 of the GDPR. We sell no data and use no third-party advertising tracker.

3 · How we obtain your Rust+ key (Facepunch)

When you pair a Rust+ server, your agent obtains from Facepunch an access key (authentication token) and notification identifiers (push credentials). We store them in order to make Rust+ calls on your behalf — live map, alarms, chat — and to receive the notifications. You can revoke this access at any time: Settings → Privacy and data → “Unlink Rust+” erases the pairings, the devices, the notification identifiers and the Facepunch key from your PC and from your account. Facepunch, however, offers no documented way to invalidate these keys on its side.

4 · Community reports and Radar

You can report players for cheating or toxicity. These reports feed an aggregated suspicion score shared with the community. Regarding reported players, who are third parties:

• Their SteamID is never stored in the clear in the shared community database: it is replaced by a coded fingerprint, which can only be matched back to a SteamID with a secret key held by us alone (pseudonymisation by keyed HMAC). Only aggregated counters are displayed.
• A player who has only been reported, without confirmation, is never named publicly.
• A player whose VAC ban or game ban is confirmed by the Steam API — a public fact that Steam displays itself — may be identified, for the purpose of preventing cheating.
• Legal basis: legitimate interest (article 6(1)(f)), with a documented balancing test. You have a right to object and a right to erasure (section 11).

4a · Clan

A clan is a private space: what it holds is visible to its members only, never to the rest of the community. We keep:

• Your membership and your role (leader, officer, member), and the permissions the leader grants you.
• The clan chat: your messages and mentions, kept for 30 days and then deleted.
• The log of alarms shared with the clan (Rust+ smart alarms): 48 hours.
• Invitations: the SteamID of the invited person — a third party who has not accepted yet — and the name you give them. They are deleted when they expire, 14 days after being sent.
• What the clan shares: the clan's server, the “Today” note, tasks (deleted 14 days after being done), bases marked on the map and the contents of boxes linked to a Storage Monitor shared with the clan.
• In-game presence: the map grid square a member is in, and only on the clan's server. It is held in memory for a few minutes, never written to the database or to the logs.
• Erasure: leaving the clan removes your seat, your tasks and the devices you were sharing; your messages stay in the chat until they are deleted at 30 days. Deleting your account also erases your messages. Disbanding the clan erases all of its content. The leader of a clan that has other members must first hand leadership to an officer: their account cannot be deleted before that, so the clan does not vanish without its members knowing.

5 · How we use your data

To provide the service (server list, Rust+, favorites, playtime, radar); to secure it and prevent abuse; to debug and improve; to notify you, for example when a player you reported is confirmed banned; and to comply with our legal obligations.

6 · Legal bases (GDPR / UK GDPR)

• Contract — art. 6(1)(b): operation of the service (account, Rust+, favorites, future payments).
• Consent — art. 6(1)(a): optional cookies and trackers, linking of the Rust+ and Steam accounts.
• Legitimate interest — art. 6(1)(f): security, abuse prevention, debugging, improvement and Radar (see section 4).
• Legal obligation — art. 6(1)(c): accounting and tax.

7 · Who we share with — processors and transfers

We share your data only with the technical processors that are necessary:

Some of these providers are established outside the European Union — Steam/Valve, Google, Expo, Cloudflare, Discord and GitHub in the United States, Facepunch in the United Kingdom. These transfers rely on the appropriate mechanisms, namely the standard contractual clauses and the adequacy decisions.

The technical logs attached to a bug report do not go to Discord: only their number of lines appears there, the content stays in our database.

A Discord webhook you set up yourself: if you enter your own webhook in the PC app, your notifications go straight from your computer to your Discord server, without passing through our servers. We receive neither those messages nor the webhook address.

Location of our servers: the backend is hosted by Railway in the European region (Paris), verified on 14 August 2026. The Supabase database is hosted in the European region (Ireland), verified on 10 October 2026.

8 · Cookies, trackers and usage measurement

The site and the app use strictly necessary cookies only. No third-party advertising tracker.

The app measures its usage in a configuration exempt from consent within the meaning of the CNIL's criteria:

• the events recorded are technical and not nominative — app opened, tab visited, feature used, error encountered;
• they are attached to a random installation identifier, with no link to your account, your SteamID or your IP address;
• no cross-referencing with other processing, no transmission to a third party, no resale;
• the measurement serves only to know which features are used and where the app fails.

You can turn it off at any time in the app's settings, with no degradation of the service.

9 · Retention periods

• Account data: for the life of the account, deleted within 30 days after the account is deleted.
• Database backups: 30 days, then deleted. Data erased from the database (deleted account, objection) may therefore remain there for up to 30 days; the backups serve only to restore the service after an incident.
• Logs containing IP addresses: 90 days.
• Unconfirmed reports: a rolling 12 months.
• Unconfirmed server sightings: 60 days without a new sighting. After that, the coded fingerprint is deleted and only an anonymous counter remains, so that a server's statistics are not distorted by losing their denominator.
• List of players awaiting a ban check (SteamID in the clear, temporary): 60 days.
• Data used to tune the suspicion score (calibration set): 18 months.
• User feedback: kept for the time it takes to handle it and then for product archiving; the technical log possibly attached is purged along with the feedback.
• Confirmed bans (public facts): kept, reviewed upon objection.
• Clan: chat 30 days, alarm log 48 hours, invitations and done tasks 14 days; the rest lives as long as the clan (section 4a).
• Usage measurement: 13 months, the maximum period recommended for a usage-measurement identifier.
• Payment records (to come): the applicable statutory period — in France, around 10 years for accounting documents.

10 · Security

All exchanges are encrypted (HTTPS); the database is encrypted on disk (encryption at rest); your Rust+ access key is additionally encrypted by us inside it (AES-256-GCM); the SteamIDs of other players are replaced by a coded fingerprint (keyed HMAC); and each part of the service has only the strictly necessary access (principle of least privilege).

11 · Your rights

You have the rights of access, rectification, erasure (the “right to be forgotten”), restriction, objection and portability, as well as the right to withdraw your consent. You may also lodge a complaint with your supervisory authority — in France, the CNIL.

To exercise them, write to inrust@proton.me. We answer within 30 days. When an account is deleted, most of the data is erased automatically; the erasure of a reported player is carried out on request, and confirmed ban facts, being public, are examined case by case.

12 · United States residents

If you live in a US state with a privacy law — California (CCPA/CPRA), Virginia, Colorado, Connecticut, Utah and others — you have specific rights: to know the categories of data collected and their purpose, to request access to it, its correction or its deletion, and to refuse its “sale” or its “sharing”.

Inrust neither sells nor “shares” your personal data within the meaning of those laws, and displays no advertising targeted by third parties: there is therefore no “Do Not Sell or Share My Personal Information” button to activate. You can exercise your other rights by contacting us (section 15). We will not discriminate against you for exercising those rights.

13 · Children

Inrust is not aimed at people under 15 in France, or under 16 in the European Union depending on the member state, and does not knowingly collect their data.

14 · Changes

We may update this policy; the date at the top shows the last revision. Substantial changes will be signalled in the app.

15 · Contact

inrust@proton.me