Thames Valley Police defend Halloween poster criticised online
Summarised from 2 outlets · Updated 31 Oct, 13:08 · Archive
Thames Valley Police has defended its 'No Trick or Treat' poster after a GB News anchor criticised it on social media.
Thames Valley Police has defended its 'No Trick or Treat' poster after GB News anchor Alex Armstrong criticised it on social media platform X. Armstrong claimed the poster, which he said came from Buckinghamshire Council and the force, included a warning that Halloween can upset religious or cultural beliefs.
The police force responded by saying the poster can be used by anyone, such as elderly or vulnerable residents, who do not wish to have unexpected callers or be disturbed. Thames Valley Police stated: 'At no point have we mentioned that Halloween can upset religious or cultural beliefs.' The poster is designed to be displayed in windows to give trick-or-treaters a clear message not to knock at those homes.
The force has promoted the scheme for many years, with versions of the sign dating back to at least 2009. Police say the poster is particularly useful for elderly and vulnerable residents, while trick-or-treaters are encouraged to respect homes displaying the sign and move on. Police also remind children and families to only visit homes where Halloween visitors are clearly welcome.
How it is being reported
- Thames Valley Police hit back at GB News anchor over social media postThames Valley Police has defended a Halloween poster after it was criticised online by a GB News anchor.Oxford Mail · 31 Oct, 11:30
- Thames Valley Police hit back at GB News anchor over social media postThames Valley Police has defended a Halloween poster after it was criticised online by a GB News anchor.Oxfordshire Guardian · 31 Oct, 11:30
In this story: Thames Valley Police · Alex Armstrong · GB News · Buckinghamshire · Oxfordshire
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)