Maintenance
Mobile app permissions checklist for removing an app: camera, microphone, photos, contacts and location
Before you delete a mobile app, revoke its camera, microphone, photos, contacts and location access, clean up what it left and close the account.
What to take away
- Uninstalling usually leaves the account and server-side data intact, so removal is three actions: uninstall, close the account, delete the data.
- Save local files and secure your account recovery options before you close anything.
- Revoke camera, microphone, photos, contacts and location access first, then look at what the app already copied.
- Remove special access, device-administrator roles, connected apps and tokens.
- Retest calls, alarms, navigation, health and safety alerts afterwards.
Uninstall, close the account, delete the data
Removing an app is three separate actions: uninstall it, close the account and delete the data. Uninstalling usually leaves the account and server-side data intact, so a vanished icon proves nothing. Treat each step as its own task and keep the confirmation for each.
Order matters. Save what you need locally, secure the way back into your accounts, then revoke access, then close and delete. Doing it the other way round can leave you without the files or the email you still need.
Save your files and secure recovery first
Preserve local files and your account recovery options before anything else, because closing an account can cut off the email you need. Then write down who the app belongs to, since a deletion request has to reach the right company.
App identity and source
- Record app name, developer, package, version
- Confirm installation source is authorized
- Check update history and current support
- Know account and feature purpose
- Save dated store label and privacy notice
- Know managed-device restrictions and admin contact
- Developer name and contact details match the app you installed.
- Version and last update date are recorded.
- Local files and exports are saved somewhere you control.
- Work profile or managed-device rules are known before you remove anything.
Revoke each permission before you remove the app
Revoke access one permission at a time in the phone's own settings, because in-app menus often hide or soften these controls. On iPhone open Settings > Privacy & Security. On Android open Settings > Privacy > Permission manager.
| Permission | Revoke to | What may remain afterwards |
|---|---|---|
| Camera | Off | Scans, clips and images the app already stored |
| Microphone | Off | Transcripts and recordings the app already stored |
| Photos | Off | Copies of images the app already holds |
| Contacts | Off | Contacts and events synced to the service |
| Location | Off | Location history, check-ins and shared location |
| Nearby devices | Off | Paired accessories and companion apps |
| Notifications | Off | Marketing messages from the service |
California's privacy agency advises checking your smartphone's privacy settings to see what data apps can access. It suggests disabling unnecessary permissions or removing apps that ask for more access than they need to work. Use that as the test for each row.
Camera and microphone come first, because camera and microphone access is the pair most often granted by accident. Note which feature used each one before you switch it off.
Camera and microphone access
- Map camera access to a chosen feature
- Map microphone access to a named function
- Match recent-use indicators to expected activity
- Deny access when feature is not in use
- Control retention of recordings and cloud copies
- Document unexpected indicators with evidence
- Camera access maps to a feature you used, such as scanning or video calls.
- Microphone access was limited to calls, recording or voice input.
- Clips, transcripts and recordings have a stated retention period, or you ask the developer.
- Unexpected activation is reported and reviewed.
Clean up what the permissions left behind
Revoking access is not the same as deleting files the app already copied. Shared images may carry coordinates and visible location clues, and screenshots can expose codes, messages or account details. Check where downloads and app-created files are stored.
Contacts and calendars need their own cleanup. Synced contacts and events should be removed after the app goes, and it is worth checking whether the app only read entries or also added and edited them.
Location is the permission with the longest tail. Look at precise versus approximate location to see what the app could infer, then review location history, check-ins, photo geotags and saved addresses separately.
Nearby device access can support proximity and location-based features. Recognize each paired accessory and companion app, and remove unused pairings before resale.
Remove special access and connected apps
Special access comes off before the app does. Device-administrator roles and similar privileges can block an uninstall or keep running after you think the app is gone, so remove them safely first.
- Remove special access and device-administrator roles.
- Revoke connected apps, tokens and shared access.
- Review background app refresh and battery exceptions on their own.
- List the analytics, advertising, crash, map and payment recipients the app used.
If the app handled health data, note the rules. In the United States, the FTC has brought cases about health data collected through apps and connected devices, and its health privacy guidance sets out how it treats that data.
Close the account and ask for deletion
Account closure and data deletion are not part of uninstalling. Use the service's account and deletion controls, and keep the confirmation. State privacy laws add access and deletion rights for some residents, so name your state in the request.
A deletion-request template is in the mobile app privacy permissions guide. For a wider check of what a service collects, shares and keeps, work through the personal data lifecycle checklist.
Retest and confirm
Retest calls, alarms, navigation, health and safety alerts once the app is gone. Removing a permission or an app can quietly switch off something you relied on, and it is better to find that out on the same day.
If you only want to tighten an app you keep, follow how to audit mobile app permissions for a repeatable routine that covers background access.
