{"id":3360,"date":"2018-10-24T16:30:41","date_gmt":"2018-10-24T15:30:41","guid":{"rendered":"https:\/\/www.dataleaklawyers.co.uk\/blog\/?p=3360"},"modified":"2018-10-24T10:20:35","modified_gmt":"2018-10-24T09:20:35","slug":"cleveland-police-data-breach","status":"publish","type":"post","link":"https:\/\/www.dataleaklawyers.co.uk\/blog\/cleveland-police-data-breach","title":{"rendered":"Cleveland Police data breach"},"content":{"rendered":"

The Cleveland Police data breach was another example of a preventable public sector data breach that should never have happened in the first place.<\/p>\n

As a result of what\u2019s being classed as a \u201chuman error\u201d incident, the personal details of 1,661 people were leaked online. As part of the police\u2019s procedures for disclosing data about \u201cuse of force\u201d, information was put online that was accidentally not redacted. What should have been generic information about people who had been restrained by the police between April and June this year instead disclosed far more information.<\/p>\n

Anyone affected by the Cleveland Police data breach may be eligible to pursue legal action<\/strong><\/a>.<\/p>\n

<\/p>\n

What happened in the Cleveland Police data breach?<\/strong><\/h3>\n

As part of efforts to be transparent with the public, Cleveland Police published information about how their officers had applied \u201cuse of force\u201d in the field. The data published was intended to be generic data about persons who had been restrained by the force during a period of time.<\/p>\n

Unfortunately, the information published was unredacted, meaning personal information was disclosed as well.<\/p>\n

The data was published on 24th<\/sup> July 2018, but it was not until September when they were alerted of the breach by another police force. Those affected are being contacted.<\/p>\n

What information was disclosed in the Cleveland Police data breach?<\/strong><\/h3>\n

The information disclosed in the Cleveland Police data breach included:<\/p>\n