Refund Policy

Refund Window and Guarantee

You may request a full refund for any reason within 30 days of your first payment. The refund window starts when the first payment is successfully completed, as verified against the order payment record and ticket submission time. Requests submitted within this window do not require proof of connection problems or prior troubleshooting.

If you have questions about route selection or client settings, you may contact support first, but this is not a prerequisite for requesting a refund. If you need to provide additional order information for an existing request, reply to the original ticket to keep the complete request record together and avoid confusion from duplicate submissions.

Eligibility and Limitations

Requests that meet the window above are covered by the full-refund guarantee, no questions asked. Connecting to a route, importing a subscription, or using some of the included data does not, by itself, justify refusing a refund. VPNWind does not impose unpublished data-use percentages or deduction thresholds under this policy.

Orders outside the refund window are not automatically covered by this guarantee. If you have questions about refunds for renewals, upgrades, or data-package orders, specify the order type and related records in a ticket so support can review and explain. This policy does not treat each subsequent payment as reopening the refund window for the first payment.

For unusual data usage, suspected violations, or payment disputes, the order and account details must first be reviewed. Normal data use is not, by itself, a violation. For disputes involving the terms of service, provide the specific basis rather than a vague claim of “excessive use.” Requests that cannot be matched to a payment record require additional materials before processing can continue.

How to Request a Refund

1. Log in to the user dashboard, open the ticket portal, and clearly state that you are requesting a refund.
2. Provide the relevant order number, plan or data-package name, payment method, and payment record. If multiple orders are related, explain which payment corresponds to each order.
3. Provide any necessary verification materials requested in the ticket, then check the original ticket for updates and return progress.

You may optionally provide a reason for the refund request to help improve the service; it is not required for requests within the refund window. Redact information unrelated to order verification from payment screenshots. Do not submit your login password, full subscription link, or account access credentials. No email address is required; log in with your username and password to submit a ticket.

Refund Methods and Payment Differences

Supported payment methods are Alipay / WeChat Pay / USDT. Refunds are generally returned through the original payment method; available options depend on the original transaction record and the payment provider's capabilities. Do not make another payment before ticket verification is complete, and do not ask an unverified third party to handle your refund request.

Alipay and WeChat Pay orders require verification against the corresponding transaction record. If the original method cannot be used for the return, explain why in a ticket and wait for confirmation of the next steps. USDT transfers cannot be reversed like ordinary payment transactions. If a transfer is needed to return funds, the network and receiving address must be verified in a ticket first; a screenshot of an address alone is not sufficient to establish ownership.

Refund Status and Disputes

Request acceptance, document verification, refund initiation, and receipt of funds are separate steps. The time it takes to receive funds depends on the original payment channel, transaction status, and any required verification; this policy does not guarantee a fixed number of days. A notice that a refund has been initiated in a ticket does not mean the funds have reached your account. Check the transaction records with your payment provider.

If the funds have not arrived, add the current transaction status to the original ticket so support can investigate. Do not publicly share complete payment records or receiving addresses. For duplicate payments, amount discrepancies, or disputes about eligibility, list each order separately. See the Terms of Service for related service rules and the Privacy Policy for information about data handling.