Subprocessors
Last updated: 2026
UmamiMind may use third-party subprocessors to support delivery of the Mission Control service. Subprocessors are engaged under contractual confidentiality and data protection obligations. The list below describes common subprocessors and categories used in typical deployments. Specific deployments may differ based on customer configuration and region.
| Subprocessor | Purpose | Location | Data Categories |
|---|---|---|---|
| Supabase | Database, authentication, and storage for Mission Control environments. | Varies by region selected by Customer | Account data, workspace metadata, customer content (as configured). |
| Cloud infrastructure provider | Compute, networking, and hosting for the Service. | Varies by deployment region | Service telemetry, logs, and encrypted customer content in transit. |
| AI model provider(s) | LLM inference used to generate outputs requested by Customer. | Varies by provider and region | Prompts and relevant context required to fulfill the request (subject to org policy). |
Notes
- Customer administrators can configure governance controls (model allowlists, budgets, retention) that affect what data is processed and where.
- For enterprise customers, UmamiMind can provide deployment-specific documentation and a customized subprocessor list upon request.
Contact
Questions about subprocessors may be directed to:
privacy@umamimind.ai