BugScribePrivacy policy
BugScribe does not upload your data. It has no server, no accounts and no analytics.
Effective: 9 October 2026. Applies to the BugScribe Chrome extension, version 1.0.0 and later.
What BugScribe captures
Only on a tab you chose to analyze, from the moment you press Analyze page until you press Stop capturing or close the tab:
- Console messages: errors and warnings, with stack traces.
- Network failures: the URL, method and status of requests that failed or returned an error status. Request and response bodies, headers and cookies are never recorded.
- Your actions: clicks and page navigation, described by the element's visible label or role. Typed values are never recorded, and password and card-number fields are ignored.
- Environment: the page URL, browser and version, operating system and window size.
- A screenshot of the visible page, taken when you press Report this bug.
Masking before storage
Before anything is stored, BugScribe masks tokens, JWTs, card numbers, long keys and passwords in URLs, and sensitive URL parameters such as token, key, secret, auth, session and code. Email addresses are masked by default; you can switch that off in Settings. Masking is automatic and best-effort, so read the preview before you share a report.
Where it is stored
| Data | Where | How long |
|---|---|---|
| Captured events for a tab | Browser session storage on your device | Until you stop capturing, close the tab or close the browser |
| Saved reports (last 5) and screenshots | Extension storage and IndexedDB on your device | Until you delete them or press Clear all data |
| Settings | Extension storage on your device | Until you uninstall |
What leaves your device
Nothing. BugScribe makes no network requests of its own, includes no analytics or tracking, loads no remote code, and shares no data with third parties. Reports go only where you put them: when you copy, download or export a report, you decide where it is pasted or saved.
Why the permissions
- activeTab, scripting: to record the one tab you clicked BugScribe on and take its screenshot.
- debugger: to read Chrome's DevTools event feed (console messages and failed requests) for that tab only. This is why Chrome shows "BugScribe started debugging this browser". BugScribe does not change the page through it.
- storage: to keep the data listed above on your device.
BugScribe requests no access to all websites.
Deleting your data
- Stop capturing in the popup ends recording for the tab, and Clear empties what was captured.
- Clear all data in Settings removes captured events, drafts, saved reports and screenshots.
- Uninstalling the extension removes everything it stored.
- In Settings you can also block capture on specific sites.
Children
BugScribe is a developer and testing tool and is not directed at children.
Changes
If this policy changes, the new version is posted here with a new effective date. If a future version were ever to send data off your device, it would be opt-in and described here first.