Privacy Policy - VPNWI | No-Log Policy & Data Retention

VPNWI provides a cross-border network acceleration subscription service. This page explains what data is processed when you sign up, buy, and use the service, why it is processed, how long it is kept, and how to request deletion.

Key points: no record of which websites users visit; signup needs no email address — a username and password are enough; account and order data is kept only as long as needed to provide the service and reconcile accounts.

What this policy covers

This policy applies to the marketing pages on vpnwi.com and to the user dashboard on this site (account login, plan purchase, subscription retrieval, ticket submission). Once you follow a link from this site to a third-party website, that website is responsible for its own data handling; please review their privacy notice.

Data we collect and how it is used

Only the data needed to deliver the subscription service is collected — four categories in total.

Account data: username and password. Signup does not require an email address — a username and password are enough; passwords are stored in an irreversible form, and no plaintext is kept at any stage.
Order data: plan name, amount, payment method, order time, and order status, used to activate routes, calculate the monthly traffic reset from the activation date, and process refund requests.
Session data: login sessions, client type (Windows / macOS / iOS / Android / Linux), and last login time, used to spot unusual logins and troubleshoot connection issues.
Visit statistics: aggregated records such as page views, referral source, browser, and device type, used to judge which content is useful to visitors; not used for advertising.

Beyond these four categories, no information unrelated to the subscription service is collected, and there is no requirement to provide your real name, address, or similar details.

Access logs and retention policy

Keeping no logs is a fixed policy of this service. Here is what that means in practice.

No record of what you access: no record of which websites users visit, no DNS query contents, and no connection session details. Routes only forward traffic; traffic contents are not parsed or retained.
No account linkage: there are no records on the route side that tie a given connection to an account, so it is impossible to later compile a list of what a particular account visited.
Operational metrics that are kept: to troubleshoot route issues and detect abuse, route-level availability status and aggregate traffic counters are kept. These metrics are per route and contain no individual account's browsing history.
Boundaries: the no-log policy covers traffic and access records; accounts, orders, and tickets are business data and are kept for the periods described below. The two kinds of data are stored separately and never mixed.

Cookies and local storage

Browser local storage on this site is used for three necessary purposes only.

Login state: the user dashboard's session credentials are stored locally in the browser so you do not have to log in again each time; they expire when you log out or clear your browser data.
Language preference: remembers the interface language you last chose, so your next visit opens directly in that language.
Interface state: temporary state such as the currently selected plan period tab.

Page visit statistics use aggregated records and do not write identifiers that could be used for cross-site tracking. All of the above can be cleared at any time in your browser settings; after clearing, you will need to log in again, and the language and interface state return to their defaults.

Payment processing and third parties

Payments are handled by third-party payment channels; this site supports Alipay / WeChat / USDT.

Payment credentials: card numbers, account balances, and other payment information are handled by the payment channel; this site neither touches nor stores them.
Order results: what this site receives from the payment channel is the order number, amount, payment method, and payment status, used only to activate plans and reconcile accounts.
Refund records: for requests submitted within the 14-day no-questions-asked refund period, the handling record (request time, amount, status) is kept as a financial voucher.
Infrastructure: providers such as server hosting and domain resolution services access data only to the extent necessary to provide infrastructure, limited by the service contract.

Beyond the parties above, this site does not sell or share account data with third parties.

Data retention, deletion, and policy updates

Retention periods:

Account data is kept while the account is active; after a closure request is submitted, it is deleted or anonymized once the processes needed to reconcile orders and handle refunds are complete.
Order and payment records are financial vouchers and are kept for the period needed for account reconciliation and refund handling, then deleted.
Ticket records are kept for a period after the ticket is closed so they can be referenced later, then deleted once that period ends.

How to request deletion: submit a deletion request through the ticket entry in the user dashboard, stating your username and the scope of data to be deleted; it is processed after identity verification, and progress is answered in the same ticket. Deleting an account does not affect order reconciliation and refund handling that have already been completed.

Policy updates: if this policy changes, the "Last updated" date on this page will be revised, and a notice will appear in the user dashboard announcements. Updates only concern how data is handled. If you do not agree with the updated content, you may stop using this service; refunds are handled under the Terms of Service.