The boundary
visualize creates the file. It does not require an account or send the file anywhere. Your chosen agent may have its own data policy.
When you want a hosted version, ask explicitly:
Publish the reviewed report with dsp.
display.dev is one optional destination. Its own access, privacy, pricing, and processing terms apply. You can also use another host or keep the document as a local file.
Generated images
An image generated during creation is an ordinary local asset, but display.dev's current MCP, CLI, and fallback transports publish one HTML or Markdown file. They do not upload an adjacent PNG or JPEG.
Before using this publish path, make the reviewed HTML self-contained by embedding the image as a data URL, then verify the rendered result. Keep a multi-file artifact local or choose another host that accepts the reviewed asset set.
visualize preserves provider-supplied image metadata unchanged before publication.