This policy describes only the data processing that actually takes place. The service does not actively collect any data type that is not listed here.
Key points: signing up requires only a username and password, with no email address; the service does not log which websites you visit; payments are completed by the payment providers, and no payment credentials are stored; data access and deletion requests can be opened as a ticket in the user panel.
1. Scope
This policy applies to individual users who subscribe to VPNFH online through this site, and covers four stages: account registration, plan purchase, client use and ticket communication. For bulk purchases by businesses or teams, the terms confirmed by both parties apply, with this page serving as background information.
This policy does not cover third-party websites and services that users reach over international routes. Those sites have their own privacy policies, and their data handling is unrelated to this service.
2. Data We Collect and Why
The service collects only the information needed to maintain the subscription relationship, itemized below.
- Account information: username and password. Registration does not require an email address, so the service stores no email field; passwords are kept as irreversible hashes, and staff cannot recover the plaintext.
- Order and billing records: plan tier, data packs, payment channel, order number and order time. Used to activate and renew subscriptions, reset data and verify refunds.
- Ticket content: problem descriptions, screenshots and replies that users submit voluntarily. Used only to diagnose and resolve issues.
- Visit statistics: aggregated data such as page views, referral source and device type, used to check whether pages load properly and which device types run into problems.
Account information and order records are a prerequisite for providing the service; without either, a subscription cannot be activated. Visit statistics are aggregated and are not used to identify individuals.
3. Where We Stand on Logging
No-logs means the service does not record which websites users visit or which apps they use while connected. The operator does not generate or store the following:
- Domains and URLs that users visit
- Destination IP addresses and ports of connections
- DNS query records
- Start and end times of each connection, or traffic details
Since connection logs are never generated, there is no retention period for them. To keep routes available, the operator looks only at operational metrics that are unrelated to individuals: total bandwidth usage per route, the number of active sessions, and fault alerts. These metrics are aggregated per route and are not linked to any individual account.
No-logs and an account system are not in conflict: billing requires knowing who is paying, so account information and order records are kept for the periods described at the end of this page.
4. Cookies and Local Storage
This site uses no third-party advertising cookies and does no cross-site tracking. Only three types of data are stored in the browser:
- Language preference: records the interface language the user has chosen, so it does not have to be selected on every visit.
- Sign-in state: after signing in to the user panel, the sign-in token is stored in the browser's local storage so the password does not have to be entered again; it expires when the user signs out or clears browser data.
- Visit statistics: page visits recorded in aggregate, with no identifier that could point to an individual.
All of the above can be cleared through browser settings. After clearing, you will need to sign in again and the interface language returns to its default; purchased plans and order records are unaffected.
5. Payments and Third-Party Processing
The service supports three payment methods: Alipay, WeChat and USDT. Payment is completed by the respective provider; the service never touches or stores card numbers, payment passwords or full payment credentials. The provider returns only the order number, amount, payment status and the necessary transaction reference, which are used to confirm receipt and activate the plan.
USDT payments are made as on-chain transfers; the service records only the transaction hash and the amount received, in order to confirm the order. On-chain records are publicly visible, and this data is not controlled by the service.
Refunds are returned through the original payment channel, and the time to arrive is set by that channel. For refund rules, see the 7-day no-questions-asked refund section in the Terms of Use.
6. Data Retention, Deletion and Policy Updates
Retention periods for each type of data are as follows.
- Account information and order records: kept for as long as the account exists; deleted or anonymized within 30 days after a closure request is processed, except for the parts that laws and regulations require to be retained.
- Ticket content: kept for 12 months after the ticket is closed, so similar faults can be reviewed.
- Visit statistics: aggregated data with no personal identifiers, which may be kept long term.
- Connection logs: never generated, so there is no retention period.
How to delete: open a ticket in the user panel stating which data should be deleted; the service will act after verifying account ownership. Account deletion is irreversible — plans and data-pack balances in the account lapse at the same time, so please confirm before submitting.
Policy updates: if this policy changes, the "Last updated" date on this page will be revised and a notice posted in the user panel. Changes that expand the scope of collection or alter its purpose will be explained before they take effect; continuing to use the service after a change takes effect means you accept the updated version.
If you have questions about this policy, or need to access, correct or delete account data, submit them via a ticket in the user panel; the service will reply after verifying account ownership.