Data residency

For the ATOSS Cloud Core Services, ATOSS stores customer's personal data in the geographic regions set forth below (each a "data center location region"). ATOSS Cloud Core Services means those Cloud Services which are not listed as ATOSS Cloud Dedicated Services. ATOSS does not control or restrict the regions from which customer or any of customer's end users may access or use the ATOSS Cloud Core Services.

Further information on the security measures taken or the selection process of our sub processors can be found in our whitepaper - Transfer Impact Assessments.

Download Whitepaper 

We would also like to refer you to our whitepaper - global data processing, which summarizes further information on this topic. Our whitepaper is available for download at any time in our ATOSS Customer Lounge (see "Data Protection" section there), where you can also find out about any changes.

* If this option is chosen, the "worldwide" option also applies to the ATOSS Cloud Dedicated Services.
** Only for the products ATOSS Staff Efficiency Suite and ATOSS Startup Edition. See also https://learn.microsoft.com/en-us/privacy/eudb/eu-data-boundary-learn. If this option is chosen, the "EU Data Boundary" option also applies to the ATOSS Cloud Dedicated Services if available, otherwise the "worldwide" option applies.
*** The following Microsoft Azure location regions currently apply: Germany West Central, Germany North, North Europe, West Europe. See also https://learn.microsoft.com/en-us/azure/reliability/regions-list.

* The E-mail Relay Service is only in use if the sending of e-mails is configured in the ATOSS product. 

** When ATOSS Mobile Workforce Management Notification Services is enabled and the push function is used, we may also provide the following specific information:

• The push function must be explicitly set up by the customer. This means that if this function is not set up by the customer, no push message will be sent and therefore no data will be sent to our sub-processor Google Ireland Ltd.
• With iOS, the recipient of a push message must agree once, in accordance with the standard mechanisms, to allow our app to receive push messages. This means that even if the customer generally sets this up, on iOS it is still up to the individual employee to decide whether to allow our app to receive push messages. On Android, permission to send push notifications is turned on according to the standard mechanisms of the Android operating system, but can be turned off by the individual employee via setting. This means that even if the customer sets this up in general, it is still up to the individual employee to decide whether to allow our app to receive push notifications.
• The type of data sent via push message depends on the configuration of the customer's "Task Management" module. The customer decides for which use cases (e.g. employee's qualification is about to expire, employee has violated core time) a push message is sent and decides which information text the respective push message contains (e.g. name of qualification, expiration date).
• Our privacy statement for our mobile app ATOSS Mobile Workforce Management is available for our customers to download from the website, where you can find out about any changes.

*** Only for customers of ATOSS CLOUD24/7 or ATOSS CLOUD24/7 (EU Data Boundary).

* See also https://learn.microsoft.com/en-us/privacy/eudb/eu-data-boundary-learn If this option is chosen, the "EU Data Boundary" option also applies to the ATOSS Cloud Dedicated Services if available, otherwise the "worldwide" option applies

** The E-mail Relay Service is only in use if the sending of e-mails is configured in the ATOSS product. 

*** Only for customers of ATOSS CLOUD24/7 or ATOSS CLOUD24/7 (EU Data Boundary)

Changes to this content
We reserve the right to change this content from time to time and to post changes.