Make Images Without Making Records

There is something strange about needing a permanent record for every little act of imagination.

Make a draft. Record it. Upload a reference. Record it. Try a bad prompt. Record it. Generate five outputs. Record them. Delete the session. Keep enough residue to make the word delete feel more like interior decorating.

Creative work has always needed temporary space. Sketches, scraps, rough notes, whiteboards, embarrassing first versions, bad mockups, and images that exist only long enough to teach you what not to do. AI should make that space bigger, not turn it into a database with ambition.

Records are sometimes necessary. Billing records, rate limits, abuse controls, security logs, and user-saved projects all have legitimate roles. The argument is not “store nothing ever.” The argument is that the creative substance should not be recorded by default just because the tool can.

Prompts are records of intent. Uploads are records of source material. Outputs are records of exploration. Histories are records of change. For sensitive image work, these records can expose more than the finished image ever would.

Ephemeral workflows should be normal. Run the job. Return the output. Let the user download or deliberately save. Delete temporary inputs. Avoid keeping prompt history. Use content-blind operational logs. Make the absence of memory part of the product, not an apology.

This will annoy some growth dashboards. Saved history increases return visits. Galleries increase engagement. Convenient archives make products stickier. Fine. Not every product should be optimised to stick. Some products should be optimised to let the user leave cleanly.

We should be able to make images without making records because experimentation is fragile. People try better things when the tool is not quietly keeping score.

Further reading: The right to experiment without being logged, The case against creative tools that remember everything, and The case for zero prompt history.