Plain-language rules for using the Hub.

Keep your Hub password secure and use accurate identity information. Steam and Discord linking must be completed through the official provider pages. Do not share authenticator codes or access credentials.

Do not post illegal, abusive, hateful or privacy-invasive content. Staff may hide material or restrict accounts to protect the community and keep discussions usable.

Package details, duration and server availability are shown before checkout. Orders and delivery state remain recorded so players and staff can resolve problems through the support workflow.

A commercial PBG plugin purchase gives the buyer a licence to run that plugin on the number of Rust server activations shown at checkout; it does not transfer ownership of the source code. Licence keys and protected downloads are attached to the buyer’s Hub account and must not be shared, resold, redistributed or used to remove or bypass the licence checks. A server move may require the old activation to be reset by PBG support.

The Hub stores information needed for accounts, moderation, support and community features. It also records public page visits for security and site statistics using the page path, time, browser/device type, a masked network prefix and a one-way IP hash; the raw IP address is not stored. If you sign in during the same Hub session, visits carrying that same random session reference may be linked to your Hub account and shown to authorised staff using your current Hub display name. The Hub does not identify an account from an IP address alone. Commercial plugin licence validation sends the product code, plugin version, server name and a random installation identifier to the Hub over HTTPS; the Hub stores a one-way server fingerprint and network hash with activation/last-seen times so activation limits can be enforced. Steam/Discord credentials are handled by those providers; the public directory does not expose private email or account records.