Privacy Policy

Last updated: 9/2026

This page explains how the VPNOh cross-border network acceleration subscription service handles registration, subscription and access data: what is collected, why, how long it is kept, and how users can review or delete it. Registration does not require an email address, and no browsing content is logged on the network side — these two points are the core of this policy, and the sections below set out the exact scope and limits.

Scope of This Policy

This policy covers every page under the vpnoh.com domain, along with the registration, subscription, ordering and subscription-retrieval flows in the user panel. Payment channels, app distribution platforms and operating systems handle data in their own environments under their own privacy rules, which this policy does not cover.

What Data Is Collected and Why

• Account data: registration requires only a username and password, with no email address. The account record stores the username, an encrypted password, the registration time and account status, used for login verification and subscription ownership.
• Order and subscription data: plan type, amount, payment channel, order time and expiry time, used to activate subscriptions, calculate remaining traffic, and process upgrades and refunds. Monthly plan traffic resets each month on the activation date; data packs last until they are used up and never expire, and the metering rules are likewise driven by order records.
• Usage data: aggregated traffic consumption per account across each route, used for plan metering and route capacity planning. Usage is aggregated by account and is not linked to any specific destination.
• Visit analytics: aggregate metrics such as page views, referral sources, browser and device types, used to judge which content is useful to users. Both the analytics script and the analytics data are hosted on this site's own domain and maintained by the service itself.

No-Logs Stance and Connection Records

This service does not record which websites users visit. The network side stores no destination domains, full URLs or DNS query contents, and no session details for individual connections; once a connection ends, that information is no longer retained.

For billing and troubleshooting, the account side keeps only the records it needs: aggregated traffic usage per route, subscription status and expiry time, and order and refund transactions. These records are used to determine remaining plan traffic, identify route issues and reconcile bills, and are kept for as long as the account remains active.

Cookies and Local Storage

This site uses browser cookies and local storage for three purposes:

• Keeping you signed in: the user panel stores login credentials locally in the browser, so refreshing or reopening the page does not require signing in again; clearing browser data signs you out, and signing in again restores access.
• Remembering preferences: interface preferences such as language choice are stored locally, so your next visit opens directly in the matching language version.
• Visit analytics: the analytics script writes a small identifier used to distinguish unique visitors and count page views and referral sources; measurement is limited to this site's pages and results are used in aggregate.

All of this local data can be cleared at any time through your browser settings, and clearing it does not affect purchased plans or subscription status.

Payments and Third-Party Processing

Subscription payments are made via Alipay, WeChat and USDT, and each payment channel processes its part of the transaction under its own privacy rules. This site never touches or stores card numbers, payment passwords or wallet private keys; the order record holds only the amount, payment channel, order time and payment result status, used to activate subscriptions and reconcile bills.

Refunds follow the 14-day no-questions-asked policy. Processing a refund requires reading the original order's payment channel and amount, and the related records are kept until the refund process is complete, after which they are handled under the retention periods in the next section.

Data Retention, Deletion and Policy Updates

Account data and order data are kept for as long as the account exists. After an account is closed, all remaining data is deleted or anonymized and no longer used for any business purpose, except for transaction records still in the refund process or required to be kept by law.

How to delete: submit a deletion request through the ticket entry in the user panel and state which account should be processed. Once that is done, the username and its records can no longer be used to sign in, and the subscription and traffic balance are voided at the same time.

Policy updates: if this policy changes, the content of this page and the “Last updated” date at the top will be revised; major changes affecting the scope or purpose of data handling will be flagged prominently on the site.

To review, correct or delete your account data, or if you have questions about this policy, submit a request through the ticket entry in the user panel; tickets keep a complete record of how the request was handled.