The following is a list of mobile app permissions that may be requested and what they are used for in-app. At no time is any personally identifiable information (PII) ever automatically obtained or stored.
Both platforms will request location permissions when needed to provide latitude and longitude to show location on a map feature, to update local weather, and to optionally add the user’s lat/long to the form feature (e.g. submit-a-tip).
The storage permission is required on Android to cache the information loaded into the app for assisting with download speeds and feature transition speeds in-app. Other features that may access device storage space include the Asset Tracker, which saves user-inputted inventory information to the device, and the Emergency Plan which saves user-inputted emergency contact information to the device.
These permissions are requested for saving a contact to the user’s device. Write access allows for contact info to be saved, and read access allows a user to select contact information to place in a feature such as the Emergency Plan. At no time are device contacts otherwise accessed.
These permissions are requested for when a user chooses to add an image to the feature they are interacting with. These features include the Form submission (e.g. attaching an image to a submit-a-tip form) and the Asset Tracker (e.g. adding an image of an inventory item).
These permissions are requested when a user prompts to take an image to add to the feature they are interacting with. This includes the Form submission attachments and the Asset Tracker images.
These permissions are requested when a user is attempting to save an event to their device.
These permissions are requested to enable a user to receive push notifications on their device that agencies will send out from the app control panel.