Refund Policy

Refund Window

A full refund may be requested within 30 days of the first payment, with no reason required. The refund window starts when that first payment is completed, and the same rule applies to monthly subscriptions and data packages. A no-questions-asked refund does not require proof of a network-quality issue, but you must provide enough information to identify the account, order, and payment records.

Orders submitted after the refund window, along with renewals, repurchases, and other separate orders made after the first payment, are outside this guarantee. If such an order involves duplicate charges, an abnormal payment status, or failed delivery, submit the relevant records through a user-panel ticket so support can review the actual order status.

Eligibility

During the refund window, normally testing the subscription, switching international routes, or verifying connectivity on a supported platform will not by itself remove your eligibility simply because normal data usage occurred. Usage records on Windows, macOS, iOS, Android, and Linux are reviewed under the same policy, and the number of devices online at once does not change the refund window.

The account must be accessible and match the first-payment order for which the refund is requested. No email address is required to register; you can verify your identity with your username, order identifier, and payment records. If the order was upgraded mid-term, provide the related orders before and after the upgrade so any price difference converted into remaining days can be verified.

Exclusions

The following situations are outside the first-payment no-questions-asked refund guarantee or require additional verification first:

• The application is submitted after the 30-day refund window following the first payment.
• The order in the application is not the account’s first paid order.
• The data allowance has been exceeded, the purchased data package has been fully used, or abnormal actions were used to circumvent the data rules stated in the order.
• The account has been restricted for violating the terms of use, or the order involves false payment records, duplicate refunds, malicious disputes, or other abusive activity.
• The payment failed, the order was canceled, or the payment channel has not yet confirmed receipt. These cases require payment-status verification and are not refunds for a completed payment.

Data packages remain valid until fully used and do not expire. If no refund is requested, their validity does not change because of inactivity. Eligibility is determined by the verifiable order status and actual usage records available when the application is submitted.

How to Apply

All refund requests must be submitted through a user-panel ticket. Include your username, the identifier of the order to be refunded, payment method, payment date, and the purpose of the request. You may briefly state the reason; during the no-questions-asked refund window, the reason itself does not need to be proven.

If the order record cannot be matched directly to the payment status, support may ask for additional proof of payment or a transaction identifier. Do not submit your account password, subscription URL, or sensitive information unrelated to the refund in a ticket. Once the information is complete, VPNLZ will verify the first-payment date, order ownership, data usage, and account status, then reply with the review result in the same ticket.

Refund Method

Approved refunds are generally sent back through the original payment route. Payments made through Alipay or WeChat Pay will be submitted for refund to the corresponding original payment route. After submission, the actual posting time depends on the payment channel’s processing status; VPNLZ does not make an additional guarantee about a fixed posting time on the channel’s side. Keep the ticket record and check the result in your payment records.

USDT transactions are processed on a blockchain and cannot be automatically reversed in the same way as Alipay or WeChat Pay payments. In the ticket, provide the original transaction identifier and confirm the refund address and corresponding network as requested by support. The address and network information must be accurate; the refund will not be submitted until the details are confirmed. If a refund through the original route cannot be completed because of the payment channel’s status, support will first explain the available handling method in the ticket before proceeding.

Records Used

Refund reviews are based on the order created at payment, payment-channel records, and account usage records. The brief refund notice on the plan page summarizes the guarantee; this page defines the application scope, review boundaries, and handling process. If an order has an unresolved payment dispute, first complete a status check in a ticket to prevent the same transaction from being processed twice.