Joint Controllers Without Data Access: What the IAB Europe Ruling Means for Shared Analytics Protocols
A vendor can help determine how personal data is processed without ever seeing the records. The IAB Europe judgment shows why contracts must follow real decisions, not labels.
An organization does not need to receive personal data to become a joint controller of how that data is processed. For developers building shared analytics protocols, SDKs, or event pipelines, the CJEU’s IAB Europe judgment is a reminder that privacy roles follow influence over processing—not just database access or contract labels.
The protocol can shape processing
The GDPR defines a controller as the party that determines the purposes and means of processing, alone or with others. A processor handles personal data on a controller’s behalf. These are functional roles: what each party actually decides matters more than the name assigned in a contract.
In IAB Europe v Gegevensbeschermingsautoriteit (C-604/22), the Court considered the Transparency and Consent String, a standardized record of users’ choices used within the advertising ecosystem. The Court held that a string can be personal data when it can be associated with an identifiable user, and that an organization such as IAB Europe may be a joint controller where it influences the purposes and means of processing, even if it cannot itself access the data held by participants.
That is not a rule that every standards body, SDK publisher, or analytics vendor is automatically a controller. The Court left the factual assessment to the referring court. The key engineering question is whether a party’s decisions shape a particular processing operation: for example, what information a shared protocol captures, how it is encoded, or how participating systems use it.
Joint responsibility has boundaries
The same judgment also draws a limit. Joint controllership does not automatically make an organization responsible for every later use of the data by other participants. The responsibility reaches only processing operations whose purposes and means that organization helped determine.
This distinction matters in a vendor stack. A provider might process site events only on documented customer instructions in one operation, while deciding independently to use separate information for its own purposes in another. A third party might jointly design a shared protocol but have no role in a customer’s later analytics or advertising decisions. Classify each operation on its facts; do not assign one role to an entire product or relationship.
Article 26 requires joint controllers to set out their respective GDPR responsibilities in an arrangement, especially for handling data-subject rights and providing required information. Article 28 applies when a processor acts on a controller’s behalf and requires a written contract with specified details and safeguards. One agreement may document multiple arrangements, but calling a joint-controller relationship a “DPA” does not make it a processor relationship.
Turn architecture into contract boundaries
Start by drawing the actual data path, from the browser or server to storage and onward integrations. For each distinct operation, record who chooses its purpose, which party selects essential means, what instructions constrain the recipient, and whether the parties make those decisions together. Keep the map tied to the deployed product: a proposed feature is not the same as processing already taking place.
Then align the contracts with those decisions. Where a provider acts only on instructions, document the Article 28 particulars, including the subject matter, duration, nature and purpose, data types, and data-subject categories. Specify how instructions are recorded, how subprocessors are authorized, and how the provider supports security, rights requests, and compliance checks. These clauses should describe working controls, not promise that the customer is always the only controller.
Where purposes and essential means are jointly determined, identify the operation and allocate Article 26 tasks clearly. State how requests are routed, which party maintains the relevant records, and how the arrangement’s essence is made available to people. The allocation does not erase an individual’s rights against either controller.
A developer’s role review
For an analytics integration, ask whether the vendor merely implements the customer’s measurement choices, or also decides why particular data is collected and how it is used. A configurable endpoint alone does not settle that question. Neither does a vendor’s inability to inspect raw event rows: protocol design, required fields, and shared rules can still be relevant evidence of influence.
A useful review artifact is a per-operation table linking product behavior to the relevant contract clause and accountable team. Revisit it when an SDK adds fields, a default changes, a new recipient is introduced, or data begins serving a new purpose. Those changes can alter the role analysis without changing the product’s “processor” label.
The goal is not to make every supplier a joint controller. It is to make the contract tell the same story as the system. If the code and operational controls show who actually chose the purposes and means, the legal allocation becomes testable—and a contract can guide a real implementation instead of masking it.
Sources
- CJEU judgment in Case C-604/22, IAB Europe v Gegevensbeschermingsautoriteit
- General Data Protection Regulation (Regulation (EU) 2016/679), Articles 4, 26, and 28
- EDPB Guidelines 07/2020 on the concepts of controller and processor in the GDPR
- CJEU judgment in Case C-683/21, Nacionalinis visuomenės sveikatos centras
Comments
Loading comments…