Under the GDPR, a controller that uses a processor must have a contract setting out the subject, duration, nature and purpose of the processing. The processor may act only on the controller's documented instructions, must keep the data secure, and must delete or return it at the end of the service. Several US state privacy laws require similar contracts with service providers.
For a company thinking about licensing data, DPAs are often the decisive documents. A software vendor that hosts customer records is typically a processor for those records. The DPA it signed with each customer says it will process the data only to provide the service. Licensing those records to an AI lab is a new purpose that the instructions do not cover. Doing so could breach the contract and move the vendor into the role of a controller without a lawful basis. A data title search reads the company's DPAs for this reason. The usual outcome is that customer-controlled data comes out of scope unless the customer agrees.
DPAs differ between customers. Large customers often negotiate their own terms, so a review has to cover the negotiated agreements as well as the standard form.
Example
A helpdesk software vendor holds tickets for its business customers. Its DPA limits use to providing the helpdesk. Those customers' tickets are excluded from any dataset the vendor licenses.