Privacy Policy

Summary

DevKit processes captured traffic and workspace data locally in Chrome. It has no developer-operated backend and does not transmit captured data, analytics, telemetry, or identifiers to the developer or third parties.

Data DevKit processes

DevKit starts capture only after you press Record in a browser tab. While recording that tab, DevKit may process request URLs, methods, timing, headers, query parameters, request bodies, response headers, response bodies, WebSocket frames, and Server-Sent Events. This traffic may contain personal or sensitive information supplied by the sites and APIs you choose to debug.

DevKit does not monitor unrelated tabs. Each tab has an independent recording state and capture session.

Local storage and retention

DevKit uses chrome.storage.local to retain bounded, tab-specific capture sessions and reusable workspace data on your device. Workspace data may include saved request templates, collections, environments and variables, assertions, scenarios, mock/interception rules, Proto schemas, baselines, and preferences.

You can delete a tab's captured traffic with Clear session. Closing the tab deletes its stored capture session. Workspace data remains until you remove it, clear extension-local storage, or uninstall DevKit. DevKit does not provide cloud history or synchronization.

Replay and data transmission

DevKit does not send captured traffic or workspace data to the developer. When you explicitly replay a request, DevKit sends the request you reviewed or edited directly from Chrome to the selected HTTP or HTTPS target origin. DevKit requests optional access to that origin at send time. The target server's own privacy practices apply to the replayed request.

Chrome permissions

• sidePanel displays the DevKit workspace beside the selected tab.
• storage retains bounded local sessions, workspace data, recording state, and preferences.
• debugger attaches only after you press Record in a tab. It lets DevKit inspect that tab's network traffic and response bodies without requiring Chrome DevTools to be open. Chrome displays a debugging indicator while attached.
• Optional HTTP/HTTPS host access is requested only when you choose to replay a request to a specific origin.

DevKit does not request browser history, cookies, privileged tab metadata, or global background traffic access through webRequest.

Data sharing and sale

DevKit does not sell, rent, share, or use captured data for advertising, creditworthiness, analytics, profiling, or purposes unrelated to its web/API debugging functionality. No human at the developer can access locally captured data through DevKit.

Security and privacy controls

Recording is off by default. Sensitive headers are masked by default, request and response bodies are size-limited, and the number of retained requests and stream messages is bounded. DevKit does not use analytics, advertising, telemetry, tracking technologies, or remote executable code.

Limited Use

DevKit's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only to provide or improve the user-facing debugging features described above and is not transferred except where required by law or necessary for security.

Changes to this policy

This policy may be updated when DevKit's functionality or legal obligations change. The revised policy will be published on this page with a new effective date and the applicable extension version.

Contact

For privacy questions, support, or deletion requests, open an issue in the public support tracker.