Taicho legal
Core, conditional, and customer-selected providers that may process service data.
| Provider | Purpose | Data | Status / location |
|---|---|---|---|
| Infrastructure provider pending legal approval | Application and database hosting | Workspace and service data | Hosting location pending legal approval |
| Cloudflare R2 | Customer media staging and delivery | Files and object metadata | Enabled; region and contract pending approval |
| OpenRouter | Customer-directed model inference | Prompts and generated output | Enabled; provider routing terms pending approval |
| Datadog | Operational telemetry | Privacy-filtered metrics, logs, and traces | Conditional; not launch-configured |
| Langfuse | AI telemetry | Redacted AI usage and trace metadata | Conditional; not launch-configured |
| Qdrant | Assistant knowledge retrieval | Embeddings and tenant-scoped document metadata | Conditional; not launch-configured |
| OpenAI | Embeddings | Bounded text sent for embedding | Conditional; not launch-configured |
| Tavily | Customer-requested web research | Search queries and returned pages | Conditional; not launch-configured |
| Resend | Transactional and campaign email | Recipient, message, and delivery events | Conditional; not launch-configured |
A customer may direct Taicho to exchange data with CRM, social, publishing, calendar, CMS/MCP, storage, and communication providers. Those providers act under the customer's account and selection; their own terms and privacy notices apply.
The approved agreement must define advance notice, objection, replacement, and termination rights for new subprocessors. Until that mechanism and every provider region are approved, this notice remains a launch blocker.
Legal notices: Legal contact pending legal approval. Privacy requests: Privacy contact pending legal approval.
Operator: Legal entity pending legal approval, Registered address pending legal approval.