Privacy & permissions
Which Apps Are Using Bluetooth on Your Mac?
Find every app with Bluetooth permission on your Mac, learn what each can do, and revoke access from apps that don't need wireless devices.
Bluetooth is one of the newer permissions in macOS. Apple introduced explicit user control over Bluetooth in Monterey, recognizing that Bluetooth ranging can identify nearby devices, beacons, and even people — and that an app’s “I need Bluetooth for headphones” justification often stretches further than users expect.
Here’s what the permission grants, who legitimately needs it, and how to keep your list lean.
What Bluetooth permission grants
When an app has Bluetooth access on macOS 14 Sonoma or 15 Sequoia, it can:
- Discover nearby Bluetooth devices that are advertising
- Read advertising data (manufacturer, device name, beacon UUIDs)
- Connect to paired devices
- Connect to BLE devices for direct data exchange (heart rate monitors, IoT, etc.)
It does not:
- Control your Mac’s audio output (that’s a separate audio routing thing)
- Read messages your phone is sending over Bluetooth
- Use the system audio devices that pair through System Settings (those go through normal CoreAudio, not the app permission system)
The reason this is a permission at all: Bluetooth advertisements include identifiers that can track devices over time. If an app silently scans for nearby Bluetooth, it could build a profile of where you go and who you’re near. The toggle gives you control over which apps can do that.
Where to find the list
Open System Settings → Privacy & Security → Bluetooth. Each app on the list has a toggle.
The list is usually small. Most users see entries for one or two specific tools.
Who legitimately needs Bluetooth permission
A short list:
- Bluetooth peripheral managers — Logitech Options, Magic Trackpad utilities, Sleep Mouse
- Sports and fitness apps — Strava (for sensor pairing), Wahoo, Garmin Connect
- Smart home apps — Eve, Hue (when local control is needed), Govee, Bose, Sonos
- Audio production tools — apps that pair with specific Bluetooth audio interfaces
- Game controller utilities — for non-Apple-supported controllers
- AirDrop and proximity tools — some third-party file-sharing tools
If you don’t use any of those, your list might be empty, and that’s fine.
What about Bluetooth audio?
This is the most common misconception. Bluetooth headphones and speakers don’t need any app to have Bluetooth permission. They’re handled by macOS at the system level — once paired in System Settings → Bluetooth, audio routes through CoreAudio just like any other output device.
So an app like Spotify or Apple Music doesn’t need Bluetooth permission to play through your AirPods. The permission is about apps that talk directly to Bluetooth devices over BLE protocols — fitness sensors, IoT, peripherals with their own SDKs.
If you see Spotify or a media player on the list, it might be there because of a less common feature (controlling specific Bluetooth speakers via their direct API). Check the app’s docs, but you can usually toggle it off without affecting normal playback.
What about “nearby device” features?
A few apps use Bluetooth ranging for features like:
- “Find nearby people” or social discovery
- Bluetooth-based handoff or sync
- Proximity-based unlock
If you don’t use those features, the permission can be off without affecting the apps’ main use.
How to revoke
In System Settings → Privacy & Security → Bluetooth, toggle off any entry that doesn’t match a real workflow. The app may need to relaunch.
If a Bluetooth feature breaks afterwards, the app will reprompt. Granting again is one tap.
The location-tracking concern
Bluetooth advertisements can be used for location tracking even without GPS. Bluetooth Low Energy beacons (commonly deployed in retail and venues) broadcast unique IDs. An app with Bluetooth permission can scan for those IDs continuously and infer where you are based on which beacons are visible.
Most apps don’t do this. But the technical capability is real, which is part of why Apple gates Bluetooth behind a user-visible toggle. If you want to minimize this surface, audit the list and turn off Bluetooth for any app whose primary use isn’t connecting to a specific paired device.
What’s on the list by default?
A clean Mac will usually have:
- Apple’s own utilities (system-level, may not always show)
- Whatever Bluetooth peripheral apps you’ve installed
Anything else — random utilities, unrelated apps — is worth questioning. A weather app doesn’t need Bluetooth. A note-taking app doesn’t. A game (unless it pairs to a specific controller) doesn’t.
System Settings → Bluetooth (the connection itself). The permission list is for app-level access, not pairing.Sandbox apps and Bluetooth
App Store apps need the com.apple.security.device.bluetooth entitlement to ask for Bluetooth. With it, they can scan and connect like any other app. Without it, they physically can’t request the permission and the toggle doesn’t appear.
This is one of the more clearly-bounded permissions in the sandbox model. If a sandboxed app from the App Store wants Bluetooth, the entitlement is in its Info.plist and Apple has reviewed it. If a non-sandboxed direct-download app wants Bluetooth, you grant it via the prompt with no sandbox check.
What about iPhone-paired Bluetooth?
Your iPhone’s Bluetooth devices don’t migrate to your Mac. Each device pair is per-device. So if you’re auditing the Mac, you’re only looking at apps using Bluetooth from this Mac, not from your phone. The iPhone has its own toggle list under Settings → Privacy & Security → Bluetooth.
The exception is Continuity / Handoff features, which use a private Apple-only Bluetooth + Wi-Fi mesh. That’s system-level on both devices and not exposed in the per-app permission UI.
Audit checklist
Once a year is enough for most people:
- Open
System Settings → Privacy & Security → Bluetooth - Confirm each app on the list connects to a Bluetooth device you actually use
- Toggle off anything that doesn’t
- If the list is empty, leave it that way
What about the bluetoothd system process?
You might see bluetoothd or related system processes referenced in some tools. These aren’t third-party apps and don’t appear in the per-app toggle list. They’re Apple’s Bluetooth daemon and run with system-level access by design. You don’t manage them through Privacy & Security.
Bluetooth is one of the easier permissions to audit because the legitimate-use cases are narrow and the misconceptions are common. Audio playback doesn’t need it. Most apps don’t need it. Keep the list to specific peripheral tools and fitness apps you actually use, and there’s nothing to worry about.