This policy covers the site pages and the user dashboard, from account creation and subscription through using routes and opening tickets. In this document, “the Service” means the cross-border network acceleration subscription provided by VPNDH.
What data is collected and why
The Service collects only the data needed to maintain a subscription relationship, in four categories.
- Account data. Creating an account does not require an email address; an account consists of a username and password. Passwords are stored as irreversible hashes — the Service never keeps plaintext passwords and cannot recover the original from the hash.
- Order and billing data. This includes the order number, plan purchased, amount, payment method, activation date and traffic usage. Traffic counters are used to check plan allowances, reset monthly on the activation date, and calculate the prorated difference when upgrading mid-cycle.
- Visit statistics. This includes page view counts, referral source, browser and device type, and coarse region. The data shows which explanations are clear and which pages need work; it is not used for cross-site tracking or ad targeting.
- Ticket content. Problem descriptions, screenshots and replies that users submit voluntarily, used to diagnose faults and follow up on the case.
Connection logs: what is not recorded
When the subscription is in use, the Service does not record which websites a user visits, does not store DNS query contents, and does not keep mappings such as “this account connected to this destination at this time”.
Running the routes produces necessary metering data: concurrent connections on the current route and traffic already used by the account. This data exists as counters or aggregates, is used only for capacity scheduling and plan metering, and is not linked to specific destinations.
The Service does not record destinations, does not store DNS query contents, and keeps no link between connection times and destinations. This applies to every route, regardless of plan tier. Because no access logs exist, if a competent authority issues a formal legal request, the only information the Service can provide is account and order-level data.
What cookies and local storage are used for
The site uses no third-party advertising cookies and does no cross-site behavioral tracking. Browser local storage is used for three things only: keeping users signed in (storing the login token), remembering the interface language preference, and remembering the plan cycle last viewed.
This data lives in the user's own browser and can be removed by clearing browser data; after that, signing in again is required. Visit statistics are self-hosted, and no page-behavior data is sent to third-party ad networks.
Payment is handled by third parties
The site accepts Alipay, WeChat Pay and USDT. Payment is completed on the relevant channel's page or app; card numbers and payment account credentials are handled by the payment channel and are never seen or stored by the Service.
The Service only receives the result sent back by the channel: order number, amount, payment status and payment time, used to activate the subscription, reconcile accounts and issue refunds. Refunds follow the “60-day refund, no questions asked” policy; see the Terms of Service for conditions and process.
Data retention, deletion and account rights
Account and order data is kept for as long as the account exists. Users can open a ticket in the user dashboard at any time to request account deletion; once deleted, the account and its subscription cannot be restored, and any remaining traffic allowance is forfeited.
Order and payment records are kept for the period required by reconciliation and legal requirements, then deleted or anonymized and no longer used for any other purpose.
Users may also request correction of account details, look up order records, or ask that their data not be used for visit statistics. Requests are handled after identity verification.
Policy updates and contact channels
When the policy changes, the “Last updated” date at the top of this page changes with it. Material changes to how data is used are announced on the site or flagged in the user dashboard. Continuing to use the Service after a change means accepting the updated version; if the update is not acceptable, users can stop using the Service and request account deletion.
The contact channel is the ticket system in the user dashboard; before submitting, users can also check the Help Center or the support page — most common questions already have an answer there.