How Muse handles your privacy, safety and security

We’ve designed Muse to have multiple layers of privacy and security protections. No automated system is perfect, so review Muse’s activity and only grant the access you’re comfortable with.

Your data in Muse

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. Muse also maintains backups to help protect your agent’s history from data loss. Every Muse user’s VM is isolated so no one else’s agent can access it.

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.

Muse and Meta ads

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.

How Muse keeps logins safe

When you connect an app or service, credentials like usernames and passwords are stored in a Secure Credentials Store. Muse can use the Secure Credentials Store to complete an authorized action without the AI model seeing your password. Before Muse uses your credentials, the request goes through checks designed to confirm that:

Protection against malicious instructions

Websites, emails, files and connected services can contain instructions intended to manipulate an AI agent. This is sometimes called a prompt injection attack. Muse uses multiple protections to help detect and resist these attempts. These include model training, automated detection systems, and limits on the information and services Muse can access during a task. Important permission and security checks operate separately from the AI model, meaning that they don’t depend only on Muse recognizing that an instruction may be malicious.

Improving our AI models

You decide whether we can use your interactions with Muse to develop and improve our AI models. This setting is on when you first use Muse. You can change it at any time using the toggle in your Settings under Data controls. 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.

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.

You control connected apps and services

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.

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). 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.

Learn more about Connectors and how to manage them.

Permissions for important actions

Muse is designed to ask you to confirm before it takes certain important actions like sending an email or making a purchase. When Muse requests permission, you can review the proposed action before allowing or denying it. Permission requirements may vary depending on the action, the Connector and the default permissions you selected.

Many of these approval checks are enforced outside the AI model, so they don’t rely only on Muse deciding whether it should ask. You can also review Muse’s activity at any time. Learn more about how Muse works with your guidance and approval.

Safety standards

Muse is built to a set of safety standards that govern both what your Muse says and what it does. For example, these standards are designed to prevent your Muse from:

Deleting and forgetting 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 deletes all your Muse data.

After you delete something from Muse, Muse may still remember information it learned from what you deleted. You can also use the forget skill: simply ask Muse to forget a topic or set of interactions. Forgetting works by asking Muse to look for information about a specific person, topic or matter in its memories and supporting files and remove it 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.

Report a problem

If your Muse does something unexpected or concerning, you can report it so our team can investigate and improve safety. To report a bug:

Reporting helps us identify and address bugs and concerning behavior.