FTC unavoidable disclosure: a link or hover is not enough
Under the FTC's testimonials rule Q&A, a disclosure is avoidable if viewers must click or hover to see it. Here is how burned-in text passes that test.

No. The FTC's Q&A says "unavoidable" is an objective standard, and that a disclosure is avoidable when "a consumer must take any action, such as clicking on a hyperlink or hovering over an icon, to see" it. A disclosure that is part of the picture needs no action from the viewer, so for video the straightforward route is to put the words in the frame.
Quotes are from the FTC Q&A page, read 2026-10-01. This is not legal advice. Tool facts are from the Video captions and Video trim docs.
What counts as avoidable under the Q&A?
The page quotes the rule's definition of "clear and conspicuous", under which a disclosure is avoidable if the consumer must act to see it. It also says "unavoidable" turns on whether consumers could have avoided the disclosure.
| Placement | What the Q&A says |
|---|---|
| Behind a hyperlink click | Avoidable |
| Behind a hover over an icon | Avoidable |
| First line of a consumer review | The Commission would consider it unavoidable |
| Platform built-in disclosure tool | The page has a question on whether it is enough; read the answer before relying on it |
How do I burn disclosure text into an existing video?
POST /v1/video-captions takes a public HTTPS video_url and returns a job-backed captioned video. Pass cues (or segments), each with text, start and end, and the authored text is drawn on the frame without speech-to-text. The docs also note that a silent clip fails as caption_no_speech with next_action: use_overlay_captions, so a silent clip needs authored cues.
Because the result is a new captioned file, you publish that file instead of the clean one. For a related walkthrough see burning captions onto video.
Does trimming affect the burned-in text?
If you cut after captioning, the docs say video trim's default precision: exact is a frame-accurate re-encode (libx264, yuv420p). A cut can remove the seconds where your text appears, so trim first and caption last, then watch the final file.
What is the practical checklist?
Show the words on screen without any tap, keep them on long enough to read, and verify the exported MP4 rather than the preview. The FTC page does not give a timing or size rule, and Sume's docs do not claim a disclosure feature, so the wording and timing remain your decision.
Sources
Related posts
More in Use cases
- Seamless looping food video with AI: same first and last frame
To loop a food clip, send one image as image_url and end_image_url to Gemini Omni Flash 1.1, which Google says suits seamless loops. Clips run 3 to 10 seconds.
- Gemini TTS two-speaker limit: three-voice dialogue with Sume concat
Gemini TTS configures two speakers per request. For three voices on Sume, make one TTS job per voice and join up to 20 parts with Timeline audio concat.
- Google Play screenshot rules: 320-3840 px, no alpha, 2x ratio
Play screenshots must be JPEG or 24-bit PNG, 320 to 3840 px, with the long edge at most twice the short one. Sume's 3:1 limit is looser, so check 2:1.
- Change a garment's colour in a photo with a mask_url edit
Recolour clothing with a mask: send the photo as an input reference, a public HTTPS mask_url, and a colour prompt to ChatGPT Image 2.5 on POST /v1/images.
Written by Sume