Yesterday, a cleanup tool nearly went through a client’s entire drive
At 9 p.m. Tuesday, I was in a Hangzhou café demonstrating Mac automation for a client. A small utility claiming to “clean cache” popped up and requested Full Disk Access. My first reaction was to click Allow. Then it hit me: that would let it view almost every file on the hard drive. I’d made this mistake before too—after clicking Allow, the system doesn’t conveniently tell you which data was touched.
I didn’t grant access; first, I checked what it wanted
On Mac, Full Disk Access isn’t an ordinary permission. It lets an app read files protected by other apps, including email attachments, chat histories, and browser data. Apple explains in its support document, “If an App Asks for Full Disk Access or System and App Protection Override,” that users can manually grant access when an app genuinely needs backup, security, or file-management features—but there’s no reason to enable it otherwise.
Later, I asked my security-consultant friend Chen Hao to walk me through it. In his office in Nanshan, Shenzhen, he opened System Settings, went to Privacy & Security, selected Full Disk Access, reviewed which apps had already been authorized, and used the “−” button beside an app to revoke access. It took no code, but it did require understanding where the app came from.
My no-cost, 10-minute, no-code check
It cost ¥0 and took about 10 minutes. The only technical hurdle was knowing the difference between System Settings and an ordinary app prompt. First, I didn’t click Allow in the pop-up. I opened Mac System Settings → Privacy & Security → Full Disk Access. Then I checked the app name, developer information, and stated purpose. If the source was unclear, or I’d never actively used the relevant feature, I removed its authorization with the “−” button. If the prompt returns, I can check the developer’s official website or where the installer came from.
Not everyone needs this check. If an app comes from legitimate software I’ve used long term, and its feature clearly involves backup or file management, it’s worth assessing separately. There’s no urgency to test this either. I just remember not to let a pop-up rush me.
At each stage, I authorize less and avoid shortcuts
When I’m just starting and don’t have stable clients yet, I make a software authorization list and record the source and permissions of every app. I leave unnecessary features off for now. With one or two clients, I first check whether folders and cloud drives containing client files are accessible to unrelated apps, then decide whether whole-drive access is necessary. I give access only to software that truly needs it. As I scale, I have whoever handles security review the authorization list every quarter, and add “verify the source when a permission prompt appears” to the team’s onboarding guide. For permissions, the lowest-effort move isn’t two quick clicks; it’s taking ten seconds longer to look carefully.