
Table of contents
Have you ever wondered why a flashlight app needs your contacts, or a weather app needs your microphone? A recent review by security researchers found that a large share of popular apps request permissions they don't need to work. Fortunately, both Android and iOS make it easy to audit those permissions. In this guide, we show you how to make your phone safer in just a few minutes.
What to watch for on the permission screen
The permission prompt that pops up the first time you open an app is usually dismissed in seconds. The “Allow” button is big and inviting, while the “Deny” option looks small and faded. Yet that brief moment is the real decision about who gets access to your data, and for how long. The rule is simple: a permission makes sense if it's directly tied to what the app does.
The mobile security experts we spoke with recommend splitting permissions into three groups. Hardware permissions like camera and microphone are the most sensitive; location and contacts come second; notification and storage permissions carry relatively low risk. It's natural for a photo editing app to access your gallery, but if the same app wants to read your contacts, that's a sign to stop and think.

If an app asks for a permission it doesn't need, the answer should always be no.
Mark Ellison
Limiting location and microphone access
Location is one of the most commonly misused permissions. Maps and ride-hailing apps may need constant location access, but a shopping or gaming app rarely has a good reason to track you in the background. Both Android and iOS now offer “only while using the app” and “approximate location” options; for most apps, these two settings are more than enough.
We recommend a similar approach for the microphone. Open the permission manager in your phone's settings, list the apps that can access the microphone and switch off access for any you haven't used in the past month. Most apps keep working even after the permission is revoked. They'll ask again when they truly need it, which also teaches you which feature requires which permission.
Learn to read privacy reports
Modern operating systems offer privacy reports showing which app used which permission and when. These reports can look technical at first glance, but a few minutes of digging reveals a surprising picture. Seeing that an app you thought you never opened accessed your location dozens of times a day is, for most users, the first real motivation for this audit.
| Topic | Security |
|---|---|
| Highlights | privacy, app, smartphone |
| Reading time | 7 minutes |
| Written by | Mark Ellison |
Key takeaways
- The permission an app asks for should be directly tied to what it does.
- Sharing approximate location only while the app is in use is usually enough.
- A five-minute monthly check of the privacy report reveals surprise access.
When reading the report, look at patterns rather than individual access counts. Access during the night, background activity from apps you don't use and connections to third-party domains are all red flags. Restrict the permissions of any app you find suspicious, and remove it if that doesn't help. This five-minute monthly check is the cheapest way to protect your data.
What do you think about this post?



































































2 Comments
Really useful piece, thank you for putting it together.
I had never thought about this side of it. Looking forward to a follow-up.