Privacy Policy
In short
- Nothing is recorded until you approve a specific site.
- Everything stays on your device. The extension has no server, account, analytics or telemetry, and we never receive your data.
- It stores request metadata, not content: method, URL without its query string, status, timing and a derived result.
- It never stores headers, cookies, credentials, request bodies or response bodies.
- Data leaves your device only when you press Copy for issue or Download JSON.
Who is responsible
Network Recorder is developed by Aref Farahani, an independent developer. Contact: support@aref.run
Opt-in: when recording starts
At first run, capture is off and no site is approved. To record a site you open the extension on that page, choose Approve this origin and accept Chrome's permission prompt, then turn Capture on. Only HTTPS sites, or HTTP on localhost, 127.0.0.1 and [::1], can be approved.
Approval is for one exact origin (scheme, host and port). If the page calls an API on a different origin, you approve that API origin separately. Requests to anything else are not recorded. Pausing capture or revoking a site stops recording immediately.
What the extension reads
Only for approved sites, and only for requests made by the page you approved:
- Request metadata through Chrome's
webRequestevents: HTTP method, URL, HTTP status, start and end time, redirects, and the error code when a request fails at the network level (for examplenet::ERR_CONNECTION_RESET). The extension only observes; it does not block, delay or change requests. - Error signals in JSON responses. For those same requests, the extension looks at the response's
content-typeandcontent-lengthheaders. If the response is JSON and no larger than 256 KB, it reads a copy in memory (the page still receives the original response unchanged) to check whether the top-level object containssuccess,okor a non-empty GraphQLerrorslist, as enabled for that site. The copy is then discarded. Only the result is kept: whether the response was an application error, an application success or unknown, and which rule matched. - Not read: request bodies, cookies, request headers, other response headers, form fields, page content, and anything on sites you have not approved. Responses that are larger than the limit, are not JSON, or have an HTTP status of 400 or higher are not read at all.
What is stored, and for how long
Everything is stored locally in your Chrome profile, in the extension's own storage. It is not synced and not sent anywhere.
| Data | What it contains | Retention |
|---|---|---|
| Settings | Your approved origins and API origins, the response checks enabled for them, and the capture on/off switch. | Until you change or revoke them, or remove the extension. |
| Live log | For each recorded request: method, origin and path (never the query string, fragment or credentials), status, duration, redirect information, any network error code, and the derived result. | 10 minutes (2 minutes for a request that never finished), at most 500 records per tab and 2,000 in total. Older records are deleted automatically, including when the extension wakes after being idle. |
| Saved reports | When you press Mark bug, a copy of that tab's records from the previous 30 seconds, plus the title and note you type, the rows you leave out, and any path masks you choose (including the original path, so a mask can be undone). | At most 20 reports, each for 7 days, or until you delete it. |
| Panel state | Which report is open in the side panel, kept in Chrome's temporary session storage. | Cleared by Chrome when the browser session ends. |
URL paths can contain personal data
Query strings, fragments and credentials are removed before anything is stored. The path is kept, and a path can contain identifiers such as an account ID, a user ID, an email address or a record number, for example /api/users/48213907/orders. Your live log and saved reports on your device can therefore contain such identifiers, because that is part of what you need to diagnose a bug.
How masking works. In a saved report, Mask path proposes a replacement in which segments that look like identifiers (long numbers, UUIDs, long hexadecimal strings, email addresses and long tokens) become :redacted; if none is found, the last segment is replaced. You can edit the proposal. A mask applies to every row with the same path, in both the Markdown and the JSON export, so a masked path cannot appear in one and not the other. The unmasked original stays on your device inside the saved report, so you can unmask it, until you delete the report.
Masking is a review step that you control, not an automatic guarantee: the extension cannot know which parts of a path are personal. Check the preview before you share anything. The title and note you type are exported exactly as written.
Exports are user-initiated
The extension never uploads anything. Two buttons in the side panel create output from the reviewed selection of a saved report:
- Copy for issue places Markdown on your clipboard.
- Download JSON saves a file through your browser.
Both contain: your title and note; the page origin; the time window; per request, the time, method, origin, path (masked where you chose), HTTP status, network error code, classification and matched rule, a partial-data flag, duration, and whether it was fetch or XHR. They do not contain query strings, fragments, headers, cookies, request or response bodies, rows you left out, or the original version of a masked path. Once you paste or share an export, the privacy practices of the place you share it with apply.
Controls and deletion
- Capture switch: pauses recording everywhere; open pages stop inspecting.
- Clear this tab and Clear all: delete the live log (saved reports are kept).
- Revoke site: stops recording that origin, deletes its recorded requests, and releases Chrome host permissions that no other approved site needs.
- Delete report (in the popup or the side panel): deletes a saved report.
- Removing the extension deletes its local data from your browser.
Sharing, sale and tracking
Because the data never leaves your device, we do not collect, share, sell or transfer it, and no person at the project can read it. The extension contains no advertising, analytics, telemetry or third-party services, and it loads and runs no remote code: all of its code is in the installed package, and its extension pages allow scripts only from the package itself. The data is used only for the extension's single purpose: showing you recent requests and helping you write a bug report.
Why the extension asks for each permission
| Permission | Used for |
|---|---|
webRequest | Observing the outcome of requests on approved sites (read-only). |
scripting | Registering the small content scripts that watch fetch and XHR on approved pages only. |
storage | Keeping your settings, the live log and saved reports on your device. |
activeTab | Lets the popup read the address of the tab you are on, only when you click the toolbar button. Before you approve a site the extension has no access to it, so without this the popup could not tell which site Approve this origin refers to. It gives no ongoing access. |
sidePanel | Showing a saved report beside the page. |
| Optional host access | Chrome requires every site an extension may ever ask for to be declared in advance. So that you can choose any site, Network Recorder declares HTTPS sites in general (https://*/*) and localhost over HTTP as optional, never required. None is granted at install. When you click Approve, the extension asks Chrome for access to that one site only (for example https://app.example.com/*). An API origin you add is requested separately, and Revoke site releases access that no other approved site needs. Chrome's host permissions do not include port numbers, so the extension enforces the exact origin, including the port, itself. |
This website
This website (recorder.aref.run) sets no cookies and uses no analytics, advertising or third-party scripts. It is hosted on Vercel, which, like any host, processes standard server logs (such as IP address, requested URL and user agent) to operate and secure the service. The QA demo uses synthetic data only, including a fake token that is not a real credential, and stores nothing.
Children
Network Recorder is a developer tool and is not directed at children.
Changes to this policy
If the extension's data handling changes, this page will be updated before the change ships, with a new effective date and version.
Contact
Questions about this policy: support@aref.run