T Cloud Public
Cloud infrastructure · t-cloud-public.com · last read 2026-11-16
At a glance
- Is T Cloud Public GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what T Cloud Public itself publishes, each answer linked to its source and the date we read it.
- Does T Cloud Public have a data processing agreement (DPA)?
- Yes. T Cloud Public publishes a data processing agreement at t-cloud-public.com. It gives between 28 and 42 days' notice before a new subprocessor is added, depending on the case; the terms tab gives each. It promises breach notification "without undue delay", with no number of hours. Source and date
- Which version of the T Cloud Public DPA is current?
- On 2026-11-09, T Cloud Public's DPA at t-cloud-public.com printed “Last revised: April 2026”. Source and date
- Does T Cloud Public have a SOC 2 report?
- T Cloud Public states SOC 2 (no type given) on its own page, but does not say there how to get a report. We read this on 2026-10-08. Source and date
- Is T Cloud Public ISO 27001 certified?
- T Cloud Public states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-10-08. Source and date
- How does T Cloud Public transfer personal data out of the EU?
- We found no entry for T Cloud Public on the official Data Privacy Framework List. Source and date
- Does T Cloud Public offer EU data residency?
- The vendor documents an EU region but states nothing about which plan reaches it or what it costs. Source and date
- Who are T Cloud Public's subprocessors?
- T Cloud Public lists 3 third-party subprocessors; 0 of them name at least one processing country outside the EEA. We last read the list on 2026-10-08. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | T-Systems International GmbH |
|---|---|
| HQ | DE |
| Parent company | DEUTSCHE TELEKOM AG |
| Ultimate ownership | DE |
| EU contracting entity | — |
| LEI | 5299004XPX8GS3AHAV34 |
| US CLOUD Act reach | No US company in the ownership chain on record |
| Source | t-cloud-public.com · 2026-10-08 |
Legal entity from the vendor's own terms. LEI, registered country and parent company from the Global LEI Index (GLEIF); ownership is left empty where GLEIF names no parent. The CLOUD Act row is arithmetic over those countries, not an assessment of risk.
T Cloud Public data residency
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | Terms not stated | — | t-cloud-public.com | 2026-10-08 |
EU: The document lists T Cloud Public data centers in Germany and the Netherlands and mentions "GDPR-compliant data storage in Europe". It names no plan and no cost for using these locations.
The same question for every vendor: where SaaS vendors store EU data.
Other European cloud providers, their registers and certifications: sovereign clouds.
Subprocessor chain
3 third parties · 9 of the vendor's own group companies · 0 with a country outside the EEA · all read 2026-10-08
| Subprocessor | Country | Purpose |
|---|---|---|
| iits-consulting GmbH | DE | Consulting |
| operational services GmbH & Co. KG | DE | IT service provider |
| SC Combridge S.R.L | RO | Cloud provider |
T Cloud Public's own group companies listed as subprocessors (9)
| Company | Country | Purpose |
|---|---|---|
| Deutsche Telekom Individual Solutions & ProductsGmbH | DE, NL | 1st level & level 1.5 support, hardware maintenance and setup |
| Deutsche Telekom IT GmbH | DE | MyWorkplace |
| Deutsche Telekom MMS GmbH | DE | IT service provider |
| Deutsche Telekom Security GmbH | DE | IT service provider |
| Deutsche Telekom Systems Solutions Slovakia s.r.o. | SK | Cloud provider |
| Deutsche Telekom TSI Hungary Kft. | HU | Operation, 2ndlevel support |
| T-Systems Client Services GmbH | DE | Service Desk (1st Level Support) |
| T-Systems ITC Iberia, S.A. | ES | Operation, 2ndLevel Support |
| T-Systems on site services GmbH | DE | Development services |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
From the vendor's data processing agreement · read 2026-10-09 · t-cloud-public.com
| Term | What the agreement says |
|---|---|
| Transfer mechanism | other |
| Notice of new subprocessors | At least four weeks in advance, express written notice to the controller of intended additions or replacements to the agreed subprocessor list |
| Notice of new subprocessors | Six weeks in advance, in writing, with information needed to exercise the right to object |
| If you object to one | Controller may object to the changes before the subprocessor is engaged; processor must provide the information needed to exercise the objection right |
| If you object to one | Object in writing within four weeks (otherwise deemed approved; not unreasonably); if the objection makes service impossible, customer may terminate affected services without notice within one month of notification; transition phase up to six months during which the new subprocessor is not used for the customer's data |
| Obligations passed to subprocessors | contract imposing on the subprocessor substantially the same data protection obligations as apply to the processor under these clauses |
| Breach notification | without undue delay after becoming aware of the breach |
| Deletion when the service ends | On termination, at the controller's choice, erase all personal data and certify the erasure, unless EU or member state law requires retention; the clauses continue to apply until erasure |
| Getting your data back | On termination, at the controller's choice, return all personal data and erase existing copies, unless EU or member state law requires retention |
| Requests from data subjects | Informs the controller without undue delay of any request received from a data subject and does not answer it unless authorised by the controller; assists the controller in responding to data subject rights requests, following the controller's instructions |
| Audit | Non-event-driven on-site inspections may be replaced by documents, evidence, certifications or audits; must be announced in advance in a timely manner, avoiding business disruption; inspectors bound to confidentiality and may not be competitor representatives |
| Audit | Processor provides compliance information; on controller's request, permits and contributes to audits at reasonable intervals or when there are indications of non-compliance; controller may consider processor's certifications |
| Audit | Processor provides information to demonstrate compliance and permits audits at reasonable intervals or when there are indications of non-compliance. Audits by the controller or an independent auditor, and may include inspections of premises with reasonable advance notice. The controller may consider the processor's certifications. |
| Audit | Telekom may prove compliance (per item 3.2) by evidence: Art. 40 GDPR codes of conduct, Art. 42 certification, current certificates/reports or report excerpts from independent bodies (e.g., auditors), other suitable certification, or a processor affidavit |
| Audit | routine on-site inspections twice per calendar year, announced in advance; event-driven inspections unaffected; customer to first consider whether documents, evidence, certifications or audits can replace them; inspectors bound to confidentiality and may not represent competitors of Telekom |
| Processing on your instructions | only on the controller's documented instructions, unless EU or member state law requires otherwise (controller notified beforehand where permitted) |
| Confidentiality of staff | authorised persons committed to confidentiality or under a statutory obligation of confidentiality |
| Security measures | at least the technical and organisational measures listed in Appendix III |
Terms as the agreement states them. Where it is silent on a term, there is no row; that is not a statement that the vendor does not offer it.
Which version applies
On 2026-11-09, the agreement printed: Last revised: April 2026
at t-cloud-public.com
Last updated 2026-04
This version is in our copies from 2026-10-09.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
Does T Cloud Public have a SOC 2 report?
T Cloud Public states SOC 2 (no type given) on its own page, but does not say there how to get a report. We read this on 2026-10-08.
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
Is T Cloud Public ISO 27001 certified?
T Cloud Public states ISO/IEC 27001 on its own page, but does not say there how to get the certificate. We read this on 2026-10-08.
On the same list T Cloud Public also names ISO/IEC 27017 and ISO/IEC 27018. Each standard's page says how it relates to ISO/IEC 27001.
Of the 122 vendors in this registry whose own pages state ISO/IEC 27001, 16 link to the certificate, 43 say it is available on request, and 63 state it without saying how to get it. A certificate names the certification body, the scope and the expiry date: those are the three things to check.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| BSI C5 (Typ 2) · C5 | Claimed | T Cloud Public | t-cloud-public.com | 2026-10-08 |
| ISO 22301 · ISO22301 | Claimed | T Cloud Public; business continuity management | t-cloud-public.com | 2026-10-08 |
| ISO 27001 · ISO27001 | Claimed | T Cloud Public | t-cloud-public.com | 2026-10-08 |
| ISO 27017 · ISO27017 | Claimed | T Cloud Public; cloud-specific security measures | t-cloud-public.com | 2026-10-08 |
| ISO 27018 · ISO27018 | Claimed | T Cloud Public | t-cloud-public.com | 2026-10-08 |
| ISO 9001 · ISO9001 | Claimed | T Cloud Public; standardized quality management | t-cloud-public.com | 2026-10-08 |
| Trusted Cloud data protection profile | Claimed | T Cloud Public | t-cloud-public.com | 2026-10-08 |
| SOC 2 · SOC2 | Claimed | T Cloud Public | t-cloud-public.com | 2026-10-08 |
| TISAX | Claimed | T Cloud Public | t-cloud-public.com | 2026-10-08 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
| Register | Offering, as the register names it | Status | Level | Valid until | Observed |
|---|---|---|---|---|---|
| ENS certificates of conformity (CCN, Spain) | Los sistemas de información que soportan los procesos y servicios contemplados en el anexo. The information systems supporting the processes and services referred to in the Annex. ANEXO (página 1/1): Los sistemas de información que soportan los procesos y servicios de: ANNEX (page 1/1): The informat… · T-SYSTEMS INTERNATIONAL GmbH | certified | ENS ALTA | 2027-10-17 | 2026-10-18 |
| Global LEI Index (GLEIF) | T-Systems International GmbH · T-Systems International GmbH | ISSUED | DE | 2027-08-26 | 2026-10-09 |
- ACN qualified cloud (Italy): checked 2026-11-02, no entry under T Cloud Public; T-Systems International GmbH
- ISO 27001 on the basis of IT-Grundschutz (BSI, Germany): checked 2026-11-09, no entry under T Cloud Public; T-Systems International GmbH
- CISPE Data Protection Code of Conduct (GDPR Art. 40): checked 2026-11-09, no entry under T Cloud Public; T-Systems International GmbH
- DORA critical ICT third-party providers (ESAs): checked 2026-10-26, no entry under T Cloud Public; T-Systems International GmbH
- Data Privacy Framework List (US): checked 2026-11-02, no entry under T Cloud Public; T-Systems International GmbH
- ENS certificates of conformity (CCN, Spain): checked 2026-11-02, 1 entry under T Cloud Public; T-Systems International GmbH
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-02, no entry under T Cloud Public; T-Systems International GmbH
- FedRAMP Marketplace (US): checked 2026-11-02, no entry under T Cloud Public; T-Systems International GmbH
- GPAI Code of Practice signatories (European Commission): checked 2026-11-09, no entry under T Cloud Public; T-Systems International GmbH
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-02, no entry under T Cloud Public; T-Systems International GmbH
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
What an entry on the Data Privacy Framework List covers, and which vendors hold one: EU-US Data Privacy Framework.
Support window
| Product | Support period | State | SBOM | Source | Observed |
|---|---|---|---|---|---|
| T Cloud Public (service) | — | Service only | unknown | t-cloud-public.com | 2026-10-11 |
Vulnerability reporting: no security.txt at the well-known path (read 2026-10-17)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-10-08 |
| dpa | Public | full | 200 | 2026-10-09 |
| residency | Public | full | 200 | 2026-10-08 |
| subprocessors | Public | full | 200 | 2026-10-08 |
History
Nothing has moved since we started watching this vendor on 2026-10-08. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.