ILLUSTRATIVE WORKED WALKTHROUGH These steps explain a complete approach. They are not a claim that this live provider/account test was performed for you. Use your own project and record your actual observations. 1. Use a private avatars bucket with storage-side size/type settings and owner-folder policies. Upload an allowed image as account A; inspect the returned storage result, then open the short-lived signed preview. A blob preview alone proves no remote upload. 2. Try an unsupported or oversized file and attempt an upload/read under account B's folder. A must not gain access merely by changing a path in developer tools. Signed URLs intentionally grant temporary access until their expiry. 3. For deletion, add a DELETE policy using the same bucket/owner-folder condition and call remove with the exact stored path. Verify the object is absent afterward and a cross-owner deletion leaves the other owner's object intact. The reference deletion module is separate so you can inspect the path and policy before integrating it.