This policy explains what data VPNWing collects while providing its cross-border network acceleration subscription service, why it is collected, how long it is kept, and how users can review and delete it. The service covers 120+ countries / 160+ routes, with apps for Windows / macOS / iOS / Android / Linux. The policy applies to the vpnwing.com site, the user panel and the apps listed above.
Account Data and Sign-up Information
Signing up for this service requires no email address — a username plus a password is enough. The only things stored at the account level are: the username, the password hash (plain-text passwords are never stored), plan tier and remaining data allowance, the subscription credential, and the current number of active connections. There is no cap on simultaneous devices; the connection count is used only to show current status in the user panel, is not used for device fingerprinting, and is not linked to browsing behaviour.
Optional information is stored only when the user chooses to provide it. Ticket text, screenshots and client logs submitted in the user panel are handled according to the periods in the "Data Retention Periods and Deletion" section below.
Orders and Payment Records
Order records contain the plan tier, amount, order time and payment status. Payment methods are Alipay / WeChat / USDT. The payment itself happens on the respective channel; this service neither touches nor stores payment credentials such as card numbers, payment passwords or wallet private keys. The channel returns only a transaction ID and the payment result, used for reconciliation and refund handling.
A full refund can be requested within 30 days of the first payment, no reason required. That commitment needs order records as the basis for verification, so order data is kept longer than account data; the exact periods are in the table below.
No-logs Stance
This service does not record which websites users visit over international routes, does not store DNS query records, and does not store connection start and end times or communication content. On the route side, only the aggregate metrics needed to keep things running are kept, such as the current connection count on a given route; these metrics carry no account identity and cannot be traced back to an individual user. Traffic is protected with military-grade encryption, and this service cannot read users' communications.
Scope note: The no-logs stance covers automatically collected connection and access records. Ticket content, screenshots and client logs that users submit voluntarily are not part of it — that data is provided by the user, is used only to diagnose the reported problem, and is deleted according to the periods below.
Cookies and Browser Local Storage
The site uses a small number of cookies and browser local storage for three purposes:
- Language preference: remembers the interface language the user picked, so it does not have to be chosen again on every visit.
- Sign-in state: keeps the session credential in the user panel and clears it on sign-out.
- Visit statistics: counts page views to judge which documentation needs expanding. The figures are aggregate, are not used for advertising, and involve no cross-site tracking.
Clearing this data in browser settings does not affect a purchased plan; it only ends the sign-in state, so one more sign-in is needed.
Data Retention Periods and Deletion
Each type of data is kept for the period below; once that period ends it is deleted or anonymised:
| Data type | Retention period | Notes |
|---|---|---|
| Account data | While the account exists | Deleted within 7 business days of a closure request |
| Order and payment records | 24 months after the order is completed | Needed for refund handling and reconciliation |
| Ticket records | 12 months after closure | Makes it easier to compare if the same issue recurs |
| Visit statistics | 14 months | Aggregate only, no account identity |
Deletion requests are submitted through the ticket entry in the user panel, stating which data should be deleted. Orders that are in the refund process are deleted after the refund is completed. Once an account is closed, the old username is not released for other users to register.
Policy Updates and Scope
When the policy is updated, the "Last updated" date at the top of this page changes with it. Material changes to what is collected or how it is used are announced in the notices area of the user panel. Continuing to use this service after an update takes effect counts as accepting the updated terms; users who do not agree with the changes can follow the refund terms in the terms of service and stop using the service.
This policy does not cover the privacy practices of third-party payment channels themselves. The Alipay, WeChat and USDT payment pages are operated by the respective channels, and their data handling follows those channels' privacy terms.