If you have shared a Meta Muse conversation by link, assume that anyone with the link could read it, and possibly people searching for it too. Check every link you have created, delete the ones you no longer need, and keep sensitive material out of anything you share in future.
What you need before you start
The Verge reports that Meta has turned Muse sharing back on. Sharing had been paused after researchers at Claroc found that public conversation links could be easy to discover. According to the report, the researchers came across Muse pages including a marketing company’s internal revenue review and a small business owner’s loan application. The source does not say what Meta changed before turning sharing back on, how many pages could be found, or whether links created before the pause behave any differently now. Plan on the basis that older links may still be reachable.
Before you begin, make sure you have:
- Access to the account you use with Muse, on the web and on any app where you are signed in.
- A list, even a rough one, of the people or channels where you have posted Muse links: email threads, team chat, documents, social posts.
- Twenty to thirty minutes without interruptions, because the review is only useful if you finish it.
- If you work for an organisation, the name of whoever handles data protection or IT security, in case you find something that should be reported.
List every conversation you have shared
Start with an inventory. Open Muse and look for a part of the settings, history or account area that lists shared links or public conversations. Many AI chat products keep such a list. Menus change, though, and this guide cannot confirm exactly where Muse puts it. If you cannot find a central list, go through your conversation history and look for any conversation marked as shared or public.
Then search your own outgoing messages. Look through sent email, chat history and shared documents for links that point to Muse pages. Write each one down along with what it contains and who it was meant for. This second search often turns up links you have forgotten, particularly ones pasted into a group conversation months ago.
Check whether a link can be found publicly
For each link, decide whether it is only reachable by people who were sent it or whether it can be found some other way. Open it in a private browsing window while signed out. If the full conversation loads, then anyone holding the URL can read it.
Next, try a search engine. Put a distinctive phrase from the conversation in quotation marks, or use the search engine’s site-restriction operator together with the domain shown in the link. If your conversation appears, it has been indexed. Search results can take time to update, so a link that does not show up today may still have been visible earlier. Keep in mind that the researchers’ findings, as reported, were about how easy the pages were to find, and that does not depend only on search engines.
Delete or revoke links you no longer need
For any link that has served its purpose, use whatever option Muse offers to stop sharing, unshare, or delete the conversation. Turning off sharing usually makes the public page unavailable while you keep the conversation. Deleting removes the conversation completely. Choose deletion when you have no need to keep the content.
Once you have removed a link, open it again in a private window to check that it no longer loads. If an indexed copy still appears in search results, most major search engines provide a way to request removal of outdated content once the original page has gone. Removal from search results does not reach copies someone else has already saved, screenshotted or forwarded.
Remove sensitive details before sharing again
If you still need to share a conversation, make a clean version first. Start a fresh conversation without names, account numbers, financial figures, client details, health information or anything else you would not put on a public noticeboard. Use placeholders such as “Client A” or “Q3 figure” in place of real values. The material the researchers reportedly found, an internal revenue review and a loan application, is exactly the kind of content that should never end up in a shareable chat.
Read the whole conversation before you create a link, including the model’s replies. AI responses often repeat details from your prompt, so removing them from your own messages alone does not remove them from the page.
Use a safer channel for confidential material
When the content is confidential, do not use a public link. Copy the parts you need into a document stored in a system that controls access by named account, such as your organisation’s file storage. Then share it with specific people, not with “anyone with the link”. This lets you see who has access and remove it later.
For work material, check whether your employer allows staff to put company data into consumer AI tools in the first place. Many organisations have rules about this, and a sharing setting cannot make up for content that should not have been entered.
Mistakes people actually make
- Treating a long, random-looking URL as private. An unguessable link is not access control. Once it is forwarded, posted or indexed, it is public in practice.
- Assuming a pause fixed old links. Sharing being switched off and back on tells you nothing about what happened to pages created earlier. Check them yourself.
- Reviewing only one device. Conversations started on a phone may not be the ones you remember from the web, so check both.
- Forgetting that the AI repeats your data. People scrub their own prompts and leave the same details sitting in the model’s answer.
- Sharing a whole conversation to show one answer. Usually a short excerpt, pasted as text, is all the recipient needs.
- Not telling anyone. If a client’s or employer’s data was exposed, keeping quiet can turn a minor slip into a reportable incident.
When this approach is the wrong choice
This audit is for individuals and small teams cleaning up their own links. It is not enough if you think someone else’s personal data, such as a customer’s or an employee’s, was in a public conversation that may have been read. In that case, involve your organisation’s data protection lead, because legal duties to assess and possibly report a breach may apply.
It is also the wrong tool if your organisation needs ongoing control. Checking links by hand does not scale across many staff, and a workplace AI service with central administration and sharing restrictions would be a better fit. Finally, if you cannot find any way in Muse to list or revoke shared links, deleting the affected conversations and contacting Meta’s support channels may be the only reliable option.
Frequently asked questions
Is Meta Muse sharing safe to use now?
The Verge reports that Meta has turned Muse sharing back on after researchers raised concerns that public conversation links were easy to find. What Meta changed, if anything, before re-enabling the feature is not known from that report. The safest approach is to treat any shared link as readable by anyone who obtains it and to share only content you would be comfortable making public.
How do I find out if my AI chat link is public?
Open the link in a private browsing window while signed out. If the conversation loads, anyone with the URL can view it. Then search for a distinctive phrase from the conversation in quotation marks to see whether a search engine has indexed it. Repeat the check after a few days, because search results do not always update at once.
Does deleting a shared conversation remove it from Google?
Deleting the conversation or turning off sharing should make the original page unavailable. Search engines may still show a cached or listed copy for a while. Most major search engines let you request removal of outdated content once the source page has gone. Neither step affects copies or screenshots that other people have already saved.
What should I do if I shared confidential work data through an AI chat?
Revoke or delete the link straight away and check that it no longer loads. Then tell your manager or your organisation’s data protection or IT security contact, explaining what was shared and for roughly how long. They can judge whether the exposure needs further action, including any reporting obligations that may apply to personal or client data.
Sources and further reading
- The Verge: reporting on Meta re-enabling Muse sharing and on the researchers’ findings.
- Claroc: the security researchers credited with finding that Muse public conversation links were easy to discover.
- Search engine help centres: published guidance on removing outdated content from search results.
- National data protection regulators: general guidance on handling and reporting personal data breaches.
Surfaced from the rss:verge signal “AI chat sharing restored”. AI-assisted draft, editorially reviewed.
