Data collection and how it is used
VPNLS only touches data to the extent needed to run the service, and keeps each category separate by purpose. What it actually handles falls into three groups.
- Account details. Registration needs only a username and password; no email address is required. Passwords are stored as irreversible hashes, and support staff cannot read them in plain text. If you volunteer contact details in a ticket, they are used only to reply to that ticket.
- Order and billing records. These cover plan tier, amount, payment method, activation date and data usage. They are used to activate the right tier, calculate remaining data (which resets monthly on the activation date), work out the pro-rated difference when an upgrade happens mid-cycle, and handle refunds and reconciliation.
- Visit statistics. Aggregated data such as page views, referral source, device type and browser version, used to judge which pages need maintenance and which content needs expanding. Statistics are reviewed in aggregate and are not used to reconstruct any single visitor's path through the site.
No-logs stance
VPNLS keeps no logs of which sites users visit. While traffic is forwarded, the service does not store destination domain names, destination IP addresses or DNS query contents, and does not store the start and end times or traffic details of individual connections. None of this data falls within the retention scope.
Data usage needed for billing is totalled per account — for example, how much has been used this month and how much remains. These totals are unrelated to browsing targets and are not tied to any specific site or single connection event.
One case deserves a separate note: when a connection problem is being investigated, any ticket description, screenshot or client log the user submits is stored in order to locate the fault. Such material is provided voluntarily and can be deleted on request at any time.
Cookies and local storage
The site uses a small number of cookies and browser local storage, limited to the following three purposes:
- Language preference. Remembers the language version you picked, so your next visit goes straight to the matching language directory without switching again.
- Sign-in state. Sign-in credentials are kept in browser local storage to maintain your session inside the user panel. After you sign out or clear browser data, that credential stops working and you will need to sign in again.
- Interface preferences. For example, whether a collapsible panel is expanded or how a list is sorted. These stay on your device and are never uploaded to the server.
Cookies are limited to the three purposes above and are not used for advertising. You can clear this data at any time in your browser settings; afterwards the language preference returns to its default and the sign-in state has to be re-established.
Third-party payment processing
Payments are completed through third-party channels: Alipay, WeChat and USDT. VPNLS neither touches nor stores payment credentials such as card numbers, payment passwords or security codes. Once a transaction completes, the provider returns a result containing the order number, amount and payment status; the site uses it to activate the matching plan and write the order record, and does not obtain full details of the paying account.
USDT transfers happen on-chain and are initiated by the user. The site records only the link between the received payment and the order; it does not record wallet private keys or seed phrases. Payment providers apply their own privacy policies to the data they handle, and it is worth reading them before placing an order.
Data retention and how to delete it
Account details are kept for as long as the account exists. After an account is closed, the sign-in credentials and interface preferences linked to it are deleted.
Order and billing records are transaction evidence and are kept for the period required by applicable tax and consumer-protection rules, then deleted or anonymised. Records tied to unsettled orders or refund disputes can only be deleted once those matters are resolved.
Deletion requests are submitted through the ticket entry in the user panel, stating what should be deleted — the account, ticket records or statistics. Once a request arrives, account ownership is verified, the request is completed within a reasonable period and the outcome is sent back. Verifying ownership is only meant to stop someone else acting on your behalf; it does not affect how the request itself is handled.
How this policy is updated
This policy is updated as the service changes. The latest version is always published on this page, with the month of the last update shown at the top.
Changes to what data is collected, why it is used or how long it is kept are flagged in a prominent place on the site, with time allowed to read them. Continuing to use the service after a change takes effect is taken as acceptance of the updated version; if you do not accept it, you can request deletion as described in the previous section and stop using the service.
If you have questions about this policy, or need to confirm whether a particular piece of data is stored, raise them through the ticket entry in the user panel.