Launch
Mar 31, 2026
umamimind.ai icon
Trust & Compliance

Subprocessors

Third-party transparency with risk-based governance and NDA-ready disclosures.

Purpose

This page provides transparency into third-party providers (subprocessors) used to support platform delivery and operations, governed through security, privacy, and contractual safeguards.

Governance

  • Security and privacy risk assessment prior to engagement
  • Contractual data protection and confidentiality obligations
  • Periodic review of subprocessor posture
  • Access limited to the minimum necessary

Categories and examples

UmamiMind can be deployed with different infrastructure choices. The table below lists common subprocessor categories and typical examples; the authoritative list for a specific deployment is provided during contracting and through the Trust Pack workflow.

Category
Typical examples
Purpose
Hosting / Delivery
Vercel or equivalent (deployment dependent)
Serve the web application
Database & Auth
Supabase or customer-provided Postgres (deployment dependent)
Identity, sessions, and application data
Object Storage
S3-compatible storage (deployment dependent)
Store exports and uploaded artifacts
Email
Customer SMTP / transactional provider (deployment dependent)
Send notifications and onboarding messages
Webhook Delivery
Svix (optional)
Reliable webhook delivery to customer endpoints

Subprocessor list availability

A detailed, current list for your specific deployment (including processing purpose and region) is available through the Trust Pack process under NDA where appropriate.

Pilot-stage notice

Subprocessor usage reflects pilot-stage operations and evolves toward General Availability.

PilotsDemoTour