This policy applies to the cross-border access subscription service provided by VPNWu, and covers the information pages on this site, the pricing pages, and the user panel you use after signing in. Subscribing, importing a subscription URL and opening a support ticket are all handled as described below. If you disagree with any part of it, you can stop using the service and request a refund under the refund policy.
What data we collect and why
The data this service handles falls into three categories, all directly tied to delivering your subscription and keeping the books straight. None of it involves what you access.
Account information. Signing up requires only a username and a password — no email address needed. Passwords are stored as irreversible hashes; the service cannot read them in plain text and cannot restore one to tell anyone. The username identifies your account in the panel and locates your order in support tickets.
Order and usage records. This covers the plan or data pack purchased, the amount, activation and expiry dates, data used, and refund status. It is used for billing, for resetting data on the activation date each month, for prorating the difference when you upgrade mid-cycle, and for checking claims under the 60-day money-back guarantee. Usage is counted as a total only and never touches what you access.
Visit analytics. We record the page path, referrer, device type and approximate region of a visit, to see which content is useful and which pages break. Analytics are used in aggregate; they are not used for advertising and involve no cross-site tracking.
Our no-logs stance
This service does not record which websites users visit. Specifically: we do not store the destination domains or URLs you access, do not store the contents of DNS queries, do not store the start and end times of individual connections or which route they used, and do not inspect or retain traffic contents. A subscription URL maps one-to-one to an account, but the system only counts total traffic — it does not record where that traffic went.
To keep routes available, operations keeps only aggregate metrics that carry no account identifier: the reachability, load level and incident history of each route. These metrics cannot be traced back to an individual account.
As a result, when asked which websites a given account visited, this service has no records to provide. Data requests are answered only where legal process is complete, and only for the account and order information listed under “Data retention and deletion” below.
The short version
Account and order data exist to deliver subscriptions and reconcile payments; which websites you visit and which route you connect through are not logged or stored.
Cookies and local storage
This site uses no third-party advertising cookies and loads no cross-site tracking scripts. First-party cookies and browser local storage serve three purposes only: remembering your language preference; holding your sign-in token so you do not have to log in again after closing the page; and remembering temporary interface choices, such as the billing cycle you last viewed.
The sign-in token stays in your own browser. It stops working when you sign out or clear your browser data, and you will need to sign in again. To clear it, delete this site's cookies and site data in your browser settings. That affects only the sign-in state and preferences on this device, not your account or subscription.
Payments and third parties
Payments are handled by third-party channels; the methods supported here are Alipay, WeChat and USDT. Card numbers, payment passwords, wallet private keys and other payment credentials are processed by the channel — this service neither touches nor stores them. The transaction ID and payment result returned by the channel are recorded on the matching order for reconciliation, receipts and refund checks.
Third-party channels handle payment information under their own privacy policies. Apart from payment channels and the infrastructure needed to run the service (servers, the ticket system), this service does not sell user data and does not use account or order data for advertising.
Data retention and deletion
Retention periods differ by data category:
- Account information and order records: kept while the account is active; deleted or anonymised within 30 days of a closure request.
- Transaction receipts: kept as required for payment and accounting compliance, deleted once that period ends, and used only for reconciliation in the meantime.
- Visit analytics: kept in aggregate form, with no account identifier.
- Support tickets: kept for a traceable period after closure, then deleted.
How to delete: sign in to the user panel and submit a data deletion or account closure request through the ticket entry point, stating your username and the scope you want handled. Once the request is confirmed, it is carried out within the periods above, and the outcome is answered in the same ticket. After deletion, the subscription URLs tied to that account stop working, and any remaining allowance on purchased plans or data packs is not restored.
Policy updates and contact
When this policy changes, a new version is published on this page and the “Last updated” date at the top is changed accordingly. If a change affects the scope of data use or the retention periods, notice is given in the user panel in advance; continuing to use the service means you accept the updated version.
Privacy-related requests all go through the ticket entry point in the user panel — data access, deletion, account closure and policy questions alike. For billing questions, see also the Terms of Use and the Refund Policy.
Related terms
Billing and subscription rules are in the Terms of Use; refund eligibility is in the Refund Policy; data and account requests go through the ticket entry point in the user panel.