What is Privacy by Design?
A principle based on putting data protection and privacy at the foundations of any new business process or system created rather than layering them on as a later consideration. Although not mandated by data regulations, it is strongly advised in order to help ensure compliance throughout your organisation.
When might Privacy by Design be relevant?
The principle will be relevant when any new project is being planned. Common examples of projects that will require particular attention to the privacy and protection of data include:
- Building/choosing a new IT system that has access to any personal data (i.e. CRM, marketing automation etc.)
- Migration of any personal data to a different system.
- Creating any new procedures that affects personal data (i.e. employee access rights, password policies)
Why use a Privacy by Design approach?
Embedding data protection principles from the offset of any new project has plenty of benefits when it comes to risk and consumer trust. By considering the implications from the beginning you can:
- Easier create a positive data privacy friendly culture in your organisation. If your projects have it at their core, your employees will more likely consider it a core issue.
- Reduce the risk of any data issues arising such as a large scale data breach. Not only does this severely damage trust with the public, but will likely result in large punishments under GDPR.
- Identify any potential issues with your strategy earlier on in the process, likely reducing the time and effort it will cost to rectify it.
How can you encourage high level buy-in for your data quality?
We look at how you can encourage a data quality centric culture in your organisation by understanding the issues with your current business case – and advice on how to make it more powerful.