Trust center

Why Reqix needs browser permissions

A request interception tool needs to observe and modify traffic on websites you choose. Every Manifest V3 permission maps to a current feature.

Last updated: August 12, 2026

storage

Stores rules, groups, settings, page scripts, recent request snapshots, and hit logs inside extension storage. Reqix has no account or developer-operated cloud sync.

tabs

Identifies the current tab and site so Popup, DevTools, content scripts, and background state agree. Browsing history is not sent to Reqix servers.

scripting

Injects the request interception bridge and synchronizes rule runtime state on pages the user allows.

userScripts

Registers and runs page scripts that the user creates or intentionally imports. The feature requires additional browser authorization and can be disabled.

declarativeNetRequestWithHostAccess

Implements supported redirects and header handling in Chromium's native network layer under Manifest V3 constraints.

<all_urls>

Lets request rules work on HTTP(S) sites selected by the user. The default per-site mode does not take over every page after installation. Users must enable the current site and target rule; grouped rules also require their groups to be enabled.

Web-accessible resources

The interceptor and sandbox resources bridge Fetch/XHR in the page context and isolate dynamic response logic. Production builds do not load remote code.