Legal

Privacy Policy

Last updated: 09/2026

This policy explains what information VPN-LG (referred to below as the Service) comes into contact with while providing its cross-border network acceleration subscription service, what that information is used for, how long it is kept, and how users can access and delete it. It applies together with the Terms of Service and the Refund Policy.

1. Scope and Basic Stance

This policy covers the vpnlg.com website, the user dashboard and the VPN-LG clients for every platform. The basic stance is a single rule: collect only the information required to activate subscriptions, handle billing and keep routes stable. Nothing unrelated to those purposes is collected, and user information is never used for advertising.

Registering for the Service requires only a username and password, with no email address, so the Service does not hold a user's email by default. If a user voluntarily enters an email address or other contact details in a support ticket, that information is used only to reply to that ticket.

2. What Data Is Collected and Why

  • Account information: username and password. Passwords are stored in encrypted form; plaintext is never saved.
  • Subscription and order records: plan type, activation and expiry dates, data pack balance, order number and payment status. Used to activate subscriptions, process renewals, reconcile accounts and handle after-sales requests.
  • Device and connection metadata: client platform (Windows / macOS / iOS / Android / Linux), connection start time and the route ID used. Used for route scheduling, concurrent connection management and troubleshooting.
  • Visit statistics: aggregated traffic data for the site and user dashboard, such as page views and referral type. Used to judge whether content is useful, and never used to identify individuals.

3. The No-Logs Stance and Connection Records

The Service follows a no-logs policy: it does not record which websites a user visits, does not log DNS query contents and does not store transmitted content. None of these three categories falls within the Service's logging scope.

To maintain route quality, the system generates minimal connection metadata, including the connection start time, the route ID used and the data volume. This metadata is used only for route scheduling and troubleshooting, is kept for the shortest period needed to fulfil that purpose, and is deleted once troubleshooting ends. It is never used for advertising, nor provided to third parties for marketing.

The no-logs scope covers every route type, including IEPL dedicated lines, relay and direct connections.

4. Cookies and Local Storage

Cookies record language preference, keep login sessions alive and count aggregated page views. Local storage (localStorage) holds login credentials and interface preferences, such as the last selected language and platform. Login credentials are stored only in the user's own browser, so there is no need to sign in again on every visit.

Users can clear cookies and local storage at any time in their browser settings. After clearing, a new sign-in is required; purchased plans and order records are unaffected, and subscription status is determined by the records held in the account.

5. Payments and Third-Party Processing

Payments for subscriptions and data packs are handled by third-party payment channels; Alipay, WeChat and USDT are currently supported. The Service neither accesses nor stores full payment account credentials. After a payment completes, the Service receives only three results — order number, amount and payment status — and uses them to activate the corresponding plan.

Third-party payment channels handle payment information under their own privacy policies, so it is worth reading the relevant channel's terms before paying. Subscriptions support a 14-day no-questions-asked refund; see the Refund Policy for eligibility and processing times.

6. Data Retention, Deletion and Policy Updates

Retention periods: account information is kept while the account remains active; order and transaction records are kept for as long as needed for reconciliation and dispute handling; connection metadata is kept for the shortest necessary period; aggregated visit statistics contain no personally identifiable information and may be retained long-term for capacity planning.

Deletion: to close an account or delete data, submit a request through the ticket entry in the user dashboard, stating the account and the scope to be handled. Once an account is closed, account information and device metadata are deleted or anonymised, except for transaction records that must be retained by law.

Policy updates: when this policy changes, the “Last updated” date at the top of the page is revised at the same time. If a change affects the scope of collection or the purposes of use, it takes effect only after being announced on the site. Questions about an update can likewise be raised through the ticket entry in the user dashboard.