Refund Policy

Refund window and scope

You may request a full refund for any reason within 30 days of your first payment. The submission timestamp in the user panel ticket determines when the request was made; the first payment date is verified against your account order and payment records. You do not need to complete troubleshooting first or provide a reason for no longer using the service.

Identify the order you want refunded in your request. Monthly subscriptions and data plans are billed differently. If your request involves a renewal, upgrade, or multiple payments, list each order separately so the ticket can identify the corresponding amount. Later payments do not restart the refund window, which begins with the first payment. Requests made after the window are not covered by this no-questions-asked refund policy, though payment issues may still be submitted for review.

Eligibility and verification limits

You may request a refund within the refund window if the routes do not suit your day-to-day needs, your device usage habits have changed, or you no longer need the subscription service. Normal connections and data usage are not, on their own, grounds for denying a refund. This policy does not impose an unpublished data-usage threshold.

An order that has not been paid, has already been refunded, or cannot be verified as belonging to the requesting account cannot be refunded again or processed directly. If there is unusual usage beyond the plan allowance, a suspected account violation, or a payment dispute, the order, usage records, and relevant terms must be reviewed. A refund cannot be ruled out solely based on an anomaly flag. The decision and its basis should be explained in the ticket. See the Terms of Service for usage rules.

How to request a refund

1. Open a support ticket in the user panel, submit the request from the account associated with the payment order, and clearly state that you are requesting a refund.
2. Provide the order ID, payment date, payment method, and amount paid. If payment records need to be checked, you may attach proof of payment with information unrelated to the order concealed.
3. Add any verification materials to the original ticket and check its status as the request is reviewed, the refund is initiated, and the process is completed. Do not open multiple tickets for the same order, as this can split the records.

No email address is required for the account; you can get started with a username and password. Refund discussions also take place through support tickets in the user panel. Do not submit your account password, payment password, private keys, or recovery phrases. If you cannot access your account, first check the user panel access instructions on the Contact page.

Refund destination and processing status

Eligible payments are returned through the original payment method whenever possible. Initiating a refund and receiving the funds are separate steps. Processing by the payment channel, settlement status, and handling by the receiving account can all affect timing, so this policy does not guarantee a fixed arrival time.

If the ticket shows that a refund was initiated but the funds have not arrived, first check the transaction records for the original payment account, then add the current status to the original ticket. If the original payment route is unavailable, verify the response from the channel and confirm the next steps through the ticket to avoid duplicate refunds. The status of the order, plan, and remaining data after a refund is completed should also be clarified in the ticket.

How different payment methods are handled

For Alipay and WeChat payments, refunds are sent through the original transaction whenever possible. The destination and displayed processing time depend on the relevant payment channel's records. Keep the original transaction receipt, and do not assume the funds have arrived based only on a change in subscription status.

USDT transfers cannot be reversed in the same way as Alipay or WeChat transactions. The original transaction must be verified, and the refund network and receiving address confirmed in the ticket. Do not change the receiving information without confirmation, or send additional funds to any address to process a refund. If network fees apply or the original route cannot be used, the handling method should be explained and confirmed before a transfer is made. No unpublished fee rules are assumed.

Disputes and policy records

If you have questions about a verification result or refund status, raise them in the original ticket and add the relevant order records. VPNGH will review the request date, payment details, and refund records, and will not ask you to resubmit information that can already be verified.

This page, the Terms of Service, and the Privacy Policy explain the service rules together. Policy updates should not retroactively reduce refund commitments that were clearly stated at the time of payment. If this page differs from your order records, keep the relevant records and ask for verification through a support ticket.