Right to object - definition
The right to object is a data subject right under Article 21 of Regulation (EU) 2016/679, the General Data Protection Regulation (GDPR). It allows an individual to object, on grounds relating to that individual’s particular situation, to processing of personal data that is based on Article 6(1)(e) GDPR, public task or official authority, or Article 6(1)(f) GDPR, legitimate interests. It also includes a separate right to object to processing for direct marketing under Article 21(2) GDPR.
For image and video footage, the right is especially relevant when an organization records, stores, reviews, publishes, or shares footage on the basis of legitimate interests. Common examples include security camera recordings, incident investigation footage, visitor management recordings, and video material used to document damage, safety events, or service quality. If the footage shows an identifiable person, the image is personal data under Article 4(1) GDPR. A visible license plate can also be personal data where it can be linked to a person.
Article 21(1) GDPR states that, after a valid objection, the controller must stop the processing unless it demonstrates compelling legitimate grounds that override the interests, rights, and freedoms of the data subject, or unless the processing is needed for the establishment, exercise, or defense of legal claims. This is not an automatic deletion right, but it can lead to deletion, restriction, masking, or exclusion of the person from further use of the footage.
Role of Right to object in video anonymization
In a video workflow, the right to object affects both legal assessment and operational handling. A controller that relies on legitimate interests should be able to identify which recordings are affected, what purpose applies, and whether continued processing is still justified.
Scenario | Typical lawful basis | Effect of an Article 21 objection |
|---|---|---|
Closed-circuit television used for premises security | Article 6(1)(f) GDPR, legitimate interests | The controller must verify whether security, incident preservation, or legal claims override the individual objection. |
Publication of event footage showing identifiable attendees | Often Article 6(1)(f) GDPR, depending on context | The controller may need to blur the person’s face, remove the clip, or justify continued publication. |
Sharing footage with an insurer or legal adviser after an incident | Article 6(1)(f) GDPR, unless a specific legal obligation applies | Processing may continue if necessary for legal claims, but irrelevant faces and license plates should be minimized. |
Footage already irreversibly anonymized | GDPR no longer applies if identifiability is removed | Recital 26 GDPR explains that anonymous information is outside GDPR. A later Article 21 objection cannot apply to data that is no longer personal data. |
Operational response to an objection
An objection should be handled as a controlled request, not as an informal editing task. The controller should first confirm whether the requester is identifiable in the footage and whether the processing is based on legitimate interests or public task.
- Register the request. Article 12(3) GDPR requires a response without undue delay and in any event within one month. This may be extended by two further months where necessary due to complexity or number of requests.
- Restrict processing during review. Article 18(1)(d) GDPR gives the data subject a right to restriction while the controller verifies whether its legitimate grounds override the objection.
- Assess overriding grounds. Recitals 47 and 49 GDPR recognize that legitimate interests may exist, including fraud prevention and network and information security, but the assessment must consider the individual’s rights and reasonable expectations.
- Apply a technical measure if appropriate. If continued use of the footage is not justified in identifiable form, the controller can blur the face, blur the license plate, crop the sequence, remove the clip, or limit access.
- Document the decision. Article 5(2) GDPR requires accountability. The record should show the footage identifier, purpose, lawful basis, assessment result, action taken, and response date.
Technical application to faces and license plates
For anonymization work, the right to object often becomes a question of whether the objecting person can remain identifiable in a recording. Face blurring and license plate blurring reduce identifiability when performed with sufficient coverage and quality control.
Gallio PRO supports automatic detection and blurring of faces and license plates in image and video files. It does not perform real-time anonymization or video stream anonymization. It also does not automatically detect company logos, tattoos, name badges, documents, or content displayed on monitors. These elements can be blurred manually with the built-in editor when they create an identification risk.
Important technical controls include detection recall, false negative review, blur strength, frame-by-frame consistency, and audit documentation. The GDPR does not prescribe a numeric recall, precision, or blur radius threshold. The controller must therefore select settings and quality checks that fit the risk, the resolution, the purpose of disclosure, and the likelihood that a person could still be identified.
Limits and common compliance issues
The right to object does not apply to every processing activity in the same way. Article 21(1) applies to processing based on Article 6(1)(e) or Article 6(1)(f) GDPR, while Article 21(2) gives a separate right to object to processing for direct marketing. It does not apply in the same way where processing is based on consent, contract, legal obligation, or vital interests, although other GDPR rights may apply.
Controllers should also distinguish objection from access, erasure, and restriction. If an objection is upheld, erasure under Article 17(1)(c) GDPR may follow where there are no overriding legitimate grounds. If the footage is needed for legal claims, continued retention may be lawful, but wider publication or internal reuse may still need to stop.
Legal basis and references for Right to object
The main legal source is Article 21 GDPR, supported by Recital 69 GDPR. Recital 69 explains that where personal data is processed for public interest, official authority, or legitimate interests, the data subject should have the right to object, and the controller should demonstrate compelling legitimate grounds.
Source | Relevance |
|---|---|
GDPR Article 21(1) | Right to object to processing based on Article 6(1)(e) or Article 6(1)(f). |
GDPR Article 18(1)(d) | Restriction of processing while overriding grounds are verified. |
GDPR Article 12(3) | One-month response deadline, with possible two-month extension. |
GDPR Recital 26 | Anonymous information falls outside GDPR if the person is no longer identifiable. |
European Data Protection Board Guidelines 3/2019 on processing of personal data through video devices, version 2.0, adopted 29 January 2020 | EU-level guidance on video surveillance, transparency, lawful basis, data subject rights, and minimization. |
US equivalent
There is no single United States federal equivalent to Article 21 GDPR. The closest rights are sectoral or state-based, such as opt-out rights under the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act of 2020, and specific biometric rules such as the Illinois Biometric Information Privacy Act, 740 Illinois Compiled Statutes 14. These frameworks do not create a general right to object to all legitimate-interest-based video processing. For US footage, obligations depend on the applicable state privacy law, biometric law, public records law, employment law, court order, or sectoral rule.