Separation Control. Where legally required, Provider will ensure that Personal Data collected for different purposes can be Processed separately. Provider shall also ensure there is separation between test and production systems. AVAILABILITY CONTROL. Provider protects Personal Data against accidental destruction or loss by following these controls:
Separation Control. According to the separation requirement, data collected for different purposes must be processed separately (also: requirement of non-linkability). This is intended to ensure that the intended purpose of the Personal Data is implemented through organisational and technical measures. The separation requirement is particularly important in the context of order processing, if, for example, data of several clients is stored on a system. If the separation requirement cannot be achieved by technical measures such as access control software, separate storage is necessary.
Separation Control. Measures to ensure that data collected for different purposes are processed separately either logically or physically.
Separation Control. Separation of personal data must be ensured through different storage locations or client separation.
Separation Control. The goal of separation control is to ensure that data collected for different purposes can be processed separately. The following measures are implemented: Use of multi-tenant systems with logical client separation Development and quality assurance systems are completely separate from productive systems in order to ensure productive operation. The only exchange that takes place is in the form of files that are needed for processing data (program files, parameter files, etc.) Customer systems are only accessed by authorized personnel of Unify or involved Partner.
Separation Control. Seatti Software is multi-client capable and all customer-related data is managed in a separate client in a central data processing system. Data records are provided with a client ID, which is used for authentication and clear demarcation. Clients can only view data authenticated for them in their user interface and, if necessary, edit it to the extent provided.
Separation Control. Aim: Data collected for different purposes can be processed separately. Measures for separate processing (storage, modification, deletion, transfer) of information with different purposes: • functional separation / production / non-production: SAP maintains completely physical separation between production, development and testing. Customer is provisioned 2 distinct instances: one for production and at least one for non production. • Customer (including its Affiliates) have access only to Customer’s instance(s).
Separation Control. Aim: Data collected for different purposes can be processed separately.
Separation Control. HWD processes proprietary personal data only within the scope of systems and processes needed for the specific assignment. Within the scope of proprietary processing of personal data, HWD separates test environments from production environments. Depending on the service provided, HWD segregates customer data either physically (separate hardware systems, e.g. “dedicated server hosting”), or logi- cally. Logical segregation may be realized in different ways, depending on the service provided. (“virtual server,” “multitenant software”). The customer is responsible for any further separation control measures for the storage and processing of personal data within the scope of the order processing.
Separation Control. Measures to ensure that data collected for different purposes can be processed separately: • Logically strictly separated storage of data in different customer systems • Encryption of data records that are processed for the same purpose • Providing records with purpose attributes/data fields • Separation of production and test system
