Skip to content

Legal

Subprocessors

Last updated 24 September 2026

This document is a working draft published for transparency about how the product is built. It has not completed legal review and is not a contract. The executed agreement for your account is the one you sign.

How this list works

These are the categories of provider the product depends on to operate. The current named list, with regions and functions, is provided under the agreement and updated with notice before any addition.

Cloud infrastructure

Compute, storage, content delivery and backup for the product and the agent runtime, in the region set for your account.

Model providers

Large language model providers, routed per task and per the model choice configured on each agent. Which provider handles which task is a platform decision and is not exposed as a per-request cost to you.

Providers are engaged under terms that prohibit training on account content. Categories you mark sensitive are excluded from model requests by default. Where your plan allows you to supply your own provider, that provider is yours rather than ours and is governed by your agreement with them.

Operational services

Transactional email delivery, error monitoring and product analytics for the application. None of these run on this marketing website.

Payments

A payment processor for subscription and usage billing. Card details are held by the processor and never by us.

Message delivery

Where you do not connect your own mailbox, an email delivery provider for sending from your domain. Message content passes through it in the ordinary course of delivery.

Give AI a job.

Build an agent, choose what it can access, define what it may do, and deploy it to work safely across your business.

No code required · Full SDKs and API · Stop any agent instantly · [email protected]