Muse Privacy Policy

Meta Muse · agreement dated September 17, 2026 · Official agreement

Read the agreement

25 of 25 cards

Legal Rights & Agreement Rules · Context

This version of the Muse Privacy Policy took effect September 17, 2026

The policy states that it is effective September 17, 2026.

Supporting quotations

Effective September 17, 2026

Legal Rights & Agreement Rules · Context

The Meta Privacy Policy also applies to Muse, and the Muse policy controls if they conflict

The Meta Privacy Policy applies to all Meta Products, Muse included. The Muse Privacy Policy adds details specific to Muse and explains when data use is more limited than the Meta Privacy Policy describes. If the two policies conflict, the Muse policy takes precedence.

Supporting quotations

The Meta Privacy Policy applies to all Meta Products, including Muse.
This Muse Privacy Policy adds details specific to Muse and explains when data use is more limited than the Meta Privacy Policy describes. If the two policies conflict, this Policy takes precedence.

Qualifications & exceptions

  • Precedence applies only where the two policies conflict.

Not stated here

  • The Meta Privacy Policy is linked but its text is not part of this document, so which of its terms the Muse policy narrows or overrides is not shown here.

Security & Safeguards · Company practice

Muse keeps what you share and create in a cloud virtual machine that is isolated per user

Muse runs in a cloud environment called a virtual machine (VM). This is where Muse keeps information you share and things you create together. The policy says every Muse user's VM is isolated so that no one else's agent can access it.

Supporting quotations

Muse runs on an environment in the cloud called a virtual machine ("VM"). This is the core environment where Muse keeps information you share and things you create together.
Every Muse user's VM is isolated so no one else's agent can access it.

Qualifications & exceptions

  • The stated isolation is from other users' agents.

Not stated here

  • This passage does not say whether anyone other than agents, such as company personnel or service providers, can access a VM.

Linking & Identification · User right or choice

A separate account keeps Muse data from other Meta Products; a shared Accounts Center may combine it

You can use Muse with a separate account or with an account in the same Accounts Center as your other Meta accounts. If you keep accounts separate, Muse won't share your Muse interactions or data on your VM with other Meta Products. If you instead add Muse to the same Accounts Center as other Products, the company says it may combine and use your information across profiles and devices in that Accounts Center, except in circumstances where this policy says data will not be used.

Supporting quotations

You can choose whether to use Muse with a separate account, or with an account in the same Accounts Center as your other Meta accounts. If you keep accounts separate, Muse won't share your Muse interactions or data on your VM with other Meta Products.
Except in circumstances where this Privacy Policy says data will not be used, if you add Muse to the same Accounts Center as other Products, we may combine and use your information across profiles and devices in that Accounts Center.

Qualifications & exceptions

  • Combining in a shared Accounts Center is something the company "may" do, not a stated certainty.
  • Exception: circumstances where this policy says data will not be used.

Not stated here

  • This passage does not list every circumstance in which the policy says data will not be used in a shared Accounts Center.

Cross-references

Also annotated in the same passage (2)

Security & Safeguards · Context

A Muse Confidential VM, meant to keep information private even from Meta, is described as a future option

The policy says that in the future Muse users will also have the choice to use a Muse Confidential VM, an environment the company is designing to keep people's information private, even from Meta.

Supporting quotations

In the future, Muse users will also have the choice to use a Muse Confidential VM: an environment we're designing to keep people's information private, even from Meta.

Qualifications & exceptions

  • Future option, described as being designed, not as currently available.

Not stated here

  • No date, terms or limits for the Confidential VM are given, and the policy does not say whether a standard VM is private from Meta.
Also annotated in the same passage (2)

Sharing & Disclosure · Company commitment

Muse says it does not share your conversations or VM data with Meta ad systems, even in a shared Accounts Center

Muse doesn't share your conversations or the data in your virtual machine with Meta ad systems. The policy says this applies even if your Accounts Center includes other Meta Products.

Supporting quotations

Muse doesn't share your conversations or the data in your virtual machine with Meta ad systems. This applies even if your Accounts Center includes other Meta Products.

Qualifications & exceptions

  • Covers conversations and data in your VM.

Not stated here

  • This passage does not say how other information collected through Muse, such as activity and metadata, is treated for ads, and the Meta Privacy Policy is not supplied.

Cross-references

Use & Processing · User right or choice

You choose whether your Muse interactions train Meta's AI, and the setting is on when you first use Muse

You decide whether the company can use your interactions with Muse to train and improve its AI models. The setting is on when you first use Muse, and you can change it at any time with the toggle in Settings under "Data controls." When the setting is off, your interactions with Muse will not be used to develop and improve AI at Meta, and the policy says changes to the setting also apply to previous interactions. Elsewhere the policy describes "interactions" as your messages and instructions, Muse's responses and information from services, including Connectors, used to perform tasks; this can include text, voice, photos, things you create together and information about you or others.

Supporting quotations

You decide whether we can use your interactions with Muse to train and improve our AI models. This setting is on when you first use Muse.
When the setting is off, your interactions with Muse will not be used to develop and improve AI at Meta. Changes to this setting also apply to previous interactions.
Your messages and instructions, Muse's responses, and information from services including Connectors used to perform tasks for you. This can include text, voice, photos, things you create together and information about you or others.

Qualifications & exceptions

  • Default is on at first use.
  • When off, the stated limit is on developing and improving AI at Meta.
  • The policy says changes also apply to previous interactions.

Not stated here

  • The passage does not say whether AI models already trained on earlier interactions are changed when you turn the setting off.
  • The linked "AI at Meta" page is not supplied here, so what developing and improving AI at Meta covers is not shown.

Cross-references

Also annotated in the same passage (1)

Use & Processing · Company practice

If you allow training, certain personal identifiers are removed and interactions are disassociated from your account

Allowing the company to use your interactions in training is said to help it make smarter, more capable models. If you allow this, the policy says it still removes certain categories of personally identifiable information, like names, email addresses, phone numbers and Social Security Numbers, and disassociates the interactions from your account.

Supporting quotations

Allowing us to use your interactions in training helps us make smarter, more capable models.
If you do allow this, we still remove certain categories of personally identifiable information like names, email addresses, phone numbers and Social Security Numbers. We also disassociate the interactions from your account.

Qualifications & exceptions

  • Applies if you allow training use.
  • Only "certain categories" of personally identifiable information are described as removed; the examples are introduced with "like".

Not stated here

  • The full list of categories removed is not given.
  • How interactions are disassociated from your account, and how reliably, is not described.

Use & Processing · User right or choice

Information from services Muse uses for your tasks is covered by the same training toggle

Your interactions with Muse can also include information from services Muse uses to perform tasks for you, including Connectors. The same Settings toggle controls whether that information can be used to improve AI at Meta.

Supporting quotations

Your interactions with Muse can also include information from services Muse uses to perform tasks for you, including Connectors (explained below). The same toggle in your Settings controls whether that information can be used to improve AI at Meta.

Qualifications & exceptions

  • Covers information from services Muse uses for tasks, including Connectors.

Cross-references

Linking & Identification · User right or choice

Connecting Muse to apps and services is optional and gives Muse new abilities

You can choose to connect Muse to apps and services provided by Meta or third parties, which the policy calls Connectors. When you set up a Connector, Muse gets new abilities, such as seeing your calendar or writing an email.

Supporting quotations

You can choose to connect Muse to apps and services provided by Meta or third-parties. We call these Connectors. When you set up a Connector, Muse gets new abilities, like the ability to see your calendar or write an email.

Qualifications & exceptions

  • Connectors can be provided by Meta or by third parties.

Use & Processing · User right or choice

Muse by default asks your approval before many important actions, and you can change when it asks

By default, Muse will not take many important actions, like sending an email, without your approval. Many Connectors can also be set up so Muse can only retrieve data and not take actions, such as sending a calendar invite. You can change when Muse asks for your approval in Settings.

Supporting quotations

By default, Muse will not take many important actions, like sending an email, without your approval. Many Connectors can also be set up so that Muse is only able to retrieve data, but not take actions (like sending a calendar invite).
You can change when Muse asks for your approval

Qualifications & exceptions

  • The default covers "many" important actions, not stated to be all.
  • Retrieve-only setup is available for "many" Connectors, not stated to be all.
  • You can change when approval is requested in Settings.

Not stated here

  • The policy does not list which actions need approval by default or which Connectors can be set to retrieve only.

Sharing & Disclosure · Context

Connectors have their own terms and privacy policies for the information Muse gives them

When you connect a Connector, you are requesting that Muse exchange information with it to perform actions for you. The policy says Connectors have their own terms and privacy policies that govern how they use the information they receive.

Supporting quotations

When you connect Connectors, you are requesting that Muse exchange information with them to perform actions for you.
Connectors have their own terms and privacy policies that govern how they use the information they receive.

Qualifications & exceptions

  • How a Connector uses information it receives is governed by that Connector's own terms and policies.

Not stated here

  • The terms and privacy policies of individual Connectors are not part of this document.

Data Access & Collection · Company practice

Muse is designed to exchange with Connectors only the data they need to work for you

The policy says Muse was designed to exchange with Connectors only the data needed for them to work for you. For example, connecting your email lets Muse search your email, but it will not download your whole inbox unless you tell it to.

Supporting quotations

We designed Muse to exchange with Connectors only the data that's needed for them to work for you. For example, connecting your email allows Muse to search your email, but it won't download your whole inbox (unless you tell it to).

Qualifications & exceptions

  • Stated as a design intention ("We designed Muse to"), not as an absolute guarantee.
  • Exception: Muse can download more, such as a whole inbox, if you tell it to.

Not stated here

  • The policy does not define what data counts as "needed".
Also annotated in the same passage (1)

Data Access & Collection · Company practice

Some Connectors can send information to Muse on their own, and the company says it identifies them before you connect

Some Connectors can also share information proactively with Muse. For example, calendar Connectors can update Muse automatically when there are changes in your schedule. The company says it identifies Connectors that do this before you connect them.

Supporting quotations

Some Connectors can also share information proactively with Muse. For example, calendar Connectors can update Muse automatically when there are changes in your schedule. We identify Connectors that do this before you connect them.

Qualifications & exceptions

  • Applies to "some" Connectors.
  • Identification is stated to happen before you connect.

Not stated here

  • How a proactive Connector is identified to you is not described.
Also annotated in the same passage (1)

Retention & Deletion · User right or choice

You can disconnect a Connector at any time, but data Muse already used may remain in its memories and your history

Disconnecting a Connector stops Muse from exchanging data with it. Data Muse previously used to perform tasks with that Connector may remain in Muse's memories and your conversation history. You can ask Muse to "forget" those interactions, as described under deleting Muse data.

Supporting quotations

You can disconnect a Connector at any time. This stops Muse from exchanging data with the Connector. Data that Muse previously used to perform tasks with that Connector may remain in Muse's memories and your conversation history. You can ask Muse to "forget" those interactions, as described below.

Qualifications & exceptions

  • Disconnecting stops exchange going forward; previously used data "may remain".

Not stated here

  • The policy does not say how long such data may remain in memories or conversation history.

Cross-references

Retention & Deletion · User right or choice

You can delete messages, Side Chats and VM files, or reset Muse to delete all your Muse data

You can delete any message you send to Muse, Side Chats with Muse, and files in your virtual machine. If you want to start from scratch, you can reset Muse, which the policy says deletes all your Muse data.

Supporting quotations

You can delete any message you send to Muse, Side Chats with Muse, and files in your virtual machine. If you want to start from scratch, you can reset Muse, which deletes all your Muse data.

Qualifications & exceptions

  • Individual deletion covers messages you send, Side Chats and files in your VM; reset deletes all your Muse data.

Not stated here

  • This passage does not state how quickly deleted data is removed, or whether copies held by Connector services or data already used for AI training are affected.

Cross-references

Retention & Deletion · Restriction or exception

Muse may still remember information it learned from something you deleted

After you delete something, Muse may still "remember" information it learned from what you deleted.

Supporting quotations

After you delete something, Muse may still "remember" information it learned from what you deleted.

Qualifications & exceptions

  • Stated as "may", not as always.

Not stated here

  • The passage does not say how long, or in what form, remembered information is kept.

Cross-references

Also annotated in the same passage (2)

Retention & Deletion · User right or choice

You can use the Forget skill to ask Muse to forget topics or people, and you can see what Muse remembers

You can use the Forget skill to have Muse forget information about specific topics or people; Muse will forget the information to the best of its ability. You can find out what Muse remembers about you at any time by asking it directly or by viewing files like your MEMORY.md.

Supporting quotations

You can also use the Forget skill to have Muse forget information about specific topics or people; Muse will forget the information to the best of its ability.
You can find out what Muse remembers about you at any time by asking directly, or by viewing files like your MEMORY.md.

Qualifications & exceptions

  • Forgetting is "to the best of its ability", not stated as guaranteed.
  • Applies to specific topics or people you name.

Cross-references

Also annotated in the same passage (2)

Data Access & Collection · Company practice

What Muse collects depends on how you use it, and is in addition to what the Meta Privacy Policy describes

The information the company collects depends on how you use Muse and what you choose to share or connect. The policy lists the Muse-specific items below in addition to the information described in the Meta Privacy Policy.

Supporting quotations

The information we collect depends on how you use Muse and what you choose to share or connect.
In addition to the information described in the Meta Privacy Policy, we collect:

Qualifications & exceptions

  • Collection varies with how you use Muse and what you share or connect.

Not stated here

  • The Meta Privacy Policy is linked but its text is not supplied here, so the information it describes is not shown by this card.

Data Access & Collection · Company practice

Muse collects your messages, its replies and task information, including voice, photos and info about others

The policy says the company collects your interactions with Muse: your messages and instructions, Muse's responses, and information from services, including Connectors, used to perform tasks for you. This can include text, voice, photos, things you create together and information about you or others.

Supporting quotations

Your interactions with Muse. Your messages and instructions, Muse's responses, and information from services including Connectors used to perform tasks for you. This can include text, voice, photos, things you create together and information about you or others.

Qualifications & exceptions

  • The list of what interactions "can include" is introduced with "can", so it may not be complete.
  • Can include information about people other than you.
Also annotated in the same passage (1)

Data Access & Collection · Company practice

Muse collects files you upload or create, plus saved preferences, goals, memories and scheduled tasks

The policy says the company collects files you upload, ask Muse to store, or create with Muse, including Artifacts and system files such as MEMORY.md. This also includes saved preferences, goals, memories and scheduled tasks. Elsewhere the policy says you can find out what Muse remembers about you at any time by asking directly or by viewing files like your MEMORY.md.

Supporting quotations

Files and stored information. Files you upload, ask Muse to store, or create with Muse, including Artifacts and system files such as MEMORY.md. This also includes saved preferences, goals, memories, and scheduled tasks.
You can find out what Muse remembers about you at any time by asking directly, or by viewing files like your MEMORY.md.

Qualifications & exceptions

  • Covers files you upload, ask Muse to store or create with Muse, and saved preferences, goals, memories and scheduled tasks.
Also annotated in the same passage (2)

Data Access & Collection · Company practice

Information Muse gets from connected services is collected and counts as part of your interactions

The policy says the company collects information Muse retrieves or receives from connected services, such as emails and calendar events. Information used for a task forms part of your interactions with Muse, so the same Settings toggle that controls training use of your interactions also covers information from services used for tasks, including Connectors.

Supporting quotations

Information from Connectors. Information Muse retrieves or receives from connected services, such as emails and calendar events. Information used for a task forms part of your interactions with Muse.
The same toggle in your Settings controls whether that information can be used to improve AI at Meta.

Qualifications & exceptions

  • Examples given are emails and calendar events; the list is introduced with "such as".
  • The task-information link to the training toggle applies to information used for a task.

Cross-references

Data Access & Collection · Company practice

Muse collects activity and metadata, including features used, websites visited, and actions and transactions

The policy says the company collects information about how you use Muse, including features used, websites visited, actions and transactions, timing and frequency, and associated metadata.

Supporting quotations

Activity and metadata. Information about how you use Muse, including features used, websites visited, actions and transactions, timing and frequency, and associated metadata.

Qualifications & exceptions

  • The listed items are introduced with "including", so the list may not be complete.

Not stated here

  • The passage does not say how websites visited, actions and transactions are observed, for example whether only those Muse performs for you.

Linking & Identification · User right or choice

To keep Muse out of a shared Accounts Center, you can sign up with an email not tied to an existing account

Except in circumstances where this policy says data will not be used, if you add Muse to the same Accounts Center as other Products, the company may combine and use your information across profiles and devices in that Accounts Center. If you don't want to use Muse in the same Accounts Center as other Products, you can sign up for Muse with an email that isn't associated with an existing account. Earlier the policy says that if you keep accounts separate, Muse won't share your Muse interactions or data on your VM with other Meta Products.

Supporting quotations

Except in circumstances where this Privacy Policy says data will not be used, if you add Muse to the same Accounts Center as other Products, we may combine and use your information across profiles and devices in that Accounts Center.
If you don't want to use Muse in the same Accounts Center as other Products, you can sign up for Muse with an email that isn't associated with an existing account.
If you keep accounts separate, Muse won't share your Muse interactions or data on your VM with other Meta Products.

Qualifications & exceptions

  • Combining is something the company "may" do.
  • Exception: circumstances where this policy says data will not be used.
  • The separate-account route described is signing up with an email not associated with an existing account.

Not stated here

  • The linked help page on how information is used and shared across accounts is not supplied here, so what it adds is not shown.
  • This passage does not list every circumstance in which the policy says data will not be used.
Also annotated in the same passage (2)

Legal Rights & Agreement Rules · Context

Using Muse through Meta Wearable Products adds the Supplemental MPT Privacy Policy; the Muse policy wins conflicts

If you access or use Muse through Meta Wearable Products, the Supplemental MPT Privacy Policy also applies. If the two conflict, the Muse Privacy Policy takes precedence.

Supporting quotations

If you access or use Muse through Meta Wearable Products, the Supplemental MPT Privacy Policy also applies.
In the event of any conflict, the Muse Privacy Policy takes precedence.

Qualifications & exceptions

  • Applies only when you access or use Muse through Meta Wearable Products.
  • Muse policy precedence applies only in the event of a conflict.

Not stated here

  • The Supplemental MPT Privacy Policy is linked but its text is not supplied here, so what it adds or where it conflicts is not shown.