Data processor: the details
The distinction matters because it splits the obligations. The controller decides why and how the data is used and answers to the people affected. The processor may only do with it what the controller has instructed. Article 28 of the GDPR requires that relationship to be set out in a contract detailing the subject matter, the duration, the type of data, the security measures and what happens to the data at the end.
The processor can’t subcontract without authorization, must help the controller respond to people’s rights and has to notify it without undue delay if it suffers a breach. When you buy cloud software or AI services, your company is normally the controller and the vendor is the processor: before sending it personal data you need that contract and you need to know where the data is processed.