Privacy policy

Information handled

When you activate a mock, JediMock processes the matching URL, request and response data needed to provide the feature on the current tab. Your mock settings—including JSON, headers and matching rules—are stored locally using the browser extension storage API.

How information is used

The information is used only to create, apply and remember the mocks you request. Active page data is processed in the browser and is not available to the JediMock developer.

No data sale or advertising

JediMock does not collect analytics, transmit browsing activity, sell information, use information for advertising or credit decisions, or share information with third parties.

Optional developer support

The extension includes an optional Support JediMock link to Buy Me a Coffee. It opens only when you select it. JediMock does not append mock data, page data or tracking parameters; the destination site's own privacy terms apply after it opens. Supporting JediMock does not unlock or change extension functionality.

Sharing and retention

• Settings remain on your device until you clear them or remove the extension.
• An active mock ends when you stop it, reload the page or navigate away.
• A share link contains the selected configuration, including any headers. It is created and copied only when you ask. Remove secrets before sharing it.

Browser permissions

• activeTab: temporary access to the page where you open JediMock.
• scripting: installs or removes the mock on that page.
• storage: remembers your configuration locally.

JediMock requests no permanent access to websites.

Limited Use

JediMock's use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact and changes

Questions can be submitted through the JediMock support page. Material changes to this policy will be published here with an updated date.