Updated regularly · CBECzone Editorial
CBECzoneCROSS-BORDER INTELLIGENCE
Tuesday, November 17, 2026
Search the site →
Compliance

GDPR Controller

A GDPR controller determines the purposes and means of personal-data processing, alone or jointly with others.

Aliases: Data controller, GDPR data controller

Article 4 of the General Data Protection Regulation defines a controller by its decisions about the purposes and means of processing personal data. The role is functional. A business does not avoid being a controller merely because a hosting company stores the records or an application performs the processing. Conversely, possessing technical infrastructure does not make a provider controller of every operation it supports.

Purposes, means and separate activities

An online merchant may decide to collect delivery details to fulfil customer orders or use customer information for its own marketing. Those decisions can place it in the controller role for the relevant processing. Different operations can involve different role allocations. Joint controllership and independent controllers require their own assessment rather than being assumed whenever two companies exchange data.

A GDPR processor processes personal data on a controller's behalf. Article 28 governs relevant contractual and organisational requirements. Appointing a processor does not erase the controller's responsibilities, including choosing an appropriate service and ensuring the required arrangements exist. A provider can separately act as controller for a different purpose it determines itself.

Responsibilities in practice

Controller duties can include identifying a lawful basis, providing transparent information, respecting data-subject rights, setting appropriate retention and implementing suitable security. Which duties apply depends on the processing and circumstances. Consent is one possible lawful basis under the GDPR, not a universal requirement for every processing operation.

Cookie consent also involves rules on access to or storage of information on terminal equipment. Those rules should not be collapsed into the controller definition or assumed to disappear because another GDPR lawful basis may support subsequent processing.

Ecommerce platforms

For a Shopify merchant, the current DPA helps identify when Shopify processes customer data on behalf of the merchant and when other roles apply. A generic statement that Shopify handles privacy is too broad to establish the merchant's responsibilities. The assessment should follow actual purposes, settings, apps and disclosures. Legal labels in a contract provide useful evidence but do not replace the facts of who determines the processing.

Sources

FAQ

Is the controller always the company hosting the data?
No. The role depends on determining purposes and means.
Can a controller use external processors?
Yes. Outsourcing processing does not remove the controller's responsibilities.
Is consent always the required GDPR lawful basis?
No. The GDPR provides several lawful bases, depending on the circumstances.
Can one provider have different roles for different activities?
Yes. Roles must be assessed for each relevant processing activity.
Does a platform DPA make every merchant a processor?
No. A merchant can remain controller for purposes it determines.
Related Topics ShopifyComplianceEurope