Refund Policy
Last updated: October 2026
This policy explains the refund scope, application process, and payment handling principles for VPNMG subscription services. Keep your order records and submit a support ticket through the user panel. Refund decisions are based on order verification and the handling record in the ticket.
Application Window and Eligibility
You may request a full refund for any reason within 60 days of your first payment.The application window starts from the first successful payment and is verified against the ticket submission time. You do not need to prove dissatisfaction with the service or complete troubleshooting first.
This policy applies to paid monthly subscriptions and data packages. Specify the orders you want reviewed when submitting a request. If you have renewals, upgrades, or multiple payments, list each one separately to avoid combining distinct transactions. Later payments do not restart the application window for your first payment; the applicable orders will be verified in the ticket.
Requests outside this window are not covered by this policy's full-refund promise for any reason. You may still submit a ticket for transaction issues, such as duplicate charges or a successful payment that was not correctly credited to an order.
Usage Records and Exceptional Cases
Connecting normally, using some of a package's data, or using the service on different devices does not by itself justify refusing a refund request made within the application window. VPNMG does not set an additional used-data percentage or data deduction threshold in this policy, and will not deduct a refund based on unpublished criteria.
If data use exceeds the package allowance, an order has an unusual status, a payment is disputed, or an account may have violated the Terms of Service, the order, billing records, and relevant facts must be reviewed. Account status and refund amounts are checked separately; a decision will not be based solely on an anomaly label.
If payment ownership cannot be confirmed, a transaction has already been refunded, or a payment dispute is in progress, the payment status must first be clarified to prevent duplicate refunds. If a request cannot proceed, the ticket should explain the specific reason and any information that can be provided.
How to Apply and Information Required
Sign in to the user panel support ticket page and submit a refund request with the order number, payment date, amount, and payment method. List each order separately if you are requesting refunds for multiple orders. Providing a reason is optional and is not required for a refund within the application window.
If the order in the panel does not match your payment record, you can provide a payment receipt or transaction ID. Include only the details needed to verify the transaction in screenshots, and hide unrelated personal information. Do not submit your account password, payment password, private key, or recovery phrase.
After submitting your request, check the original ticket for verification updates and any requests for additional information. You can view replies in the panel without an email address. Before a refund is processed, the ticket will explain which orders and related service benefits are affected; associated benefits will be adjusted once the refund is complete.
Refunds to the Original Payment Method and Tracking
Refunds are generally returned through the original payment method. Order verification, initiating a refund, and the funds arriving are separate steps. A refund marked as initiated in the panel does not mean the funds have reached your payment account. Arrival time depends on the payment provider and account status; this policy does not promise a fixed timeframe that has not been confirmed.
Orders paid through Alipay or WeChat Pay are processed through the original transaction route. If the original transaction cannot be refunded directly, explain why in the ticket and confirm a feasible alternative first. You will not be asked to pay an additional fee to receive a refund.
To check progress, provide the original ticket and order number so the refund status and available transaction records can be verified. If processing is marked complete but the funds have not arrived, check your payment account statement as well, and avoid submitting the same request again.
USDT and Special Payment Handling
USDT transactions usually cannot be automatically reversed through the original transaction. The original payment record must be verified in a ticket, followed by confirmation of the return network, receiving address, and refund amount. Do not assume a refund destination based only on a historical transfer address; an address used by a trading platform to send funds may not be able to receive a refund.
If network fees, currency conversion, or payment provider restrictions apply, the handling method must be explained and confirmed before processing. No unpublished rates or deduction rules will be assumed. Check the receiving details carefully; on-chain transactions usually cannot be reversed after they are sent.
This policy applies alongside the Privacy Policy and Terms of Service. Later wording updates will not retroactively reduce refund commitments that have already taken effect. If you have questions about the orders covered or the outcome, you can request a review in the original ticket.