mumo← Back

mumo — Terms of Service

Effective: April 30, 2026 Last updated: April 30, 2026

These Terms of Service ("Terms") govern your use of mumo, a multi-model AI deliberation platform operated by Sourced LLC ("mumo," "we," "us," or "our"). By accessing or using mumo, you agree to these Terms.

1. What mumo is

mumo is a multi-model AI deliberation platform. You submit prompts, context, steering input, annotations, and other content. mumo routes selected content to AI models and displays their responses in a deliberative interface. You decide what to include, route, preserve, share, or discard, subject to the features available in your plan.

mumo may be used through the web application, API, MCP (Model Context Protocol) interfaces, scripts, agents, or other approved programmatic interfaces.

Models available through mumo include proprietary models and open-weight models. Proprietary model routes may include models such as Claude (Anthropic), GPT (OpenAI), Grok (xAI), and Gemini (Google). Open-weight model routes may include models such as Kimi (Moonshot), GLM (Zhipu), and Qwen (Alibaba), hosted by third-party inference providers. We may add, remove, rename, replace, reroute, or limit models at any time. The model list shown in the product at the time you use mumo is the authoritative list of currently available models.

2. Eligibility

You must be at least 18 years old to use mumo. By creating an account or using mumo, you represent that you meet this requirement.

3. Accounts and credentials

You may sign in using Google OAuth or other authentication methods we support. We do not store your Google password.

You are responsible for maintaining the security of your account, workspace, mumo API keys, MCP credentials, and other access tokens. Any request made using your credentials is treated as authorized by you unless and until you revoke the credential or notify us that it has been compromised.

If you create a mumo API key, you are responsible for storing it securely. We may revoke, rotate, restrict, or suspend credentials where we believe doing so is necessary for security, abuse prevention, provider-policy compliance, legal compliance, or platform integrity.

4. What you can do

You may use mumo for lawful personal, professional, educational, research, and internal business purposes.

You may use approved mumo APIs, MCP interfaces, and documented programmatic access methods, subject to these Terms, applicable plan limits, provider restrictions, safety controls, and rate limits.

You may share conversations using share links where that feature is available. Shared conversations are publicly accessible to anyone with the link unless and until you delete the underlying session or revoke the share link where revocation is supported.

5. What you cannot do

You agree not to use mumo to:

  • violate applicable law or the rights of others;
  • generate illegal, abusive, threatening, harassing, exploitative, or rights-violating content;
  • generate spam, phishing, malware, credential theft, or other abusive or deceptive content;
  • attempt to circumvent model safety systems, access controls, rate limits, provider policies, billing systems, or technical restrictions;
  • reverse engineer, scrape, attack, overload, or attempt to extract mumo source code, non-public systems, or model/provider credentials;
  • impersonate another person or organization, or misrepresent AI-generated content as human-authored where disclosure is legally or ethically required;
  • use mumo to violate the terms, policies, or usage rules of any underlying model provider, inference provider, infrastructure provider, or integrated service;
  • access mumo through automated systems except via mumo-approved interfaces, including documented APIs and MCP interfaces; or
  • submit data that you do not have the right to process, transmit, or route through mumo and its providers.

We may suspend or terminate accounts, credentials, sessions, models, or features that violate these Terms or create legal, security, abuse, provider-policy, or platform-integrity risk.

6. API, MCP, and autonomous agents

mumo supports access through APIs, MCP clients, scripts, tools, autonomous agents, and other programmatic interfaces. You are responsible for all activity conducted through your account, workspace, mumo API keys, MCP credentials, or other access tokens.

If an agent, script, tool, employee, contractor, integration, or automated system acts under your credentials, its actions are treated as your use of mumo. This includes prompts submitted, files or tool outputs transmitted, third-party data retrieved, routing choices made, models selected, analysis-feedback records submitted, and outputs generated.

You represent that you have all rights, permissions, notices, and authority necessary to submit content through mumo, including content submitted by agents or integrations acting on your behalf. This includes authority to transmit that content to mumo, to selected model providers and inference providers, and to infrastructure providers described in these Terms and our Privacy Policy.

You are responsible for configuring, supervising, and monitoring agents that use mumo. mumo is not responsible for an agent exceeding your intended scope, disclosing sensitive information, generating incorrect output, violating third-party terms, or taking actions you did not anticipate.

We may impose rate limits, spend limits, model limits, safety checks, abuse monitoring, logging, or other controls on API, MCP, and agentic use.

7. Your content and AI outputs

You retain ownership of the prompts, context, annotations, commentary, steering decisions, uploaded materials, and other content you submit to mumo ("User Content").

Subject to your plan, settings, and these Terms, you grant mumo a non-exclusive, worldwide license to host, store, process, transmit, display, reproduce, and use User Content as necessary to provide, secure, operate, support, debug, and improve mumo as described in these Terms and our Privacy Policy.

AI-generated responses are generated by third-party model providers or inference providers. Rights to use AI-generated output may be governed by the applicable provider's terms. You are responsible for reviewing provider terms where your use requires certainty about output ownership, publication, commercial use, or other downstream rights.

Analysis-feedback records. Analysis-feedback records are structured assessments of deliberation sessions. They may be generated by you, by your agents or tools, or by mumo features, and may include ratings, labels, summaries, critiques, model comparisons, routing recommendations, skill-behavior observations, failure analyses, and references to prompts, annotations, model responses, or other session content. Analysis-feedback records are treated as session-derived content submitted under your credentials and are subject to the Platform Improvement settings described in Section 8.

8. Data use, model training, and Platform Improvement

No training of competing or generative AI models on your content. mumo does not use your conversations, prompts, annotations, steering decisions, model responses, analysis-feedback records, or other session content to train, fine-tune, distill, align, pretrain, or reinforcement-learn AI models that generate text, reasoning, embeddings made commercially available to third parties, audio, images, video, or other generative outputs. mumo does not use your content to develop AI models that compete with the underlying model providers' products or services.

Internal orchestration tooling. mumo may develop internal models, classifiers, rankers, or scoring functions used solely to operate and improve the mumo orchestration layer — for example, classifiers that categorize incoming requests, rankers that score model-suitability for a prompt, or pipelines that inform default panel composition. These internal models are not distributed, licensed, or made commercially available to third parties as standalone products, and are subject to your tier's Platform Improvement settings (below).

No provider training of your traffic. mumo configures third-party model and inference-provider routes so that your mumo session content is not used by those providers to train their models, except where you separately and explicitly opt in through a feature that clearly says so. Provider policies and account-level settings may change over time; we will update this Section if a route materially differs from this posture.

Platform Improvement. Depending on your tier, account settings, and per-session settings, mumo may use session data, metadata, model outputs, annotations, steering decisions, and analysis-feedback records to improve the mumo platform. Platform Improvement includes improving panel composition, default model selection, routing behavior, prompt assembly, skill behavior, evaluation methods, abuse prevention, reliability, safety, latency, cost controls, and usability. Platform Improvement may include developing the internal orchestration tooling described above.

Platform Improvement does not include training generative AI models on your content. It does not include selling your content to model providers. It does not include using provider API data to build a model that competes with the underlying providers' products or services.

Free Tier. Free-tier sessions are eligible for Platform Improvement by default as part of the free service. This includes potential generation and review of analysis-feedback records derived from free-tier sessions. Free-tier users may upgrade to a paid plan to access exclusion controls.

Paid Tier. Paid-tier sessions are eligible for Platform Improvement by default if the Platform Improvement setting is enabled at enrollment or in account settings. Paid users may turn this setting off at enrollment, later in account settings, or per session through supported API/MCP controls. The Platform Improvement toggle is shown in the paid enrollment flow and is operable before purchase activation.

Per-session API/MCP controls. Where supported, API and MCP session-creation requests may include an optional boolean:

{ "improvement_consent": true }
  • omitted — mumo uses the plan-level and account-level setting in effect at the time of the session.
  • true — the session is eligible for Platform Improvement, if allowed for the account.
  • false — the session is excluded from Platform Improvement, where available for the account. For Paid accounts, false is honored for the session.

Free-tier exclusion handling. Free-tier accounts do not have access to per-session exclusion, since Free Tier participation in Platform Improvement is part of the free service.

  • On the REST API, a Free-tier request that sets improvement_consent: false is rejected with the error consent_exclusion_unavailable. The session is not created.
  • On the MCP tool surface, a Free-tier request that sets improvement_consent: false is accepted; the session is created and included in Platform Improvement, and the response carries an explicit disclosure explaining that Free-tier sessions are included under accepted terms and the exclusion request was not applied.

This split exists for workflow continuity: error responses on synchronous calls let developers correct configuration immediately, while autonomous agents calling mumo at volume over MCP receive a non-blocking, in-band record of the resolution. The MCP path is not a privacy escape hatch: the resolved outcome (inclusion) is identical to what would happen on the API path if a developer ignored the error and retried; the audit trail and disclosure are the same.

We record both the requested improvement_consent value and the resolved Platform Improvement state for each session for auditability, regardless of transport.

Excluded sessions. If a session is excluded from Platform Improvement, mumo will not intentionally add that session to the analysis-feedback queue or use it for Platform Improvement. mumo may still process and retain limited metadata and logs as needed to provide the service, maintain security, prevent abuse, debug errors, enforce limits, comply with law, and maintain ordinary business records.

Agent-submitted feedback. Analysis-feedback records may be generated outside mumo by your agent, tool, or client and submitted to mumo through the API, MCP, or other supported interfaces. mumo treats those records as content submitted under your credentials. Unless a feature clearly says otherwise, mumo does not send excluded sessions to a separate third-party model provider solely to generate analysis-feedback records.

9. Model infrastructure and routing

When you use mumo, the content needed to generate a model response is transmitted to the provider or inference host for the selected model route.

Direct proprietary routes. For proprietary model routes (such as Claude, GPT, Grok, or Gemini), mumo sends the relevant prompt, selected context, generation parameters, and technical metadata directly to the applicable model provider (e.g., Anthropic, OpenAI, xAI, Google). Proprietary model providers may temporarily retain API inference data for limited periods for abuse monitoring, security, and policy enforcement, per each provider's own policies. As described in Section 8, providers do not use mumo's API traffic to train their models.

Inference-provider routes. For certain open-weight model routes (such as Kimi, GLM, Qwen, and similar models), mumo sends the relevant prompt, selected context, generation parameters, and technical metadata to Fireworks AI, a U.S.-based inference provider that hosts and serves those model weights. For these Fireworks-hosted routes, Fireworks AI receives your inference payload; the original model architect (e.g., Moonshot, Zhipu, Alibaba) does not receive that inference payload from mumo. This is a deliberate part of mumo's privacy posture.

Fireworks AI operates under a zero data retention architecture for open-model inference: prompt and generation data exist only in volatile memory for the duration of the request and are not written to persistent storage. mumo uses Fireworks' standard chat completions endpoints and has not opted into any Fireworks features that would change this retention behavior (such as FireOptimizer, persistent prompt logging for advanced features, or the Response API's longer retention window). If we enable such features in the future, we will update this Section and provide additional notice where required.

Fireworks AI's commitments are Fireworks AI's commitments — they govern Fireworks' processing, not mumo's storage, retention, or Platform Improvement practices, which are described separately in these Terms and our Privacy Policy.

We may modify, limit, or discontinue access to specific AI models, providers, or routing features in response to changes in provider policies, availability, or legal requirements.

10. Platform API keys and credentials

All third-party model calls are made using mumo-managed provider credentials unless we expressly support another method. mumo does not currently support bring-your-own provider keys (BYOK).

If you create a mumo API key, only a hashed form is retained server-side. We cannot retrieve or view the full key after it is first displayed.

mumo API keys and MCP credentials are sensitive credentials. You are responsible for securing them and for all activity under them. We may log credential identifiers, request metadata, model routes, consent-resolution values, and safety/security events for auditing, abuse prevention, billing, debugging, and compliance.

Usage may be subject to rate limits or feature gating described elsewhere in these Terms.

11. Shared conversations

When you generate a share link, anyone with that link may view the shared conversation content, including model responses, annotations, commentary, and steering decisions included in that shared view.

Shared conversations do not expose your Google password, mumo API key, or private account credentials. They may expose personal, confidential, proprietary, or sensitive content if you included that content in the session.

You are responsible for what you choose to share.

12. No professional advice

mumo does not provide medical, legal, financial, tax, investment, security, or other professional advice. AI-generated content may be inaccurate, incomplete, outdated, biased, or misleading. You are responsible for evaluating and verifying outputs before relying on them.

13. Availability and changes

mumo is provided on an "as is" and "as available" basis. We do not guarantee uptime, availability, model availability, uninterrupted service, response quality, latency, or continued access to any particular model, route, provider, feature, API, or MCP interface.

Third-party provider outages, rate limits, policy changes, safety systems, pricing changes, and legal requirements may affect mumo features.

We may modify, suspend, limit, or discontinue any part of mumo at any time.

14. Intellectual property

The mumo platform — including its software, design, branding, interface, workflows, documentation, and non-user content — is owned by Sourced LLC or its licensors. These Terms do not grant you rights to mumo intellectual property except the limited right to use mumo under these Terms.

15. Disclaimer of warranties

To the maximum extent permitted by law, mumo is provided "as is" and "as available," without warranties of any kind, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, non-infringement, availability, accuracy, security, or reliability.

16. Limitation of liability

To the maximum extent permitted by law, Sourced LLC and its officers, employees, contractors, agents, affiliates, and licensors will not be liable for:

  • the accuracy, completeness, usefulness, or reliability of AI-generated content;
  • decisions or actions taken based on AI-generated content;
  • unauthorized, unexpected, or undesired actions taken by agents operating under your credentials;
  • loss, disclosure, or corruption of data except to the extent liability cannot be excluded by law;
  • third-party model provider, inference provider, or infrastructure provider actions, outages, policy changes, suspensions, or processing;
  • indirect, incidental, special, consequential, exemplary, or punitive damages; or
  • lost profits, lost revenues, lost business opportunities, loss of goodwill, or business interruption.

17. Indemnification

You agree to indemnify and hold harmless Sourced LLC and its officers, employees, contractors, agents, affiliates, and licensors from claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys' fees) arising from:

  • your use of mumo;
  • User Content submitted through your account;
  • activity by agents, scripts, integrations, employees, contractors, or other automated systems operating under your credentials, including activity that violates third-party model provider, inference provider, or infrastructure provider terms;
  • your violation of these Terms;
  • your violation of applicable law or third-party rights; or
  • claims, suspensions, or terminations arising from activity traceable to your account or credentials.

18. Termination and deletion

You may delete your account at any time. We may suspend or terminate your access if you violate these Terms, create risk for mumo or its providers, or if we discontinue the service.

Upon account deletion, we will delete or de-identify account data and stored conversation data associated with your account within 30 days unless retention is required for law, security, abuse prevention, dispute resolution, backup integrity, provider compliance, or ordinary business records.

If a deleted session has linked analysis-feedback records that remain associated with that session, we will delete those linked records as part of the session deletion process. De-identified, aggregated, or account-separated Platform Improvement records that are no longer reasonably associated with your account or session may be retained unless applicable law or your plan-specific controls require deletion.

19. Dispute resolution

Any dispute arising out of or relating to these Terms or your use of mumo shall be resolved through binding arbitration on an individual basis, conducted in Florida under the rules of the American Arbitration Association.

You agree that disputes will not be resolved through class actions, consolidated actions, or representative actions. You waive any right to participate in a class action or jury trial relating to these Terms, to the maximum extent permitted by law.

20. Governing law

These Terms are governed by the laws of the State of Florida, without regard to conflict-of-law principles.

21. Changes to these Terms

We may update these Terms from time to time. Material changes will be communicated through the platform, email, or other reasonable means.

Material changes to model routing, provider architecture, or Platform Improvement data use may require renewed affirmative acceptance before further platform use.

If you do not agree to updated Terms, you should stop using mumo and delete your account.

22. Contact

Questions about these Terms? Contact us at support@mumo.chat.