ReRoute Privacy Policy
Last updated:
In short
ReRoute does not collect, sell, log or transmit your data to any external server. All URL redirects, header overrides, query parameter edits and HTTP response mocks execute locally inside your browser.
What it stores and where
- Your rules, profiles and preferences (
chrome.storage.local): rule patterns, redirect targets, header names and values, query parameter overrides, mock payloads, profile names, active profile ID, language, master toggle and theme preferences stay exclusively on your device. - Transient engine state (
chrome.storage.session): internal mappings between your rules and native declarative rules, plus sync status flags for toolbar badge feedback. This state never leaves the browser and clears automatically when the browser closes. - UI view cache (
localStorage): remembers the last selected theme and popup filter state so the interface opens without visual flicker.
Rules and profiles are only written to a file when you explicitly export them from the Import / Export page in JSON format.
What it never does
- It never connects to external servers: no analytics, no telemetry, no crash reporters, no ads and no user accounts.
- It never uploads or inspects your browsing history, credentials, headers or intercepted payloads outside your machine.
- The local mock interceptor runs only on pages and requests when active mock rules or optional in-page notifications require it, strictly inside your browser session.
Chrome permissions
declarativeNetRequest: compiles and applies URL redirect rules, request header additions/removals, query parameter rewrites and static data-URL responses natively in Chrome.storage: saves your rules, profiles and preferences locally on your device (chrome.storage.local) and holds transient engine mappings in session memory (chrome.storage.session).scripting: injects the lightweight in-page interceptor into theMAINworld on demand so synthetic mock responses and request body overrides work cleanly forfetchandXMLHttpRequest.webRequest: observes when declarative redirect or header rules trigger on a request so optional in-page toast notifications can inform you which rule matched.sidePanel: lets you dock the same interface inside Chrome’s Side Panel alongside DevTools while debugging.- Host permissions (
<all_urls>): required so your user-defined rules can match, redirect, modify headers on or mock any URL or local development port you choose to configure.
Changes
If this policy is updated in future releases, the revision date at the top of this page will be updated accordingly.
Questions? Email me at limbermay21@gmail.com.