Sub-processors
Who takes part in running Deutsche Cloud, what each receives, where; Hetzner’s certificates.
What it is
The companies other than Deutsche Cloud that take part in running the platform, what each one receives, and where. Deutsche Cloud is operated by DeutschlandGPT GmbH, Germering, Germany. When you store personal data on Deutsche Cloud, DeutschlandGPT GmbH processes it on your behalf (Art. 28 GDPR), and the companies in the first table are its sub-processors.
This page describes the platform as it runs. It is not itself a contract: the binding list is the annex of the data processing agreement (DPA, German: AVV) you sign with us. To request the DPA, write to info@deutschlandgpt.de.
Last reviewed: 13 November 2026.
Concepts
| Term | Meaning |
|---|---|
| Sub-processor | A company that processes personal data you store on Deutsche Cloud, on our instructions, to deliver the service. |
| Service provider | A company involved in running the platform that does not receive the personal data you store with us (for example, DNS for our own hosts). |
| Your integration | A service you connect yourself (your identity provider, GitHub, an audit log destination). You choose it and it is not our sub-processor. |
Region de1 |
The region every resource is created in: zone de1a is Hetzner's Falkenstein site, zone de1b is Hetzner's Nuremberg site, both in Germany. |
Sub-processors
| Sub-processor | What it does for Deutsche Cloud | Data it receives | Where |
|---|---|---|---|
| Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany | Data centres, physical servers, virtual machines, block volumes, networks, load balancers and the object storage behind Deutsche Cloud buckets, backups and registries | Everything you store on Deutsche Cloud, as stored on its hardware. Disks of managed databases, caches and (by default) volumes are encrypted before they reach it. | Falkenstein and Nuremberg, Germany. Helsinki, Finland only in the cases listed under Data location. |
| Amazon Web Services EMEA SARL, Luxembourg (Amazon Simple Email Service) | Delivers the e-mails Deutsche Cloud itself sends you: sign-up and sign-in codes, password resets, invitations, alarms and notices | Recipient name and e-mail address, and the content of that e-mail | AWS region eu-central-1 (Frankfurt, Germany). The parent company is in the USA; see Transfers outside the EU. |
DeutschlandGPT model API (api.deutschlandgpt.de), operated by DeutschlandGPT GmbH |
Answers questions typed into the console assistant, with one of DeutschlandGPT's standard models. Which models it can reach is set on Deutsche Cloud's API key; of those, Deutsche Cloud offers only chat models the API reports as hosted in Germany or the EU, and your organization picks one under Account → AI settings (default Auto: the model DeutschlandGPT marks as recommended). No other model is used | What you type, the console page you are on, your organization name and IAM user name, and the resource data the assistant reads when it is allowed to | Germany or the EU, as DeutschlandGPT's API reports for each model; the settings page names the region of each, and the DPA annex names the providers that run them. Only used when someone in your organization opens the assistant and sends a message, and never when your organization has switched the assistant off. |
Provider of the model you call through the model API (/ai/v1) |
Runs the model a request names: Mistral AI, IONOS, STACKIT, Scaleway or another provider the installation offers | The request body (prompt, images, parameters) and the answer. Never your organization name, IAM user or access key: the provider sees Deutsche Cloud as its customer | Per model, in GET /ai/v1/models and the console: a residency label (eu, eu-processed, non-eu) and a location. Only eu models are usable until an administrator allows more; see AI models. |
E-mail that you send with the Deutsche Cloud Email product is not sent through Amazon SES. It leaves through mail relays Deutsche Cloud runs itself on Hetzner machines in Germany and goes to the recipients' mail servers.
Other service providers
These providers are involved in running the platform but do not receive the content you store.
| Provider | Purpose | What it receives |
|---|---|---|
| Let's Encrypt (Internet Security Research Group, USA) | TLS certificates for the console and for your apps' domains | The domain names to certify. Certificates are published in public Certificate Transparency logs. |
| Amazon Route 53 | DNS for the platform's own host names | DNS lookups of platform host names. Your hosted zones are served by Deutsche Cloud's own nameservers. |
| European Commission (VIES) | Validates the VAT ID you enter | Your VAT ID, at sign-up and when billing details change |
| GitHub (GitHub, Inc., USA) | Hosts Deutsche Cloud's own source code and runs the jobs that build and install new platform releases | Deutsche Cloud source code. Release jobs connect to the control plane hosts to install a release. |
| 1Password (AgileBits Inc., Canada) | Holds Deutsche Cloud's platform credentials, which are loaded when the control plane starts | Platform credentials and keys. No customer content. |
Invoices are paid by bank transfer. No payment processor receives card data.
Your integrations
Services you connect yourself are processed under your own agreement with that provider:
- an OIDC or SAML identity provider for single sign-on;
- GitHub, when you import a repository or let GitHub Actions sign in with OIDC;
- 1Password, when you sync secrets from it;
- audit log destinations: your bucket, webhook, syslog server or alarm e-mail addresses;
- the servers your apps, functions, webhooks and event rules call.
Hetzner's certificates
Hetzner Online GmbH operates the data centres and the infrastructure layer. Its attestations cover that layer, not Deutsche Cloud's own software and operation (see Compliance for Deutsche Cloud's own status).
| Attestation | Issued by | Scope | Period / date |
|---|---|---|---|
| ISO/IEC 27001:2022 certificate | SOCOTEC Certification | The infrastructure, operation and customer support of Hetzner's data centre parks in Nuremberg, Falkenstein and Helsinki | See the certificate |
| BSI C5:2020 Type 2 attestation | WP Koehler GmbH Wirtschaftsprüfungsgesellschaft (ISAE 3000) | Dedicated and managed servers; cloud (virtual servers, volumes, load balancers, networks, floating IPs); storage including object storage; colocation. Hetzner's European sites in Gunzenhausen, Nuremberg, Falkenstein and Helsinki | Audit period 1 February to 31 August 2025, report of 17 November 2025 |
| Audit of technical and organisational measures | TÜV Rheinland | Hetzner's TOMs as a processor | Regular; the protocol is available to Hetzner's DPA customers |
Sources: Hetzner, Information security at Hetzner, ISO certificate, C5 attestation.
Data location
Germany by default. Every resource you create is in region de1: Falkenstein (de1a, the
default) or Nuremberg (de1b), Germany, unless your organization decides otherwise as described
below. This covers instances, volumes and their snapshots, managed PostgreSQL and its backups,
Valkey, Kubernetes clusters, file storage, load balancers, VPN, NAT, buckets, CI runners, and the
storage behind Git, the container and npm registries.
Other EU locations only on purpose. Region fi1 (Helsinki, Finland, EU) is available only when
both are true:
- an administrator of your organization has turned on Allow EU locations outside Germany
(Settings → Data location;
PUT /settings/api/organization/data-location, recorded in your audit log), and - someone places a resource there explicitly, by choosing that location for it.
| Service | How Helsinki is chosen |
|---|---|
| Apps | locations: ["hel1"]; an app's locations are all in one region, never mixed |
| Buckets | zone fi1a when the bucket is created; replication into it from Germany also needs the setting |
| Instances, volumes, networks (VPC), elastic IPs, key pairs | regionId: "fi1" (zone fi1a) |
| Load balancers | regionId: "fi1"; a balancer targets machines of its own region only |
| Managed PostgreSQL | regionId: "fi1"; its machines, disks and backups (pgBackRest, bucket in fi1a) stay there |
| MySQL, Valkey caches | regionId: "fi1"; machines and disks there, snapshots stored in Germany (see below) |
| Kubernetes | regionId: "fi1" on the cluster; node groups, volumes and balancers follow the cluster |
| File storage | regionId: "fi1" (zone fi1a); its machine, disk and snapshots stay there |
| Client VPN and site-to-site VPN gateways | regionId: "fi1"; the gateway machines and their public address are there |
| Auto scaling groups | regionId: "fi1" on the launch template and the group |
| Functions | the X-EWS-Region: fi1 header; they run on Deutsche Cloud function hosts in Helsinki |
| API in general | the X-EWS-Region: fi1 header (CLI --region fi1, SDK/Terraform region) |
Snapshots of a Valkey cache or a MySQL cluster in fi1 are stored in the platform's object
storage in Germany (encrypted per snapshot): data of an opted-in resource can move from Finland
into Germany, never from Germany into Finland. Highly available databases, caches and VPN gateways
in fi1 run on separate physical hosts in the one Helsinki zone: they survive a host failure, not
the loss of the site.
Every other regional service (queues, events, schedules, email, sandboxes) creates its resources
in Germany only and refuses fi1 with a 400 naming what is offered there. Without the setting,
every service answers 403 "outside Germany" before anything is ordered; an unknown region is a
400, never a silent fallback. A
resource and everything it attaches to (volumes, targets, subnets) stay in one region. Turning the
setting off moves nothing: resources already in Helsinki stay there and can still be used and
deleted, and nothing new is placed there. Prices in Helsinki are the same as in Germany.
Never outside the EU, never across a border by itself.
- Locations outside the EU (Hetzner's US and Singapore locations) are offered nowhere and refused everywhere.
- Nothing is moved to another country because a location has no capacity. For example, functions
run on Deutsche Cloud-managed hosts in their region (Falkenstein or Nuremberg for
de1, Helsinki forfi1), and when Hetzner has no capacity there, Deutsche Cloud waits for capacity. - Every machine, volume, address and load balancer Deutsche Cloud orders from Hetzner is checked just before the order is sent. Without your opt-in and an explicit choice, the check allows only Falkenstein and Nuremberg; with them, it adds Helsinki; it never allows anything else.
The control plane (console, API, IAM, audit log, billing) and its database run on machines in Falkenstein and Nuremberg.
- The one Deutsche Cloud machine outside Germany is an uptime probe in Helsinki (Finland, EU). It requests the public URLs you ask Deutsche Cloud to monitor and records the response time and status; it stores none of your data.
Transfers outside the EU
The resources you create, and their backups, are stored in the EU (see above). Providers that belong to companies outside the EU:
- Amazon SES processes e-mail in Frankfurt. Amazon Web Services EMEA SARL is a Luxembourg company with a US parent.
- Let's Encrypt and GitHub are US companies; 1Password is a Canadian company. None of them receives the content you store.
- The console assistant calls DeutschlandGPT's model API. The models it can reach are set on the
platform's API key; of those, Deutsche Cloud lists only chat models the API reports as hosted in Germany or
the EU, and your organization chooses one (or Auto, the API's recommended model). The settings
page and
dcloud ai settings getshow which model is in use. The DPA annex names the provider behind each model.
The transfer basis for each of them is set out in the DPA annex.
Changes to this list
The DPA sets how a new sub-processor is announced and how you can object to it. This page is updated at the same time.