ProxyJam Connector — Privacy Policy
Effective 3 September 2026 · Applies to the ProxyJam Connector extension for Chrome, Microsoft Edge, and Firefox (version 1.0.0 and later)
Scope — please read this first
This policy covers the ProxyJam Connector browser extension and nothing else.
The ProxyJam proxy service is a separate product, operated by Pryvus Inc, with its own privacy policy. That policy describes accounts, billing, payment processing and service usage, because the service has all of those. The extension has none of them.
The two are connected only if you choose to connect them. The extension is a generic proxy manager: it works with whatever proxies you configure, including ones from other providers or your own, and it never signs you in to anything on its own. It also has one optional tab, ProxyJam, where you can sign in to a ProxyJam account, buy proxies, and manage them. That tab makes no network request of any kind until you sign in, and it is the only part of the extension that ever contacts ProxyJam. The only other requests it can make are the optional network checks listed below, which go to third-party services and never to us.
If you do sign in, the service policy above applies to your account, exactly as it would if you had signed in on the website. Everything else in this document describes the extension itself and is true whether you sign in or not.
Summary
ProxyJam Connector is offline by default. It has no telemetry, no analytics, no crash reporting, no advertising, no tracking, and no cloud sync, and it never calls home. Everything it knows lives in your browser’s local extension storage on your own device. The extension is free, with nothing to buy to unlock a feature and no license server.
Every outbound request the extension can make is optional, off by default, and individually enabled by you. That includes the ProxyJam account tab, which sends nothing until you sign in. They are all listed in full below, along with the ones that repeat on a schedule.
What we collect
Nothing, unless you sign in to a ProxyJam account. There is no telemetry, no analytics, no crash reporting, no advertising, no tracking, and no cloud sync at any point.
If you use the optional ProxyJam tab and sign in, then your email address and password are sent to
api.proxyjam.com to authenticate, and your orders and wallet are read back so the tab can show
them. That is the whole of it: your browsing, your page content, your other proxy profiles, and how
you use the extension are never sent, signed in or not. Signing out clears the stored session.
What the extension stores on your device
The following is written to your browser’s local extension storage (storage.local) and never
leaves your device unless you explicitly export it:
- Proxy profiles — name, scheme, host, port, username, password, notes, remote-DNS flag, favorite flag, color tag, failover target, timestamps.
- Auto-switch rules — the conditions you define and the profile each one routes to.
- Rule sets — the named groups you organize rules into, and whether each group is on.
- Bypass list — hosts, globs, and CIDR ranges that skip the proxy.
- Settings — theme, debug-logging flag, the four network-check toggles, the health-check
schedule, and whether
api.proxyjam.comstays off the proxy. - Active selection — which proxy mode is currently on, so it survives a browser restart.
- Health status — the result and time of the last health check, and the last automatic failover.
- Container assignments (Firefox) — which proxy profile each container uses.
- ProxyJam account (only if you sign in) — the session, the metadata of your orders, and which profile mirrors which order. It is empty until you sign in and cleared when you sign out; the section below describes it in full.
Checker results are not written to storage at all: they live in the page that ran the check and are gone when you close it. Neither is the generated PAC script — it is recompiled from your rules whenever the proxy is re-applied and handed straight to the browser.
Proxy credentials
Proxy usernames and passwords are the most sensitive thing the extension holds. They are stored locally in the same extension storage, and:
- they are redacted in every log path — the logger replaces any secret-named field with
••••before it can reach the console; - they are never sent to the extension’s own UI — the interface receives only
hasUsername/hasPasswordbooleans; - they are omitted from exports unless you explicitly opt in to including them, and an export that includes them can be encrypted with a passphrase you choose;
- they are sent only to the proxy server you configured, by the browser itself, to authenticate your connection. That is the entire purpose of storing them.
Browser extension storage is not encrypted at rest. Anyone with access to your operating-system user account can read it. Use full-disk encryption and a locked screen if that matters to you.
Optional outbound requests
Apart from the ProxyJam account tab described further down, these are the only requests ProxyJam Connector can originate. Each is disabled until you turn it on in Settings → Network checks, and none can run until you also grant the optional host permission.
| Feature | Endpoint | What is sent | Third party |
|---|---|---|---|
| External IP check | https://api.ipify.org | The request itself, routed through your active proxy. No identifiers are attached. | ipify |
| Geo / ASN lookup | https://ipwho.is/<ip> | Only the egress IP address returned by the check above. | ipwho.is |
| WebRTC leak test | stun:stun.l.google.com:19302 | A standard STUN binding request, used to enumerate your local ICE candidates. | |
| Health check | https://api.ipify.org | The same request as the external IP check, repeated on the interval you choose. | ipify |
| DNS-leak test | — none — | Nothing. See below. | — |
Those are three hosts in total, not five: the health check reuses the external IP endpoint, and the DNS-leak test contacts nothing at all. Detecting a DNS leak requires a DNS reflection service, we ship none, and we will not guess — so that field reports unavailable rather than a made-up verdict.
These providers are independent services with their own privacy practices; we have no agreement with them and receive nothing from them. If you do not want to contact them, leave the corresponding toggle off — the rest of the extension works fully without it.
Every request uses HTTPS, or the STUN protocol for the leak test.
One feature repeats without you pressing anything. The checker runs only when you press
Check. The health check is different by design: once you enable it, it probes your active proxy
every 5, 15, 30, or 60 minutes — whichever you picked — so it can warn you, or fail over to a backup
profile, when that proxy stops answering. It is off by default, it contacts only api.ipify.org,
and turning it off stops it immediately.
Permissions and why they exist
| Permission | Why it is needed |
|---|---|
proxy | To set the browser’s proxy configuration. This is the extension’s core function. |
storage | To save your profiles, rules, and settings locally. |
webRequest + webRequestAuthProvider (Chrome/Edge) | To answer your proxy’s authentication challenge programmatically, so you are not prompted by a browser dialog on every request. |
alarms | To schedule the optional periodic health check. No alarm exists while that feature is off. |
contextualIdentities (Firefox) | To list your containers, so you can assign a different proxy to each. Used to read container names and colors only. |
| Host access to all sites (optional) | Requested only when you configure an authenticated HTTP/HTTPS proxy or enable the network checks. It is never requested at install time, and the extension is fully usable without granting it. |
Host access to api.proxyjam.com (optional) | Requested only at the moment you sign in on the ProxyJam tab, and never before. Declining sends nothing at all. It is deliberately separate from the all-sites permission, so signing in to an account does not cost you access to every website. |
ProxyJam Connector has no content scripts. It does not read, modify, or inject anything into the pages you
visit, and it does not have or use the tabs, history, or scripting permissions.
The ProxyJam account tab
This is the only networked feature, and it is inert until you sign in.
What it sends. Your email address and password, once, to authenticate. After that, an API key or a session token accompanies each request you trigger — browsing the catalogue, buying a proxy, refreshing your orders, reading your wallet.
What it stores on your device. The session token, the refresh token and the API key; the metadata of your orders (country, type, status, expiry, bandwidth); and, for a proxy you buy through the extension, its host, port, username and password — stored exactly like any proxy profile you would have typed in yourself, because that is what it becomes.
What it never sends. Your browsing history, the pages you visit, how you use the extension, your other proxy profiles, or anything at all before you sign in.
Payments. The extension never handles card or bank details. A purchase either spends a balance that already exists on your account, or opens the payment provider’s own page in a browser tab. Adding funds is not offered inside the extension; it links to the website.
One host is kept off your proxy. Requests to api.proxyjam.com bypass the active proxy by
default. Without that, a proxy that stops working would also cut off the account tab you would use
to replace it, leaving no way back from inside the extension. Only that subdomain is affected —
the site and the dashboard route through your proxy like any other page — and the behaviour can be
turned off in Settings. It does mean ProxyJam sees the IP address you are connecting from, which it
would see anyway for an account you signed in to.
Signing out clears the session. You choose whether the proxies you bought stay as ordinary profiles or are deleted from the browser; either way they remain on your ProxyJam account.
What we do not do
- We do not sell or transfer your data to third parties.
- We do not use your data for advertising, profiling, or creditworthiness assessment.
- We do not use your data for any purpose unrelated to the extension’s single purpose.
- We do not read your browsing history or page content.
- We do not execute remote code. All JavaScript that runs is contained in the signed store package.
- We do not phone home to validate a license, check for updates, or count installs.
How to delete your data
- All of it: uninstall the extension. The browser deletes its local storage with it.
- Selectively: delete individual profiles, rules, or bypass entries in the options page.
- Back it up first: use Import / Export → Export to save a copy. Exports exclude passwords unless you tick the option to include them, and can be encrypted with a passphrase.
Because we never receive your data, there is nothing for us to delete on your behalf and no deletion request to file.
Children
ProxyJam Connector is a network utility for general audiences. It is not directed at children and collects no data from anyone, including children.
Changes to this policy
Material changes will be published here with an updated effective date. Continued use after a change constitutes acceptance.
Contact
- Email: support@proxyjam.com
- Support page: /extension-support/
- Source availability: GitHub repository