Terms of Service

Last Updated: October 27, 2026

1. About these Terms

Remade is a community-maintained directory for discovering independently developed software reimplementations, supporting tools, and requests for software people would like to see recreated. Remade also provides public datasets and, where available, agent guides and Remade Launcher.

These Terms govern your use of the Remade-operated website at remade.wiki, its account and community services at api.remade.wiki, and Remade-operated catalog and update services used by Remade Launcher (the “Service”). In these Terms, “Remade,” “we,” and “us” mean Replicraft, which operates Remade. “You” means the person using those services or the organization that person is authorized to represent.

When you create an account or take an action that clearly asks you to agree to these Terms, you agree to them. If you do not agree, do not create an account or use those features. We will request additional agreement where required for a new service or a material change.

Our Privacy Policy explains how personal information is handled. It is a notice, not a request for blanket consent to all processing. The Submission Policy sets editorial eligibility requirements. Our Disclaimer provides additional context about reimplementation, third-party projects, and rights concerns.

2. Open-source licenses remain separate

These Terms govern Remade’s hosted services and community interactions. They do not replace, narrow, revoke, or add conditions to rights granted by an applicable open-source license.

The Remade website code and Remade Launcher are distributed under the licenses supplied with their respective repositories and releases. Where the MIT License applies, it continues to govern use, copying, modification, and redistribution of that software. You do not need a Remade account merely to exercise those license rights.

Third-party projects, bundled dependencies, guides, screenshots, and other materials may have different licenses. A directory listing does not grant permission to use material beyond the rights its actual rights holder provides. Publicly viewable source code is not necessarily open-source or licensed for reuse.

Suspending access to a hosted Remade service does not revoke rights you already hold under a software or content license.

3. Accounts and eligibility

Accounts and community submissions are available to people who are at least 13 years old and meet any higher applicable legal or identity-provider age requirement. If you are not legally able to enter into these Terms yourself, your parent or legal guardian must authorize your use where lawful. Do not create an account on behalf of another person without authority.

GitHub and Discord are available to authenticate website accounts. Your Remade account has its own identifier, separate from a provider username or account ID. Authentication identifies an account; it does not verify your professional qualifications, ownership of a listed project, rights in an original product, or authority to speak for its developers.

Protect your identity-provider account and devices, do not share or sell access to a Remade account, and contact us privately if you suspect unauthorized access. You are responsible for actions you authorize, including those performed by tools you connect. This does not make you automatically responsible for every unauthorized action or excuse Remade’s own obligations.

We may restrict an account involved in abuse or a security incident. A provider outage, revoked authorization, or provider account restriction may prevent login. While signed into Remade, you can explicitly connect another sign-in provider by authenticating it. If that identity already belongs to another Remade account, the accounts can be merged when a freshly verified provider email matches an email fingerprint observed on the signed-in account. Merging combines identities, votes and builder indications, counts overlapping selections once, and revokes old sessions for both accounts. Matching names or emails alone never sign you in or automatically connect accounts. We do not promise account recovery through an unconnected provider.

4. Listings, requests, and community signals

Catalog inclusion and Featured placement are editorial decisions. Submission does not guarantee publication, continued listing, a particular ranking, or eligibility for installation through Remade Launcher. Maintainers may ask for changes, decline a submission, correct inaccurate information, or remove an entry.

A Project Request expresses interest in an implementation. It is not a development contract, assignment, bounty, reservation of a product name, authorization from a rights holder, or promise that Remade or another developer will build it.

Votes, builder indications, and similar community signals, where available, express account holders’ preferences or statements. They do not establish verified development progress, ownership, popularity among unique human beings, or endorsement. Do not manipulate them through deceptive accounts, coordinated abuse, or unauthorized automation.

Project maturity, compatibility, licenses, release information, and statistics may come from contributors or upstream repositories. They may be incomplete or out of date. Check the project’s own documentation, current release, and license before relying on a listing. A “Listed on Remade” badge means that a project is listed, not that it has passed a security audit or legal review.

5. Your submissions and permissions

You retain ownership of content you contribute, subject to any existing rights or licenses. Submit only material you own or are authorized to provide, and accurately identify its source, licensing, and limitations. Do not include credentials, confidential information, or personal information you are not authorized to make public.

For content you submit to Remade, you grant us a non-exclusive, worldwide, royalty-free permission to host, reproduce, format, make necessary editorial changes, display, and distribute it as needed to operate the directory and its related public datasets, search, documentation, and community workflows. We may use service providers to perform those functions. This permission is not a transfer of ownership and does not authorize unrelated sale of your private account information.

Contributions submitted to an open-source repository are also subject to the contribution and licensing terms identified for that repository. A separately identified license on an accepted guide or other contribution remains applicable. Submitting a link to someone else’s repository does not let you relicense that repository or grant rights in its code.

Public contributions may be included in Git history, public issues or discussions, feeds, search indexes, and downloads. Public recipients may retain copies under applicable licenses. Removing an account or an entry cannot guarantee removal of independently controlled copies. We nevertheless assess correction, deletion, and other lawful requests; public availability is not a blanket exemption from privacy obligations.

The operational permission above continues only as necessary for already published material, lawful archival records, license compliance, and handling disputes or legal obligations. It does not override your statutory privacy rights or the removal terms of an applicable content license.

6. Public submissions and third-party platforms

GitHub issues, discussions, pull requests, and repository contributions are public unless expressly identified otherwise. A website form that publishes to GitHub must identify that destination before you submit. The published material can include your submitted text, links, GitHub handle, and contribution history.

Linked Discord servers and threads, external project websites, and third-party support channels are operated under their own rules and privacy practices. Linking to them does not make their operators part of Remade or give Remade access to private conversations.

You may be responsible for complying with a platform’s terms when you use it. Remade does not promise that another platform will retain, remove, or alter content at our request.

7. Acceptable use

Use the services lawfully and respect other people’s rights. Do not use Remade to distribute malware, phishing, stolen credentials, unauthorized source code or assets, pirated copies, or material that infringes another person’s rights. Do not impersonate maintainers, falsely claim affiliation or ownership, harass people, expose private information, or submit deliberately deceptive information.

Do not attempt unauthorized access, interfere with availability, evade access restrictions, or use automation to manipulate accounts or community activity. Responsible security research and lawful interoperability work are not prohibited merely because they involve analyzing software. Contact us privately about vulnerabilities, avoid unnecessary access to personal information, and do not publish usable credentials.

Developer tools and AI agents are welcome to use Remade’s intentionally public datasets in accordance with their applicable licenses. Reasonable automated access is not prohibited simply because it is automated. Respect published limits, caching guidance, and access controls; do not bypass them or place an unreasonable load on the service.

Agent instructions and community guides are untrusted third-party material. Review commands, permissions, and downloads before applying them to your environment. Listing a guide does not make it safe to execute or establish its effectiveness.

8. Remade Launcher and third-party applications

These provisions apply when you use a Remade Launcher build or its associated online services. Features vary by version, operating system, and installation method. Documentation of a planned or experimental feature is not a promise of availability.

The Launcher can retrieve catalog information, download third-party releases, and manage supported installations on your device. Depending on your actions and settings, it can write or replace files, create launch entries, run selected applications, and remove managed installations. Review the proposed operation and maintain backups of important data.

Third-party applications remain their authors’ responsibility and are subject to their own licenses, terms, and privacy practices. The Launcher does not supply rights to any original software or assets an application may require; obtain any required permissions separately. They may contact external services or access information available to their process. Remade does not control all behavior of software after it is launched.

Launcher eligibility is decided by Remade maintainers. A reviewed catalog entry, valid checksum, signature, or other integrity check is not a guarantee that an application is harmless, fully compatible, correctly licensed, or free from defects. Verification has a defined technical scope and is not a general certification of the publisher.

Where the Launcher lets you add a repository yourself, that source is separate from the maintainer-curated catalog and has not been approved merely because the Launcher can download it. Respect the additional warnings and review the publisher and release yourself. A user-added source is not automatically submitted to the public directory.

Uninstallation or rollback may not remove every file a third-party application created or reverse every external effect. Do not rely on the Launcher as your only backup or recovery system. We may remove a project from future catalog distribution without deleting or disabling an already installed application on your device.

9. Updates and connected agents

Application updates and updates to the Launcher itself have separate controls. Review both. An update can change functionality, compatibility, licensing, or third-party privacy practices.

The current documented Launcher defaults are manual installation of application updates and automatic updates to the Launcher itself for supported standalone installations. Optional application-update modes can install eligible updates when the Launcher starts or through an explicitly enabled background updater. Distribution-managed builds may instead depend on their package manager. Consult the settings and release documentation for your build.

Selecting an automatic mode authorizes the operations described by that mode. It does not authorize unrelated access to your files, undisclosed telemetry, new paid services, or permission changes outside that scope. You may change the available settings; stopping updates may leave known defects or security issues unresolved.

If you connect the Launcher to an AI assistant or automation tool, review the permissions you grant and the operations it proposes. Local integration does not necessarily mean that the assistant keeps all information on your device. The assistant or model provider has its own data practices. Do not supply a tool with credentials or destructive permissions it does not need.

10. Moderation, rights concerns, and ending access

We may remove content, limit functions, or suspend access where reasonably needed to address policy violations, suspected infringement, abuse, security risks, service integrity, or a legal obligation. Where appropriate and lawful, we will explain a decision and consider a request for review. We may act without advance notice when delay would increase harm or compromise an investigation.

Report copyright, trademark, privacy, or other rights concerns using the private contact on our Disclaimer page. Identify the relevant content and explain your concern and authority to raise it. Do not place sensitive supporting material in a public GitHub issue. We may remove access while reviewing a report without deciding the underlying legal dispute.

We may terminate accounts of repeat infringers in appropriate circumstances. These Terms do not represent that Remade has registered a designated DMCA agent or satisfies every condition of a statutory safe harbor.

You may stop using the services at any time. You can request account closure through the private contact described in the Privacy Policy. Logout ends a session; it is not an account-deletion request. Account closure, removal of public contributions, and uninstalling local software are different operations.

11. Availability and warranties

To the extent permitted by applicable law, the hosted services and information are provided “as is” and “as available,” without a promise of uninterrupted access or warranties of merchantability, fitness for a particular purpose, non-infringement, or complete accuracy.

We do not guarantee that a project will remain available, that an original software vendor authorizes a reimplementation, or that a download will satisfy your needs. Nothing here certifies clean-room development or determines whether a particular reimplementation is lawful.

Open-source software warranties and disclaimers are governed by its applicable license. This section does not remove a warranty, remedy, or duty that cannot lawfully be excluded.

12. Limits on liability

To the extent applicable law allows, Remade is not liable under these Terms for indirect, incidental, special, or consequential losses arising from use of the hosted services, including lost profits or business opportunities. This exclusion applies only where such losses may lawfully be excluded and does not turn direct losses into indirect losses by relabeling them.

Nothing in these Terms excludes or limits liability for fraud, willful misconduct, gross negligence where it cannot be excluded, death or personal injury where exclusion is prohibited, or any other liability or mandatory consumer or data-protection remedy that law does not allow us to exclude or limit.

These Terms do not impose mandatory arbitration, a class-action waiver, or a general obligation for individual community members to indemnify Remade. Any limitation under a third-party software license is a separate matter.

13. Changes to the services and these Terms

We may improve, change, or discontinue hosted features. We will provide reasonable notice of a material service change where practical and required by law. Existing rights under open-source licenses remain separate.

We will publish changes to these Terms with an updated Last Updated date. Material changes affecting account obligations will receive a prominent notice, and we will request renewed agreement where required. We will not treat a silently changed page as consent to a new use of personal information requiring separate consent.

The version applicable to an earlier event remains relevant to that event. A later revision does not retroactively remove mandatory rights or change an existing license grant.

14. Governing Law

These Terms and your use of the Service are governed by the laws of the State of California, without regard to its conflict-of-laws principles.

Nothing in these Terms limits any mandatory consumer rights or protections that cannot lawfully be waived under applicable law.

15. Dispute Resolution

Before filing a formal legal proceeding arising out of or relating to these Terms or the Service, you and Replicraft agree to make a reasonable good-faith effort to resolve the dispute informally.

You may contact us through the legal contact on our Disclaimer page with a description of the dispute and the relief you are requesting.

If the dispute cannot be resolved informally, and except where applicable law provides otherwise, any judicial proceeding arising out of or relating to these Terms or the Service will be brought exclusively in the state or federal courts located in San Francisco County, California.

You consent to the personal jurisdiction and venue of those courts.

16. General Provisions and Contact

If a provision is unenforceable, the remaining provisions continue only to the extent they can lawfully do so. Our failure to enforce a term on one occasion is not a general waiver of it.

Please contact Replicraft privately through the legal and privacy contact with questions or concerns about these Terms.