# Subprocessors

> The third parties MTDT engages to process personal data on behalf of its customers, their processing locations, and how MTDT notifies customers of changes.

# Subprocessors

**Last updated: 25 August 2026**

**Download:** [Markdown](https://docs.mtdt.io/legal-information/subprocessors.md)

This page lists the third parties that MTDT engages to process personal data on behalf of its
customers. It is the page referred to in Section 4.1 and Appendix 5 of the MTDT Data
Processing Agreement (DPA), and changes to the lists below are published here.

A **subprocessor** is a third party engaged by MTDT that processes personal data contained in
customer data in the course of providing the Services. Vendors that do not process customer
personal data — for example tools used only for internal accounting or for our own website —
are not listed here.

## Infrastructure and platform subprocessors

| Entity | Service | Personal data involved | Location |
|---|---|---|---|
| Hetzner Online GmbH | Infrastructure hosting for the Services | All personal data processed in the provision of the Services | Falkenstein, Germany |
| Better Stack, Inc. | Aggregation of application and infrastructure logs | Operational telemetry, containing pseudonymous identifiers of users, teams and connected organizations | Log data is held in the European Union; the provider is established in the United States |
| Propeller Plan Sp. z o.o. | Development and technical support of the Services | All personal data processed in the provision of the Services, accessed as required for support and maintenance | Poznań, Poland |
| Slack Technologies | Operational alerting | Operational telemetry, as above | United States |
| Amazon Web Services | Delivery of transactional email to users | Recipient email address and the content of the notification | United States |
| Stripe | Billing and subscription management | Email address and an MTDT-internal user identifier. Name, billing address and tax identifier, where collected, are provided by the payer directly to Stripe and are not stored by MTDT | United States |

All processing of customer data in the provision of the Services takes place on infrastructure
located in Germany. The subprocessors listed above with a location outside the EEA receive
only the categories of data described in the corresponding row.

## AI-assisted feature subprocessors

The AI-assisted features of the Services are described in Appendix 5 of the DPA. They are
optional, and where a feature is not enabled no data is submitted to any AI service for that
feature.

The features are served by services that MTDT operates. Because MTDT operates them they are
not subprocessors. Where such a service uses a third-party model provider on MTDT's behalf,
that provider is a subprocessor:

| Entity | Service | Personal data involved | Location |
|---|---|---|---|
| Google LLC | Language model inference (Gemini), used for deployment description generation | Deployment and organization identifiers, and the metadata differences of the components the customer selected, as described in Appendix 5 Section 2 of the DPA | United States |

Deployment descriptions are generated only when a user explicitly requests one for a
particular deployment. Nothing is sent to the model provider automatically, and no data is
sent for a deployment where no user has asked for a description.

This is the only model provider MTDT currently engages. Engaging an additional provider, or
using the provider above for a further feature that submits new categories of personal data,
is a change subject to the 30-day notice and objection mechanism described below.

Where a customer supplies its own model provider credentials, the provider that customer
designates is not an MTDT subprocessor. Appendix 5 Section 3.2 of the DPA sets out how that
arrangement works.

## What is not a subprocessor

**Destinations the customer configures.** Where a customer configures the Services to write to
object storage or to a database that the customer controls — for example an Amazon S3 bucket
or an Azure Blob Storage container under the customer's own account — MTDT does not select or
control that destination and it is not an MTDT subprocessor. The same applies to the
Salesforce orgs, Git providers and issue trackers that the customer connects.

**Services MTDT operates.** Services that MTDT runs on its own infrastructure are not
subprocessors. The infrastructure they run on is, and is listed above.

## How we notify you of changes

At least 30 days before engaging a new subprocessor, MTDT will inform customers by email or by
publishing the change on this page. Where a customer has a legitimate objection under data
protection law to a new subprocessor, the objection and termination mechanism in Section 4.1
of the DPA applies.

MTDT may replace a subprocessor without prior notice where the replacement is reasonably
necessary for urgent operational or security reasons, and will publish the change here
promptly afterwards.

Removing a subprocessor, narrowing the data a subprocessor receives, or recording a change of
name is published here without advance notice.

## Change log

| Date | Change |
|---|---|
| 1 April 2025 | Subprocessor list effective from this date. |
| 24 August 2026 | Removed Resend, previously listed as a fallback provider for transactional email. Transactional email is delivered by Amazon Web Services. |
| 25 August 2026 | Added Propeller Plan Sp. z o.o., which develops and supports the Services from Poland. Corrected the location of Better Stack: log data is held in the European Union. |

## Contact

Questions about this page, or an objection to a subprocessor, can be sent to
mtdt@mtdt.io.