FAQ

No. Residential describes the type of exit network; return-to-China describes the connection direction. Choose the option for your purpose, and do not assume every return route is residential.

Start with the separate mainland-return option, where your app and account offer it. Choose residential IP when the exit network needs to be residential, not merely because you want to connect back to China. Check the destination's own access requirements; neither choice guarantees access to a particular service.

Use a signed-in account eligible for the route you select. Shared residential options and the separate mainland-return option can have different membership requirements; check the current app and subscription information.

Residential supply changes as participating connections become available. Check the current options for your account; the mainland-China return option is listed separately.

Check that you are signed in, review your current membership and confirm that your app supports the option. Residential destinations depend on participating connections being available; mainland return is a separate offering. If the option is still missing, contact support rather than assuming a different route is equivalent.

First check whether you selected the route for your purpose. Then check the destination service's account and region requirements and keep its security checks enabled. If the issue continues, send support your app version, operating system, selected option and error message. Do not send passwords, sign-in codes, tokens or private browsing records.

Smart Routing refers to rules that can choose a connection path for a destination. This is different from automatic server selection, which chooses a server. Availability depends on the app and version; choosing a server automatically does not by itself establish country-based traffic splitting.

Where these modes are supported, Global is intended to send app-managed traffic through the selected service connection, while Smart can choose paths by destination using routing rules. Exceptions and traffic coverage depend on the app and settings. A mode name alone does not mean all traffic on the device is covered.

No. A website's language or apparent location is not enough to determine its connection path. Where destination-based routing is supported, the active rules and exceptions determine the route. Do not assume that every local site connects directly or every overseas site uses the service connection.

Where domain filtering is available, it can block requests that match the active rules. It does not guarantee that every ad, cookie or fingerprinting method is blocked. Coverage depends on which traffic the filter handles; filtering alone does not guarantee faster browsing.

If your app shows a blocked-request counter, treat it as the app's reported activity within its filtering scope. Units and reset behavior can vary by app and version. A count is not a count of people tracking you, and zero is not proof that no tracking occurred.

If your app provides a filtering control, use its current settings and help. Menu names and supported modes vary; do not assume every app has the same switch. Turning one filter off does not necessarily mean other network rules or protections are disabled.

'Via Tunnel' labels traffic counted by the app for the service connection. Statistics describe what the app can measure; they are not a privacy audit or proof that every connection on the device follows the same path. Labels and statistics support vary by app and version.

'Direct' means a request uses the device's regular internet connection rather than the KazeGo service connection. Available counters and traffic coverage vary by app; a Global label is not proof that other device traffic cannot go direct.

A zero counter does not by itself mean no data was transferred. Check the connection status and what the app's counters measure. If you have used the connection but the counter stays at zero, contact support with your app version and operating system; do not include passwords, tokens or private browsing history.

No. Availability, defaults and controls depend on the app, operating system and version. Check the options actually shown on your device. A protection label alone is not a guarantee that all device traffic will be blocked after a disconnection.

Use the options actually offered by your installed app and follow its current setup guidance. Do not infer a security ranking, extra encryption layers or speed from an option's name alone. If you are unsure, ask support with your app version and operating system; never send passwords or tokens.

Reconnection behavior depends on the app, operating system and settings. Check the current connection status after a network change or interruption. Do not assume that all traffic is blocked while reconnecting or that every app has the same interruption protection. If you need to prevent network access, use your device's network controls instead of treating a reconnect label as a guarantee.

If your app offers automatic server selection, you can start there. For manual selection, consider the current available locations and latency. Lower latency does not guarantee higher download speed or access to a particular service. Selection controls vary by app and version; check currently available locations in your app.

On first connect, macOS requires you to approve KazeGo's network extension. The system notification only shows for a few seconds — if you missed it, KazeGo keeps waiting. 1. Open System Settings → General → Login Items & Extensions. 2. Scroll down to Extensions, click ⓘ next to Network Extensions, and turn on KazeGo Tunnel. Confirm with your password or Touch ID. 3. Return to KazeGo and click Connect. If macOS asks to add a configuration, click Allow. On macOS 14 or earlier: System Settings → Privacy & Security → click Allow at the bottom. Still stuck? Make sure KazeGo is in your Applications folder (not run from the DMG), then quit and reopen it. You only need to approve once.

If your app includes a route lookup, use it to inspect a routing decision for a domain or address. Available inputs and controls vary by app. A lookup result is not a trace of an actual connection and does not prove that a website is reachable.

A result may indicate a service path, a direct path or a block decision under the tested rules. Labels and details vary by app. An IP address, if shown, is not proof of a successful connection; use the result together with the current settings and connection status.

KazeGo provides connection apps for phones, computers and TV, with available downloads on the Download page. Features, settings and connection coverage can differ by app and version; do not assume a feature mentioned here is available on every device.

Registered devices, simultaneous connections and data usage are different measurements. Check your account's current membership details for any applicable limits or trial eligibility. Do not infer one limit from another.

We do not log what you do while connected. We never collect browsing history, DNS queries, records linking your account to destinations, or traffic content. Our servers briefly retain ordinary access logs, including the request network address and arrival time, only for security and abuse prevention.

Use the Download page to find current apps for your phone, computer or TV. Review any listed operating-system and processor requirements before installing. Available features and settings may differ between apps.