GDPR applies to any organisation processing personal data of EU and UK residents, regardless of sector. Energy organisations face a specific configuration of obligations shaped by the personal data they collect, the regulatory environment they operate in, and the systems they use to do it.
This page covers the GDPR obligations specific to Energy, the lawful bases that apply, and the implementation approach that survives supervisory authority scrutiny.
Regulatory context
Supervisory authority: National supervisory authorities + ACER (EU)
Key personal data categories: retail customer records, consumption data, trading counterparty data, employee records including field operations
Special category data present: Typically no — standard Article 6 lawful bases apply
Primary lawful bases: Contract (retail supply, trading), Legal Obligation (regulatory reporting), Legitimate Interests (fraud prevention)
Energy companies undergoing transition to renewable portfolios often acquire or merge with smaller operators. Each M&A event is a change of controller requiring notification to data subjects, an assessment of existing consent coverage under the new entity structure, and integration of the acquired entity's data flows into the ROPA. Data privacy software with a data mapping module significantly reduces the time required for this work.
The hard part
Energy trading platforms process counterparty data in real time across jurisdictions. Where the counterparty is an individual trader rather than a corporate entity, their data is personal data. Determining which jurisdiction's law applies to each trading relationship is a recurring compliance question.
This is the implementation decision that most Energy GDPR programmes get wrong. It is also the issue most likely to appear in a supervisory authority audit or a data subject complaint.
Required controls
- Counterparty data classification policy distinguishing corporate from individual counterparties
- Retail customer consent model for variable tariff communications and third-party sharing
- H&S records for field operations under legal obligation lawful basis
- DSAR workflow spanning CRM, billing, trading, and HR systems
- Cross-border transfer mechanisms for trading counterparty data flowing to non-EU locations
GDPR gap assessment framework for Energy
A gap assessment for a Energy organisation covers five areas:
1. Data inventory and ROPA
Map every system that holds personal data specific to Energy operations: retail customer records, consumption data, trading counterparty data, employee records including field operations. Document the purpose, lawful basis, retention period, and third-party recipients for each. The ROPA must be current — a snapshot taken at implementation and not updated is not compliant.
2. Lawful basis audit
For each processing activity, confirm the lawful basis is documented and appropriate. Energy organisations frequently find that processing that was assumed to be covered by legitimate interests has not had a Legitimate Interests Assessment completed. Where special category data is present, Article 9 requires a separate documented basis.
3. Consent management
Where consent is the lawful basis, verify that consent records meet GDPR Article 7 requirements: freely given, specific, informed, unambiguous, and withdrawable. Legacy consent from before the current privacy notice version should be assessed for adequacy.
4. DSAR readiness
Test the DSAR workflow with a synthetic request. The test should cover: intake, identity verification, data discovery across all systems identified in the data inventory, response assembly, and delivery within the 30-day deadline. Most Energy DSAR gaps are discovered at the data discovery stage — systems that hold personal data but are not connected to the DSAR workflow.
5. Breach preparedness
Verify the incident log, the severity classification matrix, and the 72-hour notification workflow. The Energy-specific question is: which data categories, if breached, trigger notification to individuals (not just to the supervisory authority)? Notification to individuals is required where the breach is likely to result in high risk to their rights and freedoms.
Implementation priority order
For Energy organisations starting a GDPR programme:
- Data inventory — identify all systems holding personal data before configuring any controls
- Lawful basis documentation — stop processing for which there is no documented basis
- DSAR workflow — rights requests can arrive at any time; the workflow must be operational before launch
- Consent remediation — address legacy consent before running any marketing to the affected population
- ROPA — live, connected to source systems, reviewed quarterly
- Breach procedure — tested annually; DPO and legal team both trained on the 72-hour obligation