Privacy Policy

Last updated: May 18, 2026

What BugSnaps Collects

BugSnaps collects information only when a user manually creates a report. Reports may include the page URL, page title, screenshot, browser and device metadata, viewport size, console messages captured after extension injection, optional network request metadata, user-written descriptions, reproduction steps, project names, and account email addresses. Users can choose which report sections to include before saving or copying a report.

Anonymous Activation Analytics

BugSnaps collects limited activation analytics to understand whether users can complete the install-to-first-report flow. These analytics may include event names such as extension installed, welcome page opened, popup opened, capture clicked, sample report created, report created, Markdown copied, dashboard clicked, signup started, and signup completed. These events are stored with anonymous install and session identifiers plus a timestamp.

Activation analytics do not include page URLs, page titles, screenshots, console messages, network request details, user-written report text, project names, account email addresses, passwords, or other report contents. The admin dashboard shows aggregate counts only.

Extension Capture Controls

The browser extension provides report-section controls for screenshot, technical environment details, console messages, and network metadata. Network metadata is limited to request details such as URL, method, status, type, timing, and request errors. BugSnaps redacts sensitive URL parameters such as tokens, passwords, secrets, session values, and authorization codes where possible.

What BugSnaps Does Not Do

BugSnaps does not continuously record browsing activity, does not intentionally capture passwords, does not collect keystroke logs, mouse positions, scroll behavior, or click trails, does not sell user data, and does not use report content to train AI models. Copying a Markdown report in guest mode stays local unless the user separately shares it.

Diagnostics

BugSnaps may store app-side diagnostic logs when dashboard, browser, or API errors occur. These logs can include the signed-in user ID, request route, method, response status, error source, message, stack trace, timestamp, and limited technical metadata so the service can be debugged and hardened.

Data Sharing

Private reports require account access. Public report links are opt-in and can be revoked. Authentication is handled through Neon Auth and password login for approved accounts. Passwords are stored as salted hashes. Payment processing is handled by Stripe. Production deployments may store screenshots in private object storage and serve them through authenticated BugSnaps endpoints. BugSnaps does not sell or transfer user data for unrelated purposes.

Retention and Deletion

Users can delete reports from the dashboard. Production operators should configure backups, object-storage lifecycle rules, and account deletion workflows before public launch.

Contact

For privacy requests, contact support@bitforgellc.com.