Privacy Policy
Last updated: August 2026
This policy applies to the Clash Docs Center website at clash-amd64.com. It explains how data is handled when you browse the documentation, use site navigation, or visit download pages. This is a static content website; network activity and data processing within a client after installation are outside the scope of this policy.
1. Data We Collect
This site does not offer account registration, ask visitors for their name, email address, or phone number, or allow online uploads of subscription or configuration files. You can read YAML examples, switch tabs, and copy code without submitting your personal configuration. Do not include real subscription URLs, node credentials, or management API keys in publicly shared page links.
When you visit the site, the servers and delivery infrastructure hosting it receive information needed to fulfill your request. This may include your IP address, request time, page path, browser identifier, and response status. These technical records help deliver pages, troubleshoot access issues, and detect unusual requests. A static website can still generate server access logs.
2. Website Analytics and How We Use Them
We use website analytics to understand which pages are read, where visitors come from, and which entry points they use. We may also record certain actions, such as switching platforms on a download page. This helps us identify installation guides that need more detail, links that may be broken, and usability issues across devices.
Analytics data may include pages visited, referring pages, device and browser categories, visit times, and interaction events. We do not ask visitors to link this data to a name or account, and documentation pages do not access client proxy traffic, node lists, or connection logs. Avoid including sensitive information in URL query parameters, as it could be captured in technical records alongside the page address.
3. Cookies and Local Storage
Depending on the site’s configuration, analytics may use cookies or browser storage to distinguish visits and avoid counting the same visit more than once. Whether data is stored, how long it is kept, and which keys are used can be checked in the storage records for this site in your browser. Site tabs may also use URL fragments to remember the selected tab; fragments are not cookies.
You can view, restrict, or clear this site’s cookies and local storage in your browser’s privacy settings, or use your browser’s script-blocking features. Blocking analytics scripts generally does not affect access to static content, but disabling all scripts may affect shared navigation, tabs, and copy buttons. Clearing browser storage does not delete access records already generated on the server.
4. Downloads and Third-Party Links
Documentation pages may link to app stores, client websites, and open-source project pages. When you follow a link, the destination handles your data under its own policies; the relevant service is responsible for its accounts, payments, permission requests, and privacy settings. Download files may also be served through separate file-delivery infrastructure, which generates necessary network records when processing download requests.
Before visiting an external page, check the destination domain, app name, and publisher, and read the applicable privacy information. Before installing a client, make sure the package supports your operating system and processor architecture, and understand why it requests system proxy, VPN, or TUN permissions. This website’s privacy policy does not replace a client’s own privacy policy or guarantee how an external service will act in the future.
5. Policy Updates and Questions
If our analytics methods, storage purposes, or third-party integrations change, we will update the relevant terms on this page and revise the date at the top. We will explain significant new data uses when the relevant processing begins. Check this page periodically for the current scope of data processing.
To determine whether an action took place on the website or in a client, start with the instructions in the user guide and check your browser’s site permissions and storage records. When troubleshooting, share only the details needed to describe the issue. Remove subscription URLs, access tokens, and other personal information from screenshots or logs before sharing them.