RUSTPORTS TERMS OF SERVICE COMMUNITY INDEX FOR GAMES PORTED TO RUST
Rโ†—rustports.COMMUNITY INDEXโ† Back to the index
VERSION 3 ยท EFFECTIVE 30 SEPTEMBER 2026

Terms of Service.

Last updated: 30 September 2026

RustPorts is a metadata directory, not a game host or network relay. Creators operate and host their own game servers. RustPorts may store and display a direct connection address, but does not connect to, proxy, relay, tunnel, or monitor game traffic. No game files or assets may be uploaded.

1. About RustPorts

RustPorts is an independent community index for ports, conversions, and parodies of games implemented in the Rust programming language. Projects may be based on any game. RustPorts is not about the Rust game, and is not affiliated with any game publisher or rights holder. Trademarks and other rights remain with their respective owners.

2. Eligibility and accounts

You may use RustPorts only if you can legally agree to these terms where you live and meet the minimum age required by applicable law. Accounts use GitHub authentication. Keep your GitHub account secure and do not impersonate another creator. When creating or accessing a RustPorts account, you must actively accept the current Terms of Service. We record your GitHub account ID, the accepted terms version, and the acceptance time so we can administer your account.

3. What you may submit

Submissions contain text metadata (such as a title, description, category, and development stage), one link to a public GitHub repository, and optionally a direct game-server address in hostname:port or [IPv6]:port form. RustPorts checks public repository metadata only to confirm that the repository link is public. It does not fetch source files, download releases, clone, mirror, or host the repository. RustPorts stores a submitted server address as text only and never opens a connection to it. GitHub and all creator-run hosting providers are third-party services governed by their own terms.

By submitting a project, you confirm that you created it or are authorized to represent its creator, have permission to link the repository publicly, and have the rights needed for the original work described. A GitHub link is not a transfer of ownership and does not authorize RustPorts to distribute any files.

4. No file or asset submissions

RustPorts has no file-upload feature. Do not try to upload or transmit executables, game builds, source code, source archives, screenshots, cover art, models, textures, audio, maps, logos, or other assets through RustPorts. Do not include copied or ripped assets from the game being ported, converted, or parodied, or any other third-party game, in a RustPorts project. RustPorts does not accept assets at all, whether or not you have permission to use them. Rewriting game logic in Rust, inspiration, or parody does not grant permission to copy protected assets.

RustPorts accepts only project metadata, a GitHub URL, and an optional direct connection address. Creators must operate their own servers and arrange their own hosting, network security, moderation, availability, and compliance. Players connect directly using the relevant game client. RustPorts does not provide, operate, secure, or route those servers or connections. A public link does not mean RustPorts reviewed or endorsed every file in the linked repository or content served by a creator.

5. Moderation and project status

Every submission is private to its creator until a moderator reviews it. Moderators may mark a project submitted, under review, changes requested, approved, published, rejected, or removed. Only published projects appear in the public catalog. We may ask for changes, decline a submission, hide/remove a listing, suspend an account, or preserve moderation records where reasonably needed to enforce these terms or respond to rights complaints. Project status is informational and is not a guarantee of safety, quality, legality, or endorsement.

Before approving or publishing, moderators must review the public GitHub page, any publicly accessible project information needed for the listing, and the submitter's rights and server-operation attestations. RustPorts does not probe or connect to game servers. If rights, asset ownership, or authority to publish an address are unclear, the project must not be published. Moderation is performed by people and may not detect every rights violation. Tell us if you believe a listing infringes your rights or contains prohibited material. Use our contact and rights-report process to request review of a listing.

6. Your content and our limited permission

You keep ownership of your project and submission. You grant RustPorts a limited, non-exclusive, worldwide, royalty-free permission to store and display the text metadata, GitHub URL, and server address you submit solely to operate, review, moderate, and promote the RustPorts index. This permission does not include any right to host, copy, or distribute project files or assets, or to carry game traffic. You can request removal of your listing; required moderation, safety, and legal records may be retained as allowed by law.

7. Acceptable use

Do not use RustPorts to infringe copyright or trademarks, mislead people about affiliation, harass others, submit unlawful or deceptive material, evade moderation, probe or disrupt the service, or attempt to send files to endpoints that do not accept them. Do not submit a repository you lack permission to publicize. We may remove content or restrict access to protect users, rights holders, and the service.

8. Third-party links and availability

GitHub links and direct game connections leave RustPorts. We do not control, host, operate, secure, or guarantee third-party services, repositories, creator-run game servers, or their content. A listed server address is supplied by its creator and RustPorts does not test or proxy it. RustPorts itself still operates a website and API that store and display directory metadata. The service is provided on an evolving, as-available basis; we cannot promise uninterrupted availability of RustPorts or any linked project.

9. Privacy

RustPorts stores the GitHub account identifier and username needed for sign-in, accepted-terms records, project metadata, submitted GitHub links and server addresses, picks, sessions, and moderation history. The sign-in flow requests read-only profile access; RustPorts does not request permission to write to repositories and does not store a GitHub access token. A public server address can reveal where a creator's server is reachable, so do not submit private, personal, or sensitive endpoints. See our privacy notice for retention, account data requests, and the verified deletion request process.

10. Changes

We may update these terms. The current version and its acceptance time are recorded for accounts. If a change materially affects your use, we will ask you to accept the new version before continuing.

11. Legal review

These terms are a product-policy draft for the RustPorts implementation, not legal advice. The owner should have qualified counsel review jurisdiction, liability, privacy, takedown, dispute-resolution, and contact provisions before opening registration to the public.

Return to RustPorts