Manifest Destiny

YAATA

COMMUNICATION

Trackers

Permissions

Total permissions: 41
Unknown permissions: 17
Signature permissions: 1
Permissions considered normal: 12
Permissions considered dangerous: 11
No description yet, this could be a misspelling or a permission created by the app itself
Allows applications to access information about networks.
Allows applications to access information about Wi-Fi 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 applications to change network connectivity state.
Allows applications to change Wi-Fi connectivity state.
Allows applications to disable the keyguard if it is not secure.
Allows applications to open network sockets.
No description yet, this could be a misspelling or a permission created by the app itself
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 an application to read SMS messages.
hardRestricted
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.
Allows an application to monitor incoming MMS messages.
hardRestricted
Allows an application to receive SMS messages.
hardRestricted
Allows an application to receive WAP push messages.
hardRestricted
Allows an application to record audio.
Allows an application to send SMS messages.
costsMoney hardRestricted
(signature setup appop installer pre23 development)
Allows an app to create windows using the type TYPE_APPLICATION_OVERLAY, shown on top of all other apps. Very few apps should use this permission; these windows are intended for system-level interaction with the user. 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_OVERLAY_PERMISSION. The app can check whether it has this authorization by calling android.provider.Settings#canDrawOverlays Settings.canDrawOverlays()
Allows access to the vibrator.
Allows using PowerManager WakeLocks to keep processor from sleeping or screen from dimming.
Allows an application to write to external storage. 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 '>getExternalFilesDir and getExternalCacheDir. If this permission is not allowlisted for an app that targets an API level before Q this permission cannot be granted to apps.
softRestricted immutablyRestricted
We need to keep this around for backwards compatibility
removed
No description yet, this could be a misspelling or a permission created by the app itself
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
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 0

Map of past connections