Refund Policy
Last updated: August 2026
This policy explains the refund terms, request process, and payment return methods for VPNSQ subscriptions and data packages. A full refund may be requested without giving a reason within 30 days of the first payment. The request does not require a personal explanation, but the order’s payment status, service usage records, and account compliance must still be verified.
Refund Window and Eligibility
The refund window starts when the first payment is completed. An eligible first payment with a verifiable order status may qualify for a full refund under this policy. Requests are handled for specific orders. If a mid-term upgrade creates a price difference, it is converted according to the remaining days, so the original order and upgrade records will be reviewed to confirm the actual payment relationship.
Monthly subscription data resets each month from the activation date. Data packages remain valid until used and do not expire. Not having used the service, connection results that do not meet expectations in the current network environment, or an incomplete client setup does not prevent a request within the refund window. Once a refund is completed, the service benefits tied to the relevant order will also end.
Exclusions
A no-questions-asked refund means that the requester does not need to provide a subjective reason; it does not waive verification of order authenticity or account compliance. Requests submitted after the refund window are outside the refund commitment of this policy. Duplicate payments, abnormal payment statuses, or clear technical order errors may be reviewed separately through a ticket and are not automatically assessed as standard refund requests.
A refund request may be suspended or denied if the account has a record of violations, a payment dispute, forged transaction evidence, interference with service operation, or a breach of the Terms of Use. Abnormally concentrated use of purchased data to obtain a refund, data that has already been used beyond its allowance, or repeated exploitation of the refund mechanism to obtain service benefits does not qualify as a refund following normal use. A single connection failure will not by itself justify rejection; the order, data usage, and account records will be considered together.
Request Process and Required Information
Requesters should sign in to the user panel and submit a refund request through a ticket. The ticket must state the username, the order to be refunded, and the original payment method, together with a transaction record or payment receipt that can be used to verify the payment. No email address is required; account registration and identity checks are based on the username and relevant order information.
After submitting a request, keep the original order and payment records, and do not submit the same request again. If the available materials cannot be matched to a specific order, the review team will ask for verifiable information in the ticket. Reply within the same ticket to prevent inconsistencies between multiple requests from affecting processing.
Review and Service Status
The review covers the first payment date, order amount, payment status, refund window, data usage records, and compliance with the Terms of Use. When the information is complete and meets the policy, the refund enters processing. If information is missing, payment records cannot be matched, or the transaction is still awaiting channel confirmation, processing will wait until the information is completed or the payment status is updated.
After a refund request enters processing, the related subscription or data package may stop being available to prevent new usage records during the review. If the request is withdrawn or not approved, any still-valid order benefits will be handled under their original status. Once approved, the related benefits will not be restored; to use the service again, select an available plan.
Settlement Time and Original Payment Method
After approval, funds are generally returned through the original payment channel. Once VPNSQ initiates the refund, the actual posting time depends on the channel’s processing progress, account status, and settlement procedures. This service cannot promise a specific posting time on behalf of the payment channel. Requesters can check the refund record in the original payment account. If the channel shows that processing is complete but the funds have not arrived, add a screenshot of the transaction status to the original ticket for further review.
The refund amount is based on the actual payment record of the approved order. Exchange-rate display differences, asset price changes, or the way information is shown on the account side do not change the basis used to verify the original order payment in the system.
Handling by Payment Method
Alipay and WeChat Pay payments are returned through the original transaction path when permitted by the channel. If the original account is restricted, the transaction status cannot be identified, or the channel refuses to process the return through the original path, the requester must provide the information returned by the channel through a ticket before processing can continue. This service will not ask for a payment account unrelated to the order to receive the refund.
USDT transactions use on-chain settlement. The original transaction record, payment asset, and corresponding network must be verified after submission. Once approved, the refund is returned in the original payment asset to the verified payment address. If the original address cannot receive the funds, confirm a compatible address in the ticket. The requester is responsible for checking the address and network information. Processing will be paused when the information is incomplete to prevent assets from being sent to an incompatible address.
If you have questions about the refund result, continue the conversation through the original ticket in the user panel. VPNSQ does not list other external contact methods in this policy and will not ask you to process a refund through a phone call, an offline address, or an unverified third-party account.