Compliance overview

Data location, certificates, the DPA, evidence for audits, leaving Deutsche Cloud.

What it is

What you need from Deutsche Cloud for your own compliance work: where your data is, who processes it, which measures protect it, which certificates apply, and which contract documents exist. Start here when your data protection officer, your auditor or a customer's procurement team asks about Deutsche Cloud.

Last reviewed: 13 November 2026.

Concepts

Term Meaning
Controller You, for the personal data you store or process on Deutsche Cloud (Art. 4(7) GDPR).
Processor DeutschlandGPT GmbH, which operates Deutsche Cloud and processes that data on your behalf (Art. 28 GDPR).
DPA / AVV The data processing agreement (Auftragsverarbeitungsvertrag) between you and DeutschlandGPT GmbH. It binds the TOMs and the sub-processor list.
TOMs The technical and organisational measures of Art. 32 GDPR.
Inherited control A control that Hetzner, as the data-centre operator, implements and evidences with its own certificate.

Documents

Document What it answers
Sub-processors Which companies take part, what each receives, where; Hetzner's certificates; data location
Technical and organisational measures The Art. 32 measures, what you configure yourself, and what is not covered
Security whitepaper Architecture, shared responsibility, identity, data protection, network and operations
Data processing agreement (AVV, German, with English translation) Request it at info@deutschlandgpt.de
Audit log What is recorded, how to verify the hash chain, how to export it

The pages above describe the platform. The DPA is the contract: its annexes take the TOMs and the sub-processor list as of the date you sign.

Where your data is

  • By default every resource is created in region de1: Falkenstein (de1a) or Nuremberg (de1b), Germany, in Hetzner's data centres. Backups stay in the same region.
  • Other EU locations (Helsinki, Finland: region fi1) are used only if your organization turns on Allow EU locations outside Germany and someone places a resource there on purpose. Today that applies to apps, buckets (zone fi1a), instances, volumes, networks, elastic IPs, load balancers, managed PostgreSQL, MySQL, Valkey caches, Kubernetes clusters, functions, auto scaling groups, file storage and VPN gateways (region fi1). The console marks every such resource and choice "outside Germany". Snapshots of a Valkey cache or MySQL cluster in fi1 are stored in Germany.
  • Locations outside the EU are never offered. Nothing moves to another country by itself, for example when a location has no capacity.
  • The control plane and its database run in Falkenstein and Nuremberg.

Details: Data location.

Certifications

Deutsche Cloud holds no certificate or attestation of its own yet.

The data-centre and infrastructure layer is operated by Hetzner Online GmbH, which holds an ISO/IEC 27001:2022 certificate and a BSI C5:2020 Type 2 attestation covering its cloud servers, volumes, networks, load balancers and object storage in Falkenstein, Nuremberg and Helsinki. The physical and environmental controls of ISO/IEC 27001 Annex A (section 7) are inherited from Hetzner. See Hetzner's certificates.

How to

Collect evidence for an audit

  • Who can do what: IAM users, groups, roles and attached policies, over the console (IAM) or the API.
  • What happened: the audit log, exported as JSON lines or CSV, or streamed to your own bucket. Check its integrity with the verification described in Audit log.
  • Encryption: the API reports whether each volume, database, cache and bucket is encrypted and under which key; a database's detail page shows it in the console.
  • Backups: each database shows its retention and restorable window.

Give an auditor read-only access

Create an IAM user for the auditor and attach the ReadOnlyAccess policy (the ReadOnly role). It can read every service's configuration and the audit log, but not secret values or source code.

Leave Deutsche Cloud

Your data leaves through each service's own interface: git clone, registry pulls, pg_dump or the database's connection, the S3 API for buckets, zone export for DNS.

To close the organization, delete your resources and then request closure under Settings → Danger zone (see Billing). Closure waits 30 days, and is refused while anything still runs or stores data in any service; the check lists each one. Closing the organization suspends its members and stops its keys. 30 days after closure everything left (IAM, settings, monitoring history, CI and Git leftovers, the audit log) is deleted, except the invoices and billing account, kept for the statutory ten years. Details: What happens to your data after closure.

Each person deletes their own login under My account → Danger zone (GDPR Art. 17): the account is locked at once, restorable for 30 days from the mailed link, then purged; the person can purge it at once from the same link. An empty organization they alone own closes with it. Invoices and each organization's audit entries naming them are kept (ten years; the organization's audit retention). Details: Deleting your account.

What is not supported

  • A Deutsche Cloud certificate (ISO/IEC 27001, BSI C5) of its own.
  • Moving resources back to Germany: with Allow EU locations outside Germany off (the default), nothing new is placed outside Germany, but a resource created in Helsinki while it was on stays there until you delete it.
  • A single export of everything in an organization.
  • A dedicated auditor role or an access-review workflow.
  • A compliance posture view in the console.
Did this page help you?