By accessing or using RustCommander ("the Service"), you agree to be bound by these Terms of Service. If you do not agree, do not use the Service.
1. Description of Service
RustCommander is an independent, community-built web application that provides Rust game server administrators with tools for RCON management, player tracking, map operations, plugin monitoring, VIP management, chat logs, Discord status bot integration, and related server administration workflows.
2. Accounts
To use the Service you must create an account using an email address and password or a supported third-party sign-in provider, currently Google, Discord, or Steam. A valid email address is required in every case. Steam does not provide an email address to RustCommander, so users who continue with an unlinked Steam account must enter an email address and verify it with a short-lived code. If that verified email already belongs to a RustCommander account, the Steam identity is linked to that account; otherwise a new account is created.
You are responsible for maintaining the security of your RustCommander account and linked provider accounts, and for all activity that occurs under your account. You must provide accurate information, keep it up to date, and must not use another person's account without permission. We reserve the right to suspend or terminate accounts that violate these Terms.
While signed in, you may link supported Google, Discord, and Steam identities to your RustCommander account. A provider identity cannot be linked to more than one RustCommander account, and only linked identities may be used to sign in to that account.
When you choose Discord sign-in, you authorize RustCommander to request the Discord permissions displayed on Discord's authorization screen, including permission to add your Discord account to the official RustCommander community server. Using another sign-in method does not perform this Discord community action.
3. Acceptable Use
You agree not to use RustCommander to:
- Violate any applicable law or regulation.
- Access or attempt to access servers or data you do not own or have permission to manage.
- Abuse, disrupt, or attempt to gain unauthorized access to the Service or its infrastructure.
- Send malicious RCON commands intended to damage servers or harm other users.
- Scrape, crawl, or extract data from the Service in an automated manner without prior written consent.
4. Third-Party Services
Account authentication may be provided by Google, Discord, or Steam. Your use of those services remains subject to their respective terms and policies. RustCommander may be unable to authenticate you through a provider when that provider is unavailable, changes its APIs, revokes access, or restricts your account.
The Service integrates with third-party platforms including RustMaps for map generation. Your use of RustMaps features is also subject to RustMaps' own terms. RustCommander is not affiliated with RustMaps, does not include or resell RustMaps licenses, and is not responsible for RustMaps availability, pricing, API limits, map output, service interruptions, or policy changes. RustCommander only provides a panel workflow for using your own RustMaps access.
Payments and subscription checkout are processed through Stripe. Transactional emails may be sent through Resend.
The optional Discord status bot feature connects to Discord's Gateway API using a bot token you supply. Your use of this feature is also subject to Discord's Terms of Service and Discord's Developer Policy. RustCommander is not affiliated with Discord and is not responsible for Discord API availability, rate limits, policy changes, or any consequences arising from bot usage in your Discord server. You are responsible for ensuring your bot complies with Discord's rules and that you have the right to add it to your server.
5. Server credentials and automated plugin updates
If you save SFTP credentials for a server, you authorize RustCommander to store the password encrypted and use it to perform the file operations you request. The saved connection is shared at server level with team members who have been granted the Files permission. RustCommander does not display or return the stored password after saving it.
If you separately enable automatic RustCommander plugin updates, you authorize the Service to detect an outdated RustCommander.cs file, upload a replacement through SFTP, retain a timestamped backup of the previous file when one exists, and run the specific RCON command required to reload RustCommander. This option is disabled by default and requires an additional confirmation.
SFTP access can modify or delete server files and therefore carries significant security risk. You are responsible for limiting Files and Settings permissions to trusted team members, protecting your RustCommander account, using appropriately restricted SFTP credentials where available, and maintaining independent backups. Encryption at rest reduces exposure but cannot eliminate risks caused by compromised accounts, excessive permissions, vulnerable hosting panels, or actions expressly authorized through the panel.
6. Subscriptions, Licenses, and Billing
Paid plans grant licenses for the number of servers and team features described at checkout. Licenses remain active while the related subscription or paid period is active. If payment fails, is canceled, refunded, or expires, access to paid features may be limited or disabled.
Prices, plan limits, and included features may change over time. Any material changes will be shown in the Service or during checkout before they affect a new purchase.
7. Privacy and Cookies
Use of the Service is also governed by the Privacy Policy and Cookie Policy. The landing website and portal share the same cookie consent preference where possible.
8. Intellectual Property
All content, code, and design of RustCommander are the property of RustCommander and its contributors. You may not copy, reproduce, or redistribute any part of the Service without prior written permission.
"Rust" and related marks are trademarks of Facepunch Studios. Their use within RustCommander is purely descriptive and does not imply any affiliation or endorsement.
All official Rust game assets displayed, rendered, or referenced through the Service—including 3D models, props, prefabs, monuments, textures, names, and icons—remain the property of Facepunch Studios and/or their respective rights holders. RustCommander claims no ownership of these materials. Their use is limited to descriptive, visualization, interoperability, and server-administration purposes and does not imply affiliation, sponsorship, or endorsement by Facepunch Studios.
9. Disclaimer of Warranties
The Service is provided "as is" and "as available" without warranties of any kind, either express or implied. We do not guarantee that the Service will be uninterrupted, error-free, or free of harmful components. Use of the Service is at your own risk.
10. Limitation of Liability
To the fullest extent permitted by law, RustCommander and its contributors shall not be liable for any indirect, incidental, special, or consequential damages arising from your use of the Service, including but not limited to loss of data, server downtime, or unauthorized access to your RCON credentials.
11. Changes to These Terms
We may update these Terms from time to time. Continued use of the Service after changes are posted constitutes acceptance of the revised Terms. Material changes will be communicated via the Service or by email where possible.
12. Contact
For questions about these Terms, email [email protected] or reach us through the RustCommander Discord community.
© 2026 RustCommander. All rights reserved.