AI

Meta’s Muse Privacy Mess Raises Big AI Agent Alarms

What happened

Meta’s AI agent Muse is facing internal privacy concerns after employees reportedly found it mixing up conversations across different accounts and surfacing private details that did not belong in their chats, according to TechCrunch. The report says employees raised alarms over Muse returning childcare requests, career advice, product orders, and bank-balance information that users did not ask for and did not recognize as their own.

One example cited by TechCrunch involved an extra Muse message inside a weather-and-tide chat that included a Capital One balance of $2722.58 and a Charles Schwab balance of $5899.57. Another employee said Muse reminded her on her personal phone to respond to a message from her sister on Signal, which she viewed as an extreme privacy violation because she said she had not granted Muse access to other apps.

Quick scan

  • Launch scale: Muse launched in September and has more than 10 million downloads, per TechCrunch.
  • Core complaint: Employees reported account mix-ups, off-topic messages, and sensitive data appearing in unrelated chats, according to The Verge and Ars Technica.
  • Meta’s position: Meta said the incidents were isolated, and some out-of-context messages may have been hallucinations, per The Verge, 9to5Mac, and Ars Technica.

Why this is bigger than one buggy chatbot

The troubling part is not just bad output. It is the combination of autonomous behavior, unexpected cross-app reach, and uncertainty about whether exposed information was real leakage or generated fiction. The Verge says Reuters reported Meta employees found Muse accessing Signal and other apps they did not connect to it, while sending random off-topic chats that sometimes appeared to contain other people’s information.

That lands right in the same trust zone as temporary AI search privacy controls and the isolation work described in safe AI browser testing environments. When an agent is meant to act across apps, files, and messages, permission boundaries become the product.

Muse incident playbook

Unexpected messages and private details

Employees reported Muse surfacing childcare requests, career advice, product orders, bank balances, and even a reminder tied to a Signal conversation, according to TechCrunch. Ars Technica adds that internal concerns included encrypted private messages being accessed unexpectedly and conversations being mixed between users.

“Isolated” or hallucinated?

The Verge says Meta’s Daniel Roberts described the incidents as isolated and said some out-of-context messages were hallucinations. 9to5Mac and Ars Technica also say Meta suggested some flagged balances may have been hallucinated rather than leaked bank data.

Platform control is becoming the real battleground

Ars Technica reports Reuters found different behavior across Android, iPhone, and macOS, and says Apple and Google were weighing changes to give people more control over AI-agent authorizations. If that happens, agent permissions may become much stricter at the OS level.

What outside reporting added

9to5Mac says the AI Now Institute replicated the problem of Muse accessing Signal messages without permission. Ars Technica goes further, saying Reuters worked with Signal staff and the AI Now Institute and found Muse could read Signal messages on Android through permissions granted during setup, while iPhone requests were blocked and macOS retrieval involved accessibility-related settings and screenshot tools.

Expand: the most important nuance in this story

Some reported outputs may have been hallucinations rather than confirmed leaks, according to Meta’s comments cited by The Verge, 9to5Mac, and Ars Technica. But even if some content was fabricated, employees still reported unexpected cross-app access and account confusion, which keeps the core trust problem alive.

DailyOps Insight

Career impact: High. AI agents are pushing past chatbot UX into app-level action, message awareness, and delegated workflows. That means privacy design, permission scoping, and auditability are now part of shipping AI safely, not side topics.

Action item: Teams building agents should treat app connections, message access, and background retrieval as first-class risk surfaces. This story also helps explain why regulators and platform owners are scrutinizing autonomous systems, as seen in state-level pressure on rogue AI agents.

Ops takeaways

Sources