Summary
When a user uploads a profile image and later replaces or removes it from the profile section, the application does not delete the previously uploaded image from the backend storage. Although the UI reflects that the image has been removed or replaced, the original file remains stored and accessible through its previously generated URL.
This behavior results in orphaned files being retained in storage without user visibility or control.
Impact
- User-uploaded content persists beyond user intent.
- Users may assume removed images are no longer stored or accessible.
- Orphaned files accumulate in storage, potentially increasing storage usage and operational costs.
- Indicates improper data lifecycle and retention handling.
Root Cause
The application updates the profile image reference at the application/database level but does not delete the previously uploaded object from backend storage.
gnaitikg Reporter
Summary
When a user uploads a profile image and later replaces or removes it from the profile section, the application does not delete the previously uploaded image from the backend storage. Although the UI reflects that the image has been removed or replaced, the original file remains stored and accessible through its previously generated URL.
This behavior results in orphaned files being retained in storage without user visibility or control.
Impact
Root Cause
The application updates the profile image reference at the application/database level but does not delete the previously uploaded object from backend storage.