Version applicability
This page distinguishes the published 1.0.1 release from the upcoming 1.0.2 release. Behavior labeled 1.0.2 applies only after that version is installed; updating this website does not change an installed extension.
storage
Stores local notification preferences, temporary hit summaries, and storage-maintenance state. Primary rules, groups, page scripts, and request-debugging data use local IndexedDB. Version 1.0.2 (upcoming) also stores usage dates and review-invitation state and preferences in chrome.storage.local; it does not record review content or include this state in configuration exports. Reqix has no accounts and does not sync configuration through browser sync services.
tabs
Identifies the current tab and site, updates the extension icon, manages per-site switches, opens extension management pages, and clears temporary state on navigation or tab closure. Reqix does not request the history permission or send tab information to a developer server.
scripting
Injects Reqix’s bundled Fetch/XHR interception code into pages and frames where request handling must run, enabling configured request rewrites, mocks, delays, and cancellation. Global or per-site controls determine whether handling runs; version-specific defaults are described under host access below.
userScripts
Registers and runs page scripts that the user creates or intentionally imports. Chrome and Edge require the separate “Allow user scripts” setting; users can disable individual scripts or revoke this permission at any time.
webRequest
Version 1.0.1: observes completion, failure, and redirect events read-only to maintain local recent-request records and verify native redirect hits.
Version 1.0.2 (upcoming): observes only onBeforeRedirect events read-only to verify user-configured native Redirect rules and record hits. It no longer maintains a site-wide recent-request list from completion or failure events. This permission does not block or modify requests or read response bodies.
declarativeNetRequestWithHostAccess
Applies user-configured native URL redirects and the CORS response-header adjustments needed for cross-origin redirects. Rules are subject to global or per-site controls and the enabled state of rules and groups.
<all_urls>
Allows request rules and page scripts on arbitrary HTTP(S) sites, local development servers, and test APIs. These debugging targets cannot be enumerated in advance, which requires broad host access.
Version 1.0.1: request handling is off on first install and uses per-site mode, with explicit confirmation before first enablement. Version 1.0.2 (upcoming): request handling is on globally on first install; users can turn it off or choose per-site controls. Upgrading to 1.0.2 preserves existing switch settings instead of forcing global enablement.
Individual rules and their groups must also be enabled. Browser-level site-access restrictions remain in effect.
Web-accessible resources
The interceptor and sandbox resources bridge Fetch/XHR in the page context and isolate dynamic response logic. Reqix’s own code is bundled with the extension, not downloaded for execution from a developer server. User-created or imported scripts and dynamic response code may access the network according to their content.