What happens to your code and photos

Up to 10 reference images you upload for Image to Image are relayed through a temporary, signed URL that stops working 10 minutes after the render starts. The images themselves are deleted from that temporary storage the moment the render job finishes — whether it succeeds or fails. They are never written to a database and never outlive that one render.

For Text to Image and Image to Image, the code you paste is used directly as the character source for that one render. It is not written to a database on its own, and it is never logged — Cographic’s error logs never include code or prompt content.

A render’s finished image — which is your code, rendered pixel by pixel; that’s the entire product, not an incidental detail — is cached so an identical request (same image, same code, same settings) doesn’t have to be rendered twice. That cache currently has no automatic expiry: an unpurchased render’s output can persist indefinitely. It is stored under a one-way hash of its exact inputs, not searchable or browsable, and reachable only by submitting the identical code and image again — but it is not deleted on any schedule today. If that changes, this page will say so.

Suggest from code sends the code you paste — and, in Image to Image, the reference image you’ve already uploaded — to Claude, Anthropic’s model, to write an image-generation prompt. That transfer is governed by Anthropic’s own API data-handling terms, not Cographic’s. Cographic does not separately store what it sends there.

When Cographic generates an image — Text to Image, Image to Image, or a vault artwork — the prompt and any reference images go to whichever model you selected: GPT Image 2, Seedream 5 Pro, or Nano Banana Pro. Each is governed by its own provider’s data-handling terms, not Cographic’s.

If you buy a print, a Digital or Verified Ownership Key, or an Empty Vault, the code and source image behind that render are stored permanently — by design, not by oversight. Fulfillment, reprints, refunds, and order support all depend on being able to look up exactly what was ordered.

For a Digital or Verified Ownership Key specifically, that stored code is the product: a timestamped copy you are paying to have on record as proof of authorship.

A reference image you upload is gone within minutes. Pasted code used in an unpurchased render isn’t logged or separately recorded as text, but its rendered output is cached with no expiry today. Anything tied to a purchase — a print, an Ownership Key, a vault — is kept on purpose, indefinitely, because that’s what you paid for.