← Blog

Data retention, provider by provider.

Every generation goes somewhere before it comes back to you. Here's how long each provider actually keeps it, straight from their own terms, and what Fuze does about the one part it can change.

Replicate

By default, Replicate automatically deletes all input parameters, output values, output files, and logs for any prediction created through the API, one hour after it finishes. No setting needed on Fuze's side, it's already the shortest window of any provider here.

fal.ai

In Fuze today: reference images and generated results expire in 30 minutes, and the prompt and parameters behind each request aren't stored at all. fal's own defaults are looser, files for at least 7 days, prompts for 30 days. Fuze forces the shorter numbers on every call it makes. A "debug logs" switch in Settings can flip prompt storage back on temporarily to troubleshoot a failed generation, it resets to off the next time Fuze restarts.

Kie.ai

Kie keeps files for 14 days and logs for 2 months. Both are fixed, there's no setting, on Kie's side or Fuze's, to shorten either.

Google Vertex AI

Google caches request data for 24 hours by default. That's the number for normal use. The one exception: if automated filters flag a request as suspicious, that specific prompt can stay logged for up to 90 days for manual review, only flagged content, most requests never reach this. You can exclude your account from that flagging entirely through Google's exemption form, which removes the 90-day case too.

Google Cloud Storage buckets

A bucket is a cloud drive, public or private, that holds files until something deletes them. Fuze can use one to upload reference images so a model can read them from a URL. How long anything sits there is entirely your call, you set the deletion rule yourself in your own Google Cloud account.

Cloudflare AI Gateway

Cloudflare's own logs are on by default for every gateway, and by default they persist indefinitely, the prompt, the response, and the request metadata, until you hit your plan's storage cap or delete them yourself. You can turn logging off entirely in the gateway settings, or send cf-aig-collect-log-payload: false on each request to keep only metadata (tokens, cost, model, duration) without the prompt or response. Fuze doesn't send that header today, so whatever goes through Cloudflare stays there under whatever setting your own gateway already has.

ProviderFilesPrompts / logs
Replicate1 hour1 hour
fal.ai, via Fuze30 minNot stored
Kie.ai14 days2 months
Google Vertex AI24h cache90 days if flagged
Cloudflare AI GatewayNo expiry by defaultNo expiry by default

What this means with Fuze

  • Replicate's one-hour window is automatic on Replicate's side, Fuze doesn't need to shorten it further.
  • fal's file retention is 30 minutes, and prompts/logs aren't stored at all, both set by Fuze.
  • Kie's retention isn't adjustable, by Kie or by Fuze.
  • Cloudflare's default is to keep everything until you or your plan's storage limit removes it. Fuze doesn't send the header that would turn that off, it's still a setting on your own gateway.

For a job where privacy matters most: Replicate's one-hour default and fal's numbers through Fuze are the shortest, followed by Google's 24-hour cache. Kie's 14 days and 2 months are longer and can't be shortened. Cloudflare is the one to watch, its default has no expiry at all unless you turn logging off yourself.

! Terms change, especially at smaller platforms. Confirm anything that matters for a client contract directly with the source before relying on it.