Skip to content
Messaging Agents

What Muse does with your messages

Source: Meta's published security write-up for Muse, read 2026-10-03. Its words are quoted, never paraphrased.

Whose hands it passes through

Somebody carries the message, somebody runs the model that reads it, and where the agent uses a website on your behalf somebody operates that browser. A blank below is not an absence of a company, it is a company nobody has named.

  1. You, onWhatsApp, Web
  2. The productMeta
  3. Carries the messagesMeta
  4. Runs the modelMeta
  5. Drives the browserRuns its own
  6. Holds it, under whose lawUnited States, rolling out to people 18 and over. Meta's general company policy covers everything the Muse security write-up does not.

Every link read off the product’s own published pages. Across the 79 policies in this directory, 3 name all four, and 13 name none of them.

In its own words

“If you do not want your data to be used in model training at all, you can opt-out via a simple switch in Muse settings.”
On training, Yes, with opt-out

Quotes are verbatim. We report what the document says and link it; we do not interpret its legal effect, and policies change.

What it does not answer

Each of these is a question some policies in this directory answer. The count is how many of the 79 we have read close it.

Silence is not a denial and it is not a promise. A document that does not address the people in your group thread has not agreed to anything about them.

How old this document is

The document carries no revision date. 71 of the 79 policies here carry one and 8 do not, and without one there is no way to tell whether this describes the product as it ships today.

We have read it 2 times and it has changed once since we started watching, most recently on 2026-10-03. What changed, sentence by sentence.

Who else answers this the same way

The products that gave the same answer, each on a page like this one.

Read next