In September, the UK’s Department for Digital, Culture, Media & Sport (DCMS) released a consultation document about the future of data protection law in the UK.
The consultation proposes a raft of changes to the UK’s data protection law. Some are small changes and clarifications intended to resolve uncertainties in the GDPR’s drafting, while others are fundamental reforms to the operation of the UK’s data protection laws and the obligations and protections they bring. All organisations operating in the UK should be interested in potential changes to:
There are also proposals of significant interest to those involved in research and AI, and reforms on the powers and governance of the ICO, the supervisory authority.
The consultation is open to all respondents until 19 November 2021. The DCMS document sets out structured questions on each of the proposed changes, and encourages respondents to provide their own views and experiences on the challenges and possible solutions that the UK’s current regime presents. Below, we summarise the main changes proposed in the consultation document, with a colour coding showing the degree of change to the UK’s existing data protection compliance framework. Green means that a proposal makes no significant change to existing legal framework; amber a medium change; and red a significant change.
Suggested reform | Paragraph reference | Impact |
Amend the data subject access request provisions to introduce a cost limit modelled on the Freedom of Information Act. | 188 |
This proposal will be welcomed by controllers in the UK. Many organisations have felt the burden of “weaponised DSARs” and the introduction of a cost limit would reduce this burden. The suggestion made by DCMS is that this should be based on the existing and well-established regime under the Freedom of Information Act, which allows public authorities to refuse freedom of information requests which cost more than £450 - £600 (depending on the type of organisation). Interested parties wishing to respond to the consultation should consider submitting information about what the cost limit should be, or criteria used to establish it. A sliding scale depending on turnover and sector may be a good model.
Suggested reform | Paragraph reference | Impact |
Introducing “privacy management programmes” as a compliance requirement | 145 | |
DPO requirement to be replaced with a requirement for a suitable individual responsible for the privacy management programme | 163 | |
Removal of DPIAs in favour of allowing organisations to choose their own approach to assessing privacy risks | 167 | |
Replace Record of Processing Activities with a personal data inventory, as part of the privacy management programme | 177 | |
Raise the threshold for data breach reporting to the ICO | 180 |
The departure from the existing GDPR framework for accountability is puzzling. DCMS’ stated reason for the proposed reform is that current accountability obligations place a “disproportionate administrative burden” on organisations, yet its proposals involve replacing existing accountability requirements with other very similar (and no less burdensome) obligations. With the exception of the higher threshold for breach reporting, all other accountability requirements have been replaced with a different compliance requirement, often with the choice of the format left to organisations. This would likely create more work for organisations, who would need to assess whether their existing GDPR documentation matched the new UK requirements. For example, there is a suggestion that GDPR-DPOs could not serve as the person responsible for the privacy management programme (as the independence they require for GDPR purposes would – implicitly – disqualify them from this new role), so that an organisation which chose to retain its DPO would need to appoint an additional data protection professional [164]. The proposals seem to diverge from the GDPR without providing any discernible benefit to organisations in the UK.
Suggested reform | Paragraph reference | Impact |
Introduce alternative transfer mechanisms, including allowing organisations to identify their own mechanism as appropriate | 261 | |
Expand use of Article 49 derogations to repetitive transfers | 270 | |
Encourage use of certification mechanism | 267 |
In the wake of Schrems II and the associated EDPB guidance, transferring data out of the EU and UK has been complicated. The consultation proposes a number of reforms to improve the UK aspect of this, from encouraging adoption of existing mechanisms (use of codes of conduct) to widening existing mechanisms (such as the derogations under Article 49 GDPR). It also includes a more controversial proposal to allow exporters to make their own decisions about how to protect personal data being transferred out of the UK, including by using contracts developed by the contracting parties without the ICO’s review or approval. This proposal is based on the approach taken in New Zealand and that was possible in the UK under the Data Protection Act 1998.
There are also proposals to change the process for the UK’s adequacy assessment of third countries (see paras 247-254), which are not assessed in this article as they do not directly affect compliance requirements.
Suggested reform | Paragraph reference | Impact |
No consent needed for analytics cookies and possibly other “low risk” trackers. | 198 | |
Call for views on how to reduce consent fatigue for cookie consent | 206 | No clear proposal yet |
Expansion of soft opt-in to non-commercial organisations – and possible complete exemption of political parties from PECR | 223 | |
Increase fines under the Privacy of Electronics Communications Regulations to match fines under the UK GDPR | 216 | |
Nuisance calls: tweak legislation such that the ICO can take into consideration calls made by the controller, not just calls received by the data subjects | 212 | |
Obligation on communication providers to report fraudsters to the ICO | 215 |
The consultation has widely been announced as a reform of the UK GDPR, yet a section on the UK’s Privacy of Electronics Communications Regulations has also been included. Most changes in this area are relatively minor and are likely to be welcomed both by controllers and data subjects. There is an attempt to obtain cross-party support for at least some of the proposals by proposing to exempt political parties from these rules in their entirety, although the consultation document does acknowledge that the prospect of receiving automated calls from political parties may not be welcomed by everyone.
The proposal also includes a call for views on how organisations could comply with the GDPR’s principles of lawfulness, fairness and transparency “without use of the cookie pop-up notices”. This section references browser settings as a possible option but offers no other suggestions, so it is hard to assess the possible impact of this.
Suggested reform | Paragraph reference | Impact |
Group all GDPR and DPA legal provisions relating to research for ease of reading | 40 | |
Incorporate the definition of scientific research into law (currently interpretative aid in the GDPR recitals) | 42 | |
Clarify when universities can rely on the public interest condition under Article 6 | 44 | |
Create a new legal basis for research under Article 6 | 44 | |
Broad consent to be permissible for research purposes | 48 | |
Changes to how to assess whether a secondary processing purpose is incompatible with the original purpose | 54 | |
Apply the “disproportionate effort” exemption for privacy notices to Article 13, not just Article 14 | 50 |
In line with the UK government’s National Data Strategy, the consultation document pushes for reforms to encourage research in the UK. The document stresses that data protection laws are complex and difficult to navigate, which discourages researchers from using personal data.
The proposal to consolidate all research-specific data protection provisions may achieve the aim of brining greater clarity to the area, though it is unlikely to have a strong impact. The proposal also suggests moving a number of research-related recitals into the Articles of the UK GDPR, to increase legal certainty. As part of this, the UK GDPR would define scientific research in law, and the consultation seeks views as to what this should be defined as.
There is also a proposal to include a new legal basis for scientific research under Article 6 UK GDPR, to match the condition for processing sensitive personal data for research purposes under Article 9. Currently, researchers would be likely to rely on either research being necessary for a task in the public interest or necessary for a legitimate interest, so it is unclear what benefit this would bring; further, to the extent clarity could help, it could be achieved by guidance instead of primary legislation.
Much of the discussion on research focuses on challenges faced by universities. The private sector is also a critical part of the UK research base and it would be advisable for private sector organisations engaging in research to make clear to DCMS that their interests must also be considered.
The consultation includes a number of proposals on how to change the law relating to re-use of data for research purposes. The proposals in this area are not wholly clear, and are in some cases contradictory. They include clarifying that a broad consent is permitted when obtaining consent for research and that re-use for research is always compatible with the original purpose, both of which would be welcome but could be achieved by regulatory guidance rather than new legislation. There are also (unclear) proposals to allow further processing for incompatible purposes when this safeguards an important public interest [54]. The Data Protection Act 2018 already allows this for the public interest purposes specified in Schedule 2. Allowing a general public interest override to purpose limitation will significantly weaken protections for individuals, so it would be useful to understand the size of the problem that DCMS thinks it is addressing with this proposal.
It is also striking that the consultation does not make any reference to the laws relating to patient confidentiality beyond data protection law. In the authors’ experience, it is the law in this area which is the biggest constraint on research – both as a matter of principle and because of uncertainty in interpretation. No amount of tidying up of data protection law will achieve significant benefit unless this is addressed.
Suggested reform | Paragraph reference | Impact |
Create an LIA “white-list” in law explaining when an interest is considered legitimate and no balancing test is needed | 60 |
DCMS proposes creating a list of legitimate interests for which no legitimate interest assessment would need to be conducted, as the legislation would recognise the processing purposes as always outweighing the interests of the individuals. The proposed list is relatively limited and uncontroversial and would reduce the burden of documentation obligations.
Suggested reform | Paragraph reference | Impact |
Call for views on how the concept of fairness applies to this field | 80 | No clear proposal yet |
Bias monitoring and correction to be added to LIA white-list | 90 | |
Amend Schedule 1 DPA 2018 to explicitly permit processing of sensitive personal data for bias monitoring | 91 | |
Human review for automated decisions – potential for removing Article 22, or clarifying its application | 100 | |
Supporting data intermediaries | 128 | |
Incorporate Recital 26 into the main text of the UK GDPR to state that anonymisation should be assessed based on the reasonable likelihood that the controller is able to identify the data subject | 121-123 | |
Compulsory transparency reporting for algorithms used by public services processing using public data | 290 |
The consultation document notes that “currently, an AI practitioner needs to consider each use case individually and work out each time whether the data protection regime permits the activities”. Our view is that this statement not only holds true of any processing activity in any industry, but is true of other legal considerations outside of data protection. The application of the law is always based on the relevant facts and consequentially new projects will require new assessments of the law.
The proposal to reform the law to make the use of sensitive personal data for bias detection and correction easier is likely unnecessary. The existing framework under the UK GDPR and Data Protection Act permits this, and the ICO has already provided sector specific guidance in this area.
The proposal to support the development and use of data intermediaries could be very beneficial to organisations sharing data for research and development purposes. Though the consultation document is very light on detail in this area, the proposal is welcome and could allow for innovative frameworks for data sharing within the existing data protection framework.
The proposal has an interesting discussion of algorithmic “fairness” – it postulates that determination of what is fair should be best left to sector specific regulators, rather than the ICO [79].
It also suggests clarifying when data will be regarded as “anonymous”. The suggestions to write recital 26 into the text of UK GDPR seem to add little to current guidance from the ICO on this topic. More interestingly, DCMS suggests that it may stipulate that anonymisation should be assessed based on whether it is likely that the controller can identify the data subject. This would be a more permissive test than that set out in the GDPR – which requires one to consider the likelihood of identification by the controller or by another person (i.e., by anyone). In effect, this would be a return to the provisions of the Data Protection Act 1998. The proposal would help to clarify that if party A releases de-identified data to party B but retains the underlying identifiable data, the fact that party A could still identify individuals in the data would not automatically result in the data being personal in party B’s hands. Currently, if data is made accessible to the public at large (rather than a limited group of recipients), it is typical to require a higher standard of de-identification to achieve anonymisation, as it is harder to assess the motives and the means an unknown actor may go to identify the data. It is not clear how the proposal would protect individuals in this situation.
Suggested reform | Paragraph reference | Impact |
Controllers must have complaints handling process in place | 386 | |
Additional powers for the ICO: commission technical reports, compel witnesses | 394 | |
Extend deadline for issuing penalty notice from 6 months to 12 months after the notice of intent. | 404 | |
Stop the clock mechanism during an ICO investigation, to pause deadlines if parties to not provide required information | 406 | |
ICO to set out timelines for the phases of an investigation to the relevant data controller(s) at the beginning of an investigation | 408 |
The amendments provide the ICO with stronger enforcement powers, and will also change the timelines for enforcement action. The extension of the limitation period for investigations in particular will give the ICO more time to assess whether or not to issue a notice, potentially increasing the number of notices issues. The proposals are not disproportionate and are likely to have a beneficial impact on the regulatory environment in the UK.
The reform also includes substantial amendments to the ICO’s internal governance and relationship with its sponsoring department, DCSM. These changes, if implemented, would have a big impact on the role and running of the ICO but we have not addressed them in detail in this document as they would not directly impact compliance obligations for data controllers and processors. Highlights of the proposed reforms are:
The proposed changes would significantly change the UK’s data protection landscape. As we have discussed above, some of this would be welcome while other proposals are problematic or unclear. We encourage organisations to consider which areas of the proposal may be of relevance to them, and engage with DCMS on those issues.
*This article has been previously published on the IAPP website and shared with its members.