🐛 BugReporter — Privacy Policy
Last Updated: April 2026
1. Overview
BugReporter is a Chrome extension designed to help developers capture, annotate, and report bugs efficiently. This privacy policy explains how we collect, use, and protect your data.
2. What Data We Collect
2.1 Screenshots and Screen Recordings
When you use BugReporter, you have the option to:
- Capture screenshots: Images of the current webpage or selected areas
- Record screen video: Video recordings of your screen activity (optional feature)
- Annotate content: Add drawings, highlights, arrows, and text to screenshots for annotation
These captures are created locally on your device and are never automatically transmitted anywhere without your explicit action.
2.2 Voice Notes and Transcriptions
When you enable microphone recording, BugReporter may:
- Record audio locally on your device
- Use Chrome's built-in Web Speech API to transcribe your voice (runs locally, not sent to our servers)
2.3 Page Context
We automatically capture:
- Current webpage URL
- Page title
- Browser version and OS information (for bug context)
2.4 User Notes and Metadata
Any text you enter in the extension (bug descriptions, component names, severity levels) is stored locally until you generate a ticket.
3. How Your Data is Used
3.1 Ticket Generation via AI
When you click "Generate Ticket," your collected data (screenshots, notes, metadata) is sent to one of the following AI services based on your chosen provider:
- Google Gemini API — if you configured your own API key
- OpenAI API — if you configured your own API key
- Anthropic Claude API — if you configured your own API key
- xAI Grok API — if you configured your own API key
⚠️ Important: BugReporter does not host any AI services. You must provide your own API keys, and data is sent directly to the AI provider's servers. By using this extension, you agree to those providers' terms and privacy policies.
3.2 What Gets Sent to AI Providers
When generating a ticket, the following is transmitted:
- Screenshots (as base64-encoded images)
- Voice transcriptions (if generated)
- Your notes and bug description
- Component and severity information
- page metadata (URL, title, browser info)
- Any custom context you configured in settings
3.3 What Does NOT Get Sent
- Video recordings (stored locally only, never transmitted)
- Personal browsing history
- Cookies or authentication tokens (except your chosen AI provider's API key which you control)
- Any data without your explicit action to generate a ticket
4. Local Data Storage
All data before ticket generation is stored locally in your browser using Chrome's storage.local API, including:
- Screenshot data
- Your notes and fields
- Session state
- Your API keys (encrypted in Chrome's secure storage)
- Extension settings and preferences
This data persists only in your local browser profile and is not synced to cloud services.
5. API Key Security
- API keys are stored locally in your browser's secure storage
- API keys are never logged, transmitted, or shared with any third party
- API keys are only used to authenticate requests to the AI provider you selected
- You can view, edit, or delete your API keys at any time via the extension settings
6. Google OAuth Authentication (Optional)
If you configure Google OAuth for authentication, you are subject to Google's Privacy Policy. We do not receive or store OAuth tokens. OAuth is used only for user identification within the extension.
7. Third-Party Services
BugReporter integrates with the following third-party AI providers. Your data transmission to these services is governed by their privacy policies:
8. Data Retention
- Local Extension Data: Persists in your browser until you manually clear it or uninstall the extension
- AI Provider Servers: Governed by each provider's retention policies (typically 30–90 days for processing logs)
- Generated Tickets: You control where generated content is stored (you copy-paste it)
9. Data Deletion
You can delete your local data by:
- Clearing individual screenshots or notes directly in the extension
- Clicking "Reset Session" to clear all data in the current session
- Uninstalling the extension (all local data is removed)
- Clearing browser data for the extension in Chrome settings
10. Analytics and Tracking
BugReporter does not collect analytics or usage data. We do not track:
- How often you use the extension
- What websites you visit
- What bugs you report
- Any telemetry or crash data
11. Security Practices
- All data transmitted to AI providers uses HTTPS encryption
- Local storage data is isolated to your browser profile
- No data is stored on external servers owned by BugReporter
- API keys are never logged or exposed in debug messages
12. Your Rights
- Access: You have full visibility into all data collected and stored locally
- Control: You choose which AI provider to use and decide when to send data
- Deletion: You can delete any or all data at any time
- Opt-Out: Stop using the extension to stop data collection
13. Changes to This Policy
We may update this privacy policy from time to time. Any changes will be effective immediately upon publication. Your continued use of BugReporter indicates acceptance of the updated policy.
14. Contact & Support
© 2026 BugReporter. This extension is not affiliated with Google, OpenAI, Anthropic, or xAI.