Meta rejects political ads with no AI disclosure: June 2026 detection
From June 1, 2026 Meta uses automated detection for AI in political ads. Non-disclosure means rejection and repeat penalties. What to keep for a review.

Skipping the disclosure on a political ad has consequences. The Meta ad standards page for social issue, election and political ads, read on 2026-10-05, says that starting June 1, 2026 Meta uses automated detection to add the AI info label to such ads. It says failing to disclose leads to ad rejection, and repeated failures lead to penalties.
So the safest assumption is that Meta may find the AI on its own and label or reject the ad whether or not you ticked a box.
The sequence in plain terms
| Step | What the page says |
|---|---|
| You disclose | The ad is labelled with AI info |
| You do not disclose, Meta detects AI | Automated detection can add the label (from June 1, 2026) |
| You do not disclose, ad is reviewed | Rejection |
| Repeat non-disclosure | Penalties |
Where the label shows
Meta's help page says the AI info label appears under "About this ad" in the three-dot menu, and sometimes next to the Sponsored text. It also says not all ads that use Meta's tools carry the label yet, so a missing label is not proof that no AI was detected.
What to keep for a review
If an ad is rejected, fix the disclosure first and resubmit; do not re-render the clip hoping detection misses it. With repeat penalties on the table, hiding the AI is the costly option.
Sume's docs describe jobs, results and a metadata field stored on the job; they do not describe any Meta integration or label. Keep your own record rather than relying on a Sume field to prove disclosure.
- The source file and the generation record, for example the job id and model name from the tool that made the clip.
- The disclosure choice you made in the ad flow, and a screenshot with the date.
- A note on which parts are AI: the visuals, the voice, or both.
- The final delivered file, because a re-encode can change what detection sees.
Treat the first rejection as a process failure to fix, not a one-off. Add the AI question to the checklist your team runs before any political or social issue ad goes live, name who answers it, and re-run it when the creative changes, because a new voice-over or a swapped background can change the answer. If several people submit ads from one account, agree one owner for disclosures so a repeat does not come from a handoff gap. Keep rejection notices with the creative record so you can see patterns across campaigns, and ask for review rather than resubmitting unchanged.
Sources
Related posts
More in Use cases
- Meta text overlay rules: one CTA, contrast, safe zone, Sume captions
Meta's overlay advice is four lines: clean font, contrasting hue, one call to action, stay in the safe zone. How to meet each with a Sume caption job.
- Midjourney 100K-image history crash fixed; archive your files anyway
Midjourney's Oct 2 changelog fixes a crash opening images in 100K+ histories. Keep your own copy: download outputs and log prompts, settings and cost.
- Midjourney collaboration is 'upcoming'; hand off with Sume metadata
Midjourney's Oct 2 changelog lists collaborative generation and edit history as upcoming. On Sume, put a handoff note in the job metadata field.
- Mixed-language recording: detach ranges, STT with a hint per range
Split a bilingual video into audio ranges with Sume audio detach, then transcribe each range with its own language_code. Detach output caps at 900 s.
Written by Sume