Legal information
ProxRule privacy policy
ProxRule routes only websites explicitly selected by the user through a user-configured proxy. The extension runs locally in the browser, requires no account and has no developer backend.
Data processed
To use the extension, the user may provide:
- proxy address, port, protocol and connection profile name;
- HTTP/HTTPS proxy username and password;
- domains that should use the proxy or a direct connection;
- selected rule and pause durations.
The popup reads the current tab's hostname to show its route and to add a rule after an explicit user action. If the user separately starts related-domain discovery, the extension reloads that tab once and locally processes resource hostnames, resource types and request counts. Full URLs, paths, queries, headers, cookies, page content and form data are not collected.
Local diagnostics process the extension and browser-platform version, configuration modes, aggregate counts and fixed issue codes. A manual network check makes one HTTPS request to a user-selected website without cookies or referrer and does not read the response body.
How the data is used
Data is used only for the stated features: applying the selected proxy to specified websites, explaining the route decision, performing requested proxy authentication, temporary rules, diagnostics or related-domain discovery. It is not used for advertising, profiling, analytics, creditworthiness or data sales.
Information received through browser APIs is used in accordance with the Chrome Web Store User Data Policy, including Limited Use requirements. Access is requested only for user-visible features and is not used for unrelated purposes.
Where data is stored
Settings, profiles and permanent rules are kept in local storage of the browser profile. By default, proxy credentials are stored only until the browser fully closes. The user may explicitly choose persistent browser storage after a warning that it is not an operating-system secure vault.
Temporary rules, pause state and technical session state are removed when the browser closes. Related-domain results are kept for no more than five minutes and never survive the browser session. One-step undo keeps the previous state only in memory while the settings page remains open.
A backup is created only at the user's request and excludes usernames, passwords, temporary rules, pause state and scan results. The file is saved wherever the browser downloads it.
Data transmission and disclosure
The developer does not receive, store or share user settings, credentials, domain lists, browsing history or diagnostic data. The extension contains no telemetry, analytics, advertising or requests to developer infrastructure.
When enabled, network requests to selected domains pass through the third-party proxy configured by the user. By design, that proxy receives the proxied traffic and, when required, proxy authentication credentials. Selected websites receive normal browser requests. Those services process data under their own terms and policies; the user chooses and configures the proxy.
The extension does not sell data or give the developer or advertising platforms access to it. No person on the developer side reads user data because it is not sent to the developer.
Security and user control
Executable code is bundled with the extension; no remote executable code is loaded. Credentials are excluded from PAC, backups, diagnostic reports, badges, error messages and console output. Proxy credentials are sent only to the server matching the active proxy configuration; an HTTPS proxy is recommended on untrusted networks.
The user can edit or remove profiles and rules or select “Delete all data” in settings. Uninstalling the extension also removes its local and session storage. Downloaded backup files must be removed by the user.
Policy changes
If data practices change, the new practice will be clearly disclosed before it is enabled, and this policy and the store listing will be updated. The effective date appears at the top of this document.