Meta's Muse agent turns a shared conversation into a web page that anyone with the link can open. That part is by design. The problem is that people who were never given a link can still find it, because of how Muse names the page.
The address gives the page away
Muse builds each share's web address from the conversation's title, then a random code. A chat called "home sale budget" gets an address that starts with those words. When your colleague opens the link, their browser looks the address up, the way it does for every website. Some services that watch those lookups record them and keep them in a database that anyone can search.
So the title the user typed, and the random code that was meant to make the address impossible to guess, both land in a public list. The code only works as a secret while it stays secret. One search for Muse's content domain returned more than 6,800 shares, each named after its conversation. Most of the few hundred that were opened were harmless: small-business sites, event listings, calendars. A minority were not. They included a small-business loan application with the amount requested, a real-estate investor's income and mortgage figures, a bank fraud alert with a partial account number, and a staff vacation calendar naming dozens of employees.
Why the usual precaution misses it
After the ChatGPT and Grok cases, companies learned to tell search engines to stay away from share pages, and Muse does. That instruction only asks well-behaved crawlers not to visit. Nobody here used a search engine or guessed anything. The list of addresses already existed, and it comes with titles, so a reader can pick the interesting ones before opening a single page.
That makes the list more useful to a rival than a pile of random pages would be. A competitor who searches it for a customer's name, a product code or the word "pricing" does not have to read thousands of chats. The titles do the sorting. Even a page that is dull in itself can give away something private: a title like "call prep" with a meeting time shows who is talking to whom and when.
Only shares that someone has opened appear this way, which sounds like a comfort until you remember that opening is the whole point of sharing. Meta's help page for sharing its AI chats also describes a link that never expires and can be passed on by anyone who has it, so a share from the day Muse launched is as findable as one from today. Meta has also pushed Muse at small businesses, where one person often holds the loan paperwork, the supplier prices and the staff rota in the same chat history.
How to share without publishing
The same weakness can appear in any tool that puts a document's title into its web address, so the useful habit is not specific to Muse. A shared link is a published page with a hard-to-guess name, and a hard-to-guess name only protects it until someone looks it up.
The safer way to send someone the result of a Muse chat is to send the result: copy the answer into an email or a document, or export it, and share that through the tools your company already controls. When a link is the only practical option, give the chat a dull title such as "notes 14", and leave out anything you would not put on a notice board. Then test it. Open the link in a private browser window where you are not signed in. If the page loads, it will load for everyone who finds the address.