Android permissions

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_LOCATION ACCESS_FINE_LOCATION	Yes	Used in our Campus Maps and Mapwize features in order to display the user's locationon the maps.
ACCESS_NETWORK_STATE ACCESS_WIFI_STATE	No	Used to determine if an Internet connection is available.
FOREGROUND_SERVICE	No	Allows to check, when the app is launched, whether an update is available.
INTERNET	No	Allows communicating the networked services.
READ_CALENDAR WRITE_CALENDAR	Yes	Required to add events to the user's personal calendar in our Events feature. The read permission is needed to check if an event was already added to the calendar in order not to have duplicates.
RECEIVE_BOOT_COMPLETED	No	Used to launch background services when the device starts up, in order to keep updating data when the app is in the background.
VIBRATE	No	Used to make the device vibrate on specific actions (student card 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 of 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).