Full Disk Access on Mac: Which Apps Should Have It (And Which Shouldn't)

Full Disk Access is probably the most powerful permission you can grant an app on your Mac. It's also the one most people understand least.

I discovered this the hard way when I was building CoreLock. During testing, I noticed that a backup utility I'd been using for months could read my Messages database, my Safari browsing history, even my Mail attachments. Not just the files I was backing up — everything. That's when I realized how fundamentally different Full Disk Access is from regular file permissions.

What Full Disk Access Actually Grants

When you give an app Full Disk Access (FDA), you're essentially handing it the keys to your entire digital life. We're not talking about just accessing documents in your home folder. This permission bypasses most of macOS's privacy protections.

Here's what apps with FDA can access:

Your entire Mail database lives in ~/Library/Mail/. That includes every email you've ever received, sent, or drafted. Your Messages conversations are stored in ~/Library/Messages/. Your Safari browsing history, bookmarks, and even saved passwords (if they're in Safari's keychain) become accessible.

Time Machine backups are fair game too. The app can read /Volumes/YourBackupDrive/.Backups/ and see historical versions of files you thought were private. System logs in /var/log/ that might contain sensitive information? Yep, those too.

Here's the thing though — regular file access permissions don't work this way at all.

How Full Disk Access Differs from Regular File Access

Most Mac permissions follow Apple's concept of "least privilege." When you give an app access to your Photos library, it can only see photos. When you grant Camera permission, the app can capture new images but can't read your existing photo files.

Full Disk Access throws this principle out the window. It's a binary choice: either the app can read almost nothing protected, or it can read almost everything.

The technical reason involves macOS's System Integrity Protection (SIP) and the Transparency, Consent, and Control (TCC) framework. Normally, TCC prevents apps from accessing certain protected directories without explicit permission. You can see these restrictions in the TCC database at /Library/Application Support/com.apple.TCC/TCC.db.

But when an app has Full Disk Access, it can bypass most TCC protections. It's like having a master key.

Apps That Legitimately Need Full Disk Access

Some applications genuinely require this level of access to function. Backup software is the obvious example.

Carbon Copy Cloner, ChronoSync, and Arq all need FDA to create complete system backups. They have to read Mail databases, Safari data, and system files to do their job properly. Without FDA, these apps would create incomplete backups that might fail to restore your system correctly.

System maintenance tools often need it too. DiskSight requires FDA to analyze disk usage across protected directories. Disk Utility itself has this permission by default — it needs to verify and repair system-level disk structures.

Some development tools legitimately need it. Xcode occasionally requests FDA to debug system-level code or access crash logs in protected directories. Popular IDEs like VS Code might need it for certain debugging scenarios, though honestly, I'd be cautious about granting it unless you're actively developing system-level software.

Anti-malware tools present an interesting case. Malware often hides in protected directories, so security software needs FDA to scan these areas effectively. Tools like CoreLock use this permission to monitor file system changes across the entire system, not just user-accessible areas.

Apps That Definitely Don't Need Full Disk Access

This is where it gets frustrating. I've seen note-taking apps, photo editors, and even games request Full Disk Access. There's rarely a legitimate reason for this.

Text editors like Sublime Text or Atom don't need FDA to edit code files. Neither do photo editors like Pixelmator Pro or Affinity Photo. These apps can function perfectly well with standard file access permissions.

Social media apps requesting FDA should immediately raise red flags. There's no reason Instagram, Twitter, or TikTok needs to read your email database or Messages history. Same goes for music apps — Spotify doesn't need full disk access to play songs.

Browser extensions requesting FDA are particularly suspicious. Most extensions run within the browser's sandbox and shouldn't need system-level file access.

How to Check Which Apps Have Full Disk Access

You can see which apps have this permission in System Settings > Privacy & Security > Full Disk Access. But here's what drives me nuts about Apple's implementation — it doesn't tell you when these apps last used the permission.

That's actually one of the reasons I built CoreLock's permission audit feature. After discovering that a note-taking app had full microphone access on my personal Mac (I'd granted it for a voice memo feature I used once and completely forgot about), I realized we needed better visibility into permission usage.

You can also check the TCC database directly from Terminal:

sudo sqlite3 /Library/Application\ Support/com.apple.TCC/TCC.db "SELECT client,service,allowed FROM access WHERE service='kTCCServiceSystemPolicyAllFiles';"

This shows which apps have requested Full Disk Access and whether the request was allowed. The kTCCServiceSystemPolicyAllFiles is Apple's internal identifier for FDA.

The Hidden Risks Most People Don't Consider

Here's something most articles won't tell you: apps with FDA can potentially access data from other applications, even if those applications have their own privacy protections.

For example, that backup app with Full Disk Access could theoretically read your 1Password data files, your VPN logs, or your cryptocurrency wallet files. These apps store data in protected directories specifically to prevent other applications from accessing them.

FDA essentially breaks this isolation model.

There's another risk that's harder to quantify. Apps with FDA can monitor file system changes across your entire Mac. They can see when you create new files, modify existing ones, or delete sensitive documents. This creates a detailed profile of your computer usage patterns.

Making Smart Decisions About Full Disk Access

The key is being ruthless about which apps actually need this permission. Here's my approach:

Start by asking whether the app's core functionality requires reading system-level data. For backup software, the answer is obviously yes. For a note-taking app, it's almost certainly no.

Consider the app developer's reputation and privacy practices. Established companies with clear privacy policies are generally safer bets than indie developers or companies with questionable data handling practices.

Check whether the app offers specific explanations for why it needs FDA. Legitimate apps usually explain exactly which protected directories they need to access and why. Vague requests like "to improve performance" should be red flags.

When You Should Revoke Full Disk Access

I regularly audit the apps that have FDA on my Mac. If I haven't used an app in months, I revoke the permission. You can always re-grant it later if needed.

Apps that have been acquired by new companies deserve special scrutiny. That innocent backup utility you trusted two years ago might now be owned by a data broker. Privacy policies can change, and Full Disk Access permissions don't expire automatically.

If an app starts requesting FDA after an update, that's worth investigating. Why does the new version need system-level access when the old version didn't?

The Gatekeeper Problem

Here's something that might surprise you: Gatekeeper, Apple's app verification system, doesn't prevent apps with FDA from accessing sensitive data inappropriately. Gatekeeper checks that apps are signed by registered developers and scans for known malware, but it doesn't audit how apps use granted permissions.

An app could have a completely clean Gatekeeper signature while still misusing Full Disk Access to collect data you never intended to share.

This is honestly where I think Apple's current approach falls short. The permission system assumes users will make informed decisions about FDA requests, but most people don't understand what they're granting access to.

A Personal Reality Check

To be completely honest, this is probably overkill for casual Mac users who primarily use mainstream apps from the Mac App Store. App Store apps undergo additional review processes that make permission abuse less likely (though not impossible).

But if you're a developer, work with sensitive data, or install apps from outside the Mac App Store, being selective about Full Disk Access becomes much more important.

I might be overly cautious here, but I'd rather err on the side of protecting your privacy than assume every app developer has good intentions.

The Future of Full Disk Access

Apple has been gradually tightening permission controls with each macOS release. Sequoia introduced new restrictions on screen recording permissions, and I expect FDA will eventually get similar treatment.

The challenge is that some applications genuinely need broad system access to function. The trick is finding a middle ground between security and functionality.

For now, though, Full Disk Access remains an all-or-nothing permission. That makes your decisions about which apps to trust even more critical.

Understanding what permissions your Mac apps have isn't just about privacy — it's about maintaining control over your own data. Full Disk Access might be the most powerful permission on macOS, but it doesn't have to be the most dangerous if you're thoughtful about how you grant it.