Privacy Policy

Scope and Processing Principles

This policy applies to VPNHu marketing pages, the account panel, order flows, client download entry points, and international route connection services. Data is processed to manage accounts, deliver subscriptions, maintain routes, process payment status, troubleshoot issues, and protect service security. Only data relevant to these purposes enters the applicable workflows, with access limited according to its use.

This policy does not apply to external websites or services accessed through international routes. Each external service determines its own data collection practices, and users should review the privacy information provided by those services.

Data Collected and Its Uses

No email address is required for registration; an account can be created with a username and password. The system stores the account identifier, securely processed password information, subscription status, and necessary account settings to authenticate users, display service status, and restore their choices.

Order records include the selected plan, payable and paid amounts, payment channel, order status, creation and completion times, and related records needed for refunds. This data is used to confirm entitlements, verify payments, handle order disputes, and meet financial record obligations. The system also processes traffic usage and reset status to apply monthly subscription and traffic package rules, but does not use this information to create a browsing-content profile.

When the website is accessed, the server may process basic analytics such as page requests, referring pages, browser type, operating system, IP address, error information, and access time. This information is used to analyze page performance, identify abnormal requests, and resolve compatibility issues. It is not used to infer specific content viewed on international websites.

No-Logs Position and Connection Records

VPNHu does not record which websites users access through the service. It does not store webpage content, search queries, transmitted content, or application message bodies, and does not organize access destinations into a browsing history linked to an account.

Routine route operations do not create connection logs that can be traced to specific account activity over the long term. To locate route failures, prevent misuse, or handle security incidents, the system may temporarily process a minimal amount of operational event data, such as error type, route status, and the time an anomaly occurred. These events do not contain browsing content, are not used to build user profiles, and are deleted or de-identified after troubleshooting or security handling is complete.

Route services must process necessary network data in real time during a connection to complete forwarding. This real-time processing is not the same as storing access records; transmitted content is not retained for routine operational purposes after forwarding is complete.

Cookies, Local Storage, and Payment Processing

The website may use Cookies or browser local storage to save login status, interface language, session identifiers, and necessary security information. These data maintain account sessions and restore user settings. If necessary storage is disabled, login status, language preferences, or account panel functions may not remain available.

Payments can be completed through Alipay, WeChat, or USDT. Payment credentials and payment authorization are handled by the relevant third-party payment process. VPNHu receives the payment result, order identifier, and status information needed to complete an order. Third-party processors retain payment data under their own rules, and users should also read the terms provided by the relevant channel before payment.

To deliver infrastructure, maintain the website, and process payment status, the service may share task-essential data with providers responsible for related functions. Such data is limited to the purpose of the relevant service and is subject to applicable access controls and confidentiality requirements.

Data Retention, Access, and Deletion

Account information is generally retained while the account remains active. Order and payment results are retained for transaction verification, refund processing, security review, and applicable record obligations. Basic analytics and temporary operational events are retained only as long as needed for analytics, troubleshooting, or security purposes. When the purpose for retention ends, the relevant data is deleted, aggregated, or de-identified.

Users can view available account and order information in the account panel. To correct account information, delete an account, or submit a request concerning personal data, users can use the ticket entry in the account panel. To prevent action by someone else, account control may need to be verified before processing. After a deletion request is completed, information that must remain available for transaction obligations, security incident handling, or dispute resolution may be retained with restricted access; other deletable data is removed from normal business systems.

Cookies and local storage in the browser can be cleared through browser settings. After clearing them, users may need to log in again and reselect interface settings.

Policy Updates and Questions

This policy may be updated when the scope of data processing, product functions, payment flows, or applicable rules change. The new version will be published on this page, and the last-updated date at the top will be changed. Important adjustments to data usage will be communicated through available on-site methods, and the updated terms will apply to subsequent data processing from the time they are published.

For questions about this policy, data processing records, or the deletion process, please submit specific details through the ticket entry in the account panel. Requests should avoid including sensitive information unrelated to the issue, so verification and processing can be completed within the minimum necessary scope.