Legal

Privacy Policy

This policy explains what user-related data VPNYN processes when providing its cross-border network acceleration subscription service, why it is processed, how long it is kept, and how users can access or delete it.

Last updated: 2026-09

1. What data we collect, and why

Registration asks only for a username and password; no email address or other identity information is collected. The username is used for sign-in, for linking orders to an account and for identifying you in support tickets; the password is stored as an irreversible hash, and the service never keeps it in plain text.

Order records include the plan name, amount, payment method, order time and activation time. These records are used to activate plans, calculate remaining data allowance, process refunds and reconcile accounts, and they are the receipt that both payer and payee need to keep.

Visit statistics record aggregate information such as page views, referral source, device type and approximate region, used to judge which content is useful to visitors and which pages need improvement. Statistics are self-hosted on this site and are not shared with third-party ad platforms.

2. Our no-logs stance: we do not record the websites you visit

We do not record which websites you visit, we do not store any link between a destination and an account, and connection logs are not retained.

The service does not keep connection logs built from connection time, exit region and destination, and it does not use browsing records for statistics, profiling or disclosure to third parties.

Route status is measured as aggregate metrics, such as the overall latency and bandwidth load of a given route, to decide whether capacity needs expanding or configuration needs adjusting. These metrics contain no account identifiers and cannot be traced back to what any individual user accessed.

To troubleshoot a single route being down or a client failing to connect, engineers may review server-side operational logs, which contain only the route ID, error code and timestamp — never the destination.

3. How we use cookies and local storage

This site does not serve third-party ads and does not use advertising tracking cookies.

Browser local storage (localStorage) holds two kinds of content: sign-in credentials, so you do not have to log in again while they are valid, and your language preference, so your next visit opens directly in the matching language version.

Visit statistics use a first-party cookie to distinguish sessions; they count only pages and referrers, do no cross-site tracking and are not used for profiling. After clearing browser cookies and local storage you will need to sign in again, and the language preference returns to its default value.

4. Payments are handled by third-party providers

Payments are completed through Alipay, WeChat or USDT. Card numbers, payment passwords and identity details are handled by the relevant payment provider on its own pages; this service neither accesses nor stores them.

Once payment is complete, the service receives only the order number, amount, payment status and payment time, used to activate the plan, record the order and reconcile accounts; for USDT payments, the on-chain transaction hash is also recorded to confirm receipt.

Refunds follow the order record: a full refund can be requested without giving a reason within 7 days of the first payment.

5. How long data is kept and how to delete it

Account information is retained until the account is closed. Order and payment records are kept for as long as the account exists, for reconciliation, refund checks and dispute handling; after the account is closed, nothing is retained except what is needed to complete a refund or resolve a dispute.

How to delete: sign in and open a ticket in the user panel, stating the username to be closed. Once closed, the account cannot be restored, and the sign-in credentials and language preference linked to it are erased as well.

If you need to check an order or request a refund, do so before submitting the account closure request.

6. How this policy is updated

This policy is updated as the service changes and legal requirements evolve. The updated version is published on this page, and the last-updated date at the top is changed at the same time.

Where a change materially affects how data is used, the key points will be explained prominently on this page. Continuing to use the service means you accept the updated policy.

If you have questions about this policy, or need to access or correct the data in your account, use the same ticket entry point in the user panel.

Start Free