Privacy Policy

1. Data We Collect

This is a static content site. We don’t offer account registration or email signup forms. You can read our guides without submitting your name, phone number, subscription URL, or client configuration. Don’t add subscription tokens, node passwords, or other credentials to site URLs or send them as query parameters.

When you access pages, fonts, images, or download links, the infrastructure hosting the site and forwarding downloads receives information needed to fulfill your request. This may include your IP address, request time, page path, response status, browser type, and referring page. These technical logs support content delivery, troubleshooting, and handling unusual requests; they are not information you have actively submitted as personal details.

Our webpages don’t access client configurations, subscription contents, or proxy traffic on your device. Data handling by client apps and subscription services is outside the scope of this site’s features; please consult their respective privacy information.

2. Analytics and How We Use Data

We use analytics to understand page views, traffic sources, device categories, and actions such as switching platform options or clicking download links. This helps us assess whether guides are easy to find, identify navigation issues, and improve the reading experience across screen sizes. A click on a download link only records a click; it doesn’t confirm that a file was downloaded or software installed.

We primarily use aggregated trends in page views and actions. Analytics aren’t used to check client app status or infer which nodes visitors use. Technical logs and analytics data are limited to the purposes described above and retained only as long as needed to fulfill them. Retention periods may vary based on the hosting service, so we can’t promise a single unverified timeframe.

3. Cookies and Browser Storage

Analytics tools may use cookies or browser storage to recognize sessions and avoid duplicate counts. Whether data is stored, and for how long, depends on the analytics configuration in use and your browser settings. We don’t use cookies to store subscription URLs, node passwords, or client configurations.

Platform selections can be restored using URL fragments; this doesn’t mean every interface preference is saved in browser storage. Browser caching of static files and cookies are separate mechanisms, so clearing one won’t necessarily clear the other.

You can block cookies, restrict scripts, or clear this site’s data in your browser settings. Restricting scripts may affect the navigation menu, tabs, and dynamic download link resolution. After clearing site data, analytics may treat your next visit as a new session.

4. Download Sources and Third-Party Links

Our download pages provide client links by platform and use same-origin forwarding paths to retrieve remote version lists and files. Client installers aren’t stored in the site’s static asset directory. A same-origin address doesn’t mean the software was developed by this site or change its license or terms of use.

Download requests may pass through hosting or file distribution services, which receive network information needed to transfer files. When you visit a third-party site, that provider may process referral information, cookies, and access logs under its own policies. This policy doesn’t replace theirs. Subscription services or remote servers that client apps connect to are also responsible for explaining their own data practices.

5. Policy Updates and Questions

If our data uses, analytics, or download process changes materially, we’ll update the relevant sections on this page and revise the month shown at the top. Since we don’t collect email addresses, this page is the notice for policy changes; we won’t send individual email notifications. Any new data use will be explained where the relevant feature is provided.

For help with downloads or setup, see the FAQ or setup guide. When checking a privacy-related issue, note the page path, steps taken, and browser restrictions. Don’t include subscription tokens, passwords, or other sensitive information in text or screenshots that may be shared publicly.