Use Unexposed when you want private image generation from open-weight models without prompt history, public galleries, third-party image APIs, or provider-side prompt retention.
For Unexposed, zero retention is about generation content: prompts, source images, and generated outputs should not become a hosted history, gallery, training feed, or provider-side image API record.
What Zero Retention Means Here
Unexposed is designed so generation content is task content, not account content.
That means:
- no hosted prompt history;
- no public gallery;
- no prompt or source image in normal application logs;
- outputs stream back after generation;
- third-party image-generation APIs do not receive your prompts or source images.
The goal is simple: once the generation task is finished and the output has been delivered, Unexposed should not keep the prompt, source image, or generated output as a product feature.
Why This Is Different From Prompt History
Many AI image tools are built around saved projects, galleries, remix feeds, team workspaces, or account-level prompt history. That can be convenient, but it is not the right default for private generation.
Unexposed starts from the opposite default. Your generation request exists to run the model and return the result. It is not meant to create a long-lived hosted library of your ideas.
What May Still Be Kept
Zero retention for generation content does not mean the service keeps no records at all.
Unexposed may keep account records, billing records, token metadata, usage counts, task status, error metadata, and security logs where needed to operate the service, prevent abuse, satisfy legal duties, or handle accounting.
Those records should stay content-blind: they should not contain your prompt, source image, or generated output.
Read Your Data for the practical data lifecycle.
Start With Zero Prompt History
Use Unexposed when your priority is private open-weight image generation, not a hosted prompt archive.