BugSetu is an offline-first bug capture Chrome extension. This policy explains what data the extension handles and where it goes.
The short version: BugSetu has no servers. Everything you capture stays in your own browser unless you connect your own ClickUp workspace — in which case captures are sent only to ClickUp, using your own API token, on your instruction.
Data the extension stores (locally only)
Identity profile — the name and email you enter on first run (or pull from your Chrome profile via the "Use my Chrome account" button). Used solely to label your local capture library and attribute captures ("Created by"). It is never transmitted anywhere and never verified against any server.
Captures — screenshots, annotated images, screen recordings, page metadata (URL, title, browser details), console logs from the captured page, your comments, priority, and module selection. Stored in your browser's IndexedDB.
Settings — your capture shortcut, ClickUp personal API token (if you connect one), and selected ClickUp target list. Stored in chrome.storage.local.
All of the above lives on your device. Removing the extension deletes it — Chrome removes extension storage on uninstall.
Data sent to third parties
ClickUp (optional, user-initiated). If you connect ClickUp by pasting your personal API token, captures are synced as tasks to the workspace and list you choose. This includes the screenshot or video, your comment, page URL and title, browser environment details, console logs, module, and your profile name and email (shown as "Created by" on the task). This traffic goes directly from your browser to api.clickup.com — ClickUp's privacy policy applies to data stored there.
Nothing else. No analytics, no telemetry, no error reporting, no advertising, and no BugSetu servers of any kind.
On-device AI
The optional "Draft with AI" feature uses Chrome's built-in on-device model (Gemini Nano, via Chrome's Prompt API). Prompt content — element details, page title and URL, recent console errors, and your rough note — is processed on your device by Chrome and is not sent to BugSetu or any third-party service by the extension.
Permissions
BugSetu requests only the permissions needed for bug capture: taking screenshots of the active tab, injecting the element picker and console-log collector into the page being reported, storing captures locally without a size cap, and reading your Chrome profile email — the latter only when you click "Use my Chrome account", to prefill the identity form.
Changes to this policy
If this policy changes, the updated version will be posted at this address with a new "Last updated" date. Since BugSetu has no servers or accounts, changes can never retroactively affect data — it was never collected in the first place.