Internal reports
Meta employees have expressed concern that Muse, the company's AI agent, allegedly mixes conversations belonging to different accounts, exposing users' private data. The account comes from Reuters, which examined posts published on the company's internal channels, and is echoed by TechCrunch.
In the cases cited by employees, Muse allegedly surfaced support requests concerning children that had never been made, career advice that had never been requested, product orders that had never been placed, and bank account balances that could not be linked to the individuals concerned. These are internal reports reported by the press, not independent verification or confirmation by the company.
Two cited incidents
One employee reportedly told colleagues that Muse had inserted an unsolicited message into a conversation about weather and tides, abruptly adding two banking updates with balances from Capital One and Charles Schwab accounts. In another case, an employee who was using the agent on her personal phone reportedly received a reminder to reply to a message from her sister on Signal, the end-to-end encrypted messaging app.
The employee reportedly described the incident as a serious privacy breach, saying she had never authorized access to other applications and did not remember being asked about it. This, too, is a reported account, not a technical finding.
Why it matters and what is missing
The case carries weight for two reasons that emerge from the material. The first is its reach: launched in September, Muse is described as one of the fastest-growing apps ever recorded, with more than 10 million downloads. The second is the nature of the data involved: not simple preferences, but private conversations, orders and financial information—categories in which an error in attributing data across accounts has concrete consequences.
Meta did not immediately respond to TechCrunch's request for comment. The central questions therefore remain open: whether and how the problem was reproduced, how many users or accounts were affected, what measures were taken, and whether the company confirms or disputes Reuters' account. The available material does not make it possible to establish the technical cause of the alleged mixing or to assess the effectiveness of any corrections.
The news should be read as an internal report reported by the press, not as a proven breach. Its editorial significance lies in the fact that it concerns a very widespread product and sensitive data, but the conclusions remain subject to company confirmation or independent verification.
