BreachRx is a cybersecurity incident response management platform built around privacy, legal, security, IT, and communications coordination during live incidents. The product automates tailored response plans, tracks jurisdiction-specific regulatory requirements, centralizes communications and approvals, and creates audit-ready incident records. This is one of the few vendors in this batch with clear in-house legal relevance: BreachRx explicitly markets to legal and privacy teams, its customer evidence includes outside counsel participation, and customer stories emphasize legally defensible documentation and cross-functional coordination. Founded 2018 in the United States. Public funding evidence shows a $15M Series A announced on May 19, 2025, with PitchBook indicating roughly $23.9M raised to date. LinkedIn followers ~2.6K. No public pricing found. Security posture is stronger than most batch peers: SOC 2 Type II, SSO via OIDC/SAML, audit trail support, and hosting on certified data-center infrastructure.
Company Info
- Founded: 2018
- Team size: 11-50 employees
- Funding: $7M
- HQ: United States
- Sector: Governance/Compliance/Risk Management
What We Haven’t Verified
This page was assembled from publicly available information. Feature claims and workflow mappings are based on what the vendor and third-party listings publish — not hands-on testing or practitioner feedback.
Workflows
Based on practitioner evidence, Breachrx is used in these workflows:
What practitioners struggle with
Real frustrations from legal professionals — the problems Breachrx addresses (or should address). Sourced from practitioner reviews, Reddit threads, and case studies.
A suspected data breach hits on a Friday night and suddenly legal, privacy, security, IT, comms, cyber insurance, and outside counsel are all running separate email and Slack threads — nobody has one defensible timeline of who approved what, which facts are confirmed, or whether the company is coordinating toward the same response plan before executives and regulators start asking questions.
The security team says an incident is contained, but the GC still has to answer the harder question: which state, national, contractual, and sector-specific notice clocks just started, what facts are still missing, and how do we prove later that every regulator, customer, and board-level reporting decision was made on time and with the right legal sign-off.
Where it fits in your workflow
Before Breachrx
A suspected cyber or privacy incident is detected by security, IT, or a business team and immediately triggers questions about containment, privilege, investigation scope, regulatory exposure, and stakeholder communications.
After Breachrx
After the initial triage, legal and privacy teams determine notification obligations, security and IT document containment and forensics decisions, communications teams prepare internal/external messaging, outside counsel and vendors are brought into the incident workspace, and the organization preserves a defensible record for regulators, boards, insurers, and post-incident reviews.
Integrations & hand-offs
Security tooling and ticketing systems can launch or sync incidents into BreachRx; legal/privacy then use the platform to assign tasks, manage regulatory obligations, and track approvals; downstream handoffs include outside counsel, regulators, cyber insurers, PR firms, and post-mortem governance reviews.
Community Data
Loading practitioner-sourced data…