Sub-processor - definition
A sub-processor is a separate entity engaged by a processor to carry out personal data processing on behalf of the same controller. Under Regulation (EU) 2016/679, the General Data Protection Regulation (GDPR), the term is expressed as “another processor” in Article 28(2) and Article 28(4). In practice, a sub-processor sits one level below the main processor in the processing chain.
For image and video anonymization, a sub-processor may be a hosting provider, cloud storage provider, graphics processing unit (GPU) computing provider, annotation provider, maintenance provider, or technical support provider that can access footage containing identifiable faces or license plates. The key point is access to, or processing of, personal data before anonymization is complete. Once footage is truly anonymized in a way that no longer relates to an identified or identifiable person, the GDPR no longer applies to that output, but the processing steps before that point remain regulated.
Controller authorization and the responsibility chain
The GDPR does not allow a processor to add sub-processors freely. Article 28(2) requires prior written authorization from the controller. This authorization can be specific, naming a particular sub-processor, or general, allowing the processor to use sub-processors subject to notice of intended changes and the controller’s opportunity to object.
Authorization model | What it means | Practical effect for video anonymization |
|---|---|---|
Specific written authorization | The controller approves each named sub-processor before use. | Useful where raw footage is high-risk, such as hospital, school, workplace, or public-security video. |
General written authorization | The controller approves the use of sub-processors in principle and receives notice of changes. | Common for software-as-a-service or managed processing workflows where infrastructure providers may change. |
No authorization | The processor may not lawfully engage the third party for personal data processing. | Using an unapproved provider to store or process identifiable footage creates a GDPR Article 28 compliance gap. |
Article 28(4) creates the chain of responsibility. The processor must impose the same data protection obligations on the sub-processor by contract or other legal act. If the sub-processor fails to meet those obligations, the original processor remains fully liable to the controller for that failure.
Role of a sub-processor in face and license plate blurring
Face detection and license plate detection often occur before anonymization. At that stage, the footage may still identify people, vehicles, locations, timestamps, or behavioral patterns. Any external party that stores, analyzes, renders, transfers, or supports this footage may become a sub-processor if it acts for the processor.
In an on-premise deployment, a software vendor is not automatically a sub-processor. If Gallio PRO is installed and operated within the customer’s own environment, and the vendor has no access to source footage, detection results, or personal data, the vendor will usually be a software supplier rather than a sub-processor. If remote support, managed processing, hosted storage, or diagnostic access gives a vendor access to identifiable footage, the role must be reassessed under Article 28.
Gallio PRO does not collect logs containing face or license plate detections. It also does not collect logs containing personal data or special category data. Automatic blurring covers faces and license plates only. Other visible elements, such as logos, tattoos, name badges, documents, or monitor content, may require manual masking in the built-in editor.
Contract terms required for sub-processing
A sub-processing arrangement should not rely on operational trust alone. The processor-to-sub-processor contract or other legal act must reflect the controller-to-processor obligations required by GDPR Article 28(3) and Article 28(4).
- Subject matter and duration: identify the video or image processing activity and how long the sub-processor may process the footage.
- Nature and purpose: state whether the sub-processor provides storage, compute capacity, support, rendering, transfer, or quality assurance.
- Types of personal data: describe relevant data, such as faces, license plates, timestamps, location context, and audio if audio is processed.
- Categories of data subjects: identify groups such as employees, visitors, patients, students, customers, drivers, or bystanders.
- Security measures: define encryption, access control, authentication, segregation, deletion, backup, and incident handling requirements.
- Deletion or return: require return or deletion of source footage and intermediate files at the end of the service.
- Audit rights: allow the controller or processor, as applicable, to verify compliance through documentation, reports, or audits.
Key parameters for compliance review
Sub-processor assessment should be evidence-based. For image and video anonymization, the review should cover both legal terms and technical exposure.
Parameter | Why it matters |
|---|---|
Access scope | Determines whether the third party can view or process identifiable footage. |
Processing location | Identifies whether international transfer rules under GDPR Chapter V apply. |
Retention period | Limits how long raw footage, temporary files, and processing outputs remain available. |
Support model | Shows whether troubleshooting can occur without access to personal data. |
Security controls | Supports Article 32 measures, including confidentiality, integrity, availability, and resilience. |
Legal basis under EU law
The main source is Regulation (EU) 2016/679, applicable from 25 May 2018. Article 28(2) states that a processor shall not engage another processor without prior specific or general written authorization of the controller. Article 28(4) requires the same data protection obligations to be imposed on the sub-processor and keeps the original processor liable to the controller.
The European Data Protection Board, Guidelines 07/2020 on the concepts of controller and processor in the GDPR, version 2.0 adopted on 7 July 2021, explains how roles must be assessed by the actual allocation of decision-making over purposes and essential means. For transfers outside the European Economic Area, Commission Implementing Decision (EU) 2021/914 on standard contractual clauses may be relevant, together with the GDPR Chapter V transfer rules.
US equivalent
There is no single United States equivalent to the GDPR sub-processor concept across all sectors. The closest concepts are subcontractors of business associates under the Health Insurance Portability and Accountability Act of 1996 (HIPAA), especially 45 CFR 160.103 and 45 CFR 164.502(e), and service provider or contractor flow-down obligations under the California Consumer Privacy Act as amended by the California Privacy Rights Act. These rules are sectoral or state-based and should not be treated as a general federal sub-processing regime.