Privacy & permissions
Which Apps Have Access to Your Mac's Contacts?
Find every app with access to your Mac's Contacts, understand what they can read, and revoke access from apps that don't need your address book.
Your Contacts on a Mac aren’t just names and phone numbers. With iCloud sync, they include addresses, birthdays, photos, notes you’ve written about people, custom relationship labels, and every email you’ve ever attached to a contact card. Hand that to the wrong app and you’ve handed over a meaningful slice of your social graph.
Here’s how to check who has access, what the permission actually grants, and how to keep the list lean.
What Contacts permission grants
When an app has Contacts access on macOS 14 Sonoma or 15 Sequoia, it can:
- Read every contact card in your library
- Read every field on each card (name, phone, email, address, birthday, notes, photos)
- Read groups and smart groups
- Read relationship metadata (“Mom,” “Spouse,” etc.)
- Write new contacts or edit existing ones if it has write access
It does not automatically let an app:
- Read messages you’ve exchanged with those contacts
- Read your call history
- Read your email
- Sync contacts to its own servers (the app would have to upload, which is a separate action)
The data behind the toggle is significant. iCloud Contacts on a typical user might be 500 to several thousand entries, each with multiple fields. That’s a real address book.
Where to find the list
Open System Settings → Privacy & Security → Contacts. Each app on the list has a toggle. On is full read access; off is no access.
Apple is consistent here — there’s no “selected contacts” mode like there is for Photos. It’s all-or-nothing.
Who legitimately needs Contacts access
A short list:
- Mail clients — Apple Mail (system-integrated, no toggle needed), Spark, Mimestream, Airmail, Outlook
- Messaging apps — WhatsApp, Telegram, Signal, Messages (system-integrated)
- VoIP and video conferencing — Zoom, Teams, Webex, Skype, FaceTime (system-integrated)
- CRM tools — Salesforce, HubSpot integrations, Cardhop
- Email senders and newsletters — apps that auto-suggest recipients
- Backup tools that mirror Contacts
- Address book sync utilities — Spaceship contacts, BusyContacts
Outside these categories, the justification is usually thin. A photo editor doesn’t need contacts. A music player doesn’t. A file manager doesn’t. A new tab page doesn’t. If you see those in the list, they probably grabbed access during initial onboarding for a feature you never use.
Why the list grows
Three usual reasons:
- Onboarding flows — apps ask for everything during setup, hoping you’ll click yes once.
- Feature creep — an app you’ve used for years adds an integration, asks for the permission once, and you never revisit.
- Forgotten trials — an app you tested for a day still has the toggle on.
The first one is especially common in mobile-first apps that ported their iOS onboarding to Mac. iOS users often grant everything because the prompts are tied to specific actions. On Mac, the prompts come during a setup wizard and feel optional, but the result is the same — full Contacts access for an app that may not need it.
What metadata is in there
A contact card on iCloud can hold:
- First, middle, last name plus prefix and suffix
- Phonetic name fields
- Multiple phone numbers, each with a label
- Multiple email addresses
- Multiple postal addresses
- Birthday and other dates
- Job title and company
- Multiple instant messaging usernames
- Social media handles
- Multiple URLs
- Notes (free-text field people often use for sensitive context)
- Related names (“Spouse,” “Child,” etc.)
- Profile photo
Apps with Contacts permission see all of it. The Notes field is the one most users underestimate — people put account numbers, gate codes, allergy info, and other things they wouldn’t want loose.
Revoking access
In System Settings → Privacy & Security → Contacts, flip the toggle. The app may need to quit and relaunch for the change to take effect.
If the app needs Contacts again later — say, you decide to use Telegram’s contact-sync feature — it’ll prompt you and you can grant again.
For ghost entries (apps you’ve uninstalled that still appear), select the row and press the minus button at the bottom of the list. macOS will ask you to authenticate.
What about CardDAV and Exchange accounts?
If you have a work account that syncs Contacts via Exchange or CardDAV, those contacts merge into the same Contacts database. Any app with Contacts permission sees the merged view — work contacts and personal contacts together.
If you don’t want third-party apps to see work contacts, the cleanest fix is to keep the work account on a separate user profile or to not enable Contacts sync for that account on this Mac. Once the contacts are in your local Contacts.app database, any permitted app sees them.
Apps that should never be on this list
If any of the following appear, it’s worth a hard look:
- A “free” weather, flashlight, or system-utility app
- A free download from a site you’ve never heard of
- A “PDF reader” with a generic name
- An “uninstaller” that isn’t from a developer you recognize
- A “speed booster” or “memory cleaner” type app
None of those have any reason to read your address book. If they’re on the list, revoke and consider uninstalling the app.
com.apple.AddressBook.ContactsAccountsService. If the path starts with /System/Library, leave it alone — that's Apple's own.Sandbox containers and Contacts
App Store apps need the com.apple.security.personal-information.addressbook entitlement to even ask for Contacts. The sandbox doesn’t restrict access once granted — a sandboxed app with the toggle on sees the same data as a non-sandboxed app with the toggle on.
What the sandbox does help with is exfiltration. A sandboxed app can only make network requests to servers it has declared upfront in its entitlements. So a sandboxed contact-syncing app you grant access to can’t suddenly start uploading your contacts to a third-party analytics endpoint without it being visible in the entitlements.
Non-sandboxed apps from outside the App Store have no such restrictions. They can do anything any program can do with network access. That’s why the audit matters more for direct-download apps than for App Store ones.
What about Contacts in Mail’s autocompletion?
Mail (Apple’s first-party email client) reads Contacts directly. It doesn’t show up as a togglable entry in the Contacts pane because it’s a system app. Same with Messages, FaceTime, and Phone (if you’ve enabled iPhone calls on Mac).
This is fine. Apple’s first-party apps are deeply integrated and don’t go through the same permission UI. If you don’t want them to use Contacts, the workarounds are different (like signing out of iCloud Contacts entirely).
Audit checklist
Once a quarter:
- Open
System Settings → Privacy & Security → Contacts - Verify each app on the list has a real reason to be there
- Toggle off anything you can’t justify
- Investigate any apps you don’t recognize
- Remove ghost entries with the minus button
The Contacts list is one of the easiest privacy audits on Mac because the legitimate-use categories are narrow. Mail and chat: yes. CRM and contacts manager: yes. Almost everything else: no, and the toggle off is a click. The apps that genuinely need it will reprompt if access is revoked.