Privacy Policy

1. Scope and Data Boundaries

The FlClash Official Site is a static website offering download links, setup guides, and troubleshooting information. There is no account registration, email signup, or subscription form. You can read documentation, browse pages, and view download links without submitting your name, phone number, or email address.

The website and the FlClash client involve separate data processing. For subscription URLs, proxy settings, connection logs, and system permissions in the client, refer to the software you installed and the services you use. This website does not access client settings on your device or ask you to upload subscription details. Do not include URLs containing access credentials in links to this site or share them publicly as feedback.

2. Access Logs and Analytics

When your browser requests a page or download, the infrastructure serving it may receive your IP address, request time, resource path, response status, and request headers sent by your browser. This information is used to deliver content, investigate access issues, and protect service security. A static website can still generate network logs.

This site uses analytics to understand page visits, referral sources, device types, and download platform selections. These insights help identify broken links, improve the mobile reading experience, and refine documentation. A platform selection event only records a change to the download category; it does not confirm a successful installation or reveal network activity in the client.

Analytics may receive page URLs and referral information, so do not include subscription keys or other private information in URL parameters. This site does not use analytics to collect proxy node details. How long infrastructure logs and analytics data are retained depends on the deployment configuration; this policy does not promise a specific retention period that has not been verified.

3. Cookies and Local Storage

This site does not have account login sessions. Analytics tools may use cookies or similar browser identifiers to associate visits, or may run without writing cookies, depending on the analytics configuration actually loaded on the page. A static website does not, by itself, mean analytics never uses browser storage.

The selected tab may be preserved in the URL fragment. This is different from using cookies or local storage. Your browser may also cache pages, fonts, and scripts to avoid repeat requests.

You can view and clear this site's cookies, site data, and cache in your browser settings, or restrict analytics scripts. Blocking analytics usually won't affect access to static page content, but blocking functional scripts may affect navigation or updated download links. Clearing this site's data does not remove settings from the FlClash client.

4. Downloads and Third-Party Links

The download page may request package metadata to update download URLs and version information. When you click a package, project website, or app store link, the request may be handled by another provider. That provider can access the network information needed to fulfill the request, and its own privacy policy and terms apply.

This policy does not cover external websites, app stores, subscription services, or the client itself. Before downloading, check the selected platform, processor architecture, source page, and release notes. During installation, review system prompts and permission requests. Links on this site do not mean we can control how external services store data or change their practices.

5. Policy Updates and Questions

If analytics methods, site features, or links to external services change in a relevant way, this page will be revised and the date at the top updated. Check this page again before using download or interactive features. Actual data handling depends on the page features available and your browser settings at the time of your visit.

For questions about using the website or configuring the client, see the FAQ or Getting Started Guide. When troubleshooting, share only the error details needed and redact subscription URLs, access credentials, and personal network information. Do not publish your full configuration to explain an issue.