ICO Smart Product Privacy Guidance vs. Mandatory Settlement Concerns
Regulatory Framework Evolution
The ICO published crucial new guidance in June 2025 specifically targeting smart product manufacturers, marking the first comprehensive IoT privacy framework in the UK. This development occurs alongside significant tensions between the ICO and Ofgem over smart meter data access policies.
[cite author="ICO" source="ICO Press Release, June 2025"]For the first time, the ICO has published draft guidance on Internet of Things (IoT) products and services, which will provide regulatory certainty to the industry[/cite]
The guidance represents a watershed moment for enterprise IoT privacy compliance. Smart products collect vast amounts of personal information, including sensitive data streams that require enhanced protection under UK GDPR and the new Data (Use and Access) Act 2025.
[cite author="ICO" source="ICO Guidance Document, June 2025"]Smart products often collect large amounts of personal information from users β including sensitive information β so manufacturers and developers must ensure their products are designed with data protection in mind[/cite]
ICO vs. Ofgem: Regulatory Conflict Over Data Access
A significant regulatory conflict has emerged between the ICO and Ofgem regarding mandatory half-hourly smart meter data collection. The ICO's position directly challenges Ofgem's settlement reform proposals:
[cite author="ICO" source="Response to Ofgem Consultation, 2025"]Mandating half-hourly data be used for settlement directly contradicts that framework. Changing the framework to allow for mandatory half-hourly settlement should not be taken lightly[/cite]
This regulatory tension creates substantial compliance uncertainty for enterprises managing smart meter data. The ICO argues that Ofgem's proposals violate the established Data Access and Privacy Framework (DAPF) that governs smart meter data usage.
Current Privacy Framework Structure
Two parallel governance frameworks currently govern smart meter data:
[cite author="Open Energy Analysis" source="Data Protection Report, 2025"]The two main governance frameworks consist of the General Data Protection Regulation (GDPR) β implemented through the UK Data Protection Act (DPA) β and the Data Access and Privacy Framework (DAPF)[/cite]
The DAPF provides additional protection beyond GDPR, specifically designed to address smart meter rollout concerns:
[cite author="Government Guidance" source="Smart Meter Rights Document, 2025"]The DAPF is an additional framework governing access to smart meter data, designed to enhance public trust in the smart meter roll-out[/cite]
Enterprise Compliance Requirements
Current enterprise compliance requirements create complex data controller responsibilities:
[cite author="Regulatory Analysis" source="GDPR Compliance Report, 2025"]Suppliers are currently 'data controllers' from a GDPR perspective, while DNOs with Ofgem-approved privacy plans can access aggregated/anonymised half-hourly smart meter data[/cite]
The Data (Use and Access) Act 2025 introduces additional complexity without replacing existing frameworks:
[cite author="DUAA Analysis" source="Kennedy's Legal Analysis, 2025"]The DUAA will not replace the UK General Data Protection Regulation ('UK GDPR'), Data Protection Act 2018 or the Privacy and Electronic Communications (EC Directive) Regulations 2003, but it will make some changes to them[/cite]
Implementation Timeline and Enterprise Impact
Key regulatory deadlines approaching in 2025-2026 require immediate enterprise attention:
[cite author="ICO" source="Regulatory Update, August 2025"]On August 21, 2025, the UK ICO initiated public consultations to refine certain ICO guidance following amendments to UK data protection law passed under the DUAA[/cite]
These amendments include new compliance requirements for enterprise data controllers:
[cite author="DUAA Implementation Guide" source="August 2025"]These amendments include the introduction of a new lawful basis referred to as 'recognized legitimate interest,' and a requirement for organizations to establish a data protection complaints process[/cite]