About this site
Privacy Policy
Last updated: September 2026
This policy applies to the client download links, setup guides, and technical resources on clash-iphone.com. It explains what data may be generated when you visit the site, how that data is used, and where this policy no longer applies. For information about how a client app handles data, refer to that app’s own documentation.
1. What data we collect
This site serves content as static pages. You don’t need to create an account, submit an email address, or fill out forms with personal information. You can read guides, look up terminology, and visit download links without providing your name, phone number, or subscription link.
Requests to our pages may generate technical logs through our hosting and analytics services. These may include the time of the visit, requested URL, browser and device type, referring page, and network address. This information helps deliver pages, understand how content is used, and identify failed loads or unusual requests. We don’t ask visitors to identify themselves through these logs or use analytics to build individual user profiles.
2. Analytics and server logs
We use analytics to see which pages are read, which site links lead visitors to our guides, and whether pages display correctly on different devices. We use these results to improve navigation and documentation and troubleshoot page errors. Analytics don’t indicate a client’s connection status or access configuration files, proxy rules, or subscription content stored in a client app.
Logs generated by the hosting service to respond to page requests may be handled separately from page analytics. Their availability and retention depend on the hosting configuration in effect; this policy does not set a single retention period for all logs. Visiting this site necessarily generates network requests. To avoid generating records from future visits, stop accessing the site.
3. Cookies and local storage
You don’t need to accept cookies to read pages on this site. Browser cookies or local storage may be used by analytics to distinguish repeat visits or retain limited analytics state. What gets stored depends on your browser settings and the analytics configuration in use. Cookies and local storage aren’t used to store client configuration files or subscription links.
You can use your browser settings to view, restrict, or clear this site’s cookies and site data. Restricting this storage generally won’t affect access to static documents, but analytics may no longer be able to distinguish repeat visits from the same browser. You control your browser’s privacy settings; clearing site data won’t remove settings from an installed client app.
4. Downloads and third-party links
Our download pages may link to app stores, client project websites, or file download pages. After you follow a link, the destination may handle visit logs, account information, or download requests under its own policies. This policy does not replace the destination’s privacy notice. When opening an external site, check the address shown in your browser and review the destination’s terms.
When installing a client, read the installation instructions for your device platform and check the purpose of any permissions requested by the operating system. Our guides explain common steps but don’t replace information provided by app stores, operating systems, or client projects about their services. For installation and connection setup questions, start with Getting Started and the Help Center.
5. Policy updates
We may revise this policy if site features, analytics methods, or applicable data-handling processes change. Any revised policy will appear on this page, along with an updated “Last updated” month at the top. Check the version shown here for the latest information about our practices.
If a change could materially affect how visitors understand the scope of data handling, we’ll add relevant details to the appropriate pages. Policy updates don’t retroactively change actions you’ve already taken on third-party sites. For data handled by client apps or external services, consult the relevant provider’s documentation.