GDPR applies to any organisation processing personal data of EU and UK residents, regardless of sector. Utilities 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 Utilities, the lawful bases that apply, and the implementation approach that survives supervisory authority scrutiny.
Regulatory context
Supervisory authority: National supervisory authorities + energy regulators
Key personal data categories: smart meter consumption data, billing records, customer contact data, field service records, employee data
Special category data present: Typically no — standard Article 6 lawful bases apply
Primary lawful bases: Contract (supply agreement), Legal Obligation (regulatory reporting), Legitimate Interests (fraud prevention, grid management)
Smart meter data revealing detailed consumption patterns at short intervals (half-hourly or less) provides sufficient information to infer occupancy, lifestyle, and appliance usage. Some data protection authorities treat high-frequency interval data as sensitive by nature even though it is not formally special category data under Article 9. A privacy impact assessment is advisable before enabling granular analytics on interval data.
The hard part
Smart meter data is collected continuously and at high frequency. Retaining granular interval data beyond the period needed for billing and grid management is difficult to justify under data minimisation. Defining the minimum necessary retention period for interval data — against which DSARs and erasure requests must be assessed — is the core governance challenge.
This is the implementation decision that most Utilities 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
- Retention policy for smart meter interval data by purpose (billing vs. grid management vs. analytics)
- Separate consent for secondary analytics uses of consumption data
- DSAR workflow spanning billing, field service, and grid management systems
- ePrivacy compliance for real-time data services and in-home displays
- Processor agreements with smart meter hardware vendors and data analytics providers
GDPR gap assessment framework for Utilities
A gap assessment for a Utilities organisation covers five areas:
1. Data inventory and ROPA
Map every system that holds personal data specific to Utilities operations: smart meter consumption data, billing records, customer contact data, field service records, employee data. 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. Utilities 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 Utilities 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 Utilities-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 Utilities 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