Category Archives: Uncategorized

Tweets and Tw*ts, redux

NOTHING TO SEE HERE, MOVE ALONG.

UPDATE: 13 December 2012

In a tweet to me of 5 December the ICO kindly clarified that there has been no change. The reference to twitter names is now contained in this guidance.

Has there been a subtle change of policy by the ICO on the subject of FOI requests made by twitter?

Last year I blogged about a Freedom of Information Act 2000 (FOIA) request I made to the Information Commissioner’s Office (ICO) via twitter. I referred the ICO to their own guidance (hosted as part of a web page, not as a separate download), which said

The request must state the name of the applicant…A Twitter name may not be the requester’s real name, but the real name may be shown in their linked profile…The request must also state an address ‘for correspondence’. Does this include Twitter names? The length of a tweet makes it difficult for the authority to respond fully, but there are ways of dealing with this. The authority could ask the requester for an email address in order to provide a full response. Alternatively, it could publish the requested information, or a refusal notice, on its website and tweet a link to that.

The question I have given emphasis there did not have a specific answer in the guidance, but one inferred that the answer was “yes” from the words that followed.

This morning I made a twitter FOIA request to the Department for Education, to which they replied asking me to provide an email address or fill in an online form. I was going to refer them to the ICO’s guidance, but found that it doesn’t exist anymore. Fair enough: websites change and URLs get broken. However, unless I am mistaken what I have also found is that the ICO no longer seems to imply that a twitter name is an address for correspondence, according to section 8(1)(b) of FOIA. As far as my search skills can ascertain, the ICO now says

Requests can also be made via the web, or even on social networking sites such as Facebook or Twitter if your public authority uses these…[the request must] include an address for correspondence. This need not be the person’s residential or work address – it can be any address at which you can write to them, including a postal address or email address

No reference there to twitter names. More detailed guidance from the ICO says

Where a request has request in line with section 8(1) of FOIA if the requester has provided their name and a valid address. Where possible a response to the requester should be sent for example by providing a web link. If the name or address is not provided it is not a valid request, therefore if information is not being provided a reply should be sent advising the requester of this, and asking for the required information.

Again, no reference to twitter names.

These changes, unless I have indeed missed something, with their absence of reference to the possibility of a twitter name being “an address for correspondence” indicate a retreat by the ICO. It could well be that they’ve had to acknowledge that twitter is perhaps not the most appropriate medium for FOIA requests. If so, it would be helpful if they could – clearly – issue revised guidance. Their announcement that requests could be made by twitter got a lot of coverage, and led to the highest court in the land accepting that it had been wrong to imply it would not consider them valid requests.

I’ve made a FOIA request to the ICO to find out whether their policy has changed. Guess which medium I used?

UPDATE: 13 December 2012

In a tweet to me of 5 December the ICO kindly clarified that there has been no change. The reference to twitter names is now contained in this guidance.

7 Comments

Filed under Freedom of Information, Information Commissioner, transparency, Uncategorized

Internal Affairs

Has an NHS Trust tried wrongly to prevent publication of information under FOI? Or are they just perhaps (naively) internally exploring the options?

Brace yourselves. Hold on to your china. I have a shocking announcement to make: NOT ALL PUBLIC AUTHORITY STAFF FULLY UNDERSTAND FOI!

In fact, some of them don’t even like it – check out some of the submissions made to the Justice Committee when it was conducting its post-legislative scrutiny of the Freedom of Information Act 2000 (FOIA).

Even worse than those who don’t understand it and say so, are those who don’t understand it but think they do. All practitioners have been faced with the person who announces loudly and wrongly which exemption should be claimed, and won’t accept they’re wrong, because “that’s what we always used to say when I worked at [former employer]”.

These observations are prompted by a twitter exchange, and subsequent Telegraph article yesterday, regarding the accidental disclosure of internal emails by NHS Newcastle-upon-Tyne, in which staff there discuss how to respond to an FOI request. The article reports how the staff considered whether they had to disclose a strategy report, and that the following comments were made

The planned preventative maintenance is all my own work for which I can express intellectual rights…

The…strategy is commercially sensitive and subject to executive approval…Can we say that our Strategy is commercially sensitive and refuse to disclose?

We could refer to [other information] which is in the public domain…It would at least make us look slightly helpful

The Trust clearly did not want this exchange disclosed, because after inadvertently doing so, they tried to use an email recall function, which as we all know, hardly ever works. I don’t blame them – this sort of exchange hardly reflects well on the FOI knowledge of and intentions of, certain staff. If it happened in my organisation I’d toddle on down to their office with a rolled-up copy of ICO guidance and bang them on the head with it (or maybe just suggest they have some training).

However, this sort of exchange goes on daily, in hundreds of public authorities, as hard-working, possibly naive staff grapple with complex FOI requests. They’ll mull things over, discuss options, make ridiculous suggestions, until, ultimately – one hopes – an FOI officer pulls it all together and arrives at a reasoned, fair and lawful decision about disclosure.

Of course that doesn’t always happen, and not all organisations have the bulwark of an honest, good FOI officer in place, but disclosure of internal discussions about potential exemptions, before any final decision on disclosure has been arrived at, does not point towards a potential criminal offence, as some were suggesting on twitter, and it doesn’t really make for a good story.

Leave a comment

Filed under Uncategorized

Stupid, Stupid, Stupid.

How data security is like a car park. Sort of.

Last Friday I parked in my usual car park. I entered it past the signs informing me of the terms for parking there, and the penalties for breaching them. After parking I walked past the signs reminding me in big letters “HAVE YOU PAID AND DISPLAYED?”, and went in to work.

But when I returned later that day I had a ticket on my windscreen – a penalty charge notice – imposed for failing to display a ticket. I still don’t know how I managed to do this. Every other time I have parked, and bought a ticket, and placed it in the same place on the dashboard. But something went wrong this time.

Ever one to draw a clumsy analogy for the sake of a blog post, it got me thinking about data security. We all know how to avoid enforcement action by the Information Commissioner’s Officer (ICO): train your staff, have good policies and procedures and check regularly they’re being complied with. Then, if something goes wrong, the ICO will determine that there was nothing more as an organisation you could do to prevent the incident, and you are not in breach of the Data Protection Act. (Of course it’s a bit more complicated than that. But not much).

However watertight your policies are though, and however often and loudly you remind people about them, mistakes happen. As Einstein is reported to have said “Two things are infinite: the universe and human stupidity; and I’m not sure about the universe.” All you can do is mitigate the risks, and mitigate them sufficiently to satisfy those who regulate you. Thus, the ICO will (should) not impose a Monetary Penalty Notice if you had taken all the data security precautions you reasonably could have taken but one person made a stupid mistake leading to a data breach.

And, because the car park has clear and fair terms and conditions, I won’t challenge the lawfulness of imposing a penalty charge notice just because one stupid individual failed to check that his stupid car had a stupid $%*&ing ticket on the stupid dashboard last Friday morning.

 

1 Comment

Filed under Uncategorized

A Campaign Worth Fighting For

How the Campaign for Freedom of Information was integral to the original enactment of the Freedom of Information Act, and continues to lead on the subject. Support it.

In the mid-1990s my understanding of the concept of Freedom of Information was limited to two points: first, that it was heavily pushed by an organisation called the Campaign for Freedom of Information, and its director, Maurice Frankel and late Chairman, James Cornford and second, that FOI was, surely, unarguably a Good Thing.

In the heady months after Labour’s 1997 election victory it was easy simply to assume that the manifesto commitment to introducing a Freedom of Information Bill would be honoured. While those with more than a passing interest in the subject noted over the following months, with concern, a major retreat from David Clark‘s White Paper Your Right to Know, the Freedom of Information Act 2000, as passed, was still a piece of progressive legislation, very much to be welcomed.

It is interesting, then, to read, in Jack Straw’s recently published, and sometimes rather mean-spirited memoirs, potentially just how little is owed to those who are now seen as the key figures in that Labour administration, and how much is owed to the Campaign for Freedom of Information. Straw describes how the manifesto commitment resulted in a White Paper to parts of which he and Tony Blair were fundamentally opposed:

Tony himself was by now getting extremely worried about the eccentric FOI policy to which his government, in a trance, had seemingly committed itself

and how

I had half a thought that the best thing might to be bin the whole bill, or kick it into the long grass with a Royal Commission

But ranked against him were “all the enthusiasts for FOI-max, ably briefed by the indefatigable Maurice Frankel”.

(Straw effectively, by his account, found himself fighting his own bill. His victory, as he sees it, was to ensure that a power for ministers ultimately to veto disclosure was included. The unsavoury picture painted is of an over-eager administration – committed by its manifesto – unwillingly enacting a progressive law, but ham-stringing it in the process. And of course, we have since had several instances where that ministerial veto has been exercised (twice by Straw himself),, most recently and worringly to prevent disclosure of lobbying correspondence by the Prince of Wales, despite an extraordinarily thorough ruling in favour of disclosure in the Upper Tribunal.)

But this blog post is not about Jack Straw, now sniping from the opposition back benches, and not about the illiberal ministerial veto. It is about what a debt we all have to the Campaign for Freedom of Information, which has continued to argue for a more robust FOI Act, while defending it against threats of diminution. Regarding the latter, it is difficult to over-emphasise the significance of a late submission by the Campaign to the Justice Committee’s post-legislative scrutiny of the Act, which demolished many of the more specious arguments made by those criticising the Act. (Let us hope that the Committee’s welcome final report is accepted by the government, and that those of us who defend the Act can breathe easily, for a time at least.)

I have no personal interest in the Campaign (although I should perhaps declare that Maurice once gifted me a very-well-used-but-broken La Pavoni espresso machine) but it needs celebrating, and cherishing, and supporting (funding will always be an issue with an organisation like this). Everyone who uses and champions FOI should recognise this.

8 Comments

Filed under Uncategorized

Private emails, FOI and Criminality

Private emails are subject to FOI searches, and it’s a crime intentionally to conceal relevant information.

So, it appears that the Department of Education (DfE) has conceded that business emails sent by private email accounts are subject to the Freedom of Information Act 2000 (FOIA), thus accepting what the right-thinking world, and, indeed, anyone with a glimmer of common sense knew all along.

Plaudits, or brickbats, according to your position on the merits of FOIA, should go to Christopher Cook of the Financial Times, who has pursued the Department of Education (DfE) on this with the enthusiasm of a Jack Russell terrier faced with a scurrying rat. Fellow hacks at the Independent had also joined themselves to the proceedings listed (but now withdrawn) in the First-tier Tribunal (Information Rights). The DfE had had the balls to launch a challenge to a previous decision by the Information Commissioner (ICO) that the information (held in private email accounts) requested by Chris should be released. The decision notice itself was clear, and difficult to argue with, as is the advice on the subject published by the ICO around the same time. One wondered what possible grounds the DfE had to base a successful appeal on, and the withdrawal of the appeal probably answers that point, although it appears the withdrawal was actually prompted by the imminent publication of Cabinet Office guidance.

Some are now predicting that there will be a deluge of FOI requests specifically targeted at information held in private emails, or text messages, and I think this is probably right. What is not clear is how they will be handled. The ICO’s guidance suggests that, faced with requests for information that could be held in private emails, public authorities should restrict themselves to asking the person to search their account and keeping a record to show that this was asked:

The public authority will then be able to demonstrate, if required, that appropriate searches have been made in relation to a particular request. The Commissioner may need to see this in the event of a…complaint

This suggests that, when investigating a complaint about refusal to disclose information, the ICO will restrict himself merely to satisfying himself that an authority has asked its staff to check emails. Absent any evidence that those staff have not been honest about the contents of those private emails, the ICO will take no further action. The reasons for this are, really, quite obvious: the powers open to a public authority to access private email accounts are limited. Although the Telecommunications (Lawful Business Practice) (Interception of Communications) Regulations 2000 allow an employer to “intercept” an employee’s private emails  (if sent using the employer’s systems) to determine whether they are business-related, those powers must be exercised with due regard to the employee’s privacy rights. The interception of private emails in a private email account (sent using the employer’s systems) must be necessary and proportionate. If an employee has told his or employer that their private emails contain no information caught by an FOI request it is doubtful, absent any evidence to the contrary, that a “trawl” of emails without the employee’s consent would be lawful (I’ve written for PDP journals on this subject – subscription needed).

On one view, then, nothing much has changed with the concession by the DfE, although no doubt many new FOI requests will be made as a result. What has changed, perhaps, is the focus on individuals’ personal responsiblity under FOIA. Currently, section 77 creates an offence if a person alters, defaces, blocks, erases, destroys or conceals a record in response to an FOI request. If a trawl of emails on a public authority’s systems is required this will normally fall to IT, or similar, and employees have little say – or, if you like, given the existence of back-up systems – limited opportunity to commit a section 77 offence. Now, if the same employee is asked whether private emails contain specific information, and he or she untruthfully says “no”, criminality – the mens rea – will be relatively easy to make out.

The question is, how would we find out?

6 Comments

Filed under Freedom of Information, Information Commissioner, Information Tribunal, Privacy, RIPA, Uncategorized

The Public Interest in the Hillsborough Disaster

How could the Cabinet Office have originally decided the public interest favoured non-disclosure of information held about the Hillsborough Disaster?

On 15 December 2009 Alan Johnson, the then Secretary of State for the Home Department, announced that an Independent Panel would be appointed to enable disclosure of information relating to the 1989 Hillsborough disaster, and the events which followed it. The Panel would lead to

maximum possible public disclosure of governmental and other agency documentation on the events that occurred and their aftermath

As we all know, the Panel has now published an extraordinary amount of information, with a devastating covering report. It was not the Panel’s role to apportion blame for the tragedy but the disclosure has finally led to unequivocal public and political acceptance that, in the words of the Prime Minister, and despite previous despicable insinuations or outright pronouncements to the contrary

Today’s report is black and white. The Liverpool fans “were not the cause of the disaster”.

The efforts of bereaved families and those close to them in effecting this outcome can never be overstated. But a small part was attempted to be played using the Freedom of Information Act 2000. On 23 April 2009 a BBC journalist made an FOI request to the Cabinet Office for

Copies of all briefings and other information provided to Margaret Thatcher in April 1989 relating to the Hillsborough disaster [and] Copies of minutes and any other records of meetings attended by Margaret Thatcher during April 1989 at which the Hillsborough disaster was discussed.

The request was turned down. The Cabinet Office, rather than the 20 working days permitted by law, took nine months (they’re traditionally not very good at this FOI compliance thing, you must understand) to state that the information was exempt from disclosure under sections 31(1)(a), 31(1)(b), 31(1)(g) – which deal with prejudice to law enforcement – and sections 35(1)(a), 35(1)(b) and 35(1)(d) – which deal with information relating to the formulation or development of government policy, Ministerial communications and the operation of any Ministerial private office. All of these exemptions, if engaged, required consideration whether the public interest in disclosure outweighed the public interest in maintaining the exemption. In all instances, the decision was against disclosure: the public interest did not – according to those at the Cabinet Office determining this request – favour disclosure.

On appeal the Information Commissioner disagreed. He said

 the Commissioner considers it clear that the public interest in disclosure of information relating to the Hillsborough disaster – constituting improved public knowledge and understanding of the causes of and reaction to this event (and in relation to this specific information how the Government of the day reacted) – means that the balance of the public interest favours disclosure

He did not accept the Cabinet Office’s argument that the fact that the Independent Panel had now been set up was relevant to a decision as to whether the application of the exemptions was correct

 [the Panel] did not exist at the time of the request, or within 20 working days following the receipt of the request by the public authority. This Notice concerns whether the information should have been disclosed within 20 working days from the receipt of the request, and any factor that did not apply at the time of the request is not relevant

Notwithstanding this, the BBC ultimately agreed to withdraw its request, given the imminence of the outcome of the Panel’s work. And now we know the truth.

The Prime Minister went on to say in his statement

 At the time of the Taylor Report [Margaret Thatcher] was briefed by her private secretary that the defensive and – I quote – ‘close to deceitful’ behaviour of senior South Yorkshire officers was ‘depressingly familiar’. And it is clear that the then government thought it right that the Chief Constable of South Yorkshire should resign. But… governments then and since have simply not done enough to challenge publicly the unjust and untrue narrative that sought to blame the fans.

Information Commissioner decisions requiring disclosure of Cabinet minutes, and similar information, have four times been subject to a ministerial veto to maintain secrecy. Was the initial refusal of the BBC’s FOI request for this Hillborough disaster information simply reflective of a government approach which automatically seeks to exempt any Cabinet minutes from disclosure? I rather hope so, because the alternative is that officials, and ministers, thought that the public interest did not favour disclosure of information relating to what some are calling the biggest cover-up in British history.

UPDATE

I’ve been reflecting on this. I think it’s only fair to point out that, arguably, because the Cabinet Office took so long (nine months, remember) to get round to responding to the request, by the time they did so, the Independent Panel was set up. So, by that argument, the person looking at the request never actually determined that the public interest did or did not favour disclosure, until it was clear that it was going to be published in the future. The Information Commissioner did not accept that point

This Notice concerns whether the information should have been disclosed within 20 working days from the receipt of the request, and any factor that did not apply at the time of the request is not relevant. This situation applies regardless of the lengthy delay

and was correct in law not to, but in fairness to the Cabinet Office officials, they might have handled the request differently (by the time they got round to it) if the Independent Panel, with its remit to disclose, had not been set up.

10 Comments

Filed under BBC, Cabinet Office, Freedom of Information, Information Commissioner, police, Uncategorized

What the Papers Say

It appears that a police officer has inadvertently disclosed operational notes regarding arrangements for the arrest of Julian Assange. This is not the first time a blunder like this has happened, and it should serve as a reminder that physical data needs to handled just as securely as electronic data.

In 2009 Britain’s then most senior counter-terrorism officer, Bob Quick, arrived at Downing Street for an important meeting. He’d probably been reading up on the issues during the journey there, and was clutching a file as he emerged from his car. Unfortunately for him, photographers were able to capture the contents of the document he was holding face up. Marked “Secret” (the second highest category in the government protective marking Security Policy Framework) it contained information some of which still cannot be disclosed because a DA-Notice applies. It led to anti-terror raids being brought forward, and it also led to his resignation.

Now we learn that a rather less senior police officer has been photographed in similar circumstances, outside the Ecuadorian Embassy wherein lies the persecuted activist/suspected rapist (delete according to your leanings) Julian Assange. Apparently the information relates to possible arrest plans.

Now, when I have to carry papers from one building to another at work, I make damn sure that they’re secured in an opaque binder, and as far as I know the eyes of the world’s press are not on me when I’m doing so. Information security and data protection are not just about taking care with electronic data: I recently did a quick analysis of the monetary penalty notices handed down by the Information Commissioner, and found that around two-thirds arose from a breach of security involving physical data*.

Modern photographic developments mean that millions of people have the ability quickly to capture compromising or damaging information, and internet publishing means that the same information can be uploaded and circulated within seconds. The European Association for Visual Data Security (yep, there is one) recently produced a white paper on the subject. In its article about the white paper The Register gave some examples of shoulder-surfing, in addition to Bob Quick’s infamous incident

a senior UK civil servant at the department of Business, Innovation and Skills fell asleep on a commuter train, leaving highly sensitive information displayed on his screen. A fellow passenger took two photographs of the information while it was displayed on the screen, which made their way into a Daily Mail story about the breach…[and] in August 2011 the UK’s International Development Secretary was photographed leaving Number 10 Downing Street with sensitive government papers relating to Afghanistan on display. These papers were caught on camera by news photographers and film crews.

Any organisation which needs to handle data outside its own office walls should make very sure it can’t be seen by prying eyes.

 

 

 

*It’s difficult accurately to categorise them. For instance, a fax is both electronic and physical, and a lost hard-drive is loss of physical data, but seriousness is tied to the electronic contents of said drive.

Leave a comment

Filed under Confidentiality, Data Protection, Information Commissioner, monetary penalty notice, police, Uncategorized

MPs and data protection offences, part three

In previous posts I have written about the apparent failure by several MPs to register with the Information Commissioner’s Officer (ICO) for data protection purposes. I have pointed out that a failure by someone to do so in circumstances where they should constitutes a criminal offence. In the last post I related that I had made a Freedom of Information Act (FOIA) request to the IC asking him what he was doing about these potential offences. I have now received the response.

In general terms Section 21 of the Data Protection Act 1998 creates a criminal offence if a data controller processes personal data without an entry being made in the register held by the ICO: the power to prosecute lies primarily with the ICO itself. MPs process personal data, and the very large majority properly register this processing (which costs them £35 a year – in contrast to the £500 notification fee for larger data controllers). However, FOI requests over recent months have revealed that several MPs have not only failed to do so, but their failure has continued despite the ICO reminding them of their obligation.

On 10 May I wrote to the ICO, naming the then 22* MPs who had not registered, and asking

Please inform me…

1. What enforcement action has been taken against these MPs?

2. How many reminders each has been given (I understand you normally operate a two-reminder, then enforcement, system)

3. In addition to these 22, how many other MPs have not renewed
their notification? (as more than seven months have elapsed I
presume there will be some additional notifications which have
lapsed)

(As for the third question, I was sent a spreadsheet showing (as at 24 May) all MPs and their notification record. (Interestingly, two MPs who have been elected to the House of Commons in the last two years have no registration showing at all – Debbie Abrahams and Louise Mensch)).

As for the second question, the ICO’s reply comes with an attachment showing that – with three exceptions – the 22 MPs in question had all received two reminders (one had received only one reminder, and two – because of a technical glitch – had received none). The reply also came with some explanatory comments to the effect that

it is the responsibility of the Data Controller to assess their data processing at that point and make a determination as to whether notification is still required…We provide a reminder service to notified entities to help them maintain their notification. However, because there are legitimate reasons why many Data Controllers may not need to renew their notification once it expires, we do not actively pursue all 350,000 of our annual renewals.

These points are well-made. However, regarding the first question (what enforcement action had taken place) I was told

no enforcement action has been taken against these MP’s.

By explanation a distinction was drawn between the “reminder” service, and the non-notification enforcement activities of the ICO, and

Our non notification activities are targeted at particularly high risk or under represented groups or sectors.

This seems to suggest that, even where non-notification – a potential criminal offence, remember – by MPs is drawn to the IC’s attention he will not take enforcement action unless MPs form part of a group of data controllers who are being specifically targetted by the ICO.

I’m really struggling with this. I understand the extreme resource pressures the ICO has to cope with, and I even understand that taking action against MPs ((perhaps as far as prosecuting them) is not a very attractive proposition for a sometimes beleaguered regulator, but the evidence points towards named MPs failing persistently to comply with a legal obligation – even when reminded by the regulator. If law makers break the law, and the enforcer turns a blind eye, why would anyone else feel the need to obey that law?

The full request can be seen at http://www.whatdotheyknow.com/request/enforcement_of_section_18_dpa/new

*One of the 22 – Shailesh Vara – appears since to have registered

13 Comments

Filed under Uncategorized

When ARE emails subject to FOIA?

Information held in private email accounts can be subject to the Freedom of Information Act 2000. Conversely, information held in the email accounts of the public authority can, in some circumstances, not be subject to FOIA. A recent decision by the Information Commissioner (ICO) confirms this.

There has been much recent discussion and argument about the extent to which information contained in “private” email accounts (such as “gmail”, “hotmail” etc) can be said to be “held on behalf of” a public authority under FOIA. The ICO issued guidance in December 2011 that says in unequivocal terms

 FOIA applies to official information held in private email accounts (and other media formats) when held on behalf of the public authority.

No one sensible who knows anything about FOIA is likely to disagree with this.

In a Decision Notice against the Department for Education (DfE), issued after this guidance was published, the ICO applied these principles to a request for information made by the Financial Times’ Christopher Cook. Cook, in an interesting twist, already had leaked “private” emails in his possession, and was seeking information corroborating certain details about them. He showed one of these emails to the ICO, whose subsequent Decision Notice said

 The Commissioner has reviewed this email and found that whilst it was sent from a private email account it was held on behalf of the DfE for the purposes of the Act. By failing to disclose details of the email the DfE breached section 1 of the Act

(It is understood that the DfE is going to appeal this Decision Notice to the Information Tribunal.)

What has been overlooked, to a certain extent, in all this is the corollary of the proposition that “FOIA applies to official information held in private email accounts (and other media formats) when held on behalf of the public authority” which is, that FOIA does not apply to private information held in public authority email accounts, when it is not held on behalf of that authority.

Thus, for example, an email from a employee, or an elected member, of a public authority asking her partner to feed the cat this evening, is highly unlikely to be considered to be information “held” by the public authority for the purposes of FOIA. This is because section 3(2)(a) of FOIA says

information is held by a public authority if…it is held by the authority, otherwise than on behalf of another person

Private information might physically be stored on the email servers of the public authority, but for the purposes of FOIA it is being “held on behalf of” the employee (for our purposes here we don’t need to consider whether the terms of employment actually allow the employee to use the employer’s systems to engage in private correspondence).

In a Decision Notice published on 27 March the ICO has affirmed this position. A complainant had sought copies of emails received or sent by a councillor at Camden Council, on his “camden.gov.uk” address. The complainant argued

…that use of a camden.gov.uk email address for correspondence explicitly renders any correspondence on that email account part of the business of the council

The ICO rejected this submission:

 the Commissioner observes that none of these emails are about council business but instead relate either to correspondence between the councillor and constituents in his role as a ward councillor, or to personal matters of the councillor, or business which is external to his council activities… Because this information is not council business, it cannot be argued to be held by the councillor on behalf of the council. It may instead be considered to be held by the council, on behalf of the councillor as an individual, solely by virtue of being hosted on the council’s email systems.

Those previously concerned about the implications of the ICO’s guidance on private emails might take some reassurance from this statement about the limits of FOIA. However, there may also be a lesson for public authorities themselves: it is not safe always to assume that an email sent from or received by an employee’s work email account is subject to FOIA.

8 Comments

Filed under Freedom of Information, Information Commissioner, Uncategorized

Open Justice Charter versus Privacy Rights

 The Guardian has published an article suggesting court lists should be freely available as part of a drive towards open data. William Perrin, in his own words a local active citizen, proposes (“with the government’s drive to transparency and open data “) a charter for transparency in the courts under which

people should be able to find out easily, on the internet:
what cases are expected to come up in a court from the time that they are scheduled
name, address and specific charges in all cases available from the time the case is scheduled (see footnote)
the full names, including first names, of judges, prosecution and defence lawyers, witnesses, and other professionals who speak during proceedings (e.g. magistrates’ clerks giving legal advice) from when they are known
judgements handed down from the end of the working day on which the case is concluded

Footnote

In criminal cases, the following basic information should be readily available
The full spelling of a defendant’s name
Their date of birth and full home address, including door number and postcode
The charges against them (including an opportunity to read them)
Written copies of any reporting restrictions applicable in the case

Perrin appreciates some of the risks

All the above is subject to contempt of court and protection of vulnerable defendants and witnesses

but

The longstanding openness of courts must not be compromised by data protection. In particular, well meaning but misplaced concerns about the data protection act and copyright must not stop the recording and transmission of information presented in open court.

(In passing, I struggle to understand his contrasting of “codified” data protection and copyright and “uncodified” open justice. If by “codified” he is referring to written laws and procedures then I would refer him to, in particular,  rule 39.2(1) of the Civil Procedure Rules, which provides that “The general rule is that a hearing is to be in public”. This is reinforced by our Convention rights, given full domestic effect in the Human Rights Act 1998. Article 6 says

In the determination of his civil rights and obligations or of any criminal charge against him, everyone is entitled to a fair and public hearing within a reasonable time by an independent and impartial tribunal established by law. Judgement shall be pronounced publicly by the press… (emphasis added))

Justice certainly should be, as a general principle, open. It is an ancient concept – it goes to the heart of the judicial system.  Lord Halsbury famously said, in 1913

Publicity is the very sole of justice…and the surest of all guards against improbity (Scott v Scott 1913 AC 417)

and Lord Diplock, in 1979

The application of this principle of open justice has two aspects: as respects proceedings in the court itself it requires that they should be held in open court to which the press and public are admitted and that, in criminal cases at any rate, all evidence communicated to the court is communicated publicly. As respects the publication to a wider public of fair and accurate reports of proceedings that have taken place in court the principle requires that nothing should be done to discourage this (Attorney-General  v Leveller Magazine Ltd. and Others [1979] A.C. 440)

At the recent Justice Wide Open event at CityUniversity, I saw Perrin speak eloquently about his experiences of trying to engage as a member of public in his local courts. He and other speakers gave dispiriting accounts of misinformed court staff and the paucity of reporters covering court news.  Addressing these shortfalls is a worthy aim, and I would not want to be seen as in any way criticising someone for doing that. Perrin, however, appears to see data protection (and perhaps to a lesser extent, the law of copyright) as contributing to an erosion of open justice.

The DPA has its origins – in part – in concerns about the potential for harm caused by electronic processing of personal information. As far back as 1972 the Younger Committee on Privacy had recognised public concerns about the accumulation by the state of electronic databanks. Electronic processing power has increased immeasurably since then, and it is in the light of that increase that we must consider proposals to open up the personal data of those appearing in court.

The DPA gives effect to theUK’s obligation under Directive 95/46/EC on the protection of individuals with regard to the processing of personal data and on the free movement of such data. In very broad terms it requires that those who “process” “personal data” in the role of “data controller” do so in compliance with the Act and specifically with eight data protection principles (at Schedule 1). Failure to do so can in some circumstances constitute a criminal offence. The DPA is enforced primarily by the Information Commissioner (IC) who has various powers, including one to impose monetary penalties (to a maximum of £500,000 for serious breaches of the Act).

Personal data are

data which relate to a living individual who can be identified from that data

so, clearly, someone’s name, address and criminal charge would be personal data

“Processing” is defined as

obtaining, recording or holding the information or data or carrying out any operation or set of operations on the information or data

Publishing court listings on the internet would be classed as “carrying out an operation on the data”. Under Perrin’s proposals it would appear to be, at least in the first instance, the courts themselves which would be disclosing. The courts would certainly be classed as data controllers (the “person who…determines the purposes for which and the manner in which any personal data are…processed”). They would, therefore, have to process the personal data in accordance with the Act.

Just because personal data are or might be considered to be in the public domain, this does not necessarily authorise further processing. In R (on the application of Robertson) v City Of Wakefield Metropolitan Council [2001] EWHC Admin 915 the High Court held that the sale of the electoral register to commercial concerns was in breach of section 11 of the DPA (which gives data subjects the right to object to direct marketing based on their personal data) and of their Article 8 rights. Kay J rejected a submission that because an individual could not object to public right of inspection of the electoral register, there was not an actionable breach of these Article 8 rights arising from the sale of the same (and he could have equally rejected a similar submission on DPA grounds). The collection and publishing of personal data in the form of an electoral register available for physical public inspection was prescribed in law, and was a legitimate form of processing; its sale to commercial interests was not.

For similar reasons the Information Commissioner advises planning authorities that, although they may have a statutory duty to maintain, and make available for physical public inspection, a register of planning applications including objections

Extreme care should be taken to avoid any unnecessary disclosure of telephone numbers, email addresses and signatures. The need for the local authority to hold such information is obviously of benefit to all parties. However, there is no requirement to make it publicly available on the Internet… The recommendation…is that the applicant’s telephone number, email address and signature should not be visible via a website or other online system.

The DPA says that information about criminal offences will almost certainly be “sensitive personal data”, which includes

Personal data consisting of information as to… the commission or alleged commission by [the data subject] of any offence, or…any proceedings for any offence committed or alleged to have been committed by him, the disposal of such proceedings or the sentence of any court in such proceedings.

Such data must be processed fairly and lawfully, but also at least one condition in Schedule 3 must be met. In simple terms, Schedule 3 will, broadly, for the current purposes, only permit processing of sensitive personal data if the data subject has explicitly consented to it,  if it is required by law or if it is necessary for the purposes of legal proceedings or the administration of justice.

Even the posting outside the court room of lists is processing of sensitive personal data, and, although there is some inconsistency (I have heard, for instance, that some courts tweet the names of defendants) the general approach is that these lists are not published widely by the court service. (To the limited extent that they are published I would suggest that the processing would be justified by an argument that it is necessary for the purposes of legal proceedings or the administration of justice.)

The problem with publishing, on the internet, the sort of information Perrin’s charter proposes, is that the internet has few limits, whether special, technological or temporal.

Anyone, in any country, could harvest the data published. They could amass huge data banks not just of criminals, but those who have merely been charged with an offence, as well as witnesses. If that information is then tied to their address (and date of birth) hugely sensitive databases could be created, about which there might be little knowledge, and over which there might be little control. In 2009 the Information Commissioner prosecuted a man called Ian Kerr for running a secret blacklist of containing information about construction workers’ personal relationships, trade union activity and employment history. Kerr created the blacklist on behalf of an organisation called The Consulting Association. The Commissioner only had jurisdiction because this processing of personal data took place in theUK. A blacklist amassed from court data, and hosted outside the EU, could be hugely damaging to the employment prospects of countless people, whether they be convicted, charged and not convicted, or even merely witnesses.

Moreover, this information could be kept indefinitely. Rehabilitation of offenders, and the laws that underpin the rehabilitation could be greatly compromised if this sort of court data is openly available for anyone to retain and archive. In S and Marper v United Kingdom 30562/04 [2008] ECHR 1581 the European Court of Human Rights held that the indefinite retention of DNA samples of people who had been arrested or charged, but not convicted of an offence, was a violation of Article 8 of the Convention, and observed that

The protection of personal data is of fundamental importance to a person’s enjoyment of his or her right to respect for private and family life, as guaranteed by Article 8 of the Convention. The domestic law must afford appropriate safeguards to prevent any such use of personal data as may be inconsistent with the guarantees of this Article

Marper was concerned with the indefinite retention of sensitive information under a state measure authorising its retention. Perrin’s charter is silent on how long the information it describes should be retained, or remain published, and it would be interesting to see how it would fit into the proposed new European data protection framework [pdf] which proposes a “right to be forgotten” (a right which in fact arguably already exists under principle 3 and 5 of the DPA), but even if the state or an emanation of the state deleted the data at a later date, it is difficult to see how any restrictions could be imposed on the information which would prevent its retention (even if such retention was unlawful) by private individuals, or organisations, or even other emanations of the state.

The permanence of internet-published information, and the ease with which it can be harvested and disseminated, could also greatly increase the risk of witness (and judge, and lawyer, and court official) intimidation or retribution, and most strategies for prevention [pdf] of this understandably focus on restricting the amount of information.

And, ultimately, mistakes and crimes often occur with the electronic processing of personal data. Given the huge financial pressures the court system is currently experiencing, it is very difficult to imagine that there could never be a data breach, and if one occurred it would potentially involve the personal data of vulnerable victims of crime, as well as witness, and those accused.

For these reasons, and absent any major change in the UK data protection statutory scheme (which in turn would suggest there would have had to have been a major change in the European framework) I have doubts that Perrin’s charter, as currently presented, could operate without the people acting under it being at risk of breach of the DPA, and potentially in violation of Article 8.

Those who work in the field of data protection are often accused of putting barriers in the way of progress, and of effective working. I don’t accept this: I’m an advocate of good data protection, but I’m also an advocate of freedom of information, transparency and open justice. It seems clear that the court system could be better at promoting open justice without disproportionately infringing private rights. However, I don’t think that Perrin’s charter is the way forward, because I do not feel it goes anywhere near far enough in adequately protecting the personal information of those who would be publicised under it.

Addendum 9 May 2012

Since writing this blog post my attention has been drawn to the Magistrates Court Act 1980 (thanks @Greg_Callus on twitter). Section 8 deals with restrictions on reporting of commital proceedings, and, by way of s8(4) permits publication of

(a)the identity of the court and the names of the examining justices;

(b)the names, addresses and occupations of the parties and witnesses and the ages of the accused and witnesses;

(c)the offence or offences, or a summary of them, with which the accused is or are charged;

(d)the names of the legal representatives engaged in the proceedings;

(e)any decision of the court to commit the accused or any of the accused for trial, and any decision of the court on the disposal of the case of any accused not committed;

(f)where the court commits the accused or any of the accused for trial, the charge or charges, or a summary of them, on which he is committed and the court to which he is committed;

(g)where the committal proceedings are adjourned, the date and place to which they are adjourned;

(h)any arrangements as to bail on committal or adjournment;

(i)whether a right to representation funded by the Legal Services Commission as part of the Criminal Defence Service was granted to the accused or any of the accused.

These provisions of the MCA appear to have been drafted in order to prevent the risk of prejudice to forthcoming trials, rather than with a view to protecting any privacy rights of accused. Nonetheless, they clearly, in general terms, permit publication of the sort of information proposed by Will Perrin’s Open Justice Charter. Whether the ICO would consider that they were sufficient to mean that a Schedule 3 DPA condition were met is another matter. The Data Protection (Processing of Sensitive Personal Data) Order 2000 does provide a Schedule 3 condition if the disclosure “is in the substantial public interest…[and]…is in connection with…the commission by any person of any unlawful act (whether alleged or established)…[and]…is for the special purpose [of journalism]”. However, can a blog, even one as clearly public-focussed as Perrin’s, be classed as “journalism”?

The MCA was enacted long before the internet as we know it was even conceived (it was amended in 1990 to encompass television broadcasts) and the DPA was enacted in the modern internet’s infancy. “Journalism” has no fixed definition, probably for very pragmatic reasons, but modern technology means that many people, such as bloggers, social commentators, twitter users, etc, are engaging, to a greater or lesser extent, in activities which might broadly be defined as journalism.

This leads on to wonder, in an age when “we are all journalists”, might we all benefit from the common law and statutory protections afforded to journalism? And, if so, in what way could journalism benefit from being a special category under laws such as the DPA?

5 Comments

Filed under Uncategorized