Privacy Policy

Last updated: 2026-06-29

This Chrome extension (Proxy Settings) is built to keep your data on your machine. This page describes exactly what the extension does and does not do with your information.

Data we collect on our servers

None. We do not operate any servers, telemetry pipeline, or analytics collection for this extension. We have no way to identify you, track your usage, or read your proxy list.

Data stored locally on your device

The extension persists the following to your browser’s chrome.storage.local namespace. It is never transmitted off your device by the extension itself, and uninstalling the extension removes it.

• The list of proxies you have added (hostnames, ports, optional usernames and passwords).
• Which proxy you currently have selected, and whether the master switch is on or off.
• Your sort preference for the list (“Recent” or “Type”).
• The most recent connectivity-test result per proxy (visible egress IP, country code, latency, success/failure timestamp).

If you have saved a proxy with credentials, those credentials are kept verbatim in chrome.storage.local so the extension can supply them in response to HTTP 407 proxy-authentication challenges. They are not encrypted at rest by the extension itself — Chrome’s own profile encryption is what protects this data.

Network requests made by the extension

The extension performs exactly one type of outbound network request on its own behalf:

When you tap Test on a proxy, the extension sends a single HTTPS request to https://ipwho.is/ through the proxy under test, to read back the visible egress IP and country code. The response is stored locally for display in the popup and is not transmitted anywhere else.

ipwho.is is a third-party service we do not operate. Their privacy practices apply to that request — refer to https://ipwho.is for details. If you do not want any third party to receive a request from the extension, simply do not tap the Test button.

All other network traffic Chrome makes while a proxy is active is the result of your own browsing — the extension does not initiate it, inspect it, log it, or transmit it.

Permissions used and why

Permission	What it’s for
proxy	Apply your selected proxy server to Chrome’s network settings.
storage	Save your proxy list, sort preference, and last-test result locally.
webRequest	Detect HTTP 407 (Proxy Authentication Required) responses.
webRequestAuthProvider	Programmatically reply to 407 challenges with the credentials you saved against the active proxy, so Chrome does not pop up an OS auth dialog on every request.
Host permission <all_urls>	The selected proxy applies to every URL; 407 challenges may originate from any host. The extension does not read or modify page content on any site.

Children’s privacy

This extension is not directed at children. We do not knowingly collect data from anyone, including children. The extension does not collect data at all.

Changes to this policy

Material changes to this policy will be reflected in the Last updated date at the top of this document and announced in the extension’s release notes on the Chrome Web Store.

Contact

For questions about this policy or the extension, please open an issue on the project’s source repository (link in the Chrome Web Store listing or the website footer).