Refund Policy

Refund window and scope

The refund window is 60 days, counted from the date your first payment succeeds and based on the payment time recorded in your user panel order history. Requests submitted inside the window are handled under the rules on this page; orders past the window are no longer eligible for a refund.

This policy covers two kinds of paid items:

• Monthly plans: ¥9.9/month for 60GB, ¥18/month for 250GB, ¥28/month for 500GB. Data resets every month on the activation date, and any price difference from a mid-cycle upgrade is prorated by remaining days.
• Data plans: ¥158/300GB, ¥358/1000GB, ¥658/3000GB — good until used up, with no expiry.

Both kinds of item share the same refund window. If one order contains both a monthly plan and a data plan, submit the request for the order as a whole; it is not split.

Cases where a refund is available

• Orders submitted within 60 days of the first payment can be refunded in full, no questions asked — whether or not you have started connecting, and regardless of how much data you have used.
• If routes in commonly used regions stay unreachable and a ticket-based check does not restore them, you can request a refund within the window.
• If a payment is charged twice, or the amount paid does not match the order amount, the overcharged portion can be refunded separately.
• If you have questions about how an upgrade price difference was prorated, open a ticket to review the bill first, then decide whether to request a refund.

Cases where a refund is not available

The following fall outside the scope of refunds:

• Orders past the 60-day refund window.
• Accounts restricted or suspended for breaking the Terms of Service, including reselling subscriptions, handing an account to someone else for long-term use, or using the service for purposes that break local law.
• Duplicate requests submitted after the same order has already been refunded.
• Subscriptions or data plans obtained through unofficial channels such as third-party resellers or purchasing agents.
• Requests where the payment record cannot be verified and no order number or payment proof can be provided.

How to apply and what to include

1. Log in to the user panel, open a new ticket on the tickets page, and select the “Billing & Refunds” category.
2. In the ticket body, give your username, order number, payment method, payment time and the amount actually paid.
3. Explain why you are requesting the refund. No-questions-asked refunds do not require a reason; anything you write is used only to troubleshoot route issues.
4. Make sure the receiving account matches the account used to pay, so the refund does not fail.
5. After submitting, follow up in the same ticket — both the review result and the progress are posted there.

Neither registration nor refund communication requires an email address; a username and password are enough for the whole process. Tickets are the only intake channel; refund requests made elsewhere cannot be matched to an order and are not treated as formal requests.

Refund payouts and the original payment route

Refunds always go back to the original payment method — no cross-channel transfers, and no refunds to someone else's account. Once approved, the payment channel completes settlement, and how long it takes depends on that channel's own processing; you can check the current status in the ticket.

The refund amount is based on what was actually paid for the order; if the order involved an upgrade difference prorated by remaining days, the prorated amount actually paid applies.

Once the refund is complete, the subscription time and data plan allowance tied to that order are voided at the same time. The account itself stays open, and you can purchase again later.

Differences between payment methods

• Alipay / WeChat: returned to the account used for payment. The account details in the ticket must match the payment record; if the account has been closed or restricted, say so in advance.
• USDT: returned to the chain and address used for payment, and the ticket must include the transaction hash for verification. On-chain transfers cannot be reversed once confirmed, and funds sent to a wrong address cannot be recovered.
• Original channel unavailable: if the payment account has been closed or the channel has stopped operating, explain the situation in the ticket; once the payment record is verified, the case is handled separately.

This policy, together with the Terms of Service and the Privacy Policy, forms part of the service terms. Plan tiers and data plan prices are listed on the pricing page. The policy is updated as the service changes, and updates are published on this page; refund requests already submitted are handled under the version in effect when they were submitted. If anything on this page conflicts with applicable laws and regulations, the laws and regulations prevail.