Privacy Policy

Last updated: April 4, 2026

        Summary: HttpMockBench processes all data locally on your device. We do not collect, transmit or sell your personal data, your requests, or the content of intercepted responses.
      

1. Who we are

HttpMockBench is a Chrome browser extension developed and maintained as an independent project. For any privacy-related questions, contact us at support@httpmockbench.com.

2. Data we do NOT collect

HttpMockBench does not collect, store on external servers, or transmit:

The content of any HTTP request or response you send or inspect
The URLs you visit or test
Any personally identifiable information
Browsing history or behavior analytics

3. Data stored locally on your device

HttpMockBench stores the following data exclusively in your browser's local storage (IndexedDB and chrome.storage.local), which never leaves your device:

Mock rules: the interception rules you create, including URL patterns, response bodies and headers.
Collections & saved requests: HTTP requests you save for later reuse.
Environments & variables: variable sets used to parameterize your requests.
Request history: the last 50 requests you sent, stored for your convenience. Clearable at any time from Settings.
User preferences: panel layout, active environment and other display settings.
License status: whether your account has an active Pro subscription (cached locally to avoid repeated network calls).

4. License verification (Pro tier)

If you purchase a Pro license, the extension communicates with ExtensionPay solely to verify your license status. This involves:

Sending your Chrome identity token to ExtensionPay's servers to check subscription status.
No request content, mock rule data, or browsing data is included in this request.

ExtensionPay's own privacy policy applies to this interaction: extensionpay.com/privacy.

5. Permissions used

The extension requests the following Chrome permissions, each with a specific and limited purpose:

scripting / activeTab: to inject the request interceptor into the current tab when mocking is active.
webRequest: observe-only, used to capture HTTP traffic for the real-time logger.
declarativeNetRequest: to redirect requests matching redirect rules.
storage: to save your rules, collections, environments, and history locally.
sidePanel: to display the API client and mocker in the browser side panel.
devtools: to provide the HTTP Logger panel in Chrome DevTools.

6. Third-party services

HttpMockBench does not integrate any advertising network, analytics platform, or data broker. The only third-party service involved is ExtensionPay, used exclusively for Pro license management (see section 4).

7. Changes to this policy

We may update this privacy policy as the extension evolves. Changes will be reflected by updating the "Last updated" date at the top of this page.

8. Contact

For any questions regarding this privacy policy, please contact us at support@httpmockbench.com or open an issue on GitHub.