Data protection by design & default

Organisations often overlook data protection by design and default (DPbDD) when they are considering their UK GDPR compliance obligations. This is understandable, as DPbDD is an intangible, all-pervading concept that can be difficult to translate into specific actions, particularly compared to other discrete requirements of the UK General Data Protection Regulation (UK GDPR). However, there is a dedicated section in the UK GDPR about DPbDD (Article 25) and extensive guidance published by the Information Commissioner’s Office (ICO).

In essence, DPbDD involves considering data protection and privacy issues upfront in everything you do. This means you have to integrate data protection into your processing activities and business practices, from the design stage right through the lifecycle.

UK GDPR requirements

DPbDD is a general concept of the UK GDPR regime, but also a specific requirement under Article 25 of Assimilated Regulation (EU) 2016/679 (UK GDPR):

  1. Article 25(1) contains the data protection by design obligation

  2. Article 25(2) covers data protection by default

This is supplemented by Recital 78, although much of this repeats the substantive content in Article 25.

The UK GDPR can be difficult

To view the latest version of this document and thousands of others like it, sign-in with LexisNexis or register for a free trial.

Powered by Lexis+®
Latest Practice Compliance News
View Practice Compliance by content type :

Popular documents