Last updated: December 2026
Refund Policy
This policy explains the refund scope, application process, and return procedure for VPNKD subscriptions. Read it alongside the Terms of Service and your order records. Submit refund requests through a support ticket in the user panel; updates on the request will remain in that ticket.
Refund Window and Commitment
You may request a no-reason full refund within 30 days of your first payment.The refund window is based on the order record for the first successful payment on your account. Submit your request within that window and keep a record of the ticket submission. Review time and payment provider processing time are separate from the time you submit your request.
You do not need to prove a connection issue or explain why you are dissatisfied to request a no-reason refund. Changes in whether you continue using the service, device compatibility, or usage habits can be included as background, but giving a reason is not a requirement.
A renewal, upgrade, or separately added data package does not reopen the refund window for your first payment. If your request concerns multiple orders, specify each one so the support team can check the payment records and respond clearly.
Eligibility and Dispute Review
Requests made within the first-payment window above are handled under the no-reason full refund commitment. Having connected to the service or used some data does not automatically change the refund to a prorated amount based on remaining data. Monthly subscriptions and data packages are billed differently, so identify the relevant order when applying to avoid confusion between account benefits.
Orders outside the refund window for the first payment are not covered by this policy’s no-reason full refund commitment. Repeated requests for the same order after a refund has been completed will not result in another payment. If a payment was unsuccessful, check its status first rather than treating it as a completed payment eligible for a refund.
Excessive data use, account violations, and disputes over who made a payment require separate checks of usage records, relevant terms, and transaction evidence. This policy does not set an unpublished data deduction threshold or treat an account restriction as automatic cancellation of refund eligibility. If a dispute arises, the support ticket should state the basis for the review and its outcome.
How to Apply and What to Provide
Sign in to the user panel support ticket, state that you are requesting a refund, and provide the relevant order number, payment method, amount, and payment date. For an upgrade or data package, also list any related orders that need to be checked. You do not need to provide an email address for the request.
If the order status does not match the payment record, you can provide transaction evidence or a transaction ID. Keep screenshots limited to the order details needed for verification, and hide balances and other transactions unrelated to your request. Do not send account passwords, payment passwords, private keys, or recovery phrases in a support ticket.
After submitting your request, check the original ticket for a response or requests for additional information. Once the review is complete, the response should specify the refunded order, amount, return method, and how the related service benefits will be handled. An order with a completed refund should no longer be treated as an active paid benefit.
Refund Route and Arrival Status
Refunds are generally returned through the original payment method, rather than automatically converted into account balance, credit, or another benefit. If the payment provider imposes a restriction, the reason should first be explained in the support ticket, and an alternative verifiable return method should be confirmed with the payer.
Request acceptance, refund initiation, and receipt of funds are separate stages. The time to receive a refund depends on order verification and payment provider processing; this policy does not promise a fixed number of days. After you receive confirmation that a refund has been initiated, also check the transaction history of the original payment account.
If the refund has not arrived, provide the refund record and current payment status in the original ticket so the issue can be checked further. Do not submit another refund request for the same order, as details may differ between tickets.
Refunds by Payment Method
Alipay and WeChat Pay refunds are generally made through the original transaction route. The actual account receiving the funds and the displayed status depend on the payment provider’s records. If the original payment account has an issue or the provider cannot process the return, confirm the next steps through a support ticket.
USDT transfers use a different refund process from Alipay and WeChat Pay transactions. The original transaction, network used, and receiving address must be checked, and the return arrangement confirmed in a support ticket. Do not assume that similar-looking addresses use the same network, and do not provide an address for another cryptocurrency.
If an on-chain transfer cost or amount calculation applies, explain and confirm it before proceeding; no fee or exchange rate is assumed in advance. The full refund commitment should not be replaced by an unexplained deduction. See the Privacy Policy for information on account and transaction evidence handling.