Privacy Policy

Last updated: April 19, 2026

This Privacy Policy describes how BugMe ("the Extension") handles data collected during its use. BugMe is a Chrome extension that records browser interactions and diagnostic data to help users create structured bug reports in Azure DevOps.

1. Data we collect

BugMe collects the following data during an active, user-initiated recording session:

• User activity — clicks, text inputs, page navigation events, and scroll actions captured as reproduction steps.
• Website content — browser console log messages and network request details (URL, HTTP method, status code, duration) from the active tab.
• Screenshots — point-in-time PNG screenshots of the active tab, taken only when explicitly requested by the user.
• Browser environment — Chrome version, screen dimensions, window dimensions, device pixel ratio, and page URL at the time of capture.
• Authentication information — your Azure DevOps Personal Access Token (PAT) and organisation URL, stored locally for API authentication.

2. How we use your data

All collected data is used exclusively to fulfil the single purpose of BugMe: creating a documented Bug work item in your Azure DevOps organisation. Specifically:

• Reproduction steps, environment details, and screenshots are submitted to your Azure DevOps work item via the official ADO REST API using your own PAT.
• Console and network diagnostic data is posted as a comment on the same work item.
• Your PAT and organisation URL are used only to authenticate API calls to your Azure DevOps instance.

BugMe does not use your data for advertising, analytics, profiling, or any purpose unrelated to bug report creation.

3. Data storage

• Bug report data (actions, metadata) is persisted in chrome.storage.local on your device only.
• Your ADO configuration (organisation URL and PAT) is stored in chrome.storage.local on your device only.
• Active recording state is held in chrome.storage.session and cleared when the browser session ends.
• Screenshots are stored in IndexedDB (BugMeDB) on your device only.

No data is stored on any external server operated by BugMe.

4. Data sharing and transfer

BugMe does not sell, rent, trade, or transfer your data to any third party. The only external transmission of data is from your browser directly to your own Azure DevOps organisation when you explicitly click "Create Bug in ADO". This transmission is made using your own credentials to your own account.

5. Data retention and deletion

All captured data remains on your device in browser storage. You can delete individual bug reports or all history at any time from within the extension. Uninstalling BugMe removes all extension storage from your browser.

6. Permissions

BugMe requests the following Chrome permissions and uses them only as described:

• activeTab — to take screenshots of the current tab on explicit user request.
• debugger — to capture console messages and network requests via the Chrome Debugger Protocol during an active session.
• scripting — to inject the content script into the active tab when a recording session starts.
• storage — to persist bug reports, ADO configuration, and recording state on your device.
• tabs — to broadcast live recording state updates to the extension popup.
• host_permissions (<all_urls>) — to allow capture on any website the user chooses to test.

7. Security

Your PAT is stored only in chrome.storage.local on your machine and is never transmitted to any server other than your own Azure DevOps API endpoint. BugMe does not log, cache, or expose your PAT in any other way.

8. Children's privacy

BugMe is intended for use by software development and QA professionals. It is not directed at children under the age of 13 and does not knowingly collect data from children.

9. Changes to this policy

If this Privacy Policy is updated, the revised version will be published at this URL with an updated date. Continued use of the extension after changes constitutes acceptance of the updated policy.

10. Contact

For questions about this Privacy Policy, open an issue on the BugMe GitHub repository.