English
English

ProxyJam Lite — Privacy Policy

Effective 7 August 2026 · Applies to the ProxyJam Lite extension for Chrome, Microsoft Edge, and Firefox (version 1.0.0 and later)

Scope — please read this first

This policy covers the ProxyJam Lite 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 not connected. Installing the extension does not create a ProxyJam account, does not sign you in to anything, and sends nothing to ProxyJam’s servers. It is a generic proxy manager: it works with whatever proxies you configure, including ones from other providers or your own. If the service policy and this one appear to disagree, it is because they describe different products — this one is the accurate description of the extension.

ProxyJam Lite has no backend. We operate no servers, run no accounts, and receive no data from you — not your proxies, not your credentials, not your browsing. Everything the extension knows lives in your browser’s local extension storage on your own device.

Three optional features can make an outbound request. All three are off by default, each must be turned on individually, and they additionally require you to grant a separate browser permission. They are listed in full below.

What we collect

Nothing. ProxyJam Lite transmits no data to us. There is no telemetry, no analytics, no crash reporting, no advertising, no tracking, no user accounts, and no cloud sync.

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, timestamps.
  • Auto-switch rules — the conditions you define and the profile each one routes to.
  • Bypass list — hosts, globs, and CIDR ranges that skip the proxy.
  • Settings — theme, debug-logging flag, and the three network-check toggles.
  • Active selection — which proxy mode is currently on, so it survives a browser restart.
  • Checker results — the most recent check output per profile, for display only.
  • Generated PAC script — the compiled auto-switch script, cached to avoid regenerating it.

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 / hasPassword booleans;
  • they are omitted from exports unless you explicitly opt in to including them;
  • 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

These are the only requests ProxyJam Lite 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.

FeatureEndpointWhat is sentThird party
External IP checkhttps://api.ipify.orgThe request itself, routed through your active proxy. No identifiers are attached.ipify
Geo / ASN lookuphttps://ipwho.is/<ip>Only the egress IP address returned by the check above.ipwho.is
WebRTC leak teststun:stun.l.google.com:19302A standard STUN binding request, used to enumerate your local ICE candidates.Google

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.

All three requests use HTTPS (or the STUN protocol, for the leak test). No request is ever made on a schedule or in the background: they run only when you press Check.

Permissions and why they exist

PermissionWhy it is needed
proxyTo set the browser’s proxy configuration. This is the extension’s core function.
storageTo 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.
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.

ProxyJam Lite 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.

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.

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.

Because we never receive your data, there is nothing for us to delete on your behalf and no deletion request to file.

Children

ProxyJam Lite 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, and the version history is public in the extension’s Git repository. Continued use after a change constitutes acceptance.

Contact