Sub-Processors
Msasa uses certain third-party service providers (“Sub-Processors”) to help us operate the Service, provide integrations, and deliver AI and workflow features. Depending on the features you enable (for example, connecting an integration or using AI features), these providers may process Customer Data on our behalf.
Last updated: March 2026
Infrastructure and application hosting
| Sub-Processor | Purpose | Data processed | Location |
|---|---|---|---|
| Supabase | Core application infrastructure, authentication, and data storage | Account information, workspace data, service metadata, and logs | United States |
| Google Cloud Platform | Cloud infrastructure and application services | Customer content and service metadata processed by enabled product features | United States |
Authentication
| Sub-Processor | Purpose | Data processed | Location |
|---|---|---|---|
| Supabase Auth | User sign-up, sign-in, session management | Email address, authentication credentials, and session data | United States |
Accounting and financial data
| Sub-Processor | Purpose | Data processed | Location |
|---|---|---|---|
| Xero | Accounting integration (reports, journals, contacts, invoices, budgets, bank transactions) | Accounting data you choose to sync through your Xero connection | As per Xero’s terms (varies by region) |
| Intuit QuickBooks | Accounting integration (reports, open invoices, general ledger, aged receivables/payables) | Accounting data you choose to sync through your QuickBooks connection | As per Intuit’s terms (varies by region) |
Used only when you connect and use Xero or QuickBooks.
CRM
| Sub-Processor | Purpose | Data processed | Location |
|---|---|---|---|
| Zoho Corporation (Zoho CRM) | CRM integration for workflow operations | CRM data you choose to sync through your Zoho connection | Depends on your Zoho region (e.g., US, EU, IN, AU, JP, CN) |
Used only when you connect and use Zoho CRM.
Productivity and collaboration
| Sub-Processor | Purpose | Data processed | Location |
|---|---|---|---|
| Google (Google Sheets / Drive) | Spreadsheet read/write and optional Drive access for workflows and AI tools | Spreadsheet content, file metadata, and related workflow data | As per Google Cloud/Workspace terms |
| Slack | Sending messages via webhooks you configure | Message content and delivery metadata for messages you send | As per Slack’s terms |
Google: used when you connect Google Sheets or use Sheets/AI tools. Slack: used when a workflow sends a message to a Slack webhook you provide.
AI and language models
| Sub-Processor | Purpose | Data processed | Location |
|---|---|---|---|
| OpenAI | AI models for the workflow Agent and related features | Customer content submitted to enabled AI features and resulting outputs | As per OpenAI’s terms |
| Google (Vertex AI / Gemini) | AI models for the Agent and Copilot | Customer content submitted to enabled AI features and resulting outputs | United States |
| Anthropic | AI models for the Agent | Customer content submitted to enabled AI features and resulting outputs | As per Anthropic’s terms |
Used when you use the workflow Agent, Copilot, or other AI features. The provider depends on the model you select.
Observability
| Sub-Processor | Purpose | Data processed | Location |
|---|---|---|---|
| LangChain (LangSmith) | Optional tracing and observability for agent runs | Operational metadata and, depending on configuration, limited feature data | As per LangSmith’s terms |
Observability tooling can be limited or disabled for certain environments or workflows.
Client-side only (not sub-processors)
Excel export: Export to Excel from workflows or dashboards is performed in your browser. No spreadsheet data is sent to a third-party server for export.
Updates
We may add or change Sub-Processors over time. We will update this page and, where required by law or contract, provide notice or obtain consent before a new Sub-Processor processes personal data.
For questions, or to request a data processing agreement, contact your Msasa account owner or legal contact.