Privacy Policy

Extension: BugSnapPro | Last updated: April 6, 2026

      BugSnapPro is a developer tool designed solely for capturing browser bug
      reports. All data collected by this extension is used exclusively for
      generating a local debug report at the user's explicit request.
      No data is transmitted to any external server, sold, or shared with any
        third party.
    

      🔒 100% Local — No Server Involved. BugSnapPro does
      not have a backend server. All data accessed during a bug
      capture session — including screen recordings, console logs, network
      requests, cookies, and browser storage — is processed and remains
      entirely on your local machine, inside your browser.
      Nothing leaves your device unless you choose to export and share
      the report yourself.
    

      ⚠️ Important: When you export a bug report (e.g., as a
      PDF or file), that file may contain sensitive page data such as cookies,
      storage values, or network headers. Please review the report before
      sharing it with others. The extension developer has no access to this data
      at any point.
    

1. Overview

BugSnapPro ("the Extension") is a Chrome browser extension that helps developers, QA teams, and testers capture comprehensive bug reports including screen recordings, console logs, network activity, and browser storage diagnostics. This Privacy Policy explains what data the Extension accesses, why, how it is handled, stored, and shared (or not shared).

2. Data We Collect and Why

The Extension accesses the following data only when the user explicitly initiates a bug capture session:

Screen Recording (Tab Video): A video recording of the active browser tab is captured using the tabCapture API. This is used solely to visually document the bug being reported.
Console Logs: JavaScript console output (errors, warnings, logs) from the active tab is collected via the debugger API to provide runtime debugging context.
Network Requests: HTTP/HTTPS network requests made by the active tab during the capture session are recorded via the debugger API. This includes request URLs, methods, headers, and response status codes.
Cookies: Cookies associated with the active tab's website are inspected using the cookies API. This helps diagnose session and authentication-related issues.
Browser Storage (localStorage, sessionStorage, IndexedDB): Storage data from the active tab's origin is read using injected scripts via the scripting API, to assist in diagnosing state-related bugs.
Page Metadata: Information such as page URL, title, user agent, and PWA-related details is collected from the active tab to provide context for the bug report.
Extension Preferences: User preferences and temporary session state (e.g., whether a recording is in progress) are stored locally using the Chrome storage API.

3. How Data Is Used

All data accessed by the Extension is used exclusively to:

Generate a local bug report (e.g., a PDF or exportable file) at the user's request.
Display diagnostic information within the Extension's interface for the user's review.
Temporarily store session state and preferences within the user's own browser.

The Extension does not use collected data for analytics, advertising, profiling, or any purpose unrelated to bug report generation.

4. Data Storage

      🖥️ Your data never leaves your machine. BugSnapPro has no
      server, no database, and no cloud backend. Every byte of data the
      extension accesses stays on your local device.
    

All captured data is stored locally within the user's browser using Chrome's built-in storage APIs.
Data is held only for the duration of the active bug capture session or until the user clears it.
No data is written to any external database, cloud storage, or remote server — not even temporarily.
The extension developer has zero access to any data you capture.

5. Data Sharing

The Extension does not transmit any collected data to the developer, to third-party services, or to any external server.
The Extension does not sell, rent, license, or otherwise transfer user data to any party.
Bug reports generated by the Extension are exported only by the user's explicit action (e.g., downloading a file). The user controls where this report is shared.

6. Third-Party Services

The Extension does not integrate with, or send data to, any third-party analytics, advertising, or data processing services. No remote code is executed by this Extension — all scripts are bundled locally within the extension package.

7. Permissions Justification

Each Chrome permission requested by this Extension is required for its core bug-capture functionality:

activeTab: To access the currently active tab when the user starts a capture session.
tabs: To identify and manage the active tab and open the reporting interface.
scripting: To inject local scripts for collecting page-level storage and DOM diagnostics.
storage: To save temporary session state and user preferences locally.
debugger: To collect console logs and network request data during a debugging session.
cookies: To inspect cookies of the reported website for session/auth diagnostics.
tabCapture: To record the active tab's screen when the user starts a recording.
Host permissions (<all_urls>): To allow the Extension to function on any website where the user needs to capture a bug report.

8. Children's Privacy

This Extension is intended for use by developers, QA engineers, and technical professionals. It is not directed at children under the age of 13, and we do not knowingly collect data from children.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be reflected by updating the "Last updated" date at the top of this page. Continued use of the Extension after any changes constitutes acceptance of the updated policy.

10. Contact

If you have any questions or concerns about this Privacy Policy, please open an issue on the BugSnapPro GitHub repository or contact the developer directly via GitHub.