Scope of this policy
This policy covers VPNHF's website pages, user panel and client apps on every platform (Windows / macOS / iOS / Android / Linux), and explains how the service handles information about visitors and registered users.
The policy does not cover third-party sites reached through the service. Those sites follow their own privacy practices and cookie settings, which the service cannot describe on their behalf and is not responsible for.
The service is offered to users with full legal capacity and is not intended for minors.
What data is collected and why
Account data. Registration needs only a username and password; no email address is required. Passwords are stored irreversibly, so the service cannot read them in plain text or recover an original password — it can only be reset through the reset flow. If a user voluntarily includes contact details in a ticket, that information is used only to reply to that ticket.
Order and billing data. This covers plan tier, order amount, payment method, order time, order number and remaining data-pack balance. It is used to activate service, reset monthly subscription data on the activation date, deduct data-pack allowance, and handle refunds and reconciliation.
Device and session data. This covers the current number of concurrent connections, client platform type and the approximate region of the connected route. It is used to support unlimited simultaneous connections and to identify which link in the chain is at fault when a connection fails.
Visit statistics. Aggregated data such as page paths, referrers, device types and coarse region, used for capacity planning and page improvements. The analytics script is self-hosted, so the data does not pass through a third-party analytics platform.
No-logs stance and connection data
The service does not record which websites a user visits, does not store DNS queries or browsing history, and does not use connection records for advertising profiles. This is part of the terms of service and does not change with the plan tier.
To bill and run the service properly, the system processes two kinds of necessary technical data:
- Traffic metering: the cumulative data used by each account (measured in GB), used for the monthly reset of subscriptions and for deducting data packs.
- Session state: the current number of concurrent connections and the route ID, used for unlimited-device concurrency management and protection against abnormal traffic.
Both kinds of data are kept for a shorter period than order data — only as long as needed for metering, troubleshooting and abuse prevention, then cleared on a regular cycle. Transfers use bank-grade encryption.
Cookies and local storage
The cookies and browser local storage used on this site serve only three purposes:
- remembering language preference so it does not have to be chosen on every visit;
- keeping the user panel session signed in, expiring automatically on logout or token expiry;
- remembering interface state in the panel, such as the last section viewed.
This data is used only for the three purposes above; it is not used for ad targeting or to stitch together a user's behaviour on other websites. It can be cleared at any time in the browser's site settings; after clearing, you will need to sign in again or reselect a language, and the validity of purchased plans is unaffected.
Payments and third-party processing
Payment is completed through Alipay, WeChat or USDT. Each payment is handled by the relevant channel; this site neither touches nor stores card numbers, payment account passwords or private keys. For USDT transfers only the on-chain transaction hash is recorded, to confirm receipt.
Apart from payment channels, account and order data is not provided to third parties for marketing. Where a valid legal process requires it, the necessary account and order records may be provided within the scope that the process explicitly sets out.
Data retention, deletion and policy updates
Retention periods. Account data is kept while the account exists; after closure, the account identifier and login credentials are discontinued and deleted. Order and billing records are kept from the last transaction until both the 60-day no-reason refund window and the period needed for reconciliation have ended, then deleted or anonymised — refund handling needs these records, so they cannot be removed early within that window. Visit statistics are kept in aggregate form without identifiers that could point to an individual.
How to request deletion. Deletion requests are submitted through the ticket entry in the user panel, stating the scope of data to be deleted. After account ownership is verified, the request is processed accordingly; records such as completed reconciliation vouchers may be retained until the retention period ends for legal or accounting needs, and the outcome is answered in the ticket.
Policy updates. When this policy is updated, the “Last updated” date at the top of the page changes with it. Major changes to how data is used or to its scope are announced on the site; continued use of the service is taken as acceptance of the updated policy. Questions about this policy can be raised through the ticket entry in the user panel.