Refund Policy - VPNRS | 14-Day No-Questions-Asked Refunds

Refund window and scope

You may request a no-questions-asked full refund within 14 days of your first payment. The window starts from the record of your first successful payment and is checked against the ticket submission time. If the payment time is unclear, attach the payment record to your ticket so customer support can verify the order.

This policy applies to refund requests for VPNRS subscription services. Monthly subscriptions and data packages are billed differently, so identify the relevant order in your request and do not combine payments, data balances, or upgrade records from separate orders. A renewal or upgrade does not restart the refund window for the first payment.

You do not need to give a reason for requesting a refund. Details about connection issues are optional; completing troubleshooting, submitting speed test results, or switching routes is not a requirement for processing a refund.

Eligibility checks and exclusions

Requests that fall within the window above are handled as no-questions-asked full refunds. Requests outside the window are not covered by this commitment. Unpaid orders, and orders that were canceled without a charge, have no collected payment to refund. The same payment will not be refunded more than once.

Data usage records are used to verify the relationship between a subscription and its order. This policy does not impose an unpublished data usage threshold for deductions. If you see an excessive usage notice or an unusual data total, check the billing records; this alone will not convert an eligible full refund into a usage-based refund.

If an account is subject to a violation of the Terms of Service, the service status and refund request are reviewed separately. An account restriction does not automatically invalidate a refund request. If there is a payment dispute, unclear order ownership, or a duplicate request, the payment and any previous refund must first be clarified, with the basis for handling explained in a support ticket.

How to request a refund

Sign in to the user panel, open the support ticket page, and submit your refund request. Include your username, order number, payment time, amount paid, and payment method, and specify which order you want refunded. If there was an upgrade or renewal, include those details to help verify the payment.

If payment succeeded but the order has not updated in the panel, you can provide the transaction record or a payment screenshot. Keep only the information needed to verify the transaction visible; you may redact other personal details. Do not send your login password, payment password, keys, or subscription links.

Customer support will review the information and update the status in the original ticket. If more information is needed, reply in the same ticket. Submitting the request on time and providing additional verification later should not change the original request time just because the support reply arrives after the refund window.

Refund routes and payment methods

Alipay and WeChat Pay refunds are normally returned to the original payment account through the original payment channel. If the original transaction cannot be refunded directly, confirm the alternative arrangement and recipient in the ticket. Refunds will not be sent to an unrelated third-party account without confirmation.

USDT transfers follow a different refund process from Alipay and WeChat Pay. An on-chain transfer cannot be treated as a payment that can be automatically reversed. Before processing, the original transaction, network used, and receiving address must be checked, and both parties must confirm the refund arrangement in the ticket.

If the currency, network fees, or pricing differ, the specific handling method must be explained and confirmed first. No unpublished fee or conversion rate is assumed. Check the address and network details carefully to avoid issues receiving the funds.

Refund status and aftercare

Request acceptance, refund initiation, and receipt of funds are separate stages. Processing by the payment channel, account status, or on-chain confirmations can affect when funds arrive; this policy does not promise an unverified fixed settlement time. Customer support should explain the current status in the ticket. After initiation, you can check the original payment channel’s records.

If the ticket shows a refund as complete but your payment records have not updated, reply in the original ticket and provide any transaction lookup details needed. Duplicate payments or charges should be checked individually; submitting another refund request is not a substitute for reconciling the records.

Once a refund is complete, the subscription benefits and related data eligibility provided by that order end. The data package description “use it until it’s gone, with no expiration” refers to its validity during normal use; it does not mean the order benefits remain after a refund. For other billing rules, see package pricing. For information about personal data handling, see the Privacy Policy.