by ZHAW, IUNR (publisher); Garzotto GmbH (technical developer/programmer)
Thank you for using or showing interest in the smartphone app 'Fire blight' (henceforth referred to as the 'smartphone app'). This privacy policy applies to the preventative 'Fire blight' app. The publisher and technical developer adhere to the following guidelines: The smartphone app does not collect any data other than that needed to fulfil its purpose.
Reports of fire blight sightings are saved on a server available to the publisher and developer of this app. The data is used to ensure an improved fire blight monitoring in the countries where reports are made.
The smartphone app does not send any data to a server other than data the server requires to fulfil its purpose/function.
The publisher and the developer, the smartphone app and the data servers do not pass on any user-specific data to third parties, unless this is made clear to the user, and they have expressly given their consent.
The smartphone app determines the position of the user. When using the app, it is either completely clear why the app does this (for example, to show the location on a map) or the app explains why it wants to do so and seeks the consent of the user.
Current or historical location information is never communicated externally or tracked by the 'Fire blight' app, unless the user explicitly shares their location with someone else, or if the user explicitly gives their consent to do so at each sharing process step, for example, when the geographical location where a fire blight sighting occurred is to be sent to a server for anonymous processing.
All collected data is anonymous and cannot be traced back to the originator. Each recorded data set includes the anonymous device code of the recording device, however, no connection to the originator can be established.
The smartphone app may require access to further information on the device such as: the anonymous device identification number, contact information, calendar and photo library. In these cases, it is either obvious why the app requires this access, or the user is explicitly asked for permission. Data acquired in this way by the app is not communicated externally by the app unless the user deliberately shares it (via Twitter, Facebook, SMS, etc.), or the user explicitly gives their consent to this.