Legal

Privacy Policy

Last updated: October 2026 (2026-10)

This policy explains what data VPNAF handles while providing cross-border network acceleration subscriptions, why that data is needed, how long it is kept, and how you can review or delete it. Each section follows the actual processing workflow so you can check it point by point.

1. Scope

This policy applies to the VPNAF website, the user panel and the clients for each platform, and covers data processing for accounts, subscriptions, billing and support. Third-party sites you reach through our routes have their own privacy policies; their data handling is unrelated to this service and falls outside this policy. Where a feature comes with its own data notice, that notice takes precedence.

2. Data Collection: Scope and Purpose

We collect only the data required to run the subscription service, in four categories by purpose:

• Account information: signing up requires only a username and password, with no email address. Passwords are stored as irreversible hashes; plaintext is never kept.
• Subscription and billing: order number, plan tier, activation and expiry dates, and remaining traffic, used to calculate plan allowance, handle prorated mid-term upgrades and process refunds.
• Visit analytics: page path, referrer, device type and browser version, used to judge which pages need improvement; results are reviewed in aggregate.
• Support records: ticket content and screenshots you submit voluntarily, used only to diagnose faults and answer your questions.

3. Our No-Logs Stance and Connection Records

We do not record which websites you visit while connected, do not store browsing content or DNS query records, and do not build a traceable access log for each account. On the network side we keep only the technical state needed to maintain a session, such as the current exit route and session duration; once the session ends, that state is no longer linked to any destination.

Traffic usage for billing is counted per account and used only to determine the remaining plan allowance; it contains no destination information.

One boundary worth stating: Alipay, WeChat and USDT payments are handled by third-party channels, and visit analytics are provided by a third-party service, each bound by its own terms. If we receive a legally valid request, the service may be required to provide account and order records, limited to the account and billing data described above.

4. Cookies and Local Storage

We use a small number of cookies and browser local storage entries, for three purposes only:

• Language preference: remembers the language you last chose, so you do not have to pick it again when moving between pages.
• Sign-in state: user panel credentials are kept in browser local storage, so you stay signed in after closing the page; signing out clears them.
• Visit analytics: anonymous page-view counts, with no cross-site tracking.

All of these can be cleared at any time in your browser settings. After clearing, you will need to sign in again and the language preference returns to its default; disabling cookies does not affect reading public pages.

5. Payments and Third-Party Processing

Payments are completed through third-party channels; we support Alipay, WeChat and USDT. Credentials such as payment account and password are entered on the channel's page and never pass through our servers. We receive only the order number, amount and payment status returned by the channel, used to activate the subscription and reconcile accounts; full payment credentials are not stored.

Beyond delivering the service, billing and troubleshooting, data is not used for other purposes and is not shared with unrelated third parties. Where disclosure is required by legal process, it is limited to account and order records.

6. Data Retention, Deletion and Policy Updates

Retention: account and order records are kept for as long as the account exists. After a subscription expires, billing records are kept a while longer for financial reconciliation, then deleted or anonymised; traffic usage is aggregated monthly and per-connection details are not retained.

Deletion: you can submit a deletion request through the ticket form in the user panel, stating which account or data you want removed; we verify account ownership and then act. Records tied to orders and refunds can only be fully deleted after the 60-day no-questions refund window closes.

Policy updates: this policy is revised as the service changes; the new version is published on this page and the last-updated month at the top is changed at the same time. Changes affecting how data is used are announced in the user panel.