GDPR Processor
A GDPR processor processes personal data on a controller’s behalf under applicable statutory and contractual requirements.
Aliases: Data processor, GDPR data processor
Article 4 of the General Data Protection Regulation defines a processor as a person or organisation processing personal data on behalf of a controller. The defining relationship is acting on another party's behalf for the relevant processing. It does not follow automatically from being a software vendor, contractor or data recipient.
Relationship to the controller
A GDPR controller determines the purposes and means of processing. A processor operates within the relevant instructions and arrangements, subject to the regulation. Article 28 requires a binding contract or other qualifying legal act setting out specified elements of the processing relationship. Calling a document a DPA is not sufficient if the required substance is absent.
Processor arrangements address matters such as the subject matter and duration of processing, its nature and purpose, categories of data and data subjects, and the controller's rights and obligations. The regulation also addresses confidentiality, security, assistance, subprocessors and the treatment of data after services end. These are linked duties rather than a general promise that a provider is compliant.
Multiple roles and subprocessors
A service provider can be a processor for one activity and a controller for another. Where it determines purposes and means beyond the processor role, the legal assessment changes. A merchant should therefore avoid assigning one label to all activities merely because they involve the same company.
Shopify's current Data Processing Addendum distinguishes processing on merchants' behalf from circumstances involving other roles. App providers may also introduce separate relationships. The actual contracts and processing purposes need assessment; a store's main platform agreement does not necessarily describe every external integration.
Practical limits
Using a processor does not remove a controller's accountability. Nor does processor status remove the provider's own statutory obligations. Security incidents, rights requests, deletion instructions and subprocessor changes require workable arrangements, not just a signed document.
Cookie consent addresses another part of the store's data environment. A processor agreement does not automatically authorise non-exempt device access or establish an appropriate lawful basis for all later processing. The most useful role analysis follows the actual activity, decisions and instructions, then connects the relevant duties to the party performing them.