Legal

Privacy Policy

Last updated: 10/2026

This policy explains which user-related data VPNYF processes while providing its cross-border network acceleration subscription service, why it is processed, how long it is kept, and how users can access, correct and delete it.

What Data Is Collected and Why

The service collects data only to the extent needed to open an account, bill it and provide support, and never asks users to supply personal information unrelated to the service.

  • Account details: signing up requires only a username and password, with no email address. Passwords are stored as irreversible hashes, and no support process will ever ask for a plaintext password.
  • Order and subscription status: the plan purchased (¥9.9/month for 60GB, ¥18/month for 250GB, ¥28/month for 500GB, or data packs of ¥158/300GB, ¥358/1000GB and ¥658/3000GB), activation and expiry dates, and traffic used in the current period. This is used for billing, monthly traffic resets on the activation date, prorated mid-term upgrades and support verification.
  • Ticket content: the problem description, screenshots and optional contact details a user submits, used only to handle that request.
  • Visit statistics: page views, referral source, device type, coarse region and browser language. Used to judge which guides need expanding and which pages load slowly.
  • Payment results: order number, amount, payment channel and payment status, returned by the payment provider's callback. The service neither receives nor stores card numbers, payment passwords or wallet private keys.

How Connection Logs Are Handled

How connection logs are handled is the core clause of this policy: no records are kept of the websites visited, DNS queries made or content transferred while a subscription connection is active.

The service does not build user profiles from browsing behaviour, and does not use connection records for ad targeting or pass them to third parties.

To keep connections up and troubleshoot faults, the network side holds a small amount of session-level technical data, such as the current number of concurrent connections, the selected route and the connection start time. After a session ends this data is not archived as history searchable by account; route statistics are kept in aggregate form for capacity planning and fault isolation, and are not linked to any specific account identity.

Subscription connections use quantum encryption, negotiated between the client and the route; the service holds no decryption material for user devices.

Cookies and Local Storage

The site uses cookies and browser local storage to keep three kinds of information:

  • Language preference: remembers the interface language last chosen, so it does not have to be picked again on every visit.
  • Sign-in state: the user panel's login token is kept in browser local storage so users do not have to sign in repeatedly; it stops working after signing out or clearing browser data.
  • Visit statistics: an anonymous identifier that contains no account identity, used to tell unique visitors apart and count page views.

This information is not used for cross-site advertising and is not shared with ad networks. Users can clear it at any time in their browser settings; after clearing, they will need to sign in again or reselect a language.

Third-Party Payment Processing

The site supports three payment methods: Alipay, WeChat and USDT. Payment is completed on the relevant channel's page or on-chain, and payment account details are handled by that channel under its own privacy policy; the service receives only three results: whether payment succeeded, the order amount and the order number.

For USDT transfers, only the on-chain transaction hash and confirmation status are recorded; wallet private keys, seed phrases and exchange account credentials are never involved. Under no circumstances will support ask for that information.

Data Retention Periods and How to Delete

Different categories of data are kept under different rules:

  • Account details: kept for as long as the account exists; deletion begins once the account is closed.
  • Order and payment records: kept for the period required for reconciliation and tax compliance, then deleted or irreversibly anonymised.
  • Ticket records: deleted once the request is resolved and the period needed for follow-up has passed.
  • Visit statistics: only aggregated results are kept; raw detail is cleared periodically.

How to delete: sign in to the user panel and open a ticket stating that the account should be closed or specific data removed. The request is carried out after account ownership is verified, and deletion cannot be undone; beforehand, you can ask for an export of the orders and subscription records in the account. If the account still holds an unexpired subscription or unused data pack, read the refund policy before deciding to close it.

Policy Updates and Contact

When the policy changes, the last-updated date at the top of the page changes with it. Adjustments that materially change the scope of data processing are announced in the user panel; continuing to use the service after a change takes effect means accepting the updated terms.

For queries, corrections and deletion requests relating to this policy, use the ticket entry in the user panel: Submit a ticket. Include the username and the specific request so the account can be located.

This policy, together with the Terms of Service and the Refund Policy, forms the terms framework for the service.

Start Free Trial