Refund Policy

Refund Window and Eligibility

The refund window begins when the first payment is completed. Users who meet the first-payment condition and submit a request within 14 days may request a full refund without giving a reason through a panel ticket. The reason for the request may help verify the service experience, but it is not required proof when the request meets the window conditions.

Normally importing a subscription, connecting to international routes, switching platforms, or using the data included with an order does not by itself change refund eligibility. This policy does not use the number of devices as a refund condition, and simultaneous devices remain unlimited. Eligibility is primarily checked against the first-payment time, the relevant order, and account status.

Exclusions and Irregular Cases

The full-refund commitment without giving a reason does not apply when the 14-day window after the first payment has passed, when the request cannot be matched to the first payment order, or when it concerns a later renewal or another non-first transaction. Monthly subscription data resets each month on the activation date; data packages remain available until used and never expire. Valid data packages outside the refund scope remain subject to the original rules.

Normal use of the data included in an order is not irregular usage. If an account uses more data than its purchased benefits allow, bypasses billing, resells the service, submits false transaction information, or otherwise violates the Terms of Use, the request will first undergo account and order verification rather than being handled directly as a standard no-questions-asked request. Restrictions and action for violating accounts follow the Terms of Use; refund rights that must be preserved by law are not affected.

Request Process and Required Information

All refund requests must be submitted through a user panel ticket. Sign in to the relevant account, open the ticket page, select the matter related to the order or refund, and describe the transaction that needs to be verified. This site does not publish a contact email or social account, so do not send payment details through channels outside the panel.

1. Open Panel Tickets and submit the request using the account that made the payment.
2. Provide the account username, order identifier, payment method, payment record, and the necessary information for transaction verification.
3. If the order status or payment route differs, provide the corresponding proof in the ticket reply.
4. After the review is complete, the ticket will record the refund decision and the next processing route.

VPNPG registration requires no email address, so refund verification does not require one. Avoid submitting sensitive information unrelated to transaction verification in a ticket. Processing will wait for additional information if the details are incomplete or the order cannot be matched.

Payment Routes and Settlement Rules

Payments made through Alipay or WeChat will, in principle, be returned through the original payment route after approval. Once a refund is initiated, the actual crediting time depends on the payment channel's settlement process and account status. VPNPG does not promise a fixed settlement time that is not specified in the applicable rules. If the original route cannot receive the refund because of the channel status, the handling method will be confirmed in the ticket.

USDT transactions cannot be automatically reversed through traditional payment channels. After approval, the user must confirm in the ticket the address that can receive the refund and the corresponding network. VPNPG will process the refund based on the verified payment record. On-chain settlement depends on network confirmations. Submitting an incompatible or unrecoverable address may pause processing, so no transfer will be initiated until the address is confirmed.

Plan Changes and Refund Results

When a monthly subscription is upgraded mid-cycle, the price difference is converted based on the remaining days. If a renewal, upgrade, or other order change has already occurred within the first-payment window, list the relevant orders in the same ticket so the first payment can be distinguished from later transactions. Handling of later transactions does not automatically expand the scope of the first-payment refund commitment.

After a refund is approved and initiated, the benefits associated with the order may be terminated, and the related subscription entry will be adjusted with the order status. Users should make any necessary usage arrangements before submitting a request. If you have questions about the review result, order ownership, or refund route, continue adding details to the original ticket to avoid dispersing transaction information across duplicate requests.