← Back to home

Privacy Policy

Last updated: October 13, 2026

Overview

TraceBug is a QA bug reporting tool that records user interactions during testing sessions and generates developer-ready bug reports. TraceBug is designed with privacy as a core principle: nothing goes to TraceBug. There is no TraceBug server that receives your reports. A capture's content stays on your device until you choose to send it somewhere, and the only destinations are services you configure yourself: GitHub, Linear, Slack, or an AI provider.

Data Collection

When a user explicitly enables TraceBug on a website, the following data is recorded locally during the active session:

  • User interactions — clicks (element tag, text, id, class), form inputs, select changes, form submissions, and page navigation
  • Console errors — console.error() messages, unhandled exceptions, and promise rejections with stack traces
  • Network requests — fetch and XMLHttpRequest URLs, methods, status codes, and response times
  • Screenshots — captured only when the user clicks the Screenshot button, stored in memory (not persisted)
  • Environment info — browser name/version, operating system, viewport size, device type, and connection type
  • Voice transcripts — speech-to-text transcriptions when the user explicitly uses the Voice Note feature, processed by the browser's built-in Web Speech API

Data Storage

  • All recorded session data is stored in the browser's localStorage under the key tracebug_sessions
  • Screenshots and voice transcripts are stored in memory only and are not persisted
  • Sessions are capped at 50, with a maximum of 200 events per session
  • Old sessions are automatically pruned when limits are exceeded
  • The Chrome Extension stores the list of enabled site hostnames in chrome.storage.local
  • No capture is sent anywhere unless you send it — and never to TraceBug. See “What leaves your device, and when” below.
  • API tokens and keys you enter (GitHub, Linear, Slack, OpenAI, Anthropic, Ollama) are stored in chrome.storage.local on your own device, and are sent only to the service they belong to. They are never stored on the websites you test, and never reach TraceBug.

Sensitive Data Protection

TraceBug automatically redacts sensitive information before it is stored:

  • Password fields — values replaced with [REDACTED]
  • Credit card numbers — detected and redacted
  • Social Security Numbers — detected and redacted
  • API tokens and authorization headers — detected and redacted

Data Sharing

TraceBug does not:

  • Run a server that receives your reports — there isn't one
  • Use analytics, telemetry, or tracking of any kind
  • Share, sell, or transfer your data to anyone of its own accord
  • Use data for advertising, profiling, or creditworthiness
  • Send anything you have not chosen to send

What leaves your device, and when

Three things can leave your device. All three are started by you, and none of them goes to TraceBug.

  • A report you send to an issue tracker or an AI provider — when you click Send for GitHub, Linear, Slack, or ask for AI analysis, the report content is sent directly from your browser to that service, using the token you supplied. In the extension you see the full report and the destination in a confirmation window first, and nothing is sent until you approve it. Those services then handle that data under their own privacy policies.
  • The uninstall survey — removing the extension opens a page that receives the version number you had installed, plus whatever you choose to type in the optional form. Nothing else, and answering is optional: Skip sends nothing at all.
  • Anything you export and share yourself — an exported .html report is a file on your machine. Where it goes afterwards is entirely up to you.

User Control

  • TraceBug only records on websites where the user has explicitly enabled it
  • Recording can be paused and resumed at any time
  • All session data can be cleared with the "Clear" button in the dashboard
  • The extension can be disabled or uninstalled at any time
  • Clearing browser data or localStorage removes all TraceBug data permanently

Chrome Extension Permissions

activeTab — To inject the recording UI and capture screenshots on the current tab
storage — To remember which sites the user has enabled TraceBug on
scripting — To inject the TraceBug SDK into the page context for session recording
unlimitedStorage — A report with an interactive replay can exceed the default storage limit. It is stored only on your device.
alarms — To cancel an unanswered send-confirmation window after two minutes.
Optional host permissions — Not requested at install. TraceBug captures the tab you are on from your own click. It asks for site access only if you want a capture to keep running after you navigate to another site, and for one specific address when you save a GitHub, Linear, Slack, OpenAI, Anthropic or Ollama integration. Declining is fine — capture still works on the page you are on.

Open Source

TraceBug is fully open source. You can review the complete source code at github.com/prashantsinghmangat/TraceBug-ai.

Contact

For privacy questions or concerns, please open an issue at github.com/prashantsinghmangat/TraceBug-ai/issues.

This privacy policy applies to the TraceBug Chrome Extension and the TraceBug SDK (npm package: tracebug-sdk).