BugSnap — Privacy Policy

01 Overview

BugSnap ("the Extension") is a Chrome browser extension that helps software teams report bugs to Jira by capturing screenshots, screen recordings, console logs, network requests, and other diagnostic information from the browser.

This Privacy Policy explains what data the Extension accesses, how it is used, and where it goes. We are committed to full transparency: BugSnap is designed as a privacy-first tool where you remain in complete control of your data.

02 Data Collected & Where It Goes

The Extension accesses the following categories of data when you explicitly trigger a capture action. No data is collected passively or in the background without your interaction.

Data Type	Purpose	Storage	Sent To
Screenshots	Visual capture of the current tab for bug reports	Local only	Jira (as ticket attachment, on submit)
Screen recordings	Video capture of tab activity	Local only	Jira (as ticket attachment, on submit)
Console logs	JavaScript errors, warnings and log output	Local only	Jira (as ticket comment, on submit)
Network requests	XHR/fetch URLs, status codes, timings	Local only	Jira (as ticket comment, on submit)
Session replay	Click, scroll, input and navigation events	Local only	Jira (as ticket comment, on submit)
`localStorage` / `sessionStorage`	Browser storage state at time of bug	Local only	Jira (as ticket comment, on submit)
Cookies (non-sensitive)	Session state context. Auth tokens are automatically masked.	Local only	Jira (as ticket comment, on submit)
Page URL & title	Identifies the page where the bug occurred	Local only	Jira (in ticket description, on submit)
Browser & viewport info	Environment details for bug reproduction	Local only	Jira (in ticket description, on submit)
Jira credentials	API host, email, token, project key	Local only	Jira API (authentication only)
Anthropic API key	Powers optional AI description improvement	Local only	Anthropic API (optional feature only)
Slack webhook URL	Optional ticket creation notifications	Local only	Slack API (optional feature only)

We do not operate any servers. All data flows directly from your browser to the services you have configured (Jira, Anthropic, Slack). BugSnap has no backend, no analytics, and no telemetry.

03 Permissions & Why We Need Them

The Extension requests the following Chrome permissions. Each is strictly necessary for the features described.

📸

activeTab

Captures a screenshot of the visible tab when you click the extension icon. Only accessed on explicit user action.

🗂

tabs

Identifies the current tab for capture and opens the created Jira ticket in a new tab after submission.

💾

storage

Persists your Jira configuration and API keys locally in your browser using chrome.storage.sync. Data never leaves your device except via your own Jira/Anthropic API calls.

💉

scripting

Injects the log-collection script into the active tab to capture console errors and network requests, and injects the stop-recording overlay bar during recording sessions.

⏺

tabCapture

Captures the video stream of the active tab for screen recording. Only activates when you explicitly click Record.

🖥

offscreen

Creates a hidden document to run the MediaRecorder API. Chrome service workers cannot use Media APIs directly; this is the only way to encode video in a Manifest V3 extension.

🌐

<all_urls> host permission

Required to collect debug data from any website you are viewing when you trigger a bug report. The extension only activates when you interact with it — it does not monitor browsing activity passively.

04 Third-Party Services

BugSnap communicates with the following external services, all of which are configured by you and only contacted when you perform an explicit action:

Service	When contacted	What is sent	Their privacy policy
Jira (Atlassian)	When you click "Create Ticket"	Bug title, description, screenshot, recording, debug logs	atlassian.com
Anthropic Claude API	Only when you click "✨ Improve with AI" (optional)	Bug title and description draft. Your own API key is used.	anthropic.com
Slack	Only after ticket creation, if a webhook is configured (optional)	Ticket key, title, priority, and Jira URL	slack.com

We have no affiliation with these services beyond using their public APIs. Your credentials and data are yours — we are simply the conduit.

05 Sensitive Data Handling

BugSnap applies automatic redaction to sensitive values before they are included in bug reports:

▸ Passwords in form inputs are automatically replaced with •••• in session replay events.
▸ Auth cookies — any cookie whose name contains token, auth, session, jwt, or secret — are replaced with a character count only.
▸ You are in full control of what gets submitted. You can review all captured data in the extension popup before clicking "Create Ticket".

06 Data Retention & Deletion

All data captured by BugSnap is held temporarily in chrome.storage.local during your active session and is cleared when you close the popup, clear the capture, or reset between bug reports.

Your settings (Jira credentials, API keys) are stored in chrome.storage.sync and persist until you manually clear them in Settings or uninstall the extension.

To delete all BugSnap data: go to chrome://extensions, find BugSnap, click "Remove", and confirm. All locally stored data will be permanently deleted.

07 Children's Privacy

BugSnap is a developer tool intended for use by adults and software development professionals. It is not directed at children under the age of 13, and we do not knowingly collect any information from children.

08 Changes to This Policy

If we make material changes to this Privacy Policy, we will update the "Last updated" date at the top of this page and, where appropriate, provide notice through the extension itself. Continued use of BugSnap after changes constitutes acceptance of the updated policy.

Because BugSnap collects no personal data and has no user accounts, we are not able to notify you directly by email. We recommend checking this page periodically.

09 Contact

If you have questions or concerns about this Privacy Policy or BugSnap's data practices, please reach out. We aim to respond within 5 business days.

Questions about privacy? We're happy to help.

✉ privacy@bugsnap.dev