SoftGlaze Proxy privacy policy

The short version: SoftGlaze Proxy keeps your proxies, logins, rules and keys in your browser’s storage on your computer, and sends nothing to SoftGlaze. It contacts outside services only for the jobs listed here, and the optional AI features send what you ask to the AI provider you choose.

Last updated 9 November 2026 · SOFTGLAZE (SMC-PRIVATE) LIMITED, a single member private company registered in Pakistan

The short version

Your proxies, their logins, your site rules, settings and keys stay in the browser’s storage on your computer. Nothing is synced.Read
Nothing is sent to SoftGlaze. There is no account, no analytics and no telemetry.Read
Every outside service the extension can contact is in a table below, with when and why.Read
In Firefox, the install prompt lists what the extension sends outside the browser, and Firefox asks before the AI assistant sends your first message.Read
A proxy provider key goes only to that provider’s own API, straight from your connection.Read
The AI assistant is off until you turn it on. The AI provider you choose receives what you type and the tool results, never passwords, proxy usernames or keys.Read
AI apps reach the extension only through the bridge on your computer, after you pair it.Read
Its use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.Read

Who is responsible

SoftGlaze Proxy (“SoftGlaze Proxy Switcher: Free Proxies, Per-Site Rules & AI Assistant” in the Chrome Web Store and Microsoft Edge Add-ons, “SoftGlaze Proxy Switcher” in Firefox Add-ons) is made by SOFTGLAZE (SMC-PRIVATE) LIMITED, a single member private company registered in Pakistan (SECP CUIN 0335492), the company that makes SoftGlaze Browser. It is responsible for the extension and for this policy. Its registered office is Rehmania Colony, Chak No. 86/M, Khan Bela Road, Jalalpur Pirwala, Multan Cantt., Punjab 59250, Pakistan.

Privacy questions and data requests go to legal@softglaze.com. Help with the extension goes to support@softglaze.com.

This policy covers the extension, version 1.0.0, in Chrome, Microsoft Edge and Firefox, and the SoftGlaze Proxy Bridge that lets AI apps use it.

What stays on your computer

The extension keeps everything in the browser’s own extension storage on your computer: chrome.storage.local, which lasts until you remove the extension, and chrome.storage.session, which is emptied when the browser closes. Its pages also remember a few display choices in their own page storage (the last row of the table). It never uses the browser’s sync storage, so nothing is copied to your browser account or to other computers, and we have no copy of any of it.

Firefox keeps the same data in its own extension storage, under the same names. The table names each storage key the extension uses.

What the extension keeps, and where
What	Where	Details
Your proxies and settings	chrome.storage.local, “state”	Proxies and their logins, groups, site rules, the failover list, the “Never use a proxy for” list, the last test of each proxy (with its exit IP and the place the IP service gives for it), and your settings.
Proxy provider keys	chrome.storage.local, “providers”	The key or login you enter on the Providers page. Kept apart from your proxies, never in an export, and shown on the extension’s pages only masked.
AI assistant settings and keys	chrome.storage.local, “ai” and “aiKeys”	Your choice of provider and model, and the key you enter. The key is kept apart from your proxies, never in an export, and shown only masked.
The bridge pairing	chrome.storage.local, “bridge”	Whether AI apps may connect, the folder you typed, and the secret made when you paired. Never exported and never shown on a page.
The AI activity log	chrome.storage.local, “aiLog”	What the assistant and AI apps asked, each tool they used, your decision and the outcome. The last 500 entries, no keys. You can read and clear it in Settings.
The AI conversation	chrome.storage.session, “ai.chat”	Gone when the browser closes, or when you press New chat.
Sites a proxy refused	chrome.storage.session, “proxyRefusals”	When a page fails through any of your proxies and the extension’s own check finds that the proxy refuses only that site (an “access denied” page of the proxy’s own, a secure connection refused while plain http gets an answer, or the login refused only there), the site’s name, kept for that proxy (by its address and port) only to tell you in the popup and in the proxy’s details. At most 5 sites per proxy, gone when the browser closes.
Proxies cooling off	chrome.storage.session, “proxyCooldowns”	When the extension’s own check finds that a proxy does not work for any site (it refuses its login, gives no proper answer, or denies every site): that proxy’s id and name, the reason (login, broken or denied), when its 10-minute pause ends, and how many times it happened. Failover lists and rotating groups skip it until then. A passing test, an edited proxy or “Try it now” ends the pause, and it is gone when the browser closes.
Short-lived status	chrome.storage.session: “run.check”, “run.free”, “ai.pending”, “ai.grants”, “bridge.pairing”, “bridge.status”, “lastProxyError”, “badge”, “overlayActive”, “controlLevel”	Test and free-proxy search progress, waiting approvals, 1-hour permissions, a pairing code while it is valid, whether the bridge is connected, the last proxy error, what the toolbar badge shows, whether a test is using its own routes right now, and whether the browser lets the extension set the proxy. Gone when the browser closes.
Display choices	The extension pages’ own localStorage and sessionStorage	A copy of your theme choice for the first paint, whether the AI settings open on “I have an API key” or “I pay for an AI plan”, and, for the current tab only, the settings section you came from (for the Back button on My IP and leaks).

An export is a file you make and save yourself, from Import and export. It includes your proxy passwords unless you untick “Include passwords”, and it never includes provider or AI keys.

To remove everything, remove the extension from the browser: the browser deletes its storage with it. The AI activity log can also be cleared on its own, in Settings. If you used the bridge, delete the softglaze-proxy-bridge folder and its pairing file (where that file is kept is under AI apps and the bridge).

Data the extension handles

The Chrome Web Store and Microsoft Edge Add-ons ask which kinds of user data an extension handles, even when the data stays on your computer. For SoftGlaze Proxy there are three, and none of them is sent to SoftGlaze.

Authentication information. The proxy usernames and passwords, proxy provider API keys or logins, and AI provider API keys that you enter. They are kept only in chrome.storage.local on your computer. A proxy’s login is sent only to that proxy, when it asks for it. A provider or AI key is sent only to that provider’s own API, is never in an export, and is shown on the extension’s pages only masked.

Personal communications. Only if you turn on the AI assistant: what you type to it is sent to the AI provider you chose, with the results of the tools it uses. With Ollama it stays on your computer. The conversation is kept in chrome.storage.session and is gone when the browser closes, or when you press New chat.

Location, as an IP address. To show you what sites see, and to check that a proxy doesn’t reveal your real IP, the extension reads your own IP address with one plain request, sent without any proxy, to checkip.amazonaws.com (or to ifconfig.me, only if that gives no proper answer). The request carries nothing but the request itself. On the My IP page, and when the AI assistant or an AI app checks the IP, it also asks ipinfo.io or get.geojs.io for your own country, over a secure connection and again without any proxy. For each proxy it tests, it reads the proxy’s exit IP from the same plain services, and its country and the place the IP service gives for it (region, city, postal code, network and time zone, when the service knows them) from ipinfo.io or get.geojs.io, through that proxy. All of this is shown to you on your computer. Your own IP and country are kept in the extension’s memory for a few minutes (up to 5) and are never saved; a proxy’s exit IP and place are saved with that proxy’s test result in chrome.storage.local.

What it does not handle:

Names or email addresses. None are asked for, and there is no account. A provider login that happens to be an email address is kept as a login, as above.
Payment details. Getting proxies from Proxy302, which sells each proxy, spends your own Proxy302 balance through Proxy302’s API, after you confirm. The extension never sees card or bank details.
Browsing history. No list of the pages you visit is kept. The popup reads the site name of the current tab to offer a site rule, and keeps it only if you add that rule. When a page fails through your proxy with a proxy error, the extension checks why with requests of its own (see the check after a failed page). If the proxy refuses only that site, the site’s name is kept for that proxy in chrome.storage.session, at most 5 per proxy, only to tell you in the popup and the proxy’s details; it is gone when the browser closes. Nothing else about failed pages is kept.
Page content. The extension has no content scripts and never reads or changes the pages you visit.

In Firefox

Firefox asks a different question: what an add-on sends outside the browser, even to a service you chose. It shows the answer when you add the add-on. The Firefox version of SoftGlaze Proxy (Firefox 140 or newer) declares:

Authentication information, needed to work. A proxy’s login goes to that proxy when it asks, a provider key or login to that provider’s API, and an AI key to the AI provider you chose.
Browsing activity, needed to work. With the proxy on, the proxy you chose receives the sites you open: that is what a proxy does. When a page fails through that proxy with a proxy error, the extension also asks that site once more through the same proxy, over https and plain http (below).
Personal communications, optional. Only for the AI assistant: what you type goes to the AI provider you chose. Firefox asks you to allow this when you turn the assistant on, and the assistant sends nothing until you do. With Ollama it stays on your computer.

It does not declare location: the IP lookups above send nothing but the request itself. None of this goes to SoftGlaze, in any browser.

Every outside service it contacts

This is the same list the extension shows in Settings, “Where it connects”, and the extension’s own tests fail if its code uses a host that is missing from it. None of these services belongs to SoftGlaze. Each one sees the request and the IP address it comes from: yours, or the proxy’s for a request sent through a proxy. Each handles that under its own privacy terms.

One more party can see where you go if you use a SOCKS4 proxy in Chrome or Edge. SOCKS4 has no password, and those browsers look up site names on your computer before using it, so your DNS server can see the sites you visit. The extension offers SOCKS4 with that warning and suggests SOCKS5 or HTTP. In Firefox, SOCKS proxies (SOCKS4 too) look up site names themselves.

The check after a failed page. When a page you opened fails through one of your proxies with a proxy error (a refused login, a refused secure connection, or no proper answer), the extension finds out whether the proxy refuses only that site or does not work at all. It makes up to three requests of its own, all through that same proxy: first Google’s connection check over plain http (left out if the proxy passed it in the last 5 minutes); if that works, the site’s front page over https, and then over plain http. Plain http is not encrypted, so that request can be read on its way through your proxy, as any plain-http page can; it carries no cookies and nothing from you, only a random check code in the address. If the proxy refuses only that site, the site is noted for that proxy, as above. If it fails Google’s check too (it refuses its login, gives no proper answer, or denies every site), failover lists and rotating groups skip it for 10 minutes. Each proxy and site is checked at most once every two minutes, and at most 20 checks run in 10 minutes. Nothing about it goes to SoftGlaze.

Where the extension connects
Service	Why	When
Your own proxies	The proxies you add or choose. Your browsing goes through them while the proxy is on, and tests send small requests through them.	While a proxy is on, and when you test one
`ipinfo.io`	Shows the IP address, country and, when it knows them, region, city, postal code, network and time zone a proxy gives you, over a secure connection. During a test only the test request goes through the proxy. On the My IP page, and when the AI assistant or an AI app checks your IP, it can also be asked once without any proxy, for your own country.	Tests, free-proxy search, the My IP page
`get.geojs.io`	A second IP and country service, so two proxies can be tested at the same time (and, like ipinfo.io, for your own country).	Tests, free-proxy search, the My IP page
`checkip.amazonaws.com`, `ifconfig.me`	Answer with nothing but the IP address a plain (not secure) request comes from. A test sends one through the proxy to read its exit IP (ifconfig.me first, because some providers refuse Amazon Web Services addresses, then checkip.amazonaws.com), and one without any proxy so the anonymity check knows your own IP (checkip.amazonaws.com, and ifconfig.me only when it gives no proper answer).	Tests, free-proxy search, the My IP page
`httpbin.org`	Echoes back the headers an HTTP proxy adds, which shows whether the proxy reveals your real IP.	Tests of HTTP and HTTPS proxies, free-proxy search
`connectivitycheck.gstatic.com`	Google’s tiny connection check, to see that a proxy can reach ordinary sites, and that a proxy still works for them when a page failed through it.	Tests, and after a page failed through a proxy
A site your proxy seems to refuse	When a page you opened fails through your proxy with a proxy error, that site is asked once more through the same proxy (over https and plain http), to tell a site the provider refuses from a proxy that does not work at all. At most once every two minutes per site, and nothing else is sent.	After a page failed through a proxy
`dns.google`	DNS-over-HTTPS lookups that ask the Spamhaus, SpamCop and Barracuda blocklists whether a proxy’s IP is listed. Only the proxy’s IP is looked up.	Tests
`api.proxyscrape.com`, `proxylist.geonode.com`, `raw.githubusercontent.com`, `cdn.jsdelivr.net`	Public free-proxy lists (ProxyScrape, Geonode, the monosans list on GitHub, the Proxifly list on jsDelivr). Read as plain lists of addresses, never run as code.	Only when you search for free proxies
Free proxies from those lists	Each candidate gets a few test requests before it is offered to you. Free proxies are run by strangers.	Only when you search for free proxies
Proxy provider APIs (23), listed in the next table	Only the provider you connect on the Providers page: to check your key and get your proxies. Your key goes only to that provider’s own API. These calls go straight from your own connection, never through a proxy: for the few seconds of each call, that one address skips your proxy, and then your setting is put back exactly as it was. At all other times a tab you open to that address uses your proxy like any other site.	Only when you press “Test key” or “Get proxies” on the Providers page
AI provider APIs (3): `api.anthropic.com` (Anthropic), `api.openai.com` (OpenAI), `generativelanguage.googleapis.com` (Google Gemini)	Only the one AI provider you choose for the AI assistant (Anthropic, OpenAI or Google Gemini), with your own key. It receives what you type and the results of the tools it uses (proxy names, addresses, countries and test results), never passwords, proxy logins or keys. These calls always go straight from your own connection, never through a proxy.	Only when the AI assistant is on and you use it, or press “Check the connection”
Ollama on this computer	If you choose Ollama for the AI assistant, the chat goes to Ollama on your own computer (127.0.0.1 or localhost, port 11434 unless you change it) and nowhere else.	Only when the AI assistant uses Ollama
SoftGlaze Proxy Bridge on this computer	Lets AI apps on your computer (Claude Desktop, Claude Code, Codex CLI, Antigravity CLI, VS Code, Cursor, Gemini CLI) use the extension, on 127.0.0.1 ports 47615 to 47617. The connection never leaves your computer; the AI app sends its requests to its own AI provider.	Only when “Let AI apps connect” is on
`stun.l.google.com`	A WebRTC check (STUN) that shows which IP addresses WebRTC would reveal to a site.	Only on the My IP and leaks page

The proxy provider API hosts

The extension can call these 23 addresses, and only the ones of the provider you connect. Its connectors refuse any other address.

Proxy provider API hosts (23)
Host	Provider	Note
`*.liveproxies.io`	Live Proxies	Only for a plan list link you paste
`airproxy.io`	Airproxy
`api.brightdata.com`	Bright Data
`api.coronium.io`	Coronium
`api.gsocks.net`	Gsocks
`api.marsproxies.com`	MarsProxies
`api.proxidize.com`	Proxidize
`api.proxies.sx`	Proxies.sx
`backend.mangoproxy.com`	MangoProxy
`catproxies.com`	CatProxies
`dashboard.anyip.io`	AnyIP	Only when an API key and Team ID set up the proxy login
`gw.dataimpulse.com`	DataImpulse	On port 777
`liveproxies.io`	Live Proxies	Only for a plan list link you paste
`mpsapi.com`	MobileProxy.Space
`proxmint.com`	Proxmint
`proxy-seller.com`	Proxy-Seller
`proxy-solutions.net`	Proxy-Solutions
`proxy302.com`	Proxy302
`proxybonanza.com`	Proxy Bonanza
`px6.link`	PROXY6
`resi-api.iproyal.com`	IPRoyal
`shopsocks5.com`	ShopSocks5
`singaporemobileproxy.com`	Singapore Mobile Proxy

Links only

These addresses appear only as links. They open in a new tab when you click them; the extension never connects to them or sends them anything by itself. The Providers page also links to each provider’s own website, dashboard and documentation.

browser.softglaze.com, azhar.softglaze.com: SoftGlaze: the extension’s web page, privacy policy, support, setup guides and the bridge download, and the developer’s site (the links at the bottom of each page).
platform.claude.com, platform.openai.com, aistudio.google.com, docs.ollama.com: Where to get an AI key, and Ollama’s notes (AI assistant settings).
modelcontextprotocol.io, code.claude.com, learn.chatgpt.com, antigravity.google, code.visualstudio.com, cursor.com, geminicli.com: Each AI app maker’s own setup guide (AI apps settings).

Proxy providers

When you connect a proxy provider on the Providers page, the key or login you type is kept in chrome.storage.local under “providers”, apart from your proxies. It is never in an export, the extension’s pages only ever show it masked, and it is sent only to that provider’s own API hosts in the table above.

Those calls go straight from your own connection, never through a proxy, so the provider sees your own IP address, which is what its account checks expect. Only that exact address skips your proxy, and only for the few seconds of the extension’s own call; then your setting is put back exactly as it was. Several of these addresses are also the provider’s website (for example proxy-seller.com, airproxy.io, catproxies.com and proxy302.com): a tab you open to one of them uses your proxy before and after, like any other site.

“Test key” never buys anything. Getting proxies from Proxy302, which sells each proxy, asks you every time before it spends. The proxies a provider gives you are saved with your other proxies. What the provider does with your account and requests is covered by its own terms and privacy policy.

The AI assistant

The AI assistant is optional and off until you turn it on in Settings, AI assistant, under “I have an API key”. You choose one provider: Claude (Anthropic), OpenAI or Google Gemini with your own API key, or Ollama running on your computer. When you save a key and “Check the connection” works, the assistant is turned on.

The other choice there, “I pay for an AI plan”, sends nothing anywhere: it shows which AI app works with your plan, and that app connects through the bridge (below). Anthropic does not allow other products to sign in with a Claude plan, so the built-in assistant takes API keys only.

What the provider receives: what you type, and the results of the tools the assistant uses (proxy names, addresses, countries and test results). Never passwords, proxy usernames or keys: a login is masked even inside a proxy’s name, and the chat warns you before you send something that looks like a key or password.
Where it goes: only to the provider you chose (api.anthropic.com, api.openai.com, generativelanguage.googleapis.com), always straight from your own connection, never through a proxy. With Ollama the chat goes to 127.0.0.1 or localhost and stays on your computer. “Check the connection” only asks the provider for its list of models.
Your key: kept in chrome.storage.local under “aiKeys”, apart from your proxies, never in an export, and shown only masked. Only the extension’s background worker sends it, and only to that provider.
Your approval: the assistant reads at once, but anything that changes your proxy setting waits for you: Allow once, Allow for 1 hour, or Deny. Every request, tool call and decision goes into the AI activity log in Settings (the last 500 entries, with no keys), which you can clear.
The conversation: kept in chrome.storage.session, gone when the browser closes or when you press New chat.
In Firefox: the assistant opens in the sidebar, and Firefox asks you to allow it to send your messages to the AI provider before the first one. Until you allow it, nothing is sent.

The provider handles what it receives under its own privacy terms and your agreement with it, not this policy. Read them before you turn the assistant on.

AI apps and the bridge

AI apps on your computer (Claude Desktop, Claude Code, Codex CLI, Antigravity CLI, VS Code with GitHub Copilot, Cursor, Gemini CLI) can use the extension through the SoftGlaze Proxy Bridge, a small program you download and run with Node.js. It is optional: nothing connects until you turn on “Let AI apps connect” in Settings, AI apps (MCP), and pair the bridge.

Local only. The bridge talks to the AI app over stdio and to the extension on 127.0.0.1, ports 47615 to 47617. Only a browser extension can connect to it (in Chrome, Edge or Firefox), never a web page, and after pairing only the paired extension. Nothing goes to SoftGlaze.
Pairing. A one-time code that works once, for 10 minutes. Neither the code nor the secret made from it crosses the connection. The secret is kept in chrome.storage.local under “bridge” and in the bridge’s pairing file: %APPDATA%\SoftGlaze\proxy-bridge.json (Windows), ~/Library/Application Support/SoftGlaze/proxy-bridge.json (macOS) or ~/.config/softglaze/proxy-bridge.json (Linux).
What the AI app’s provider receives. The AI app sends its requests to its own AI provider. That provider receives what the app asks and the tool results (proxy names, addresses, countries and test results), never passwords, proxy usernames or keys. The app and its provider handle that under their own terms.
The same approvals. Every change an AI app asks for opens an approval window first, and every call goes into the same AI activity log.

Permissions

When you add the extension, Chrome and Edge warn that it can “Read and change all your data on all websites” (from the proxy permission and host access) and “Change your privacy-related settings” (from the privacy permission). Firefox words its warnings its own way and also shows the data it may send (In Firefox). This is what each permission is for.

Permissions and why the extension needs them
Permission	Why
`proxy`	The core feature: sets the browser’s proxy (one proxy, per-site rules, failover) and gives the setting back to the browser when you turn it off. It also hears about a broken proxy, to show it on the toolbar badge.
`storage`	Keeps your proxies, logins, groups, site rules and settings in the browser’s storage on your computer, and short-lived test progress for the session.
`webRequest`	Needed together with the next permission to answer a proxy’s username and password request. It also listens for requests that fail (onErrorOccurred, which reports only the address and the browser’s error code). When a page fails through your proxy with a proxy error, the extension checks that proxy with requests of its own, to tell you that the provider refuses that site, or to skip a proxy that does not work for 10 minutes. It never blocks, changes or reads the content of page requests.
`webRequestAuthProvider`	Lets the extension sign in to HTTP and HTTPS proxies that need a username and password. Only a proxy’s sign-in request is answered.
`privacy`	Only for the WebRTC leak protection switch, which is off until you turn it on. Turning it off clears the setting again.
`contextMenus`	The right-click item “Open this site through...”, which adds a site rule for the page’s site.
`alarms`	Rotation: moves to the next working proxy in a group every few minutes (1 minute or more). When AI apps may connect, a 30-second alarm also reconnects to the bridge on your computer.
`sidePanel`	Shows the optional AI assistant in the browser’s side panel. The assistant is off until you turn it on. Firefox has no side panel: there the assistant opens in the sidebar, and the Firefox version does not ask for this permission.
Host access to all sites	A proxy asks for its password on whatever site you open, and the browser only lets an extension answer for sites it has access to (in Firefox, also to choose the proxy for each site). The same access reads the test services’ answers during a proxy test and reaches the APIs listed above. There are no content scripts: the extension never reads or changes the pages you visit.

No telemetry

The extension sends nothing to SoftGlaze, and there is no SoftGlaze server it talks to. It has no analytics, no telemetry, no crash reports and no advertising, and it runs no code from outside its package: proxy lists, provider answers, test answers and AI answers are read as data, never run. We don’t sell or share data, because we never receive any.

This website

Reading these pages or downloading the bridge from browser.softglaze.com shows up in our hosting provider’s ordinary web-server logs, like any visit to this site. The website’s privacy notice explains those logs under This website.

Limited Use

SoftGlaze Proxy’s use of information complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

In practice: the data described here is used only to switch and test your proxies and to run the AI features you turn on. It goes to a third party only when you ask for it (a proxy you use, a provider you connect, the AI provider you choose). It is never sold, never used for advertising or to decide creditworthiness, and nobody at SoftGlaze reads it, because none of it reaches us.

Age

SoftGlaze Proxy is for people aged 18 or over. We don’t knowingly hold data about children, and the extension isn’t designed for them. Because it sends us nothing, we hold no data about anyone who uses it, children included.

Changes to this policy

If this policy changes, the date at the top changes with it. A version of the extension that keeps something new or contacts a new service comes with an updated policy, and the list in Settings, “Where it connects”, changes in the same version.

Contact

Write to legal@softglaze.com about privacy and data requests, and to support@softglaze.com for help with the extension. You get a first reply within one business day, Monday to Friday.

Because the extension sends us nothing, we have no extension data about you to copy or delete: whatever it keeps is on your computer, and removing the extension removes it. If you email us, we keep your email as the website privacy notice describes.