Last updated: October 2026
Privacy Policy
This is the official Shadowrocket website and manual. This policy explains how information is handled when you visit this site, including its documentation, navigation, and App Store links. It does not replace the privacy information for the Shadowrocket app or Apple services.
1. Scope and visit data
This site provides content through static pages. It has no user accounts, does not ask for your email address, and has no forms for collecting subscription URLs, server passwords, or payment details. You do not need to submit existing subscription or server information to read the guides. Such information should be handled only through app workflows you have chosen to use.
When your browser requests a page, the service hosting the site may generate access logs containing the request time, page path, response status, IP address, and browser request information. This data is used to deliver pages, maintain the site, and investigate unusual requests. It is distinct from information you choose to submit.
This site does not use web pages to read the app’s Config, SERVER list, or connection history. Instructions shown here do not mean the site can access app data on your device.
2. Analytics: scope and purpose
We use analytics to understand how visitors use the documentation and navigation. Analytics may include pages viewed, referring pages, device and browser categories, and on-site interaction events. This information helps us find broken links, improve content organization, and check usability on mobile devices.
When you choose to click the App Store button on the app authenticity page, we record an event for that store-link click. It records a click, not a completed purchase, and does not include your Apple Account, order amount, or payment credentials. We cannot use it to confirm an individual purchase.
Analytics are intended to measure site usage. Do not include passwords or full subscription URLs in page addresses or feedback; URL parameters may be included in request logs or analytics records.
3. Cookies and local storage
Depending on page caching, analytics, and the site’s actual deployment configuration, your browser may store cookies or other site data. Cookies, local storage, and cache are different mechanisms. You can check the specific data stored in your browser’s site data or privacy settings.
You can restrict cookies, clear this site’s data, or use content-blocking settings to control analytics requests. After clearing the cache, fonts and page resources may need to reload. Restricting analytics may make visit records incomplete, but you do not need to submit personal information to read public documentation.
Clearing this site’s browser data does not delete configurations in the Shadowrocket app, nor does it clear account or transaction information stored by Apple. Manage those separately through the relevant services.
4. App Store links and service boundaries
The only way to get Shadowrocket is through its App Store product page. Apple operates that page. Once there, account sign-in, purchases, payments, and transaction records are governed by Apple’s terms and privacy rules. This site does not collect payments or receive payment details.
A one-time purchase of the app is not a service plan. This site does not provide, sell, or recommend proxy servers or subscriptions; it only explains how to use information you already have. App compatibility and system requirements are as listed on the App Store page.
5. Policy updates and questions
This page will be revised if the scope of data handling, analytics purposes, or site features change, and the updated month will appear at the top. Any new data handling should be understood according to the specific updated explanation. This site’s policy does not extend to the app or Apple services.
Check this page periodically and manage site data in your browser. For app instructions, see the user guide. For purchases and restoring previous purchases, see the App Store guide. When troubleshooting, redact account identifiers, subscription URLs, and server credentials; do not include them in publicly accessible content.