Permissions worth saying no to, and what stops working
Since Android 6 permissions are granted when they are used rather than at install, and since Android 11 they can be granted once, for a session. That gives you real control, and the reason people do not use it is uncertainty about what a refusal breaks. Here is the honest answer, permission by permission.
What each refusal actually costs
| Permission | What breaks if you refuse | Refuse by default? |
|---|---|---|
| Camera | Taking photos in that app. Nothing else. | Yes, until needed |
| Microphone | Voice messages and calls in that app | Yes, until needed |
| Location, precise | Maps and anything genuinely local | Use approximate instead |
| Location, background | Almost nothing you will notice | Yes, nearly always |
| Contacts | Finding friends. Messaging still works. | Yes |
| Storage or media | Attaching and saving files | Allow selected items only |
| Phone | Call handling. Rarely needed by non-dialler apps. | Yes |
| SMS | Reading codes automatically | Yes, type the code |
| Notifications | Alerts from that app | Case by case |
| Accessibility | Automation features | Yes, unless you know exactly why |
Anúncio
Location is three permissions, not one
Android splits location into approximate, precise, and background, and most apps asking for all three need one. The distinction is worth learning because it is where the largest privacy gain is available for the least inconvenience.
- Turn-by-turn navigation
- Ride hailing pickup
- Fitness tracking a route
- Finding the nearest branch of something
- Weather
- News with a local section
- Shopping and delivery apps
- Almost every social app
Background location is separate and much rarer to need. An app that wants your location while it is closed should be a navigation app, a fitness tracker recording a workout, or a family locator. Everything else is collecting.
Auditing what you already granted
- Open the permission manager Settings, Privacy, then Permission manager. It lists by permission rather than by app, which is the useful direction.
- Start with location, microphone and camera Read the list of apps holding each one. There will be surprises.
- Revoke anything you cannot explain If it breaks, the app will ask again and you can decide with context.
- Turn on auto-revoke for unused apps Android removes permissions from apps you have not opened in a few months.
- Check the privacy indicators The dot in the corner shows when the camera or microphone is live. Learn what it looks like.
Permissions and apps from outside Play
An app installed from anywhere is subject to the same permission model, and the install dialog shows the full list before you confirm. That list is more informative than any store rating, and reading it takes ten seconds.
The signal to look for is a mismatch between what the app does and what it asks for. A calculator wanting contacts, a wallpaper app wanting SMS, a game wanting accessibility. None of those needs to be malicious to be a good reason to choose a different app.
Refuse background location and accessibility by default, use approximate location and selected-media access, and audit the permission manager once.
Frequently asked questions
Will refusing a permission break the app?
A well-built app degrades gracefully and asks again when it needs the feature. One that refuses to run at all is a choice the developer made.
What is the once-only option?
It grants the permission for that session and revokes it when you leave the app. It is the right default for camera and microphone.
Does Android tell me when an app uses the camera?
Yes, since Android 12 there is an indicator in the status bar, and the privacy dashboard shows a history.
Read next
This is not a rivalry. Each does something the other cannot.
You are not buying encryption. You are buying an operator whose income does not depend on you.
For a plain ZIP either works. For a split, password-protected archive, only one does.
