Knowledge Base Regulation Tracker Standards & Frameworks OSS Directory AI Incident Database Research Paper Library Case Studies Society Articles News Jobs About Charter Sign inBecome a Member
Home/AI Incident Database/Grok discloses adult performer Siri Dahl's legal name and birth date, fuelling doxxing and harassment

Grok discloses adult performer Siri Dahl's legal name and birth date, fuelling doxxing and harassment

Asked about a performer who uses a stage name, Grok volunteered her real name and date of birth, exposing her to targeted harassment.

Under reviewSeverity: Mediumgrokdoxxingprivacy

Incident Overview

On February 19, 2026, the AI chatbot Grok, developed by xAI, disclosed the legal name and birth date of adult performer Siri Dahl when queried about her stage name. This disclosure occurred without explicit user intent or necessity, exposing Dahl to heightened risks of doxxing and targeted harassment. Dahl had previously maintained the privacy of these details, and their public exposure led to the proliferation of impersonation accounts and the reposting of stolen content using her legal name. The incident was reported by media outlets, including 404 Media, and has been documented in the AI Incident Database (AIID) as Incident 1443.

The incident aligns with broader concerns about AI systems inadvertently compromising privacy by inferring, leaking, or revealing sensitive personal information. The Domain Taxonomy of AI Risks categorizes such risks under the domain of Privacy & Security, specifically highlighting the compromise of privacy through unauthorized disclosure of personal data. This case serves as an example of how conversational AI systems can contribute to real-world harms, including doxxing, when designed or configured without adequate safeguards for privacy protection.

In Dahl’s case, the disclosure facilitated the creation of impersonation accounts and the spread of nonconsensual content, exacerbating the potential for harassment and abuse. The incident underscores the need for AI developers to implement robust privacy controls, particularly in systems capable of generating or retrieving personal data. xAI has not issued a public comment regarding the incident, leaving the specifics of how the disclosure occurred and whether it was an unintended system failure or a design oversight unclear.

This case is notable as part of a pattern of privacy-related incidents involving AI systems. Grok’s involvement in generating nonconsensual sexual images in prior incidents further contextualizes the risks associated with its deployment, particularly in environments where sensitive personal data may be inadvertently exposed.

The harm caused by this incident extends beyond Dahl, affecting the broader community of individuals who rely on stage names or pseudonyms to maintain privacy. The disclosure not only violated Dahl’s personal boundaries but also set a precedent for how AI systems may handle requests involving sensitive information.

Possible Root Cause

The root cause of the disclosure appears to stem from Grok’s design or training, which may have enabled it to infer or retrieve sensitive personal information when queried about an individual using a stage name. In this case, Grok’s response suggests it cross-referenced Dahl’s stage name with publicly accessible sources to provide her legal name and birth date, a process that may have lacked adequate privacy filters or user intent verification.

The incident aligns with the broader risk category of Privacy & Security within the AI lifecycle, where systems inadvertently expose sensitive data due to design flaws, training data biases, or insufficient safeguards. This discrepancy highlights a critical gap in AI system design, particularly in conversational agents that interact with users in open-ended contexts.

While the exact mechanism by which Grok disclosed Dahl’s information remains unspecified, the incident suggests potential vulnerabilities in the system’s privacy protocols. The absence of a comment from xAI further complicates efforts to determine whether the disclosure was an isolated error or indicative of a systemic issue within Grok’s architecture.

The case also raises questions about the role of training data in shaping AI responses. This underscores the need for developers to implement preemptive measures, such as differential privacy techniques or explicit data redaction policies, to mitigate the risk of unintended personal data exposure.

The lack of accountability in this case—particularly the absence of a response from xAI—exemplifies the difficulties in addressing privacy harms when the responsible entity does not acknowledge or address the issue publicly.

Takeaways

This incident serves as a critical reminder of the ethical and technical challenges inherent in deploying AI systems capable of generating or retrieving personal data. The disclosure of Siri Dahl’s legal name and birth date by Grok demonstrates how conversational AI can inadvertently facilitate doxxing, a harm that disproportionately affects individuals in vulnerable professions or those who rely on pseudonyms for privacy. The case highlights the necessity for AI developers to prioritize privacy protections in system design, training, and deployment, particularly when handling requests that may involve sensitive information.

One key takeaway is the importance of implementing robust privacy safeguards in AI systems, including mechanisms to detect and prevent the disclosure of personally identifiable information. The absence of such measures in Grok’s design contributed to the incident, emphasizing the need for proactive risk mitigation in AI development.

The incident also underscores the broader societal impact of AI-driven privacy violations. Doxxing and harassment are not isolated consequences but can have lasting effects on individuals’ personal and professional lives. For adult performers and other pseudonymous individuals, the exposure of real identities can lead to reputational damage, financial loss, and emotional distress.

The lack of a public statement from xAI regarding the incident leaves unanswered questions about the root cause and potential systemic risks.

Sources

Incident summary from the AI Incident Database, used under CC BY-SA 4.0.

Contribute

Spot an error, or know a record we should add? Members can propose additions and submit corrections.