Your debugging data stays on your device

Privacy Policy

DevKit โ€“ API Debugger & Network Inspector ("DevKit") is a Chrome extension for capturing, inspecting, editing, sending, comparing, and organizing web/API traffic. This policy explains how DevKit handles data.

Effective November 9, 2026 ยท Applies to version 0.2.0

Summary

DevKit processes captured traffic and workspace data locally in Chrome. It has no developer-operated backend and does not transmit captured data, workspace 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, including authentication headers and cookies, supplied by the sites and APIs you choose to debug.

While a tab is recording, DevKit may also:

  • block, delay, mock, or modify that tab's matching traffic, but only according to rules you have enabled; and
  • add a small script to the tab that keeps a reference to each WebSocket the page opens, so that a frame you type can be sent through the page's own connection. The script does not read page content, change the DOM, or send anything on its own.

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 requests and collections, environments and variables, authentication values you enter (bearer tokens, basic-auth usernames and passwords, API keys), files attached to multipart bodies, Proto schemas, assertions, baselines, scenarios, mock and interception rules, the history of the last runs of each saved request including the responses received, and preferences.

Values marked as secret are masked on screen, but they are stored in local extension storage like other workspace data, because DevKit needs them to send requests. Files you import (cURL commands, Postman collections, .proto files, JSON exports) are read locally, and exports are saved only where you choose. An exported workspace leaves out secret variable values unless you choose to include them.

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.

Sending and data transmission

DevKit does not send captured traffic or workspace data to the developer. When you explicitly send a request, DevKit sends the request you reviewed or edited, including any authentication values you attached to it, directly from Chrome to the selected HTTP or HTTPS target origin. DevKit requests optional access to that origin at send time. When you send a WebSocket frame, it goes through the connection the page already has open. The target server's own privacy practices apply to that traffic.

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 read that tab's network traffic and response bodies without requiring Chrome DevTools to be open, apply interception rules you have enabled, and send WebSocket frames you type. Chrome displays a debugging indicator while attached.
  • Optional HTTP/HTTPS host access is requested only when you choose to send 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 or stored data for advertising, creditworthiness, analytics, profiling, or purposes unrelated to its web/API debugging functionality. No human at the developer can access data processed by 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.