| Business name of the actor | Role in the hosting service (Host/processor of the Host) | HDS certified | SecNumCloud 3.2 qualified | Hosting activities in which the actor is involved | Access to personal health data from countries outside the European Economic Area, by the Host or one of its processors (Requirement No. 29 of the HDS framework) | Host or processor subject to a risk of access to personal health data from countries outside the European Economic Area, imposed by the legislation of a third country in breach of EU law (Requirement no 30 of the HDS framework) |
|---|---|---|---|---|---|---|
| commercetools | Host / Processor | Yes | No | Activities 3,4,5 | Yes. Support teams may have limited access from the US and other third countries not covered by an adequacy decision. Standard Contractual Clauses (SCCs) are in place. | No |
| MongoDB | Processor | Yes | No | Activities 3,4 | Yes. Technical support may access from the US, UK, Canada, India, Australia, Singapore, etc. See the MongoDB HDS-related publication and the certification status. | Yes, USA |
| Google GCP | Host | Yes | No | Activities 1,2,3 | Yes. Customer support or telemetry data may be processed from countries such as the US. Data hosting location is customer-configurable. See GCP Data Processing and SCC policies. For more transparency regarding the DSCP processing, see the publication by Google. | Yes, USA |
Information relevant to Requirement 31 (HDS V2.0)
Ask about this Page
Copy for AI
View as Markdown