FOI 1024/24 Communications Act ArrestsDisclosure log response · Cleveland Police
Communications Act Arrests
Read it at Cleveland Police's website
- Published
- 8 Apr 2025
- Published by
- Cleveland Police
- Outcome
- Disclosed
- Source
- Cleveland Police's website
- Recorded by PoliceFOI
- 2 Sept 2026
We read the outcome automatically from the response's own words, so this can be wrong: report a mistake. What the outcomes and codes mean.
In full, as Cleveland Police published it
We show a record in full only where its publisher's terms allow it. Most police forces in England and Wales publish under the same publication scheme terms: anyone may reproduce a force's own material free of charge if it is accurate and not misleading and the source and copyright are acknowledged, but not for any commercial purpose. PoliceFOI is published by a company, so we treat our use as commercial, and for those forces we show each record's title and summary, with a link to the original, until the force agrees to more. A few forces' terms are stricter still. None of these terms covers material owned by someone else, or a force's logo, so we link to such material rather than copy it.
FOI 1024/24 Communications Act Arrests
Dear [requester],
Enquiry Reference: 1024 - 24
I write in connection with regards to your Freedom of Information request. Below is your request and our response.
I would like to know how many arrests you made under Section 127 of the Communications Act 2003 in the following years: 2017, 2018, 2019, 2020, 2021, 2022, 2023, and the first nine months of 2024. Please can you provide separate figures for each year.
- a) The below figures relate to the below offences:
Send by public communication network an offensive/indecent/obscene/menacing message/matter – Contrary to section 127(1)(a) and (3) of the Communications Act 2003.
Cause to be sent by public communication network an offensive/indecent/obscene/menacing message/matter - Contrary to section 127(1)(b) and (3) of the Communications Act 2003.
Cause to be sent by public communication network a false message to cause annoyance/inconvenience/anxiety - Contrary to section 127(2)(b) and (3) of the Communications Act 2003.
Persistently make use of public communication network to cause annoyance/inconvenience/anxiety - Contrary to section 127(2)(c) and (3) of the Communications Act 2003.
2019 – 17
2020 – 24
2021 – 19
2022 – 32
2023 – 59
2024 – 29
In a separate table, please can you provide the number of arrests you made under Section 1 of the Malicious Communications Act 1988, over the same time period and in the same year-by-year breakdown.
- a) The below figures relate to the below offences:
Send communication / article of an indecent / offensive nature - Contrary to section 1(1)(b) and (4) of the Malicious Communications Act 1988.
Send letter / communication / article conveying indecent / offensive message - Contrary to section 1(1)(a) and (4) of the Malicious Communications Act 1988.
Send letter / communication / article conveying a threatening message - Contrary to section 1(1)(a) and (4) of the Malicious Communications Act 1988.
Send letter / communication / article conveying false information - Contrary to section 1(1)(a) and (4) of the Malicious Communications Act 1988.
2019 – 11
2020 – 41
2021 – 51
2022 – 35
2023 – 32
2024 – 11
Having made enquiries within the Force the analyst has provided the above. We only have data since 2019. To trace the legislation, we have looked up the CJS codes and then looked to see what arrests were made under the power. Above lists the CJS codes used and the number of arrests per year since 2019 and 2024 relates from 1st Jan to 28th Oct 2024. Please note that all statistical data supplied in relation to Freedom of Information requests is a snapshot of data held at the time the request was received by the Freedom of Information office and is subject to constant change/updates.
The Cleveland Police response to your request is unique and it should be noted that Police Forces do not use generic systems or identical procedures to capture and record data therefore responses from Cleveland Police should not be used as a comparison with any other force response you receive.
If you are not satisfied with this response or any actions taken in dealing with your request, you have the right to request an independent internal review of your case under our review procedure. The Freedom of Information Code of Practice (see below link) states that a request for internal review should be made within 20 working days of the date on this response or 40 working days if extenuating circumstances to account for the delay can be evidenced. Public authorities are not obliged to accept internal reviews after this date.
https://www.gov.uk/government/publications/freedom-of-information-code-of-practice
Yours sincerely
Information Rights Decision Maker
© Cleveland Police. Reproduced for non-commercial purposes from https://www.cleveland.police.uk/foi-ai/cleveland-police/disclosure/2024/october/foi-102424-communications-act-arrests/ under Cleveland Police's publication scheme terms, which allow free reproduction if accurate and not misleading, with the source and copyright acknowledged. The text only, as read from the published documents; material owned by others is not covered. Collected on 2 September 2026; Cleveland Police may have changed or withdrawn it since.
If this text names you or you own part of it, ask us to take the full text down: it is hidden as soon as you send the form, and the title and summary stay.
Related releases
- FOI 553/26 Equality, Diversity and Inclusion(EDI) Disclosure log response · Cleveland Police · 6 Jul 2026
- FOI 558/26 EDI Costs and Operational Guidance Disclosure log response · Cleveland Police · 6 Jul 2026
- FOI 562/26 Equality, Diversity and Inclusion Staff Disclosure log response · Cleveland Police · 6 Jul 2026
- FOI 247/26 Palantir Technologies Disclosure log response · Cleveland Police · 1 Jul 2026
- FOI 293/26 Palantir Technologies Disclosure log response · Cleveland Police · 1 Jul 2026
Ask us to remove a name from this page (free) · Report a mistake