Privacy policy

Effective date: 24 October 2026. This policy covers versions 2.0 and 2.1 of Easy DevTools – Network Interceptor, developed by Arman Hilmioglu.

Data processed on your device

The extension reads HTTP/HTTPS request URLs and tab identifiers to show recent requests and apply your URL redirect and blocking rules. URLs may contain personal or sensitive information. Recent request records are kept in Chrome session storage, limited to 50 entries, cleared when you change the active tab, and removed when the browser session ends.

Your interception rules, replacement URLs, master switch setting, and dismissed notices are stored locally in the browser profile. The popup also uses local storage as a local cache. No browser sync service is used by the extension.

Local-file responses in version 2.1

If you select a local file, the extension reads and stores a snapshot of its contents, file name, and MIME type in extension-local storage on this device. A file can be up to 2 MiB. The extension does not monitor your disk or update the snapshot automatically. Remove its rule to delete the saved snapshot, or uninstall the extension to remove its stored data. File contents are not sent to the developer or a server. Only select files you intend to expose to the website you are testing: their replacement response becomes available to that page and its scripts.

Page debugging in version 2.1

Chrome requires the debugger permission at installation; it cannot be requested as an optional permission. This is a powerful permission that can read and change page data. This extension uses it only to substitute selected local-file responses for matching request URLs. When monitoring is enabled and local-file rules exist, it attaches to the active HTTP/HTTPS tab in the last focused window, including related iframe and worker targets. Chrome displays a debugging banner.

The debugger may deliver request metadata, including headers and request data, to the extension while pausing a matching request. The extension checks the URL and method and supplies the selected file body with its MIME type; it does not retain debugger request headers or request bodies, or send them to the developer. It does not take screenshots or evaluate code through the debugger. Switching tabs detaches the old tab and moves debugging to the newly active HTTP/HTTPS tab. Turning off monitoring or removing the last local-file rule detaches it completely. Cancelling the debugging banner pauses monitoring; enable it again explicitly to resume. Other debuggers or DevTools can prevent attachment, and the popup shows attachment or replacement failures.

No developer collection or analytics

The extension does not send request logs, browsing activity, or rules to the developer. It includes no analytics, advertising, remote code, or developer-operated collection service. The developer does not sell or share extension data.

Redirect destinations

If you create a redirect rule, Chrome sends the redirected request to the destination you choose, subject to browser security rules. That destination may receive request information such as your IP address and applicable request headers or cookies. Its own privacy practices apply. Only configure destinations you trust.

Permissions

Access to HTTP/HTTPS websites and the webRequest permission allow the extension to observe request URLs. The declarativeNetRequestWithHostAccess permission applies your block and redirect rules. The storage permission keeps your rules, selected file snapshots (version 2.1), and settings locally and the recent request list in session storage. The debugger permission in version 2.1 supplies local-file replacement responses as described above. Version 2.0 does not include debugger-based local-file responses.

Your controls and deletion

Remove individual rules in Existing rules or turn off the master switch to stop monitoring and interception. Uninstalling the extension removes its stored data from the browser profile. Changing the active tab clears the recent request list. Keep sensitive URLs out of support messages.

Support and website

If you email the developer, the information you provide is used to respond to your request and is processed by the email provider. These static website pages are hosted by GitHub Pages, whose hosting service may process technical request information under GitHub’s privacy statement. These pages add no analytics or tracking cookies.

Changes and contact

Policy updates will be posted here with a revised effective date. For privacy questions or requests concerning information you sent in a support email, contact arman.hilmioglu@gmail.com.