AI Bug Reporter

Privacy Policy

Last updated: February 17, 2026

1. Introduction

AI Bug Reporter ("the Extension") is a Chrome browser extension designed to help developers and QA teams capture and report bugs efficiently. This Privacy Policy explains how we collect, use, and protect your information when you use our Extension.

2. Data We Collect

When you actively initiate a bug report, the Extension collects the following data from the current web page:

  • Screenshot: A visual capture of the current browser tab, taken only when you click the capture button.
  • Console Logs: JavaScript console messages (log, warn, error, info) generated by the web page during your browsing session.
  • Network Requests: HTTP request details including URL, method, status code, response body, and timing information. Automatically generated cURL commands for debugging purposes.
  • System Information: Browser name and version, operating system, viewport size, language, and timezone.
  • Page Information: The URL and title of the current web page.
  • Screen Recording: Video capture of the browser tab, only when you explicitly start a recording session.
  • User Description: Any text you voluntarily enter to describe the bug.

3. How Data is Stored

All collected data is stored locally on your device using:

  • Chrome Storage API: For storing bug report metadata (titles, descriptions, system info, logs).
  • IndexedDB: For storing larger files such as screenshots and video recordings.

Your data remains on your device and is not automatically transmitted to any external server.

4. Third-Party Services

The Extension uses the following third-party service:

  • Groq API: When you capture a bug, the collected data (console logs, network request summaries, system info, and your description) is sent to the Groq API to generate an AI-powered bug report. This data is processed by Groq's servers to produce the analysis. Screenshots and video recordings are NOT sent to Groq.

Please refer to Groq's Privacy Policy for information on how they handle data.

5. Data We Do NOT Collect

  • Personal identification information (name, email, address)
  • Passwords or authentication credentials
  • Financial or payment information
  • Health or medical data
  • Browsing history beyond the current page
  • Cookies or tracking identifiers
  • Data from other browser tabs or windows

6. Data Sharing

We do not sell, trade, or transfer your data to third parties. Data is only shared with the Groq API for the sole purpose of generating AI-powered bug reports, as described in Section 4. No data is used for advertising, analytics, or any purpose unrelated to bug reporting.

7. Your Control Over Data

You have full control over your data:

  • View: Access all your bug reports through the Extension's reports page.
  • Export: Download your reports as Markdown, PDF, or JSON files.
  • Delete: Remove individual reports or clear all data at any time.
  • Uninstall: Removing the Extension deletes all locally stored data.

8. Browser Permissions

The Extension requires the following permissions, each used solely for bug reporting functionality:

PermissionPurpose
activeTabCapture screenshot and access current page URL
tabsGet tab URL and title for bug reports
scriptingInject monitoring scripts for console and network logs
storageStore bug reports locally on device
contextMenusAdd right-click menu option for quick bug reporting
tabCaptureRecord screen when user initiates recording
offscreenProcess video recording using MediaRecorder API
host_permissionsEnable bug reporting on any website

9. Security

We take reasonable measures to protect your data. All data is stored locally using Chrome's built-in storage APIs which are sandboxed and isolated from other extensions and websites. Network communication with the Groq API is conducted over HTTPS.

10. Children's Privacy

The Extension is designed for software developers and QA professionals. We do not knowingly collect data from children under the age of 13.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be reflected on this page with an updated revision date. Continued use of the Extension after changes constitutes acceptance of the updated policy.

12. Contact

If you have any questions or concerns about this Privacy Policy, please contact us through our GitHub repository or email at framazanyilmaz@gmail.com.