LEGAL / DISCLAIMER

Disclaimer

Last updated: August 2026

By accessing, browsing, or using this site, you confirm that you have read and understood this disclaimer. The site provides Clash client download guidance, configuration references, setup instructions, and Troubleshooting resources. This disclaimer clarifies the site’s purpose, the scope of the information provided, and the responsibilities visitors assume when using software and third-party services.

1. Site Status and Project Relationships

This site is an independently maintained resource and download guide. It is not the official website of Clash, Mihomo, or any related graphical client project, nor does it represent their developers, maintainers, contributors, or distribution platforms. Project names, client names, trademarks, and other identifying information shown on this site are used to describe the software and help visitors locate the relevant resources.

The Clash ecosystem includes open-source cores and clients maintained by different teams. Each project has its own license, release process, maintenance cycle, and supported platforms. This site categorizes and introduces these projects; it does not constitute an authorized agency, joint operation, product endorsement, or promise of ongoing maintenance. For licensing, feature scope, and project status, refer to the project’s actual published materials.

2. Download Guidance and Software Sources

The download pages organize available links for platforms including Windows, macOS, Linux, Android, and iOS. Some buttons may lead to project release files, app store pages, official project websites, or file paths forwarded by the deployment system. Clients do not share a single release schedule, and file names, system architecture requirements, and support status may change as projects evolve.

Before downloading, visitors should confirm the client name, operating system version, and processor architecture, and review the maintenance status shown on the page. Software that is no longer maintained may not receive future compatibility fixes; its current usability should not be judged solely by old tutorials or past experience. Visitors are responsible for assessing and accepting the consequences of choosing the wrong build, installing an incompatible package, encountering system restrictions, or using a project that is no longer maintained.

3. Software Risks and Responsibility

Proxy clients may interact with system proxies, DNS, virtual network adapters, routing rules, network permissions, and configuration files. Incorrect settings can interrupt connectivity, cause DNS resolution problems, restrict local network access, prevent applications from connecting, or leave the system proxy unrecovered. Before enabling TUN, service mode, or administrator permissions, understand how each feature affects the current system network stack and keep the original settings available for recovery.

The information provided by this site is not a guarantee of suitability for any particular purpose, network environment, or configuration. Visitors must comply with applicable local laws, network service terms, software licenses, and device-management requirements, and independently assess subscription sources, node services, rule files, and custom configurations. To the extent permitted by applicable law, this site is not liable for direct or indirect losses arising from installing, configuring, updating, uninstalling, or using related software.

4. Content Accuracy and Version Changes

Tutorials and configuration references are prepared based on the client interfaces, core behavior, and configuration formats that could be verified when they were written or updated. After a project update, button labels, menu locations, default options, field meanings, and system requirements may change. Different forks or third-party clients may use different configuration-merging logic and interface terminology even when they rely on similar cores.

This site will correct obvious errors within reason, but cannot guarantee that every page will always match the latest version of every client. When operating the software, prioritize the information shown by the current client, its runtime logs, and the project documentation. If the steps on a page differ from the actual interface, first review the general process in the User Guide, then use the FAQ to check version differences and the recommended Troubleshooting order.

5. External Links and Third-Party Services

This site may link to app stores, official project websites, open-source project pages, and other third-party resources. These links are provided for additional information or to help visitors reach relevant pages; they do not mean that this site endorses or guarantees third-party content, service quality, continued availability, privacy practices, or transaction terms.

Third-party pages may change their addresses, content, access requirements, or service policies without notifying this site. After leaving this site, visitors should read the target page’s terms of use and privacy rules. Consequences arising from an unavailable third-party page, changed content, account restrictions, service interruptions, or other third-party actions should be handled by the relevant provider and visitor according to the provider’s rules.

6. Scope of This Disclaimer and Content Feedback

This disclaimer applies to the pages, tutorials, download guidance, and configuration materials provided by this site. The site may update this disclaimer based on content structure, project status, or applicable rules; revisions take effect when published on the page. Before continuing to use the site, visitors can use the update date shown at the top of the page to decide whether they need to read this disclaimer again.

If you find that tutorial steps no longer match the current version, a page link is broken, or a term is unclear, first check the existing guidance in the FAQ. When you need to reinstall and reconfigure the software, follow the order provided in the User Guide to avoid changing multiple network options at once and making Troubleshooting more difficult.