mukul975/privacy-data-protection-skills

gdpr-prior-consultation

- Guides the GDPR Article 36 prior consultation process with supervisory authorities when a DPIA indicates high residual risk.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill gdpr-prior-consultation

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Conducting Prior Consultation Process

Overview

Article 36 requires controllers to consult the supervisory authority prior to processing where a DPIA under Art. 35 indicates that the processing would result in a high risk in the absence of measures taken by the controller to mitigate the risk, and the controller is unable to sufficiently mitigate that risk.

When Prior Consultation Is Required

Prior consultation is mandatory when all of the following conditions are met:

  1. A DPIA has been conducted under Art. 35.
  2. The DPIA identifies high risks to data subjects' rights and freedoms.
  3. All reasonably available mitigation measures have been applied.
  4. Residual risk remains high despite mitigation efforts.

Required Documentation (Art. 36(3))

The controller must provide:

  1. Respective responsibilities of controller, joint controllers, and processors
  2. Purposes and means of the intended processing
  3. Measures and safeguards to protect data subjects
  4. DPO contact details
  5. The completed DPIA under Art. 35
  6. Any other information the authority requests

Timeline

PhaseDurationReference
Authority initial response period8 weeks from receiptArt. 36(2)
Extension for complex casesUp to 6 additional weeksArt. 36(2)
Maximum total period14 weeksArt. 36(2)
Processing commencementOnly after advice received or deadline expiredArt. 36(2)

Consultation Process

Step 1: Pre-Submission Preparation

  1. Verify the DPIA is complete with all Art. 35(7) mandatory elements.
  2. Confirm all available mitigation measures have been documented.
  3. Document why residual risk remains high despite mitigation.
  4. Obtain DPO review and sign-off.
  5. Prepare the submission package with all Art. 36(3) documents.

Step 2: Submission

  1. Submit to the competent supervisory authority (lead authority for cross-border processing under Art. 56).
  2. Use the authority's prescribed format if available.
  3. Retain proof of submission with date stamp.

Step 3: Authority Engagement

  1. Respond promptly to requests for additional information.
  2. Track the 8-week deadline and any extension notifications.
  3. Do not commence processing until advice is received or deadline expires.

Step 4: Outcome Handling

OutcomeAction
Authority approvesProceed subject to any conditions specified
Authority provides recommendationsImplement recommendations, document compliance
Authority objects or restrictsDo not proceed; revise processing design; resubmit if appropriate
No response within deadlineDocument that consultation was submitted and deadline expired; may proceed

Member State Variations

Art. 36(5) permits Member State law to require prior consultation for processing in the public interest, including social protection and public health. Controllers must check local implementing legislation.

Common Reasons for Triggering Prior Consultation

  • Large-scale biometric identification systems
  • Systematic public area surveillance with facial recognition
  • Processing of genetic data at population scale
  • Automated decision-making with legal or similarly significant effects where mitigation is insufficient
  • Novel technology processing with unpredictable risk profiles

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
mukul975
コミュニティ

applying-privacy-design-patterns

- Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate. Covers pattern selection methodology per processing activity, mapping to GDPR principles, and practical implementation guidance for privacy-by-design system architecture.

導入数
1
GitHub Stars
315
更新日
3月16日
mukul975
コミュニティ

brazil-lgpd

- Guides compliance with Brazil's Lei Geral de Proteção de Dados (LGPD, Lei 13.709/2018). Covers the 10 lawful bases under Art. 7, DPO appointment, ANPD enforcement, data subject rights under Arts. 17-22, and international transfer mechanisms. Keywords: LGPD, Brazil data protection, ANPD, lawful bases, data subject rights, international transfers.

導入数
1
GitHub Stars
315
更新日
3月16日
mukul975
コミュニティ

adequacy-assessment

- 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.

導入数
1
GitHub Stars
295
更新日
3月16日
mukul975
コミュニティ

age-gating-services

- 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.

導入数
1
GitHub Stars
295
更新日
3月16日