Privacy Notice

This notice explains how BugRadar handles information when people visit the site, create an account, join a workspace, use the visual reporting tools, or contact us.

A workspace organization decides which projects, environments, members, and reporting connections it uses. Workspace owners are responsible for configuring access appropriately.

Account and workspace information can include a name, email address, authentication records, organization and project membership, roles, permissions, and preferences.

Product content can include issue text, comments, screenshots, recordings, annotations, attachments, CSS selectors and click locations, URLs, viewport and browser details, console information, activity history, and environment data submitted through the reporting workflow.

On approved websites, the embedded widget and browser extension can collect recent console errors and warnings, uncaught JavaScript errors, unhandled promise rejections, and failed page fetch or XMLHttpRequest calls after BugRadar activates. Request entries include the method, status when available, and URL origin/path; they exclude query parameters, fragments, headers, and bodies. This bounded information is attached automatically when a report is submitted if the project setting is on. BugRadar cannot read earlier console history or capture native form navigation and resource-load failures in this feature. Credential masking is best effort; messages and URL paths can still contain sensitive information. Saved diagnostics are visible to everyone who can view the task, including client members. Turning capture off stops future collection and storage, but does not delete diagnostics already saved on tasks.

Plan records include your selected plan, launch-offer claim and activation dates, and the date Pro access ends. BugRadar does not collect payment-card details for the launch offer.

We use information to authenticate users, operate workspaces and real-time boards, process reports and files, enforce permissions and plan limits, apply the launch offer, protect the service, investigate problems, and respond to inquiries.

We may also use service-level operational information to understand reliability and improve the product. We do not describe customer screenshots or issue content as public product material.

Information is shared with members and trusted reporters according to workspace configuration and permissions. Workspace-initiated webhooks or integrations may send selected event data to destinations chosen by that workspace.

When a project owner enables AI Task Assist, opening a task can send a bounded copy of its title, description, page location, browser details, selected diagnostics, and one screenshot to Groq for a suggested title, severity, optional description, and developer guidance. Suggestions are stored with the task; a person chooses whether to apply them. The project setting controls future generation and can be turned off. BugRadar does not send recordings or other attachments to this feature.

Service providers help operate BugRadar, including infrastructure, PostgreSQL database hosting, Cloudflare R2-compatible file storage, email delivery, and, for enabled projects, Groq AI processing. They process information for the services they provide. Information may also be disclosed when required by law or needed to protect rights, safety, and service integrity.

BugRadar uses tenant-scoped access controls and organization-scoped data operations to separate workspace data. Files are stored through S3-compatible object storage. Launch-offer eligibility and expiry are enforced by the server.

No system can guarantee absolute security. Account holders should protect credentials, workspace owners should review membership and roles, and reporters should avoid capturing unrelated sensitive data.

Information is retained while needed to provide the service and for legitimate operational, security, dispute, and legal purposes. Different records may require different retention periods.

Because no single public retention schedule is currently promised, contact us about a specific workspace or record type before relying on a particular deletion timeline.

You can update certain account and workspace details in the product. Workspace owners can manage members, roles, projects, environments, and organization settings. Pro launch-offer status and dates appear in Plan & usage settings.

For access, correction, deletion, or another privacy question, contact us. We may need to verify the requester and consider the workspace owner’s role, security needs, and applicable law before acting.

We may update this notice as BugRadar, its vendors, or legal requirements change. The date above identifies the latest published version.

Send privacy questions to support@bugrader.site.