Data Protection Assessment vs. DPIA: What Is the Difference?

Close
Read time
7 mins
Published
Nov 13, 2026
Share

  • A DPIA is the GDPR's required risk assessment for processing that is likely to result in a high risk to the rights and freedoms of individuals.
  • "Data protection assessment" is the term many U.S. state privacy laws use for a comparable but separate requirement. California calls its version a risk assessment.
  • The GDPR asks whether a risk is high. U.S. laws list activities, such as targeted advertising, sale of personal data, and sensitive data processing, that must be assessed.
  • U.S. assessments weigh the benefits of processing against its risks. A DPIA focuses on necessity, proportionality, and risk to individuals.
  • Several state laws allow an assessment prepared for one law to count for another when the scope and effect are reasonably comparable.
  • The Cookiebot cookie scanner can help document which cookies and trackers your website runs, which is a starting point for either assessment.

A DPIA is the GDPR's risk assessment for high-risk processing. Many U.S. state privacy laws require something similar, called a data protection assessment, but the triggers, test, and regulator access differ. This article compares the two, explains when a website or online store may need one, and shows how to build a single process that covers both.

Privacy teams often use "DPIA" and "data protection assessment" as though they meant the same thing. They come from different legal traditions, and the distinction matters if your website serves visitors in both the EU and the United States.

This guide separates the two. It explains what each requirement asks for, how they compare, when a website or online store is likely to need one, and how to run a single process that covers both. It is general information, not legal advice.

What Is a DPIA Under the GDPR?

A Data Protection Impact Assessment (DPIA) is a documented risk assessment that Art. 35 GDPR requires before processing that is likely to result in a high risk to the rights and freedoms of individuals. The controller, meaning the organization that decides why and how personal data is processed, is responsible for it.

At a minimum, a DPIA must include:

  • A description of the processing and its purposes
  • An assessment of whether the processing is necessary and proportionate to those purposes
  • An assessment of the risks to individuals
  • Measures planned to address those risks

The GDPR specifically requires a DPIA for systematic and extensive profiling or automated decision-making that significantly affects individuals, large-scale processing of special category or criminal offense data, and large-scale systematic monitoring of publicly accessible areas. Supervisory authorities also publish national lists of other processing that calls for one.

Where a data protection officer (DPO) has been appointed, the controller must seek the DPO's advice. If a DPIA shows a high risk that cannot be reduced, the controller must consult the supervisory authority before processing begins. 

The GDPR also applies to organizations outside the EU that offer goods or services to people in the EU (extraterritoriality), so a DPIA can be relevant even if your business is based elsewhere.

What Is a Data Protection Assessment Under U.S. State Laws?

There is no comprehensive U.S. federal privacy law, so this requirement comes from individual U.S. state laws. Virginia, Colorado, Connecticut, and Texas, among others, require controllers to conduct and document a "data protection assessment" for certain activities. California's regulations under the CCPA use the term "risk assessment" for a similar obligation.

Virginia's law, for example, requires controllers to assess:

  • Processing personal data for targeted advertising
  • Sale of personal data
  • Profiling that presents a reasonably foreseeable risk of certain harms to consumers
  • Processing sensitive data
  • Any other processing that presents a heightened risk of harm to consumers

Other states vary in the details, including how they define sensitive data, so each applicable law needs to be checked. California's updated regulations, effective January 1, 2026, require a risk assessment before a business sells or shares personal information, processes sensitive personal information, or uses automated decision-making technology for significant decisions, among other activities. 

Businesses must submit an attestation and a summary of their risk assessment information to the California Privacy Protection Agency (CalPrivacy) by April 1, 2028.

Data Protection Assessment vs. DPIA: How Do They Compare?

The two requirements share a goal, which is to make organizations think through the risks of a data practice before it begins. They differ in what triggers them, how the analysis is framed, and who can ask to see the result.

AspectDPIA (GDPR)Data Protection Assessment (U.S. States)
DefinitionA documented risk assessment of processing likely to result in a high risk to individualsA documented assessment of specified processing activities that weighs benefits against risks to consumers
Legal BasisArticle 35 of the GDPR (and the UK GDPR)Individual state laws, such as Virginia's CDPA; California's CCPA regulations call it a risk assessment
Scope Of CoverageProcessing likely to be high risk, including three named cases and national listsListed activities, such as targeted advertising, sale of personal data, and sensitive data processing
FocusNecessity, proportionality, and risk to individuals' rights and freedomsBenefits of the processing weighed against risks to consumers, as reduced by safeguards
Regulator AccessNot filed routinely; the supervisory authority must be consulted if a high risk remainsTypically available to the state attorney general on request; California also requires an attestation and summary filing
ExamplesLarge-scale profiling; large-scale monitoring of publicly accessible areasTargeted advertising; sale of personal data; processing of sensitive data

In short, a DPIA asks whether the processing is likely to be high risk and, if so, how to contain that risk. A data protection assessment starts from the activity, then asks whether the benefits justify the risks.

Data Protection Assessment or DPA? A Note on Terminology

The abbreviation "DPA" causes confusion because it has more than one common meaning in privacy work. This article spells out "data protection assessment" to avoid mixing them up.

Depending on the document or the conversation, DPA can refer to a:

  • Data processing agreement, the contract between a controller and a processor that Art. 28 GDPR requires
  • Data protection authority, the regulator that supervises GDPR compliance in a country
  • Data protection assessment, the U.S. state law requirement discussed here

When a vendor asks you to sign a DPA, it usually means the first of these.

When Does a Website or Online Store Need One?

Using cookies does not trigger either requirement by itself. What matters is what the cookies and other trackers do, how much data they collect, and who receives it.

Under the GDPR

A typical small website with analytics and a few marketing tags is not automatically in DPIA territory. Regulatory guidance treats the following as indicators of high risk, and the more of them are present, the more likely a DPIA becomes:

  • Tracking behavior, location, or movements
  • Combining datasets from different processing operations
  • Using new technologies
  • Processing data about vulnerable people, including children

Under U.S. State Laws

In states with a data protection assessment requirement, advertising technology is the most common trigger. A website that runs targeted advertising or sells personal data is likely to have in-scope processing in states that list those activities. Whether a law applies at all depends on thresholds, such as the number of residents whose data you process or your annual revenue, which vary by state.

How to Build One Process for Both

Most small teams do not need two parallel sets of paperwork. Virginia's law, for instance, allows a single assessment to cover a comparable set of processing operations and accepts assessments prepared for other laws if they have a reasonably comparable scope and effect. Several other state laws include similar provisions.

A practical approach is to write the assessment to the more demanding standard, then check it against each law that applies. These steps suit most websites:

Map the processing

List the cookies, pixels, and other trackers on your site, what each one does, who provides it, and what data it collects.

State the purpose and necessity

Describe why each activity is needed, in specific terms rather than generic phrases such as "improving services," and whether the same goal could be met with less data.

Identify risks and benefits

Note the risks to visitors, such as loss of control over their data, discrimination, or financial harm, and the concrete benefits to them, to your business, and to others.

Record safeguards

Document measures such as access controls, encryption, data minimization, and retention limits, and note any risk that remains.

Get a decision and set a review date

Have someone with authority approve the assessment, consult your DPO if you have one, and schedule a review for when the processing changes.

A scan covers only the first step. The judgments in steps two to five remain with your team, your DPO, or your legal adviser.

What Is Changing in Assessment Requirements?

Both sets of rules are moving, so an assessment is better treated as a living document than a one-time filing.

In California, the CCPA risk assessment rules have applied since January 1, 2026, and the first submissions to the California Privacy Protection Agency are due by April 1, 2028. 

In the EU, the European Commission's Digital Omnibus proposal of November 2025 would task the European Data Protection Board with proposing EU-wide lists of processing that does and does not require a DPIA, along with a common template and methodology, replacing the current national lists. The proposal is still being negotiated between the EU institutions, and the GDPR's existing DPIA rules continue to apply.

Key Things to Remember and Next Steps that Support Compliance

A DPIA and a data protection assessment share a purpose but not a rulebook. Knowing which one applies to your website, and building a single well-documented process to cover both, can save a small team a good deal of duplicated effort.

Start by finding out which laws cover your visitors, then document what your website actually tracks. For the assessment itself, consult a qualified legal professional, privacy expert, or DPO.

Frequently asked questions

No, although they are closely related. A DPIA is the GDPR's risk assessment for processing that is likely to be high risk. A data protection assessment is the term many U.S. state privacy laws use for a requirement tied to listed activities, such as targeted advertising, sale of personal data, and sensitive data processing. California's version is called a risk assessment.

Not automatically. Under the GDPR, a DPIA is needed when processing is likely to result in a high risk, which depends on factors such as scale, profiling, and the type of data. Under U.S. state laws, cookies used for targeted advertising or the sale of personal data are likely to fall within an in-scope activity where the law applies. Check the laws that cover your visitors.

The controller, which the CCPA calls a business, is responsible. A processor or vendor may supply information, and an outside adviser may prepare the document, but responsibility stays with the controller.

Generally not. Under the GDPR, a DPIA is not filed routinely, but the supervisory authority must be consulted before processing begins if a high risk remains after mitigation. Under U.S. state laws such as Virginia's, the attorney general can request relevant assessments during an investigation. California adds a filing requirement: businesses must submit an attestation and a summary of their risk assessment information to the California Privacy Protection Agency, with the first submission due by April 1, 2028.

Often, yes. Virginia's law, and several others, allow an assessment prepared for another law to count if its scope and effect are reasonably comparable. Writing to the more demanding standard and checking it against each applicable law is a common approach. Confirm the details with a qualified legal professional.

Whenever the processing changes in a significant way. Under the GDPR, a DPIA should be revisited before new purposes or data types are introduced. California's regulations require an update within 45 calendar days of a material change and a review at least once every three years.

No. A scanner cannot carry out the risk analysis. The free Cookiebot cookie scanner can help with the first step by listing the cookies and trackers on your website and categorizing them by purpose, provider, and data type.