Privacy Policy

Privacy Policy

Last updated: September 2026

This policy explains what information VPNVF processes when providing cross-border network acceleration services, its website, and the user panel, why it is processed, and how users can manage it. Using the service means you have read this policy; if you disagree with these practices, stop using the relevant features.

Information Scope and Processing Purposes

No email address is required to create an account; a username and password are sufficient, so an email address is neither required nor collected by default during registration. VPNVF processes the username, account status, and necessary authentication information that users provide to identify accounts, maintain sign-in status, and deliver subscription services. Passwords are used for authentication in a form that cannot be directly read and are not stored as ordinary text accessible to operations staff.

When purchasing a plan or data package, the service stores order details, amount, order status, selected payment method, refund status, and records related to delivery. This information is used to complete orders, verify subscription entitlements, handle support requests, and maintain financial records. To calculate plan usage and display remaining quota, the system also processes aggregated traffic usage associated with the account. This data does not include website names, page content, or specific network activity.

The website and user panel may process page visits, browser type, device operating system, referring pages, error information, and basic request metadata to identify page failures, analyze feature usage, and maintain service security. Website analytics are kept separate from data generated by network acceleration connections and are not used to build profiles of the websites users access internationally.

No-Logs Position and Connection Data

VPNVF does not record which websites users visit or retain access destinations, search queries, transmitted content, or application activity records. The service does not create connection logs combining connection times, source addresses, exit addresses, session duration, and access destinations, nor does it use such logs to track an individual account’s network activity.

The system may process aggregated usage to provide traffic quotas and subscription status, and may briefly process the technical information required to complete routing while a connection is active. This information is used only for that network transmission and is not retained as connection history. Website security records, order records, and aggregated usage are not browsing-content records and do not change the no-logs principle described above.

Cookies and Local Storage

The website may use Cookies or browser local storage to save sign-in credentials, interface settings, language preferences, and necessary session status. This data is used to maintain sign-in, restore user choices, and keep the user panel working properly. It is not used to record websites accessed through international routes.

Users can clear Cookies and local storage through their browser settings. After clearing them, sign-in status and some interface preferences may reset, requiring users to sign in again or select the relevant settings again. If the browser is prevented from saving necessary data, account authentication, order viewing, or subscription management may not work properly.

Third-Party Payment Processing

VPNVF supports Alipay, WeChat, and USDT. Payments are processed by the relevant payment service or transaction network, whose collection and use of information are governed by its own rules and privacy terms. The service receives the payment result, transaction status, and necessary order identifiers required to complete an order; it does not require users to submit complete authentication credentials for a third-party payment account to VPNVF.

Payment services may independently retain relevant information for transaction processing, risk control, or compliance purposes. VPNVF cannot directly control third-party data retention arrangements. Before choosing a payment method, users should review the terms presented by the relevant provider and decide whether to proceed based on their own needs.

Data Retention and Deletion

Account information is retained while the account remains in use so that sign-in, subscription, and support features can be provided. Order and refund records are retained for the period necessary to complete transactions, resolve disputes, and meet required record-keeping obligations. Website analytics are retained only as long as necessary to maintain the service after troubleshooting and aggregation are complete. Information with no remaining processing purpose is deleted or converted into aggregate results that cannot be linked to a specific account.

Users can request deletion of their account and deletable associated information through the ticket function in the user panel. After a request is submitted, VPNVF verifies account ownership and processes the deletion request. Data that has already been aggregated and cannot be linked to an account, as well as records that must be retained by law or to resolve incomplete orders and disputes, may not be deleted at the same time. They will be cleared through the relevant process once the retention purpose ends. Deleting an account may permanently remove remaining subscription entitlements, access to historical orders, and client subscription management features.

Policy Updates and User Choices

This policy may be updated when service features, data practices, or applicable requirements change. The updated text will be published on this page, and the last-updated month at the top of the page will be changed accordingly. Important changes to processing scope or user rights will be communicated through the website, user panel, or other available on-site methods.

Users may stop using the service at any time, clear local data in their browser, or submit data access and deletion requests through the user panel. Continuing to use relevant features after a policy update indicates that the user has read the updated content. If the user disagrees with the changed practices, they should stop using the service and request account-data handling as described above.