Effective date: May 31, 2026
DevLogBus Browser Tap is a Chrome extension for local development workflows. It publishes user-selected browser debugging events to a DevLogBus daemon endpoint configured by the user so browser-side records can appear beside backend, CLI, journal, HTTP, and SDK records in the local development stream.
The extension’s single purpose is to publish user-triggered active-tab debugging events to the user’s local DevLogBus development log stream.
Browser Tap only captures data after the user clicks Attach for the active tab. Depending on enabled capture options, records may include:
The extension does not intentionally collect personal communications, financial information, health information, location, or personally identifiable information. However, debugging text and URLs can contain sensitive data if a website or application includes it in console output, exception text, or network URLs.
Captured records are posted to the configured DevLogBus daemon endpoint. The default endpoint is:
http://127.0.0.1:7423
DevLogBus does not operate a cloud collection service for this extension. Captured records are not sent to DevLogBus-owned servers.
The extension stores configuration in Chrome local extension storage, including:
The extension does not store captured debugging records in Chrome extension storage.
Browser Tap redacts common sensitive values before publishing records when redaction options are enabled. Redaction covers common authorization headers, bearer/basic credentials, API keys, sensitive query parameters, and cookie values.
Redaction is a safety net, not a guarantee. Users should avoid attaching the extension to sensitive workflows or pages that may expose secrets in unusual formats.
Data handled by the extension is used only for extension functionality: publishing selected browser debugging events into the user’s local DevLogBus development log stream.
The extension does not use captured data for:
Users control when capture starts and stops. Capture starts only after clicking Attach and stops when the user clicks Detach, closes the tab, disables capture, or Chrome ends the debugger session.
Users can restrict capture with allow and deny patterns before attaching to a tab.
Report privacy or security concerns through the DevLogBus project repository:
https://github.com/dan-sherwin/DevLogBus