Disclaimer

Last updated: March 2026

This disclaimer applies to the pages, configuration guides, and download links provided at clash26.com. Before using this content, review the scope of our services and the risks outlined below. Consider your own environment before making changes involving personal data, device permissions, or network settings.

1. Site purpose and scope

Clash Docs Center is an independent guide to Clash, offering tutorials, links to client downloads, and config.yaml configuration examples. We explain how clients, cores, and configuration fields relate, helping you choose software for your operating system and understand basic settings.

Our download directory includes clients maintained by different projects. Listing software does not mean we develop, publish, or operate it. Refer to each project's release notes for its licensing, maintenance status, and features. We do not provide proxy nodes, subscription accounts, or network access. Examples in our guides are not a promise to provide these services.

2. Software and configuration risks

You are responsible for deciding whether to install software, run it, or change its configuration. System proxy, TUN, DNS, and LAN listening settings can change how your device connects, potentially causing network outages, connection failures in apps, or changes to request routing. Back up your existing configuration before making changes, keep track of what you change, and make sure you can restore your system's network settings.

Before enabling allow-lan, check the listen address, firewall rules, and which devices can access your network. Confirm why an action requires administrator privileges before granting them. Never publish configurations containing subscription URLs, passwords, or access tokens. To the extent permitted by law, you are responsible for losses caused by your device environment, configuration errors, or third-party software defects. Nothing in this disclaimer limits liability that cannot legally be excluded.

3. Accuracy and version compatibility

Our guides are based on the versions and information available when they were written. Client updates may change menu names, settings locations, supported fields, and default behavior. The same YAML field may work differently across cores and clients; a similar-looking interface alone does not establish compatibility.

We strive to match our guides to the actual configuration fields, but cannot guarantee that every page covers every version, platform, or network environment at all times. Configuration snippets illustrate specific structures and should not be used as complete replacements unless the page explicitly says so. If results differ from a guide, check the client logs and release notes for your version, then troubleshoot one change at a time. Avoid piling on unverified changes.

We may link to app stores, project websites, and other reference pages. These links help you find resources or additional information; they do not mean we control those sites or guarantee their content, service quality, or future availability.

Accounts, payments, data submissions, and services accessed through external links are subject to the destination platform's terms and privacy policy. Verify the destination URL and what you are authorizing. Third-party pages may go offline, resources may be withdrawn, regional availability may change, or access may be interrupted, affecting downloads and reference materials. We cannot guarantee that external resources will remain available and do not handle disputes involving third-party transactions or accounts.

5. Lawful use and support

You must comply with applicable local laws, network policies, and the terms of any services you use. Our explanations of configuration syntax and connection methods are technical information, not legal advice, and do not authorize access to networks, systems, or data without permission.

If you have trouble importing a configuration, choosing a mode, or connecting, review the steps in our Getting Started guide, then check the relevant fields in the configuration reference. Remove subscription links and account credentials before sharing diagnostic details. We may revise this disclaimer as features and content change; updates will be posted on this page. Revisions do not affect rights you have under applicable law.