Last updated: 2026-09
What Data Is Collected and Why
This service collects only the data needed to run subscriptions, billing and support. It falls into four categories:
- Account data: username and password. Registration does not require an email address — a username and password are enough. Passwords are stored as irreversible hashes, and the service cannot recover the plaintext password.
- Order data: the plan or data package purchased, the amount, the payment channel, the order and activation times, and the order status. Used to activate subscriptions, meter traffic, reconcile accounts and process refunds.
- Visit statistics: page paths visited, referrer, device and browser type, and the approximate region inferred from the IP range. Used to see which documentation is useful and to troubleshoot page errors; the statistics are used in aggregate and are not linked to individual accounts.
- Ticket records: the issue description you submit and the replies exchanged, used to follow up on support requests and troubleshoot problems.
Signing up and everyday use require only a username and password. If you voluntarily add other contact details in a ticket, that information is used only to answer that request.
No-Logs Stance and Connection Log Policy
A connection log is a record that links an account to a destination address at a particular time. This service's default policy is not to create or retain such records.
Billing and traffic metering need aggregate usage: the data used per account (in GB) and the subscription expiry date. These figures show only how much was used, never what was accessed.
Operations monitoring covers link-level metrics such as route availability and bandwidth headroom, used to detect and resolve faults; these metrics are never tied to what a specific account accessed.
Account data, order data and usage data are never sold, rented or used for advertising. The only usual reason to look up account information is to verify an order or a refund.
How Cookies and Local Storage Are Used
Cookies and browser local storage serve only three functions, and this site uses no third-party advertising or cross-site tracking cookies:
- Language and interface preferences: remembering your chosen language, the plan period you last viewed and similar settings, so they stay the same next time you visit.
- Sign-in state: your dashboard sign-in credential is kept in browser local storage so you do not have to log in again; it stops working after you sign out or clear your browser data.
- Basic visit statistics: used to count page views, with the data used in aggregate form.
You can clear this data at any time in your browser settings. Doing so resets your language preference and sign-in state, but does not affect subscriptions you have already purchased or your use of the routes.
Payments and Third-Party Processing
Alipay, WeChat Pay and USDT are all handled by their respective third-party payment services. Account information and payment credentials generated during payment are handled by the payment channel under its own privacy rules; this service neither sees nor stores complete payment credentials.
After payment completes, the only information this service receives is the order number, the amount, the payment status and the payment time, used to activate the subscription and reconcile accounts.
USDT transfers happen on-chain and the transaction records are publicly visible; check the address and amount before sending.
Refunds are handled under the Refund Policy, which offers a 30-day no-questions-asked refund.
Data Retention and Deletion Options
Account data is retained for as long as the account exists. Once a deletion request is submitted and verified, the account information and subscription records are deleted or anonymized.
Order and payment records are kept for as long as needed for accounting reconciliation and refund handling, and are deleted or anonymized afterwards.
Deletion requests are submitted through the ticket form in the user dashboard; just name the account you want deleted. A deleted account cannot be restored, and unused data packages and any remaining subscription time become unavailable. Deleting an account does not automatically trigger a refund; refunds must be requested separately under the Refund Policy.
Policy Updates and Contact
The last-updated date shown on this page is refreshed with every revision. If the scope of data processing changes materially, it will be explained in a site announcement; the scope of data collection will not be expanded without users knowing.
If you have questions about this policy, or need to access, correct or delete your data, submit a request through the ticket form in the user dashboard — tickets are the main channel for these requests.
This policy covers only how this service handles data; payment channels and third-party websites you visit are governed by their own privacy policies.