MockPilot Privacy Policy

1. Information stored by MockPilot

MockPilot stores the following information locally in your browser using IndexedDB:

• Workspace names, folders, and saved API requests.
• Request URLs, methods, query parameters, headers, request bodies, and authentication configuration that you enter.
• Environment names and variables that you create.
• Request history and captured request records.
• Mock configuration, including status codes, response bodies, response headers, and delays.

Theme selection and small application settings are stored using browser storage. MockPilot does not require an account and does not maintain a remote workspace database for this information.

2. API requests and browser traffic

When you send an API request from MockPilot, the request is sent to the target URL that you provide. That target server may receive the URL, headers, authentication, body, and other data required by your request. MockPilot does not control the privacy practices of those target servers.

When you start API Capture, MockPilot observes eligible fetch and XMLHttpRequest activity from the browser tab you select. Captured records are used to show the request in MockPilot and can be saved locally to your workspace.

When Mock Server is enabled, MockPilot can intercept matching browser requests and return the mock response configured by you.

3. Chrome permissions

MockPilot requests Chrome permissions needed for its single purpose: testing, capturing, and mocking browser APIs.

• Storage: persist extension settings and local workspace state.
• Tabs and activeTab: identify the tab selected for API Capture and interact with the active tab when required.
• Scripting: install the capture and mocking bridge in pages where the feature is enabled.
• webRequest and declarativeNetRequest: observe or control matching browser requests for capture and mocking.
• debugger: support the browser request inspection and interception workflow.
• Host access: support API capture and mocking on the sites selected by the user.

Chrome displays the final permission prompt during installation. Do not use MockPilot on sensitive systems unless you understand and accept these permissions.

4. Data sharing and sale

MockPilot does not sell, rent, or share your workspace data with advertisers, data brokers, or a remote MockPilot analytics service. The extension does not include advertising or third-party tracking analytics.

Data can still be sent to services you choose to call from API Editor, and browser traffic can be sent to the target servers involved in the pages you use. Those services operate under their own policies.

5. Data deletion and export

You can delete workspaces, requests, environments, history, and captured records from MockPilot's interface. You can also remove all extension data by removing MockPilot from Chrome or clearing the extension's site data through Chrome settings. Workspace exports are files under your control and may contain credentials or other sensitive values.

6. Security

MockPilot is designed to keep workspace data in the browser, but local browser storage is not a substitute for device security. Protect your operating-system account and browser profile, avoid storing production secrets unnecessarily, and treat exported workspace files as confidential.

7. Changes to this policy

This policy may be updated when MockPilot's features, permissions, or data handling change. The effective date at the top of this page identifies the current version.

8. Contact

MockPilot is a product by Hawker Softwares Pvt Ltd. For privacy questions or support, open an issue in the MockPilot GitHub repository or use the Hawker Softwares contact page. Do not include API keys, passwords, tokens, or other secrets in a public issue.