Privacy Policy

Last updated: March 2026

Shadowrocket Home is the official website and manual for Shadowrocket. This policy explains how information is handled when you visit this website. It does not replace the privacy information for the Shadowrocket app or Apple’s terms. This website does not provide nodes or subscriptions.

1. Scope and Sources of Information

This is a static website with no registration, sign-in or email collection forms. You can read the guides without submitting your name, phone number, payment details or Apple Account information. The website does not access in-app configurations, connection logs, or your existing subscription or server information.

When your browser requests a page, the infrastructure hosting the website must receive technical information such as your IP address, request path, access time, browser type and response status. This information is used to deliver pages, diagnose access errors and maintain security. It is not the same as a personal profile you submit yourself.

2. Website Analytics and How We Use Them

We use website analytics to understand page readership, on-site navigation and common access errors. Analytics may include page URLs, referring pages, device and browser categories, and events when users click an App Store button. Click events help us assess whether the app information is useful; they do not include purchase outcomes or payment details.

Analytics rely primarily on aggregated page and event data to improve content organization and troubleshoot issues. They are not used to make purchases or change settings on your behalf. How operational logs are handled depends on the actual deployment configuration, so we do not promise a fixed retention period. Access should be restricted during maintenance, and information unrelated to these purposes should not be retained.

3. Cookies and Local Storage

This website does not require login cookies to maintain your reading session. Whether analytics set cookies, which identifiers they retain and for how long depends on the analytics service configuration. A static website does not necessarily mean that your browser stores no data. Language switching uses page links, and feature panels may use URL fragments to preserve your location.

Your browser may also cache fonts, images and scripts to avoid repeat requests. Cache, cookies and local storage are separate mechanisms; you can review or clear them individually in your browser’s site data settings. Restricting storage or scripts may affect analytics and interactive features, but you can still read the main content using page links.

4. App Store Links and Purchase Information

Shadowrocket is available only on Apple platforms, and the App Store is the sole place to get it: App Store product page. The page is operated by Apple. Once you open it, account verification, purchases, payments and related data handling are governed by Apple’s terms and privacy information. Check the App Store page for system requirements and purchase availability.

The website does not receive payment information from the App Store and cannot confirm a purchase from a link click. A one-time purchase of the app is not a service plan. The guides assume you already have your own subscription or server information. Do not post actual subscription URLs, passwords or payment credentials on public pages or in screenshots.

5. Privacy Controls and Policy Updates

You can clear this website’s data in your browser settings, restrict cookies, stop analytics scripts from loading or leave the site at any time. Clearing browser data does not automatically delete operational logs already created by the website infrastructure; these are handled separately.

Revisions to this policy will be published at this address, and the last-updated month at the top of the page will be changed accordingly. Any material change to the purposes or scope of data handling will be clearly explained in the revised policy. For help with usage questions or troubleshooting, see Troubleshooting and User Guide. When describing an issue, include only the details needed to explain the error and avoid exposing account or configuration credentials.