Data protection provisions of our ATOSS Mobile Workforce Management App.

ATOSS Software AG
Am Moosfeld 3
81829 Munich
Germany

Registry Court: District Court of Munich
Registration number: HRB 124084
Head Office of the company: Munich
Management Board: Andreas F.J. Obereder, Christof Leiber

VAT No. pursuant to § 27 a VAT Act: DE812622540

Contact:
Phone: +49 89 427710 
email: info@atoss.com

The application permits the personal details of the app user ("user") to be entered or corrected. In particular, the user can enter and change the password required for authenticating use of the app, post and correct times, initiate and process workflows as well as carry out further data processing procedures related to workforce scheduling and time management.

<uses-permission android:name="android.permission.INTERNET"/>
Permits the application to connect to the Internet.

<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
Permits the application to access information through WIFI networks.

<uses-permission android:name="android.permission.CAMERA"/>
The app requires access to the camera in your mobile device to take pictures for workflow functions. Workflow applications can also contain attachments which the camera or picture gallery provides. Attachments to a workflow are sent in encrypted form and subsequently saved to the service provider's application server or that of a third party commissioned by him.

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
Allows pictures to be saved to the picture gallery on your mobile device for workflow functions. Workflow applications can also contain attachments which the camera or picture gallery provides. Attachments to a workflow are sent in encrypted form and subsequently saved to the service provider's application server or that of a third party commissioned by him. (Log) files for error analysis can also be generated on the basis of separate authorization. However, any such authorization must be explicitly activated by the service provider, and also requires the user's consent.

<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
Permits the application to determine your approximate location. This function, however, must be explicitly activated by the service provider, and also requires the user's consent.

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
Permits the application to determine your exact location. This function, however, must be explicitly activated by the service provider, and also requires the user's consent.

<uses-permission android:name="android.permission.VIBRATE"/>
Permits the application to access the vibration module.

<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>
Permits the application to access information through WIFI networks.

<uses-permission android:name="android.permission.CAMERA"/>
The app requires access to the camera in your mobile device to take pictures for workflow functions. Workflow applications can also contain attachments which the camera or picture gallery provides. Attachments to a workflow are sent in encrypted form and subsequently saved to the service provider's application server or that of a third party commissioned by him.

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
Allows pictures to be saved to the picture gallery on your mobile device for workflow functions. Workflow applications can also contain attachments which the camera or picture gallery provides. Attachments to a workflow are sent in encrypted form and subsequently saved to the service provider's application server or that of a third party commissioned by him. (Log) files for error analysis can also be generated on the basis of separate authorization. Any such authorization, however, must be explicitly activated by the service provider, and also requires the user's consent.

<uses-permission android:name="android.permission.INTERNET"/>
Permits the application to connect to the Internet.

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
Permits the application to access information through networks.

<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
Permits the application to determine your approximate location. This function, however, must be explicitly activated by the service provider, and also requires the user's consent.

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
Permits the application to determine your exact location. This function, however, must be explicitly activated by the service provider, and also requires the user's consent.

a) The function for entering or correcting the user's personal details serves to process contractual agreements to be made between the user and the service provider. The data are synchronized between the user's mobile device and the service provider's application server, as described in Clause 4 b) below.

b) An Internet connection is required to transmit data between the app and the service provider's application server or that of a third party commissioned by him. All data (text, images, etc.) are transmitted to the application server via a dedicated ATOSS mobile information server which the service provider or a third party commissioned by him makes available.

c) Access to the camera and the picture gallery are required for full use of the workflow functions offered by ATOSS Mobile Workforce Management in accordance with contractual agreements to be made between the user and the service provider.

d) Location Based Services (LBS, GPS, location data) are used in the app to reference the location against a location area specified by the service provider. Times can only be posted via the app within this location area.

- Service provider or a third party commissioned by the former -

- Processing contractual agreements to be made between the user and the service provider -

a) The user decides on the entry or correction of their personal details taking into account the contractual agreements to be made between them and the service provider.

b) When the app first starts (after the installation or activation of this service by the service provider), the user can give or refuse permission for the app to access the location of their mobile device.

c) When the "camera" function is first launched after the app has been installed, the user can give or refuse permission for the app to access the camera in their mobile device.

d) When the "picture gallery" function is first launched after the app has been installed, the user can give or refuse permission for the app to access the picture gallery on their mobile device.

If the user rejects the functions described in Clause 7, the app will not have access to its full range of functions.