Product1 publisher3 min readPublished
The Oversight Board pulled a councillor's deepfake after Meta's systems skipped human review
Meta's own board overturned it on both videos on 17 September, and those removal orders are binding. The nine policy changes it wants, on labels and demotion, are recommendations Meta has 60 days to answer.
The Product Desk · Product desk

What happened
- On 17 September the Oversight Board called Meta's deepfake rules "consistently and fundamentally inadequate to address the rapid rise of AI-generated content".
- The first video, posted by a Facebook user in November 2025, showed the likeness of a Labour councillor in Scotland making inflammatory comments about refugees that she never made.
- A majority of the board ruled the video broke Meta's hateful conduct rules, finding it alleged "serious criminality and predatory sexual behavior" against refugees as an entire group.
- In the second case, involving a young Muslim woman in Europe, Meta automatically closed the first report and the appeal, and removed the video only after the board became involved, Engadget reported.
- The board issued nine recommendations across the two decisions, six in the councillor case and three in the second.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- constraint The part of this that binds Meta reaches two videos. Thresholds, screens, demotion and penalties all depend on Meta agreeing to build them, so what Meta owes inside the window is a written answer.
- decision Meta now has to decide whether "high risk" keeps meaning elections and crises. Widen it and the label, plus any click-through screen, starts landing on ordinary posts, and a team inside Meta owns the complaints from creators who get screened.
- exposure Private individuals with no escalation partner are left with the automated path. The request to cover private individuals under unwanted manipulated imagery is the one change that would alter that.
- contradiction Meta argued low harm from low engagement and lost on both videos, so a moderation team that defends a call with distribution numbers is now arguing against a decision that binds its own employer.
Two people reported the councillor video, and one of them was the councillor. Meta's systems kept it out of human review, and both appeals failed [9]. She said she had also reported it to the police, without success [10]. The case reached a human decision because the other person who reported it appealed to the Oversight Board [9].
Meta's defence was that nothing in its rulebook caught the video. No Trusted Partner organisation had flagged it, and it contained no banned claims about voting or the census [12]. Meta said the video was satirical and drew little engagement, with no election or crisis close by [13]. Even after the board took the case, Meta held that the video sat within its rules and required no AI label [11], and it told the board it had not penalised the user for failing to disclose AI use [14].
Little engagement measures distribution. The video and the album it sat in, which included a photo of several named women at an anti-far-right protest, drew more than 5,000 views [8]. In the second case, AI-manipulated videos and images mocking the campaigner had tens of millions of views online, including on Meta's platforms, according to the Guardian [26]. The councillor told the board that the words in the fabricated video ran contrary to everything she stands for [10].
"From politicians to private citizens, AI-generated deepfakes are increasingly being used to harass and silence women from engaging in public discourse," said Pamela San Martin, a co-chair of the board [5].
The removals are settled. Board decisions bind Meta [4], and it overturned Meta in both cases, the Guardian reported [3]. The rest arrived as requests. Meta has 60 days to respond, Engadget reported [24]. Sixty days from 17 September falls on 16 November [32].
Two of the requests would change what a Facebook user sees. The board asked Meta to put a click-through screen, instead of a label, on content marked AI-generated or "High Risk AI" [21], and to lower the threshold for high risk labels beyond crises and elections [20]. The pair sets how often someone scrolling has to tap past a screen to reach a post. On the threshold Meta applies now, the board's majority found this video should have carried the High Risk AI label [17]. Other requests would demote or demonetise High Risk content, penalise accounts that share it repeatedly [22], and have Meta publish yearly data on how often it applies the labels [23].
The cases separate on two axes a team can apply to its own queue: whether the subject is a public figure, and whether an outside partner can escalate for them. The councillor counted as a public figure, so the board found no breach of the bullying and harassment rules [18]. The campaigner was a private individual, and the board asked Meta to widen "unwanted manipulated imagery" to cover deepfakes of private individuals [29]. A private individual with nobody to escalate for them gets the automated path, and in both of these cases that path left the content up. For a team running the same queue, the measurable version is the share of reports it upheld only after someone complained from outside the product.
What to watch
- Whether Meta's answer inside the 60 days accepts the lower high risk threshold, or only the yearly publication of label counts.
- Whether Meta widens 'unwanted manipulated imagery' to cover private individuals.
- Whether the click-through screen ships as a real interstitial on labelled posts, and what Meta reports about its effect.