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