REC Data Protection Changes

  • 1
    Rejected
Step 1 of 1
Rejected
Summary
A number of additional data protection related changes were identified during the progression of Change Proposal R0046A ‘Governance of Data under the REC (Alternative)’. The intent of this Proposal is to collate all remaining proposed changes, to assess and progress them independently of R0046A, to allow for more thorough industry consultation and with longer lead-times to implementation.

Latest update and next planned activity

Date of latest update
Latest Update
19/03/2024 - Following further analysis and engagement with the REC Change Panel at its meeting on 19 March 2024, the Code Manager has revisited its consideration of this Change Proposal. Despite earlier acceptance of the Change Proposal, the Code Manager, and the Change Panel, believes that the proposal has no reasonable prospect of being approved in its current format, and have determined that the Change Proposal should not progress any further. Consequently, Change Proposal R0068 has been rejected. The Code Manager has offered their assistance to the proposer should they need any support in raising a new Change Proposal to resolve any remaining issues.

Impacts Overview

Priority and rationale
Standard

Solution development

No documents available.

There is currently no Change Plan.

Original submission

Change details

Cordelia Grey - DCC
2 Sep 2022

Change details

REC Main Body Data Protection Changes and development of a REC Data Protection Schedule.
A number of key changes raised by DCC to the data protection provisions in the REC were suggested to be better addressed via a separate REC Change Proposal rather than in R0046A ‘Governance of Data under the REC (Alternative)’. Therefore the intent of this Proposal is to collate all remaining proposed changes and progress them via a change development process that can allow for more thorough industry consultation and with longer lead-times to implementation.
The changes proposed in CP R0046A addressed urgent changes required in order for MPxN level data to be shared between DCC and RECCo from Switching Go Live. DCC identified a number of additional key areas of improvement within the REC relating to data protection that were classified as less urgent but still necessary to support Market Participants and their compliance, particularly in terms of data subjects’ rights, and to ensure clearer accountabilities and responsibilities and co-ordination between Switching entities, for example, in the event of a personal data breach.
Following on from Impact Assessment responses and discussions related to CP R0046A ‘Governance of Data under the REC (Alternative)’, the following requirements should be considered as either changes to REC Main Body Clauses 19 and 20 or within a separate REC Data Protection Schedule: (1) Re-introduce the following text, that was removed under CP R0046A, at the end of Clause 19.6 to assist REC Controllers to meet their transparency obligation under Data Protection Legislation: “and such information shall include details of other REC Controllers and how and where to access the Data Subject information notices relating to the Processing of REC Data by the CRS Provider and RECCo”. (2) REC Code Manager to maintain and publish on the REC Portal a register of REC Controllers to support compliance with Clause 19.6. This obligation already exists under paragraph 10.8 of Schedule 18 (Green Deal Arrangements) to the Code, which requires the Code Manager to maintain and publish on a website an accurate list of Data Controllers who are expected to Process Personal Data in connection with the Green Deal. To the extent they are not identified in the schedules to the Code, REC Controllers who Process Personal Data in connection with the provision and/or receipt of REC Services should be required to self-notify to the Code Manager for inclusion in the register. (3) To avoid risk of non-compliance, clarify within the REC Main Body Clauses 20.4(c) and (j) that a REC Controller would not be required to cease using, or to delete, REC Data as soon as its REC Processor obligations have come to an end if it has a genuine or legitimate obligation to process the same REC Data under the REC as a REC Controller. (4) Amend Clause 20.4(h) to change the time in which a REC Processor must notify that a Personal Data Breach in relation to REC Data has occurred by substituting “without undue delay (and, in any event, within 1 Working Day)” for “as soon as practicable (and, in any event, within 1 Working Day)”. This reflects the obligation under UK GDPR Article 28 and is consistent with Clause 19.9. (5) Supplement transparency obligations documented in the Code as regards the exercising of rights by data subjects, as required by the ICO Code of Practice. (6) Supplement the arrangements for handling a Personal Data Breach concerning REC Data relating to the CRS, in line with ICO Code of Practice and EDPB guidance, and to reduce the risk of a negative outcome owing to multiple contemporaneous switching incident investigations. For example, include obligations on: a. a REC Controller who becomes aware of such a Personal Data Breach (“Notifying REC Controller”) to notify the REC Board and the CRS Provider also if it has determined to notify the ICO and/or data subjects of the Personal Data Breach; b. REC Board and/or the CRS Provider to notify other REC Controllers of any such determination by the Notifying REC Controller; c. the Notifying REC Controller to notify the ICO and/or data subjects also on behalf of the other REC Controllers collectively either (i) if those REC Controllers elect for that to happen by notifying the REC Board/ CRS Provider (‘opt in’); or otherwise (ii) unless those REC Controllers notify the REC Board/ CRS Provider that they object to such notification being made also on their behalf, having had a reasonable opportunity to object (‘opt-out’); d. each REC Controller to provide such information and assistance as the REC Board/ CRS Provider reasonably requires for the purpose of detecting, investigating and mitigating a breach in relation to REC Data relating to any Centralised Registration Service. (7) Requirements relating to the appointment by a REC Controller of a Processor, that is not a REC Processor, to Process Personal Data. (8) Pragmatic provisions in response to the Schrems II decision and guidance on supplemental measures for transfers of Personal Data to countries whose data protection regimes are not deemed adequate. (9) Maintenance by the REC Board on behalf of REC Controllers collectively of a register of restricted data transfers approved under Clause 20.8 of the Code and the applicable international data transfer mechanisms. (10) The option for the Code Manager to specify that each CSS User can nominate a data protection specific Operational Contact under Clause 24.2 of the Code for the purpose of managing data protection issues on behalf of the CSS User, and the maintenance by the Code Manager of a register of such data protection-specific Operational Contacts.
DCC have worked closely with RECCo, Ofgem and the Code Manager in the development of data protectionrelated changes to the REC Main Body, including those that were raised under CP R0046A. It was suggested that the changes listed within this REC Change Proposal be addressed via a separate REC Change Proposal and the majority of changes were suggested as better placed in a separate Data Protection Schedule to the REC.

Impacts

Electricity, Gas, Domestic Prepayment, Domestic Credit, Microbusiness, Small and Medium Enterprise (SME)
Trust and confidence
The additional changes to the Code’s data protection provisions will improve transparency of data processing activities in relation to REC Services and how energy consumer data subjects can exercise their rights.
REC Main Body
Proposal for a new REC Data Protection Schedule to be created and maintained.
No details provided
-
No details provided
-
No details provided
-
No details provided
-
Central Switching Service (CSS), Switching Operator
The changes will affect all REC Controllers (i.e. REC Service Providers and REC Service Users when acting as a Controller in respect of the Processing of Personal Data in connection with the Code (“REC Data”)) and REC Processors (i.e. REC Service Providers and REC Service Users when acting as a Processor in respect of the Processing of REC Data).
Energy Suppliers, Distribution Network Operators, Gas Transporters, DCC, Shippers, Data Collectors
The changes will affect any additional REC Controllers and REC Processors not identified above.
No details provided
-
No
No details provided

Priority & timing

No
-
-
-
No details provided
-

Activity

james.hardy has been allocated as Lead Analyst.