By Malia Rogers and David Stauss

Key point: Recent changes in California, Delaware, and New Jersey mean it is time for many companies to revisit their data processing agreements to add cybersecurity audit and risk assessment cooperation terms, third-party due diligence provisions, and data broker registration safeguards.

It has been several years since most companies needed to substantially update their U.S. data processing agreements. But recent developments in California, Delaware, and New Jersey suggest that the time has come for many companies to take a fresh look at those documents—both to add new terms and to reconsider existing ones.

First, recent amendments to the California Consumer Privacy Act (CCPA) regulations should prompt companies to consider whether their agreements need new terms addressing cybersecurity audit and risk assessment cooperation. Second, effective January 1, 2027, Delaware will impose new obligations on controllers that disclose personal data to “third parties,” including, most notably, a first-of-its-kind requirement to conduct affirmative due diligence on those third parties. Finally, companies should consider adding provisions addressing New Jersey’s new data broker registration law—in particular, to reduce the risk of being swept in as a “data collector.”

Below, we discuss each of these developments and what companies should consider doing about them. We have also published a new chart comparing state data processing agreement requirements.

California: Changes to Service Provider and Contractor Provisions

Starting April 1, 2028, businesses subject to the CCPA’s cybersecurity audits or risk assessment requirements will need to file certifications with the California Privacy Protection Agency (CalPrivacy) attesting, under penalty of perjury, that those have been completed. The cybersecurity audits requirement is staggered by revenue with businesses with more than $100 million in annual gross revenue required to certify by April 1, 2028; businesses with between $50 million and $100 million in annual gross revenue required to certify by April 1, 2029; and all other covered businesses required to certify by April 1, 2030.

The risk assessment requirement is implemented in two phases. As of January 1, 2026, businesses are required to complete risk assessments prior to initiating new processing activities that present a significant risk to consumers’ privacy (as defined in the regulations). For ongoing processing activities that predate January 1, 2026, businesses need to complete risk assessments no later than December 31, 2027.

To support this framework, CalPrivacy revised section 7051(a)(5) to provide that a service provider or contractor contract “may require the service provider or contractor . . . to assist the business in completing the business’s cybersecurity audit pursuant to Article 9, [and] to assist the business in conducting the business’s risk assessment pursuant to Article 10.”

Although the regulation’s use of the word “may” means that specific contractual assistance provisions are not mandatory, CalPrivacy also revised the regulations to create corresponding affirmative obligations on service providers and contractors to “cooperate” with businesses’ compliance efforts—regardless of what the contract says. Specifically, section 7050(h)(1) requires service providers and contractors to make available to the business’s auditor “all relevant information that the auditor requests to complete the business’s cybersecurity audit and that is in the service provider’s or contractor’s possession, custody, or control.” Similarly, section 7050(h)(2) requires service providers and contractors to make available “to the business all facts necessary to conduct the risk assessment that are in the service provider’s or contractor’s possession, custody, or control.”

CalPrivacy’s Initial Statement of Reasons explained that the changes to sections 7050 and 7051 were interrelated, and that by “incorporating the requirements of service providers and contractors directly into contracts, the business can further ensure that the service provider and contractor are fully aware of their responsibilities when cooperating with the business to comply with the CCPA’s requirements.”

That framing is worth sitting with: section 7050(h) already imposes a cooperation duty as a matter of regulation, a service provider or contractor owes that duty whether or not the parties’ contract says anything about it. Therefore, simply adding or supplementing existing data processing agreement language to require service providers and contractors to comply with these new CCPA obligations may be the preferred approach. However, there may be a real value in adding contract language to define the boundaries and set practical expectations for cooperation before an audit or assessment is underway, when both sides still have leverage to negotiate reasonable terms. Nor should the cooperation requirement and obligation to provide information necessarily be understood to create an unrestricted right to inspect systems or conduct an on-site audit. Among other things, businesses and service providers/contractors should consider addressing: the format and turnaround time for producing information; whether a business will accept a service provider’s existing cybersecurity audit, potentially supplemented by a CCPA-specific gap review, rather than requiring a separate audit; whether a business will accept a service provider’s own risk assessment of its processing activities instead of requiring a bespoke questionnaire be completed by the service provider; confidentiality obligations binding the business and any third-party auditor who receives the service provider’s information; and who bears the cost of extraordinary requests, so long as these arrangements do not narrow the service provider’s or contractor’s obligation to make available all information (and, for risk assessments, all facts) required by the regulation. Addressing these points in advance, may be considerably easier than doing so for the first time after an audit or assessment is already underway.

Delaware: New Contracting and Due-Diligence Obligations for Third-Party Transfers

Effective January 1, 2027, Delaware will become only the second state – after California – to require controllers to enter into contracts when disclosing personal data to “third parties” (as opposed to processors). Specifically, recent amendments to the state’s consumer data privacy law require controllers to enter “into binding contractual agreements with third parties to whom personal data is disclosed, including in a sale of personal data or for targeted advertising.”

Similar to the CCPA’s requirements, the contract must (1) specify that the personal data is sold or disclosed by the controller only for limited and specified purposes, including whether the purpose includes use for decisions that produce legal or similarly significant effects; (2) obligate the third party to comply with Delaware’s consumer data privacy law and obligate the third party to provide the same level of privacy protection as is required by the law; (3) grant the controller rights to take reasonable and appropriate steps to ensure that the third party uses the personal data transferred by the controller in a manner consistent with the controller’s obligations under the law; (4) require the third party to notify the controller if it makes a determination that it can no longer meet its obligations under the law; and (5) grant the controller the right, upon notice, to take reasonable and appropriate steps to stop and remediate unauthorized use of personal data.

One detail is easy to miss: Delaware’s definition of “third party” expressly excludes processors. That means this new contracting obligation targets a category of recipients – ad-tech partners, co-marketing partners, data brokers, and similar counterparties – that many companies may have never formally papered with a signed agreement at all – or limited to California personal information – because those relationships historically fell outside standard processor DPAs. Companies should not assume their existing DPA template, built around processor relationships, is the right vehicle for this obligation; a separate third-party disclosure agreement, or expanded CCPA third-party transfer template, may be needed. Further, given that lawmakers often incorporate new requirements from other states into their state laws, companies may want to make their third-party transfer templates flexible to automatically incorporate other states adopting similar requirements.

In addition, Delaware goes further than California by requiring controllers, or their designated assessor, to conduct reasonable due diligence of the third party “to assess the third party’s policies and technical and organizational measures undertaken to support compliance with” the law’s obligations. The law provides that reasonable due diligence “involves, at a minimum, assessing the third party through the use of questionnaires and review of relevant documents of the third party. Additional reasonable measures must be undertaken in a manner that is commensurate with the sensitivity of the data disclosed by the controller to the processor or third party.”

This is a first-of-its-kind requirement, and it will force data brokers – but also many other companies – to build a vetting process for the recipients of their data disclosures, not just a contract clause. Because the statute ties the depth of diligence to data sensitivity, a defensible approach is likely a tiered one: a short questionnaire for low-risk, non-sensitive disclosures, and deeper document review – security certifications, audit reports, sub-processor lists – for recipients handling sensitive data.

New Jersey: Avoiding “Data Collector” Status

As we discussed in our prior article, New Jersey’s data broker registration law will require not only data brokers to register and pay potentially large fees, but also “data collectors.” The law defines “data collector” as “a business, or units of a business, separately or together, that knowingly: (1) collect the personal data of a consumer with whom the data collector has a direct relationship; and (2) sell or license such personal data to a data broker.”

That raises three compliance hurdles. First, companies should review their existing contracts to identify any counterparties that are registered as data brokers in other states. Although data broker laws differ in scope, this is a good indicator of whether a counterparty will qualify as a data broker under New Jersey’s law, thereby potentially making the company a data collector if it sells or licenses personal data to that entity.

Second, companies should be vetting new contract counterparties to confirm they are not, and do not intend to become, registered New Jersey data brokers.

Third, for counterparties that are not currently data brokers, companies should, at a minimum, consider adding a notice-of-registration obligation to their data processing agreements, requiring the counterparty to notify them before registering as a data broker in New Jersey. The notice provision is useful, but it should not be mistaken for a shield. Whether a company is a “data collector” under New Jersey’s law turns on what its counterparty actually does – whether the counterparty meets the statutory definition of a data broker (in particular, if they register as a data broker) – not on what the contract says. A notice obligation gives a company an early warning and a basis to renegotiate or exit the relationship, but it does not retroactively change the company’s status if a counterparty registers without giving notice.

Therefore, companies relying on this kind of provision should pair it with periodic monitoring of New Jersey’s data broker registry once it opens. Companies also should consider adding a covenant limiting the receiving party’s use of personal data to the agreed processing or transaction; requiring the receiving party to notify the company before they make any change in their business activities that could cause the receiving party to qualify as a data broker; periodic recertification; a right to suspend transfers or terminate; and responsibility for resulting registration fees, penalties, or remediation where the representation was inaccurate.

Putting It All Together

Taken together, these three developments share a common thread: state legislators and regulators are pushing DPA obligations beyond the traditional controller-processor relationship. Companies now need to think about their data recipients in at least three buckets – processors, third parties who receive data outside a processor relationship, and counterparties who could be, or could become, data brokers – because each bucket now carries its own contracting and diligence obligations.