What is a Record of Processing Activities?

Record of Processing Activities - definition

A Record of Processing Activities, often called a ROPA, is the internal compliance record required by Article 30 of Regulation (EU) 2016/679, the General Data Protection Regulation (GDPR). It describes how an organization processes personal data, why it does so, who is involved, how long the data is kept, and which security measures protect it.

For image and video processing, a ROPA must cover both the original footage and any anonymization workflow applied to that footage. Video monitoring, face blurring, and license plate blurring are separate or related processing activities, depending on how the organization designs the workflow. The record should make that design clear.

A ROPA is not a privacy notice, a data protection impact assessment, or a technical configuration file. It is a structured compliance document that allows an organization and a supervisory authority to understand the processing. Article 30(4) GDPR requires the controller or processor to make the record available to the supervisory authority on request.

What Article 30 GDPR requires

Article 30 GDPR has separate requirements for controllers and processors. A controller decides the purposes and essential means of the processing. A processor acts on documented instructions from the controller. In video anonymization projects, the distinction matters because the same tool can be used in either role.

Article 30 field

How to describe video monitoring and anonymization

Controller or processor identity

Name the entity operating the cameras, receiving the footage, or anonymizing the files. Include contact details, joint controllers where purposes are shared, and the representative or data protection officer where applicable.

Purposes of processing

Examples include site security, incident investigation, access control, evidence handling, disclosure to an insurer, publication after anonymization, or responding to a data subject access request.

Categories of processing

For processor records, describe the categories of processing carried out on behalf of each controller, such as storage, review, export, anonymization, secure deletion, or hosting.

Categories of data subjects

Employees, visitors, customers, contractors, vehicle drivers, pedestrians, or persons incidentally captured in a wider scene.

Categories of personal data

Face images, license plates, vehicle appearance, location and time metadata, visible behavior, and audio if recorded.

Recipients

Internal security teams, external security providers, law enforcement, insurers, courts, auditors, or media teams receiving anonymized exports.

Transfers outside the European Economic Area

State whether footage or anonymized files are transferred internationally and identify the transfer mechanism under Chapter V GDPR.

Retention periods

Record the retention period or retention criteria for raw footage, working copies, anonymized exports, and deletion of temporary files.

Technical and organizational measures

Access control, encryption, role separation, audit trails, secure deletion, on-premise processing, review workflows, and irreversible blurring settings.

How to include monitoring and anonymization of recordings

The ROPA should treat anonymization as processing in its own right. Blurring a face or license plate requires access to the original personal data before the anonymized output is produced. The original footage remains personal data until it is deleted or otherwise made inaccessible according to the retention rule.

For a practical record, describe the processing chain from capture to deletion. This helps distinguish raw footage, temporary processing copies, and final anonymized files.

  1. Capture: identify where cameras are located and whether they record continuously, on motion, or by event.
  2. Storage: identify storage location, access rights, encryption, backup rules, and retention period.
  3. Selection: describe who selects footage for review, export, disclosure, or anonymization.
  4. Anonymization: state whether faces, license plates, or both are detected and blurred. In Gallio PRO, automatic blurring covers faces and license plates only.
  5. Manual editing: record whether the built-in editor is used to manually mask objects not detected automatically, such as logos, tattoos, name badges, documents, or monitor content.
  6. Output: identify who receives the blurred file and whether the original remains available.
  7. Deletion: record deletion rules for originals, working copies, exports, and review files.

Key parameters for video anonymization records

Article 30 does not prescribe technical metrics for blurring quality. However, a useful ROPA should reference the parameters that affect identifiability, review effort, and security. These parameters can be stored in the ROPA itself or in a linked standard operating procedure.

Parameter

Why it matters

Object scope

States whether the process covers faces, license plates, or both. It should not imply whole-body or silhouette anonymization if the system does not perform it.

Processing mode

Distinguishes batch processing of files from real-time processing. Gallio PRO does not perform real-time anonymization or video stream anonymization.

Review rule

Defines whether a human reviewer checks the output before disclosure or publication.

Blur strength or masking method

Supports consistency and helps assess whether the output is sufficiently resistant to re-identification.

Logging scope

States what operational logs are created. Gallio PRO does not collect logs containing face detections, license plate detections, personal data, or sensitive data.

Deployment model

Identifies whether processing is on-premise, which can reduce transfers of raw footage to external systems.

Relationship with anonymization, pseudonymization, and disclosure

Under Recital 26 GDPR, data is outside the GDPR only when a person is not identified or identifiable, considering all means reasonably likely to be used. Blurring may produce anonymous information if it is strong enough and if no other elements in the footage allow re-identification. If re-identification remains reasonably possible, the result may be pseudonymized, which remains personal data, or otherwise still personal data.

The ROPA should not state that all blurred video is automatically anonymous. It should describe the safeguards and the assessment used. For public disclosure in the European Union, faces usually require masking unless a lawful basis or an applicable image-law exception applies. Some national laws include exceptions for public figures, persons incidentally included in a wider public scene such as a concert, sports event, or assembly, or persons paid for use of their image. License plates should also be treated as identifiers in EU and EEA deployments where they are reasonably linkable to a person, and included in the masking workflow where footage is disclosed or shared.

The primary legal source is Article 30 GDPR, read with Recital 82 GDPR, which explains the accountability function of maintaining records. Article 5(2) GDPR sets the accountability principle. Article 24 GDPR requires controller responsibility, Article 25 GDPR covers data protection by design and by default, and Article 32 GDPR covers security of processing.

Video monitoring may also require a data protection impact assessment under Article 35 GDPR, especially where there is systematic monitoring of a publicly accessible area on a large scale. The European Data Protection Board (EDPB) addressed video processing in Guidelines 3/2019 on processing of personal data through video devices, version 2.0, adopted on January 29, 2020. Anonymization analysis is also informed by Article 29 Working Party Opinion 05/2014 on Anonymisation Techniques, adopted on April 10, 2014, which remains a commonly cited EU reference.

The exemption in Article 30(5) GDPR for organizations with fewer than 250 employees is limited. It does not apply where processing is likely to result in a risk to rights and freedoms, is not occasional, or includes special categories of data under Article 9 GDPR or criminal conviction data under Article 10 GDPR.

US equivalent

There is no direct United States federal equivalent to the GDPR Record of Processing Activities. US organizations often maintain data inventories or records of processing to support sectoral and state obligations, such as the California Consumer Privacy Act as amended by the California Privacy Rights Act, the Illinois Biometric Information Privacy Act, the Health Insurance Portability and Accountability Act, or public records rules. For video footage, the relevant US requirement depends on the sector, state, purpose, and whether the footage contains biometric, health, education, employment, or law enforcement data.

See also