Subprocessor and Model Provider Policy

This policy explains how Boo uses subprocessors and model providers to provide the Services. It is part of the Master Subscription Agreement and Terms of Service.

Subprocessors

Subprocessors are third parties that process Customer Data or Customer Personal Data on Boo's behalf to provide the Services. Examples may include cloud infrastructure, database hosting, logging, monitoring, billing, support, analytics, messaging, and model providers.

Model providers

Model providers are third-party providers of foundation models, large language models, embedding models, reasoning models, speech models, image models, coding models, ranking models, or related AI infrastructure.

Provider commitments

Boo will require subprocessors and model providers that process Customer Data to protect Customer Data through confidentiality, security, and data protection obligations. Boo will require model providers not to use Customer Data to train their models unless Customer gives Explicit Approval, including through a Customer-Approved Provider Setting where available that is off by default.

Provider restrictions

Customer may restrict model providers through an Order Form or supported admin control where available. Restrictions may make some features unavailable and may affect quality, latency, cost, reliability, or supportability.

Public web retrieval and external sources

Boo may use public web retrieval providers, search tools, browser infrastructure, or external data sources when a task requires current or public information. Public web retrieval may involve sending search queries, URLs, page contents, or task context to retrieval providers or browser infrastructure as needed to complete the task. Public sources are not controlled by Boo and may be inaccurate, outdated, or subject to third-party rights.

Changes to providers

Boo may add or replace subprocessors and model providers to support, secure, maintain, improve, or provide the Services. Boo will provide notice through a trust page, email, admin console, or other reasonable method when required by the Agreement or applicable law.

Objections

Customer may object to a new subprocessor where required by law, the Agreement, or the applicable Order Form. Boo will use reasonable efforts to address the objection. If the objection cannot be resolved, Customer may stop using the affected feature or terminate the affected Order Form where required by law, the Agreement, or the applicable Order Form.

Emergency replacements

Boo may replace or add a provider without prior notice when necessary for security, availability, legal compliance, abuse prevention, or service continuity. Boo will provide notice as soon as commercially reasonable where required.

Provider categories

Boo currently uses providers in the following categories to deliver the Services:

• Cloud infrastructure: hosting, compute, storage, and networking
• Database and storage: product data, indexes, metadata, and logs
• Model providers: text, reasoning, code, embeddings, and multimodal inference
• Search and web retrieval: public web information when a task calls for it
• Billing: usage metering, invoicing, and payments
• Support and communications: customer support and operational notices
• Security and monitoring: logging, alerts, abuse detection, and incident response

Current production provider register

The following providers are currently in use to deliver the Services. Regions reflect the primary processing location.

Where a provider above is also available as a customer-connected integration (e.g. Slack, Linear), the subprocessor relationship covers Boo Lab's own operational use of that service. When a Customer connects the same service to Boo using the Customer's own credentials, the Customer authorizes Boo to access it on the Customer's behalf and that access is governed by the Customer's own agreement with the provider.