Privacy Policy
This policy describes what data BugZee collects, how it is used, and your rights as a user.
Last updated: March 15, 2025Contents
1. Overview
BugZee is a bug-reporting Chrome Extension designed for development teams. It captures page context when you explicitly submit a bug report and sends that data to a webhook URL that you configure and control. BugZee does not operate any central server that stores your reports, and it does not collect data in the background or without your action.
This Privacy Policy applies to the BugZee Chrome Extension and its companion web dashboard hosted at bugzee.ditis.us. By installing the extension or using the dashboard, you agree to the practices described here.
2. Data Collected
BugZee only collects data at the moment you click Submit Report. No background data collection occurs. The following information is captured per report:
| Data Point | Description | Required? |
|---|---|---|
| Screenshot | A full-page screenshot of the active browser tab at the moment of submission. | Yes |
| Page URL | The URL of the page where the bug was found. | Yes |
| Page title | The <title> of the page for easier identification. | Yes |
| Browser info | Browser name and version (e.g. Chrome 122), derived from the User-Agent string. | Yes |
| Console errors | JavaScript errors logged to the browser console on the reported page. | Yes |
| Bug description | The text you type describing the bug. | Yes |
| Steps to reproduce | Optional steps you type to help reproduce the bug. | Optional |
| Severity | The severity level you select (Low / Medium / High / Critical). | Yes |
| Reporter name & email | Your name and email address if you choose to provide them in the extension settings. | Optional |
| Destination email | An email address you enter in settings to receive report notifications. Stored locally in your browser only. | Optional |
| Webhook URL | The endpoint you configure for receiving reports. Stored locally in your browser only. | Optional |
BugZee does not collect: browsing history, passwords, form input on pages you visit, cookies, location data, microphone or camera data, or any data from pages you visit without submitting a report.
3. How Data Is Used
Data collected during a bug report submission is used solely for the following purposes:
Sending to your configured webhook
When you submit a report, the data is sent as a JSON payload to the Webhook URL you have configured in the extension settings. This URL is entirely under your control — it may be the BugZee dashboard at bugzee.ditis.us or any endpoint you choose. BugZee the extension itself does not retain, analyse, or forward this data to any other destination.
Forwarding to Jira (optional)
If you have configured Jira integration in the BugZee dashboard, the server you control will forward the report to your Jira project as a new issue, with the screenshot attached. This forwarding is performed by your server using the credentials you provide.
Forwarding by email (optional)
If you have configured SMTP settings in the BugZee dashboard and the report payload includes a destination email address, the server you control will send the report as a formatted HTML email using your SMTP credentials.
Local settings storage
Your extension settings (Webhook URL, reporter name/email, destination email) are saved locally in your browser using Chrome's storage.sync API. They are synced across your own Chrome profile if you are signed into Chrome, but are not accessible to BugZee or any third party.
4. Data Storage & Retention
Extension (browser)
Settings are stored in Chrome's local and sync storage APIs on your device. A history of your last 50 submitted reports is kept in local storage for reference. This data is deleted automatically when you uninstall the extension, or can be cleared at any time by resetting extension storage via chrome://extensions.
Dashboard server
If you use the BugZee self-hosted dashboard, bug reports are stored in a PostgreSQL database on the server you (or your team) operate. You have full administrative control over that database. Reports can be deleted at any time from the Reports page. Screenshots are stored as base64 data within each report record.
No centralised BugZee storage
BugZee does not operate a central server that stores your bug reports. All report data flows from the extension directly to the endpoint you configure. There is no BugZee-operated cloud database containing your reports.
5. Extension Permissions
BugZee requests the following Chrome permissions. Each is limited to what is strictly necessary:
| Permission | Justification |
|---|---|
| activeTab | Grants temporary access to the tab you are actively viewing at the moment you click Submit. Used for screenshot capture and dynamic script injection to collect console errors. The extension has no background access to any tab. |
| scripting | Required to dynamically inject a local script into the active tab to collect console errors from the page you are reporting on, so those errors can be included in the bug report for easier debugging. |
| storage | Used to save your settings (webhook URL, destination email) locally in your browser. Nothing is synced to external servers without your action. |
| tabs | Used to read the URL and title of the current tab to include in the bug report, so the developer knows exactly which page the bug occurred on. |
| downloads | Used only when you choose to download a bug report as a local JSON file. The extension never downloads files automatically or without your explicit action. |
6. Remote Code
BugZee does not use any remotely hosted code. All JavaScript executed by the extension is bundled entirely within the extension package and reviewed as part of the published version. No scripts, modules, or executable content are fetched from external URLs at runtime.
This extension complies with Chrome Web Store's Manifest V3 policy prohibiting remotely hosted code execution.
7. Third-Party Services
Jira (Atlassian)
If you connect BugZee to Jira, bug report data (description, screenshot, page URL, severity) is sent to your Jira project via the Atlassian API using credentials you provide. Atlassian's own Privacy Policy governs how that data is handled within Jira.
SMTP / Email provider
If you configure email notifications, bug report summaries are delivered via the SMTP server you specify (e.g. Gmail, Outlook). The email provider's own privacy policy applies to emails in transit.
Website analytics
The BugZee public website (bugzee.ditis.us) uses Google Analytics 4 (GA4) to measure traffic and page popularity. GA4 collects anonymised usage data such as pages visited and general geographic region. No personally identifiable information is sent. You can opt out by using a browser-level ad or analytics blocker.
Extension analytics
The BugZee Chrome extension sends anonymous usage events (e.g. popup opened, bug report submitted, Jira submission result) to the BugZee server, which forwards them to Google Analytics 4. Each extension installation is identified by a randomly generated ID stored locally — this ID is not linked to any personal information. No bug report content, page URLs, or credentials are included in these events. You can review the full list of tracked events in the extension source at popup.js.
No advertising
BugZee does not use any advertising networks, tracking pixels, or third-party marketing platforms.
Google Fonts
The BugZee web dashboard and support pages load fonts from Google Fonts. This involves a request to Google's servers; see Google's Privacy Policy for details. The Chrome extension itself does not use Google Fonts.
8. Your Rights
Access and deletion
Because bug report data is stored on infrastructure you control (your PostgreSQL database), you have direct access to all stored data and can delete individual reports or all reports at any time from the Reports page or directly in your database.
Extension data
Your local extension settings can be cleared at any time by removing the extension from Chrome (chrome://extensions → Remove). This permanently deletes all locally stored settings and report history.
No account required
BugZee does not require you to create an account or provide any personal information to use the core extension functionality. Reporter name and email fields are entirely optional.
Children's privacy
BugZee is intended for use by developers and QA professionals. It is not directed at children under 13, and we do not knowingly collect personal information from children.
9. Contact
If you have questions or concerns about this Privacy Policy or how BugZee handles your data, please contact us:
Email: privacy@ditis.us
Support: bugzee.ditis.us/support
General: support@ditis.us
We may update this Privacy Policy from time to time. Changes will be reflected by updating the "Last updated" date at the top of this page. Continued use of the extension after changes constitutes acceptance of the updated policy.