Privacy Policy · app-flclash.com

FlClash Website Privacy Policy

This policy applies only to website-level data processing on app-flclash.com. It explains technical request data, browser storage, information you intentionally submit and third-party links. FlClash is a separate open-source client for Android, Windows, macOS and Linux; its local Profiles, proxy nodes, Rules, DNS, Logs and network traffic are not automatically sent to app-flclash.com simply because you visit this site.

Server & technical logsCookies & browser storageGitHub & third-party linksRetention & user rights

1. Scope and website boundary

This Privacy Policy applies to website-level processing when you visit app-flclash.com, including page requests, server or infrastructure logs, browser storage, on-site interactions, external-link navigation and information you intentionally submit through any contact or feedback channel that is actually provided on the site.

app-flclash.com is an information website about FlClash and Mihomo. It is not the FlClash development team, the chen08209/FlClash GitHub repository, the Mihomo project or their maintainers. The site publishes download guidance, configuration tutorials, FAQs and developer material, but that does not make it the operator of those open-source projects.

Profiles, subscription URLs, proxy nodes, proxy groups, Rules, DNS settings, Connections, Logs, WebDAV settings and network traffic handled locally by the FlClash application are not automatically transmitted to app-flclash.com merely because you visit this website. If you choose to send any of that information through a feedback channel, it becomes information you intentionally submitted.

2. Information the site may process

When you access the site, the server, hosting platform, CDN, DNS provider or security infrastructure may process technical data needed to complete the request, such as IP address, request time, requested path, HTTP status, referrer, browser or operating-system type, device category, language, User-Agent and basic network logs. The exact fields depend on the deployed infrastructure.

You do not need to create a FlClash account to read the site, and normal page access does not require you to provide identity documents, payment details, proxy subscriptions, node passwords, Secrets, API Tokens or private keys.

If the site actually provides and enables a contact form, email address or another feedback channel, it may receive the information you choose to submit, such as your name or alias, email address, issue description, page URL, screenshot or device details. Remove full subscription URLs, proxy credentials, Tokens, private keys, payment information and other unnecessary sensitive data before submitting a report.

3. How information is used

Technical request data may be used to deliver pages, maintain connections and caching, diagnose errors, investigate abusive traffic, block attacks, repair broken resources, improve compatibility and maintain infrastructure security. Usage analytics are relevant only if an analytics feature is actually deployed.

Information you intentionally submit may be used to understand the reported issue, respond when needed, reproduce a page error, correct a broken link, address a security concern or improve site content. It should not be expanded to unrelated purposes unless required by law or separately authorized.

4. Cookies, browser storage and access logs

Whether app-flclash.com writes cookies, localStorage, sessionStorage or other browser storage depends on the functions that are actually deployed. Necessary site state, security controls, language preferences or interface settings may use browser storage; this policy does not imply that analytics, advertising or account-tracking features are enabled when they are not.

Browser cache improves loading of static resources and is not the same as creating a personal account or long-term identity profile. You can review, delete or restrict cookies, cache and site storage through your browser, although disabling necessary storage may affect site state, preferences or some security features.

Server, CDN or security logs are separate from browser cookies. Access logs are usually generated automatically by network requests, while cookies and local storage are read or written by the browser according to the site functions and third-party scripts that are actually in use.

5. Infrastructure providers and information sharing

The site may depend on DNS, hosting, CDN, security, error-monitoring, email or other operational services. Those providers may process technical data only to the extent required for the services they actually perform, and their independent processing is governed by their own terms, privacy policies and legal obligations.

The site is not operated for the purpose of selling visitor personal information. If analytics, forms, email, advertising or another third-party function is added in the future, this policy should be updated to reflect the service that is actually deployed rather than describing undeployed tools as if they already exist.

Information may be disclosed when required by applicable law, when necessary to protect the site or users, or when investigating abuse or security incidents. Outside those circumstances, intentionally submitted information should not be shared with unrelated third parties without a legitimate purpose.

7. Security and retention

The site should use reasonable safeguards such as HTTPS, access controls, hosting-platform security features, software updates, log review and configuration maintenance to reduce the risk of unauthorized access, abuse, tampering or technical failure. No internet service can guarantee absolute security.

Technical logs, cache records and intentionally submitted information should be retained only for as long as they are reasonably needed for security, operations, troubleshooting or responding to feedback. Because this page does not state one fixed retention period, the actual period depends on the configuration of the hosting, security or feedback systems and any applicable legal requirements.

Do not submit full subscription URLs, proxy credentials, Secrets, API Tokens, private keys, recovery keys or other information that could directly grant access to a network service.

8. User rights and controls

You can review, delete or restrict browser cookies, local storage, cache and site permissions. You can also choose not to follow third-party links, not to submit feedback, or to remove unnecessary personal information and configuration credentials before sending a report.

Where applicable law grants those rights, and where the site can reasonably identify and control the relevant information, you may request access, correction, deletion, restriction or information about processing through any contact channel that is actually published on the site. Reasonable identity verification may be required to avoid disclosing information to the wrong person.

Server security logs, CDN records, caches or third-party infrastructure data may be generated and retained through automated technical processes and may not be individually searchable or removable in the same way as account records. For information outside the site's direct control, requests should be directed to the relevant provider.

9. Minors

app-flclash.com primarily covers a network proxy client, Profiles, Mihomo, System Proxy, TUN and developer configuration. It is not designed specifically as a child-directed online service.

Minors should use external download pages, system network settings and feedback channels with appropriate supervision and should not submit account credentials, proxy subscriptions, payment information, access Tokens or other sensitive personal data.

10. Policy updates

This Privacy Policy may be updated when app-flclash.com changes its hosting, site features, cookie use, analytics tools, feedback channels, third-party services or other data-processing practices. The latest version is the version currently published on this page.

If a future feature materially expands personal-data processing, the relevant explanation should be updated as well. Changes to this site policy do not alter the separate privacy rules or technical behavior of FlClash, Mihomo, GitHub or other third-party projects.