VPNPO Help Center

No email address is required. Create an account with a username and password, then store them in a trusted password manager. You’ll need the account to view orders, access your subscription, and submit support tickets. Don’t share your password or subscription link in public notes, group chats, or screenshots; your subscription link is also a credential and should be kept secure. If you can’t sign in, check your keyboard input, capitalization, and any spaces copied along with your details, then make sure you’re on the user dashboard. Follow the account recovery options actually shown there—don’t assume email recovery is available. Never include your full password in a support request.

Sign in to the user dashboard and look for your subscription options in the account overview. Import it into your client by following the dashboard instructions. To update your routes, refresh the existing subscription from the client’s subscription or configuration manager; disconnecting and reconnecting alone won’t update it. After refreshing, check that the configuration’s update time has changed and that the active configuration is the one you just updated. A client may store multiple configurations, so a successful update doesn’t necessarily mean you’re using the latest one. If the subscription option in the dashboard has changed, copy the current link again and update the client configuration. If the problem persists, note the client’s error message and the network you were using, and hide the full subscription link when submitting a support ticket.

VPNPO allows an unlimited number of devices to be online at the same time, so switching devices alone doesn’t require a new plan. Sign in to your existing account on the new device, check your plan and data balance, then get the client and subscription from the user dashboard. Import the subscription and verify the connection. Supported platforms are Windows / macOS / iOS / Android / Linux; client download access depends on what’s available in your dashboard. Unlimited devices doesn’t mean unlimited data, so keep an eye on your account’s data balance. Before handing off or retiring an old device, sign out and remove its local subscription configuration so no one else can access your subscription details. You don’t need a separate account to move to another device.

VPNPO’s no-logs policy is a service privacy commitment. It doesn’t mean your account credentials can be shared, or that websites you visit won’t keep their own login and activity records. Protect your account password, subscription link, and destination service accounts separately. When using international routes, your browser or other software still manages your login sessions, site permissions, and local history. For details on how VPNPO handles data, read the privacy policy; don’t interpret a privacy commitment as a guarantee of complete anonymity. When troubleshooting, you can share the client name, error message, and route name, but hide credentials and personal content. Don’t expose information unrelated to the issue just to explain what went wrong.

Disconnect the proxy first and check that your local network can reach familiar websites. If the local connection itself is having problems, fix that first. Then sign in to the dashboard to check your plan and data balance. Return to the client, refresh the subscription, confirm the current configuration is active, and check that your system has granted VPN or network proxy permissions. Temporarily quit other proxy tools that are managing your network, then compare routes in different regions. Change one setting at a time and note the result so you can identify the cause. If several routes fail on different local networks, collect the error message and your system and client details for a support ticket. Don’t repeatedly delete your account or share your subscription link publicly.

A connected status means the client has established a connection; it doesn’t guarantee that requests to a particular website are using the selected route. Open a few different sites to see whether all websites are affected or just one. Then check that your system proxy, browser proxy, and client rules are aligned. If other sites work, check the destination site’s regional requirements, your account status, and whether the client rules match. If no sites work, try another route and check your DNS settings. Prefer the client’s recommended configuration, and don’t add DNS rules from unknown sources. Keep a copy of your original configuration so you can restore it. After making changes, reload the site rather than relying on a cached page to determine whether the connection works.

First check whether app-based proxying is enabled in the client and whether the app is included in the list of apps that should use the proxy. Some settings use an allowlist and others a blocklist, so selecting the same app can have the opposite effect depending on the mode. Read the mode description carefully. In rule mode, check whether the app’s domain matches the expected policy. If needed, use the client’s connection logs to see where its traffic is going. You can temporarily switch to global mode to compare results, but restore your preferred routing once you’ve finished testing. The app’s account region, permissions, or service restrictions may also affect access. Changing network routes won’t necessarily change those conditions, and a connection icon alone doesn’t confirm that the app is using the proxy.

First distinguish a background connection drop from a subscription update failure. The former is often related to system background management; the latter may involve your local network, subscription link, or account status. If the connection drops in the background, check whether your system allows the client to run in the background. Adjust battery optimization and network permissions as described in your device settings, then test the target app again with the screen locked. If updates fail, bring the client to the foreground, confirm that your local network works, refresh the subscription, and read the specific error message. Repeatedly restarting the client won’t tell you much about the cause. Menu names vary by device, so don’t follow settings instructions that don’t apply to yours. In a support ticket, describe what happens before and after the screen locks, and include the update error so the two issues can be investigated separately.

Keep the purpose and test content the same—for example, continue playing content on the same platform—while comparing routes in different regions or of different types. Pause downloads and sync tasks that are using your local network, and check whether the slowdown happens only during peak hours. If it’s slow at other times too, check your local network and device as well. After switching routes, observe page response times, playback buffering, or app request results. Don’t draw conclusions from a single number in the client. IEPL, relay, and direct routes are useful comparison points, but route type alone doesn’t guarantee stability. If the issue continues, include the time, region, route name, intended use, and results from each route in a support ticket to help identify the bottleneck.

Start by choosing the destination region and intended use, then compare route types. IEPL uses a dedicated link, relay routes connect through an intermediate node, and direct routes use a direct connection path. These terms describe how traffic is routed; none is inherently better in every network environment. Compare routes using the same device, local network, and destination service, and check both responsiveness and sustained performance. For AI tools, see whether requests complete smoothly; for streaming, check playback and whether the detected region meets your needs. Keep the route that works best for your current use and have an alternative ready. Don’t choose a route based only on its label while overlooking the destination service’s regional requirements or changes in your local network.

VPNPO covers 90+ countries / 170+ routes, but coverage doesn’t mean every platform or title will be available. Choose a region that meets the platform’s requirements, then check your account’s region, content licensing, and how the platform identifies your current exit location. Browsers and apps may have different active sessions, so reopen the service and verify access after switching routes rather than relying on the route’s region label. If the platform reports a proxy restriction, compare other routes in the same region and note the message. Changing regions doesn’t automatically change your account entitlements. Streaming information on the routes page should be verified against the platform you want to use; retest your usual content if the platform changes its policies.

Not necessarily. First determine whether the error is due to a connection timeout, regional detection, or the destination platform’s account permissions or service status. Keep your account and the action you’re testing the same, then compare a route that meets the service’s regional requirements. Also confirm that the browser or app’s traffic is being handled by the intended client rules. If the site loads but a request fails, note the exact error and where it occurs rather than describing the issue generally as “not working.” The destination platform’s account eligibility, feature availability, and usage policies still apply; VPNPO’s network connection doesn’t replace those requirements. Don’t include account passwords, keys, or private conversations in a support ticket. Share only error details with sensitive information removed.

Monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on your activation date. Data packs are ¥158 for 300GB, ¥358 for 1000GB, and ¥658 for 3000GB. They last until used and never expire. Consider how regularly you use the service and how much data you need: a monthly plan’s reset schedule may suit frequent use of international sites, while a data pack may be worth comparing if you connect occasionally. The two options don’t have the same billing period, and a data pack that never expires is not unlimited data. Check your account status, plan activation, and remaining data in the user dashboard. See the plans page for full details before choosing.

Monthly plan data resets each month on your activation date, not necessarily at the start of the calendar month. Check your plan and data details in the user dashboard, and use the activation schedule shown for your account to determine the reset date. The client’s local usage statistics may not match the remaining data shown in your account. If you upgrade mid-cycle, the price difference is prorated against the remaining days. Check the order and plan status shown in the dashboard rather than estimating extra data or an extended billing period yourself. If your plan doesn’t look as expected after payment, make sure you’re viewing the right account and order, then describe the before-and-after status in a support ticket. Keep the order record; there’s no need to share all personal details from your payment receipt.

VPNPO supports Alipay / WeChat Pay / USDT. Available payment options are shown on the checkout page in the user dashboard. If your plan doesn’t appear after payment, check the order status on the orders page, refresh the account overview, and make sure you’re signed in to the account used to place the order. Don’t pay again just because the overview hasn’t updated, and don’t use the client’s connection status to determine whether the order is complete. If the payment service shows that payment is complete but the dashboard hasn’t updated, submit a support ticket with the order ID, payment method, payment time, and a receipt with personal details removed. For USDT payments, follow the details on the current checkout page exactly. Don’t use an old order screenshot or payment information forwarded by someone else.

VPNPO offers a 60-day refund policy. To request a refund, sign in to the user dashboard, open the support ticket section, explain your request, and include the relevant order ID. Check the Terms of Service for the eligibility requirements and full refund rules; don’t infer VPNPO’s process from another website’s policies. If you’re also reporting a connection problem, include your device operating system, client name, when the issue occurred, route name, intended use, error message, and steps you’ve already tried. This helps the support team understand what happened. Hide passwords, full subscription links, keys, and personal payment details in screenshots. Follow up in the same ticket and provide any requested information. There’s no need to open multiple tickets for the same issue; check the dashboard for the latest status.