Privacy policy — last updated 2026-07-27
Everything G-garry records stays on your own computer.
G-garry is a developer tool. It adds a panel to Chrome DevTools that records the
fetch() and XMLHttpRequest calls made by the page a developer
is debugging.
| Name | Status | Time |
0 ms50100150
|
||
|---|---|---|---|---|---|
|
No requests
G-garry makes none of its own, to any destination. |
|||||
What the extension accesses
To do its job, the extension reads, on pages where it is active:
- the URLs, headers, timings and bodies of the page's fetch/XMLHttpRequest calls, including request headers that carry credentials (Authorization, Cookie, session tokens);
- the URL of the page and of the frame that issued each request;
- text content of a page element the user explicitly selects with the built-in element picker;
- the fact that a click, form submission or input change occurred, used only to associate a request with the part of the page that triggered it.
Where that data goes
Nowhere. All of it is kept on the user's own computer, in the
browser's extension storage (chrome.storage.session for the request log, which
is cleared when the browser closes, and chrome.storage.local for the user's
settings and mock rules).
The extension contains no analytics, no telemetry, no crash reporting, and no server of its own. It makes no network request of its own to any destination. The only outgoing request it can cause is the “replay” action, which the user triggers explicitly and which re-sends a captured request to the same endpoint the page had already called.
We do not collect, receive, sell, or transfer any of this data. The developers of this extension never see it.
User control
The user can clear the recorded log at any time, disable capture entirely, and remove all stored data by uninstalling the extension. Exported files (HAR or session JSON) are written by the user's own action, to a location the user chooses, and have credential-bearing headers redacted by default.