I m preparing the launch of Folder Lock Vault, a small macOS utility that turns a normal folder into a local AES-256 encrypted sparsebundle. It mounts as a Finder folder when needed and relocks when ejected; there is no account or cloud sync.
For people who protect client files, financial documents, or personal archives, which part matters most to your confidence in the workflow: clear confirmation that the encrypted copy succeeded, a simple mount/eject experience, better backup guidance, or very explicit passphrase-recovery warnings?
I m especially interested in practical feedback on the lock unlock relock flow. If you test it, please start with non-sensitive sample files and keep a separate backup.
Protect client work, financial documents, personal archives, and other private Mac folders inside local AES-256 encrypted sparsebundle vaults. Mount a vault as a normal Finder folder when needed, then eject it to relock. No account, cloud sync, ads, or tracking. The original folder is moved to Trash only after the encrypted copy succeeds. Forgotten passphrases cannot be recovered.
Folder Lock Vault protects selected Mac folders in local AES-256 encrypted sparsebundle vaults. It verifies copied contents before moving the original folder to Trash, unlocks in Finder, and relocks by unmounting. No account, analytics, cloud upload, or recovery backdoor. Free macOS beta: https://testflight.apple.com/joi.... Test only with disposable sample folders.
