"Secure delete" sounds like a simple promise: overwrite a file, remove it, and it is gone. On a current Mac, the honest answer depends on what you mean by gone. A file operation can affect the selected logical path while still leaving questions about snapshots, backups, synchronized copies, and the behavior of the storage hardware underneath it.
This is not a reason to give up on deletion. It is a reason to choose the right outcome for the situation and to avoid treating a pass count or a success alert as proof of a result it cannot establish.
Selected-file deletion and full-device erasure are different jobs
A targeted file action is designed to change a selected file or area of free space. It can record what the app asked macOS to do and what the app could observe afterward. That is useful, but it is not the same as a statement about every historical copy that may have existed elsewhere.
For an entire Mac that is being handed to a new owner, Apple provides a separate workflow. On supported Macs, Erase All Content and Settings removes user accounts, data, apps, and settings while preserving the installed operating system. Apple makes that feature available on macOS Monterey or later for Macs with Apple silicon or the Apple T2 Security Chip. It is a device-handoff tool, not a substitute for understanding the copies of one file that may exist in another service or backup.
Why SSDs change the old overwrite story
Apple’s own Disk Utility documentation draws a clear line here: secure-erase options are not available for SSDs. If Disk Utility does not offer its Security Options control, Apple says it cannot perform a secure erase on that storage device. The same documentation points people toward FileVault when they begin using an SSD for stronger protection.
That does not mean encryption retroactively changes every data path or that FileVault is a magic answer to every disposal scenario. It does mean that storage-aware security starts before a file needs to be removed. Protecting a Mac’s data at rest and selecting Apple’s full-device erase process when transferring the device are different, complementary decisions.
Snapshots are part of the storage history
APFS supports snapshots. Apple describes an APFS snapshot as a read-only copy of its parent volume at a particular moment, and says a volume can have zero or more associated snapshots. Disk Utility can show and delete snapshots on a selected volume.
That is why an honest file-by-file result should say what it completed on the selected path, not claim that it inspected every earlier point-in-time copy. Snapshots, backups, and separately synchronized copies should be identified and handled under their own applicable process. A report about one file action is not evidence about systems the action did not reach.
A better way to describe the result
PhantomWipe is still in development, and no PhantomSecure module is currently available. Its intended approach is deliberately narrower than an absolute destruction claim: document the requested method, record the observed logical outcome, and call out relevant limitations such as APFS snapshots, backup copies, and storage that an application cannot directly verify.
That leads to clearer language:
- Completed logical deletion: the requested selected-file operation finished and the application recorded its outcome.
- Completed with limitations: the selected operation completed, but known storage or copy paths prevent a broader assurance.
- Verified sanitization: reserve this for a documented process with evidence that actually matches the claimed scope.
The first two messages can be useful and truthful. The third requires more than a progress bar.
Choose the outcome before the method
- For a file you no longer need, remove the selected file and account for any independently stored copies that matter to you.
- For an SSD, plan data-at-rest protection before a loss, repair, or transfer event; Apple specifically points to FileVault in its Disk Utility guidance.
- For a Mac you are selling, giving away, or trading in, use Apple’s full-device erase workflow for your supported hardware.
- For a regulated or forensic requirement, use a documented procedure whose evidence and scope match the policy, the storage device, and the threat model.
Security claims should stop where the evidence stops
The useful promise is not “every copy is gone.” It is a transparent explanation of the operation that ran, the storage context it could observe, and the limits that remain. That is the standard we want PhantomWipe to meet as its development continues.