OpenAI chief issues formal apology over failure to report mass shooter to Canadian authorities
The technology firm admits its internal safety thresholds failed to trigger a mandatory referral to the Royal Canadian Mounted Police despite prior flags for violent activity
OpenAI chief executive Sam Altman has issued a formal public apology following the company's failure to alert Canadian law enforcement regarding a user flagged for interests in violent activities prior to a mass shooting in Tumbler Ridge, British Columbia. The tragedy, which occurred on 10 February 2026, resulted in the deaths of eight people, including family members and school staff, before the shooter took her own life.
In a letter posted on the social media of British Columbia Premier David Eby and the local news website Tumbler RidgeLines on 25 April 2026, Altman expressed his deepest condolences and stated that while words may never be enough, an apology was necessary to recognise the harm and irreversible loss suffered by the community. The correspondence confirms that Altman had spoken with Tumbler Ridge Mayor Darryl Krakowka and Premier Eby, who conveyed the community's anger, sadness, and concern regarding the incident.
It was agreed that a public apology was warranted, but time was needed for the community to grieve before the statement was released. The letter details that OpenAI had banned the account of Jesse Van Rootselaar in June 2026 after flagging her activity for the furtherance of violent actions. However, the company determined at that time that the specific activity did not meet the threshold for referral to the Royal Canadian Mounted Police.
British Columbia Premier David Eby described the apology as necessary, and yet grossly insufficient for the devastation done to the families of Tumbler Ridge. This assessment highlights the ongoing tension between corporate safety protocols and the imperative for immediate law enforcement notification in cases involving potential mass violence.
Altman reaffirmed OpenAI's commitment to working with all levels of government to prevent similar tragedies in the future. He noted that the community's reaction had conveyed a deep sense of anger and sadness, reinforcing the need for the company to find ways to prevent similar tragedies going forward. The statement underscores a critical review of the firm's safety protocols and their assessment of potential threats.
The incident serves as a stark reminder of the complexities involved in balancing user privacy with public safety obligations. While the company acted to ban the account for violating usage policies, the decision not to escalate the matter to police remains a focal point of the inquiry into how such events are managed by private technology entities.
