Last updated: November 2, 2026

GraphQL Network Inspector is a Chrome DevTools extension for inspecting the GraphQL requests a web page makes. This policy explains what data it handles and where that data goes.

What the extension handles

• GraphQL requests and responses of the page you are inspecting: URL, method, headers, query, variables and response body. They are shown in the DevTools panel and kept only in the panel's memory. They are discarded when you clear the list, navigate (unless "Preserve log" is on) or close DevTools.
• Mock rules you create: operation name, match conditions, response body, status code and delay.
• Playground settings you enter: endpoint URLs, request headers per origin (which may include authorization tokens) and the cookie setting.
• GraphQL schemas you load by introspection or from a file.

Mock rules, Playground settings and schemas are saved in chrome.storage.local on your computer so they are still there the next time you open DevTools. Panel preferences (search filter, layout, language, "Preserve log") are saved in the extension's own local storage.

Where the data goes

• Nothing is sent to the developer or to any third party. The extension has no server, analytics or tracking.
• The only network requests the extension makes on its own are the ones you trigger in the Playground (running a query or loading a schema). They go to the endpoint you entered, with the headers you set, and their responses are shown only to you.
• When you export mock rules, the file is saved to your computer. Playground headers are never included in the export.

Removing your data

Delete individual mock rules, headers and schemas from the panel, or remove the extension to erase everything it stored.

Changes

If this policy changes, the new version will be posted at this address with a new date, and any change in how data is handled will be announced in the extension's release notes before it takes effect.

Contact

[email protected]

GraphQL Network Inspector 개인정보처리방침