> ## Content Index
> Fetch the complete content index at: https://unhyd.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Check App Permissions on Android and iPhone
- URL: https://unhyd.com/article/how-to-check-app-permissions-android-iphone/
- Published: 2026-11-20T23:39:48.000Z
- Updated: 2026-11-20T23:39:48.000Z
- Description: A practical audit of what installed apps can access, what to restrict and why device permissions are not a complete privacy audit.
- Author: Tina Thormodsæter
- Tags: Technology, #sidebar-popular-posts, #sidebar-toc

Knowing **how to check app permissions** can help you find access you granted months ago but no longer need. The practical goal is not to disable every permission: it is to compare each app’s current access with the feature you actually use, then choose a narrower setting when available. Android and iPhone offer different controls, and neither permissions screen reveals everything a company does with information already collected.

## Why a permission review is different from an app-store privacy label

A store privacy label summarizes developer-reported data practices before installation. A permission review asks a narrower, operational question: which capabilities can an installed app access now, and are those capabilities still justified? Unhyd's existing [guide to app privacy labels](https://unhyd.com/article/how-to-read-app-privacy-labels/) explains the first task. This guide covers the second, including changes you can make after months of use. Neither exercise independently audits a developer's servers, advertising relationships or data retention.

## Start with the apps you actually use

Open the list of installed apps and identify applications you no longer recognize or need. Do not assume unfamiliar system components are malicious; manufacturers and workplaces may install legitimate services. Start with third-party apps whose functions you understand. Review permissions for location, camera, microphone, photos, contacts and nearby devices, depending on the operating system. The purpose is to find access that no longer matches a real feature, not to deny every permission indiscriminately. A navigation app may need location during a trip; a photo editor may need selected images; a video-call app may need microphone access while a call is active. The question is whether the access is proportionate to the task.

## How to check app permissions on Android

Google's [Android permission instructions](https://support.google.com/android/answer/9431959?hl=en&ref=unhyd.com) describe two useful routes. To review a specific app, open Settings, choose Apps, select the app, and open Permissions. To review by data type, use the device's Permission manager under Security & privacy or Privacy, depending on version. Exact menu labels vary by manufacturer and software version. For each sensitive permission, review the available options: for example, location may offer approximate versus precise access and access only while using the app. Some permissions have an Ask every time option. Select the narrowest option that still supports a feature you genuinely need. Test that feature afterward rather than assuming the change had no consequence. Google also documents an unused-app setting that can pause app activity and remove permissions for apps you have not used for a while. Verify whether it is enabled on your device instead of assuming every Android phone behaves identically.

## How to check app permissions on iPhone

Apple's [iPhone permissions guide](https://support.apple.com/en-lamr/guide/iphone/iph251e92810/ios?ref=unhyd.com) directs users to Settings > Privacy & Security, where selecting a category such as Photos, Contacts or Microphone shows the apps that requested access. Review access category by category, especially for apps installed long ago. Where the operating system offers a narrower selection—such as limited photo access or a less precise location—consider it when it serves the task. Apple also documents App Privacy Report, which shows how apps use granted permissions and certain network activity. If the report is not already enabled, turn it on; it begins collecting information only after activation, so it cannot reconstruct earlier activity. Availability and presentation depend on software version and settings. The report is a useful prompt for questions, not proof that a listed connection is improper. See [Apple’s App Privacy Report explanation](https://support.apple.com/guide/personal-safety/app-privacy-features-in-apple-products-ipsd4dac4a2c/1.0/web/1.0?ref=unhyd.com). If you revoke a permission and a feature breaks, return to the relevant setting and decide whether the benefit justifies restoring access.

## Use a three-question decision test

For each permission, ask three questions. First: what exact feature needs it? “Better experience” is less informative than “attach a selected photo to a message.” Second: when does that feature need access? A one-time scan does not necessarily justify ongoing camera or location access. Third: can a narrower alternative work? Entering a city manually, choosing individual photos or permitting access only while using the app may preserve the benefit. These are editorial decision questions, not a rating of any named app. They are deliberately applied one permission at a time, because a single app can have legitimate and unnecessary permissions simultaneously.

![Three-column decision framework asking what feature needs a permission, when access is needed, and whether narrower access would work - How to check app permissions on Android and iPhone](https://storage.ghost.io/c/df/e4/dfe4d080-643c-453a-8a60-0452bdbc0efd/content/images/2026/11/app-permissions-three-question-review-framework.png)

Three questions for reviewing each app permission, based on Apple and Google platform guidance. Graphic: Unhyd.

## Location, microphone and photos deserve separate attention

Location access can reveal routines as well as support maps, deliveries and local information. Review whether an app needs precise coordinates or only an approximate area, and whether background access is essential. Microphone and camera access may be expected in communication or recording apps but unusual in unrelated utilities. Photo-library access can cover more personal material than the one image you intend to share; where supported, select specific photos rather than an entire library. Contacts permissions can expose information about other people, not only you. For sensitive wellness and medical apps, Unhyd’s [health app privacy checklist](https://unhyd.com/article/health-app-privacy-practical-checklist/) covers the additional questions about linked services and data sharing. Do not interpret a permission grant as proof that an app has used or transmitted all available information. Equally, removing a device permission does not retroactively delete data already collected or necessarily stop all other forms of data collection.

## What the settings cannot tell you

Operating-system permissions regulate particular device capabilities. They are not a comprehensive description of information you type into an app, data generated by your activity, information provided by another service, or what a company retains after collection. The [FTC's analysis of data-broker cases](https://search.ftc.gov/policy/advocacy-research/tech-at-ftc/2024/03/ftc-cracks-down-mass-data-collectors-closer-look-avast-x-mode-inmarket?page=0&ref=unhyd.com) illustrates why a seemingly understandable location permission does not answer every question about subsequent sharing and advertising use. Read the developer's policy and account controls when the stakes are high. A privacy dashboard and a privacy policy answer different questions; neither alone establishes a complete picture.

## If an app looks suspicious, consider safety before removing it

Unexpected permissions can result from feature changes, a forgotten grant or unfamiliar software; they are not, by themselves, proof of surveillance. If you suspect coercive monitoring by an abusive person, the response is different from ordinary digital housekeeping. The [FTC cautions](https://consumer.ftc.gov/consumer-alerts/2021/09/spyfone-barred-selling-stalking-apps-secretly-monitor-phone-activity?ref=unhyd.com) that removing suspected stalkerware can alert an abuser and recommends developing a safety plan with a qualified counselor before taking action. For ordinary unwanted apps, review the developer and account, remove permissions, uninstall if appropriate and separately investigate account deletion or retained data. Deleting the icon does not guarantee deletion of information held by the service.

## A practical 15-minute review routine

Begin with your most sensitive categories: location, microphone, camera, photos and contacts. Spend several minutes reviewing apps you no longer use, then inspect apps that have broad access relative to their functions. Change only permissions whose purpose you understand, and test the affected features. Record any app that needs follow-up because its policy, workplace requirements or device behavior is unclear. Finally, schedule another review after a major phone upgrade, installation of a sensitive app, or a meaningful change in your routine. Before selling or trading in a phone, follow Unhyd’s separate [device handoff checklist](https://unhyd.com/article/how-to-prepare-phone-for-trade-in/); changing app permissions is not a substitute for securely preparing the device. There is no magic interval that guarantees privacy. The value comes from repeating a manageable decision process and recognizing that app permissions can drift away from the reasons you granted them.

## The bottom line

Checking app permissions is not a hunt for a perfect all-denied phone. It is a way to match current access with current needs. Use Android or iPhone settings to inspect grants, narrow them where the operating system permits, test the features you care about, and read separate data-practice disclosures for questions the settings cannot answer. A well-judged permission decision can reduce unnecessary exposure without pretending that a settings screen audits everything an app does.