Android Privacy Checklist: Settings Worth Reviewing on Your Phone
Review Android permissions, lock-screen previews, app access and recovery settings with a practical checklist that allows for device differences.
An Android privacy review works best when you start with the apps you use, not a list of switches to disable blindly. Maps needs location for directions. A video-call app needs a microphone during a call. The useful question is whether an app has more access, for longer, than the job requires.
Android menus differ between manufacturers and versions. Use the Settings search box when a label below is not in the same place on your phone. Change one area at a time and test the affected app before moving on, especially when the phone is used for work or accessibility support.
Start with the lock screen
Lock the phone and look at it as someone standing beside you would. Check whether message previews, calendar details or one-time codes are visible. Ask someone you trust to send a harmless test message rather than using a real sensitive conversation as your experiment.
In Settings, search for lock-screen notifications. Android's notification guide explains options for hiding sensitive content or turning off selected app notifications. Choose the least revealing setup that still lets you notice important calls and reminders.
Then review the screen lock itself and the delay before it engages. A strong code is less useful if the phone remains unlocked for long periods after you set it down. Do not use a code based on a public birthday or a simple repeated pattern.
Check any convenience feature that keeps the phone unlocked near another device or place. Extend Unlock, formerly Smart Lock, has its own settings and limitations. Keep only the conditions you deliberately want rather than inheriting an old configuration from a watch you no longer use.
Review permissions by category
Search Settings for Permission manager. Start with location, microphone, camera, contacts and photos. Looking by permission type makes it easier to spot an unexpected app than opening every installed app at random.
Google's permission instructions also describe the app-by-app route through Settings, Apps and Permissions. Depending on the permission and device, choices can include access only while using the app, asking each time or denying access.
For each app, name the feature that needs the permission. A messaging app may need a microphone for voice messages but not for reading a text conversation. A shopping app may work with a manually entered delivery area instead of continuous location access.
Prefer a narrower option where it fits. Do not grant full photo-library access simply because you need to attach one picture when the interface offers a limited selection. If denying access breaks a feature you need, restore the relevant permission rather than enabling everything.
Treat background location as a separate decision
Open the list of apps with location access and pay particular attention to those allowed to use it when they are not in the foreground. Think about each actual function: navigation, a deliberately enabled location-sharing service or a feature you no longer use.
Approximate location may be enough for some uses; precise directions and certain safety functions may need more. Test the result instead of treating one setting as correct for every app.
Remember that disabling an app's location permission does not erase locations it previously stored. Account history, shared location features and information visible in photos require separate checks. Our digital-footprint guide covers that wider view.
Do not disable a feature relied on by another person without discussing it. Shared arrangements should be intentional, including when they end.
Learn the camera and microphone indicators
On supported Android versions, a green indicator appears when an app uses the camera or microphone. Google's indicator guide explains how to open it and identify the app, along with the available quick controls.
Use this as a practical check after a call. If the indicator remains visible, inspect which app is responsible rather than assuming the device is compromised. The app may still be in a call or recording mode you did not fully close.
A system-wide camera or microphone block can be useful, but remember you enabled it when troubleshooting the next call. Keep accessibility and communication needs in mind before making a global change.
For browser-based meetings, there may also be a separate site permission inside the browser. The browser-permission checkup helps avoid confusing a website setting with an Android app setting.
Remove apps you no longer need
Review installed apps and identify old trials, one-off event apps and tools whose purpose you cannot remember. Open the app's account settings first if you need to export data or end a subscription. Uninstalling an app is not the same as deleting its online account.
Check sensitive special access as well, such as notification access, accessibility services or device administration. These settings are more consequential than an ordinary permission prompt. Remove unfamiliar grants carefully, and ask your administrator before changing a work-managed phone.
Do not install a “privacy cleaner” just to perform this review. Use the operating system's own controls first. Extra apps can introduce their own permissions and accounts without solving the underlying issue.
Keep a short note of changes that affect everyday features. It is easier to reverse one deliberate change than to diagnose ten unexplained toggles later.
Check the accounts behind the phone
A permission review does not tell you everything about the cloud accounts signed into the device. Review the accounts used for email, photos, browser synchronization and backups. Confirm which collections are syncing and who can access shared folders or albums.
Use browser-sync privacy for saved history and credentials. Use family photo sharing for albums that should reach only selected people.
Check account recovery before changing your main email or removing a device. A phone can be both the place you receive a recovery code and the device you are trying to recover. Keep an independent route available.
The lost-phone preparation guide turns that dependency into a practical plan you can test while the phone is still in your hand.
Finish with a short real-use test
Make a call, take a photo, send a file and use navigation in the way you normally would. Confirm that useful features still work and that denied permissions are requested only when appropriate.
Revisit the settings after installing a new app, changing phones or accepting a major app update that requests new access. You do not need to repeat the whole review every day.
Your finished checklist should identify fewer unnecessary permissions, a lock screen that reveals less, known cloud accounts and a working recovery route. Those are concrete improvements you can verify without turning the phone into something awkward to use.
Sources and further reading
- Android: Change app permissions Consulted 28 September 2026.
- Android: Camera and microphone indicators Consulted 28 September 2026.
- Android: Notification and lock-screen controls Consulted 28 September 2026.
- Android: Extend Unlock settings Consulted 28 September 2026.
Consult the linked documentation for current details. Settings, availability and interface labels may change.
Spotted something that needs correcting? Send a correction with this article’s title and the relevant source.