Refund Policy
Last updated: October 2026
This policy explains the refund terms, request process, and payment verification steps for VPNLH subscriptions. Refund requests are handled through support tickets in your account. For plan billing and data rules, see the plans page and the Terms of Service.
Request Window and Refund Scope
You may request a full refund for any reason within 60 days of your first payment.The request window is verified against the payment record for your first paid order. You do not need to explain why you are dissatisfied or complete troubleshooting for connection issues before submitting a request.
Please identify the order you want reviewed. If you have renewal, upgrade, or data package orders, list each one separately to avoid mixing the first payment with later payments. A later payment does not automatically restart the request window for the first payment. The support ticket review will confirm the orders covered and provide an explanation in writing.
Eligibility and Disputed Orders
Within the request window above, you may request a refund for any reason, including changes in your experience, device setup, or personal needs. Connecting to a route or using data does not, by itself, waive your right to request a refund. This policy sets no additional threshold based on the proportion of data used, and normal use is not automatically considered excessive use.
Orders outside the request window are not covered by the commitment above, and the same payment cannot be refunded twice. If an order involves a payment dispute, unusual data records, or an account-violation dispute, the relevant records and applicable terms should be reviewed first. An account restriction does not determine the refund outcome. The decision should state its basis, and a general anomaly label is not a substitute for reviewing the order.
How to Request a Refund
Sign in to the user panel and submit your request through the support ticket portal. State that you are requesting a refund and provide the relevant order number, payment date, amount, and method. If you are requesting refunds for multiple orders, specify each order separately.
If the payment record does not match the order status, you may attach proof of payment and redact personal information that is not needed for verification. Do not provide your account password, full subscription link, or other access credentials. If the support team needs more information, it should explain why. Reply in the original ticket to keep the full case history together.
We recommend keeping the submission time and ticket number. Whether a request falls within the window is verified using the request and payment records; time spent on later communication should not be treated as a delay in submitting the request.
Refund Routing and Status
Refunds are generally returned to the original payment source through the original payment channel. Order verification, refund submission, and crediting by the payment channel are separate steps. A completed status in the panel does not necessarily mean the payment channel has completed the credit. The time it takes depends on the channel's processing status; this policy does not guarantee a fixed arrival time.
After receiving a refund update, check the original transaction and payment account records. If the funds are not yet visible, ask for the refund status and available proof in the original ticket. If the original channel cannot return the funds, the reason should be explained and a workable option confirmed before proceeding. Do not change the recipient details without confirmation.
Payment Methods and Follow-up
VPNLH supports Alipay, WeChat Pay, and USDT. For Alipay and WeChat Pay, refunds are first handled against the original transaction; check the channel records for the current status. USDT transfers work differently from these channels, and an order marked as refunded does not by itself confirm an on-chain return.
For USDT, use an account support ticket to confirm the transaction record, network, and receiving address. Verify the amount to be processed and any applicable network fees before proceeding. This policy does not specify an exchange rate, fee amount, or crediting speed. If there is a discrepancy, explain it in the ticket first; an unconfirmed deduction should not be treated as final.
When a refund is completed, the related order benefits and subscription status should also be checked. Confirm the outcome using the support reply and panel records. If the status does not match, follow up in the original ticket. For details on handling other account information, see the Privacy Policy.