Summary
100% Local · No data collected
BugTest is a Chrome extension that helps developers, designers, and QA testers capture, annotate, and manage visual bug reports about the pages they're testing. All data stays on your device. The extension makes zero outbound network requests for any purpose — no telemetry, no analytics, no error reporting, no remote configuration, no content fetching.
What we collect
Nothing. BugTest does not collect, transmit, sell, share, or store user data on any remote server. We do not have a server. No part of the extension communicates with the developer, with Google beyond standard Chrome APIs, or with any third party.
What you create — and where it lives
Everything you produce while using BugTest is stored locally inside your own Chrome browser, using Chrome's standard storage APIs. You can clear it at any time by removing the extension or clearing browser data.
| Data | Stored in |
|---|---|
| Saved bug reports (titles, screenshots, annotations, priorities, expected/actual behavior, comments, timestamps) | IndexedDB (per-origin, local) |
| Preferences (selected device, zoom, orientation, theme, grid configuration, developer name) | chrome.storage.local |
| Custom device presets you create | chrome.storage.local |
| Per-tab overlay open/closed state (so the extension doesn't auto-open on new tabs) | chrome.storage.session |
| Annotation undo / redo history | In-memory only (lost on tab close) |
Permissions and why we ask
| Permission | Why BugTest needs it |
|---|---|
activeTab | To inject the bug-reporting overlay into the tab you explicitly click on (toolbar icon or keyboard shortcut). |
tabs | To call chrome.tabs.captureVisibleTab and screenshot the visible content of your active tab when you create a bug. |
storage | To persist your preferences, custom devices, and saved bug reports locally on your device. |
scripting | To re-inject the content script if Chrome has unloaded it from a tab, so the overlay still opens reliably. |
downloads | To save the printable HTML bug report file to your Downloads folder when you click Export. |
declarativeNetRequest | To strip X-Frame-Options and CSP frame-ancestors headers on the active tab while the overlay is open, so sites that block embedding can still be previewed in the device simulator. Scoped per-tab, removed the moment you close the overlay. |
host_permissions: <all_urls> | BugTest's purpose is filing bug reports about any webpage you're testing — localhost, staging, intranet, or public sites. We can't predict which sites you'll need to test. |
Remote code
BugTest does not load, fetch, execute, or evaluate any remote code. The extension ships as a self-contained bundle of vanilla JavaScript, HTML, and CSS files. There are no <script src="https://..."> tags, no eval() of network strings, no dynamic import() from remote URLs, no Service Worker fetches, and no CDN dependencies at runtime.
Third-party services
BugTest does not use, integrate with, or share data with any third-party service. There are no analytics SDKs, no advertising networks, no error-tracking services, no A/B testing platforms, no customer-support widgets, and no social-media SDKs embedded in the extension.
Children's privacy
Because BugTest does not collect any personal information from anyone, it does not knowingly collect information from children under 13 either. The extension is intended for developers and QA professionals.
Your control
- Delete a single bug: open the Bugs panel → click 🗑 Delete on the card.
- Wipe everything: Bugs panel → Clear all bugs, or uninstall BugTest from
chrome://extensions. - Browser data clear: Chrome's Settings → Privacy and security → Clear browsing data → Cookies and other site data will also remove BugTest's IndexedDB and storage entries.
Changes to this policy
If this policy ever changes — for example, if a future feature adds optional cloud sync — we'll update the "Last updated" date above and call out the change in the extension's release notes. The current version of BugTest does not transmit data anywhere.
Contact
Questions about this policy or BugTest in general?
Email: rgunasekar1608@gmail.com