Refund Policy

Eligibility and Refund Window

You may request a full refund within 14 days of your first payment. The window is based on the record of your first successfully paid order. Eligibility is determined by the time your refund ticket is submitted. You do not need to provide proof of connection failure or complete troubleshooting before requesting a refund.

Monthly subscriptions and data packages are both eligible for requests under this policy. Specify the order you want reviewed. Renewals, upgrades, and additional data packages do not restart the first-payment window. If your request involves multiple payments, list each one separately so support can verify how each order relates to the request and avoid treating separate transactions as one refund.

Usage Records and Order Concerns

Connecting normally, importing a subscription, or using package data does not by itself mean you have given up your right to request a refund within the window. This policy does not apply an undisclosed data deduction rate or require a particular reason, such as dissatisfaction with the service, to submit a request.

Orders outside the refund window are not covered by the full-refund guarantee described above, but you may submit a ticket explaining the issue. In cases involving repeated refund requests, payment disputes, suspected unauthorized payments, or accounts that may have violated the Terms of Service, we need to verify order ownership and related records first. Raising a question about a possible violation does not, by itself, mean a refund has been denied.

If usage records appear to exceed a package limit, verify the usage measurement and order status first. An unconfirmed “overuse” claim will not be used as a basis for a charge. The same order will not be refunded twice; if the payment is still being processed by the payment provider, its final status must be confirmed first.

How to Request a Refund

1. Sign in to the user panel, open the support ticket page, write “Refund request,” and list the relevant orders.
2. Provide the order number, package name, payment date and time, amount paid, and payment method. If payment succeeded but the order is not shown in the panel, you may attach transaction proof to help us match it.
3. Check the verification result in the original ticket and provide any necessary information requested by support. If connection troubleshooting is needed, you may describe your setup, but this is not a prerequisite for requests submitted within the refund window.

Before submitting proof, cover unrelated transactions and personal information. Do not send your account password, subscription URL, wallet private key, or recovery phrase. Registration does not require an email address, and refund communication takes place through support tickets in the panel, so keep access to your account.

Refund Methods and Payment Differences

Supported payment methods are Alipay / WeChat Pay / USDT. Alipay and WeChat Pay transactions are generally returned through the original payment channel, subject to support confirming that the original transaction can be refunded. If a refund through the original channel is not available, explain why in the ticket and confirm the next steps. You will not be asked to send a separate payment to an unfamiliar account to complete a refund.

USDT refunds involve an on-chain transfer. Before processing, the original transaction, network, and receiving address must be verified; this is not the same as reversing an Alipay or WeChat Pay transaction through its original channel. Confirm the refund amount, network, and any potential network fees in the ticket before the transfer is made. Do not assume the network matches based on the address format alone.

Refund Status and Service Handling

Reviewing a request, completing verification, initiating a refund, and receiving the funds are separate steps. The time it takes to receive funds depends on the payment provider or on-chain confirmations, so this policy does not guarantee a fixed settlement time. Support should explain the current stage in your ticket. After receiving a refund notification, check the original payment statement or on-chain records.

If the funds have not arrived, add the latest status to the original ticket to keep the record in one place. The result should also explain how package benefits and remaining data are handled when a refund is issued. A refunded order can no longer serve as the payment basis for continued access to the related service. If you disagree with the outcome, ask support to explain the basis for its review and provide any additional information in the same ticket.