Refund Policy

Refund Window and Eligibility

The refund window starts when the first payment order is completed. The account holder may request a full, no-questions-asked refund for that order within 14 days of the first payment. The submission record in the user panel determines whether the request was made on time.

This commitment applies to a first-time monthly subscription or traffic package purchase. Routine client installation, subscription import, international route selection, and basic connectivity checks do not by themselves remove refund eligibility. A refund request must correspond to an actually paid and verifiable order; unpaid, canceled, or unmatched payment records are not eligible.

Renewals, repeat purchases, additional traffic packages, and later payments caused by an upgrade do not create a new first-payment refund window. The price difference for a mid-term upgrade is calculated according to the remaining days and checked against the original order and upgrade record during review.

Refund Exclusions

A request submitted more than 14 days after the first payment is outside the scope of a full, no-questions-asked refund. If an account has consumed a concentrated amount of traffic that is clearly disproportionate to connection checks over a short period, the traffic is considered excessively used, and VPNFD may reject the request based on subscription records. Traffic packages remain valid until used and do not expire, but their long-term validity does not extend the first-payment refund window.

Requests may not be accepted when an account is used for activities that violate the Terms of Use, a subscription is resold or publicly shared, routes or service operations are disrupted, false payment materials are submitted, or a payment dispute is filed and a separate refund is then requested from VPNFD for the same matter. Traffic consumed because account credentials were not properly protected must also be checked against actual subscription records and is not automatically treated as unused.

Regional rules, content permissions, and service status for third-party websites, applications, or accounts are outside VPNFD's control. A request based only on a third-party feature not meeting expectations will still be handled according to this policy's refund window, traffic usage, and account status.

Request Process and Required Information

The requester should sign in to the account used for the purchase and submit a refund request through the user panel ticket system. Account creation does not require an email address, so refund verification mainly uses the username, order record, and payment details; no additional email address is required.

The ticket should identify the order to be refunded, the original payment method, the payment record, and the necessary details for locating the transaction. The reason for the refund may be stated briefly to help determine whether duplicate charges, client configuration, or route selection should be checked first. Providing a detailed reason does not affect an eligible no-questions-asked refund request.

For USDT payments, provide a verifiable transaction record and confirm the original payment network and compatible receiving details as requested in the ticket. Do not display account passwords, subscription content, or other sensitive information on public pages or in unrelated locations.

Review, Entitlement Termination, and Results

After receiving a request, VPNFD will verify the first payment time, order status, subscription usage record, upgrade record, and whether the account has violated the Terms of Use. If information is incomplete or the order cannot be located, the ticket will request the necessary details. The request is not considered approved until verification is complete.

Once a refund is approved, the subscription and remaining traffic entitlements linked to the order will stop being available, and subscription information already imported into a client may also become invalid. Before submitting, the requester should confirm that the international routes and network acceleration provided by the order are no longer needed.

If a request does not meet this policy, the ticket will explain the main basis for the decision. If the requester believes the order or traffic record contains a discrepancy, payment proof and relevant details may be added to the original ticket for review. Avoid creating duplicate requests for the same order.

Refund Routes and Payment Method Differences

Refunds are generally sent back through the original payment route and cannot be directed to an account unrelated to the payer. For Alipay or WeChat payments, processing begins through the available original transaction route for the relevant payment channel after approval. The actual display time depends on the payment channel, account status, and its processing procedure.

USDT transactions do not have the same automatic return mechanism as Alipay or WeChat. After approval, the refund is processed using the original payment network and receiving details verified in the ticket; it is not converted into an Alipay or WeChat refund. If the network or receiving details provided are incompatible, they must be corrected first to prevent the transaction from becoming unidentifiable.

If the original payment route cannot be completed because of channel restrictions, account status, or abnormal transaction details, VPNFD will explain the available handling method through the original ticket. The time for funds to arrive depends on the relevant payment channel or network confirmation, so the refund record and the channel's final status prevail.

Policy Scope and Record Retention

This policy and the Terms of Use jointly govern refund processing. Order records, payment proof, subscription usage records, and ticket correspondence are used to determine whether a request qualifies. For unusual transactions or account violations, VPNFD may pause refund processing until necessary checks are complete.

Policy changes do not alter refund results that have already been approved. When submitting a request, use the current version published on this page. If the page differs from the verification result for a specific order in the ticket, request a review through the original ticket.