Feeds

Code for handling personal data is muddled, says lawyer

Further confusion in an already bewildering area

Choosing a cloud hosting partner with confidence

A code of conduct for handling personal data was launched in London yesterday. But the document is inconsistent on the need for consent when collecting personal data, according to a data protection expert. Sometimes consent is not necessary, he said.

The Personal Data Guardianship Code was published jointly by the British Computer Society and the Information Security Awareness Forum (ISAF) in response to the number of high profile data breaches in recent years. Its aim is to change the culture of organisations towards the handling of personal data.

According to its authors, the Code "follows on the success of the BCS petition objecting to the changes in the Coroners and Justice Bill which would have seen drastic changes to the way in which government departments could have used personal information."

In March the Ministry of Justice announced that, in response to criticism from many groups, it would scrap plans that featured in the draft legislation to allow Government departments to share citizens' personal information with each other and with the private sector.

The new Code is intended to help organisations and the people in them who handle personal data to understand their individual responsibilities. It aims to promote best practice and provide 'common sense' guidance, and also lays out information for the data subject.

However, William Malcolm, a specialist in data protection law at Pinsent Masons, the law firm behind OUT-LAW.COM, described the Code as muddled.

"The Code's high-level guidance on the data life-span, stewardship and accountability is helpful but very much echoes existing guidance from the Information Commissioner's Office and Government," he said. "It's an alternative approach but it's certainly not a new approach."

Malcolm added that some references to the need for consent were wrong.

"The guidance on consent seems inconsistent and therefore muddled," he said. "The initial 'Principles' section [of the Code] suggests consent should be obtained where appropriate, which is the correct position. But the other sections seem to suggest that consent should be collected as a matter of course in a variety of situations."

The 'Principles' section of the Code states: "Individuals should be given as much control as is possible over how their personal information is used and disclosed. This means giving them clear information about this when they provide their personal data and seeking their consent where this is appropriate."

Malcolm says this is consistent with the Data Protection Act and with existing guidance from the ICO.

Another section, though, implies that consent is always required when collecting data. Under the heading 'Responsibilities of the data handler' the Code states: "Data handlers tasked with the collection of personal data should verify that the consent of the data subject has been obtained for the personal data collected."

Malcolm said that notification will suffice in many cases.

"Consent is one ground for processing data, but it is not the only ground. In many cases an organisation only needs to notify individuals that it will be processing their data – it does not need their consent," he said. "As the 'Principles' section of the Code notes, the focus should be on giving clear information about how data will be processed at the point of collection."

Louise Bennett, Chair of the BCS Security Forum, said that the Code is the culmination of two years' work. "The consultation work we've undertaken in that time exposed the need for practical help in changing culture to embed good data guardianship principles in all organisations," she said.

"This is the equivalent of the Highway Code for motorists – it will help all those involved in the management of personal data understand their role and enable them to carry out their jobs better."

Another guide to data protection compliance was launched today. British Standard BS 10012, Data protection – Specification for a personal information management system has been developed to establish best practice and aid compliance with data protection legislation. It is the first standard from BSI for the management of personal information. OUT-LAW will report on BS 10012 shortly.

The code can be downloaded from here. (Link to pdf)

Copyright © 2009, OUT-LAW.com

OUT-LAW.COM is part of international law firm Pinsent Masons.

Beginner's guide to SSL certificates

More from The Register

next story
MI6 oversight report on Lee Rigby murder: US web giants offer 'safe haven for TERRORISM'
PM urged to 'prioritise issue' after Facebook hindsight find
I'll be back (and forward): Hollywood's time travel tribulations
Quick, call the Time Cops to sort out this paradox!
Assange™ slumps back on Ecuador's sofa after detention appeal binned
Swedish court rules there's 'great risk' WikiLeaker will dodge prosecution
NSA mass spying reform KILLED by US Senators
Democrats needed just TWO more votes to keep alive bill reining in some surveillance
prev story

Whitepapers

Driving business with continuous operational intelligence
Introducing an innovative approach offered by ExtraHop for producing continuous operational intelligence.
The total economic impact of Druva inSync
Examining the ROI enterprises may realize by implementing inSync, as they look to improve backup and recovery of endpoint data in a cost-effective manner.
Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
Simplify SSL certificate management across the enterprise
Simple steps to take control of SSL across the enterprise, and recommendations for a management platform for full visibility and single-point of control for these Certificates.