Refund Policy

Request Window and Refund Scope

You can request a no-questions-asked full refund within 30 days of your first payment. You do not need to provide proof of a service issue or show that you were unable to connect. Submit a ticket within the window and keep a record of it. Use the same ticket to provide any follow-up details and check progress.

The refund window is based on the first successful payment, not the date you created an account, downloaded a client, or first connected. Monthly subscriptions and data packages use different billing methods, but the fact that data packages never expire does not mean the refund window remains open indefinitely. A renewal, additional data package, or upgrade does not automatically restart the first-payment window.

Eligibility and Order Review

Requests made within the window may be based on changing needs, device compatibility, or the access experience, and you may also choose not to give a reason. Normal connection and use alone are not grounds to deny a no-questions-asked refund. This policy does not introduce unpublished data-use thresholds or deduction formulas.

Orders outside the window are not eligible for the no-questions-asked full-refund commitment described above. Payment issues such as duplicate charges or a successful payment that is not reflected in the corresponding order can still be submitted for review; these should not be treated as ordinary refund requests. No payment return is needed for an order that was never successfully paid.

If records show unusual data usage, usage beyond the purchased allowance, or suspected violations of the terms of use, the order and relevant records must first be reviewed. An alert is not a final decision. If it affects a refund, support should explain the specific grounds in the ticket rather than giving only a vague statement that the service was used.

How to Apply and Required Details

Sign in to the user panel, open the support ticket page, state that you are requesting a refund, and provide the relevant order number, payment method, payment date, and amount paid. If you have multiple orders, identify the specific order for review so separate payments are not grouped together.

If you need to provide a payment screenshot, keep the transaction reference and information that matches it to the order, and redact unrelated personal details. Do not submit your account password, payment password, verification codes, or wallet private keys. No email address is required for an account; you can create one with a username and password. Check refund progress in the user panel.

Support will check the payment status, request date, and order ownership, then reply in the ticket with the result or any details still needed. If you cannot sign in for now, use the panel’s sign-in entry point to resolve account-access issues. Do not send account credentials through channels other than a support ticket.

Return Methods and Payment Differences

Payments made through Alipay or WeChat Pay are generally returned through the refund channel for the original transaction. The destination where funds appear depends on the payment channel and original payment source, so check the original transaction record. If the original channel has an issue, first confirm the reason and available options in a support ticket before agreeing on next steps.

USDT returns are handled differently from Alipay and WeChat Pay and should not be assumed to be automatically sent back through the original transaction. The receiving network, address, and amount must be checked and confirmed individually in a support ticket. Do not assume the original sending address can receive a refund or send funds to an address that has not been verified.

No standard on-chain fee or conversion rule is specified in the available information, so this policy does not promise a particular deduction. If a refund involves a difference, the grounds must be explained and confirmed first; an unexplained deduction cannot replace the full-refund commitment.

Checking Refund Status and Next Steps

Submitting a request, confirming a refund, and receiving the funds are separate stages. Progress depends on the payment channel, transaction status, and any necessary checks. No standard arrival timeframe is specified; refer to the ticket record and the payment channel’s result. If funds have not arrived, follow up in the original ticket to avoid splitting the records across duplicate requests.

When a refund is confirmed, the status of the order benefits, subscription availability, and any arrangements for future use should also be explained. If you disagree with the outcome, list the order and specific issue to be reviewed in the original ticket. See the Terms of Use for other service terms and the Privacy Policy for information about data handling.