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.
1. Scope and purpose
This policy explains data handling and user controls for Reqix in Microsoft Edge. The same practices apply to the Chrome version; section 8 covers the official Reqix website. The extension provides user-controlled network debugging, API mocking, and page scripts. It requires no account and provides no cloud sync, advertising, or user profiling.
2. Data handled by the extension
- Rules, groups, page scripts, per-site switches, and interface preferences.
- Network-request URLs, methods, resource types, status codes, and times. Fetch/XHR may also include query parameters, request and response headers, textual request and response bodies, sizes, and durations. This content may include identity or authentication information, cookies, business data, or other sensitive content; Reqix does not identify, analyze, or use it for a secondary purpose.
- Rule-hit records, current-tab runtime state, and recording state when the user explicitly starts a recording. Version 1.0.2 (upcoming) also stores local usage dates, review-invitation display state, and preferences such as “Don’t ask again”; this invitation state contains no visited URLs, rule contents, or review contents.
- Configuration and scripts that the user chooses to import or export.
3. When data is processed
Reqix saves configuration when a user creates, edits, imports, or records rules and page scripts.
Version 1.0.1: request handling is off on first install and uses per-site mode. Before request interception is enabled for a site or for all sites for the first time, Reqix discloses the processing scope and requires explicit confirmation. Only after confirmation do content scripts observe and process Fetch/XHR on enabled sites.
Version 1.0.2 (upcoming): request handling is enabled globally on first install to match and apply rules. Users can turn it off or choose per-site controls. Upgrades preserve existing switch settings. When no rule matches and recording has not been started, Reqix does not copy request or response bodies or save recent-request snapshots.
When the user opens the Reqix DevTools panel, the browser DevTools API supplies completed requests from the inspected page. Version 1.0.1 displays Fetch/XHR; version 1.0.2 (upcoming) can display all network resource types. This viewer is independent of the request-interception switch and does not inject into or modify traffic. The panel keeps up to 500 rows in memory; clearing the list or closing DevTools removes them from panel memory. Selected request data is saved as configuration only when the user creates a rule.
4. Local storage and retention
Reqix uses IndexedDB, chrome.storage.local, chrome.storage.session, and extension-page localStorage. It does not sync this data through browser sync services. Rules, groups, and page scripts remain until the user deletes them or uninstalls Reqix; per-site switches and preferences remain until the user changes them or uninstalls. localStorage holds interface preferences only, such as theme, navigation view, and editor height.
Version 1.0.1: recent snapshots are limited to 100 entries and 20 MB per tab, and 80 MB across all tabs. A request body may be retained only when it can be converted to text and is no larger than 1 MB. Textual response bodies are limited to 1 MB, and binary response bodies are not stored. Snapshots and daily hit logs older than 24 hours are removed the next time extension storage maintenance runs, so removal may be delayed while the browser is closed or the extension is inactive.
Version 1.0.2 (upcoming): the Popup recent-request cache is removed. Upgrading deletes the old temporary recent-request table while preserving rules, groups, page scripts, settings, and other application tables. Explicit recording still retains only supported textual request bodies of up to 1 MB and textual response bodies of up to 1 MB; binary response bodies are not stored. Daily hit logs older than 24 hours are cleared during the next storage maintenance. Review invitations store only usage dates, display state, and reminder preferences in chrome.storage.local until uninstall; choosing “Don’t ask again” preserves the suppressed state to avoid further prompts.
An explicitly started recording is limited to 10 minutes, 100 requests, or 50 MB. Finishing it converts supported requests into editable rules. Version 1.0.1 discards unfinished recordings on the next browser startup or extension install or update. Version 1.0.2 (upcoming) discards unfinished recordings on the next browser startup but preserves existing recording data during extension updates. Current-tab hit summaries use session storage and are cleared on navigation, tab close, or session end. Reqix does not add encryption to local configuration.
5. Transfer and sharing
Reqix has no backend that receives rules, request snapshots, page scripts, or usage behavior, and it contains no extension telemetry, advertising, or third-party analytics SDK. This local data is not sent automatically to Reqix developers.
Requests that are not mocked, redirected, or canceled still reach the page's original server. Redirects reach a target chosen by the user. Page scripts and dynamic response code may also initiate network access according to user-authored code and subject to browser security policies. Exported files are saved or shared only by the user after an explicit export.
6. Scripts and security boundaries
Dynamic response code runs in a dedicated extension Sandbox Worker without access to browser extension APIs or the page DOM. Page scripts use an isolated world by default. In MAIN world they can read or modify the page's JavaScript objects, and the page can inspect or interfere with the script. Reqix does not download code from a developer server; dynamic response code and page scripts come from content the user creates or intentionally imports.
Request data and export files may contain Authorization values, cookies, tokens, personal information, or business data. Use sensitive rules only on trusted devices and sites, and import or share only trusted configurations and scripts.
7. User controls and deletion
- Disable request interception for the current site or all sites from Popup.
- Disable or delete individual rules, groups, and page scripts in the management center.
- Deselect rules, groups, or page scripts that should not be included before exporting.
- Restrict Reqix site access in the browser; this does not delete data already stored locally.
- Uninstall Reqix so the browser removes the extension's local data.
8. Official website
The official Reqix website is a static site hosted on GitHub Pages. It has no account system or developer-operated analytics. The site stores only your manually selected color theme in browser localStorage. Clearing site data resets this preference; it is not sent to a server and does not access extension data. When a GitHub Pages site is visited, GitHub logs and stores the visitor's IP address for security purposes and may process service-usage data such as request time, device, or browser information under its privacy statement.
9. Children's privacy and policy changes
Reqix is intended for developers and testers, is not directed to children, and does not knowingly collect children's personal information. If data practices change materially, this page's date will be updated and Reqix will provide prominent disclosure and consent where applicable store policies require it.
10. Contact and store data-use requirements
For questions about this policy, permissions, or data handling, contact the maintainers through Reqix GitHub Discussions.
The Microsoft Edge version handles data in accordance with the personal-information, permission, and data-use requirements of the Microsoft Edge Add-ons developer policies. Data is used only to provide or improve the single purpose and user-visible features described in this policy.
For the Chrome version, Reqix's use of information received from browsers and related APIs will also adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.