Privacy Policy

Last updated: March 2026

This policy applies to pages and download links provided by Clash Review on clash05.com. It explains what data may be involved when you visit the site and how it is used. Data handled by clients, subscription services, and external websites is outside our control, even when this site describes or links to them.

1. Data We Collect

This is a static content site. It does not offer account registration or ask visitors for an email address. You can read reviews, browse guides, and choose a download platform without providing your name, phone number, or payment details. The site does not ask you to upload proxy configurations, subscription URLs, connection logs, or node credentials.

When your browser requests a page, resource, or download, the server and network infrastructure handling the request may process technical information such as your IP address, request time, URL path, response status, and browser identifier. This information helps deliver content, diagnose errors, and protect the service. While it differs from information you submit directly, it may still identify you, so its use should be limited to legitimate operational needs.

2. Website Analytics and How We Use Them

We use Matomo analytics to understand page views, referral sources, device types, and changes to client-platform selections. This helps us identify guides that need more detail, improve download links, and investigate unusual traffic. Analytics data is not the same as proxy connection logs stored by a client.

Analytics requests may include the page URL, referrer, and browser or device details. The exact fields depend on the analytics configuration and browser settings. Do not include subscription links, passwords, or other sensitive information in URL query parameters on this site, as they may be recorded in request logs or analytics data. We do not use analytics data to assess anyone’s creditworthiness or abilities.

3. Cookies and Local Storage

Page content and basic navigation do not require login cookies. Whether analytics uses cookies, how long they last, and how identifiers are assigned depend on the active analytics configuration. A static site does not guarantee that your browser stores no data. Scripts may also retain interaction state during a session, while URL fragments can point to a section or selected platform.

You can view, clear, or restrict cookies and local storage in your browser’s site settings, or use content-blocking tools to limit analytics requests. Restricting storage may prevent some preferences from being saved. Clearing browser data does not delete logs or analytics records already held on servers. Cached page resources and analytics identifiers are different things.

4. Third-Party Links and Downloads

This site links to client developers’ websites, app stores, and download pages. Once you open a third-party site, its operator may handle browsing and download data under its own policies. Requests for files routed through this site may also be processed by the service hosting those files. A link does not mean we control how an external service handles data.

Before downloading, check the destination domain, app publisher, system architecture, and file source. Review any signature and permission warnings shown by your operating system. After installation, a client may request network, system proxy, or virtual network adapter permissions; consult the relevant project documentation to understand why. Subscription providers’ handling of account, node, and connection data is governed by their own policies and is separate from this site’s analytics.

5. Policy Updates and Questions

If our analytics methods, storage practices, or download arrangements change, we will update this page and revise the month shown at the top. Because this site does not collect registration email addresses, policy changes will be announced here rather than by individual email. Check this page again when you visit to review the terms relevant to current features.

For help deciding whether an action is necessary, see Frequently Asked Questions and Configuration Guides. When troubleshooting, check your local settings first. Before sharing screenshots or logs with an external project, remove subscription URLs, access credentials, and any other information that could identify you.