本文へ移動
cccskills
無料GitHub で公開

right-to-object

Handles GDPR Article 21 right to object to processing, including compelling legitimate grounds assessment, ceasing processing obligations, documentation requirements, and the relationship with erasure under Article 17(1)(c). Activate for right to object, Art. 21, objection to processing, legitimate interest queries.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md7.2 KB
  • assets/template.md2.9 KB
  • references/standards.md2.1 KB
  • references/workflows.md2.1 KB
  • scripts/process.py8.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Handling Right to Object to Processing

Overview

The right to object under GDPR Article 21(1) allows data subjects to object to processing based on legitimate interests (Art. 6(1)(f)) or public interest/official authority (Art. 6(1)(e)), including profiling based on those provisions. Upon objection, the controller must cease processing unless it demonstrates compelling legitimate grounds that override the interests, rights, and freedoms of the data subject, or processing is necessary for legal claims.

Legal Foundation

GDPR Article 21 — Right to Object

  1. Art. 21(1) — The data subject has the right to object, on grounds relating to their particular situation, to processing based on Art. 6(1)(e) (public interest) or Art. 6(1)(f) (legitimate interests), including profiling based on those provisions. The controller shall no longer process the personal data unless it demonstrates compelling legitimate grounds for the processing which override the interests, rights, and freedoms of the data subject, or for the establishment, exercise, or defence of legal claims.

  2. Art. 21(2)-(3) — [Covered separately in managing-direct-marketing-objection skill]

  3. Art. 21(4) — At the latest at the time of the first communication with the data subject, the right to object shall be explicitly brought to the attention of the data subject and shall be presented clearly and separately from any other information.

  4. Art. 21(5) — In the context of the use of information society services, the data subject may exercise their right to object by automated means using technical specifications.

  5. Art. 21(6) — Where personal data are processed for scientific or historical research purposes or statistical purposes under Art. 89(1), the data subject has the right to object unless the processing is necessary for the performance of a task carried out for reasons of public interest.

Relationship with Art. 17(1)(c) — Erasure Following Objection

Where the data subject successfully objects and there are no overriding legitimate grounds, the data subject also has the right to erasure under Art. 17(1)(c).

Objection Processing Workflow

Step 1: Receive and Log the Objection

  1. Log with reference OBJ-YYYY-NNNN.
  2. Record the specific processing activities objected to.
  3. Record the data subject's particular situation and grounds.
  4. Acknowledge receipt within 3 business days.
  5. Verify identity.
  6. Immediately cease the objected-to processing pending the compelling grounds assessment (apply restriction under Art. 18(1)(d)).

Step 2: Identify the Processing and Its Legal Basis

  1. Identify all processing activities covered by the objection.
  2. Confirm that the legal basis for each activity is either:
    • Art. 6(1)(e) — Public interest / official authority, or
    • Art. 6(1)(f) — Legitimate interests
  3. If the processing is based on a different legal basis (consent, contract, legal obligation), the right to object under Art. 21(1) does not apply. Inform the data subject of the applicable basis and suggest the appropriate right (e.g., withdrawal of consent under Art. 7(3)).

Step 3: Compelling Legitimate Grounds Assessment

The controller must demonstrate that its legitimate grounds for processing are compelling and override the data subject's interests, rights, and freedoms. This is a higher bar than the standard legitimate interest assessment under Art. 6(1)(f).

Assessment Framework

FactorController's PositionData Subject's Position
Nature of the dataWhat categories? How sensitive?Privacy impact of continued processing
Processing purposeHow critical is this processing to the controller's operations?Alternative means available to the controller?
Impact on data subjectMinimal, moderate, or significant?What specific harm or distress does the subject describe?
Number of affected individualsDoes cessation affect only this subject or others?Individual circumstances cited by the subject
Safeguards in placeWhat measures mitigate the impact on the subject?Are safeguards sufficient from the subject's perspective?
VulnerabilityN/AIs the data subject in a vulnerable situation (child, employee, patient)?
Legal claimsIs the data needed for establishment, exercise, or defence of legal claims?Is the subject's objection related to a legal dispute?

Decision Criteria

  • Compelling grounds established: The controller can continue processing, but must document the assessment in full and inform the data subject of the outcome and their right to complain.
  • Compelling grounds NOT established: The controller must cease processing and inform the data subject. The data subject may also request erasure under Art. 17(1)(c).
  • Legal claims exception: Processing may continue if necessary for legal claims, even without compelling grounds for the main processing purpose.

Step 4: Implement the Decision

If Objection Upheld (No Compelling Grounds)

  1. Cease all objected-to processing activities immediately.
  2. Remove data from processing pipelines, analytics, and any automated systems.
  3. Retain data only in restricted storage (if needed for legal compliance or other valid legal bases).
  4. Notify third-party recipients under Art. 19.
  5. Inform the data subject of their right to request erasure under Art. 17(1)(c).
  6. Update privacy notices and records of processing to reflect the change.

If Objection Overridden (Compelling Grounds)

  1. Resume the objected-to processing (or confirm it was never ceased, if the assessment was completed within the initial processing cycle).
  2. Document the compelling legitimate grounds assessment in full.
  3. Notify the data subject:
    • The specific compelling grounds identified
    • Why those grounds override the data subject's interests
    • The data subject's right to lodge a complaint with the supervisory authority (Art. 77)
    • The data subject's right to a judicial remedy (Art. 79)

Step 5: Document and Close

  1. Record the full assessment in the objection register.
  2. Retain the record for 3 years.
  3. If the objection is upheld, ensure all downstream systems reflect the cessation of processing.
  4. Feed findings into the legitimate interest assessment register to inform future Art. 6(1)(f) reliance.

Response Timeline

  • Standard deadline: 30 calendar days from receipt.
  • Extension: Up to 60 additional days for complex cases.
  • Processing cessation: Must be implemented immediately upon receipt of the objection, pending the compelling grounds assessment. Processing may only resume if compelling grounds are demonstrated.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Implements 42 CFR Part 2 protections for substance use disorder patient records. Covers written consent requirements stricter than HIPAA, re-disclosure prohibition, court order procedures, qualified service organization agreements, and 2024 amendments aligning Part 2 with HIPAA. Keywords: 42 CFR Part 2, substance use disorder, SUD records, re-disclosure, consent, Part 2 amendments.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Preparing EU AI Act compliance documentation for high-risk AI systems. Covers Annex III classification, technical documentation under Art. 11, conformity assessment, risk management systems, and CE marking requirements. Keywords: EU AI Act, high-risk AI, Annex III, conformity assessment, CE marking.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements GDPR Art. 22 automated decision-making and AI Act Art. 14 human oversight requirements for AI systems. Covers identification of solely automated decisions, meaningful human intervention design, logic explanation mechanisms, and contestation procedures. Keywords: Art. 22, automated decision, human oversight, AI Act, profiling, contestation.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

mukul975 のスキルをすべて見る

このスキルの問題を報告する