A DPIA is a risk assessment that is carried out for any activity that involves processing user data and are a key part of privacy best practice
Data Protection Impact Assessments (DPIAs) are a key part of privacy best practice. They also pose a unique challenge.
At the most basic level, a DPIA is a risk assessment that is carried out for any activity that involves processing user data.
Going to launch a new marketing campaign that involves sharing first-party data with a partner? Going to migrate your email database to a new platform? Going to start a Consumer Loyalty Program? All of these activities should include a DPIA.
In Europe, DPIAs are legally required in certain cases.
Where a type of processing in particular using new technologies, and taking into account the nature, scope, context and purposes of the processing, is likely to result in a high risk to the rights and freedoms of natural persons, the controller shall, prior to the processing, carry out an assessment of the impact of the envisaged processing operations on the protection of personal data. – GDPR Article 35
DPIAs involve a variety of business departments working together in a way that is often unfamiliar. For data-reliant businesses, the volume of DPIAs that GDPR calls for and the unusual depth of coordination needed makes them very hard to do well. We wrote about it here.
Given this difficulty, and given that DPIAs are not “consumer-facing” in the same way as Data Subject Requests, many businesses have opted to take a “managed-risk” approach. They may conduct DPIAs only for the largest or riskiest operations and skip them for day-to-day activities that they deem lower risk. However, in the event that there are complaints about privacy practices, a lack of DPIA documentation will land them in hot water with regulators.
At Ethyca, we believe that software engineers are becoming major privacy stakeholders, but do they feel the same way? To answer this question, we went out and asked 337 software engineers what they think about the state of contemporary privacy… and how they would improve it.
The UK’s new Data Reform Bill is set to ease data privacy compliance burdens on businesses to enable convenience and spark innovation in the country. We explain why convenience should not be the end result of a country’s privacy legislation.
Our team at Ethyca attended the PEPR 2022 Conference in Santa Monica live and virtually between June 23rd and 24th. We compiled three main takeaways after listening to so many great presentations about the current state of privacy engineering, and how the field will change in the future.
For privacy engineers to build privacy directly into the codebase, they need agreed-upon definitions for translating policy into code. Ethyca CEO Cillian unveils an open source system to standardize definitions for personal data living in the tech stack.
Masking data is an essential part of modern privacy engineering. We highlight a handful of masking strategies made possible with the Fides open-source platform, and we explain the difference between key terms: pseudonymization and anonymization.
The American Data Privacy and Protection Act is gaining attention as one of the most promising federal privacy bills in recent history. We highlight some of the key provisions with an emphasis on their relationship to privacy engineering.
Our team of data privacy devotees would love to show you how Ethyca helps engineers deploy CCPA, GDPR, and LGPD privacy compliance deep into business systems. Let’s chat!Book a Demo