Android App Permissions Explained: Which Ones Google Play Restricts

Every permission your app requests appears on your store listing, can trigger a runtime dialog and must match your Data safety form. Requesting more than you need hurts installs and can even get your update rejected. Many developers are surprised to find permissions they never added – they came from libraries. Here is how Android permissions work and how to keep yours clean.

Free tool
Check your AndroidManifest permissions
Paste your manifest to list every permission with its risk level, Play policy notes and Data safety hints. Free – nothing uploaded.
Open Android Permission Checker →

Three types of permissions

TypeExamplesHow it is granted
Normal (install-time)INTERNET, ACCESS_NETWORK_STATE, VIBRATEAutomatically at install
Dangerous (runtime)CAMERA, ACCESS_FINE_LOCATION, RECORD_AUDIO, READ_CONTACTS, POST_NOTIFICATIONSUser must allow in a dialog
SpecialSYSTEM_ALERT_WINDOW, MANAGE_EXTERNAL_STORAGE, SCHEDULE_EXACT_ALARMUser must enable in system settings

Permissions Google Play restricts

Some permissions require a declaration in Play Console and are allowed only for apps whose core function needs them:

  • SMS and Call Log (READ_SMS, SEND_SMS, READ_CALL_LOG) – only for default SMS/phone apps and a few exceptions
  • All files access (MANAGE_EXTERNAL_STORAGE) – file managers, backup and antivirus apps
  • Background location (ACCESS_BACKGROUND_LOCATION) – needs a clear in-app reason and declaration
  • Package visibility (QUERY_ALL_PACKAGES) – only when the app must see all installed apps
  • Photos and videos (READ_MEDIA_IMAGES, READ_MEDIA_VIDEO) – apps with occasional photo use should use the system photo picker instead
  • Exact alarms (USE_EXACT_ALARM) – mainly alarm clock and calendar apps
  • Accessibility services – only for real accessibility use cases, with disclosure

Policies change, so always check the current Google Play policy before submitting.

Hidden permissions from libraries

When you build your app, Gradle merges the manifests of all libraries. An ads, analytics or location SDK can add permissions you never wrote. To see the final list:

  • Open AndroidManifest.xml in Android Studio and click the Merged Manifest tab, or
  • Check the merged manifest in your build output, or
  • Paste it into our Android Permission Checker.

To remove a permission a library adds, declare it in your own manifest with tools:node="remove" – but only if the library works without it.

Best practices

  • Request only what your current features need.
  • Ask for runtime permissions in context – when the user taps “Scan”, ask for the camera.
  • Explain why before the system dialog appears.
  • Handle “Deny” gracefully; the app should still work where possible.
  • Prefer permission-free APIs: the photo picker, the Storage Access Framework and approximate location.
  • Keep your Data safety form and privacy policy in line with the permissions you use.

FAQ

What are dangerous permissions in Android?

Permissions that access private data or device features, such as camera, location, microphone and contacts. Users grant them at runtime.

Why does my app have permissions I did not add?

Libraries add them through manifest merging. Check the merged manifest.

Does INTERNET permission show a dialog?

No. It is a normal permission granted at install.

Can too many permissions reduce installs?

Yes. Users are cautious about apps that ask for more than they need.

Is my manifest uploaded?

No. The checker runs in your browser.

Free tool
Try the free Android Permission Checker
No signup and nothing uploaded – it runs right in your browser. Browse all 74 free tools on our Free Tools page.
Open Android Permission Checker →

Need help building or publishing your app? Talk to Techpass Master – we design, build and publish Android apps for clients worldwide.

WhatsApp us📞 Call now