# Android permissions manager explained

URL: https://ekom.blog/android-permissions-manager-explained/
Published: 2026-06-02
Author: Ekom
Topics: Operating systems & apps

> How the Android permissions manager works, what each choice really means, and a ten-minute routine to take back control of what your apps can see.

A torch app that wants your contacts. A photo editor that wants your location. A game that asks to record audio before you've even finished the tutorial. Android lets you say no to all of it, but the controls are tucked away enough that most people never look.

The tool for the job is the permissions manager. It's one screen that lists every kind of data on your phone (camera, microphone, location, contacts and so on) and shows which apps can reach each one. Think of it as the visitor book at the front desk of a building: you can see who has a key to which room, and you can take a key back.

## How permissions work on Android

Early versions of Android took an all-or-nothing approach. You saw a long list of permissions when you installed an app, and if you wanted the app, you accepted the lot. That changed with Android 6.0 in 2015, which introduced runtime permissions. Apps now ask when they need something, usually at the moment you use the feature, and you can refuse and keep using the rest of the app.

Since then, Google has kept tightening things. A few changes worth knowing:

- Android 10 added "Allow only while using the app" for location, so an app can't quietly track you in the background.

- Android 11 added a one-time option ("Only this time"), and began automatically resetting permissions for apps you haven't opened in a while.

- Android 12 brought the Privacy Dashboard and indicators in the status bar when the camera or microphone is in use, plus quick toggles to switch those sensors off.

- Android 13 made notifications something an app has to ask for, and added a photo picker so an app can see only the pictures you choose.

- Android 14 let you share a selection of photos and videos instead of your whole gallery.

Phone makers add their own skin on top, so menu names differ a little between Pixel, Samsung, Xiaomi and others. If you want the bigger picture on that, Android skins explained covers why.

## Where to find it

On most phones, open Settings, then Security & privacy (or just Privacy), then Permission manager. Samsung puts it under Security and privacy, then Privacy, then Permission manager. If you can't find it, search "permission" in the Settings search bar. That works on nearly every phone.

You can also arrive from the other direction: long-press an app icon, tap App info, then Permissions. That view shows one app and everything it can touch.

## What each choice means

When you open a permission, you'll usually see some version of these options:

Choice
What it means

Allow all the time
The app can use it even when you're not looking at it

Allow only while using the app
Works while the app is on screen (or running a visible task)

Ask every time
The app has to ask each time it wants it

Don't allow
The app can't use it, and the feature that needs it stops working

Allow only this time
A one-off; the permission disappears when you close the app

For location, you'll also see Precise versus Approximate. A weather app doesn't need your exact doorstep. I went through that one in location permissions: precise vs approximate.

## The permissions worth your attention

You don't need to audit all of them. Start with the ones that can do real harm if abused.

Location. Few apps need it all the time. Maps and ride-hailing apps while you're using them, fine. A shopping app? Probably "while using" or "approximate" is plenty.

Microphone and camera. A video-call app obviously needs both. A calculator doesn't. If an app has either and you can't think why, remove it. There's a full walkthrough in microphone and camera permissions: how to audit them.

Contacts and call logs. These are about other people's data, not just yours. Apps that sync your contacts are uploading your friends' numbers. Be stingy.

SMS. This is rarely needed, and it's the one scammers love, because text messages carry one-time codes. Only your messaging app and perhaps a banking app should have it.

Files, photos and media. Prefer "selected photos" over "all photos" if your phone offers it.

Nearby devices. This one's newer and easy to ignore. It lets an app find and connect to Bluetooth devices, and it can also be used to work out roughly where you are.

Notifications. Not dangerous, but a noisy app is a distraction. Turn them off for anything that doesn't earn its interruptions.

## A ten-minute routine

Do this once, then repeat it every few months.

- Open the permission manager and go through Location, Microphone, Camera, Contacts and SMS one at a time.

- For each app in the "allowed" list, ask: does this app need this to do its job? If not, change it to "Don't allow" or "While using".

- Look at the Unused apps or Remove permissions if app is unused setting inside an app's info page. Make sure it's on. This quietly cleans up apps you've forgotten about.

- Open the Privacy dashboard and look at the last 24 hours (or seven days on newer versions). If something accessed your microphone at 3 a.m., you'll see it.

- Uninstall anything you don't use. An app that's gone has no permissions at all.

If you've just bought a phone, app permissions: the settings to check on every new phone is the version of this for day one.

## Common myths

"If I deny a permission, the app breaks." Sometimes a feature stops, but the app usually carries on. Try denying, and grant it later if you miss it.

"Apps from the Play Store are always safe." Google screens them, but a legitimate app can still ask for more than it needs. The permissions manager is your check, not Google's.

"Permissions only matter for strangers' apps." Big, familiar apps often hold the most permissions, simply because they've been installed the longest.

## If you manage a website

A reason to care beyond your own phone: if you run a site, you probably have admin apps on your phone for your shop, your analytics or your email. Those apps are a way into your business. Giving a random app access to your notifications or your screen can expose codes and alerts. I'd pair this with two-factor authentication on every client login and keep the number of apps with access to your accounts small.

## Key takeaways

- The permissions manager groups access by type of data, so you can see every app with a given permission in one place.

- "While using the app" is the right default for most things.

- Location, microphone, camera, contacts and SMS deserve the most scrutiny.

- Auto-reset for unused apps is on by default on recent versions, but check that it is.

- Uninstalling an app you don't use beats any setting.

## FAQ

### Does revoking a permission delete the data the app already has?

No. It stops the app from collecting more through your phone. Data it has already sent to its servers stays there, so deleting the account matters too.

### Why do some apps keep asking again?

Some apps ask each time you open the feature. If you choose "Don't allow" twice on some Android versions, the system stops showing the prompt, and you'd have to change it in Settings.

### Can I see which app used the camera?

Yes, on Android 12 and later, the Privacy Dashboard shows a timeline of which apps accessed the camera, microphone and location.

## Related reading

- App permissions: the settings to check on every new phone

- Privacy settings on iPhone and Android, side by side

- Android Private Space explained

Pick one permission today, location is a good start, and see how many apps have "all the time" access. How many did you find?

---

From Ekom (https://ekom.blog/). More: https://ekom.blog/llms.txt
