Refund Policy

Application Window and Refund Scope

You may request a full refund for any reason within 30 days of your first payment. The window starts at the time of your first successful payment and is checked against the time your refund ticket is submitted. You do not need to provide evidence of connection issues, speed tests, or other dissatisfaction. Simply state that you are requesting a refund and provide order details that can be verified.

This commitment starts with your first payment. Later renewals, additional data packages, or mid-term upgrades do not restart the application window. If your request involves multiple orders, list each one in the ticket so support can clarify which orders are eligible. Do not assume that all historical payments on your account will be treated as a single refund.

Eligibility and Verification Limits

Anyone within the application window may request a refund because of changing needs, changes in device arrangements, or an experience that did not meet expectations. Normal connections and data usage are not grounds for denying a full refund under this policy. There is no data-usage percentage threshold, and eligible refund amounts are not reduced based on data already used.

Orders outside the application window are not covered by the full-refund commitment above. Disputes involving excessive data usage, unclear order ownership, repeated refund records, or suspected violations of the Terms of Use require a review of the relevant orders and records. A review does not automatically mean a refund will be denied. If this commitment does not apply, the specific reason must be explained in the ticket rather than replaced with a general reference to account status.

How to Apply and What to Provide

Sign in to the user panel and submit your request on the support ticket page. Include the order number, package name, payment method, payment time, and amount paid. If you cannot find the order number, provide transaction details from your payment receipt that can help verify the payment, and hide personal information unrelated to this order.

Do not include your account password, payment password, private key, or account recovery information in the ticket. If support needs additional details, reply in the original ticket to keep the conversation in one record. No email address is required; sign in with your username and password to manage your account and request.

Once verification is complete, the ticket will explain the outcome and refund scope. It will also clarify how the service benefits covered by the refund will end. Save any order records you need to keep before confirming.

Refund Destination and Processing Status

Refunds are generally returned to the original payment method. Alipay and WeChat Pay orders are refunded through the original transaction where possible. The account where the funds appear and how the transaction is displayed depend on the payment provider's records. Acknowledgment of your request, submission of the refund, and receipt of the funds are separate steps; confirmation that your request has been accepted does not mean the funds have arrived.

Processing time depends on order verification, the payment provider, and the status of the receiving account. This policy does not guarantee a fixed arrival time. If the funds have not arrived after the refund is submitted, request a review in the original ticket and provide the transaction status shown by your payment provider. If the original payment method cannot accept the refund, confirm the reason and available options in the ticket first. Do not redirect the refund to an unrelated account without approval.

USDT and Special Transactions

USDT payments cannot use the same direct refund process as Alipay or WeChat Pay transactions. Include the original payment record with your request. Before a refund is made, confirm the receiving address, network, and refund amount through the support ticket. Do not post wallet details on public pages or transfer funds to external accounts claiming to process refunds.

Different networks, transfer costs, and changes in token value may affect how a refund is handled. The exact amount and method must be explained and confirmed before processing; no unpublished fee deductions are assumed. Orders with payments still processing, duplicate payments, or active disputes through a payment provider must first be checked against the payment status to avoid duplicate refunds. For information about how personal data related to refunds is handled, see the Privacy Policy.