Last updated: October 2026 (10/2026)

Privacy Policy

This policy applies to the cross-border network acceleration subscription service provided by VPNEH. It explains what data is collected, why, how long it is kept, and how users can review and delete it.

In one sentence: an account needs only a username and password — no email address; billing uses plan tier and traffic usage only; we do not log which websites you visit.

Scope

This policy explains what data VPNEH (hereafter the Service) collects when providing its cross-border network acceleration subscription service, why it is collected, how long it is kept, and how users can review and delete it. It applies to the information pages and user panel at vpneh.com. If you do not agree with any part of it, please stop using the Service; the Service offers a 14-day refund, no questions asked.

The Data We Collect and Why

  • Account data: signing up requires only a username and password — no email address. Passwords are stored as an irreversible hash; the Service never stores plaintext passwords.
  • Order and billing data: plan tier (¥9.9/month for 60GB, ¥18/month for 250GB, ¥28/month for 500GB, or data packs of ¥158/300GB, ¥358/1000GB and ¥658/3000GB), payment method (Alipay / WeChat / USDT), order number, activation date, expiry date and remaining traffic. This is used to activate the service, reset traffic on the activation date, and handle plan upgrades and refunds.
  • Connection metadata: connection time, the route selected, and upload/download usage for each session. This is used to meter traffic and troubleshoot route faults; it does not involve the content of your traffic.
  • Visit statistics: aggregate data on page views, referrers and device types. This is used to decide which documentation needs expanding and whether page structure is clear.

No-Logs Stance

The Service does not record which websites users visit. Domain names and URLs, DNS query contents and transmitted content all fall outside the scope of what is recorded, and traffic is never subject to content inspection or behavioural profiling.

Connection metadata is kept only until billing and reconciliation for the current period are complete, after which it is aggregated into usage statistics that cannot be traced back to an individual session; no records that could be linked to specific browsing behaviour are retained. Upstream route and data centre providers receive only the operational information needed to keep routes running, never users' browsing records.

Cookies and Local Storage

The site uses cookies to keep login sessions alive and browser local storage to hold the login token and language preference. Both live in the user's own browser and can be removed by clearing browser data — the only cost being that you will need to log in again. The site uses no third-party advertising or cross-site tracking cookies, and never uses local storage contents for ad targeting.

Payments and Third-Party Processing

Payments are handled by third-party channels: Alipay, WeChat and USDT each process payment through their own flow. Card numbers, payment passwords and wallet private keys are always handled on the payment channel's side and never pass through the Service; the Service receives only the order number and payment status returned by the channel, used to activate plans and reconcile accounts.

Apart from payment channels and route providers, data is not sold or given to third parties unrelated to delivering the service. Order records are disclosed only within the scope required, and only in response to a formal request with legal force.

Data Retention, Deletion and Policy Updates

Account data is retained for as long as the account exists. Order and payment records must be kept for a period after account closure to meet payment channel and tax requirements; all other data is deleted once the closure process is complete.

Users can review orders, usage and subscription status in the user panel at any time. To export or delete data, or to close an account, submit a request through the ticket entry in the user panel; a reply follows once it has been processed.

When this policy changes, this page is updated directly and the last-updated date at the top of the page is changed with it. Material changes to how data is used are also announced in the user panel.