Privacy Policy

Last updated: August 2026

This policy explains how a4VPN collects, uses, retains, and deletes data when providing cross-border access, international routes, and subscription services. Using the service means that the user has read this policy. If the user disagrees with these practices, they should stop using the relevant features.

Data Collected and Processing Purposes

a4VPN processes only the data required to provide accounts, subscriptions, payment confirmation, and technical support. No email address is required for registration; users can create an account with a username and password. The standard registration process therefore does not request an email address. The username identifies the account, while the password is stored in a protected form for authentication.

Subscription and order processing creates order records, including the selected item, payment status, creation time, and account association. These records support subscription delivery, payment verification, refund requests, order disputes, and account history. Payment methods include Alipay / WeChat / USDT; the relevant payment service handles detailed payment credentials, while a4VPN receives only the status and result information needed to complete the order.

The website may collect aggregated statistics such as page visits, referring pages, browser type, device category, and interaction events to check whether pages work properly, improve navigation, and investigate anomalies. These statistics are not used to build a profile of the websites users access internationally.

No-Logs Position and Connection Data

a4VPN does not record which websites users access, store webpage content, search content, message content, or complete browsing histories, and does not use such content for profiling. When the route system processes connection requests, it does not create historical connection logs for the purpose of continuously tracking personal network activity.

To protect accounts, calculate subscription traffic, troubleshoot connection failures, and prevent service abuse, the system may generate necessary temporary technical events, such as account status, traffic usage results, error types, and route scheduling results. These events do not contain the content of pages users access and are not retained as routine browsing records. Temporary technical data is retained only as long as needed for troubleshooting, security response, or account reconciliation; once the purpose is complete, it is deleted, aggregated, or de-identified.

When users submit a support ticket, the ticket content and diagnostic information they choose to attach are used to address the relevant issue. Users should provide only the information needed to reproduce the problem and avoid including unrelated private content in screenshots or text.

Cookies and Local Storage

The website and user panel use Cookies or browser local storage to save login sessions, interface language, necessary security states, and feature preferences. They maintain login status, restore user choices, and keep page functions consistent; they are not used to store which websites users access.

Users can clear Cookies and local storage through their browser settings. After clearing them, the account may require a new login, and language or interface preferences may return to their defaults. Disabling necessary storage may prevent authentication, order actions, or some user panel features from working properly.

Third-Party Payments and Data Sharing

Payments are handled by the third-party payment service selected by the user. A payment service may collect payment account details, transaction identifiers, or risk-control data under its own rules; such processing is governed by that service's privacy policy. a4VPN does not directly store complete authentication credentials for third-party payment accounts.

a4VPN transfers limited data to service providers only when necessary to complete payments, provide routes, maintain infrastructure, meet applicable requirements, or protect service security. Account data is not shared for the purpose of selling personal information. Service providers should process the relevant information only within the scope of their assigned purpose.

Retention, Deletion, and Policy Updates

Account data is retained while the account remains active. Order records are retained for accounting checks, refund processing, dispute resolution, and necessary compliance requirements; analytics are preferably kept in aggregated or de-identified form. Retention periods vary according to purpose. When data is no longer needed, it is deleted or converted into statistical information that cannot be directly linked to an account.

Users can use the support ticket entry in the user panel to request deletion of account data or ask about specific data practices. Account control may need to be verified before a deletion request is processed. Data related to incomplete orders, refund requests, security incidents, or necessary records will be deleted after the relevant matter is complete; aggregated data that has been de-identified and can no longer be linked to an account generally cannot be extracted separately.

This policy may be updated as service processes, storage methods, or applicable requirements change. The updated version will be published on this page, and the last-updated month at the top will be adjusted. Material changes to data practices may also be announced through the user panel. Users should review the policy in effect before continuing to use the service.