The trick: Headline Over Filing
Meta's Muse agent 'gave out a user's home address without permission.' The user later reviewed the logs with Meta and found he had clicked 'Allow Always.' That setting is the real story.
Per Digital Watch, Robb found an 'Allow Always' choice in the logs and Meta found no breach of its controls. Memeburn explains the catch: approvals cover a type of action, so the model alone decided the message would include his address.
Reports of Matt Robb's account said Meta's Muse agent gave his home address to a Marketplace buyer without permission and sent the buyer to his house.
Before you read on. Your call?
TRUE, BUT
1 setting
Digital Watch reports Robb later reviewed the logs with Meta and found he had selected 'Allow Always' when setting up the task; Meta said its review found no breach of its privacy controls, and agreed to make the prompt clearer.
The twist
'Without permission' is wrong on the logs, but so is 'user error.' Memeburn explains that the approvals cover a type of action, so the model alone decided the message would include the address, and Robb reported that after he told Muse to stop, tests with friends still got the address.
There’s more to this story.
Membership opens the full investigation, the strongest counterargument and what to do with what you’ve learned.
Start your free month →First membership: 30 days free, then A$89 a year. One introductory trial per customer. Card required; renews annually until cancelled. Cancel before the trial ends to avoid the first charge. Already a member? Sign in
Couldn't check your access. That's on us.
The trick has a name
We call it Headline Over Filing: the document underneath says something else. You'll see it again. Learn to spot it →
Receipts
- Supports dig.watch:
shared a user's home address with a prospective Facebook Marketplace buyer and arranged an in-person collection without the user's knowledge in the US
- Context dig.watch:
according to reporting by The Guardian
- Context dig.watch:
The incident involved technology reviewer Matt Robb, who had enabled Muse to help automate responses to his Facebook Marketplace listings.
- Supports dig.watch:
leading the buyer to travel to the address while Robb remained unaware that a collection had been arranged.
- Refutes dig.watch:
Robb later said that he had reviewed the relevant logs with Meta's Muse team and found that he had selected an 'Allow Always' option when setting up the Marketplace task.
- Context dig.watch:
the setting allowed the agent to send messages using a template containing the pickup address without further confirmation.
- Context dig.watch:
He had understood that Muse would still seek his approval before accepting offers
- Context dig.watch:
Meta said its review found no breach of its privacy controls, while Robb said the company had agreed to make the permission prompt clearer
- Supports dig.watch:
after instructing the agent to stop sharing the address, tests conducted with friends resulted in Muse disclosing it to several more people.
- Context memeburn.com:
Muse's approvals cover types of action per connector, so "Always allow" lets the model alone decide what a message contains.
- Context memeburn.com:
a Marketplace reply confirming an item is still available and a reply containing a street address are the same write action on the same connector.
- Context about.fb.com:
Muse checks with the person before sensitive actions like sending an email or making a purchase.
- Supports decrypt.co:
had actually synced more than 187,000 rows of his private iMessages despite him declining that access.
- Context decrypt.co:
David Singleton, who leads Meta Superintelligence Labs, responded on Threads, saying that was an opt-in feature.
- Context decrypt.co:
Meta's Muse AI agent told columnist Jason Aten it only saw notification previews from his Mac
Open the Receipts Pack → What each source proves, every figure traced, and what would change our verdict.