Scope and contact
PlayNexus.gg operates this community service. The current contact route for privacy questions or requests is a private support conversation through the official PlayNexus Discord. Do not post account identifiers, receipts or evidence in a public channel.
Data we handle
Game and operations
Rust and the server infrastructure process the connection and account information needed to run and secure a multiplayer server, including Steam identity, display name, connection data and server logs.
Discord ↔ Steam link
If you use verification, the bot stores your Discord ID, Steam64 ID, an authority-link identifier, timestamps and the claim state required to prevent duplicate rewards. One-time verification codes are not written to the bot database.
Reports and audit
A private report stores the reporting Discord ID, server, target, reason, status and timestamps. Bot audit entries use a hashed actor identifier plus the action and bounded operational detail.
Telemetry and Nexus Pulse
Private event records use wipe-scoped pseudonyms. Public output contains aggregates and regenerated wipe-scoped aliases; it excludes raw Steam IDs, Discord IDs, IP addresses, chat content and exact positions. Published heatmap cells are delayed, cohort-gated and at least 250 metres.
Store delivery
Tebex handles checkout and payment processing. PlayNexus receives the package, Steam identity, transaction reference and status needed to deliver, reconcile or revoke the related entitlement.
Why the data is used
- operate, secure and troubleshoot the game service;
- enforce team limits and community rules;
- link an account only when a player requests verification;
- deliver deterministic rewards or purchased entitlements and prevent duplicates;
- receive private reports and maintain accountable operational records;
- publish privacy-bounded aggregate activity in Nexus Pulse.
Retention: the configured facts
Telemetry backups are configured to retain no more than 31 daily snapshots and to remove snapshots older than 30 days. The current live telemetry database and Discord-bot report, claim and audit tables do not have an automatic deletion interval configured, so no fixed period is stated for those records. Security, abuse, transaction and legal needs may affect what can be removed after a request.
Unlinking with /unlink confirm:true removes the active Discord–Steam link from the configured PlayNexus systems; hashed security audit history and other independently required records may remain.
Your choices
You can leave the Discord, disable opt-in notification roles, avoid optional verification, or request account unlinking. For access, correction, objection, deletion or another privacy request, contact staff privately on Discord with enough information to locate the relevant record. Identity verification may be required before disclosing or changing account-linked data.
Contact
Use the official PlayNexus Discord and open the private route described on the Support page. Never send passwords, recovery codes, Discord tokens or Steam Guard codes. Material changes to this notice will be dated on this page.