Privacy Policy

This page explains what data C6VPN (referred to below as the Service) processes while providing its cross-border network acceleration subscription, why it processes that data, how long it is kept, and how users can access or delete it. This policy covers the information pages and user panel at c6vpn.com; it does not apply to third-party sites reached through the Service, which have their own privacy terms.

1. Data collection and use

Account and login. Creating an account only requires a username and password; the sign-up flow does not ask for an email address. Passwords are stored as irreversible hashes — the Service never keeps plaintext passwords and cannot recover the original from the hash.

Subscriptions and orders. When a subscription starts, the plan tier, order time, payment status and payment channel (Alipay / WeChat / USDT) are recorded. These records are used to activate routes, calculate remaining traffic, prorate mid-term upgrades, and process the 30-day no-questions-asked refund.

Usage records. The system tracks traffic used and current active sessions per account to show the remaining plan allowance and manage concurrent connections. There is no limit on simultaneous devices; only connection counts are measured, with no device model or device identifier involved.

Visit statistics. The information pages record aggregate data such as page views, referring page, browser type and screen size, used to judge whether page structure and content need adjusting. These statistics are not linked to any specific account.

This data is used only to deliver the service, bill for it, troubleshoot problems and protect against abuse. It is never sold, rented or used for cross-site advertising.

2. Anonymous no-logs handling of connection data

The Service follows an anonymous no-logs policy:

• No record is kept of which websites a user visits, no DNS query content is logged, and no copies of transmitted content are stored.
• Traffic patterns are not analysed to build user profiles or target advertising.
• On the route side, only the minimum state needed to keep a connection alive is maintained: the access route, session start and end times, and traffic counters.

Once a session ends, the route side no longer retains the original records of that connection; only the traffic counters are rolled up into the account usage record for billing and remaining-allowance display. What remains on the account is how much was used, not where the user went.

To keep routes available and counter abuse, the system counts connection attempts and total traffic per account. These are counts only and do not involve destinations.

3. Cookies and local storage

The information pages carry no third-party advertising and load no cross-site tracking scripts.

Local storage. The user panel keeps login credentials in the browser local storage so a refresh or a later visit stays signed in. Language preference is stored locally too, so the matching language version loads directly. Clearing browser data removes both, and the user will need to sign in again.

Cookies. Used only to maintain the basic state of the current visit and for security checks, never to record which websites have been visited. Cookies can be cleared or refused at any time in browser settings; refusing them will affect features such as staying signed in.

The site does not use cookies or local storage to hold payment credentials.

4. Third-party processing in payments

Payments are completed through Alipay, WeChat or USDT. The payment itself is handled by the relevant payment provider; account credentials and payment passwords never pass through the Service servers. The Service receives only the payment result and order number, used to activate the subscription and reconcile accounts.

Servers, bandwidth and content delivery are provided by infrastructure providers. In supplying compute and network resources, providers may have access to device-level access records, and their handling is governed by their own privacy terms.

Account data is not shared with third parties except where required by law, needed to resolve a payment dispute, or explicitly authorised by the user.

5. Data retention and deletion

Account data is kept for as long as the account exists. Order and traffic records are tied to billing, upgrade proration and refunds, so they are retained after a subscription ends until the refund window closes.

Closure and deletion. A deletion request for the account and related data can be submitted by opening a ticket in the user panel. Account status is checked first to avoid accidental deletion; once deletion is complete the account cannot be restored, order records already created are kept until the statutory period expires, and all other data is deleted or anonymised.

Access and correction. Users can view their orders and usage records in the user panel at any time; if something looks wrong, a ticket can be opened to request a correction.

6. Policy updates and how to get in touch

When the policy changes materially, the Last updated date at the top of this page is revised and the key changes are described in the user panel. Continuing to use the service after a change takes effect means accepting the updated policy.

Privacy-related access, deletion and correction requests are all submitted through tickets in the user panel, which makes it easier to verify the account and keep a record of the request.