MultiMuse
Sign in

Privacy Policy — MultiMuse

Last updated: July 15, 2026

Scope

This Privacy Policy applies to MultiMuse (the "Service"), operated by BackStagePass Group ("we," "us," or "our"). It covers:

  • The MultiMuse Discord bot, including muse profiles, proxy posting, thread tracking, connections, and related features.
  • multimuse.app and hub.multimuse.app, including the dashboard, Studio, documentation, account linking, support, and session management.
  • Character profiles, directory listings, community pages, connections, and storylines.
  • The MultiMuse Discord Activity and HTTP API.
  • Reporting, blocking, moderation, and account records.

Other BackStagePass Group products have separate policies: StageHand, BackDrop.

This Policy is part of our Terms of Service. By using the Service where consent is required by law, you agree to both documents.

Information we collect

We do not sell personal information. We collect only what is needed to operate MultiMuse.

Muse, profile, and listing content

Content you create or configure, including muse names, triggers, nicknames, slugs, avatars, banners, descriptions, quotes, notes, tags, availability, connection graphs, story timeline entries, group metadata, community descriptions, share settings, and visibility or content-rating choices.

Proxy and message data

When you post through a muse trigger, we store the text of proxied messages and related metadata, such as message IDs, channel IDs, webhook references, and muse association, so we can synchronize edits and deletions with Discord. We do not index unrelated messages that do not match a configured trigger.

Discord identifiers, account, and preferences

  • Discord user ID, username, avatar, and OAuth scopes shown when you sign in.
  • Guild, channel, and message IDs where MultiMuse is used or configured.
  • Member display names and usernames when needed for member lists, sharing, or API integrations.
  • Terms acceptance timestamp and onboarding choices, such as card publicity sync.
  • Age confirmation timestamp when you complete the website welcome flow.
  • Session cookies to keep you signed in.

Safety and community features

  • Reports you submit (reason, details, target profile or listing).
  • Block relationships between MultiMuse accounts.
  • Moderation actions taken on your account or content.

Technical data

IP address, browser type, request metadata, and error logs for security, abuse prevention, and reliability.

Anonymous web analytics

We use a self-hosted Umami instance to understand aggregate website traffic and feature use. It records page paths, referrers, browser and device categories, approximate location, Core Web Vitals, and fixed events such as bot-invite, documentation, login, and dashboard-navigation clicks.

Umami does not set analytics cookies or identify you across websites. It briefly uses your IP address, browser information, and this website's ID to derive an anonymous session and approximate location, but does not store the source IP address. We exclude URL query strings and hashes, do not send Discord or muse identifiers as analytics properties, and respect your browser's Do Not Track setting.

Billing (if applicable)

If you purchase premium features, payment processors such as Stripe or Patreon may receive billing details. We store subscription status and processor identifiers, not full card numbers.

Support

Information you send us by email, Discord support channels, or support forms.

Discord Activities (Connections)

MultiMuse offers a Discord Activity that opens an embedded viewer for muse connection clouds inside Discord.

  • Authentication. Inside the Activity iframe, we request Discord's identify scope. We use your Discord user ID and username to load your muses and published public connection clouds.
  • Launch context. When the bot starts an Activity, it registers a short-lived launch intent containing the Activity instance ID, muse ID, optional viewer slug, and guild ID so the iframe opens the correct cloud. These records expire and are not used for marketing.
  • Public browse. The generic Activity entry may show connection clouds that owners have marked public and non-private.
  • Media. Muse avatars and images may load through our Activity media proxy from allowlisted hosts to comply with Discord's iframe security rules.

How we use information

We use collected data to provide and improve MultiMuse, including proxy posting, muse management, tracking, profiles, directory and community discovery, reporting, blocking, Studio, API, and Activity features; authenticate users; enforce our policies; maintain security; and comply with law. We do not use your data for advertising or sell it. We do not train machine learning or AI models on your messages, profiles, or muse content.

Sharing and processors

We share data only as needed to operate MultiMuse:

  • Discord — OAuth sign-in, proxy posting, commands, Activities, and linked server or community information you choose to show.
  • Hosting and database providers — to store profiles, listings, reports, messages, and account records.
  • Payment processors — if you subscribe to paid features.
  • Cloudflare — image and file hosting and delivery (R2 object storage and/or Cloudflare Images, including shared CDN domains such as cdn.backstagepass.quest and product-specific media hostnames); CDN, WAF, and security services when traffic is proxied through Cloudflare. Where enabled on our media zones, Cloudflare's CSAM Scanning Tool compares cached image hashes against known abusive-material lists and may block matching URLs; we receive notifications as described in Cloudflare's documentation.
  • MultiMuse control plane — when syncing muse card data from your MultiMuse account to website profiles.

Public profiles and directory listings are visible to other visitors according to your visibility settings and content rating. NSFW-tagged content carries an 18+ rating and can be found with content-rating filters. The beta does not currently provide a per-account setting that hides all mature content.

Retention and deletion

We retain data while you use MultiMuse and as needed for legitimate operations or legal obligations. When you delete muses or content, unpublish profiles, disconnect the bot, delete your Discord account, or request account removal, we delete or anonymize associated records within a reasonable time. Anonymous web analytics are normally retained for no more than 13 months. Contact us for deletion requests we cannot handle in-product.

Security

We use reasonable technical and organizational measures (including access controls and encryption where appropriate) to protect data. No system is perfectly secure. Secure your Discord account with a strong password and two-factor authentication.

Children

MultiMuse is not directed at children under 13, and we do not knowingly collect personal data from them. Creating a MultiMuse website account, publishing profiles or communities, and browsing mature content require users to be at least 18. If you believe we collected a child's personal data, contact us and we will delete it.

International transfers

Data may be processed in the United States or other countries where our providers operate. Where required, we use appropriate safeguards for cross-border transfers.

Your rights

Depending on where you live, you may have rights to access, correct, delete, or restrict processing of your personal data, or to object or port data. Use in-bot, Studio, and account settings where available, or email support@backstagepass.quest. We will not discriminate against you for exercising these rights.

Changes

We may update this Policy. The "Last updated" date will change when we do. Continued use after material changes means you accept the updated Policy.

Contact

Privacy questions: support@backstagepass.quest. See also our Terms of Service and Content Policy.