What is a Data Processing Agreement (DPA)?

Data Processing Agreement - definition

A Data Processing Agreement (DPA) is a contract required by Article 28 of Regulation (EU) 2016/679, the General Data Protection Regulation (GDPR), when a processor processes personal data on behalf of a controller. GDPR Article 4(8) defines a processor as a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller.

For image and video anonymization, a DPA is relevant when an organization sends footage, images, extracted frames, or related metadata to a vendor that acts under the organization’s instructions. The footage may contain faces, license plates, voices, location context, timestamps, or other identifiers. Even if the goal is anonymization, the raw footage and intermediate processing data are personal data until the anonymization is effective under GDPR Recital 26.

A DPA is not a general service agreement. It is a legally required processing contract. It must describe what the processor may do with the footage, how it must protect it, when it must delete or return it, how subprocessors are controlled, and how the controller can verify compliance.

When a video anonymization vendor is a processor

A vendor is usually a processor when the customer decides the purpose and essential means of processing. In this context, the customer decides that footage must be anonymized before publication, disclosure, training, investigation, or archiving. The vendor provides the technical service, such as face detection, license plate detection, masking, blurring, export, or manual review tools.

Scenario

Likely GDPR role

DPA needed?

A customer uploads video to a hosted tool for face and license plate blurring.

Vendor is usually a processor.

Yes, under GDPR Article 28(3).

A vendor remotely accesses customer footage during support or troubleshooting.

Vendor may be a processor for that access.

Yes, if personal data can be viewed or handled.

On-premise software runs only in the customer’s environment, and the vendor has no access to footage, detections, or personal data.

The vendor may not process customer footage.

Not for footage processing, but review support and telemetry separately.

A vendor reuses customer footage to train its own models for its own purposes.

Vendor may become a controller or joint controller for that separate processing.

A DPA alone is not sufficient for that purpose.

The European Data Protection Board (EDPB), in Guidelines 07/2020 on the concepts of controller and processor, Version 2.0, adopted on July 7, 2021, states that role allocation depends on factual influence over purposes and essential means. Contract labels are relevant, but they do not decide the role by themselves.

What Article 28 GDPR requires in a DPA

GDPR Article 28(3) lists mandatory contract content. For video and image anonymization, each item should be translated into operational language that can be audited. A vague statement that the vendor will process data “securely” is not enough.

Article 28 requirement

Practical wording for face and license plate blurring

Subject matter, duration, nature, and purpose of processing

Processing of images and video files to detect and blur faces and license plates, for the contract term or a defined project period.

Types of personal data and categories of data subjects

Visible faces, license plates, contextual video metadata, and persons appearing in footage, such as employees, visitors, patients, students, customers, or members of the public.

Documented instructions

The processor may process footage only to provide anonymization, quality control, support, deletion, agreed export functions, and any agreed third-country transfers.

Confidentiality

Personnel with access to footage must be bound by confidentiality obligations.

Security under Article 32

Access control, encryption where appropriate, separation of environments, secure deletion, and protection against accidental loss or unauthorized disclosure.

Subprocessors

Prior specific or general written authorization, notice of changes, and flow-down obligations equivalent to the DPA.

Assistance to the controller

Support for data subject requests, security incidents, data protection impact assessments, and prior consultation where applicable.

Return or deletion

Return or delete raw footage, processed files, temporary frames, and processing artifacts at the end of services, unless Union or Member State law requires storage.

Audit and information rights

Provide information needed to demonstrate compliance and allow audits or inspections under agreed conditions.

Unlawful instructions

Inform the controller immediately if an instruction appears to infringe GDPR or other Union or Member State data protection law.

Technical parameters to include for image and video anonymization

Article 28 GDPR does not prescribe numerical service levels for anonymization. However, the DPA or an attached security and service schedule should define measurable parameters. These parameters reduce ambiguity and help the controller verify that the processing stays within instructions.

  • Processing scope: whether processing covers faces, license plates, audio, metadata, still images, video files, or extracted frames.
  • Detection scope: whether automatic detection is limited to faces and license plates, and whether other visible elements require manual masking.
  • Retention period: the maximum time raw files, temporary files, exports, backups, and support copies are retained.
  • Security controls: authentication method, role-based access, encryption in transit, encryption at rest where applicable, and administrative access logging.
  • Incident notice: processor notice to the controller “without undue delay” under GDPR Article 33(2), with any stricter contractual deadline stated separately.
  • Quality control: review workflow, sampling method, false negative handling, and manual correction process for missed faces or license plates.

For Gallio PRO deployments, this analysis should reflect the actual architecture. According to the stated Gallio PRO architecture, Gallio PRO performs automatic blurring of faces and license plates only. It does not perform real-time anonymization or video stream anonymization. It does not automatically detect company logos, tattoos, name badges, documents, or content displayed on monitors, although these elements can be blurred manually in the built-in editor. Gallio PRO does not collect application logs containing face or license plate detections and does not collect application logs containing personal data or special category data.

The core legal source is GDPR Article 28, supported by Recital 81 on processor selection and contractual controls, Recital 83 on security, Article 32 on security of processing, Article 33 on personal data breach notification, and Article 35 on data protection impact assessments. GDPR Recital 26 is important because anonymized information falls outside GDPR only when the individual is not identified or identifiable by means reasonably likely to be used.

Useful EU-level references include EDPB Guidelines 07/2020 on controller and processor concepts, adopted on July 7, 2021, and Commission Implementing Decision (EU) 2021/915 of June 4, 2021, which provides standard contractual clauses between controllers and processors under GDPR Article 28(7). If personal data is transferred outside the European Economic Area, the organization must also assess transfer rules under GDPR Chapter V, which is separate from the Article 28 DPA.

US equivalent

There is no single United States equivalent to the GDPR Article 28 DPA that applies across all sectors. Similar contract requirements appear in specific frameworks, such as the Health Insurance Portability and Accountability Act of 1996 (HIPAA) business associate agreement rules at 45 CFR 164.502(e) and 45 CFR 164.504(e), and the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA) service provider and contractor provisions in California Civil Code 1798.100(d) and 1798.140. These US rules use different roles and terminology, so a GDPR DPA should not be treated as a substitute for a HIPAA business associate agreement or a CCPA/CPRA service provider contract.

See also