Camera In-Use Privacy Check

Worried something else already has your camera locked before a call — the Camera In-Use Privacy Check settles it in one click. Press Run Check and it tells you whether your webcam is free, held by another app, or blocked at the permission level, rather than leaving you to guess from the indicator light alone. A platform-by-platform guide to what that light actually means on Windows, macOS, Android, and iOS sits alongside the result. Use the flip webcam image test to check your hardware is actually working the way you expect, right from this page.

Camera In-Use Privacy Check

Tests whether your camera is free to use right now, or already held by another app

Click Run Check. This briefly requests camera access and releases it immediately — nothing is recorded or previewed.

What This Actually Tests

Browsers don't let any website see which app is using your camera — only whether a new request to use it succeeds or fails. This check can't detect spyware or confirm anything is secretly recording you. What it can tell you: if the request fails with "already in use," some other running application currently has an exclusive lock on the camera — that's usually a video-call app left open in the background, not something malicious.

If you're worried about unauthorised access, the indicator light next to your camera is the most reliable signal — see the guide alongside this.

Indicator Light & Privacy Panel Guide

WindowsGreen LED lights whenever any app uses the camera. Check Settings → Privacy & Security → Camera for which apps have permission.
macOSGreen LED next to the camera lights whenever it's active. Check System Settings → Privacy & Security → Camera.
AndroidA green dot appears in the status bar when the camera or mic is active. Check Settings → Privacy → Permission manager → Camera.
iOSA green (camera) or orange (mic) dot appears at the top of the screen. Check Settings → Privacy & Security → Camera.

Ever glanced at your phone and noticed the camera indicator light glowing when you weren't actively using any app — or wondered whether a recently installed app might be capturing camera and microphone access without your knowledge? A Camera In-Use Privacy Check gives you the clarity you need: real-time and historical visibility into exactly which app is using your camera, so you can make confident decisions about which apps deserve your trust. In a world where unauthorized camera access and digital surveillance are genuine concerns for mobile users, understanding the full picture of your device's camera activity has never been more important.

How Camera In-Use Privacy Check Works: Active Monitoring, In-Use Indicators, and Usage History

Understanding Camera Permissions and What Camera Access Actually Means

Every time an app wants to use your camera, it must first obtain explicit authorization — a runtime grant that you provide either during installation or the first time the app requests it. This is not a passive formality. A camera permission prompt appears on screen, asking you to allow or deny access. Once granted, the app can call on the camera hardware whenever it is in the foreground — and, unless restrictions apply, sometimes when an app in background is still running too. Use the view webcam in fullscreen mode to check your hardware is actually working the way you expect, right from this page.

Apps legitimately need camera access for taking photos, recording videos, scanning QR codes, video calling, and augmented-reality features. However, not every app that requests access uses it responsibly. Some may access the camera in ways that go beyond their stated purpose, making it essential to perform a regular check of which access rights you have granted and to which apps.

On both iOS and the Android platform, the camera is treated as a user-sensitive resource. No app can access the microphone or camera without your explicit consent. When authorization is required — for example, when a third-party app first tries to open your camera — the OS presents a standardised dialog that you must actively accept. This foundational layer of user consent is the first line of defence in your mobile data-protection strategy.

How the Camera Indicator Light and System Alerts Work

Both the Apple and Android platforms have embedded visual privacy indicators directly into the operating system so that any camera in-use privacy check can happen at a glance — no third-party tools required.

On iOS (version 14 and later), whenever an app using camera hardware or microphone is active, a small orange or green dot appears in the top-right corner of the display — often called the privacy dot or camera dot. A green dot signals active camera use; an orange microphone indicator signals active microphone use. This in-use indicator persists whether you are inside the app, in another app, or on the Home Screen. Swiping down to Control Center surfaces a readout that names the app that most recently used your camera or microphone — a clear signal for microphone monitoring and camera oversight — giving you an immediate answer to find out which app is using camera at any moment.

On the Android 12 release and later, a green camera dot and a separate microphone dot appear in the status bar (top navigation bar) whenever an app is actively accessing those sensors. Tapping the indicator icon in the status-bar icons area opens a notification dialog — also called a usage dialog — that lists all apps currently accessing the camera, microphone, or location. This is the Android equivalent of the iOS Control Center readout. The device displays indicator information in real time, and the home-screen indicator remains visible even when you navigate away from the triggering app.

The distinction the system draws is important: an active icon appears when access is ongoing. Once the app stops, the icon transitions to a smaller dot that persists briefly, signalling recently used camera resources rather than current use. Tapping the indicator at that stage opens the same access view, but with a label noting that the app recently used the resource rather than currently using it.

App Privacy Report: Reviewing Which Apps Access Your Camera Over the Last Seven Days

For a deeper historical audit beyond real-time indicators, Apple's App Privacy Report is the most powerful on-device tool available to iPhone and iPad users. Once you enable it via the privacy and security settings (Settings → Privacy & Security → App Privacy Report), the report begins logging every instance of camera usage, microphone use, location access, contacts access, and photos access for a rolling window covering the last seven days.

The App Privacy Report view gives you a per-app breakdown: you can see exactly when each app accessed the camera, microphone, location, contacts, or photos on your sensitive hardware. This seven-day window is sufficient to surface patterns — for instance, if a social media app is repeatedly triggering the camera at unusual hours.

The Android equivalent is the Privacy Dashboard (introduced in the Android 12 release), accessible at Settings → Privacy → Privacy Dashboard. It displays a 24-hour timeline of which apps accessed the camera, microphone, and location, along with the access duration for each event. You can tap any entry to jump directly to the relevant app-access screen, enabling one-tap control.

Process Flow: How Your OS Detects and Logs Camera Activity at the System Level

Understanding the technical process flow behind camera detection illuminates why these privacy indicators are so reliable. The System UI — the persistent layer that renders your status bar, control panel, and overlays — is the component responsible for showing in-use indicators. Here is how the end-to-end flow works on the Android platform:

  1. App requests private data: An app calls a protected API that requires camera or microphone access.
  2. System checks access rights: The OS verifies whether the app holds the necessary runtime grant. If allowed, the system notifies the data source and records the event in app op records via the ops manager service.
  3. Data source responds: The camera hardware delivers the image feed (or audio data for microphone) to the requesting app.
  4. System UI reacts: The System UI listens for new app-ops entries and displays the appropriate icon in the top navigation bar.
  5. User taps the indicator: The System UI requests usage data from the access manager and presents the usage dialog showing which apps are accessing the camera, microphone, or location.

The PermissionController component is responsible for populating the dialog with recent usages and active usages. The System UI enables this feature conditionally via the device configuration flag privacy/mic_camera_indicators_enabled, which must be set to true for the indicators to appear. This device configuration switch is part of a two-phase deployment: first the feature is delivered, then it is enabled via this flag — ensuring separate delivery and activation across OEM builds.

The core App Ops API calls that drive camera access monitoring are:

  • AppOpsManager.startOp(OP_CAMERA, uid, packageName) — called when an app begins accessing the camera. This creates an active time window in the system server and triggers running-usages logging. The startOp call is the entry point for all session-based tracking.
  • AppOpsManager.stopOp(OP_CAMERA, uid, packageName) — called when the camera session ends. The System UI keeps the indicator visible for at least 5 seconds after this call fires (or 10 seconds for location), ensuring brief accesses do not go unnoticed. Invoking stopOp closes the active window cleanly.
  • AppOpsManager.noteOp(OP_CAMERA, uid, packageName) — used for discrete, non-streaming accesses. When this method fires, the indicator appears for a minimum of five seconds (camera/microphone) or ten seconds (location). Each noteOp call is logged individually in the ops records.

The System UI subscribes to two listeners for real-time camera monitoring:

  • AppOpsManager.OnOpActiveChangedInternalListener — fires whenever a session-start or session-end call transitions the activity status of a camera or microphone op. This enables real-time indicator updates without polling.
  • OnOpNotedListener — fires on each discrete-access call, covering API calls that do not maintain a continuous session.

When the System UI receives an incoming op event, it first checks whether the caller is a system app or a non-system app. For a non-system app: if the op is for the microphone, the system checks whether the microphone-muted toggle is active; if it is for the camera, it checks whether the camera-enabled state is active. Only when the relevant toggle is enabled does the indicator-displayed logic proceed and show the icon. The PermissionController then loads all recent usages and checks which are running usages (marked as running) or fall within the active time threshold: within five seconds for microphone/camera, and within ten seconds (recent window: fifteen seconds for mic/camera, twenty seconds for location) for the recent-access label.

The PermissionManager (accessed via the PermissionManager system service) serves as the data source that bridges PermissionController and the System UI. Together, these system components implement usage logging and access tracking in a way that is fully open source within AOSP, satisfying the CDD requirement for platform integrity.

The mic-camera indicators system is enabled by default on compatible devices, and the microphone stack used during phone calls is handled with separate delivery via Telephony to ensure that call audio does not generate misleading camera alerts. UI transitions from icon to dot occur automatically after the active window expires, and an intent dialog is launched via PermissionController when the user taps the icon — completing the full feedback loop of hardware-access visibility.

App Tracking Transparency and Camera Data

Apple's App Tracking Transparency (ATT) framework adds a separate consent layer on top of basic access rights. Even if an app legitimately holds camera access, ATT governs whether that app can share image output — or any other personal data — with third-party advertising networks, analytics providers, or data brokers. Starting with iOS 14.5, every app must display an app tracking prompt before it can follow you across apps and websites owned by other companies.

This matters for captured image output specifically because social media apps like those offering Instagram or Facebook camera settings may capture metadata about your camera usage — the content you photograph, the frequency with which you open the camera — and potentially use it to build behavioural profiles. ATT's openness and control mechanism ensures that this information sharing requires your active consent, not just a buried clause in a terms-of-service agreement. Behavioural surveillance without permission is prohibited under the ATT framework, and violating apps risk removal from the marketplace.

Location Data Tied to Camera Usage

Camera usage and geographic data are more intertwined than most users realise. When an app holds both camera rights and location rights, it can embed precise GPS coordinates as EXIF metadata directly into every photo you take — effectively creating a location marker for every image you share. Even without EXIF data, apps that access both sensors simultaneously can correlate your position events with camera-access events to infer movement patterns and daily routines.

On the Apple platform, the App Privacy Report shows location access and camera access in the same timeline, making it easy to spot suspicious co-access patterns. On the Android side, the Privacy Dashboard's timeline similarly surfaces location-dot events alongside camera-dot events. If you see an app repeatedly triggering both sensors in the background — especially when you haven't interacted with it — this is a red flag for potential surveillance or invasion of confidentiality, and warrants immediate review and revocation.

Location tracking via camera metadata is also why it matters to disable location-tagging within camera apps unless you specifically need it. Geo-tagged images posted to public platforms can expose your sensitive information — home address, workplace, frequently visited locations — to anyone who examines the file's embedded geodata.

Pasteboard Permission and Camera Interactions

A subtler surface adjacent to camera use is the pasteboard (clipboard). On iOS 14 and later, apps must receive explicit consent before reading your clipboard — preventing the silent interception of passwords, addresses, or other private data you copied from another app. This matters in camera workflows because some apps automatically read the clipboard when launched, looking for URLs, addresses, or QR-code text that might have been copied from another context.

The access notification that the platform displays when an app reads your clipboard is analogous to the camera indicator: a brief banner at the top of the screen informs you that the app used your clipboard. Together, clipboard controls and camera controls create a coherent system of user oversight over all the sensitive input channels on your device. If an app simultaneously accesses the camera and the pasteboard without a clear reason, treat that as a concern worth investigating.

Analytics: What Your Device Tracks Silently in the Background

Both the Apple and Android platforms offer opt-in analytics that collect aggregated usage statistics about how you use your device, including which app-usage patterns correlate with hardware-access events. On Apple devices, you control this via Settings → Privacy & Security → Analytics & Improvements. Apple applies Differential Privacy techniques to this on-device data collection, ensuring that individual behaviour cannot be reverse-engineered from the aggregated dataset.

Importantly, analytics data is distinct from the App Privacy Report: analytics reports go to the platform vendor (Apple or Google), whereas the App Privacy Report is stored entirely on your device and never leaves it. For users with heightened protection concerns, disabling analytics opt-in is a straightforward step that eliminates this particular data-sharing channel without affecting core device functionality.

App-behaviour analytics collected by third-party SDKs embedded inside apps are a separate concern — these are governed by App Tracking Transparency on the Apple platform and by data-protection regulations on the Android side. Nutrition labels in app stores now require developers to self-report exactly which analytics data types they collect, giving you an informed decision pathway before you even download an app.

Taking Control with In-Use Indicators and Privacy Settings: A Camera In-Use Privacy Check for Your Digital Privacy

Managing Camera Permissions on iOS: Privacy and Security Settings Step-by-Step

On the Apple platform, your primary tool for managing camera access rights is the Settings app under Privacy & Security. Here is a complete walkthrough — this is Figure 3 for iOS: Use the camera latency and delay checker to check your hardware is actually working the way you expect, right from this page.

  1. Open Settings on your iPhone or iPad.
  2. Scroll down and tap Privacy & Security.
  3. Tap Camera. You will see every app that has ever requested camera access along with its current status (On or Off).
  4. For each app, toggle the switch off to revoke unneeded access rights immediately. The change takes effect without requiring a restart.
  5. Return to Privacy & Security and tap Microphone to perform the same microphone-access audit.
  6. Tap Location Services to cross-reference which apps hold both camera and location rights — a combination that warrants extra scrutiny.
  7. Enable App Privacy Report (also under Privacy & Security) to begin logging camera-usage history going forward.

The iOS approach gives you per-app toggle control at the OS level, completely independent of anything the app itself offers. Even if an app does not provide its own in-app settings for camera control, iOS enforces your choice at the hardware level — camera access disabled in iOS settings means the app genuinely cannot open the camera, period. No workaround exists at the app layer.

For apps that serve legitimate but narrow purposes — for example, a restaurant-review app that only needs the camera for uploading food photos — consider changing the access setting to "Ask Next Time" rather than a permanent grant. This gives you a per-session prompt each time the app wants to open the camera, maintaining continuous awareness.

Managing Camera Permissions on Android: PermissionController and Privacy Dashboard

On the Android platform, camera access rights are managed through a layered system that begins at Settings → Apps. Here is the complete walkthrough — the Android half of Figure 3:

  1. Open Settings and tap Apps (or Apps and notifications on older versions).
  2. Tap See all apps, then select the specific app you want to audit.
  3. Tap Permissions. You will see every access right the app holds, including Camera, Microphone, and Location.
  4. Tap Camera and choose from: Allow all the time, Allow only while using the app, Ask every time, or Don't allow. Select Don't allow to fully revoke access for that app.
  5. Alternatively, navigate via Settings → Privacy → Permission Manager (the PermissionController UI) → Camera to see a categorised list of all apps with camera access — divided into "Allowed all the time," "Allowed only while in use," "Ask every time," and "Not allowed."
  6. On Samsung devices, Device Care provides additional app-monitoring insights and can surface unusual activity patterns.
  7. Use the Privacy Dashboard (Settings → Privacy → Privacy Dashboard) to review access rights and their usage timeline over the past 24 hours.

The Android 12 release and later also introduce hardware-level camera-toggle and microphone-toggle switches accessible from the notification shade. Pulling down that panel and tapping the Camera icon disables the camera sensor for all apps system-wide — applications are blocked from using it even if they hold the relevant access rights. This is the fastest possible blocking mechanism, ideal for meetings or high-sensitivity situations. The same approach applies to the microphone toggle. When the toggle is off, the camera-blocked state is enforced at the hardware abstraction layer, and any app attempting access receives an empty or blocked stream rather than live image data. No app can access the camera during this state, regardless of what rights it holds.

Touch ID, Face ID, and Camera Security Interactions

Touch ID and Face ID introduce a camera-adjacent protection dimension that many users overlook. Face ID uses the TrueDepth camera system — a dedicated infrared camera and dot projector — to perform biometric authentication. This camera operates under a completely separate system framework from the regular camera: no third-party app can directly access the TrueDepth hardware. Apps can request Face ID authentication results via the Local Authentication framework, but they receive only a binary pass/fail result — never the underlying face scan or raw sensor output.

This architecture means Face ID is not a confidentiality risk in the same way that a general camera grant is. The biometric data never leaves the Secure Enclave, is never stored on Apple servers, and cannot be accessed by the operating system or any application — making it a form of protection built in at the silicon level. Still, it is worth understanding that locking an app with Face ID does not restrict that app's existing camera access — it only controls entry to the app. Access rights must be managed separately in Privacy & Security settings.

Sensitive Content Warning and Camera-Related Privacy Risks

Apple's Sensitive Content Warning is a camera-adjacent safeguard that processes images and videos on-device before displaying them, blurring content that may contain nudity. This feature applies in Messages, AirDrop, FaceTime video messages, and the Phone app's Contact Poster feature. All processing happens locally — neither Apple nor any third party receives the image content — making it a strong example of data protection by design.

From a camera-access standpoint, Sensitive Content Warning is relevant because it intercepts camera-captured or camera-shared media before it reaches the recipient, providing an additional filter that reduces the risk of sensitive material being exploited via social engineering. Enable it via Settings → Privacy & Security → Sensitive Content Warning. It is optional and defaults to off, but it is worth enabling for digital safety in contexts where you receive images from untrusted sources.

Lockdown Mode: Maximum Camera Access Restriction for High-Risk Users

For users facing sophisticated, targeted attacks — journalists, activists, executives, and others who may be targeted by spyware — Apple's Lockdown Mode provides the most aggressive level of hardening available on a consumer device. Lockdown Mode, available on iOS 16 and later, sharply restricts a wide range of functionalities to reduce the attack surface against mercenary surveillance tools and advanced persistent threats.

In Lockdown Mode, certain camera-adjacent features are restricted: incoming FaceTime calls from unknown contacts are blocked, link previews in Messages are disabled, and specific web technologies that could be exploited via camera access are turned off in Safari. While Lockdown Mode does not globally disable the camera itself, it eliminates many of the attack vectors that sophisticated actors use to achieve unauthorized camera access through zero-click exploits. Enable it via Settings → Privacy & Security → Lockdown Mode. Proactive hardening at this level is rarely necessary for most users, but it demonstrates the depth of protection that modern platforms can provide when device integrity is paramount.

Find My and AirTag Alerts: Camera Privacy Beyond the App Layer

Physical location monitoring is as much a concern for digital privacy as camera surveillance. Apple's AirTag system is designed with openness in mind: if an AirTag that does not belong to you is detected travelling with you for an extended period, your iPhone alerts you with a notification — an access alert that prompts you to locate and disable the tag. This anti-stalking safeguard is mandatory by design and cannot be disabled by the tag's owner.

Find My, the broader device-location system, also operates with strong user-data protections: location information transmitted via the Find My network is end-to-end encrypted, meaning Apple cannot read your device's position. Find My location data is retained for only 24 hours, limiting the duration of any potential sensitive-information exposure. Understanding these mechanisms helps you maintain a complete overview of both digital and physical monitoring risks associated with your devices, reinforcing data protection across all vectors — not just app-layer camera access.

Tips to Enhance Your Camera Privacy Right Now

Privacy and Security Settings: A Step-by-Step Audit for Complete Camera Permission Control

A thorough check of your device goes beyond the camera alone. Here is a holistic audit sequence that covers the full spectrum of access rights relevant to camera-adjacent concerns — part of any robust camera in-use privacy check routine:

  • Installed apps audit: Open your app list and regularly audit what is installed. Remove unused apps entirely — an app you no longer use is an access surface you no longer need. Unrecognised apps that you do not remember installing should be removed immediately and treated as potential unauthorized-access vectors.
  • Use Screen Time (iOS) / Digital Wellbeing (Android): The Screen Time feature on iOS (Settings → Screen Time → See All Activity) lets you review historical usage patterns, including which apps have been active in the background. This can surface background camera activity that does not always appear in the App Privacy Report. On the Android side, Digital Wellbeing provides equivalent visibility.
  • Use app-specific settings: Social media apps — including those with Facebook camera settings and Instagram camera settings — embed their own in-app controls. Review each platform's camera and microphone settings within the app itself — some allow you to restrict camera access at the app layer even if OS-level rights remain granted.
  • Use third-party apps: Dedicated camera-monitor and camera-detector apps available on official marketplaces offer enhanced visibility beyond what the OS provides. Choose apps with strong data-handling practices and independently verified features, and review their nutrition labels before installing.
  • App-op review: Advanced Android users can verify app-op records directly via ADB (Android Debug Bridge) using the dumpsys appops command, which outputs a complete log of all op records including session-start timestamps, session-end timestamps, and discrete-call counts for every protected API. This level of access monitoring is particularly useful for activity review in enterprise or high-assurance environments.
  • Third-party app access audits: For any third-party app access right you grant, periodically verify that the app's stated purpose in its store listing still matches its actual behaviour. Data-protection obligations under GDPR, CCPA, and similar frameworks require developers to be accurate, but best practice demands that you verify rather than simply trust.
  • Toggle camera off globally when not in use: On Android 12 and later, use the hardware camera toggle to disable the camera sensor entirely when you are in environments where accessing the camera without permission is a risk — for instance, during confidential meetings or in sensitive locations. Re-enabling is a single tap, making this a low-friction habit with significant benefits. Note that applications are blocked from using it, so effectively no app can access the sensor while the toggle is off.
  • Monitor camera usage with notifications: Configure your device to alert you to camera use through both the OS indicator system and any third-party tool you run. Combining the indicator in the status bar with push notifications from a camera-detector app creates redundant access monitoring that is difficult for even sophisticated malware to evade without detection.

Staying informed and vigilant about your camera access rights is not a one-time task — it is an ongoing practice of digital privacy hygiene. The combination of OS-level privacy indicators, the App Privacy Report (iOS) or Privacy Dashboard (Android), regular access-rights audits, and physical safeguards like a camera cover creates a layered defence that is robust against both opportunistic overreach and more targeted unauthorized-access attempts.

Whether you are a casual mobile user concerned about which apps have camera access in the background, or someone with elevated concerns who needs to safeguard personal information against sophisticated adversaries, the tools exist at every level of your operating system to protect your data and maintain meaningful user openness over one of your device's most sensitive hardware resources. Knowing exactly when, why, and by which app your camera is being used — including catching any app using camera or microphone without permission — is both a technical feature and a fundamental expectation of data protection in the digital age. Access control starts with awareness, and awareness starts with a thorough, regularly repeated camera in-use privacy check.

Frequently Asked Questions

How can I tell if my camera is currently in use?
On iPhone (iOS 14+), a green dot appears in the top-right corner of your screen whenever an app is using the camera. On Android 12 and higher, a green camera icon appears in the status bar. If you notice this indicator when you're not actively using a camera app, check your privacy settings immediately to see which app is responsible.
Which types of apps are most likely to access my camera without me realizing?
Social media apps (Instagram, TikTok, Snapchat) and messaging apps (WhatsApp, Zoom) are among the most common camera-accessing apps because they integrate camera features deeply. Shopping apps with AR try-on features and gaming apps with face tracking are also frequent camera users. Apps sideloaded from unofficial sources carry the highest risk of unauthorized camera access.
What is the camera privacy indicator and how does it work on Android?
Android 12 introduced a green dot privacy indicator in the status bar that appears whenever an app accesses your camera or microphone. Tapping the indicator shows you exactly which app is using it. Android 12 also added the ability to disable camera and microphone access for all apps at once via Quick Settings toggles, giving you instant hardware-level control.
Can apps access my camera in the background without my knowledge?
On modern iOS and Android versions, foreground camera access is indicated visually, and background camera access is heavily restricted. However, older OS versions or improperly configured permissions may allow certain apps more latitude. Regularly reviewing which apps have 'Always Allow' camera permissions in your settings helps prevent unwanted background access.
How do I find out which apps have camera permission on my device?
On iPhone, go to Settings → Privacy & Security → Camera to see every app that has requested camera access. On Android, go to Settings → Privacy → Permission Manager → Camera. Both show a list of apps with their permission status, allowing you to revoke access for any app you don't trust or actively use for camera functions.
Does keeping my operating system updated improve camera privacy?
Yes, significantly. Each major OS update typically brings stronger privacy indicators, tighter permission controls, and security patches that close vulnerabilities exploited by malicious apps. iOS 14 introduced the camera indicator dot, and Android 12 introduced the status bar privacy indicator — features unavailable on older versions that left users with no visual warning.
What should I do if I see the camera indicator when no camera app is open?
First, check your Control Center (iOS) or swipe down the status bar (Android) — the OS will name the app currently using the camera. Go immediately to Settings → Privacy → Camera and revoke that app's access. If the behavior continues, consider uninstalling the app. On iPhone, you can also use the Privacy & Security dashboard to review recent camera access history.
Is it safe to give social media apps permanent camera access?
It's safer to grant camera access 'Only While Using the App' rather than 'Always'. Permanent camera permissions mean the app could theoretically access the camera during background processes. Most social media functions work perfectly with 'While Using' access. Review and tighten these settings every few months as app updates can sometimes reset or expand permission scopes.

Comments & Feedback