Legal

Sub-processors

Who else touches workspace data when you run Musaid, and why.

Infrastructure

  • Railway — Hosts the Musaid agent services, dashboard, website and our self-hosted monitoring. Region: US West.
  • Render — Hosts the Musaid agent, dashboard backend, and encrypted credential vault. Region: Oregon, US.
  • Supabase — Dashboard authentication and workspace/account data (managed Postgres). Region: ap-southeast-2 (Australia).

Business tools

  • Zoho (CRM and SalesIQ) — Customer records for account management and support (workspace, plan and usage summaries — never message content), plus website visitor analytics and live chat on musaid.xyz.
  • Google Analytics — Website and dashboard usage statistics (pages, clicks, sign-up funnel). Cookies only after you accept on musaid.xyz; the dashboard is cookieless. Never message content.
  • Microsoft Clarity — Session recordings and heatmaps on musaid.xyz, loaded only after you accept analytics. Form fields are masked.
  • Loops — Account and billing emails (welcome, trial, Dinar and receipt notices). Receives your name and email address only.
  • PayPal — Payments and subscriptions. Musaid never sees or stores card details.

AI model provider

Musaid is model-agnostic: the workspace admin sets which AI provider it calls (OpenAI, Anthropic, Google, Groq, Azure, or any of 46 supported backends, including self-hosted/local models that send nothing to a third party). Only the messages and files relevant to a given request are sent to that provider — see Privacy. None of these providers train on your data through Musaid.

Connected apps

If a workspace connects a third-party app (Notion, HubSpot, Gmail, etc.) through Pipedream Connect or Composio, that provider stores and signs on behalf of the account the person who connected it — Musaid never sees the password or token. See Product for how connectors work.