buggie-privacy

Buggie — QA Companion: Privacy Policy

Last updated: 22 May 2026

Buggie (“the extension”) is a QA companion that helps testers capture bug reports from web applications and file them directly into their own Azure DevOps or JIRA workspace. This policy explains exactly what the extension accesses, where that data goes, and what it never does.

1. What Buggie accesses on your device

When you actively use Buggie on a page, it can read:

• DOM snapshots & user interactions — clicks, inputs, navigation events, and DOM state, captured locally to reconstruct the steps that led to a bug.
• Browser console logs — console.error and console.warn output from the page under test.
• Network request metadata — URLs, HTTP methods, and status codes of failed (4xx/5xx) XHR/fetch requests on the page under test. Request and response bodies are not captured.
• Screenshots and short screen recordings — only when you explicitly click the screenshot or record button.
• Configuration you enter — Azure DevOps organization / project / Personal Access Token, JIRA host / email / API token / project key, AI provider API keys (Gemini or Claude), and your preferences.

2. Where that data goes

• All captured data stays in your browser’s local storage by default. It is not uploaded anywhere automatically.
• When you click “Create bug,” the captured artifacts (steps, screenshot, optional video, network errors) are sent directly from your browser to:
  • The Azure DevOps REST API at the organization URL you configured, or
  • The Atlassian JIRA REST API at the host you configured.
  • Authentication uses the Personal Access Token / API token you supplied.
• When you use AI features (optional), the bug context is sent directly from your browser to:
  • Google Gemini API (generativelanguage.googleapis.com), or
  • Anthropic Claude API (api.anthropic.com)

  whichever you selected, using the API key you supplied. Their privacy policies apply to that data: Google AI, Anthropic.

3. What Buggie never does

• No Buggie-operated servers. We do not run any backend. Your data does not pass through any server we control.
• No analytics, telemetry, tracking pixels, or third-party SDKs that report your activity back to us or anyone else.
• No selling, renting, or transferring of personal data to third parties.
• No use of your data for advertising, model training, or any purpose unrelated to the single purpose of capturing bug reports.
• No reading of pages you are not actively testing — the extension only activates when you enable it from the popup. You can also restrict it to a list of allowed domains in the Privacy tab.

4. Permission justifications

Permission	Why Buggie needs it
<all_urls> host access	Testers evaluate arbitrary internal staging environments and third-party web apps; the extension cannot pre-declare specific hosts.
activeTab	Read the active tab when you click the extension icon, to gather page context for the bug report.
webRequest	Detect failed network requests on the page under test and attach them to the bug report.
storage	Save your configuration (ADO / JIRA credentials, preferences) locally in your browser.
identity	OAuth sign-in flow for Azure DevOps.
tabCapture	Record short video clips of the bug, only when you click the Record button.

5. Google API Limited Use disclosure

Buggie’s use and transfer of information received from Google APIs (Gemini) adhere to the Google API Services User Data Policy, including the Limited Use requirements. The information is used only to provide the user-facing AI bug-refinement feature, is not transferred to others except as needed to deliver that feature, is not used for advertising, and is not read by humans unless required for security, legal compliance, or with the user’s explicit consent.

6. Your controls

• Disable Buggie at any time via the power button in the popup. When disabled, no capture occurs.
• Restrict capture to specific domains via Settings → Privacy → Allowed Domains.
• Delete all local data by removing the extension from chrome://extensions/, or clearing storage in the Recording section.
• Revoke credentials at any time by clearing them from the Configuration tab; the extension cannot file bugs without them.

7. Children’s privacy

Buggie is a professional QA tool and is not directed at children under 13. We do not knowingly collect data from children.

8. Changes to this policy

If we change this policy, we will update the “Last updated” date at the top and post the new version at the same URL.

9. Contact

Questions or requests regarding this policy: mohankumar.thangavel@kovai.co