Repro is a Chrome extension that captures browser API network requests so you can inspect, replay, save, and export them for debugging. This policy explains what data Repro accesses, how it is used, and — most importantly — what Repro does not do with it.
When you start a capture on a browser tab, Repro reads network activity for that tab in order to build the request list and detail view you see in the extension. Depending on the traffic your browser generates while you use that tab, this can include:
| Category | What this looks like in Repro |
|---|---|
| Website content | Request and response bodies (e.g. JSON payloads, form data) sent to and from the site you're debugging. |
| User activity | Network activity on the tab you choose to capture — request URLs, methods, status codes, and timing. |
| Authentication information | Authorization headers, cookies, and API tokens that happen to be present in captured requests. Repro masks these values by default whenever you copy or export a request. |
Repro does not access any of this unless you explicitly start a capture session on a tab. Capture is always opt-in and always scoped to the single tab you choose.
All captured requests, saved collections, and extension settings are stored using Chrome's local storage (chrome.storage.local) directly on your device. Repro does not operate any external server, and this data is never transmitted to us or to any third party.
Data only leaves your device if you personally choose to copy an export and paste it somewhere else — for example into an AI coding assistant, Slack, Jira, or GitHub. That action, and the destination, is entirely under your control. Repro itself does not send this data anywhere on your behalf.
Whenever you copy or export a request, Repro masks values that look like secrets — Authorization headers, cookies, API keys, bearer or basic auth tokens, and other secret-like strings — by default. You can choose to manually reveal these values before copying if you need to, but they are hidden unless you take that action.
You can clear a capture session, delete individual saved requests, or delete entire collections at any time from within Repro. Uninstalling the extension removes all locally stored Repro data from your browser.
If this policy changes, the "Last updated" date at the top of this page will be revised, and material changes to how Repro handles data will be reflected here before they take effect.
Questions about this policy or how Repro handles data can be directed to us here: linktr.ee/bomosi