StatusMock
HomeFeaturesPrivacyFAQContact
  1. Home
  2. Privacy Policy

Last updated August 26, 2026

Privacy Policy

StatusMock lets users create local rules that replace Fetch and XMLHttpRequest response status codes and bodies for URLs they choose.

Data the extension handles

StatusMock stores URL patterns, status codes, and response bodies in Chrome extension storage on your device. This information is used only to apply the response rules you create.

Response bodies can contain sensitive information. Treat private data entered into a rule as confidential and do not share it with support.

Data collection and sharing

StatusMock does not transmit, sell, share, or remotely process personal information, rule data, browsing activity, or website content. It contains no analytics, advertising, tracking, accounts, external services, remote code, or developer-controlled servers. No extension data is made available to the developer, third parties, advertisers, or other humans.

How response interception works

The extension uses Chrome's debugger API only to intercept matching Fetch and XMLHttpRequest responses in your browser. It attaches only to an ordinary browser tab you explicitly enable and only while at least one valid rule exists.

For matching responses, Chrome provides StatusMock with the request URL and method and the original response headers. StatusMock processes this information temporarily on your device only to select and apply your first matching rule. It does not read or retain the original response body, and intercepted metadata is not written to storage or sent anywhere. The configured status and body replace the response while its other semantic headers are retained.

Data storage and deletion

Rules are stored in Chrome's local extension storage. The IDs of tabs you explicitly enable are kept only in Chrome session storage and are cleared when the browser session ends. Removing the extension removes its locally stored extension data according to Chrome's normal extension-removal behavior.

Permissions

StatusMock requests Chrome's debugger permission so it can pause and replace matching Fetch and XMLHttpRequest responses in tabs you explicitly enable. It requests storage permission so your rules can be saved locally. These permissions are not used to collect browsing activity.

Limited Use

StatusMock's use of information received from Chrome APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide StatusMock's disclosed response-mocking purpose; it is not transferred to third parties, used for advertising, or made available for human review.

Contact

For privacy questions, email support@statusmock.com. Please do not include private response bodies or other sensitive information in support requests.

StatusMock

Local response mocking for Chrome.

PrivacyFAQContact