Application permissions

On mobile operating systems for smartphones and tablets, typical types of permissions regulate:[1][2]

• Access to storage and personal information, such as contacts, calendar appointments, etc.
• Location tracking.
• Access to the device's internal camera and/or microphone.
• Access to biometric sensors, including fingerprint readers and other health sensors..
• Internet access.
• Access to communications interfaces (including their hardware identifiers and signal strength where applicable, and requests to enable them), such as Bluetooth, Wi-Fi, Near-field communication (NFC), and others.
• Making and receiving phone calls.
• Sending and reading text messages
• The ability to perform in-app purchases.
• The ability to "overlay" themselves within other apps.
• Installing, deleting and otherwise managing applications.
• Authentication tokens (i.e. OAuth ones) of web services stored in system storage for sharing between apps.

Prior to Android 6.0 "Marshmallow", permissions were automatically granted to apps at runtime, and they were presented upon installation in Google Play Store. Since Marshmallow, certain permissions now require the app to request permission at runtime by the user. These permissions may also be revoked at any time via Android's settings menu.[3] Usage of permissions on Android are sometimes abused by app developers to gather personal information and deliver advertising; in particular, apps for using a phone's camera flash as a flashlight (which have grown largely redundant due to the integration of such functionality at the system level on later versions of Android) have been known to require a large array of unnecessary permissions beyond what is actually needed for the stated functionality.[4]

iOS imposes a similar requirement for permissions to be granted at runtime, with particular controls offered for enabling of Bluetooth, Wi-Fi, and location tracking.[5][6]

WebPermissions is a permission system for web browsers.[7] When a web application needs some data behind a permission, it must request it first. When it does it, a user sees a window asking him to make a choice. The choice is remembered, but can be cleared lately.

Currently the following resources are controlled:

• geolocation[8]
• desktop notifications[9]
• service workers[10][11]
• sensors
  • audio capturing devices,[12] like soundcards, and their model names and characteristics
  • video capturing devices,[12] like cameras, and their identifiers and characteristics

The permission-based access control model assigns access privileges for certain data objects to application. This is a derivate of the discretionary access control model. The access permissions are usually granted in the context of a specific user on a specific device. Permissions are granted permanently with few automatic restrictions.

In some cases permissions are implemented in 'all-or-nothing' approach: a user either has to grant all the required permissions to access the application or the user can not access the application. It remains intransparent to the user when the permission is used by a program or application to access the data protected by the permission access control mechanism. Even if a user can revoke a permission, the app can blackmail a user by refusing to operate, for example by just crashing or asking user to grant the permission again in order to access the application.

The permission mechanism has been widely criticized by researchers for several reasons, including;

• Intransparency of personal data extraction and surveillance, including the creation of a false sense of security;[13][14]
• End-user fatigue of micro-managing access permissions leading to a fatalistic acceptance of surveillance and intransparency;[15]
• Massive data extraction and personal surveillance carried out once the permissions are granted.[16][17]

There are some solutions, such as XPrivacy, which instead of providing access to the requested data instead of throwing an exception and crashing an app returning disinformation to make an app operate as if the permission was granted. Mockdroid[18] is another instance of this approach. Further transparency methods include longitudinal behavioural profiling and multiple-source privacy analysis of app data access.[19][20]