How to Audit Every App Permission on Your iPhone
Published · Last reviewed
Audit iPhone permissions by category rather than by app: open Privacy & Security in Settings and work down Microphone, Camera, Contacts, Photos, and Location Services, revoking anything that does not need that access to do the job you actually use the app for. Working by category takes about fifteen minutes and shows you every app holding a given permission side by side, which is what makes the outliers obvious.
Why category-first beats app-first
Most people audit permissions by scrolling their app list and opening each app's settings. That takes an hour and teaches you nothing, because you see one permission at a time with no basis for comparison. Going the other way — opening Microphone and seeing all eleven apps that can listen — makes the odd ones jump out instantly. A note-taking app with microphone access is expected. A shopping app with microphone access is not.
Comparison is the whole trick. You are not trying to remember what each app claimed when it asked; you are looking for the entries that do not belong in a list.
The order to work in
Sensitivity descends roughly like this, so this is the order that gets the most value from the first five minutes:
- Microphone — the most intrusive sensor, and the one fewest apps genuinely need.
- Camera — same reasoning; anything that is not a camera, scanner, or video-call app is questionable.
- Contacts — the permission that leaks other people's data, not just your own, and cannot be un-shared once uploaded.
- Photos — where full-library access is rarely necessary; Limited Access almost always suffices.
- Location Services — big enough to deserve its own pass, covered in the location guide.
- Local Network, Bluetooth, Health, Calendars, Reminders, Speech Recognition, Motion & Fitness — quick passes, but Local Network and Bluetooth are worth reading closely, because both can be used to profile the devices around you.
The decision rule for each app
- Action
- Ask one question per entry: does this app need this permission for the specific thing I use it for?
- Why it helps
- Apps request permissions for their whole feature set, not for your use of it. A social app may legitimately need a camera for its story feature you have never opened.
- Verification
- You can state, in one sentence, why each remaining permission exists.
- Action
- Revoke first and re-grant on demand, rather than agonising over edge cases.
- Why it helps
- iOS re-prompts when an app genuinely needs a permission for something you asked it to do, so the cost of a wrong revocation is one extra tap later.
- Verification
- Apps you use daily continue working; anything that breaks re-asks and you decide in context.
- Action
- Switch Photos access from full to Limited Access for any app that is not a photo editor or backup service.
- Why it helps
- Limited Access shows the app only the images you pick each time, instead of granting a standing read of your whole library and its location metadata.
- Verification
- The app shows a picker when it needs an image rather than browsing everything.
- Action
- Turn off Background App Refresh for apps that do not need to update while closed, in Settings General Background App Refresh.
- Why it helps
- Background refresh is both a privacy and a battery cost: an app that wakes periodically can also report location and usage while you are not looking.
- Verification
- The app list shows refresh enabled only for messaging, mail, and anything you rely on for timely alerts.
Verify with the App Privacy Report
Turn on App Privacy Report at the bottom of Settings Privacy & Security. Over the following seven days it logs which apps actually accessed the camera, microphone, photos, contacts, and location, and which network domains they contacted — including domains contacted while you were not using the app.
This is the only part of the process that shows behaviour rather than policy. An app that accessed your location 340 times in a week, or that contacts a dozen advertising domains, is telling you something no privacy label will. Come back in a week and revoke based on what you see.
Two settings people miss
- Local Network access lets an app enumerate devices on your Wi-Fi — printers, TVs, smart-home gear. That inventory is genuinely identifying. Only smart-home and casting apps need it.
- Bluetooth access can be used for proximity-based tracking in physical retail. Grant it to headphones, car, and wearable apps, and to nothing else.
How it works
iOS permissions work on a deny-by-default, prompt-on-first-use model. An app cannot read your contacts or open the microphone until it calls the relevant system API, at which point iOS suspends the request and shows you a prompt. Your answer is stored per app, and the app never sees the difference between “denied” and “there is nothing here” — which is why a revoked permission usually degrades a feature rather than crashing the app.
Crucially, that grant is indefinite. There is no expiry, no periodic re-confirmation, and no notification when a permission you granted in 2022 gets used for the first time in a year. The system is excellent at the moment of decision and does nothing to help you revisit it. Auditing is the manual compensation for that design gap.
The App Privacy Report closes the loop differently: rather than asking what an app may do, it records what it did, sampling sensor access and outbound domain contacts over a rolling seven-day window and keeping that log entirely on the device. Because the log is behavioural, it catches the mismatch between a stated purpose and an actual pattern — the thing a permission list alone can never show you.
Worked example
A fifteen-minute audit on a phone with 94 apps installed. Opening Microphone lists nine apps. Seven make sense — two messaging apps, a voice recorder, a video-call app, a music identification app, a translation app, and the built-in dictation. Two do not: a supermarket loyalty app and a puzzle game. Both are revoked in eight seconds. Neither has since re-prompted, which tells you they never needed it for anything the owner does.
Contacts lists fourteen apps, of which four are messaging apps that need it, and ten are apps that asked once during onboarding to find friends. All ten are revoked. Note the asymmetry here: revoking does not recall the copy already uploaded, which is precisely why the default answer to a contacts prompt should be no.
Photos shows six apps with full library access. Only the cloud backup app and the photo editor need it; the other four are moved to Limited Access. Seven days later the App Privacy Report shows the biggest surprise of the exercise: a weather app had accessed location 218 times in a week despite being opened twice. Its access is changed to While Using the App, and the phone's overnight battery drain improves as a side effect.
Frequently asked questions
How do I see which apps use my iPhone camera or microphone?
Open Settings, tap Privacy & Security, then tap Camera or Microphone to see every app that has requested that permission and whether it is currently allowed. Turning an app off there takes effect immediately.
What is Limited Access for Photos on iPhone?
Limited Access lets an app see only the specific photos you select rather than your entire library, and it re-asks each time it needs more. It is the right setting for almost any app that is not a photo editor or a backup service.
Will revoking permissions break my apps?
Individual features that depend on the permission stop working, but the app itself keeps running, because iOS presents a denied permission as an absence of data rather than an error. If the app genuinely needs it, iOS prompts again when you next use that feature.
What does the App Privacy Report actually record?
It logs which apps accessed sensitive data such as camera, microphone, photos, contacts, and location over the last seven days, plus the network domains each app contacted. The log stays on your device and is not sent to Apple.
Why does an app need Local Network access?
Legitimate uses are casting to a TV, setting up smart-home devices, and printing. Otherwise it allows an app to inventory the devices on your Wi-Fi, which is identifying information, so it is reasonable to decline for anything else.
How often should I audit iPhone app permissions?
Twice a year is enough for most people, plus a quick pass after any major iOS update, since updates can introduce new permission categories. Auditing takes about fifteen minutes when you work by category.
Want checks like this in your inbox?
The briefing is published on this site every morning. The email edition is not sending yet — leave your address and you’ll be among the first told when it starts. Nothing is sent in the meantime.