Skip to content
remade.wiki

Privacy Policy

Last Updated: October 27, 2026

Replicraft (“we,” “us,” or “our”) operates Remade. This Privacy Policy explains how we collect, use, disclose, and protect personal information when you use remade.wiki, our account services at api.remade.wiki, and Remade-operated services associated with Remade Launcher (the “Service”).

This Policy does not govern independent project websites, GitHub, Discord, or applications you discover through Remade. Those services have their own privacy practices.

1. Scope and Our Role

Remade is a community-maintained directory of independently developed software reimplementations, supporting tools, and Project Requests.

You can browse the directory without an account. If you sign in, we process account information to provide features such as request upvotes and builder indications.

Replicraft determines how information is used to operate those Remade features. A developer whose project is listed remains responsible for that project’s own software and services.

2. Information We Collect

The information we process depends on how you use Remade.

2.1 Account Information

If you sign in with GitHub or Discord, we may receive:

  • your provider account ID;
  • username;
  • public display name;
  • avatar URL; and
  • verified email information made available by that provider.

We assign a separate Remade account ID and store its connection to your sign-in identities. We do not receive your provider password or request access to private GitHub repositories through website sign-in.

GitHub sign-in requests access to verified email addresses, including private and secondary addresses. Discord sign-in requests identity and email information, and we use the email only when Discord reports it as verified.

We temporarily process those addresses to help detect duplicate accounts. We store private email fingerprints rather than raw addresses. These fingerprints can be matched to a known address and are personal information, not anonymous data. Provider access tokens are discarded after the sign-in process.

Connecting another sign-in method requires you to be signed in and authenticate that provider. If it belongs to an existing Remade account, a matching verified email can allow the accounts to be merged. Their identities and activity are combined, overlapping votes count once, and old sessions are revoked. A matching email by itself never signs you in or automatically connects accounts.

2.2 Request Activity

If you upvote a request or indicate that you are building it, we store:

  • the request identifier;
  • your Remade account ID;
  • your selection; and
  • the associated timestamp.

These records let you manage your selections and allow one active selection per account. The public interface shows totals. Signed-in users can also see their own selections; it does not publish a general list of other voters or builders.

2.3 Public Contributions and Catalog Information

We process information submitted through public issues, pull requests, catalog entries, and other contributions. This may include:

  • project names and descriptions;
  • repository and website links;
  • contributor handles and attribution;
  • compatibility and licensing information;
  • screenshots or links to images; and
  • other information a contributor chooses to provide.

We also obtain public project information from repositories, release metadata, and community contributions. A public author handle may appear in the catalog even if its owner has no Remade account.

Our request page currently directs submissions to GitHub’s public issue form. Material you publish there is also handled by GitHub under its own policies. Do not include private information in a public submission.

2.4 Technical Information

When you connect to the Service, our hosting and security providers receive information needed to deliver and protect the connection. This may include:

  • IP address;
  • browser or client information;
  • requested pages and resources;
  • request timestamps;
  • response status;
  • referring pages, where supplied; and
  • security or diagnostic information.

Requests for public datasets, embedded badges, and downloads can also produce connection information. A static website does not prevent its hosting provider from receiving network requests.

2.5 Communications

If you contact us, we receive your message, return address, attachments, and any account or case information you provide.

We use that information to respond and handle the request. Do not send passwords, access tokens, or unnecessary identity documents.

3. Cookies and Browser Storage

We use cookies and browser storage for:

  • authentication and maintaining sessions;
  • protecting sign-in and account-linking attempts;
  • deciding whether to check for an existing session;
  • confirming a recent sign-in attempt; and
  • remembering your last-used sign-in provider.

The ordinary session lifetime is up to 30 days unless the session ends sooner. Temporary authentication cookies last up to 10 minutes and are normally cleared after the callback. The session credential is protected by an HttpOnly cookie; our database stores a hash rather than the raw credential.

The last-used preference contains only a provider name. Temporary notification markers are not session credentials.

You can control or clear storage through your browser. Doing so may affect sign-in and preferences, but an account is not required for public browsing.

4. How We Use Information

We use personal information to:

  • provide and maintain the website and its public catalog;
  • authenticate accounts and maintain sessions;
  • provide request voting and builder indications;
  • connect sign-in methods at your request;
  • reduce duplicate or abusive account activity;
  • review submissions and attribute public contributions;
  • respond to support, privacy, and rights concerns;
  • investigate failures, abuse, or security incidents;
  • enforce our service and submission rules; and
  • comply with applicable law and protect people’s rights.

Agreement to service terms does not authorize unrelated advertising, optional analytics, or new Launcher permissions.

Where applicable law requires a legal basis, the basis depends on the information and the purpose. It may include:

  • providing an account or feature you request;
  • legitimate interests in operating, securing, and maintaining the Service, subject to your rights;
  • complying with legal obligations; or
  • consent for a particular use where required.

Where processing relies on consent, you may withdraw it without affecting earlier lawful processing.

6. How We Disclose Information

We do not sell or rent personal information or share it for cross-context behavioral advertising.

6.1 Service Providers

We use providers to deliver and support the Service, including hosting, database, identity, security, and communication services. They may process information needed to perform those functions.

Cloudflare provides website delivery, the Worker API, D1 storage, and associated infrastructure and security services. See the Cloudflare Privacy Policy.

GitHub provides optional sign-in, public repository and contribution workflows, release information, and file distribution. See the GitHub General Privacy Statement.

Discord provides optional sign-in and operates the community destinations linked from Remade. Website sign-in does not request bot installation, guild membership, or private messages. See the Discord Privacy Policy.

Identity-provider avatar services may receive a request when your browser loads an avatar. Contacting us also involves the providers used to deliver and store correspondence.

6.2 Public Information

Public catalog entries, issues, pull requests, attribution, and other published contributions can be accessed by people, search engines, and automated tools. They may appear in public datasets, search indexes, and repository history.

This does not give the public access to private session credentials or the account database.

We may disclose relevant information where reasonably necessary to:

  • comply with a valid legal requirement;
  • investigate abuse or a security incident;
  • protect rights, property, or safety;
  • enforce our agreements; or
  • establish, exercise, or defend legal claims.

A complaint does not automatically justify publishing the complainant’s private information.

6.4 Change of Operator

If responsibility for Remade changes, information may transfer where lawful and necessary to continue the Service. We will provide notices and obtain any permission required for a materially different use.

7. Public Information and Third-Party Copies

Consider what you choose to publish. Public material may be copied, cached, indexed, archived, or redistributed by others.

Removing a current listing or closing a Remade account does not guarantee removal from independent repositories, GitHub history, search caches, or third-party websites.

We still assess correction and deletion requests for information we control. Public availability is not a blanket reason to disregard a privacy request.

8. Your Privacy Rights

Depending on your location and applicable law, you may have rights to:

  • request access to information we hold about you;
  • correct inaccurate information;
  • request deletion;
  • receive a portable copy of certain information;
  • object to or restrict certain processing;
  • withdraw consent where processing relies on it; and
  • complain to an applicable data-protection authority.

Use the private contact on our Disclaimer page to make a request. We may need proportionate verification, such as confirming control of a connected account. Do not post personal evidence in a public issue.

Some requests may be subject to lawful exceptions. We will explain an applicable refusal, exception, or permitted extension. We do not discriminate against people for exercising protected privacy rights.

9. Accessing and Updating Information

You can change your provider profile through GitHub or Discord. Remade refreshes provider information during subsequent sign-ins, but that does not automatically change every public contribution or attribution record.

You can connect an additional sign-in method and manage supported request selections through the Service. For other corrections or account-data requests, use the private contact.

10. Account and Data Deletion

You may request closure of your Remade account and deletion of associated personal information through the private contact.

Signing out ends a session; it is not an account-deletion request. Revoking authorization at GitHub or Discord also does not necessarily end a Remade session already issued to your browser.

Deletion requests may be subject to information we are permitted or required to retain for security, legal compliance, dispute resolution, or another applicable exception. Backup and recovery copies may remain subject to their retention cycles.

Account closure, removal of public contributions, and deleting a provider account are separate actions. Closing your website account does not uninstall applications or remove Launcher files from your device.

11. Data Retention

We retain personal information for as long as reasonably necessary for the purposes described in this Policy, subject to applicable legal requirements.

Relevant factors include:

  • the type of information;
  • the purpose for which it was collected;
  • whether an account or selection remains active;
  • security and abuse-prevention needs;
  • requests for deletion;
  • applicable legal requirements; and
  • backup and recovery processes.

A record’s validity and its physical deletion are different. For example, an expired session can no longer authenticate you, but expiration alone does not remove its database row.

Public contributions may remain where needed for attribution, applicable licenses, historical records, or lawful moderation. We assess privacy requests individually rather than promising that every independently controlled copy can be erased.

12. Security

We use safeguards designed to protect personal information, including protected authentication cookies, hashed session credentials, encrypted transport, access controls, and separation of private account data from the public catalog.

No method of transmission or storage is completely secure. Protect your provider accounts and devices, and report suspected misuse through the private contact. Do not include live credentials in a public report.

13. California Privacy and Browser Signals

The information categories, purposes, recipients, and request options described in this Policy also apply to our handling of California residents’ information. Where California privacy law applies, we provide the rights and disclosures it requires.

13.1 Do Not Track

Some browsers send a Do Not Track (DNT) signal. Remade’s account and catalog features do not currently change based solely on that signal. DNT does not end an existing session or prevent the connection processing needed to serve a page.

13.2 Global Privacy Control

Global Privacy Control (GPC) communicates a request to opt out of sale or sharing for cross-context behavioral advertising. Our no-sale and no-sharing policy applies whether or not you send that signal. GPC is distinct from DNT and does not itself disable essential authentication storage.

13.3 Third-Party Services

Hosting, identity, and security providers process information needed to provide their services. Independent websites and applications you visit through Remade have their own settings and privacy practices.

14. Minors

Remade accounts are available to people aged 13 or older, subject to any higher applicable legal or identity-provider requirement. People under 13 may not create a Remade account.

If you are not legally able to agree to the applicable terms yourself, a parent or legal guardian must authorize your use where lawful.

If you believe an ineligible child has provided account information, use the private contact so we can review and take appropriate steps. An age statement does not replace our obligations under applicable law.

15. International Processing

Our service providers may process information in the United States and other countries where they operate. Those countries may have different privacy laws from your country.

Where applicable law requires safeguards for international transfers, the relevant processing must use an applicable lawful mechanism. You may contact us for information about processing relevant to your account.

16. Remade Launcher and Independent Applications

If you use Remade Launcher, the information processed depends on your build, settings, and actions. The Launcher may keep application identifiers, selected sources, versions, installation locations, preferences, and diagnostic information on your device.

Catalog requests, update checks, and downloads contact Remade, GitHub, or the relevant release hosts. Those recipients receive connection details and the requested resources. A checksum or signature does not make a network request anonymous.

An optional GitHub credential used by the Launcher is separate from website sign-in. Review your build’s storage and removal controls before supplying one.

If you connect an AI assistant or automation tool, it may receive operation results, application information, or filesystem paths. A local connection to the Launcher does not guarantee that the assistant keeps those results on your device.

Installed applications, connected assistants, and independent publishers have their own privacy practices. Removing the Launcher or a Remade account does not necessarily remove their files or backups.

17. Changes to This Policy

We may update this Policy as the Service, our practices, or applicable law changes. When we do, we change the Last Updated date at the top.

Material changes may receive additional notice through the Service or another appropriate method where required. A revised Policy does not itself authorize an unrelated use of information or replace consent where consent is required.

18. Contact

Questions, privacy requests, and concerns may be sent to Replicraft through the legal and privacy contact on our Disclaimer page.