Where AMBOSS SE (“AMBOSS”) processes personal data as a joint controller together with an institution (“Institutional Partner”, AMBOSS and the Institutional Partner individually “Party” and collectively “Parties”), the Parties implement the following technical and organizational matters to ensure a level of protection appropriate to the risk to the rights and freedoms of the users concerned. The Parties may introduce alternative measures insofar as the change does not fall below the level of protection of the measures specified below.
1. Technical and Organizational Measures of the Institutional Partner
The Institutional Partner ensures that the access data provided to its employees in accordance with Art. 32 para. 1 lit. b GDPR cannot fall into the hands of unauthorized persons and implements a suitable authorization concept for this purpose. In addition, the Institutional Partner obliges its employees/educators who receive access to personalizes usage data to comply with the joint controllership agreement, in particular with regard to the limitations on usage purposes.
2. Technical and Organizational Measures of AMBOSS
This section summarizes the technical and organizational measures taken by AMBOSS within the meaning of Art. 32 para. 1 GDPR with regard to personalized usage data. These are measures with which AMBOSS protects personal data in this context. AMBOSS’ data protection officer is heyData GmbH, Schützenstraße 5, 10117 Berlin, www.heydata.eu, email: datenschutz@heydata.eu.
a) Pseudonymization and Encryption (Art. 32 para. 1 a GDPR)
The following implemented measures protect personal data from unauthorized access:
b) Confidentiality (Art. 32 para. 1 lit. b GDPR)
aa) Access control to systems
The following implemented measures prevent unauthorized persons from gaining access to the data processing systems:
bb) Access control to data
The following implemented measures ensure that unauthorized persons have no access to personal data:
b)Separation control
The following measures ensure that personal data collected for different purposes is processed separately:
c) Integrity (Art. 32 para. 1 lit. b GDPR)
aa) Transfer control
It is ensured that personal data cannot be read, copied, changed or removed without authorization during transmission or storage on data carriers and that it is possible to check which persons or bodies have received personal data. The following measures have been implemented to ensure this:
bb) Input control
The following measures ensure that it is possible to check who has processed personal data in data processing systems and at what time:
The following measures ensure that it is possible to check who has processed personal data in data processing systems and at what time:
cc) Order control
The following measures ensure that personal data can only be processed in accordance with the instructions:
d) Availability and Resilience (Art. 32 para. 1 lit. b GDPR)
The following measures ensure that personal data is protected against accidental destruction or loss and is always available:
e) Ability to quickly restore the availability of and access to personal data in the event of a physical or technical incident (Art. 32 para. 1 lit. c GDPR)
The following measures ensure that personal data is protected against accidental destruction or loss and is always available to the client:
f) Procedures for regular review, assessment and evaluation (Art. 32 para. 1 lit. d GDPR; Art. 25 para. 1 GDPR)
aa) Data protection management
The following measures shall ensure that the organization meets the basic requirements of data protection law:
bb) Incident response management
The following measures shall to ensure that reporting processes are triggered in the event of data breaches:
cc) Data protection-friendly default settings (Art. 25 para. 2 GDPR)
The following implemented measures take into account the requirements of the principles of "privacy by design" and "privacy by default":