Deep dive 4 of 5 · Privacy & safety
Muse privacy settings: the 5-minute setup that matters
Muse connects to your mail, your files, your spending and your health. These are the settings to change before your first real prompt — plus the launch-week security reports you should know about. Last verified: 3 November 2026.
In short
- Do this first: Setup → Data Controls → toggle off “Help us improve our models”. That stops your prompts training Meta’s models.
- Second: disconnect sources you do not need. A privacy setting cannot protect a connector you granted on day one.
- Your conversations are not shared with ad systems per Meta — but everything you connect to is still readable by the agent.
- Memory and training are separate: what your Muse remembers vs what Meta's models learn. The full explainer is how Muse learns about you.
- Deleting is not one button: delete a message, delete a side chat, or Reset Muse in Data Controls — and Reset is the only true wipe. There is no standalone “delete my Muse account.”
- Launch week brought three real security stories: a macOS zero-day, a ClickFix hijack, and a misfired Messages send. All three have practical mitigations below.
- Verify after changing anything — restart the app and re-open Settings.
The five settings, in order
- 1Setup → Data Controls → “Help us improve our models” → OFF. The single highest-value toggle on the device. This is what stops your prompts becoming training data.
- 2Settings → Connectors → disconnect what you are not using. Fewer connections, smaller blast radius. Add back only when a task demands it.
- 3Settings → Permissions → every write action to “allow once”. Covered properly in the permissions guide.
- 4Check how payments are stored. Meta has said card numbers can be held as one-time tokens via Link, and that a credential store (1Password-style) is coming. Prefer tokenised cards; never paste a full PAN into a chat.
- 5Read the audit trail once. Settings → Permissions → history. You want to see what you expected to see before anything else is connected.
Paste into Muse after setup
Before we start: list every setting and connected source you can currently reach, quote my Data Controls status back to me, and do not touch anything until I confirm.
What Meta says vs what to assume
Stated by Meta
- Conversations are not shared with advertising systems.
- Permissions are under user control.
- Card data can be tokenised via Link; a credential store is planned.
- Model-training opt-out is available in Data Controls.
Practically, still assume
- Anything in a prompt exists in a system you do not control.
- Connected sources are readable in full, not “just enough”.
- Settings move — re-verify after app updates, not once and never again.
- An independent audit beats a privacy policy. Open the trail yourself.
The gap between those two columns is your working risk tolerance. Close it with fewer connections and tighter approvals, not with optimism.
Launch-week security reports you should know
Three stories broke around the September 2026 launch. None of them mean “don’t use it” — all three mean “update and don’t click”. Dates are as reported; re-check current status before acting.
1 · macOS zero-day
Security researcher Patrick Wardle (Objective-See) reported a zero-day in the launch-day Mac app. Do this: keep the Mac client updated, install from the official source only, and if you do not need the desktop app, use the iOS or web client until you have confirmed a patch. A local privilege escalation matters most on a machine with other sensitive work on it.
2 · The ClickFix hijack
A social-engineering campaign imitated Muse to get victims to paste a command into their own terminal — the “ClickFix” pattern. Do this: never run instructions that arrived in a DM, ad, or “Muse support” message. Muse does not ask you to open Terminal. Type Cmd+Q and close anything that asks.
3 · The Messages dispute
A widely shared report on September 30 described Muse acting on an old Messages instruction and contacting a contact unexpectedly. Do this: keep Messages and any sending connector on “allow once”, and inspect the audit trail after any task that touches your inbox or message history. Treat it as the concrete argument for the permissions page.
All three are launch-week reports as of September 30, 2026. Product and patch status change quickly — verify against official advisories before you rely on a detail here.
Handling something sensitive: email, money, health
Email & files
Connect read-only. Draft, never send. Scope the query — “last 20 unread” beats “summarise my whole inbox”. Start with Gmail setup.
Money
Never type a full card number into a chat. Use a tokenised card or a one-time number where offered, and keep purchase approval on “allow once”. See bank connection.
Health
Health connectors are the most sensitive grant on the list. Connect one service, read-only, and check the trail before connecting a second. Start from the connector list.
The pattern is identical across all three: read-only, scoped, approved, audited. If you cannot say what would happen if the agent misunderstood, you are not ready to connect it.
For businesses: privacy defaults per account
Individual opt-outs do not compose into an organisation policy. Before rollout:
- Set training opt-out on every account, then verify by opening Settings on a second machine — defaults reset with some updates.
- Decide which data classes may never enter a prompt: credentials, customer PII, health data, account numbers.
- One connector per team member to start, read-only, written into the permissions policy.
- Name the person who reads the audit trail weekly. Not a shared inbox — a person.
- Include Muse in offboarding: connectors revoked the day a role changes.
We set these defaults with you in one session — request a session.
Delete my data / delete my account
There is no single “delete my Muse account” button. Meta gives you three levels, and they do very different things. Pick the level that matches what you actually want — and read the warning at the bottom before touching Reset.
- 1Delete one thing. To delete a message: tap and hold it, tap Delete, confirm. To delete a side chat: in the Chats tab, tap the three-dot menu on the chat, tap Delete, confirm. To edit or delete what Muse remembers about you: Assistant icon → Identity → Memory, and edit the file directly. Identity works the same way: Assistant icon → Identity → Edit.
- 2Reset Muse — the true wipe. Settings → Data Controls → Reset (labelled “Reset Muse”), then follow the on-screen instructions and tap Reset to confirm. This returns Muse to its original state and permanently deletes all information: chat history, files, and active tasks. It cannot be undone. Before you do it, download a copy of your data first: Settings → Data Controls → download your Muse information. And cancel any paid subscription separately — resetting does not cancel billing.
- 3Delete your Meta account — the only way to remove Muse completely. There is no way to delete Muse on its own. Deleting your Meta account in Accounts Center deletes all information associated with the account, including Muse — and Facebook and Instagram along with it. Export first: Accounts Center → Your information and permissions → Export your information.
The honest caveat, in Meta's own words: “After you delete something, Muse may still remember information it learned from what you deleted.” Deleting removes the record; it does not guarantee Muse forgets what it learned. Reset is the strongest option Meta offers, and even it cannot reach models already trained on your data. If that matters to you, turn off “Help us improve our models” in Data Controls first — that toggle covers past chats too — and only then delete.
Deleting the app from your phone does none of this. Your Muse data lives in its cloud virtual machine, not on your phone — uninstalling leaves everything intact. Reset in Data Controls is the only action that permanently deletes it.
Privacy settings: questions
- How do I stop Meta using my Muse prompts for training?
- Setup → Data Controls → toggle off “Help us improve our models”. Restart the app and reopen Settings to confirm it stuck — some updates reset privacy defaults.
- Are my Muse conversations used for ads?
- Meta states conversations are not shared with advertising systems. That is separate from training and from what connected sources can read — handle all three independently.
- Is there a macOS security issue with Muse?
- A zero-day in the launch-day Mac app was reported by Objective-See around September 24, 2026. Keep the desktop client updated, install only from the official source, and consider the iOS or web client until you confirm a patch.
- What is the ClickFix Muse attack?
- A social-engineering campaign that impersonates Muse support to get you to paste a command into your own terminal. Muse never asks you to open Terminal. If a message does, close it.
- Should I put my card in Muse?
- Never paste a full card number into a chat. Use a tokenised card or a one-time number where the app offers one, and keep purchase approvals on “allow once”.
- How do I see what Muse did with my data?
- Settings → Permissions shows connections plus the activity trail. Review it after any task that touched your inbox, files, spending, or health data.