Privacy Policy — Bug Report
Last updated: August 13, 2026
Bug Report ("the Extension") is a browser extension that helps developers and testers capture JavaScript errors, network errors, and a screenshot of a web page in order to generate a bug report. This policy explains what data the Extension accesses, how it is used, and what is (and is not) done with it.
1. Data the Extension accesses
The Extension only collects data when you actively click "Create report" in the extension popup, or continuously in the background for the sole purpose of detecting failed network requests (see Network activity below). It does not track your browsing or run in the background beyond that.
| Data | Source | Purpose |
|---|---|---|
| Page URL, title, viewport size, page language | The active tab, read on demand | Included in the report so the bug can be reproduced |
JavaScript errors, unhandled promise rejections, console
messages (console.error, and optionally
console.warn) |
Captured on the page you're reporting from | Diagnose the bug |
| Failed network requests (HTTP 4xx/5xx responses, connection errors) — method, URL, status code, timing | Requests made by the active tab | Diagnose network-related bugs |
| A screenshot of the visible part of the current tab | Captured only when you click "Create report" | Visual context for the bug |
| Browser user agent and browser language | navigator of the active tab |
Environment details useful for reproducing the bug |
The Extension does not access your browsing history, bookmarks, passwords, cookies, form data, or the content of other tabs that aren't the one you're actively generating a report for.
2. Where this data is stored
-
The generated report (page info, console/network errors,
screenshot) is stored using the browser's
chrome.storage.localAPI, entirely on your device. Only the most recently generated report is kept — creating a new report replaces the previous one. -
Network errors are temporarily buffered per tab using
chrome.storage.sessionso they can be included in a report. This data is automatically cleared when the tab navigates to a new page, is reloaded, or is closed. - None of this data is transmitted anywhere by the Extension. It never leaves your browser unless you choose to copy the generated Markdown report and share it yourself (for example by pasting it into an email, a ticket, or a chat message).
3. Permissions and why they're needed
| Permission | Why it's needed |
|---|---|
storage |
Save the generated report locally so it can be displayed on the report page, and remember your preferences (such as whether to include console warnings). |
webRequest |
Detect failed network requests (HTTP errors, connection failures) on the page you're reporting a bug for. |
| Host permission — all sites | The Extension needs to run on whichever page you're reporting a bug on, since it can't know in advance which website you'll want to use it on. |
4. Third parties
The Extension does not use analytics, advertising, or tracking services of any kind. It does not integrate with any third-party API or server. No data is sold, rented, or shared with anyone.
5. Your choices
- The Extension only runs when you click its icon and press "Create report" — it does not generate reports automatically.
- You can choose whether console warnings are included in reports via a setting in the popup.
- You can delete the stored report at any time by removing the Extension, or by clearing its storage via your browser's extension settings.
6. Children's privacy
The Extension is a developer tool and is not directed at, or knowingly used by, children under 13.
7. Changes to this policy
If this policy changes, the "Last updated" date above will be revised. Continued use of the Extension after a change constitutes acceptance of the updated policy.
8. Contact
Questions about this policy or the Extension can be sent to support@propublisher.be.