Short answer: Put retention ahead of vendor selection for private health uploads: enforce revocation and verified deletion in the application, generate short-lived upload and download URLs only after authorization, and keep object keys out of client control.
The simplest object storage is not the one with the shortest SDK example. In a healthtech system, the decisive question is whether an expired record becomes unreachable and is then deleted on schedule. A private bucket and a presigned URL help with access, but neither is a retention policy by itself.
My default is boring: one metadata record owns the object lifecycle, every signed operation starts from that record, and a reconciliation job checks that database state and storage state agree. This costs more engineering time than handing permanent object URLs to the frontend.…