Shopify Stores Serving EU Customers: GDPR Roles and Cookie Consent
Shopify merchants must assess data roles and device-access consent by activity, rather than assuming the platform absorbs every privacy duty.
Using Shopify does not give every processing activity in a store the same legal role or lawful basis. A merchant can determine why customer information is collected, Shopify can process some of it on the merchant's behalf, and other features or providers can involve different roles. Cookie and tracker requirements add another legal question that cannot be answered solely by pointing to a data processing agreement.
This article examines EU-facing stores through the GDPR, the ePrivacy Directive and Shopify's current published terms and Data Processing Addendum reviewed for the article. National implementation remains relevant to device-access rules. It does not assume that every Shopify merchant is established in the EU or that every processing activity has an identical territorial connection to EU law.
GDPR scope depends on the activity and territorial connection
The GDPR's territorial provisions need assessment before its obligations are assigned. Establishment in the Union can create one connection. Offering goods or services to people in the Union or monitoring relevant behaviour can create another under the regulation's conditions. A website's global accessibility alone should not be used as a complete territorial analysis.
For a store actively serving EU customers, the relevant processing can include orders, delivery details, customer support and marketing. These activities can have different purposes and legal bases. A single privacy statement saying the store uses data to improve services may not explain the actual processing accurately enough. The facts of the store's business and technology matter.
The territorial assessment also does not settle every other legal question. It establishes whether the GDPR framework is relevant, not whether every collection is lawful or every transfer arrangement is sufficient. The merchant still needs to identify the processing purposes, parties and applicable duties. Those steps should follow the actual store rather than a generic description of ecommerce.
Controller status follows decisions about purposes and means
A GDPR controller determines the purposes and means of processing personal data, alone or jointly. A merchant choosing to collect delivery information to fulfil its orders or to use customer details for its own marketing can therefore be a controller for those operations. Outsourcing storage or technical execution does not automatically remove that role.
The analysis is activity-specific. The same provider can perform different roles for different purposes. A contractual label is useful evidence, but it should be consistent with the actual decisions and processing relationship. Calling every platform a processor or every app an independent controller without examining its function can produce the wrong allocation of responsibilities.
Controller responsibilities can include transparency, a lawful basis, data-subject rights, retention and appropriate security. The exact obligations depend on the circumstances. Consent is one GDPR lawful basis rather than a universal requirement for every order-related operation. Equally, a merchant should not assume that an operationally convenient purpose automatically qualifies for whichever basis appears easiest to document.
Shopify's DPA distinguishes more than one role
Shopify's Data Processing Addendum addresses processing of certain customer personal data on behalf of merchants. It also sets out circumstances in which Shopify acts as controller or in other specified capacities. The document should therefore be read by activity and feature, not reduced to the claim that Shopify is always the processor for everything a store does.
The addendum reviewed for this article states its current terms and relevant role allocations. A merchant should assess the applicable version and services actually used. A feature added after a previous review can change the processing picture. An earlier description of the store's setup does not automatically describe every later integration or data flow.
Shopify's general terms also preserve merchant responsibilities for operating the business and complying with applicable requirements. A platform contract and privacy settings can support the merchant's work without becoming a certification that the store has fulfilled every GDPR duty. The allocation should be reflected in accurate notices and workable arrangements, rather than a blanket statement that the platform handles privacy.
Processors need appropriate arrangements
A GDPR processor processes personal data on a controller's behalf. Article 28 requires a binding contract or other qualifying legal act with specified content. The relationship involves more than attaching the title DPA to a document: instructions, confidentiality, security, assistance, subprocessors and end-of-service handling are among the relevant subjects.
The merchant's app environment can create additional relationships beyond the main platform agreement. An analytics provider, support tool or marketing integration needs assessment according to what it actually does and whose purposes it serves. Some arrangements may involve a processor, while others can involve an independent controller or another allocation. The answer should not be inferred solely from the app category.
Using a processor does not remove the controller's accountability. The arrangements need to support real requests and events, such as deletion instructions, access requests or security incidents. A signed contract is relevant evidence, but its practical implementation matters. A merchant should understand which provider can perform which task and how the obligations apply to the data involved.
Cookie rules concern access to the user's device
Cookie consent arises from rules on storing information on, or accessing information from, a user's terminal equipment. Article 5(3) of the ePrivacy Directive establishes the framework and specified exceptions. Its reach is not limited to technologies called cookies or to information that independently qualifies as personal data.
The directive provides exceptions for transmission and for activity strictly necessary to provide a service explicitly requested by the user. Strict necessity is not the same as commercial usefulness. A store should not assume that advertising or optional measurement becomes exempt merely because it contributes to the business. The purpose and actual behaviour of the technology need assessment under the relevant national rules.
This layer is distinct from the GDPR basis for later processing. A claim of legitimate interests under the GDPR does not by itself remove a consent requirement for non-exempt device access. Conversely, obtaining device-access consent does not automatically establish that every subsequent use, retention period or disclosure of personal data is lawful and transparent.
A banner must correspond to actual technology behaviour
A visible consent interface is only one part of the assessment. Where prior consent is required, the relevant activity must respect the user's choice. A banner that records refusal while an advertising integration continues accessing the device does not implement that refusal effectively. The actual store behaviour matters more than the appearance of a preference panel.
CNIL's published background guidance explains the importance of obtaining consent before relevant operations and providing a usable withdrawal route. That source is background from 2019, rather than evidence of a new 2026 rule. Current national guidance should be checked for the exact implementation questions affecting the store; historical transition periods should not be presented as current deadlines.
Withdrawal also needs practical effect for future consent-dependent activity. A record that a user once clicked accept does not answer what should happen after that user changes their choice. Integrations, theme code and third-party services need to honour the relevant state. The legal analysis and technical behaviour should describe the same store, rather than two independent representations.
Transparency should describe the store actually operated
A privacy notice should reflect the purposes, parties and processing relevant to the merchant's activities. A generic platform template can provide a starting structure but may omit particular apps or business uses. It can also become inaccurate when copied from a store with different marketing tools or customer relationships.
Retention and rights handling need the same factual grounding. Keeping every record indefinitely because it might be useful is not a complete retention analysis. Deleting information from one app may not remove copies held elsewhere. The relevant duties should be connected to the actual systems, legal requirements and processing purposes rather than assumed from one administrative screen.
International processing requires its own assessment under the GDPR's transfer provisions where applicable. Processor status alone does not establish that every transfer arrangement is valid. This article does not claim that all Shopify processing follows one location or one transfer route. The applicable terms and actual service relationships need to be examined for the processing concerned.
Product and consumer obligations remain outside the privacy allocation
A clear data-role analysis does not settle every other duty of an EU-facing store. Product safety, consumer information and other requirements can remain relevant independently. Shopify's provision of commerce infrastructure does not turn a merchant's product claims or customer terms into automatically verified statements.
This separation helps keep the privacy assessment focused. An appropriate DPA does not prove that a product is safe, and a compliant product offer does not prove that advertising trackers respect consent. Each framework follows its own legal purpose, even where the same store and customer transaction create several obligations.
For a Shopify merchant, the useful privacy record connects purposes and decisions with the relevant controller or processor, then connects device-access technologies with their actual consent or exemption assessment. Platform documents support that analysis. They do not replace it. A store's compliance position depends on the activities it actually performs and the choices its technology actually respects.
Source review: 16 November 2026. For a product-specific or consequential compliance decision, consult an appropriately qualified legal or regulatory adviser.
Sources
- General Data Protection Regulation
- ePrivacy Directive, Article 5(3)
- Shopify Data Processing Addendum
- Shopify Terms of Service
- CNIL: Background on cookie-consent principles (2019)
About the Author
CBEC Zone Editorial
Editorial desk covering cross-border e-commerce policy, platform rules and industry knowledge for global sellers.