If an App Asks for Full Disk Access or System and App Protection Override
Apple’s upcoming changes to macOS “Full Disk Access” and related permissions aim to curb apps’ broad, often unnecessary access to users’ files, especially in light of AI tools and agents that want to scan entire systems. Commenters broadly welcome tighter, more granular controls and scarier warnings for invasive permissions, but criticize Apple’s confusing UX, inconsistently enforced rules, and limited APIs that push developers toward overbroad requests. The debate centers on how to balance strong, user-friendly privacy protections with the needs of power users and legitimate tools like backups, automation utilities, and developer software.
Purpose and scope of Full Disk Access
- FDA is treated as near‑total access to user data (“keys to the kingdom”), though it still doesn’t bypass SIP or Unix user permissions.
- Some argue Apple’s doc misrepresents FDA as mainly for backup tools, cleaners, indexers, security apps; they see it as originally more general (e.g., Terminal, developer tools, system utilities).
- Others respond that the doc targets non‑technical users and just lists relatable examples, not all valid uses.
Reaction to Apple’s new model
- Many see the new, more granular controls (folder selection, per‑app data access, stronger wording like “bypass system protections”) as a significant security improvement.
- Several users plan to wipe their FDA list and re‑grant only where necessary.
- Some think this is a reasonable way to force developers to justify permissions and curb overbroad requests.
AI, privacy, and misuse concerns
- A strong theme: AI agents and LLM tools pushed this issue by wanting FDA to crawl messages and files.
- Users are particularly alarmed by cases where AI apps instruct users to grant FDA to read private data (e.g., Messages), which some call spyware‑like.
- Many commenters say this makes people finally grasp how invasive FDA is and welcome Apple “scaring” users here.
Developer and power‑user perspectives
- Developers complain the new API is narrow, reactive, and under‑documented, especially dropped into a minor OS update.
- Power users want:
- Read‑only vs read‑write distinctions.
- Time‑limited access.
- Negative permissions (explicitly deny folders like
~/.ssh). - Per‑app filesystem ACLs and the ability to redirect or fake data.
- Others argue Apple is right to prioritize ordinary users over developers and that many apps have abused broad access for decades.
Permission UX and technical issues
- Many apps (chat, media, office, dev tools) request FDA but function fine without it, reinforcing distrust of requests.
- Repeated prompts and fragmented settings (FDA vs Files & Folders vs Accessibility) are seen as confusing and sometimes inconsistent.
- Some see macOS security as partly “theater,” citing large vendors that appear to bypass restrictions (e.g., always creating folders in Documents).