Browser extension privacy

Updated 1 November 2026 · Extension version 2.0.4

This notice explains how QuanticData Proxy Manager and Quantum Proxies Manager handle data when you connect Chrome to your proxy plans. It covers account access, information kept on your device, connection checks, site rules and the optional Extract page tool. Account, billing and service-side processing remain subject to the applicable brand’s main privacy policy linked below.

Account and proxy access

The extension uses your existing dashboard session or an API key to retrieve your account’s plans, available balance and proxy credentials. An existing dashboard session can also supply your account name or email for the sign-in interface. The extension does not ask for your account password or payment-card details.

Account requests go to the selected brand’s dashboard API over HTTPS. Proxy usernames and passwords are supplied to the proxy endpoint you choose when it requests authentication. The extension configures Chrome’s proxy settings; it is not a device-wide VPN. Transport to a proxy follows the selected endpoint’s protocol, and HTTPS websites retain their own browser TLS connection.

Information stored locally

• Your API key, proxy connection and custom proxy details, cached plans and IP inventory.
• Connection preferences, location targeting, site routing rules and recent IP/country checks.
• The most recent 50 connection events. These can include relevant domain names, IP addresses, times, response codes and connection errors.

Version 2.0.4 encrypts these local records with AES-256-GCM. A non-extractable key is kept in the extension’s browser-profile IndexedDB storage. Older local records are migrated on startup. Live proxy-authentication data also uses Chrome’s in-memory session storage. This does not protect data from someone who controls your operating system or can run code inside your browser profile.

Signing out removes the saved API key, active connection and cached plans/IP inventory, and clears live session credentials. Preferences, site-rule definitions, the event history and a manually entered custom proxy may remain on the device. Removing the extension removes its browser-managed local storage; any proxy strings or files you copied or downloaded remain where you saved them.

Site rules and connection monitoring

The extension handles the active tab’s URL and hostname to display and apply site rules. It observes main-frame connection failures and certain HTTP response codes to show a connection problem or perform optional IP replacement. Relevant hostnames can be retained in the bounded local event history.

It does not use Chrome’s browsing-history API or upload a general browsing-history log. It does not read form input, passwords typed into websites or request bodies. User-selected site rules and bypass lists stay on the device. The account dashboard, localhost and configured bypass destinations are routed directly.

IP and country checks

Connection checks contact Cloudflare trace endpoints, api.ipify.org and, when needed, icanhazip.com or ipinfo.io. Each service sees the IP address making that request: your direct IP or the proxy’s exit IP, depending on the check. These requests do not include your account API key or proxy password.

The extension uses the returned IP and country to show the connection state and compare direct and proxy addresses. Cloudflare’s network location is not presented as the IP’s city. Plans that authenticate by source IP may send your direct public IP to the account API to add it to that plan’s allowlist. These functions do not request GPS access.

Optional page extraction

Only when you select Extract page, the active page URL is sent to the brand’s Data API. The API fetches the page and returns text or Markdown for you to view, copy or download. Website content and the selected URL are therefore processed for this requested feature. Your logged-in page DOM, browser cookies and form input are not uploaded by this tool. API usage and service-side retention follow the applicable main privacy policy.

Why Chrome requests permissions

Proxy permission configures and clears browser routing. Privacy permission controls optional WebRTC protection while a connection is active. Storage saves the records described above; alarms support optional timed IP rotation; notifications report connection events; sidePanel displays the interface. WebRequest and webRequestAuthProvider handle proxy authentication and connection errors across the sites you choose to visit. No remote executable code is downloaded.

Limited use and sharing

Data handled by these extensions is used for the proxy-management features described here, including requested diagnostics and page extraction. It is not sold, used for advertising, used to determine creditworthiness or transferred for unrelated purposes. Transfers are limited to providing the requested service, security needs or legal requirements. This use follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

The extension package contains no advertising SDK, session-replay system or automatic browsing-history analytics upload. The websites’ separate analytics and cookie settings are described in their main privacy policies. Notifications and optional WebRTC protection can be changed in the extension settings.

Contact and account rights

For the identity of the applicable service operator, account retention and access, correction or deletion requests, see the QuanticData privacy policy or QuantumProxies.io privacy policy.

Contact hello@quanticdata.io for QuanticData or support@quantumproxies.io for QuantumProxies.