Privacy Policy & Data Security
Last Updated: September 8, 2026 • Version: 1.0.0 • Scope: RecBug Chrome Extension & Backend Services
Core Privacy Commitments
RecBug is designed as a developer and QA tool with strict data minimization principles. We explicitly state our adherence to the following commitments across all extension and backend operations:
Developer Data Protection & User Trust Disclosure:
- RecBug collects user-initiated screen recordings, console logs, and network telemetry strictly for bug reporting.
- Video recordings and annotations are transmitted to RecBug servers (api.recbug.com) for video transcoding/trimming.
- Data is never sold to third parties or data brokers.
- Data is not used for advertising, marketing, or creditworthiness evaluation.
1. Data We Collect & Single Purpose Limitation
RecBug operates exclusively upon explicit user command. The extension never runs in the background silently or monitors your browsing habits outside an active recording session.
RecBug collects user-initiated screen recordings, console logs, and network telemetry strictly for bug reporting. When a user initiates a recording, the following data points may be captured:
- Screen & Audio Video: Video recording of the selected browser tab and optional microphone narration audio provided by the user.
- Console Logs: Browser runtime logs (
console.error,console.warn,console.info) and uncaught exception stack traces to help engineering teams diagnose software defects. - Network Telemetry: HTTP request metadata (URLs, HTTP methods, HTTP response status codes, latency, and sanitized request/response payloads) occurring during reproduction.
- User Actions & Environment Context: Non-sensitive user interaction coordinates (clicks, navigation changes, window viewport dimensions, and page URL).
2. Server-Side Video Transcoding & Ephemeral Processing
To ensure wide compatibility with modern issue trackers (ClickUp, Jira, Linear, Slack, Teams) and provide pixel-accurate trimming:
Our server-side media processing pipeline follows strict ephemeral data handling principles:
- Encrypted Transmission: Video chunks and annotation coordinate JSON are transmitted exclusively via TLS 1.3 encrypted HTTPS channels to
https://api.recbug.com/api/v1/video/process. - Transient Execution: The server decodes the WebM video stream, applies accurate keyframe trimming, burns in visual annotation overlays (arrows, rectangles, step numbers), and encodes the stream into an optimized MP4 container.
- Immediate Deletion: Temporary input and output files are deleted from server storage immediately upon delivering the encoded MP4 file back to your extension client.
- Zero Permanent Storage: RecBug does not retain, archive, or back up your recorded videos on our servers.
3. Data Sale, Advertising & Marketing Prohibitions
In strict compliance with Google Chrome Web Store Developer Program Policies and international privacy regulations (GDPR / CCPA):
4. Chrome Extension Permissions Justification
In adherence to the Chrome Web Store Minimum Permissions Policy, RecBug requests only the permissions necessary to record software defects and deliver bug reports:
Captures high-definition tab video and microphone narration strictly when the user explicitly clicks 'Start Recording'.
Monitors active tab navigation to associate console errors, page title, and viewport dimensions with specific URLs during recording.
Persists user preferences, destination OAuth tokens, and temporary recording chunks in local browser IndexedDB.
Injects content scripts to capture runtime console logs, network errors, and user interactions on the page being actively tested.
Authenticates users with third-party bug trackers (ClickUp, Jira, Linear, Slack, Microsoft Teams) via standard OAuth 2.0 web flows.
Schedules periodic background cache cleanup and ensures recording stream health.
Sends recorded video and annotation metadata to RecBug's backend for server-side trimming and MP4 encoding.
Allows direct client-to-API requests from your browser to your authorized issue tracker destinations.
5. Destination Credentials & Direct Dispatch
When you integrate with external platforms like ClickUp, Jira, Linear, Slack, or Microsoft Teams:
- Your authorization tokens and OAuth sessions are stored securely in local extension storage (
chrome.storage.local). - When you submit a bug report, the final payload and attachments are dispatched directly to the public REST API of your authorized provider (e.g.
https://api.clickup.com,https://api.linear.app). - OAuth token exchanges are routed through RecBug's authentication proxy (
api.recbug.com/auth/oauth/exchange) without storing or harvesting user passwords or workspace credentials.
6. User Controls, Data Retention & Erasure
You maintain full sovereignty over your data at all times:
- Granular Toggles: In the extension's Settings drawer, you can independently disable console logging, network interception, or user click tracking at any time.
- Instant Review & Edit: You can review, trim, redact, or discard any video recording and its associated logs before any data leaves your browser.
- Local Purge: Clicking "Clear All Data" in the extension settings wipes all stored session recordings, cached media, and credentials immediately.
- Uninstall Erasure: Removing the extension from Chrome automatically deletes all local storage and IndexedDB entries associated with RecBug.
7. Security Disclosures & Contact
If you have questions regarding this Privacy Policy, wish to inquire about security practices, or report an issue, please contact our team:
RecBug QA & Bug Reporter
Security & Privacy Inquiries
support@recbug.com