FAQs & Subscriptions

No email address is required. Create an account with a username and password. Once you open the user panel, make sure you have saved your username before managing your plan or configuring a client. Use a unique password and keep your account details in a trusted password manager. Never post your password or subscription link in a public forum. Because account creation does not require an email address, email recovery is not a default account recovery option. If you have trouble signing in, check your username, keyboard input, capitalization, and the details saved in your password manager. If you still cannot access your account, note the on-screen error and explain the issue through a support ticket available in the user panel. Do not share your full password with anyone.

Open the user panel and check your plan status, then find your current subscription details in the download and subscription section. If the subscription is already imported into your client, open the existing entry and use its update or refresh option rather than adding the same subscription again. After refreshing, make sure the active entry is the one you just updated, then select a route again. If retrieval fails, check that the link was copied in full, without extra spaces, and that your current network can reach the panel. Do not edit the link parameters yourself. A subscription link grants access to your account, so hide the full URL in screenshots. When asking for help publicly, share only the error text and client platform.

VPNKZ supports unlimited devices, so changing devices alone does not mean you need to buy another plan. Use the appropriate client on Windows / macOS / iOS / Android / Linux and get your subscription through your existing account. Check your current plan first, then import the subscription and choose a route on the new device. If you no longer use an old device, remove its saved subscription configuration to reduce the risk of leaving credentials behind. Unlimited devices does not mean each device has a separate data allowance; check your account’s plan usage. Large file transfers and HD video streaming across multiple devices are also affected by each device’s local network and selected route, so allocate connections according to your needs.

First distinguish duplicate imports from a leaked link. Similar-looking entries in a client often result from importing the same subscription more than once; they do not, by themselves, mean someone else has accessed your account. Compare the entries with the current subscription details in the user panel, keep the one you need, disable older entries, and test the connection. If you shared the link publicly, remove the post and contact support through a panel ticket to report the exposure and ask how the subscription can be handled. If the panel offers a reset option, read its instructions before using it. Changing your account password and replacing your subscription link are separate actions; do not assume that changing the password invalidates an old link. Save new details only on trusted devices, and check whether any devices still use the old configuration.

Pause the proxy first and make sure your local network can reach familiar websites. Then reconnect the client. Check that the subscription is up to date, your plan is active, and you have selected a working route. A client showing as active does not necessarily mean system traffic is going through the proxy. Try a different region or route type, then visit several sites in a browser to see whether everything fails or only certain services. If switching routes makes no difference, check for conflicts between the system proxy settings and other networking tools. Restore the configuration if the client recommends it. When submitting a ticket, include your platform, network environment, the error message, and the steps you have tried rather than simply saying it does not work.

Apps handle network settings differently. Some follow the system proxy, others keep their own proxy settings, and some background connections may not match the current routing rules. First check whether the client is using rule-based routing or global mode. Then see whether the app needs a proxy configured in its own settings. After changing settings, fully quit and reopen the app so it does not keep using an existing connection. If the client offers modes such as a virtual network interface, follow the guide to check system permissions and supported use cases; do not enable every option just to troubleshoot. Global mode does not guarantee compatibility with every app. If the issue persists, note the app name, platform, and exact error so support can investigate through a ticket.

A successful update usually means the configuration was retrieved; it does not confirm that the active entry, account status, and system permissions are all correct. Go to the client’s configuration list and make sure you are using the latest subscription for your account. Check that the route list is not cached from an older configuration. Then check your plan status in the user panel and confirm that your system allows the client to establish network connections. If the error is related to configuration parsing, save the full error text and use the panel to find client instructions for your platform. Do not delete configuration fields at random to clear the message. Before importing again, save any settings you need. Avoid changing routing rules, proxy mode, and subscription source all at once, or it will be harder to identify the cause.

After a network change or waking your device, the existing connection may still be using the old network state. First confirm the new network can access websites, then stop and reconnect the client. If the network requires a sign-in page, complete that process first. Next, check that the system proxy still points to a running client so you do not leave proxy settings behind after the app exits. If the issue keeps recurring, note whether it happens after switching networks, waking from sleep, or launching the app, and include your platform and route type. Submit the error and steps you tried through a user panel ticket. Hide your account password, subscription link, and payment details in screenshots; never post your full configuration file to troubleshoot.

First check whether the slowdown also affects your local network. Pause large transfers on other devices, test regular websites, then compare routes using the same app so local congestion is not mistaken for an international route issue. Choose a region that meets the target service’s requirements, then compare IEPL, relay, and direct routes within that region. Keep the test content consistent after switching and check whether pages load, video buffering improves, or sessions recover instead of judging by route names alone. If only one service is slow, its own status or region detection may be involved. If the problem persists, include the time, access network, use case, and routes tested in a support ticket to help distinguish a broader issue from a single connection problem.

These terms describe how a connection is routed, not a speed ranking that applies to every situation. IEPL uses a dedicated link, relay routes traffic through an intermediate node, and direct routes depend more heavily on the connection between your local network and the destination region. Actual performance also depends on your access network, time of day, destination service, and client settings. For work calls and long sessions, focus on connection stability. For browsing, compare page load times; for streaming, also check how the platform detects your region. VPNKZ covers 120+ countries / 180+ routes. Start with the region you need, then compare route types rather than switching repeatedly to chase a particular label. See the routes page and route selection guide for details.

Not necessarily. A working route only confirms that a network connection can be established. AI tools and streaming services may also check account region, payment details, app store region, previous sessions, and exit IP address. Review the platform’s requirements, choose a route that meets its region requirements, and try to keep the same region throughout a session. Frequent region changes can make troubleshooting more confusing. If a site works in your browser but the app does not, check the app’s proxy settings and cached session as well as the route. VPNKZ provides network acceleration and route selection; it does not replace eligibility for a platform account or guarantee that all content will always be available. Include the exact region message in a support ticket to help identify the issue.

Latency, sustained throughput, and app responsiveness reflect different parts of a connection. Low latency does not guarantee consistently fast large downloads. Download speeds also depend on the content server, route, local Wi-Fi signal, and other activity on your network. Video playback may be affected by the platform’s content delivery and region checks. First confirm that the app is using the proxy, then compare routes with the same content source so differences between download servers do not skew the results. If several devices are in use, check for background syncing or ongoing uploads. Route status is a guide for choosing a route, not a guarantee of performance; judge it by the task you need to do. If several routes perform poorly under the same conditions, include your comparison in a support ticket instead of sending only a latency screenshot.

Monthly plans: ¥9.9/month for 60GB · ¥18/month for 250GB · ¥28/month for 500GB. Data packs: ¥158/300GB · ¥358/1000GB · ¥658/3000GB; data is valid until used and never expires. If you use the service regularly, compare monthly plans based on your browsing, video streaming, and file transfer habits. If your usage is less predictable, a data pack is another billing option. Do not estimate data needs from the number of devices alone; background syncing and streaming habits also affect usage. Check billing details on the plans page before choosing, then review your order in the user panel. Monthly plan reset rules do not apply to data packs, and data from different products should not be assumed to combine automatically.

Monthly plan data resets each month on the activation date. If you upgrade mid-cycle, the price difference is prorated based on the remaining days. Check your plan status and reset date in the panel; do not assume all accounts reset at the start of the calendar month. Before upgrading, review the target plan, price difference, and remaining term shown in the panel. Confirm the details before proceeding instead of estimating the result by subtracting full months. If the displayed information differs from what you expected after payment, keep the order status and on-screen message, then ask support to check through a ticket. Avoid creating duplicate orders. Data packs follow different rules: they remain available until used and never expire. If your account includes different products, check each product’s record in the panel rather than assuming how data is applied or reset.

WeChat Pay / Alipay / USDT are supported. Start the relevant payment process from the order page in the user panel, and check the amount and order status. Do not use payment details forwarded by someone else instead of the instructions in the panel. After paying, return to the original order to check its status, then refresh your plan details. If the payment page and panel do not match, keep your payment receipt and do not pay again or create duplicate orders. Submit the order details, payment method, payment status, and a screenshot through a panel support ticket so the payment can be checked against your account. Send receipts only through a trusted panel ticket. Hide transaction and account details in public discussions. The order record and support review determine the payment status; do not assume a processing time.

VPNKZ offers a 14-day no-questions-asked refund. To request one, open the support ticket section in the user panel, explain that you are requesting a refund, and include the relevant order details so the payment and plan can be checked. See the refund policy for eligibility and full terms. You do not need to prove that a route is faulty to request a refund; whether you also share feedback about your experience is up to you. Before submitting, make sure the ticket is linked to the order you want reviewed, and do not upload unrelated payment records or your full account credentials. Follow up in the same ticket and keep the replies and order status. Creating duplicate tickets will not speed up the process. The ticket replies and payment record determine the status and outcome; no arrival time is guaranteed.