Privacy Policy

General provisions

This Policy governs information processing and protection when you use the RustRecon website, account area, the @rustrecon_bot Telegram bot, the “RustRecon - Rust+ Connector” browser extension for Chrome and Firefox, and connected Rust+ features. The service is operated by the RustRecon project administration.

By using the service, you confirm that you have read and accept this Policy. If you disagree, stop using RustRecon.

Information we collect

When you register, RustRecon receives your email address and an account identifier. We also keep your plan, service settings, saved squads, interaction records required by enabled features, and records needed to secure the account.

RustRecon does not require passport data, identity documents, photographs of a person, or other personal information that is not needed for a selected service feature. Do not submit such information in input fields or support requests.

• SteamID64 values, links, and names you submit for a lookup;
• technical logs such as request time, IP address, browser, device and operating-system type, error codes, and security events;
• to count free checks: a hash of the browser fingerprint, a hash of the IP address, and a random device identifier stored in a cookie; the raw fingerprint and IP address are not kept for this purpose;
• payment records: plan, amount, currency, status, transaction ID, and payment-method type, without card details;
• Rust+, Telegram (chat ID and username), and notification connection data only when you enable those features.

Player data sources

Reports use identifiers you submit and data returned by Steam, BattleMetrics, public project-ban data sources, and other connected services. RustRecon does not create hidden game data or gain access to a player’s Steam account.

Rust+ connections

Pairing starts only at your request. We process the SteamID64, pending-pairing data, server address and name, notification settings, and the Rust+ player token required to connect to the selected server.

Sensitive connection data is sent over HTTPS and encrypted at rest. An unfinished pairing record is removed after connection or expiry. You can remove the connection from your account.

Pairing uses the free “RustRecon - Rust+ Connector” extension. It runs only on rustrecon.ru and the official Rust+ sign-in page (companion-rust.facepunch.com), opens that page, and passes the Rust+ sign-in token and SteamID64 it returns to rustrecon.ru. The sign-in token is used only to register the requested connection and is stored neither in the extension nor in the RustRecon database. The extension keeps only a short-lived random pairing state and does not read browsing history, the clipboard, or other websites.

How we use data

We use data only to operate selected features: to authenticate you, build reports, track selected players, deliver Rust+ events and messages, maintain paid access, respond to support requests, prevent abuse, analyze and improve the service, and diagnose failures. We do not sell personal data or use it for advertising profiles.

Cookies, browser storage, and analytics

The site sets two first-party cookies: a random device identifier (rr_did) used to count free checks and prevent abuse, and the chosen interface language (rr_lang). Each is kept for up to 400 days. Recent lookup history and interface preferences are kept in your browser’s local storage and can be cleared in the browser settings.

To count free checks, a technical fingerprint is computed in the browser (the open-source FingerprintJS library); it reaches the server only as a hash. Visit statistics use Yandex Metrica with Session Replay (Webvisor): it sets its own cookies and may record page activity such as navigation, clicks, and scrolling. This data is used to understand how the site is used and to fix usability problems, not for advertising. You can block Metrica with browser settings or extensions; the core features keep working.

Payments and receipts

Payments are processed by the Platega payment service. You choose the payment method and enter payment details on its page; RustRecon neither receives nor stores full card numbers or CVCs. Only the information needed to create and reconcile a payment is sent to Platega: a technical account identifier, the plan and its description, amount, currency, and the return address on the site. RustRecon receives the payment status, amount, transaction ID, and payment-method type from Platega.

Service providers and disclosure

Data is shared only with providers needed for the selected feature: Supabase for accounts and storage, Resend for email, Steam, BattleMetrics, and providers of public project-ban information for reports, Facepunch Rust+, Expo, and Firebase Cloud Messaging for connections and notifications, Telegram when you connect the bot, Platega to process payments, and Yandex for the Yandex Metrica analytics service.

Other disclosure is possible when required by law, necessary to perform obligations to you, or separately authorized by you. We do not share data with unrelated parties for their own advertising.

Retention

Account and active-feature data is kept while you use them. Some records may be retained afterwards for security, disputes, accounting, and legal obligations. Local lookup history can be cleared in your browser; shared report and squad links stay active for 3 days and are then deleted. Email confirmation and Telegram linking codes are deleted once used.

Your choices and rights

You can change notification settings, disconnect Rust+ or Telegram, and request access, correction, or deletion, including deletion of the whole account. A Pro purchase is one-time and has no automatic renewal. Message us on Telegram at @RustRecon with your account email and describe the request. Records required by law may be retained for the applicable period.

Internet transmission risks

You understand that sending information over the internet always involves risk. RustRecon uses reasonable safeguards but, to the extent permitted by law, is not responsible for loss or disclosure caused by the user or independent third parties that the service could not reasonably prevent.

Security, changes, and contact

We use organizational and technical safeguards, but no transmission or storage method is completely secure. The administration may update this Policy; the current revision and effective date are always published here. Material changes will be highlighted in the service where required.

Continuing to use RustRecon after a revision takes effect means you accept the updated terms. If you disagree, stop using the service. RustRecon is independent and is not affiliated with Facepunch Studios or Valve.