Privacy Policy

Last updated: 2026-09

This page explains what user-related data VPNPF processes while providing cross-border network acceleration, why it is processed, how long it is kept, and how users can request deletion. The policy covers the website, the user dashboard, and subscriptions activated through the dashboard.

Read this page together with our Terms of Service and Refund Policy. If you do not agree with the data handling described here, please do not sign up or continue using the service.

1. Scope

This policy applies to the VPNPF website, the user dashboard, and the subscription service itself, and the data we process is limited to what is necessary to set up an account and provide the subscription. It does not cover third-party websites you reach through the service — those sites have their own privacy policies and describe their own data collection, which this service cannot vouch for.

Account and subscription actions all take place inside the user dashboard, and requests involving account data are submitted through the dashboard ticket form so identity can be verified and progress tracked.

2. Data We Collect and How We Use It

Registration details. Accounts are created with a username and password — no email address required. The system stores the username, an irreversible hash of the password, and the registration time. Passwords are kept as hashes; the server never retains plaintext passwords.

Order and billing records. To activate plans, settle data quotas, and process refunds, the system stores the order number, the plan purchased, the amount, payment status, activation time, and the total data consumed by the account in each billing cycle. Usage totals are used for quota settlement and do not include the destinations visited.

Visit statistics. The website and user dashboard record aggregate page-visit data such as visit time, page path, referrer, and device type, used to troubleshoot problems, confirm pages load correctly, and improve content. These statistics are not used to identify individuals and are not combined with order information to build user profiles.

Ticket records. When a user submits a ticket, the system stores the ticket content and handling history so the issue can be followed up and referenced later.

3. Our No-Logs Stance

The service does not record which websites users visit through its routes, does not store destinations, domain names, or session content, and keeps no connection logs that could reconstruct browsing activity. No such records are kept on the route side.

Two kinds of data need to be distinguished: quota statistics and access logs. Quota statistics record only the total data an account consumes in a billing cycle, used for plan settlement and prorated upgrade credits, and contain no destinations or session content; access logs are not retained by this service.

To handle payment disputes, refund verification, and troubleshooting, order records and ticket records are kept for the periods necessary, as described in Section 6.

4. Cookies and Local Storage

The website and user dashboard use a small number of cookies and browser local storage, limited to the following three purposes:

Language preference: remembers the interface language you chose so your next visit opens in that language.
Sign-in state: the user dashboard stores session credentials in browser local storage to keep you signed in; they are cleared when you sign out.
Basic statistics: page-visit statistics use a cookie to distinguish sessions, solely to check whether pages open correctly.

Cookies and local storage are used only for the three purposes above, never for advertising, and browsing data is not shared with ad networks. You can clear cookies and local storage in your browser settings; after clearing, you will need to sign in again and reselect your language.

5. Payments and Third-Party Providers

Plan payments are handled by third-party payment providers; Alipay, WeChat, and USDT are currently supported. During payment, the provider processes the necessary transaction information under its own privacy policy; this service receives a payment result notification containing the order number, amount, and payment status, and never touches full payment credentials such as card numbers or payment passwords.

Refunds follow the Refund Policy: a full, no-questions-asked refund can be requested within 60 days of your first payment. Processing a refund requires checking the order record, and those records are kept for the period required for reconciliation and legal purposes after the refund is complete.

6. Data Retention, Deletion, and Policy Updates

Retention periods. Account data is kept while the account exists; order and payment records are kept for the period required for reconciliation and legal purposes; ticket records are kept for a while after the issue is closed so they can be referenced later.

How to delete. You can submit an account closure and data deletion request at any time through the ticket form in the user dashboard, stating what you want deleted. Once your identity is verified, the service deletes the account data; records still within a legal or reconciliation retention period are deleted when that period ends. After deletion the account cannot be restored, and any purchased plan and remaining data allowance are void.

Policy updates. This policy may change as the service or compliance requirements evolve. Updated versions replace the content of this page directly, and the last-updated date at the top of the page is revised; for significant changes to how data is handled, a notice will appear on the website or in the user dashboard. Continuing to use the service means you accept the updated version.

If you have questions about this page, leave a message on the contact page or open a ticket in the user dashboard.