Privacy Policy

Who operates the service

RustRecon operates the RustRecon service and publishes the Rust+ Connector extension. Privacy questions, access requests and deletion requests can be sent to rustreconofficial@gmail.com.

Data used by the website

When you create an account or use a paid or account feature, RustRecon processes the email address and authentication identifiers supplied through Supabase, subscription status, service settings and security records needed to operate the account. Essential session and anti-abuse identifiers may be stored in cookies or browser storage.

Player lookups use identifiers you submit and public or licensed data returned by Steam, BattleMetrics and RustBans. Recent lookup history is stored in your browser and can be cleared there. A report is stored on the server only when you explicitly create a share link; shared report pages are excluded from search indexing.

Rust+ Connector pairing data

Pairing starts only after you click the connect button in your RustRecon account. On the official Rust+ sign-in page, the extension handles your SteamID64 and the Rust+ sign-in token returned after login, then sends them over HTTPS to RustRecon solely to complete the requested connection.

The Rust+ sign-in token is held in memory for the registration request and is not written to extension storage or persisted in the RustRecon database. A random pairing state and the IDs of the RustRecon and login tabs are kept in browser session storage for no more than ten minutes and cleared when the flow completes or is cancelled.

While waiting for server pairing, RustRecon stores the SteamID64, a generated device ID and encrypted push-receiver credentials for up to 30 minutes. A successful pairing removes that temporary record. Expired records are removed during the next Rust+ worker cycle.

After pairing, RustRecon stores the SteamID64, paired server address and name, notification settings and status, and an encrypted Rust+ player token needed to connect to that server. This connection data remains until you disconnect Rust+ or request deletion of the associated RustRecon account data.

How data is used

Data is used to provide the features you request, operate accounts and subscriptions, deliver Rust+ events and team-chat messages, prevent abuse, diagnose errors and protect the service. RustRecon does not sell this data and does not use it for advertising, credit or lending decisions.

Services that receive data

RustRecon uses service providers only where needed to deliver the requested feature:

• Supabase provides account authentication and database infrastructure.
• Resend delivers account and security email when configured.
• Steam, BattleMetrics and RustBans receive player identifiers in lookup requests and return profile, server-history or ban data.
• Facepunch Rust+, Expo and Google Firebase Cloud Messaging receive the registration and push-channel data needed for a Rust+ connection.

Retention, security and your choices

Account and service data is kept while the account or requested feature remains active and afterwards only where reasonably necessary for security, dispute handling or legal obligations. Operational logs may contain timestamps, IP addresses, request metadata and error codes; authentication tokens must not be written to logs.

You can cancel an extension flow by closing its sign-in tab, disconnect Rust+ from the account page, clear local lookup history in your browser, or email rustreconofficial@gmail.com to request access, correction or deletion. RustRecon limits the extension to two HTTPS origins, validates message origins and pairing state, contains no remote executable code, and encrypts stored Rust+ credentials at rest.

Changes and independence

Material changes to these practices will be reflected on this page and, where required, disclosed through the browser store or extension consent flow before the changed processing begins. RustRecon is an independent service and is not affiliated with or endorsed by Facepunch Studios or Valve.