Legal
Sub-processors
Last updated: 2026-08-27
This page lists the sub-processors Botyard ApS ("Botyard") engages to process Customer Data on behalf of customers in connection with the Service, as referenced in our Data Processing Agreement. This page is the authoritative, up-to-date sub-processor list for the purposes of that agreement — it supersedes any sub-processor list attached to a signed copy of the DPA unless that copy expressly states otherwise.
A machine-readable version of this list is available at /api/subprocessors, if you would like to monitor it programmatically instead of relying solely on email notice.
The location field describes the configured service or storage location relevant to Botyard's use. It does not, by itself, describe a provider's corporate jurisdiction, every location from which its personnel or sub-processors may process data, or the legal safeguard applicable to a particular transfer. The transfer-mechanism field identifies the contractual framework Botyard relies on where a restricted transfer occurs.
Current sub-processors
| Sub-processor | Purpose | Data categories | Location |
|---|---|---|---|
Hetzner Online GmbH / Hetzner Finland Oy Cloud infrastructure, primary database & object storage | Hosts the Service's compute, primary database (including customer-scoped embedding/search storage), and primary object storage | Customer Data submitted to or generated by the Service, including content, logs, metadata, backups, configuration data, and embeddings | Helsinki, Finland (EU) Transfer mechanism: None (EU-only) |
Microsoft (Azure OpenAI / Azure AI Foundry) AI / model provider | LLM inference, document processing, and workflow assistance underlying the Service's AI agent capabilities | Prompts, inputs, outputs, and context submitted to AI agents, including documents or extracted text where enabled | Global processing; the current model deployment uses Azure's Global Standard deployment type Transfer mechanism: Microsoft Products and Services Data Protection Addendum, including the 2021 Standard Contractual Clauses for transfers requiring safeguards |
Microsoft (Azure Blob Storage) Encrypted off-site database backup | Stores encrypted base backups and write-ahead logs of the Service's primary database for disaster recovery | Full encrypted copies of Customer Data held in the primary database | Sweden Central (EU) storage region Transfer mechanism: Microsoft Products and Services Data Protection Addendum, including the 2021 Standard Contractual Clauses for transfers requiring safeguards |
Google (Gemini API) Embedding model provider | Generates customer-scoped embeddings used for search and retrieval within the Service | Text chunks or conversation content used to generate embeddings | Global processing through the Gemini API; no EU-only endpoint is configured Transfer mechanism: Google Data Processing Addendum, including the 2021 Standard Contractual Clauses for transfers requiring safeguards |
Cloudflare, Inc. (R2 object storage) Object storage for uploads and short-lived scratch data | Stores file/attachment uploads submitted via the Service, and short-lived extracted web page content generated by agent tooling | Uploaded files and attachments; short-lived extracted web page content | Global; configured with an Eastern Europe best-effort location hint (not an EU jurisdiction restriction) Transfer mechanism: EU-U.S. Data Privacy Framework and, where required, Standard Contractual Clauses |
Cloudflare, Inc. (network, CDN & tunnel) CDN, DNS, and outbound tunnel connectivity | Terminates TLS at Cloudflare's edge and routes and proxies inbound traffic to the Service's origin infrastructure | Connection metadata and request/response content transmitted through the Service | Global network Transfer mechanism: EU-U.S. Data Privacy Framework and, where required, Standard Contractual Clauses |
PostHog EU Platform analytics & session tracking | Product analytics, usage diagnostics, and aggregate usage reporting for the Service | User/session identifiers, device/browser metadata, feature interaction events, and timestamps; not used for application-log storage or model training | Germany (EU data center); supporting processing may occur in other locations identified by PostHog Transfer mechanism: PostHog Data Processing Agreement, including the 2021 Standard Contractual Clauses for transfers requiring safeguards |
Plus Five Five, Inc. (Resend) Transactional & inbound email delivery | Delivers account, security, and product email notifications, and receives inbound email sent to Botyard-hosted bot addresses | Notification content, sender/recipient email addresses, delivery logs, webhook payloads, and inbound email content and attachments where applicable | United States Transfer mechanism: EU-U.S. Data Privacy Framework and, where required, Standard Contractual Clauses |
Not yet active
The following are disclosed for transparency but are not currently processing Customer Data. Before one begins processing Customer Data, it will be moved into the active table above and notice will be given in accordance with the DPA's sub-processor notice provision.
OpenRouter Model routing (managed credits) | Not currently active — feature-gated off pending launch. When enabled, would route certain customer AI requests to third-party model providers via OpenRouter. |
Change log
We notify customers of new or replacement sub-processors at least 30 days in advance where reasonably practicable, in accordance with the DPA. This log records every change to the list above.
- 2026-08-27Initial publication of the sub-processor list, cross-checked against production infrastructure and vendor documentation.
Questions about a sub-processor?
If you'd like more detail on any sub-processor above, or want to object to a newly added one under the DPA, contact our legal team.
[email protected] →