This policy applies to the cross-border network acceleration subscription service that VPNCW provides through vpncw.com (the Service). It covers the data processed at sign-up, at checkout and during day-to-day use, the retention periods and deletion routes for that data, and what cookies and local storage are actually used for.
- Sign-up needs only a username and password, with no email address.
- No record is kept of which websites are visited, and no connection logs are stored.
- Payments are handled through Alipay, WeChat Pay and USDT.
- Accounts can be deleted in self-service, and order records are kept until the refund window closes.
What Data Is Collected
VPNCW processes only the data required to maintain accounts, activate routes and handle after-sales requests, grouped into four categories by purpose.
- Account data: username and password. The sign-up form has no email field, so a username and password are enough to create an account; passwords are stored as salted hashes and plaintext passwords are never kept. Sign-up time and the most recent login time are used to spot unusual logins.
- Order data: plan tier, amount, payment channel, order number and order status, used for activation, renewal, reconciliation and refund handling.
- Analytics data: page views, referral source, browser and device type, and approximate region, reviewed as aggregate reports to judge whether content is useful and whether pages are malfunctioning.
- Support data: text, screenshots and client logs submitted through tickets in the user panel; whether to submit anything, and what to submit, is up to the user.
ID numbers, contact lists, precise location and browsing history fall outside the scope of processing. The account system holds no email address, so there is no email identifier that could be used for cross-site linking.
No-Logs Stance and Connection Records
VPNCW does not record which websites users visit. No connection logs are kept on the route side: session start and end times, source and destination addresses, and the contents of DNS queries are not recorded. Billing is based on plan capacity and total traffic, independent of what is accessed.
Only two kinds of records are kept for operations: account and order records, and aggregate visit statistics. Neither contains access destinations.
Client logs needed for troubleshooting are submitted by the user voluntarily, used only inside the relevant ticket, and archived with that ticket once the issue is resolved.
Key point: account and order data support activation and after-sales service, aggregate statistics improve content and help diagnose faults, and access destinations never enter any record.
Cookies and Local Storage
The site uses no third-party advertising or cross-site tracking cookies. Browser-side storage serves only three purposes.
- Login session: the login credential is kept in the browser's local storage to keep the session alive between pages; it expires when the user signs out or clears site data.
- Language preference: records the language version currently selected, so the next visit opens directly in that language.
- Interface state: options such as the billing-cycle switch on the plans page keep the last selection after a refresh.
Visit statistics come from a self-hosted component that uses a short-lived cookie to tell unique visitors apart; the data stays on this site's server. All of it can be cleared at any time in browser settings, after which language preference and session state return to their defaults.
Payments and Third-Party Processing
Payments are completed through three channels: Alipay, WeChat Pay and USDT. This site neither touches nor stores card numbers, payment passwords or wallet private keys; the channel returns the order number, amount and payment result, which are used for activation and reconciliation.
USDT moves on-chain, and transactions are publicly visible. Check the receiving address and the order amount before paying; the link between address and order is kept as the basis for reconciliation.
Order records are also the basis for refunds: a 60-day no-questions-asked refund requires checking the original order against the channel receipt, so these records are kept until the refund window closes.
Data Retention and Deletion
Retention periods differ by purpose.
- Account data: kept while the account exists; once the account is deleted, the username, password hash and login records are erased with it.
- Order data: kept until the 60-day no-questions-asked refund window closes and reconciliation is complete; after that only aggregate amounts remain.
- Analytics data: kept in aggregate form and not tied to any individual user.
- Ticket data: archived after resolution for reference on similar issues later.
There are two ways to delete an account: sign in to the user panel and delete it in settings, or submit a deletion request through a ticket, which is processed once account ownership is verified. Deletion cannot be undone; transaction records that payment channels keep under their own rules are outside this site's control.
Policy Updates and Contact
When the policy changes, the Last updated date at the top of this page changes with it. If a change widens how data is used, it is announced first in the site notice bar and the user panel, and the new version takes effect afterwards.
Requests to access, correct or delete data can be submitted through the ticket system in the user panel: sign in, open the tickets page, describe the request, and follow progress on the same page.
This policy, together with the Terms of Service and the Refund Policy, forms the terms framework for the service, and wording on the same matter is kept consistent; where they differ, the Terms of Service prevail.