Short answer: keep generated AI images in private object storage, treat every original and derived file as immutable, authorize access before issuing a brief signed link, and clean up only data classes with an explicit recovery and retention policy.
The tempting first version is one bucket, one predictable filename, and a public thumbnail URL. It works in a notebook because there is one user, one worker, and no delete queue. Production changes the question. A generated image has bytes, ownership, publication state, transform history, and a retention obligation; putting all of that meaning into a path turns storage into a fragile second database.
This pattern is deliberately boring.…