Gemini API paid vs unpaid data use: Omni prompts and uploaded clips

Gemini API terms: unpaid content may improve Google products and reach human reviewers; paid content does not. What that means for Omni edit uploads.

4 min readSume
All posts

Under Google's Gemini API additional terms, unpaid services use your content to improve Google products and human reviewers may read it, while paid services do not use prompts or responses to improve products and log them for a limited time for abuse monitoring. For Omni, that matters most for edit and extend, where you upload a source clip. Use a paid project for anything you cannot share.

The terms in plain words

The Gemini API additional terms say that for unpaid services, Google uses submitted content and generated responses to provide, improve and develop products, and that human reviewers may read, annotate and process it, with a warning not to submit sensitive or confidential data. For paid services, Google says it does not use prompts or responses to improve its products and processes data under its data processing terms, while logging prompts and responses for a limited period for abuse detection.

This is a summary of the page as read on 2026-10-04; check the live page before you rely on it, since terms change.

Data handling by service type in the Gemini API terms (read 2026-10-04)
Service typeUsed to improve productsHuman reviewRetention noted
UnpaidYesPossibleNot specified here
PaidNoNot for improvementLimited-time logs for abuse monitoring

Why edit and extend raise the stakes

Omni's guide says uploaded videos for edit or extend must be 10 seconds or shorter, and video references are limited to three clips of three seconds. A short clip can still be an unreleased product shot or a face. On an unpaid project that clip is input content under the unpaid terms.

The guide also notes that editing or extending uploaded videos is unavailable in the EEA, Switzerland and the UK, so a European team may be blocked before the data question even arises.

What I can and cannot say about Sume

Sume's docs describe the pipeline, not its upstream providers' data terms, so I will not claim anything about those. What the Video Router docs do say is that an edit request takes a video_url, cannot be combined with image or reference inputs, and bills output seconds. The API reference lists the routes, but the Sume pages I read do not state upstream retention terms for uploaded clips, so get that answer in writing before you send sensitive footage.

Practical rule: classify the clip first, then pick the route. Public marketing footage can go anywhere; unreleased footage needs a written answer from whichever vendor you pick.

Sources

Related posts

More in Developers

All Developers posts

Written by Sume