Legal document · Data and privacy

Privacy Policy

This page explains what data VPNQK collects while providing cross-border network acceleration subscriptions, why it is collected, how long it is kept, and how users can request deletion.

Last updated: 10/2026

Scope of this policy

This policy explains how VPNQK (referred to below as “the Service”) handles user-related data when providing cross-border network acceleration subscriptions. It covers the public pages of this site as well as the user panel available after sign-in — registration, plan selection, subscription retrieval, orders and support tickets are all handled inside the user panel.

This policy does not cover third-party websites and services that users reach through the Service. Those sites have their own privacy practices and cookie settings, which the Service cannot control and is not responsible for.

Data we collect and how we use it

The Service collects only the data needed to deliver subscriptions and provide after-sales support. The main categories are:

  • Account information. Registration requires only a username and password — no email address. Passwords are stored as irreversible hashes; the Service cannot read them in plain text. This data is used to identify the account, keep users signed in, and attribute plans and support tickets to the right account.
  • Order and billing records. This includes the plan or data pack tier selected, the amount, activation and expiry dates, data usage, payment channel type and transaction ID. It is used to deliver the subscription, calculate remaining data, and verify orders when a 7-day refund with no reason required is requested.
  • Support tickets and correspondence. The content of tickets submitted in the user panel, plus device models and client versions users provide voluntarily to help with troubleshooting. This is used to diagnose problems and keep a record of how each case was handled.
  • Aggregated traffic statistics. Page views, referral sources, device types and browser versions. These are compiled in aggregate to see whether pages work and which device types run into problems.

None of this data is used for advertising profiles, and none of it is sold or rented to third parties.

Access data we do not log

The Service follows a no-logs policy. While providing network acceleration, it does not record which websites users visit, does not store DNS query contents, does not log connection times or transferred data, and does not build access logs that link an account to a destination website.

Where the no-logs policy ends To determine whether a route is usable, operations staff only track whether connections succeed, along with route load and failure counts. These metrics exist as aggregate values, contain no destination information, are not linked to individual accounts, and are kept only for the short period needed for troubleshooting before being rolled over and discarded.

Note that no-logs means the Service does not actively record the access information described above. Browser history and client caches on the user's device, as well as records kept by the third-party sites users visit, are outside the Service's control.

Cookies and local storage

This site does not use cross-site advertising tracking and does not load third-party advertising cookies. Browser local storage and cookies are used only for the following purposes:

  • Sign-in session. After sign-in, a session credential is stored to keep the user signed in inside the user panel. It expires on sign-out or when browser data is cleared.
  • Preferences. Remembers the selected language and the last page position, so users do not have to repeat the same steps.
  • Traffic statistics. Records page visits in a de-identified form to understand page loading and availability.

All of these can be cleared in browser settings. After clearing, users need to sign in again; purchased plans and subscription entitlements are unaffected.

Payments and third parties

The Service accepts Alipay, WeChat and USDT. Transactions are completed by the relevant payment channel; card numbers, payment account details and wallet private keys never pass through the Service's servers. The Service receives only the payment result and transaction ID, which are used to activate the subscription and verify the order.

Payment channels collect the information they need under their own privacy policies, so it is worth reading the relevant channel's notice before ordering. Except where required by law, the Service does not provide account information to anyone other than the payment channel.

Retention, deletion and updates

Data retention follows the principle of keeping the minimum necessary: account information is kept while the account exists; order and billing records are kept for the period needed for refunds and reconciliation, then deleted or anonymised; closed tickets are kept for a traceable period and then cleared; aggregate statistics are not archived long term.

To have data deleted or an account closed, users can sign in to the user panel and submit a ticket stating what should be deleted. Once account ownership is verified, the request is processed. After an account is closed, remaining data and subscription entitlements end with it, and deletion cannot be undone. Billing and refund history can only be cleared after the refund process is complete.

If this policy changes materially, the “Last updated” date on this page will be revised and a notice will appear in the user panel. Continuing to use the Service after a change means accepting the updated policy; if users do not accept it, they can stop using the Service and request account closure before the change takes effect.

This policy is accompanied by our Terms of Use and Refund Policy; the specific rules on subscription billing and refunds are governed by those two documents.