BugLens Capture

Capture bug reports — screenshot, annotations, audio, and full page context — in one click. Local-first, zero-telemetry.

View the Project on GitHub aymanrh/buglens-capture

BugLens Capture — Privacy Policy

Last updated: 2026-06-03

BugLens Capture (“BugLens”, “the extension”) is a Chrome extension that helps you capture bug reports — a screenshot, annotations, optional audio/video, and structured page context — and export or submit them to a destination you choose.

This policy explains what BugLens does and does not do with your data. The short version: BugLens collects nothing about you and sends nothing to its developer.

Data we collect

None. BugLens has no analytics, no telemetry, no tracking, and no phone-home of any kind. The developer of BugLens does not receive, store, or have access to any of your data, your browsing, or the contents of your bug reports.

Data BugLens processes — and where it stays

When you capture a bug report, BugLens processes the following entirely on your own device:

This information is stored locally in your browser (and in the files BugLens saves to your Downloads folder). It is never transmitted to the developer.

When data leaves your device

BugLens transmits a report off your device only when you explicitly send it to a destination you have configured yourself — for example, saving a local .zip (stays on your machine), or submitting to GitHub Issues or a webhook you set up. In those cases the report goes directly from your browser to that destination under your own credentials. BugLens does not route it through any developer-operated server, and the developer never sees it.

If you only use the default local-zip option, no data leaves your machine at all.

Sensitive data and redaction

BugLens redacts sensitive values (such as cookie values and authentication tokens) from captured page context by default, and shows you a preview before anything is submitted. You remain responsible for reviewing what you choose to include and where you choose to send it.

Permissions

BugLens requests the minimum permissions needed for its features and uses them only when you act. It requests no access to any website until you invoke it on a specific tab, and it declares no “read your data on all websites” host permission. A plain-language breakdown of each permission is in the extension’s installation guide.

Third parties

BugLens includes no third-party analytics, advertising, or tracking SDKs. It sets no cookies of its own. Any third party that receives a report does so only because you configured an adapter to send it there.

Children

BugLens is a developer tool and is not directed at children.

Open source

BugLens is open source and MIT-licensed. You can inspect exactly what it does.

Changes to this policy

If this policy changes, the “Last updated” date above will change. Material changes will be noted in the extension’s release notes.

Contact

Questions about this policy: hamdan.ayman.it@gmail.com