Privacy Policy

Last updated: 2026-09

VPNDQ provides cross-border network acceleration services. This policy explains what data the service collects during registration, checkout and use of the client, why it is collected, how long it is kept, and how users can access and delete it. Together with the Terms of Service and the plan descriptions, this policy forms part of the service agreement.

What data we collect and why

The service collects only the data needed to provide it, in roughly these categories:

• Account information. Registration requires only a username and password — no email address, and no name, address or other identity details. Passwords are stored as irreversible hashes, never in plain text.
• Order and payment records. These cover the plan or data package purchased, the amount, the order time, the payment channel (Alipay / WeChat / USDT) and the order status, and are used to activate routes, confirm that funds arrived and handle 7-day no-questions-asked refund requests.
• Usage and connection data. These cover connection times, the identifier of the route used and traffic volume, and are used to bill against plan quotas, reset traffic monthly on the activation date, and troubleshoot connection problems.
• Visit analytics. These cover page views, referral sources, browser and device type and coarse location, and are used to decide which documentation needs expanding and to plan route capacity.

Contact details users provide voluntarily in tickets or support conversations are used only to answer the question at hand, and for nothing else.

No-logs stance and connection log retention

The service does not record which websites users visit, does not log the content of DNS queries, and does not store the content users transmit over its routes. Traffic between the client and the routes is encrypted end to end, and the specific destinations users access fall outside what the service records. This stance applies to all 240+ routes and does not change with the route type (IEPL dedicated / relay / direct).

The session metadata needed for billing (route used, connection time, traffic volume) is handled separately from access destinations: the former is essential for settlement and troubleshooting and is kept for the billing cycle, while the latter never enters storage.

Cookies and local storage

This site uses cookies and browser local storage for a small number of essential functions, limited to the following:

• Language preference. Remembers the interface language a user selects, so the next visit opens directly in that language.
• Login state. The user panel keeps login credentials in local storage so users do not have to sign in again while they remain valid; it expires on logout or when browser data is cleared.
• Visit analytics. A self-hosted analytics component records page visits to show how much the documentation is used and where visitors come from; measurement is limited to this site.

Users can clear cookies and local storage at any time in their browser settings. Afterwards the language preference and login state need to be set again; everything else keeps working.

Payments are handled by third parties

Payments go through third-party channels: Alipay and WeChat are processed by the respective payment providers, and USDT is transferred on-chain. The service neither receives nor stores card numbers, payment passwords, wallet private keys or other payment credentials — only the transaction result returned by the payment channel, including success or failure, amount, time and the channel's order number.

Payment channels handle transaction information under their own privacy policies. That part is outside the service's control, so it is worth reading the relevant channel's terms before paying.

Data retention periods and deletion

• Account information and order records are kept for as long as the account exists. After an account is closed, records needed for reconciliation, refund disputes and legal obligations are kept for the required period; the rest is deleted or anonymized.
• Billing usage records are kept for the settlement cycle; once settlement is complete, only aggregated statistics remain, no longer linked to a specific account.
• Device and referral information in visit analytics contains no account identifiers and cannot be traced to an individual user.

To access, correct or delete your data, submit a request through the ticket entry in the user panel, noting the account name and exactly what you need, so it can be verified and handled. When an account is closed, the subscriptions and route configurations tied to it stop working at the same time.

How this policy is updated

This policy is revised as the service scope and compliance requirements change; the date at the top of the page is updated accordingly, without item-by-item notice. Material changes to what data is collected or how it is used are explained in site announcements, with a reasonable transition period before they take effect.

Questions about this policy can be submitted through the ticket entry, or via the relevant channel linked from the support page.