Meta Muse for Small Business: What It Connects To, What It Costs and the Privacy Questions

Meta is expanding Muse from a personal AI assistant into a tool for small-business work. Announced on September 29, 2026, Muse for Small Business connects to commerce, accounting, payments, design and collaboration services—as well as professional Facebook and Instagram accounts. The trade-off is straightforward: broader access could help an agent coordinate work, but it also raises the stakes of permission choices and data handling. 1730

What Muse for Small Business connects to

Meta lists 15 third-party services: Asana, Box, Canva, Dropbox, Figma, Granola, HighLevel, Intuit QuickBooks, Klaviyo, Lovable, Notion, Shopify, Slack, Stripe and Zoom. Muse can also connect to Facebook and Instagram business accounts. 30

Those integrations span several kinds of work: Shopify and Stripe for commerce and payments, QuickBooks for accounting, Canva and Figma for design, and Slack, Asana and Notion for collaboration and task management. The agent can also access Instagram professional-account analytics, Facebook Pages and Meta ad accounts. 1730

Meta’s pitch is that an owner can give Muse a broader goal—such as running parts of a business or finding customers—and have it work across connected tools. For example, reporting describes asking Muse to analyze sales, campaigns and social activity and develop a growth plan. That is a stated use case, not a guarantee that the agent will complete every business task accurately or without supervision. 2130

Pricing and Meta’s revenue strategy

Meta’s launch announcement does not set out a separate small-business price. CNBC reported that the business version would follow the existing Muse app’s model: free use with limits and a paid subscription for more access. That gives a general pricing indication, but the available reports do not specify a distinct business plan or its terms. 2630

The expansion also puts Muse into business workflows beyond Meta’s advertising products. Reuters described the move as part of Meta’s effort to diversify revenue beyond advertising. Separately, a report says Mark Zuckerberg described a plan for Muse to take a small fee from transactions; the available information does not provide a fee schedule or explain how such fees would apply to small-business customers. 1722

Privacy safeguards—and the questions they leave

Meta says each Muse user’s cloud virtual machine is isolated from other users’ agents, and that conversations and VM data are not shared with Meta’s ad systems. Meta also says users decide whether Muse interactions can be used to train and improve its AI models. Its help guidance says that setting is on when a person first uses Muse, can be changed later, and that certain categories of identifying information are removed if training use is allowed. 1315

Those safeguards do not remove the need to understand what access is being granted. A CNET report says Muse may request access to sensitive personal data, including messages, email, calendars, contacts and files. For a business, connected services may also contain customer information, financial records or unpublished plans. 730

The distinction to keep in mind is between securing an agent’s environment and controlling what it can do with authorized information. Before connecting a service, a business should check the permission requested, whether access can be limited, what actions require approval, and whether interaction data is set to be used for model improvement. Meta says users control access and training settings, but those controls are useful only when their scope is clear. 115

What the reported privacy incidents show—and what they don’t

A report that Muse read private Apple Messages without permission remains disputed. Meta said the Mac Messages integration is opt-in and requires both Full Disk Access and the Messages connector to be enabled. The reporting establishes a public disagreement about consent; it does not establish unauthorized access as fact. 27

A separate Marketplace incident involved a user who said Muse shared his home address while helping sell a keyboard. In a later account, he said he had selected “Allow Always,” believing Muse would still ask before accepting offers. The episode highlights how persistent authorization can have consequences a user may not expect; the available account does not show that Muse bypassed a permission setting. 11

Taken together, these cases point to a practical issue for small businesses: an agent’s usefulness depends on access, but the risk depends on how clearly that access and its limits are understood. Muse’s integrations could bring work into one workflow, yet owners should treat each connection—especially to customer, message and financial data—as a decision to review rather than a routine setup step.