Refund Policy

Refund Window and Eligibility

You can request a no-questions-asked full refund within 30 days of your first payment. The window starts at the time of your account's first successful payment and is verified against the time you submit a refund ticket. You do not need to provide proof of network issues, and troubleshooting routes first is not a condition for your request to be accepted.

Refunds are processed against the actual payment order, not the price displayed for a plan. Renewals, upgrades, and separately purchased data packages do not restart the first-payment refund window. If your request concerns multiple orders, list each one separately so the amounts and processing scope can be checked. The fact that a data package never expires is a usage-period rule; it does not extend the refund window indefinitely.

What Is and Is Not Covered

Within the window above, requests related to connection quality, device compatibility, route selection, or a change in personal needs are covered by the no-questions-asked refund commitment. Importing a subscription, connecting to a route, or using some of your data does not by itself invalidate this commitment. This policy does not impose any unpublished data-usage ratio or overage deduction threshold.

Orders outside the application window are not covered by this no-questions-asked refund commitment. Unpaid, failed-payment, or already-refunded orders have no completed payment amount to refund again. Suspected payment-account misuse, forged records, or prohibited use may require verification of order ownership and related records. An account restriction does not determine the refund outcome; the basis and result of the review should be explained in the ticket, rather than replaced with a vague label of misconduct.

How to Apply and What to Provide

Log in to the user panel and submit a refund request through the ticket page, specifying the order you want refunded. No email address is required; the application and follow-up communication take place in your account. Keep the ticket record and add any further materials to the original ticket to avoid scattering information across duplicate requests.

Details used for verification include your account username, order number, payment time, actual amount paid, and payment method. If the order status does not match the payment record, you can provide proof of payment and redact personal information that is not needed for verification. Do not submit your account password, payment password, wallet private key, or recovery phrase. If you are asked for additional materials, first confirm that they relate to the order in question.

After submitting your request, check the ticket reply to confirm acceptance, the order or orders covered by the refund, and how the corresponding plan and subscription access will be handled. Once the refund is complete, the related service benefits will be adjusted accordingly. Check the order and ticket records for details.

Refund Route and Processing Status

Refunds are generally returned to the original payment account through the original payment channel. Acceptance, initiation of the refund, and receipt of funds are separate steps. A processing status shown in the user panel should not be taken to mean that the funds have already arrived. The time it takes depends on the payment channel and the status of the receiving account; this policy does not promise a single processing time.

If the original channel cannot return the funds or the original payment account cannot receive them, explain the situation in the original ticket. Any alternative handling requires verification of account ownership and explicit confirmation; funds should not be sent directly to an unrelated account. When checking progress, provide the original order and refund records so that service-side processing can be distinguished from the payment channel's posting status.

Payment Methods and Follow-Up

This service supports Alipay / WeChat Pay / USDT. Refunds for Alipay and WeChat Pay are generally processed through the original transaction route. Check the refund record in the relevant payment app. If the payment receipt and order amount do not match, first verify that they relate to the same transaction.

A USDT transfer cannot be reversed in the same way as a payment in a standard payment app. Before a refund, confirm the original transaction record, receiving network, address, and refund amount basis in the ticket. If exchange rates or network fees are involved, they must be explained and confirmed in advance; deductions that have not been explained should not be assumed. Check each receiving detail before confirming the transfer arrangements.

If you have questions about the outcome, specify the order or record you would like reviewed in the original ticket. For other account and service rules, see the Privacy Policy and Terms of Service. Refund matters are handled according to the commitments on this page and verifiable transaction records.