Meta’s connector help page says users can ask Muse to create a Custom Connector when a service is absent from the catalog. The process can involve supplying the service’s API information, stored in Muse’s secure credential store. Meta explicitly says it does not review custom connectors or how they use information, making this a different proposition from selecting a familiar listed integration.
The same guidance says disconnecting a connector stops further data exchange, but information already used may remain in conversations or memory. Many connectors can be restricted to retrieving data, and important actions require approval by default. The help page is undated apart from a relative update label, so no specific feature-launch date can be established from it.
Editorial take: A custom connector is an access decision before it is a productivity shortcut. Start by understanding the destination, the data it receives and the smallest permission the task needs. A successful connection shows that two systems can communicate; it does not by itself establish that the service is trustworthy or the proposed workflow is appropriate.