A permission list tells you which apps can use the camera or microphone. The Privacy Dashboard and green sensor indicator tell you which apps did use them recently. Checking both views is the quickest way to separate an old permission you forgot about from activity happening now.
See every app with camera permission
Open Settings, Security & privacy or Privacy, Permission manager, then Camera. Android groups apps by allowed and not allowed; some versions also distinguish “while using” and “ask every time.” Review video calling, camera, document scanning, identity verification, social, and browser apps. Remove access from anything whose camera feature you do not use.
Repeat the inventory for microphone access
Open Microphone in Permission manager. Calling, voice recorder, assistant, accessibility, keyboard dictation, and meeting apps may have legitimate reasons. Games, shopping tools, and utilities should be able to explain voice access through a feature you recognize. Prefer “while using” or “ask every time” when available.
Use the Privacy Dashboard for recent history
Open Privacy Dashboard and select Camera or Microphone. Android 12 typically shows a shorter history, while later versions may offer up to seven days. Tap an event to see the app and change its permission. A dashboard event is not automatically suspicious: opening an in-app camera, recording a voice message, scanning a QR code, or joining a call should create one.
Investigate events at times you were not using a relevant feature. Compare them with call history, meeting times, voice typing, camera uploads, and browser permissions. Note the time and app before changing settings so you can tell whether the behavior stops.
Understand the green indicator
On Android 12 and later, a green indicator appears near the top-right when an app uses the camera or microphone. Swipe down and tap it to identify the app or service, then tap again to manage access. The indicator may represent a legitimate foreground use. It is valuable because it gives immediate attribution instead of requiring guesswork.
Use global sensor switches when you need a hard pause
Add Camera access and Microphone access to Quick Settings if supported. Turning one off blocks that sensor for apps until you restore it. This can be useful during a confidential conversation or while investigating unexpected use. It will also break calls, scanning, voice input, and recording, so treat it as a temporary device-wide control rather than a permanent substitute for per-app permissions.
Remember browsers and embedded web pages
A browser may have Android-level camera permission while individual websites have their own site permissions. Review camera and microphone access in the browser’s Site settings and remove old meeting, test, or support sites. The Android indicator may name the browser, not the webpage responsible, so both layers matter.
Check related access
An app that records media may also hold photo, storage, notification, overlay, or accessibility access. Those do not prove recording, but the combination changes potential impact. Review Special app access for an unfamiliar app, especially display over other apps, accessibility, device admin, and notification access.
What to do when access is unexpected
- Capture the time and app shown by the indicator or dashboard.
- Close the app and see whether the indicator disappears.
- Change the permission to “ask every time” or “don’t allow.”
- Review browser site permissions if the browser was named.
- Check Play Protect and the app’s installation source.
- Uninstall the app if its behavior and purpose cannot be reconciled.
If you entered credentials into a suspicious overlay or were recorded in a sensitive situation, handle the account or personal-safety issue separately. Permission removal prevents future access but cannot retrieve data already transmitted.
Avoid false alarms
Voice typing can activate the microphone through the keyboard or a system speech service. Camera scanning may be delegated to a system component. Calls can keep the microphone active after you switch apps. Manufacturer services can have unfamiliar names. Reproduce the action and consult the phone maker’s documentation before removing a system component.
A five-minute routine
- Review allowed camera and microphone apps monthly.
- Check Privacy Dashboard after an unexplained green indicator.
- Delete old browser site permissions.
- Use foreground-only access.
- Remove permissions from unused apps.
- Keep sensor Quick Settings tiles available for temporary control.
The useful question is not whether any app has camera or microphone permission. It is whether every allowed app has a current, proportionate reason—and whether recent history matches what you actually did.
Example: the microphone appears active after leaving a meeting
First confirm whether the meeting is still connected in the notification shade. Some apps keep a call running when you return to the home screen. End the call explicitly, then watch the indicator. If it remains, tap it to identify the responsible package, force close that app, and review its microphone permission. This sequence distinguishes a background call from unrelated recording without guessing.
When hardware indicators and Android history disagree
Some phones, headsets, and camera accessories have their own lights or companion services. Android’s dashboard records access mediated through platform permissions, but manufacturer implementation and system services can affect the label you see. Update the phone, reproduce the event, and consult the maker’s documentation. If the indicator recurs with an unknown third-party app, remove its permission and investigate the installation source before using sensitive accounts.
Official references
Google documents the camera and microphone indicator, the Privacy Dashboard, and permission controls.