Terms of Use
Last updated: October 2026
These terms apply to the documentation, configuration examples, client information, and related links provided by clash-amd64.com. Read them before using these resources. If you disagree with any of these terms, stop using the relevant content. Nothing in these terms limits rights that cannot be excluded by law.
1. Purpose and Scope
Clash Docs Center brings together installation, configuration, and troubleshooting resources for Clash clients and the mihomo core. This content is for educational, technical research, and reference purposes only; it is not legal, security, or network service advice. We do not provide proxy nodes, subscription accounts, or internet access, and we make no commitments on behalf of the projects covered here.
Field definitions and instructions may vary by core version, client implementation, and system environment. Configuration examples illustrate syntax and behavior; they are not complete solutions for every device. Consult the project documentation and your local settings, back up your existing configuration, and test changes one at a time.
2. Lawful Use and User Responsibilities
You must comply with the laws and regulations where you are located and in any jurisdiction relevant to your activities, as well as the rules of network operators, device owners, and related services. Do not use these resources or the software they describe for illegal activity, unauthorized network access, privacy violations, system damage, or intellectual property infringement.
Obtain any required authorization before changing proxy, DNS, routing, or firewall settings on a workplace, school, or other managed network. You are responsible for assessing whether your destinations, configuration sources, and subscription services are lawful and trustworthy, and for your actions and their consequences.
3. Third-Party Software and External Links
The software covered here is provided by its respective open-source projects and maintainers. Each project determines its client interface, core behavior, release schedule, and maintenance status. Our coverage and download links do not imply project authorization or mean that we control the software or related services.
External websites, app stores, and subscription services are governed by their own terms and privacy policies. Links may change or stop working, and software features may change with updates. Before installing, review the project’s release notes and confirm your system architecture, required permissions, and compatibility. Do not share subscription URLs or access credentials in public feedback.
4. Risks and Limitation of Liability
We make reasonable efforts to keep our information accurate, but do not guarantee that it will always be complete or up to date. We also do not guarantee that software will remain available, suit a particular purpose, or work in every environment. Network connectivity, system permissions, third-party services, and local configuration can all affect results.
Changing network settings may interrupt connectivity, cause apps to malfunction, or result in lost configuration. Keep backups and a recovery plan, and test changes in an isolated environment before using them for critical work. To the extent permitted by law, we are not liable for data loss, business interruption, or other damages arising from the use or unavailability of these resources, software, or external services, except where liability cannot legally be excluded.
5. Intellectual Property and Open-Source Licenses
Software names, trademarks, graphics, and third-party documentation remain the property of their respective owners. We refer to or quote these materials only to identify projects and explain technical matters; doing so does not change ownership. The license agreements and copyright notices accompanying each open-source project govern its use, modification, and redistribution.
Open source does not waive requirements for attribution, license copies, or source code. Check the applicable license before copying software or using examples in another project. When quoting original material from this site, credit the source. Do not remove attribution or present it as information published by a project’s official team.
6. Changes to These Terms and Support
We may revise these terms as our content, maintenance practices, or applicable laws change. Revisions will be published on this page, and the last-updated month at the top will be changed accordingly. Unless stated otherwise, revisions take effect when published. They do not retroactively alter rights or obligations established by law. Check the current terms before using our resources.
For configuration help, start with the user guide, then check the YAML manual for field definitions and version differences. When documenting an issue or contacting the relevant project, include your system, client, and steps to reproduce the problem, and remove sensitive information from logs.