Manifest Destiny

Contacts

COMMUNICATION

Trackers

Permissions

Total permissions: 30
Unknown permissions: 7
Signature permissions: 2
Permissions considered normal: 15
Permissions considered dangerous: 6
Allows applications to access information about networks.
Allows an application to initiate a phone call without going through the Dialer user interface for the user to confirm the call.
costsMoney
Allows a regular application to use android.app.Service#startForeground Service.startForeground
Allows access to the list of accounts in the Accounts Service. Note: Beginning with Android 6.0 (API level 23), if an app shares the signature of the authenticator that manages an account, it does not need 'GET_ACCOUNTS' permission to read information about that account. On Android 5.1 and lower, all apps need 'GET_ACCOUNTS' permission to read information about any account.
Allows access to the list of accounts in the Accounts Service.
Allows applications to open network sockets.
We need to keep this around for backwards compatibility
removed
Allows applications to perform I/O operations over NFC.
Allows an application to read the user's contacts data.
Allows an application to read from external storage. Any app that declares the WRITE_EXTERNAL_STORAGE permission is implicitly granted this permission. This permission is enforced starting in API level 19. Before API level 19, this permission is not enforced and all apps still have access to read from external storage. You can test your app with the permission enforced by enabling
softRestricted immutablyRestricted
Allows read only access to phone state, including the current cellular network information, the status of any ongoing calls, and a list of any android.telecom.PhoneAccount registered on the device. Note: If both your ' minSdkVersion and ' targetSdkVersion values are set to 3 or lower, the system implicitly grants your app this permission. If you don't need this permission, be sure your ' targetSdkVersion is 4 or higher.
We need to keep this around for backwards compatibility
removed
Allows applications to read the sync settings.
Allows applications to read the sync stats.
Allows an application to receive the ACTION_BOOT_COMPLETED that is broadcast after the system finishes booting. If you don't request this permission, you will not receive the broadcast at that time. Though holding this permission does not have any security implications, it can have a negative impact on the user experience by increasing the amount of time it takes the system to start and allowing applications to have themselves running without the user being aware of them. As such, you must explicitly declare your use of this facility to make that visible to the user.
We need to keep this around for backwards compatibility
removed
Allows access to the vibrator.
Allows using PowerManager WakeLocks to keep processor from sleeping or screen from dimming.
Allows an application to write the user's contacts data.
We need to keep this around for backwards compatibility
removed
(signature preinstalled appop pre23)
Allows an application to read or write the system settings. Note: If the app targets API level 23 or higher, the app user must explicitly grant this permission to the app through a permission management screen. The app requests the user's approval by sending an intent with action ACTION_MANAGE_WRITE_SETTINGS. The app can check whether it has this authorization by calling android.provider.Settings.System#canWrite Settings.System.canWrite()
Allows applications to write the sync settings.
Allows an application to install a shortcut in Launcher. In Android O (API level 26) and higher, the INSTALL_SHORTCUT broadcast no longer has any effect on your app because it's a private, implicit broadcast. Instead, you should create an app shortcut by using the android.content.pm.ShortcutManager#requestPinShortcut requestPinShortcut()method from the android.content.pm.ShortcutManagerclass.
No description yet, this could be a misspelling or a permission created by the app itself
No description yet, this could be a misspelling or a permission created by the app itself
No description yet, this could be a misspelling or a permission created by the app itself
No description yet, this could be a misspelling or a permission created by the app itself
No description yet, this could be a misspelling or a permission created by the app itself
No description yet, this could be a misspelling or a permission created by the app itself
No description yet, this could be a misspelling or a permission created by the app itself
COMMUNICATION 1

Map of past connections