Last updated: October 2026
Refund Policy
This policy explains the refund scope, request process, and payment handling principles for CPUVPN subscription services. Payment orders in your account are used to verify requests. To check an order’s status, sign in to the user panel and submit a support ticket.
Refund Window and Eligibility
You may request a full refund for any reason within 60 days of your first payment.The request window starts when your first payment is successfully processed; payment records and ticket submission records are used for verification. You do not need to explain why you no longer use the service or complete connection troubleshooting first.
Refund requests for monthly subscriptions and data plans are handled through support tickets. List the order or orders you want refunded. Later payments, plan upgrades, or additional data plans do not restart the refund window tied to your first payment. If you have multiple orders, each payment record must be checked separately to avoid treating different orders as one.
The data plan description “use it until it is gone; it never expires” refers to the validity of the data, not to a refund window that remains open indefinitely. Requests made after the window above are not covered by the no-questions-asked full-refund policy. You may still submit a specific issue for review.
Data Usage and Unusual Orders
Normal use of routes, importing a subscription, or downloading a client does not change the refund commitment above. This policy does not impose a threshold based on the proportion of data used, nor does eligibility for a no-questions-asked refund depend on whether a connection issue can be reproduced.
If your data usage appears to exceed your plan allowance, first check the billing records, reset status, and related orders. If you notice a discrepancy or unusual usage, explain it in a support ticket. “Data usage exceeded” alone is not grounds for automatically denying a refund, and no deduction amount should be estimated on that basis.
Orders involving policy violations, disputes over payment ownership, repeated refund requests, or payment reversals must be reviewed against the terms of service and transaction records. An account restriction does not automatically invalidate a refund request. If a request cannot be handled under this policy, the specific facts and reasons must be explained in the support ticket; a vague statement such as “account irregularity” is not a sufficient conclusion. Amounts already refunded will not be refunded again.
How to Request a Refund
- Sign in to the user panel, open the support ticket page, request a refund, and list the relevant order or orders.
- Provide the order number, payment date and time, payment method, and amount paid. If an order cannot be matched, you may provide a redacted payment receipt, keeping only the information needed to verify the transaction.
- Check replies and provide any additional information in the original ticket. Confirm which service the refund covers and the outcome. There is no need to create multiple tickets for the same request.
Do not submit your login password, payment password, wallet private key, or recovery phrase. The first ticket records the request date; providing additional information for verification should not be treated as submitting a new request. If you cannot sign in, first use the account help option provided in the panel. Account verification is still based on order ownership.
Refunds to the Original Payment Method
Refunds are generally returned through the original payment method. Alipay and WeChat Pay orders are refunded through the original transaction. The payment provider handles which account receives the funds and how the credit appears. Do not request a refund to an account unrelated to the original payment.
USDT transfers are handled differently from Alipay and WeChat Pay and cannot use the same transaction-reversal process. A support ticket is required to verify the original payment record, network used, and receiving address before confirming a workable return method. Do not act solely on an address-change instruction sent in a chat.
If network fees, exchange rates, or payment provider restrictions are involved, the specific circumstances should be explained and confirmed first. No fixed fee deduction should be assumed, and the full-refund commitment should not be reduced unilaterally. If the original payment method cannot be used, explain why in the support ticket before agreeing on an alternative that can be verified.
Refund Status and Service Settlement
A refund request, order verification, refund initiation, and receipt of funds are separate stages. The time it takes to receive a refund depends on the payment provider’s processing and the transaction status; this policy does not guarantee a standard processing time. Submitting a ticket or receiving an acknowledgment does not mean the refund has been credited.
After a refund is initiated, check the statement for the original payment method. For a USDT return, check the transaction status on the network confirmed for the refund. If the funds have not arrived, follow up in the original ticket for a status update and verifiable refund documentation. This helps prevent confusion caused by duplicate requests.
Once a refund is completed, the service benefits associated with that order should be settled accordingly, and the specific scope of any service suspension will be explained during processing. Other orders should be reviewed separately; a refund for one order does not automatically mean all services have ended. For related rules, see the Terms of Service and Privacy Policy.