Privacy Policy

Information Collected and Purposes

No email address is required to register. An account can be created with a username and password, so the registration process does not collect an email address. The system stores an account identifier, securely processed authentication data, plan status, total traffic usage, and necessary account settings to verify login status, calculate available services, enforce traffic rules, and restore configurations that users choose to save.

Purchases and refunds create transaction records such as an order number, amount, payment method, order status, and creation and completion times. These records confirm payment, deliver subscriptions, process refunds, review unusual orders, and resolve transaction disputes. HBVPN supports Alipay / WeChat Pay / USDT and processes only the transaction results needed to manage completed orders. Users are not required to submit payment credentials on marketing pages.

When users visit the site's marketing pages, servers and analytics tools may process technical information such as page addresses, referring pages, browser type, device category, network address, and request time. This helps verify that pages work properly, identify errors, analyze content access trends, and prevent abuse. Visit analytics are primarily aggregated and are not used to build personal profiles related to content accessed through network acceleration.

No-Log Policy and Connection Data

HBVPN does not record which websites users access through international routes, or retain page content, transmitted content, or historical records that could be used to reconstruct browsing activity. Traffic content handled during network acceleration is not used for advertising analysis or combined with marketing-page analytics to create browsing profiles.

To enforce plan traffic rules, determine whether a subscription is valid, and keep routes running, the system processes account-level traffic totals, subscription status, and necessary technical error events. Error events help identify connection failures, resource issues, or security risks and do not include a list of websites visited. These events are retained only as long as needed for troubleshooting and security handling, then deleted or de-identified; account traffic totals are updated as needed for subscription management.

Cookies and Local Storage

The site may use cookies or browser local storage to save login sessions, language choices, interface preferences, and necessary security status. This data keeps users signed in, remembers their choices, and prevents duplicate submissions. It is not used to record external websites accessed through the network acceleration service.

Users can clear cookies and local storage through their browser settings. After clearing them, login status and saved preferences may expire, requiring users to sign in again or select interface settings again. Some necessary storage must be enabled when using the relevant features to keep authentication and order processes working properly.

Payment Processing and Required Disclosure

Payments are handled by the relevant payment channel. Payment channels may collect and verify information needed to complete a transaction under their own rules, and their processing is governed by the applicable privacy policy. HBVPN receives payment status, transaction identifiers, and necessary settlement results to activate services, reconcile accounts, and process refunds. It does not store complete payment credentials held directly by payment channels.

Except where necessary to provide services, settle payments, protect security, or comply with applicable rules, account information is not provided to unrelated parties. Service providers responsible for hosting, analytics, or payment processing may process data only for agreed purposes and within the necessary scope. When a legally valid data request is received, it is handled only after the request's basis and scope have been verified.

Data Retention, Deletion, and Policy Updates

Account data is retained while an account remains active to provide login, subscription, and order lookup functions. Order records are retained as needed for transaction reconciliation, refund processing, dispute resolution, and applicable rules. Marketing-page analytics are deleted, aggregated, or de-identified after analysis is complete. Data no longer needed for business purposes is removed from systems in normal use, although backups created for security recovery may be cleared after the backup cycle ends.

Users can sign in to the user panel and submit a ticket to request access to, correction of, or deletion of account-related data. After receiving a request, this service first verifies control of the account and then processes eligible content for deletion. Data still related to incomplete orders, refunds, disputes, or necessary security records must remain until the relevant matter ends; after deletion, account login, subscription lookup, and access to historical orders may not be recoverable.

This policy may be updated when service processes, data handling practices, or applicable rules change. Revisions will be published on this page and the date at the top will be updated. Changes that materially affect data processing may also be announced through site notices or the user panel. Users can review the latest version and related changes before continuing to use the service.

Submit a data request through the user panel, or read the Terms of Service for account and service rules.