Privacy Policy

1. What Data We Collect

This static site provides download information, configuration guides, and protocol references. It has no account registration and does not ask for your email address. You can read the content without submitting your name, phone number, or subscription URL. There are no forms for uploading configuration files, node details, or connection logs.

When you visit a page or request a file, the hosting infrastructure receives network information needed to fulfill the request, such as your IP address, request time, resource path, response status, and browser headers. These operational logs help deliver content, troubleshoot errors, and detect unusual traffic. They are not records of proxy connections made by a client.

Our pages do not need to access client configurations stored on your device, and the site does not receive proxy passwords or subscription data. You download and run installation files yourself. For data generated by a client on your device, consult the documentation for that product.

2. Analytics and How We Use Data

We use analytics to understand page visits, referral sources, device and browser types, and interactions such as using download links or switching platforms. The results help us find broken links, improve site structure, and make pages easier to read on mobile devices. Analytics are not used to monitor client connection quality or proxy traffic.

Analytics requests may include the page URL, referring page, and time of visit. Do not include subscription URLs, passwords, or personal information in query parameters on this site, or share links that contain sensitive information.

Operational logs and analytics serve different purposes. Their retention methods and periods depend on the hosting environment, analytics settings, and troubleshooting needs. We do not make unverifiable promises of immediate deletion, nor do we infer what proxy content an individual uses from their browsing activity.

3. Cookies and Local Storage

This site does not set cookies for account sign-in. Depending on the analytics configuration, analytics may use cookies or similar browser identifiers to distinguish visits. The absence of a sign-in page does not, by itself, mean that your browser stores no analytics-related data.

Language switching and platform selection can work through page paths and URL fragments without storing subscription data. Your browser may also cache fonts, scripts, stylesheets, and other page resources. Resource caching is different from cookies used to distinguish visits.

Use your browser's site settings to view, restrict, or clear cookies and local storage, or use privacy tools to limit analytics scripts. Blocking analytics usually does not affect reading static content, but blocking all scripts may affect expanded navigation, platform tabs, and updated download links. Clearing browser data does not delete logs already created on the server.

4. Download Requests and Third-Party Links

This site links to client websites, app stores, and project resources. After you follow a link, the destination service may receive your IP address, browser information, and referral data, and handle it under its own policies. This policy does not replace third parties' privacy policies. Read the destination site's terms before submitting information or installing software.

Download links may redirect through this site to a file host. A link showing this site's domain does not mean the file transfer takes place only through our site. Check the client name, supported operating system, and destination address. If a redirect, permission request, or installation prompt looks unexpected, stop and consult the project documentation.

5. Policy Updates and Questions

If our data practices, analytics settings, or site features change, we will update this page and revise the month shown at the top. Refer to the current version. Policy updates do not replace your browser's privacy settings or change the rules that apply to third-party services.

If your question concerns installation permissions, importing subscriptions, or connection behavior, start with the Clash Getting Started Guide to distinguish website visits from client activity. When troubleshooting, record only the error details you need. Before sharing screenshots or logs through any external feedback channel, redact subscription URLs, authentication details, personal file paths, and other sensitive information.