VaultSort 5.8.1
Secure DeleteSafety NetSecurityAIWindows
Secure Delete through VaultSort's helper now acts as you, so it can only delete what you could delete yourself, and it says more clearly what it could and couldn't fully erase. This update also tightens VaultSort's protection against other programs taking control of it, keeps on-device AI requests on your computer, and fixes Reinstall Helper.
Improvements
- Secure Delete acts as you. When Secure Delete runs through VaultSort's helper, it now acts with your own permissions. It can only delete what you could delete yourself, and a file another account owns is refused with a clear message instead of being removed. If the helper can't act as you, nothing is deleted and VaultSort says so.
- Read-only files are asked about first. If a folder you securely delete holds read-only files of yours (a git repository, for example), VaultSort asks before it starts and offers Unlock and Delete. Files with other hard links, such as objects in a local git clone, are never made writable, so their other copies stay as they were.
- Clearer messages when you don't have permission. If your own permissions stop Secure Delete, VaultSort now names the item and explains, instead of showing a technical error or suggesting Full Disk Access.
- What Secure Delete couldn't guarantee is in the details. Limits of overwriting on your kind of drive (for example flash storage without encryption) now appear as a short details line in Operations, one line per kind, including for folders and for deletes that fail partway. The real error, when there is one, is shown first.
- System folders on drives are reported correctly. When you securely delete everything on a USB drive or SD card, folders such as
.fseventsdand.Trashesthat are removed rather than overwritten are now named accurately, including when the drive's top folder itself can't be removed. Folders VaultSort can't remove keep their permissions. - Safety Net's Erase History handles more cases. It now matches folders on case-sensitive drives correctly, and counts a file's resource fork when checking there's enough free space.
- Windows says "this PC". AI settings, the Smart Auto Organize recipe and redaction suggestions no longer refer to "this Mac" or Apple Intelligence on Windows.
Bug Fixes
- Reinstall Helper works. On the Safety Net page, Reinstall Helper now restarts VaultSort's helper even when it is already the current version, so it can fix a helper that has stopped working. It asks first, and it won't restart the helper while an erase, Secure Delete or other helper work is running.
- Move to Vault goes where you dropped it. Files dropped on a Vault now always go to the Vault and folder they were dropped on, and closing the import sheet while VaultSort is still checking Safety Net always cancels the move.
- System caches are deleted safely. Space Saver's cleaning of system caches now works through open folders rather than by path, so nothing swapped in during a clean can redirect it.
Security
- VaultSort can't be taken over with debugging switches. Another program could start VaultSort with a debugging switch written in an unusual way, and on Windows with any debugging switch, and then control it. VaultSort now refuses to start that way on Mac and Windows, and ignores developer settings in its environment.
- On-device AI requests stay on your computer. VaultSort no longer follows redirects from Ollama, so a program listening on your computer can't forward on-device AI requests, or document text for redaction suggestions, to another computer.