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, selected page elements, URLs, viewport and browser details, console information, activity history, and environment data submitted through the reporting workflow.

Billing records can include plan, subscription, invoice, and Stripe customer or subscription identifiers. Payment-card details are entered with Stripe rather than stored directly in BugRadar’s application database.

We use information to authenticate users, operate workspaces and real-time boards, process reports and files, enforce permissions and plan limits, support billing, 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.

Service providers help operate BugRadar, including infrastructure, PostgreSQL database hosting, Cloudflare R2-compatible file storage, Stripe billing, and email delivery. 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, and billing updates are accepted through signed Stripe webhook processing.

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, billing, 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. Billing changes are handled through the available checkout or billing portal flows.

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 sales@bugradar.io.