Chrome Extension  ·  Privacy Policy

CueVPN Chrome extension, privacy policy.

Last updated: July 3, 2026

1. What the extension is

The CueVPN Chrome extension is a browser-only client for the CueVPN service. It routes Chrome traffic through a CueVPN exit node in Germany, Singapore, or the United States over HTTPS proxy. Traffic from other browsers or apps on your device is not affected.

2. What data the extension handles

To authenticate you and issue a short-lived proxy credential, the extension handles:

  • Your CueVPN account email and password at sign-in.
  • Access and refresh JSON Web Tokens returned by the CueVPN API.
  • A proxy username and password issued for you on-demand by the CueVPN backend.
  • The identifier of the server you selected.

3. Where that data lives

Tokens and credentials are stored locally in Chrome’schrome.storage.localon your device. They never leave your browser except in two situations:

  • API calls to api.cuevpn.com over HTTPS to sign in, refresh tokens, and request or revoke a proxy credential.
  • Basic-auth challenges from the exit node’s HTTPS proxy, where the extension replies with the issued proxy username and password.

4. What the extension does not do

  • Does not read the content of the pages you visit.
  • Does not log your browsing history, DNS queries, or the data of your traffic.
  • Does not send analytics, telemetry, or usage data to any third party.
  • Does not sell or transfer your data.
  • Does not modify pages you visit or inject scripts into them.

5. What CueVPN’s servers record

When you use the CueVPN service (via this extension or any other CueVPN client), the CueVPN servers keep short-lived operational records to enforce plan limits, detect abuse, and bill correctly. These records include the connection start and end time, the total number of bytes transferred, and which server you used. They do not include the sites you visited, the DNS queries you made, or the content of your traffic. Full details are in the main CueVPN Privacy Policy.

6. Chrome permissions used and why

  • proxy: to set Chrome’s proxy configuration to the CueVPN exit node.
  • storage: to persist your sign-in tokens and last-used server across popup opens.
  • webRequest and webRequestAuthProvider: to reply to the proxy server’s HTTP 407 authentication challenge with your issued credential.
  • Host permissions for api.cuevpn.com and api-staging.cuevpn.com: the extension only ever calls the CueVPN API, no third-party hosts.

7. Deleting your data

You can sign out of the extension at any time to clear the locally stored tokens and credential. Uninstalling the extension removes all its local storage from your browser. To delete your CueVPN account and the associated server-side operational records, email us at support@cuevpn.com.

8. Contact

Questions about this policy or the extension: support@cuevpn.com.