Refund Policy

Usage Records and Unusual Orders

Normal connections, switching international routes, or using plan data do not require you to explain your reason for requesting a refund. This policy sets no undisclosed threshold for the proportion of data used, and partial data usage does not automatically result in a prorated refund.

Orders outside the request window are not covered by the full-refund commitment described above. Amounts already returned will not be refunded again; orders that have not actually been paid have no payment amount to return. If an order involves unusual activity beyond the plan allowance, a payment dispute, or an account violation, the transaction and terms of service must be reviewed first. An unusual-activity label alone is not grounds for a conclusion.

If additional information is needed, the support ticket should specify what is required and why. Account enforcement and refund verification must be explained separately; a vague violation notice cannot replace an order decision. If you disagree with the outcome, you can add information to the original ticket.

How to Request a Refund

Sign in to the user panel support ticket page, state that you are requesting a refund, and provide your order number, plan name, payment method, and payment date and time. If your payment succeeded but does not appear in the panel, attach proof of payment and the transaction ID so the actual payment record can be checked.

No email address is required; you can create an account with a username and password. Continue refund discussions in the support ticket. Do not submit your login password, full payment account credentials, or wallet private keys. You may redact information unrelated to verification in screenshots, but leave the transaction amount, status, and identifiable order details visible.

For upgrades or multiple payments, explain how they relate to one another. The price difference for a mid-term upgrade is converted into remaining days, so verification must take the order details into account. Do not estimate the refund based only on the current listed plan price. The decision, refund amount, and any changes to service entitlements should be clearly stated in the support ticket.

Return Methods and Payment Differences

Payments made through Alipay or WeChat Pay are generally returned through the original transaction route. The payment provider's records determine how the return appears. If the original route cannot be used, explain the reason in your support ticket and confirm the handling method first. You will not be asked to make another payment to complete a refund.

USDT refunds require separate verification of the original transaction, transfer network, and receiving address. The Alipay or WeChat Pay return process does not apply. Confirm the receiving details and return arrangements in your support ticket before proceeding; do not send additional assets to any address before confirmation. A refund must not be treated as payment for a new plan.

Progress and Payment Verification

Request received, information verified, refund initiated, and funds received are separate statuses. The time it takes for funds to arrive depends on the payment provider and transaction confirmation. This policy does not promise a fixed arrival time that has not been confirmed. If information is missing, the transaction status is unclear, or the return route has an issue, state what needs to be checked in your support ticket.

After receiving confirmation that a refund has been initiated, check your payment provider's statement. If the funds have not arrived, follow up in the original ticket and include your order number to avoid fragmenting the records with duplicate requests. The Terms of Service also apply; information submitted with a request is handled according to the Privacy Policy.