Explaining the term 'Privacy Policy'

The term 'Privacy Policy' is most often used in an online environment to describe a document which explains to individuals how information about them is collected and used. It may also touch on the wider data protection policy of the organisation. It is important to note that 'Privacy Policy' is not a legal term (at least not in the UK) but a user friendly one. Data protection lawyers typically refer to the document which provides an individual with information about how information about them is used as a 'privacy notice'. The requirements for what should be in such a notice are in articles 13 and 14 of the UK GDPR. Typically an organisation which operates mostly in a real world environment will have a number of privacy notices for different categories of individuals and separate data protection policy. Online, the term 'privacy policy' may refer to something which is designed to cover the requirements under articles 13 or14 or it may be more of a hybrid between 'privacy notice' and 'data protection policy'.

Guidance produced by the Information Commissioner's Office (ICO) does not refer to the term 'privacy policy'. The term 'privacy notice' is normally used by the ICO both in guidance and in their own privacy notices. However, I have noticed that there is one exception; if you click on the link for the privacy notice template then it is, in fact, headed 'Privacy Policy'.  All the notes in it then use the term 'privacy notice'. My conjecture is that the ICO takes the line that their guidance should use the term 'privacy notice' but that this heading on the template slipped through the net.

The overall conclusion is that the confusion around the term 'privacy policy' is ubiquitous.  'Privacy policy' may mean the same thing as 'privacy notice' but be aware that a 'privacy policy' may sometimes incorporate an element of data protection policy.


The ICO cannot lead on reducing barriers to data sharing

Those of you who follow data protection matters closely will know that the ICO's new Data Sharing Code of Practice is waiting to be laid before Parliament for approval. The Information Commissioner, Elizabeth Denham, spoke to the Public Services Committee on 13th January 2021. Following on from this, the Information Commissioner wrote to Lady Armstrong and this letter was published yesterday. It contains some general observations as to the limitations of the Code as a statutory code but the most interesting aspect of the letter is what the Information Commissioner says about the ICO's role in reducing barriers to data sharing which I quote below:

'However, what was clear from our discussion at the hearing, and from thewitnesses that followed, was a recognition that the task of reducing barriers to data sharing is too big to be undertaken by one body in isolation. It needs a cooperative and coordinated effort from stakeholders across society. We see this as a partnership between government, parliament, the regulator, and those sectors at the frontline of data sharing.

The ICO cannot lead the work. This is due to our status as regulator; there is a need for us to strike a balance between our role of giving advice and support to organisations undertaking data sharing, and our need to take appropriate action to protect the data rights of citizens if there is a breach of the law.'


An Early Christmas Present from the ICO - A new Data Sharing Code

The ICO published a new Data Sharing Code of Practice yesterday (17th December 2020). A welcome Christmas present as we have been without an up to date Data Sharing Code since the GDPR came into force in May 2018. This Code is a statutory one and the ICO says it will use the Code in its work to assess the compliance of controllers through its audit programme and other activities. It also says it will take the Code into account when considering whether an organisation has complied with the GDPR or DPA 2018, particularly when considering questions of fairness, lawfulness, transparency and accountability.

The new Code stresses the importance of the Accountability Principle in making data sharing decisions. There is also a heavy emphasis on doing DPIAs (Data Protection Impact Assessments) as a matter of good practice even where they are not legally required. This has been the direction of travel for some time and is logical given the need to show accountability. This Code does reinforce this to such an extent that it would appear unwise to proceed with any planned data sharing without a DPIA except in cases where there is obviously very little risk to individuals.

Data sharing agreements are covered in some detail in the new Code with helpful guidance as to what they should contain. A data sharing agreement is not actually a legal requirement except in a joint controller situation but the ICO says, ‘A data sharing agreement between the parties sending and receiving data can form a major part of your compliance with the accountability principle, although it is not mandatory’.  In practice, the ICO expects to see such agreements in place for any routine data sharing arrangements and this is already clear in the ICO audit outcomes which I have seen.

Most of what the Code does is to help an organisation go through the necessary procedural steps to share personal data in a compliant fashion. There are no easy shortcuts  or magic answers here though and the Code amounts to more of a ‘How to’ Guide than an answer booklet.

One final point of note is that the Code contains a page and a half of information on due diligence and data sharing in mergers and acquisitions. The previous code had just a short paragraph. This reflects a growing focus on data rights in this situation. I have been plugging the importance of early consideration of data issues in such situations for some time as I think they are often overlooked entirely or only raised late in the transaction. There have been ICO fines that came about because of failures in due diligence on an acquisition, e.g. Marriott Hotels. The European Data Protection Board has also pointed out the need to consider the privacy implications of mergers through its statement earlier this year.  This Code provides a clear bullet pointed list of what needs to be covered in such a situation.


Big Fish v. Small Fish - Bargaining Position as between Controller and Processor

The European Data Protection Board is consulting on its Guidelines on the concepts of controller and processor in the GDPR until 19 October 2020.  They are long and detailed and only likely to be read by those with a serious interest in the GDPR. I thought I would highlight what I found to be a very interesting paragraph (107) in relation to data processing agreements which may be included in a service provider's standard terms and conditions.

'The fact that the contract and its detailed terms of business are prepared by the service provider rather
than by the controller is not in itself problematic and is not in itself a sufficient basis to conclude that
the service provider should be considered as a controller. Also, the imbalance in the contractual power
of a small data controller with respect to big service providers should not be considered as a
justification for the controller to accept clauses and terms of contracts which are not in compliance
with data protection law, nor can it discharge the controller from its data protection obligations. The
controller must evaluate the terms and in so far as it freely accepts them and makes use of the service,
it has also accepted full responsibility for compliance with the GDPR. Any proposed modification, by a
processor, of data processing agreements included in standard terms and conditions should be directly
notified to and approved by the controller. The mere publication of these modifications on the
processor’s website is not compliant with Article 28.'

In short, a small controller cannot use its poor bargaining position as an excuse for poor GDPR compliance but large processors cannot abuse their bargaining position by simply dictating terms.


Artificial Intelligence and identifying Controllers and Processors - 2021 may bring further clarity

The ICO has just published new guidance on Artificial Intelligence (AI). I wrote a detailed blog piece on the consultation version so I will not write about it generally now. However, some important new information is that the ICO has acknowledged  that AI systems involve a number of organisations and so working out who is a Controller or Processor for the purposes of data protection law can become complex. The ICO plans to address these issues in more detail when it revises its Cloud Computing Guidance in 2021. It will consult with stakeholders because of the questions of policy raised. Most helpfully, the new guidance will include example scenarios covering when an organisation is a Controller or Processor in the context of AI services.


The Fall of the Privacy Shield – What next? The ICO and the EDPB have different approaches

The decision of the European Court of Justice in Case C-311/18 – Data Protection Commissioner v Facebook Ireland and Maximillian Schrems struck down the EU-US Privacy Shield with immediate effect. This caused gasps of horror in the data protection world and more widely as people realised just how significant this judgement was and just how often the Privacy Shield was the mechanism under which personal data was being transferred to the US. Initial articles on the subject sometimes mentioned using Standard Contractual Clauses (SCCs) instead as they appeared to have survived the Court’s scrutiny. Then there was the slow recognition that there were serious question marks over the use of SCCs as US law does not ensure an equivalent level of protection for personal data.

Such were the repercussions of the judgement and the many questions being asked that on 23 July the EDPB (European Data Protection Board) adopted a set of Frequently Asked Questions (FAQ). These are helpful to a point but by no means provide any real answer to the problems caused by the judgment. What is most interesting is the stark contrast between the EDPB’s approach and that of the ICO. The EDPB FAQ document says of the Privacy Shield, ‘Transfers on the basis of this legal framework are illegal’.  However, a visit to the Privacy Shield page of the ICO website reveals a statement as follows:

‘We are currently reviewing our Privacy Shield guidance after the judgment issued by the European Court of Justice on Thursday 16 July 2020.If you are currently using Privacy Shield please continue to do so until new guidance becomes available. Please do not start to use Privacy Shield during this period’

However, continuing to use the Privacy Shield carries risks, even if one assumes that there is no risk of ICO enforcement while the ICO statement remains as above. For example, individuals could bring claims for compensation.  The ICO has not mentioned this but the Berlin Data Protection Authority has referred to it in a press release (which is only available in German) and has also told organisations in Berlin to shift their data storage from the US back to Europe.

IMPORTANT UPDATE: On 27th July 2020, the ICO changed its statement on its website to read:

'The judgment in the Schrems II case issued by the European Court of Justice on Thursday 16 July 2020 found that Privacy Shield is no longer a valid way to transfer personal data outside of the EEA. For more information please read our latest statement.'

This statement brought it into line with the EDPB.


The End of the Brexit Transition Period - Will we get an Adequacy Decision?

The European Commission has issued a communication to all member states about the changes they can expect after 31 December 2020. A small part of this covers data protection.  It explains that there are existing mechanisms under the GDPR to allow transfers of personal data to a third country and that these can be deployed for the UK. However, will one of these be an adequacy decision?

This communication says ‘As underlined in the Political Declaration, the EU will use its best endeavours to conclude the assessment of the UK regime by the end of 2020 with a view to possibly adopting a decision if the United Kingdom meets the applicable conditions. The Commission is currently conducting this assessment and has held a number of technical meetings with the United Kingdom to gather information in order to inform the process’

The clear advice for businesses in the EU is that they should plan ahead including for the scenario where there is no adequacy decision in respect of the UK. A hint perhaps that an adequacy decision may not be forthcoming.


Workplace Testing for Covid-19 - A joint HR and Data Protection Perspective

Kate Grimley Evans and Caroline Banwell of Harmony HR Solutions have collaborated to provide a unique and helpful perspective on Workplace Testing for Covid-19,


Apple and Google joint initiative on COVID-19 contact tracing technology

The Information Commissioner has published her official Opinion on the Contact Tracing Framework being developed by Apple and Google. This opinion should be read with care with its stated limitations taken into account, in particular the fact that it is limited to the Framework itself and does not extend to Apps developed using it. It also only applies to phase 1 of the project and a more expansive phase 2 is already envisaged.

The Commissioner reaches the conclusion that the Framework is aligned with the principles of data protection by design and by default but it is still clear that there are a number of potential data protection risks which could arise from the way in which it is used, in particular if an app processes data outside the intended scope of the Framework. The Information Commissioner's opinion highlights the risk that users of a contact tracing app might not understand that the data protection by design and by default principles used in the Framework do not extend to all aspects of the app.

Most current proposals for contact tracing apps would rely on consent as the lawful basis for processing and the Commissioner points out that it is not yet clear how consent management will work or what the practical implications of a withdrawal of consent are.

To my mind, the biggest risk to the privacy of individuals would potentially be from 'scope creep' which describes the way in which it is possible that third party app developers will expand the use of Covid-19 tracing apps using the Framework beyond that original stated purpose. The Commissioner mentions this in her Opinion and reassuringly says she will monitor all developments.


Morrisons wins its Supreme Court Case

In a judgement issued on 1st April 2020, the Supreme Court held that Morrisons (i.e WM Morrison Supermarkets plc) was not vicariously liable for the actions of its employee when, motivated by vengeance against Morrisons, he placed the personal data of thousands of Morrisons employees onto a public file sharing site. The judgement contains a long discussion of the case law on vicarious liability which will be of most interest to employment lawyers. The key vicarious liability point was that the employee's bad motive was highly relevant. There is, however, a key data protection point which is that, despite the conclusion on the facts that Morrisons was not vicariously liable, there was nothing in the DPA 1998 which excluded the operation of vicarious liability. On the basis that a similar conclusion is likely to be reached in relation to the Data Protection Act 2018, there is still the distinct possibility that, in the future, on a different set of facts, an employer will find itself vicariously liable for a data protection breach committed by its employee.