Privacy Policy

Last updated: July 14, 2026

1. Introduction

BlabberBug ("we", "us", "our") is an independently operated service. This Privacy Policy explains how we collect, use, and protect your information when you use BlabberBug, including the web dashboard and Chrome extension.

By using BlabberBug, you agree to the collection and use of information in accordance with this policy. If you have questions, contact us at support@blabberbug.app.

2. Information We Collect

Account Data

When you register via Clerk (our authentication provider), we collect your email address and display name. Clerk handles all password management and authentication securely on our behalf.

Bug Recording Data

When you create a bug recording through the Chrome extension, we collect:

  • Screenshots of the tab you are reporting on
  • Screen or tab recordings (video files). For a screen recording, you choose which window or screen to share from Chrome's own picker
  • Session replay of the recorded page. All form inputs are masked by default, so text you type into fields is not captured in the replay
  • Voice audio from your microphone (when enabled), which is transcribed to text for the report
  • Browser console logs (errors, warnings, info)
  • Network request logs (URLs, methods, status codes, timing, and request/response bodies up to 100 KB each)
  • User actions (clicks, navigation)
  • Device and browser information
  • Page URL where the recording was made

AI-Generated Content

Bug report titles, descriptions, and structured reports are generated by third-party large language models accessed through the OpenRouter gateway, using your recording data. BlabberBug operates these models using its own managed credentials; you do not need to provide an API key. The generated reports are stored alongside your recordings.

Integration Credentials

When you connect an issue tracker (Linear, GitHub, Jira, or Slack), we store the credentials or tokens needed to file reports on your behalf. All such credentials are encrypted using AES-256-GCM before storage. Transcription (Deepgram) and AI report generation run on BlabberBug's own managed credentials; you do not supply keys for those.

Chrome Extension Local Storage

The Chrome extension stores the following data locally on your device only:

  • backendToken -- your authentication token
  • backendUrl -- the URL of your BlabberBug instance
  • micDeviceId -- your selected microphone device

This data is never sent to our servers beyond its intended use.

Cookies

We use essential cookies only:

  • __session -- maintains your login session (Clerk)
  • __client_uat -- tracks authentication state (Clerk)

We do not use analytics cookies, tracking cookies, or advertising cookies.

3. How We Use Your Information

  • Service provision -- to operate BlabberBug and provide bug recording, AI report generation, and bug report submission features
  • Authentication -- to verify your identity and maintain your session
  • AI processing -- to send recording data to AI services for generating bug report titles and descriptions
  • Bug report submission -- to submit bug reports to your configured integrations (Linear, GitHub, Jira, Slack)

We do not sell, rent, or trade your personal data to any third party. We do not use your data for advertising, analytics, or any purpose unrelated to providing the BlabberBug service.

4. Third-Party Services

BlabberBug integrates with the following third-party services:

  • Deepgram -- audio transcription of voice recordings
  • OpenRouter -- gateway used to access the third-party AI models that generate bug reports
  • Linear, GitHub, Jira, Slack -- bug report submission to your project management tools
  • Clerk -- user authentication and session management
  • Railway -- application hosting and infrastructure

Transcription and AI report generation run on BlabberBug's own managed credentials. Credentials for the issue trackers you connect (Linear, GitHub, Jira, Slack) are provided by you and stored encrypted. You are responsible for reviewing and agreeing to the terms and privacy policies of these third-party services.

5. Data Storage and Security

  • All data is transmitted over HTTPS encrypted connections
  • Application data is stored on secure, hosted servers
  • Video files are stored on secure, access-controlled servers
  • Authentication is managed by Clerk, a dedicated auth provider
  • API keys and integration credentials are encrypted at rest with AES-256-GCM
  • Sessions are managed with JWT tokens

6. Data Retention

Your data is retained for as long as your account exists. When you delete a recording or your account, all associated data (video files, logs, AI-generated content) is permanently removed via cascade deletion.

7. Your Rights (GDPR)

If you are located in the European Economic Area, you have the following rights regarding your personal data:

  • Access -- request a copy of the data we hold about you
  • Rectification -- request correction of inaccurate data
  • Erasure -- delete your account and all data through your dashboard settings, or contact us
  • Portability -- request your data in a portable format
  • Restrict processing -- request that we limit how we use your data
  • Object -- object to our processing of your data

To exercise any of these rights, contact us at support@blabberbug.app.

8. Children's Privacy

BlabberBug is not intended for use by anyone under the age of 16. We do not knowingly collect personal data from children under 16. If you believe we have collected data from a child under 16, please contact us immediately.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date. Continued use of BlabberBug after changes constitutes acceptance of the updated policy.

10. Chrome Web Store Compliance

BlabberBug's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Specifically:

  • Data collected through Chrome APIs (tab capture, active tab, scripting) is used solely to provide the bug recording and reporting functionality described in this policy
  • Data is not transferred to third parties except as necessary to provide the service (e.g., audio sent to Deepgram for transcription, recording data sent to OpenRouter for AI report generation)
  • Data is not used for advertising, creditworthiness determination, or any purpose unrelated to the extension's core functionality
  • No human can read your data unless you provide explicit consent, it is necessary for security purposes, or it is required by law

11. Contact

For questions about this Privacy Policy, contact us at support@blabberbug.app.