Overview
This policy explains how InterceptPilot handles technical data while supporting local debugging, request
inspection, mocking, and QA testing inside the browser.
InterceptPilot does not operate a backend service, does not send captured data to external servers, and
does not share or sell user data.
Single purpose
InterceptPilot has one purpose: help frontend developers and QA teams inspect browser requests, simulate
API behavior, and test application scenarios locally.
Capture begins only after the user explicitly starts it, and only for the browser tab the user selects.
Data handled locally
To perform its development and QA purpose, InterceptPilot may process technical data locally such as:
- browsing and request activity related to the user-selected tab
- request URLs, HTTP methods, status codes, headers, and timings
- additional technical request or response details, such as payload content, when needed for inspection, debugging, and mock flows
- logs, rules, collections, filters, and extension settings
This processing happens inside the browser on the user's device.
Data we do not collect
InterceptPilot does not collect or transmit data to a company backend because it has no backend.
- no analytics or telemetry
- no advertising identifiers
- no cross-site tracking
- no profiling
- no sale of data
How data is used
Technical data is used locally and only to support the extension's visible features, including:
- displaying inspected network activity for the selected tab in the extension UI
- supporting local debugging, diagnostics, and QA workflows
- creating, applying, and reviewing mock rules and collections
- preserving settings and working context required for the tool between sessions
Local storage
Rules, collections, filters, logs, and settings are stored in the browser's local storage area used by
the extension.
InterceptPilot uses that local storage so the user can keep configurations and continue working between
sessions without relying on remote infrastructure.
Third-party sharing
InterceptPilot does not share captured data, rules, logs, or settings with third parties. It does not
sell data and does not make captured technical data available to advertisers, data brokers, or external
analytics providers.
Remote code
InterceptPilot does not execute remote code. Its JavaScript, HTML, CSS, and related assets are packaged
with the extension itself.
The extension's scripts are loaded from extension resources, not from remote servers, and the product is
not designed around externally hosted executable code.
Permissions
InterceptPilot uses browser permissions only to provide its development and QA features, such as
attaching to a user-selected tab, inspecting requests, supporting debugging workflows, storing local
rules and settings, and rendering the extension UI.
These permissions are used only for the extension's stated purpose. They are not used for tracking,
advertising, analytics, or background collection.
debugger
activeTab
tabs
webNavigation
scripting
sidePanel
storage
management
host permissions
User control
The user chooses when capture starts, which tab is involved, and when capture stops. InterceptPilot does
not silently activate request capture across unrelated tabs.
Because data stays local, the user remains in direct control of browser-stored rules, collections, logs,
filters, and settings.
Contact
For privacy questions about InterceptPilot, contact
anderalpin@gmail.com.
Last updated
May 28, 2026