Joint controllership - definition
Joint controllership is a concept under European Union data protection law. It exists when two or more controllers jointly determine the purposes and means of processing personal data. The legal basis is Article 26 of Regulation (EU) 2016/679, the General Data Protection Regulation (GDPR), read with the definition of "controller" in Article 4(7).
In GDPR terms, a controller decides why personal data is processed and how essential processing choices are made. Joint controllership does not require equal influence, equal access to the data, or a formal contract before processing begins. It requires converging decisions about the processing purpose and the essential means. The Court of Justice of the European Union confirmed this broad approach in Wirtschaftsakademie, C-210/16, judgment of June 5, 2018, Jehovan todistajat, C-25/17, judgment of July 10, 2018, and Fashion ID, C-40/17, judgment of July 29, 2019.
The European Data Protection Board (EDPB) explains this in Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.0, adopted on July 7, 2021. The EDPB states that joint controllership may cover only a specific processing operation or stage. It does not automatically extend to all earlier or later processing by the same parties.
Role of joint controllership in image and video anonymization
Joint controllership is relevant when several organizations decide together why video or images are collected, analyzed, blurred, retained, or disclosed. This often occurs in projects involving surveillance footage, event recordings, body-worn camera footage, transport video, retail video, or shared evidence review.
For example, a venue operator and an event organizer may jointly decide to publish edited footage from an event. If they jointly define the purpose of publication and the essential anonymization rules, they may be joint controllers for that publication workflow. If one party only provides software under documented instructions and does not decide the purpose, that party is more likely to be a processor under Article 28 GDPR, not a joint controller.
In face and license plate blurring projects, the key legal question is not who owns the camera or who operates the tool. The key question is who determines the purpose and essential means of the processing.
Decision point | Possible controller-level decision | Relevance for blurring |
|---|---|---|
Purpose | Publishing footage, responding to a data subject access request, sharing evidence, or training staff | Defines why faces and license plates must be masked or retained |
Essential means | Categories of footage, categories of persons, retention period, disclosure recipients | Determines the anonymization scope and quality controls |
Non-essential means | File format, workstation configuration, export settings, editor workflow | Usually operational, unless it affects data protection outcomes |
Allocation of duties under Article 26 GDPR
Article 26 GDPR requires joint controllers to determine their respective responsibilities for compliance in a transparent arrangement. The arrangement must address, in particular, the exercise of data subject rights and the duties to provide information under Articles 13 and 14 GDPR. The essence of the arrangement must be made available to data subjects.
A joint controllership arrangement should be more specific than a general cooperation agreement. For video anonymization, it should identify who controls each compliance task and who verifies that the blurring workflow is complete before disclosure.
Compliance task | Recommended allocation question | Relevant GDPR provisions |
|---|---|---|
Transparency notice | Who informs recorded individuals about the shared processing? | Articles 12, 13, 14 |
Data subject requests | Who receives, verifies, and answers access or erasure requests involving footage? | Articles 15, 17, 26 |
Security measures | Who controls access, storage, transfer, and deletion of source and blurred files? | Articles 5(1)(f), 32 |
Quality assurance | Who checks missed faces, missed license plates, and manual masking needs? | Articles 5(1)(d), 5(2), 25 |
Accountability evidence | Who keeps records of decisions, risk assessments, and approvals? | Articles 5(2), 24, 30 |
Practical indicators in face and license plate blurring projects
Joint controllership depends on substance, not labels. A contract that calls one party a processor will not be decisive if both parties actually decide the purposes and essential means. Conversely, technical support or hosting alone does not create joint controllership.
The following indicators help assess the role split in image and video processing projects:
- Joint purpose: both parties agree to use the footage for a shared objective, such as public release, investigation, or operational review.
- Joint selection of footage: both parties decide which recordings, camera angles, dates, or locations are included.
- Joint anonymization policy: both parties decide whether all faces and license plates are blurred, which exceptions apply, and when manual review is required.
- Joint disclosure decision: both parties approve the recipients, publication channel, or external transfer of edited footage.
- Separate downstream use: if one party later reuses the same footage for its own independent purpose, it may be a separate controller for that later stage.
Key parameters and metrics for governance
The GDPR does not prescribe a fixed blur radius, pixelation level, detection recall, or review sampling rate for video anonymization. These parameters should be defined through risk assessment, data protection by design under Article 25 GDPR, and security of processing under Article 32 GDPR. Where processing is likely to result in high risk, a data protection impact assessment may be required under Article 35 GDPR.
A practical governance model can use the following formula:
Residual disclosure risk = detection risk + masking risk + review risk + export risk
Each element should be assigned to one joint controller or to both joint controllers. Detection risk concerns missed faces or license plates. Masking risk concerns insufficient blur, wrong region placement, or visible frames before or after the masked segment. Review risk concerns incomplete human quality checks. Export risk concerns accidental disclosure of the unblurred source file, wrong recipients, or excessive retention.
In Gallio PRO workflows, automatic blurring supports faces and license plates. The software does not automatically detect company logos, tattoos, name badges, documents, or content displayed on monitors. Those elements can be masked manually in the built-in editor when the controllers decide that they must be hidden. Gallio PRO does not perform real-time anonymization or video stream anonymization, and, according to its stated functionality, it does not create logs of face detections or license plate detections. Controllers should still assess whether any operational logs, file names, user accounts, or project metadata contain personal data.
Liability and accountability
Joint controllership does not remove each party's responsibility under the GDPR. Article 26(3) states that a data subject may exercise rights against each controller, regardless of the internal arrangement. Article 82 GDPR also addresses compensation and liability for damage caused by processing that infringes the GDPR.
This means the internal allocation is important, but it is not a complete shield against external claims. Recital 79 GDPR links responsibility to clear allocation of duties. Recital 146 GDPR explains that controllers involved in the same processing may be held liable, subject to the rules on responsibility and contribution. For video anonymization, this makes documented approval, quality control, access control, and deletion responsibilities central evidence of compliance.
EU legal basis and references
The primary sources for joint controllership are EU-level legal materials. National supervisory authorities may add examples, but the core test comes from the GDPR, the EDPB, and the Court of Justice of the European Union.
- Regulation (EU) 2016/679, General Data Protection Regulation, Article 4(7), Article 26, Article 25, Article 32, Article 35, Article 82, Recitals 79 and 146.
- European Data Protection Board, Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.0, adopted July 7, 2021.
- Court of Justice of the European Union, Wirtschaftsakademie Schleswig-Holstein, C-210/16, judgment of June 5, 2018.
- Court of Justice of the European Union, Jehovan todistajat, C-25/17, judgment of July 10, 2018.
- Court of Justice of the European Union, Fashion ID, C-40/17, judgment of July 29, 2019.
US equivalent
United States privacy law has no general equivalent to GDPR joint controllership. The closest concepts appear in sectoral or state frameworks, such as covered entities and business associates under the Health Insurance Portability and Accountability Act of 1996 (HIPAA), or businesses, service providers, contractors, and third parties under the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA). These frameworks allocate duties by statute and contract, but they do not use the GDPR test of jointly determining purposes and means.