Muse · Legal
This page identifies the key third parties that receive or process personal information in connection with operating Muse (also known as MuseChat) and the musechat.app website. It is linked from our Privacy Policy. We do not list ordinary development tools that do not receive Muse user personal information.
Muse uses third-party providers only for specific functions needed to operate the service, such as hosting, AI processing, messaging, diagnostics, app distribution, payments, customer support, and operating our website and waitlist.
We seek to minimize the information sent to each provider. Where a provider processes personal information on our behalf, we use the provider’s business/API service and applicable data-processing terms, and we require the provider to protect personal information to a standard at least as protective as our Privacy Policy and to use it only to provide services to Muse.
Unless you separately and affirmatively opt in, Muse will not use your private recordings, stories, transcripts, or synthetic voice data to train general-purpose artificial intelligence models. Muse configures or contracts with the providers processing this information on our behalf so that they may not use it to train their general-purpose models except where you have separately consented or where we clearly disclose a different arrangement before the information is provided.
Provider retention and processing locations vary by provider, product, account configuration, and service region. We do not represent that all processing occurs only in the United States.
Before your conversations are first sent to the providers in this section, the Muse application asks for your permission and explains what is shared.
Voice synthesis, including the temporary synthetic representation of your voice used to narrate a story you have approved, is performed by Muse itself on infrastructure we operate (see Amazon Web Services below). Your voice is not sent to a third-party voice-synthesis provider.
Purpose: Conversation and story processing.
Information processed: Conversation text, transcripts, story drafts, and relevant context needed for the request.
Anthropic’s commercial/API terms state that customer inputs and outputs are not used to train its models by default. Standard API retention may apply unless a different retention arrangement is enabled.
Purpose: Audio transcription and live voice conversation.
Information processed: Live audio and audio submitted for transcription, conversation text or transcripts, session context, and model responses needed to conduct the conversation.
OpenAI states that API inputs and outputs are not used to train its models by default. API retention varies by endpoint and account configuration.
Purpose: Database, authentication, file storage, and backend services.
Information processed: Account identifiers, profile information, recordings, transcripts, stories, sharing records, consent records, and other information stored in the Muse application database.
Supabase supports customer-selected project regions. Some support and subprocessor activity may occur outside the selected project region.
Purpose: Cloud infrastructure, text-message delivery through Amazon SNS, and the infrastructure on which Muse runs its own voice processing and voice synthesis, including the temporary synthetic voice representations described in Section 6.3 of the Privacy Policy.
Information processed: Depending on the service involved, phone numbers, audio, voice samples and temporary voice representations, story text, generated audio, and technical service data. AWS provides the infrastructure; the voice-synthesis software is operated by Muse.
For regional AWS services, Muse selects the AWS region in which customer content is stored or processed. AWS may make limited transfers as necessary to provide or maintain requested services or comply with law.
Purpose: Hosting infrastructure for Muse’s live voice service.
Information processed: Live session traffic, which may include audio, conversation text or transcripts, session identifiers, and technical session metadata while the service is operating.
Railway states that its primary processing operations take place in the United States. Availability of other storage-location options depends on the Railway service and plan.
Purpose: Transactional email, including invitations and important service messages.
Information processed: Email addresses, names where included, and the content and delivery metadata of messages Muse sends through Resend.
Purpose: Verification codes and other service text messages. Amazon SNS is an AWS service.
Information processed: Phone numbers and message-delivery information required to send those messages.
Purpose: Email for privacy requests, support, and other correspondence with Muse.
Information processed: Your email address, the content of messages you send us, and any information you include in a privacy or support request.
Google processes this information as our email provider under Google Workspace’s business terms.
Purpose: Crash reporting, error monitoring, and application diagnostics.
Information processed: Device and operating-system information, application diagnostics, error details, and limited technical identifiers.
Muse is designed not to intentionally send voice recordings, transcripts, or story content to Sentry as diagnostic data.
Sentry supports more than one data-storage region; the region used by Muse depends on our Sentry organization configuration.
Purpose: iOS App Store distribution, TestFlight beta distribution, and, when enabled, in-app purchases.
Apple handles its App Store relationship with you under Apple’s own terms and privacy practices. Apple may process purchase and payment information. Muse receives information such as purchase confirmations and transaction metadata rather than your full payment-card details.
During the beta, Apple’s TestFlight service collects crash reports from beta builds and any feedback, comments, or screenshots that testers choose to submit through TestFlight, and shares them with Muse.
Apple acts independently for portions of the App Store and payment relationship rather than solely as a processor acting under Muse’s instructions.
These providers are used for the musechat.app website and waitlist. They do not receive information from the Muse application.
Purpose: Website hosting for musechat.app.
Information processed: Standard server information such as IP address, browser type, and pages requested.
Purpose: Waitlist signup and email delivery.
Information processed: Your email address, your stated interest (for yourself or for someone you love), signup date, and email engagement information such as opens and clicks.
Purpose: Advertising measurement for the musechat.app website.
Information processed: Cookie and device identifiers, pages visited on our website, and standard usage data, which these partners may combine with information they hold about you from other websites and services. See Section 12 of the Privacy Policy for how to limit this.
Meta and TikTok act independently for advertising measurement rather than solely as processors acting under Muse’s instructions.
Muse also uses development tools such as GitHub and Expo. Based on our current configuration, these tools are used for source code, testing, and build artifacts and are not intended to receive Muse recordings, stories, transcripts, or other user content. We therefore do not list them above as user-data processors.
Our providers may change as Muse evolves. We update this page when we add, remove, or materially change a provider that receives or processes user personal information.
Questions about this list or how a provider is used can be sent to privacy@musechat.app.