Legal · Privacy Terms

Privacy Policy

Last updated: 2026-10 Applies to: vpnpx.com and the VPNPX client

This policy sets out item by item what data VPNPX processes while providing its cross-border network acceleration subscription service, why it is processed, how long it is kept, and how users can look it up or delete it. The descriptions here match actual practice, so you can check them at any time.

1. Scope of This Policy

This policy covers every page under vpnpx.com, the service's client apps, and the account and order actions in the user panel. Once payment moves to a third-party channel's page, that channel handles the data under its own policy and this policy no longer applies. The companion Terms of Use covers subscriptions, refunds and usage rules separately.

Signup requires no email address: a username and password are enough to get started. The service therefore holds no email address, real name or mailing address for users, and will not ask for them later as additional details.

2. What Data We Collect

Collection is limited to what is needed to set up and maintain a subscription, in four categories:

  • Account data: username and password. Passwords are stored as one-way hashes; no plaintext is kept and the original characters cannot be recovered.
  • Order and billing data: plan tier or data pack size, order number, amount, payment method, activation date and expiry date. Used to activate routes, reset traffic monthly on the activation date, and check refund requests.
  • Troubleshooting data: client version, operating system type, and the error codes returned when a connection fails. Read only when a user submits a ticket, to diagnose connection problems.
  • Visit statistics: page views, referral source, device and browser type, counted in aggregate to judge which documentation needs improving.

The service does not collect browsing content, contacts, photo libraries or precise location, and does not read data from other apps on your device.

3. Our No-Logs Stance

The service does not record which websites users visit, does not log DNS queries, and does not keep connection logs containing source addresses, destination addresses and timestamps. Traffic inside the encrypted tunnel is not visible to the servers, so no content is retained.

Route nodes only track aggregate metrics, such as total bandwidth usage and session counts per route, for capacity scheduling and failover. These metrics are not tied to individual accounts and cannot be used to work out what any user accessed.

The limits deserve the same clarity: no-logs means no records that could reconstruct browsing behaviour are kept; account and order data are necessary to provide the service and are not exempt. Ticket content a user submits is kept until the issue is closed.

Storage in the browser serves three purposes only:

  • Login state: the login credential is kept in the browser's local storage so you do not have to sign in again each time; it is cleared when you sign out.
  • Preferences: your language choice and recently viewed pages are stored locally, so you do not have to pick them again every visit.
  • Session and statistics: essential session cookies and basic visit statistics, used to keep pages loading properly and to judge how well content performs.

The service uses no third-party advertising cookies and does no cross-site behavioural tracking. You can clear cookies and local storage in your browser settings; afterwards you will need to sign in again, but your plan, remaining traffic and expiry date are unaffected.

5. Payments and Third-Party Processing

The site supports Alipay, WeChat and USDT. Payment is completed on the relevant channel's page or app; the service never touches or stores payment account passwords, card numbers or verification codes.

After payment, the channel returns the order number and payment result to the service, which is used to activate the subscription automatically and confirm receipt. USDT is an on-chain transfer, checked using only the transaction hash and amount, with no link to other identity information.

Data collected by the channels themselves is governed by their own privacy policies. If a channel's page asks for extra information, that channel's notice applies.

6. Retention, Deletion and Policy Updates

Retention: account data is kept until the account is closed. After closure the login credential stops working immediately and is removed during the deletion process. Order and payment records are needed for refunds and reconciliation, so the necessary transaction fields — order number, amount, date and payment method — are retained after closure, with no access records of any kind.

Deletion and correction: to look up, correct or delete data, submit a request through the ticket entry in the user panel. Once account ownership is verified, the request is handled and the result is answered in the same ticket.

Policy updates: when the policy changes, the last-updated month at the top of this page is revised at the same time. If a change widens the scope of processing, a prominent notice will appear on the site; continuing to use the service means you accept the updated policy. Questions about this policy can also be sent through the ticket entry, and the service will answer in the ticket.

Try for Free