Easy Proxy — Privacy Policy

Easy Proxy is a Chrome extension that lets you save proxy servers, pick a free one, and switch Chrome's connection to them. This page explains what data it handles and why.

What Easy Proxy stores

Everything you enter — proxy name, host, port, protocol, username, password — is stored only in chrome.storage.local, on your own device. It is never sent to us, to our servers, or to any third party by the extension itself. Saved passwords are never shown back in the UI after you save them.

What Easy Proxy sends over the network, and to whom

• To the proxy you choose to connect to — once you turn a proxy ON, Chrome routes your browsing traffic (for that profile) through that server, exactly like any VPN/proxy app. That server is operated by whoever you configured — yourself, or the operator of a proxy you picked from the Free tab — not by us. Trust that operator the way you would trust any proxy/VPN provider.
• Free proxy list — to populate the Free tab, the extension fetches a list of candidate proxies from our own checker service (zevz.ru/extensions/EasyProxy) and, as a fallback if that is unreachable, from two public lists (proxylist.geonode.com, raw.githubusercontent.com). These are plain GET requests for a list of servers — no personal data, browsing history, or identifiers are sent in them.
• Exit IP / country lookup — after you connect, the extension asks a lookup service (ipwho.is, ipapi.co, or api.ipify.org) what your new exit IP and country are, so the popup can show you "Connected — Germany 123.45.67.89". This request goes out through the proxy you just connected to, not directly from you; we don't log or store the result anywhere beyond showing it in the popup.

What Easy Proxy does NOT do

• No accounts, no sign-in, no analytics, no ad tracking.
• No reading, modifying, or injecting anything into the pages you visit.
• No selling or sharing of any data with third parties.
• No remote code execution — the only things fetched from the network are JSON proxy lists and plain IP-lookup responses, never scripts.

Why the permissions it asks for

• proxy — to actually change Chrome's proxy settings (the extension's core feature).
• storage — to save your proxy list locally, as described above.
• webRequest + webRequestAuthProvider — to supply your saved username/password when an HTTP/HTTPS proxy asks for authentication. Chrome only allows this for proxy authentication challenges, not for reading page content.
• Host permissions (<all_urls>) — Chrome requires this so the proxy authentication above can fire for any site you might visit through any proxy you configure. It is not used to read, collect, or transmit page content.

Changes

If this policy changes, this page will be updated with a new "last updated" date.

Contact

zinovenkov@gmail.com