Privacy Policy

1. Visit Data and What We Collect

This is a static content site. It has no account registration or email collection forms. You can read documentation and visit download pages without providing your name, phone number, or subscription URL. The site does not need to access client node lists, proxy configurations, connection logs, or other files on your device.

When your browser requests pages, fonts, scripts, or download endpoints, the servers hosting the site and download services receive technical information such as your IP address, request time, resource path, browser request headers, and response status. This information may be used to serve requests, troubleshoot loading errors, detect unusual traffic, and keep services reliable. Static pages can still generate network request logs.

Do not put subscription links, shared node links, or configuration parameters containing credentials in the query string of a page URL on this site. Browser history, server logs, or forwarded links may retain those URLs.

2. Website Analytics and How We Use Them

We use analytics to understand page views, referral sources, client download clicks, and platform selections. This helps us identify tutorials that need more detail and download options that may be difficult to use. Analytics may include pages visited, time on page, interaction events, device type, browser category, and referring page.

A download click in analytics means a download link was activated; it does not confirm that a file was downloaded, a client was installed, or a connection was established. These events are not used to access proxy traffic, browsing activity, or subscription accounts. Analytics may be incomplete if your browser blocks scripts or analytics requests. You can still read pages and configuration guides.

3. Cookies and Local Storage

This site has no sign-in feature, so it does not use cookies to keep site accounts signed in. Whether analytics use cookies, and how long any identifiers remain valid, depends on the deployed configuration and your browser permissions. A static site does not necessarily mean there are no cookies. If browser local storage is used to save interface preferences, it should not contain subscription credentials or node configurations.

The platform selected on a download page may be preserved in the URL fragment. This fragment restores the selected platform and is not an account identifier. Your browser may also cache pages and fonts to avoid repeat requests; caching is separate from cookies and local storage.

You can view and clear this site's cookies, local storage, and cache in your browser's site settings, or restrict them from being written. Clearing them may reset some preferences. Blocking all scripts may affect navigation, platform switching, and download information updates.

4. Download Sources and Third-Party Services

The download page uses a download endpoint provided by the deployment layer to retrieve client release information and offer file downloads. Files are supplied by the relevant release source or distribution service. Download requests may be relayed or redirected; a same-origin link does not mean the file is stored on the server hosting the page.

File providers may receive information needed to complete transfers, such as your IP address, request headers, and request time. Their respective services determine how this information is logged. Third-party links in our documentation are also subject to the destination services' policies. Users configure the subscriptions and nodes used by their clients; this site's policy does not describe the privacy practices of those services.

5. Policy Updates and Questions

If data handling, analytics purposes, or download routes change, we will update this page and revise the last-updated month at the top. Refer to the updated policy for any new purposes; this page does not grant blanket permission for any future data processing.

For download or configuration issues, start with the configuration guide and troubleshooting guide. If you need to submit screenshots or logs through a service's feedback channel, first redact subscription URLs, access tokens, node credentials, and personal network information. Include only what is needed to diagnose the issue.