Android permissions
- Former user (Deleted)
List of permissions requested and required in AppScho's Android apps
This document lists the permissions our Android application requests from the user, and the reason why those permissions are necessary.
The Contextual consent column, when marked "Yes", indicates the permissions is not implicitely granted when the app is installed, but requires an explicit user approval, at the moment of use, before we can use it.
Name | Contextual consent | Description |
ACCESS_COARSE_LOCATIO ACCESS_FINE_LOCATION |
Yes | Used in our Campus Maps and Mapwize features in order to display the user's locationon th maps. |
ACCESS_NETWORK_STATE ACCESS_WIFI_STATE |
No | Used to determine if an Interne connection is available. |
FOREGROUND_SERVICE |
No | Allows to check, when the app launched, whether an update i available. |
INTERNET |
No | Allows communicating the networked services. |
READ_CALENDAR |
Yes | Required to add events to the user's personal calendar in our Events feature. The read permission is needed to check an event was already added to the calendar in order not to hav duplicates. |
RECEIVE_BOOT_COMPLETED |
No | Used to launch background services when the device start up, in order to keep updating data when the app is in the background. |
VIBRATE |
No | Used to make the device vibra on specific actions (student car scans, for example). |
WAKE_LOCK | No | Required to schedule notifications in the future and trigger them even when the device is locked. |
RECEIVE |
No | Used to enable the receiving o push messages. |
BIND_GET_INSTALL_REFERRER_SERVICE |
No | Used by Firebase Analytics to determine where the app was installed from (for example, through Google Play). |