Does Google keep Omni and Veo prompts for 55 days?

Yes, for the Gemini API in general. Google's abuse-monitoring page says it retains prompts, context and outputs for 55 days to detect policy violations, and that flagged content can be reviewed by authorized employees under predefined guidelines. The page does not name Gemini Omni Flash or Veo 3.1, so treat it as the baseline for any Gemini API video call, not as a model-specific promise. This is read on 2026-10-08.

Three different clocks get mixed up in this question. The 55 days is the abuse log. Veo's 2-day figure is how long a generated video stays downloadable. And Omni's store setting only decides whether the next turn can edit the clip. Keeping them apart avoids a wrong answer in a security review.

Three retention numbers from Google's pages

The table lists each number with the page it comes from. None of them is a Sume number.

What the pages do not say

The Omni page gives no retention period for its stored interactions, and the abuse page does not say whether 55 days applies differently to video outputs. If a client needs an exact answer for a generated video, ask Google in writing rather than inferring it from these pages.

The SynthID watermark is a separate matter: Google's Omni docs say every generated video carries one, which is a provenance mark and not a retention setting.

How a Sume request differs

Sume does not list Veo 3.1. It lists Gemini Omni Flash 1.1 as gemini-omni-flash-1.1, and the model card in the repo describes it as a fal-served row. So Google's direct-API retention table above describes a request sent to Google, not a request sent to Sume.

On the Sume side, the video generation docs say video generation is ZDR-ineligible and that Sume has no zero-data-retention toggle. If your contract requires ZDR for video, that is a blocker on both routes, and you should read Sume's privacy material before you commit.

A short checklist before you send client footage

Decide what leaves your machine before you pick a model.

• Do not put signed URLs, customer lists or unreleased packaging into a prompt; assume a 55-day log on any Gemini API path.
• Download a Veo clip the same day. After 2 days the file is gone and extension needs a Veo-generated source.
• For Omni edits, keep store on only if you need multi-turn edits; otherwise the clip is not stored for that purpose.
• On Sume, keep the job result from GET /v1/jobs/:id/result in your own storage if the clip is a deliverable.

What to do about it

Do not put anything in a prompt that you would not want retained for 55 days. That includes names, addresses and client details. If a project needs stricter handling, ask the vendor in writing before you use the model, since a retention window and a training-use rule are separate matters.