
gdpr-compliance-skills
18 GDPR compliance skills: audit, gap analysis, accountability, DPO, certification, DPA drafting, supervisory authority cooperation
- version
- 1.0.0
- GitHub stars
- 340
Install
/plugin install gdpr-compliance-skills@privacy-data-protection-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.
Contents
Discovered from sourceSkills 18
Implementing GDPR Accountability Framework
Overview
The accountability principle under Art. 5(2) requires controllers to not only comply with data protection principles but to demonstrate that compliance. Art. 24 operationalises this by requiring appropriate technical and organisational measures that can prove compliance, reviewed and updated where necessary. This skill provides a complete framework for building and maintaining the accountability evidence portfolio.
Accountability Documentation Inventory
Tier 1: Governance Documents
| Document | GDPR Reference | Purpose |
|---|---|---|
| Data Protection Policy | Art. 24(2) | Top-level commitment to data protection principles, approved by senior management |
| Data Protection Strategy | Art. 24(1) | Multi-year plan for embedding data protection across the organisation |
| Data Protection Governance Charter | Art. 24(1), 38 | Defines roles, responsibilities, reporting lines, and decision-making authority |
| DPO Appointment and Terms of Reference | Art. 37-39 | Formal appointment, independence, resources, and reporting line |
| Data Protection Training Framework | Art. 39(1)(b) | Training curriculum, frequency, target audiences, and assessment criteria |
Tier 2: Operational Records
| Document | GDPR Reference | Purpose |
|---|---|---|
| Records of Processing Activities (RoPA) | Art. 30 | Comprehensive record of all processing activities with mandatory fields |
| Lawful Basis Register | Art. 6, 9 | Documented lawful basis assessment for each processing activity |
| Data Protection Impact Assessments | Art. 35 | Risk assessments for high-risk processing with mitigation measures |
| Legitimate Interest Assessments | Art. 6(1)(f) | Three-part test documentation for each LI-based processing activity |
| Data Processing Agreements Register | Art. 28 | Inventory of all processor relationships with DPA status |
| International Transfer Records | Art. 46-49 | Transfer mechanisms, TIAs, and safeguard documentation |
| Consent Records | Art. 7 | Evidence of valid consent: who, when, what, and how |
Tier 3: Incident and Response Records
| Document | GDPR Reference | Purpose |
|---|---|---|
| Personal Data Breach Register | Art. 33(5) | Log of all breaches including those not reported to the supervisory authority |
| Breach Notification Records | Art. 33-34 | Records of notifications to supervisory authorities and data subjects |
| Data Subject Rights Request Log | Art. 15-22 | Log of all DSARs with response timelines and outcomes |
| Complaints Register | Art. 77 | Record of data subject complaints and resolutions |
Tier 4: Review and Assurance Records
| Document | GDPR Reference | Purpose |
|---|---|---|
| Audit Reports | Art. 24(1) | Internal and external audit findings and remediation tracking |
| Training Completion Records | Art. 39(1)(b) | Evidence that staff have completed required data protection training |
| Policy Review Records | Art. 24(1) | Version history and approval records for all policies |
| DPO Annual Reports | Art. 38(3), 39 | Annual report to board on data protection posture |
| Risk Register | Art. 24(1), 32 | Data protection risks with likelihood, impact, and treatment plans |
Implementation Roadmap
Phase 1: Foundation (Months 1-3)
- Appoint or confirm the DPO with formal terms of reference and adequate resourcing.
- Draft and obtain board approval for the top-level Data Protection Policy.
- Establish the Data Protection Governance Charter with defined roles (DPO, steering committee, processing owners, data champions).
- Conduct an initial processing activity inventory to populate the RoPA.
- Implement a secure document management system for accountability records.
Phase 2: Operational Documentation (Months 3-6)
- Complete the RoPA with all Art. 30(1) mandatory fields for each processing activity.
- Conduct lawful basis assessments for all processing activities and populate the lawful basis register.
- Identify high-risk processing and initiate DPIAs per Art. 35.
- Audit all processor relationships and execute Art. 28(3) compliant DPAs.
- Document international transfer mechanisms and conduct Transfer Impact Assessments.
- Implement consent management with auditable consent records.
Phase 3: Procedures and Training (Months 6-9)
- Develop operational procedures for: breach notification, DSAR handling, DPIA process, consent management, data retention enforcement.
- Design and deploy the data protection training programme with role-specific modules.
- Establish the personal data breach register and incident response procedure.
- Create the data subject rights request handling process with SLA tracking.
- Test all procedures through tabletop exercises.
Phase 4: Continuous Compliance (Month 9 onwards)
- Schedule the first annual data protection audit.
- Produce the first DPO annual report for the board.
- Implement ongoing monitoring: quarterly RoPA reviews, monthly DSAR metrics, weekly breach register review.
- Feed audit findings and incident learnings into policy and procedure updates.
- Track regulatory developments and update the framework as required.
Evidence Portfolio Structure
Organise accountability evidence in a centralised repository:
Accountability Portfolio/
├── 01-Governance/
│ ├── data-protection-policy-v3.2.pdf
│ ├── governance-charter.pdf
│ ├── dpo-appointment-letter.pdf
│ └── board-minutes-dp-reporting.pdf
├── 02-Processing-Records/
│ ├── ropa-export-2026-01.xlsx
│ ├── lawful-basis-register.xlsx
│ └── consent-records/
├── 03-Risk-Assessments/
│ ├── dpias/
│ ├── lias/
│ └── transfer-impact-assessments/
├── 04-Processor-Management/
│ ├── dpa-register.xlsx
│ ├── due-diligence-reports/
│ └── signed-dpas/
├── 05-Incidents/
│ ├── breach-register.xlsx
│ ├── breach-notification-records/
│ └── dsar-log.xlsx
├── 06-Training/
│ ├── training-programme.pdf
│ └── completion-records/
├── 07-Audits/
│ ├── audit-reports/
│ └── remediation-tracker.xlsx
└── 08-Annual-Reports/
└── dpo-annual-report-2025.pdf
Maturity Assessment
Assess accountability maturity across five levels:
| Level | Description | Indicators |
|---|---|---|
| 1 — Ad Hoc | No systematic accountability | Policies absent, no RoPA, no DPO, no training |
| 2 — Reactive | Basic compliance efforts triggered by incidents or complaints | Some policies exist, RoPA incomplete, training ad hoc |
| 3 — Defined | Systematic framework established with documented procedures | All Tier 1-2 documents exist, DPO appointed, annual training |
| 4 — Managed | Framework actively maintained with metrics and monitoring | Regular audits, DSAR tracking, breach register maintained, board reporting |
| 5 — Optimised | Continuous improvement with proactive risk management | Privacy by design embedded, automated monitoring, predictive risk assessment |
Implementing Data Protection Certification
Overview
Articles 42-43 establish a framework for data protection certification mechanisms, seals, and marks to demonstrate GDPR compliance for processing operations. Certification is voluntary but serves as an accountability tool under Art. 24(3) and can demonstrate sufficient guarantees under Art. 28(5) for processors. Certification does not reduce the responsibility of the controller or processor.
Certification Framework
Art. 42 Key Provisions
- Art. 42(1): Member States, supervisory authorities, the EDPB, and the Commission shall encourage the establishment of certification mechanisms, seals, and marks.
- Art. 42(3): Certification shall be voluntary and available via a transparent process.
- Art. 42(5): Certification is issued by accredited certification bodies or the competent supervisory authority based on criteria approved by the authority or the EDPB.
- Art. 42(7): Certification is issued for a maximum of three years and can be renewed under the same conditions.
- Art. 42(7): Certification shall be withdrawn when requirements are no longer met.
Art. 43 Certification Bodies
- Art. 43(1): Certification bodies must demonstrate independence, expertise, and absence of conflicts of interest.
- Art. 43(3): Accreditation is granted by the supervisory authority or the national accreditation body (per Regulation (EC) No 765/2008).
- Art. 43(6): Accreditation is issued for a maximum of five years and is renewable.
Certification Criteria Development
Certification criteria must address:
- Processing operations scope: Define which processing activities the certification covers.
- Compliance requirements: Map certification criteria to specific GDPR articles.
- Technical measures: Specify the technical controls that must be in place (encryption, access controls, pseudonymisation).
- Organisational measures: Specify governance, training, documentation, and accountability requirements.
- Audit methodology: Define how compliance will be assessed (document review, technical testing, interviews).
- Ongoing compliance: Specify monitoring, reporting, and re-certification requirements.
Available GDPR Certification Schemes
| Scheme | Scope | Status |
|---|---|---|
| EDPB-approved criteria for Europrivacy | Full GDPR compliance certification | Approved by EDPB (Opinion 28/2022) |
| ISO/IEC 27701:2019 | Privacy Information Management System | Widely available; not a formal GDPR certification but demonstrates compliance |
| EuroPriSe (European Privacy Seal) | Products, IT systems, and services | Operating since 2008; updated for GDPR |
| CNIL Certification (France) | DPO competency certification | Approved by CNIL |
Implementation Roadmap
Phase 1: Readiness Assessment (Months 1-2)
- Identify the certification scheme appropriate for the organisation's needs.
- Conduct a gap assessment against the certification criteria.
- Prepare a remediation plan for identified gaps.
Phase 2: Implementation (Months 3-6)
- Implement required technical and organisational measures.
- Update documentation to meet certification criteria.
- Conduct internal pre-assessment audit.
Phase 3: Certification Audit (Months 7-8)
- Engage the accredited certification body.
- Undergo the certification audit (document review, on-site assessment, technical testing).
- Address any non-conformities identified during the audit.
- Receive certification decision.
Phase 4: Maintenance (Ongoing)
- Implement continuous monitoring aligned with certification requirements.
- Conduct annual surveillance audits.
- Prepare for re-certification before the 3-year expiry.
- Report any material changes to the certification body.
Developing Codes of Conduct
Overview
Articles 40-41 provide a framework for associations representing categories of controllers or processors to prepare codes of conduct. Codes specify the application of GDPR to specific sectors, provide practical guidance, and serve as an accountability tool under Art. 24(3).
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
Conducting Data Protection Audit
Overview
A data protection audit systematically evaluates an organisation's compliance with GDPR requirements across governance, processing activities, data subject rights, security measures, and third-party arrangements. This skill provides a structured audit framework with 50+ control points mapped to specific GDPR articles, enabling auditors to produce a comprehensive compliance assessment with prioritised remediation recommendations.
Audit Framework Structure
The audit is organised into eight domains aligned to core GDPR chapters and articles:
- Data Protection Principles (Art. 5)
- Accountability and Governance (Art. 24, 5(2))
- Privacy by Design and Default (Art. 25)
- Processor Management (Art. 28)
- Records of Processing (Art. 30)
- Security of Processing (Art. 32)
- Data Protection Impact Assessments (Art. 35)
- Data Protection Officer (Art. 37-39)
Domain 1: Data Protection Principles (Art. 5)
| # | Control Point | GDPR Ref | Evidence Required |
|---|---|---|---|
| 1.1 | Processing purposes are specified, explicit, and documented for each activity | Art. 5(1)(a)-(b) | RoPA with specific purpose statements |
| 1.2 | A valid lawful basis is identified and documented for each processing activity | Art. 5(1)(a), 6 | Lawful basis register/assessment records |
| 1.3 | Personal data collected is adequate, relevant, and limited to what is necessary | Art. 5(1)(c) | Data minimisation reviews, field-level justification |
| 1.4 | Personal data is accurate and kept up to date with rectification procedures | Art. 5(1)(d) | Data quality processes, rectification logs |
| 1.5 | Retention periods are defined for all data categories with deletion/anonymisation procedures | Art. 5(1)(e) | Retention schedule, deletion logs |
| 1.6 | Appropriate security measures protect personal data against unauthorised access, loss, or destruction | Art. 5(1)(f) | Security controls documentation, pen test reports |
| 1.7 | The controller can demonstrate compliance with all principles (accountability) | Art. 5(2) | Compiled evidence portfolio |
Domain 2: Accountability and Governance (Art. 24)
| # | Control Point | GDPR Ref | Evidence Required |
|---|---|---|---|
| 2.1 | A data protection policy is approved by senior management and communicated to all staff | Art. 24(2) | Signed policy, distribution records |
| 2.2 | Data protection roles and responsibilities are formally assigned across the organisation | Art. 24(1) | RACI matrix, job descriptions |
| 2.3 | Regular data protection training is provided to all staff processing personal data | Art. 39(1)(b) | Training records, attendance logs, completion certificates |
| 2.4 | A data protection governance structure exists with board-level reporting | Art. 24, 38(3) | Governance charter, board meeting minutes |
| 2.5 | Documented procedures exist for all GDPR obligations (breach notification, DSAR, DPIA) | Art. 24(1) | Procedure documents with version control |
| 2.6 | Internal audits of data protection compliance are conducted at defined intervals | Art. 24(1) | Audit schedule, previous audit reports |
| 2.7 | A data protection risk register is maintained and reviewed | Art. 24(1) | Risk register with risk scores and treatment plans |
Domain 3: Privacy by Design and Default (Art. 25)
| # | Control Point | GDPR Ref | Evidence Required |
|---|---|---|---|
| 3.1 | Privacy requirements are integrated into the systems development lifecycle | Art. 25(1) | SDLC documentation with privacy checkpoints |
| 3.2 | Privacy impact is assessed before deploying new systems or changing existing processing | Art. 25(1) | DPIA screening records, change management logs |
| 3.3 | Default settings ensure only necessary personal data is processed | Art. 25(2) | Configuration reviews, default settings documentation |
| 3.4 | Data minimisation is applied at the design stage of systems and processes | Art. 25(1) | Design documents showing minimisation decisions |
| 3.5 | Pseudonymisation and encryption are considered in system design | Art. 25(1), 32(1)(a) | Architecture documents, encryption standards |
| 3.6 | User interfaces facilitate data subject rights (access, deletion, portability) | Art. 25(1)-(2) | UI/UX specifications, data export functionality |
Domain 4: Processor Management (Art. 28)
| # | Control Point | GDPR Ref | Evidence Required |
|---|---|---|---|
| 4.1 | All processors are identified and recorded in a vendor register | Art. 28(1) | Vendor register with processor classifications |
| 4.2 | Written data processing agreements are in place with all processors containing Art. 28(3) mandatory clauses | Art. 28(3) | DPA register, sample DPA review |
| 4.3 | Processor due diligence is conducted before engagement and periodically thereafter | Art. 28(1) | Due diligence questionnaires, assessment reports |
| 4.4 | Sub-processor authorisation and notification procedures are documented | Art. 28(2)-(4) | Sub-processor clauses, notification records |
| 4.5 | Processor compliance is monitored through audits, certifications, or self-assessments | Art. 28(3)(h) | Audit rights exercised, SOC 2/ISO 27001 certificates |
| 4.6 | Processors return or delete personal data upon contract termination | Art. 28(3)(g) | Data return/deletion confirmations |
| 4.7 | Processor breach notification obligations are contractually defined and tested | Art. 28(3)(f), 33 | DPA breach clauses, incident response test results |
Domain 5: Records of Processing (Art. 30)
| # | Control Point | GDPR Ref | Evidence Required |
|---|---|---|---|
| 5.1 | A comprehensive RoPA is maintained for all controller processing activities | Art. 30(1) | Complete RoPA with all Art. 30(1)(a)-(g) fields |
| 5.2 | Processor records are maintained for all processing on behalf of controllers | Art. 30(2) | Processor RoPA with Art. 30(2)(a)-(d) fields |
| 5.3 | RoPA is kept up to date with a defined review and update process | Art. 30(1)-(2) | Last review dates, update procedure |
| 5.4 | RoPA can be made available to the supervisory authority on request | Art. 30(4) | Export capability, access procedure |
| 5.5 | RoPA is maintained in writing (including electronic form) | Art. 30(3) | Electronic RoPA system or documented spreadsheet |
Domain 6: Security of Processing (Art. 32)
| # | Control Point | GDPR Ref | Evidence Required |
|---|---|---|---|
| 6.1 | Risk assessments are conducted to determine appropriate security measures | Art. 32(1)-(2) | Risk assessment reports for processing activities |
| 6.2 | Pseudonymisation and encryption of personal data are implemented where appropriate | Art. 32(1)(a) | Encryption at rest and in transit documentation |
| 6.3 | Ongoing confidentiality, integrity, availability, and resilience of systems is ensured | Art. 32(1)(b) | ISO 27001 controls, access management, BCP/DR plans |
| 6.4 | Ability to restore access to personal data in a timely manner after an incident | Art. 32(1)(c) | Backup procedures, restoration testing records |
| 6.5 | Regular testing and evaluation of security measures is performed | Art. 32(1)(d) | Penetration test reports, vulnerability scans, audit results |
| 6.6 | Access to personal data is restricted on a need-to-know basis | Art. 32(1)(b) | Access control matrices, user access reviews |
| 6.7 | Physical security controls protect premises where personal data is processed | Art. 32(1)(b) | Physical security policy, access logs |
| 6.8 | Personal data breach detection and response procedures are in place | Art. 33-34 | Incident response plan, breach register |
Domain 7: Data Protection Impact Assessments (Art. 35)
| # | Control Point | GDPR Ref | Evidence Required |
|---|---|---|---|
| 7.1 | Criteria for mandatory DPIA are defined and communicated to the organisation | Art. 35(1),(3) | DPIA threshold criteria, DPA blacklist consideration |
| 7.2 | DPIAs are conducted before processing that is likely to result in high risk | Art. 35(1) | DPIA register with completion dates |
| 7.3 | DPIAs contain all Art. 35(7) mandatory elements (description, necessity, risks, measures) | Art. 35(7) | Sample DPIA review for completeness |
| 7.4 | The DPO is consulted during the DPIA process | Art. 35(2) | DPO consultation records, sign-off |
| 7.5 | Data subject views are sought where appropriate | Art. 35(9) | Consultation records or documented rationale for not consulting |
| 7.6 | DPIA outcomes are implemented and monitored | Art. 35(11) | Remediation tracking, follow-up reviews |
| 7.7 | Prior consultation with the supervisory authority is initiated when residual risk remains high | Art. 36 | Prior consultation records (if applicable) |
Domain 8: Data Protection Officer (Art. 37-39)
| # | Control Point | GDPR Ref | Evidence Required |
|---|---|---|---|
| 8.1 | A DPO is appointed where required (public authority, large-scale monitoring, special categories) | Art. 37(1) | DPO appointment letter, published contact details |
| 8.2 | The DPO has sufficient resources, independence, and access to senior management | Art. 38(1)-(3) | Budget allocation, reporting line documentation |
| 8.3 | The DPO does not receive instructions regarding the exercise of their tasks | Art. 38(3) | Independence clause in employment/service contract |
| 8.4 | The DPO's contact details are published and communicated to the supervisory authority | Art. 37(7) | Website publication, DPA notification records |
| 8.5 | The DPO is involved in all data protection matters in a timely manner | Art. 38(1) | Meeting invitations, consultation records |
| 8.6 | The DPO monitors compliance, provides advice, and cooperates with the supervisory authority | Art. 39(1) | DPO activity reports, advisory records |
Audit Execution Methodology
Phase 1: Planning (Week 1)
- Define audit scope (full organisation or targeted domains).
- Assemble audit team with data protection and information security expertise.
- Issue audit notification to business units 2 weeks in advance.
- Request pre-audit documentation package from each domain owner.
Phase 2: Document Review (Weeks 2-3)
- Review all requested evidence against each control point.
- Classify each control as: Effective, Partially Effective, Ineffective, or Not Implemented.
- Identify gaps where evidence is missing or insufficient.
Phase 3: Testing and Interviews (Weeks 3-4)
- Conduct interviews with processing owners, IT security, HR, legal, and the DPO.
- Perform sample testing of key controls (e.g., access reviews, breach simulations, DSAR process walkthroughs).
- Verify technical controls through configuration reviews or tool demonstrations.
Phase 4: Reporting (Week 5)
- Produce audit report with findings classified by severity (Critical, Major, Minor, Observation).
- Include a compliance score per domain and overall maturity rating.
- Provide prioritised remediation roadmap with owners and deadlines.
- Present findings to the Data Protection Steering Committee and Board.
Phase 5: Follow-up (Ongoing)
- Track remediation actions through the findings register.
- Conduct follow-up reviews at 30/60/90 day intervals depending on severity.
- Feed audit findings into the annual DPO report and risk register updates.
Reviewing Documentation of Processing
Overview
GDPR compliance depends on comprehensive, accurate, and current documentation. This skill provides methodology for reviewing RoPA, privacy notices, DPAs, DPIAs, consent records, and internal policies for internal consistency and alignment with actual processing.
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
Establishing Data Processing Agreements
Overview
Article 28(3) requires that processing by a processor is governed by a contract or other legal act that is binding on the processor and sets out specific mandatory elements. This skill details all eight mandatory clauses, provides a compliance checklist, and references the 2021 EU Standard Contractual Clauses for controller-to-processor transfers.
Art. 28(3) Mandatory Elements
Element 1: Subject-Matter and Duration
The DPA must specify the subject-matter of the processing (what processing is being carried out), the duration (aligned with the service contract term), the nature of the processing (collection, storage, analysis, deletion), and the purpose of the processing.
Element 2: Type of Personal Data
The DPA must list the specific categories of personal data being processed (names, email addresses, financial data, health data, etc.).
Element 3: Categories of Data Subjects
The DPA must identify which data subjects are affected (employees, customers, website visitors, patients, etc.).
Element 4: Obligations and Rights of the Controller
The DPA must set out the controller's documented instructions to the processor, covering what the processor is authorised to do with the data.
Element 5: Processor Obligations (Art. 28(3)(a)-(h))
(a) Documented instructions: The processor shall process personal data only on documented instructions from the controller, including with regard to transfers to third countries, unless required to do so by EU or Member State law — in which case the processor must inform the controller before processing (unless the law prohibits such notification).
(b) Confidentiality: The processor shall ensure that persons authorised to process the personal data have committed to confidentiality or are under an appropriate statutory obligation of confidentiality.
(c) Security measures: The processor shall take all measures required pursuant to Article 32 (security of processing).
(d) Sub-processors: The processor shall not engage another processor without prior specific or general written authorisation of the controller. In the case of general written authorisation, the processor must inform the controller of any intended changes concerning the addition or replacement of sub-processors, giving the controller the opportunity to object (Art. 28(2) and (4)).
(e) Assistance with data subject rights: The processor shall assist the controller by appropriate technical and organisational measures, insofar as this is possible, for the fulfilment of the controller's obligation to respond to data subject requests (Art. 15-22).
(f) Assistance with GDPR obligations: The processor shall assist the controller in ensuring compliance with Articles 32-36 (security, breach notification, DPIAs, prior consultation), taking into account the nature of processing and the information available to the processor.
(g) Data return or deletion: At the choice of the controller, the processor shall delete or return all personal data after the end of the provision of processing services, and delete existing copies unless EU or Member State law requires storage.
(h) Audit and inspection: The processor shall make available to the controller all information necessary to demonstrate compliance with Art. 28 obligations, and allow for and contribute to audits, including inspections, conducted by the controller or another auditor mandated by the controller.
Element 6: International Transfers
If the processor or any sub-processor transfers personal data outside the EEA, appropriate safeguards must be in place (SCCs, BCRs, adequacy decision, or derogation).
Element 7: Sub-Processor Chain
The processor must impose the same data protection obligations in the sub-processing contract. The initial processor remains fully liable to the controller for the sub-processor's performance (Art. 28(4)).
Element 8: Written Form
The contract must be in writing, including in electronic form (Art. 28(9)).
DPA Compliance Checklist
| # | Requirement | Art. Reference | Present? |
|---|---|---|---|
| 1 | Subject-matter and duration specified | Art. 28(3) | |
| 2 | Nature and purpose of processing defined | Art. 28(3) | |
| 3 | Types of personal data listed | Art. 28(3) | |
| 4 | Categories of data subjects identified | Art. 28(3) | |
| 5 | Processor acts only on documented instructions | Art. 28(3)(a) | |
| 6 | Notification if law requires processing beyond instructions | Art. 28(3)(a) | |
| 7 | Confidentiality commitment for authorised personnel | Art. 28(3)(b) | |
| 8 | Art. 32 security measures implemented | Art. 28(3)(c) | |
| 9 | Sub-processor authorisation mechanism specified | Art. 28(3)(d), 28(2) | |
| 10 | Sub-processor change notification procedure | Art. 28(4) | |
| 11 | Controller objection right to new sub-processors | Art. 28(2) | |
| 12 | Same obligations imposed on sub-processors | Art. 28(4) | |
| 13 | Assistance with data subject rights requests | Art. 28(3)(e) | |
| 14 | Assistance with Art. 32-36 obligations | Art. 28(3)(f) | |
| 15 | Data return or deletion upon contract end | Art. 28(3)(g) | |
| 16 | Audit and inspection rights for controller | Art. 28(3)(h) | |
| 17 | Information to demonstrate compliance | Art. 28(3)(h) | |
| 18 | International transfer safeguards (if applicable) | Art. 28(3), Ch. V | |
| 19 | Written form (including electronic) | Art. 28(9) | |
| 20 | Processor breach notification to controller | Art. 33(2) |
2021 Standard Contractual Clauses Reference
Commission Implementing Decision (EU) 2021/914 of 4 June 2021 established new SCCs that include a Module Two (Controller to Processor) and Module Three (Processor to Processor) set. These SCCs can serve as the DPA or can supplement an existing DPA for international transfers. Key clauses in the controller-to-processor module:
- Clause 7: Docking clause (additional parties can accede)
- Clause 8: Data protection safeguards including Art. 28(3) requirements
- Clause 9: Sub-processor provisions with specific or general authorisation
- Clause 10: Data subject rights
- Clause 13: Supervision by supervisory authority
- Clause 14: Transfer impact assessment obligations
- Clause 15: Obligations in case of government access requests
Practical Considerations
Negotiation Priorities
- Audit rights: Ensure meaningful audit rights, not just acceptance of SOC 2 reports as a substitute for on-site audits.
- Sub-processor transparency: Require a current list of sub-processors and timely notification (at least 30 days) before changes.
- Breach notification timeline: Art. 33(2) requires "without undue delay" — specify a concrete timeline (e.g., 24-48 hours).
- Data deletion evidence: Require written certification of deletion with a specific format and timeline.
- Liability: Art. 82(2) establishes processor liability for damage caused by non-compliance with processor-specific obligations or acting outside/against controller instructions.
GDPR Supervisory Authority Cooperation
Overview
Article 31 requires controllers and processors to cooperate, on request, with the supervisory authority in the performance of its tasks. This obligation is unconditional and applies to all interactions with data protection authorities, including formal investigations, audit requests, information requests, and complaint-driven inquiries. Non-cooperation can itself result in administrative fines under Art. 83(5)(e).
Types of Supervisory Authority Interactions
1. Information Requests (Art. 58(1)(a))
The supervisory authority may order the controller and processor to provide any information it requires for the performance of its tasks. Responses are typically required within 4 weeks unless a shorter deadline is specified.
2. Data Protection Audits (Art. 58(1)(b))
The authority may carry out investigations in the form of data protection audits, reviewing documentation, interviewing staff, and testing controls.
3. On-Site Inspections (Art. 58(1)(f))
The authority may obtain access to premises of the controller and the processor, including to any data processing equipment and means.
4. Complaint-Driven Investigations (Art. 77)
When a data subject lodges a complaint, the authority investigates and may request documentation, explanations, and corrective actions from the controller.
5. Cross-Border Cooperation (Art. 56, 60-66)
In cross-border processing cases, the lead supervisory authority cooperates with concerned authorities under the consistency mechanism. Controllers may be required to provide information to multiple authorities.
Response Procedures
Receiving an Authority Request
- Log the request: Record the date, authority, reference number, scope, and deadline in the regulatory correspondence register.
- Notify key stakeholders immediately: DPO, General Counsel, CEO/Managing Director, and the relevant processing owner.
- Assess scope: Determine which processing activities, documents, and personnel are in scope.
- Legal privilege review: Identify any documents that may be subject to legal professional privilege and consult with external counsel.
- Assemble response team: DPO (lead), legal counsel, relevant processing owners, IT/security (if technical information requested).
Preparing the Response
- Gather evidence: Collect all requested documents from the accountability portfolio.
- Verify accuracy: Cross-check all documents for consistency and currency before submission.
- Draft response letter: Address each item requested with specific evidence or explanation.
- Quality review: DPO and legal counsel review the complete response package.
- Submit within deadline: Submit the response via the authority's preferred channel with delivery confirmation.
- Archive: File a copy of the response in the regulatory correspondence register.
During On-Site Inspections
- Preparation: Ensure the inspection room is prepared with relevant documentation available. Brief all staff who may be interviewed.
- Escort protocol: Authority inspectors must be accompanied at all times by a designated representative.
- Documentation: Record all questions asked, documents reviewed, and verbal statements made during the inspection.
- Scope management: Politely but firmly ensure the inspection remains within the stated scope. Seek clarification from the authority if requests appear to go beyond the stated purpose.
- Technical access: Provide access to systems as requested but ensure access is supervised and logged.
- Post-inspection: Prepare a detailed internal record of the inspection. Identify any follow-up actions committed to.
Cooperation Obligations vs Legal Rights
While Art. 31 mandates cooperation, controllers and processors retain certain rights:
- Right to legal representation during interviews and inspections
- Right to claim legal professional privilege over attorney-client communications
- Right to request clarification of the legal basis and scope of the investigation
- Right to contest factual inaccuracies in authority findings
- Right to be heard before corrective measures are imposed (Art. 58(4))
- Right to judicial remedy against authority decisions (Art. 78)
Common Pitfalls
- Delayed response: Missing the response deadline is itself a compliance failure that can result in fines.
- Incomplete response: Providing partial information without explaining why certain items are unavailable.
- Inconsistent documentation: Submitting documents that contradict each other or contradict the organisation's public privacy notice.
- Uncoordinated communication: Multiple employees providing different answers to the authority.
- Obstruction: Any action perceived as impeding the authority's investigation, including destroying documents, withholding information, or providing misleading statements.
Appointing EU Representative
Overview
Article 27 requires controllers or processors not established in the Union but subject to GDPR under Art. 3(2) to designate a representative in a Member State where affected data subjects are located.
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
Conducting GDPR Compliance Gap Analysis
Overview
A GDPR compliance gap analysis systematically compares current data protection practices against full GDPR requirements across all chapters, identifying gaps, assigning risk ratings, and producing a prioritised remediation matrix.
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
Managing One-Stop-Shop Mechanism
Overview
Article 56 establishes that the supervisory authority of the main establishment shall be the lead authority for cross-border processing, providing a single point of contact for organisations operating across multiple Member States.
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
Developing GDPR Policy Framework
Overview
A GDPR policy framework provides the documented governance structure underpinning operational compliance, comprising strategic policies, operational procedures, practical guidelines, and training materials aligned to specific GDPR requirements.
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
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:
- A DPIA has been conducted under Art. 35.
- The DPIA identifies high risks to data subjects' rights and freedoms.
- All reasonably available mitigation measures have been applied.
- Residual risk remains high despite mitigation efforts.
Required Documentation (Art. 36(3))
The controller must provide:
- Respective responsibilities of controller, joint controllers, and processors
- Purposes and means of the intended processing
- Measures and safeguards to protect data subjects
- DPO contact details
- The completed DPIA under Art. 35
- Any other information the authority requests
Timeline
| Phase | Duration | Reference |
|---|---|---|
| Authority initial response period | 8 weeks from receipt | Art. 36(2) |
| Extension for complex cases | Up to 6 additional weeks | Art. 36(2) |
| Maximum total period | 14 weeks | Art. 36(2) |
| Processing commencement | Only after advice received or deadline expired | Art. 36(2) |
Consultation Process
Step 1: Pre-Submission Preparation
- Verify the DPIA is complete with all Art. 35(7) mandatory elements.
- Confirm all available mitigation measures have been documented.
- Document why residual risk remains high despite mitigation.
- Obtain DPO review and sign-off.
- Prepare the submission package with all Art. 36(3) documents.
Step 2: Submission
- Submit to the competent supervisory authority (lead authority for cross-border processing under Art. 56).
- Use the authority's prescribed format if available.
- Retain proof of submission with date stamp.
Step 3: Authority Engagement
- Respond promptly to requests for additional information.
- Track the 8-week deadline and any extension notifications.
- Do not commence processing until advice is received or deadline expires.
Step 4: Outcome Handling
| Outcome | Action |
|---|---|
| Authority approves | Proceed subject to any conditions specified |
| Authority provides recommendations | Implement recommendations, document compliance |
| Authority objects or restricts | Do not proceed; revise processing design; resubmit if appropriate |
| No response within deadline | Document 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
Creating GDPR Remediation Roadmap
Overview
A remediation roadmap converts gap analysis findings into an actionable, phased implementation plan prioritised by regulatory risk, data subject impact, and organisational capability.
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
Conducting GDPR Article 30 Records Audit
Overview
Article 30 of the GDPR mandates that every controller and processor maintain written records of processing activities under their responsibility. This skill provides a structured methodology for auditing RoPA entries against the exhaustive field requirements specified in Art. 30(1) for controllers and Art. 30(2) for processors, ensuring completeness, accuracy, and readiness for supervisory authority review.
Controller Record Requirements — Art. 30(1)
Each processing activity record maintained by the controller must contain:
| Field | GDPR Reference | Description |
|---|---|---|
| Controller identity and contact details | Art. 30(1)(a) | Name, address, and contact details of the controller, joint controller, and DPO |
| Purposes of processing | Art. 30(1)(b) | Specific, explicit, and legitimate purposes for each processing activity |
| Categories of data subjects | Art. 30(1)(c) | Identification of all data subject groups (employees, customers, patients, minors) |
| Categories of personal data | Art. 30(1)(c) | Types of personal data processed per activity (identifiers, financial, health, biometric) |
| Categories of recipients | Art. 30(1)(d) | All recipients including processors, joint controllers, and third-country recipients |
| International transfers | Art. 30(1)(e) | Transfers to third countries or international organisations with safeguard documentation |
| Retention periods | Art. 30(1)(f) | Envisaged time limits for erasure of different categories of data |
| Technical and organisational measures | Art. 30(1)(g) | General description of Art. 32 security measures protecting the data |
Processor Record Requirements — Art. 30(2)
| Field | GDPR Reference | Description |
|---|---|---|
| Processor identity and contact details | Art. 30(2)(a) | Name and contact details of the processor(s), each controller on behalf of which the processor acts, and the DPO |
| Categories of processing | Art. 30(2)(b) | Categories of processing carried out on behalf of each controller |
| International transfers | Art. 30(2)(c) | Transfers to third countries or international organisations with safeguard documentation |
| Technical and organisational measures | Art. 30(2)(d) | General description of Art. 32 security measures |
Audit Methodology
Phase 1: Inventory Validation
- Retrieve the current RoPA from the data protection management system or document repository.
- Cross-reference the RoPA against the enterprise application inventory to identify processing activities not yet recorded.
- Verify each business unit has submitted processing activity declarations by comparing against the organisational chart.
- Check that shadow IT and informal data processing (spreadsheets, shared drives) have been captured through departmental interviews.
- Validate that both automated and manual processing activities are represented.
Phase 2: Field Completeness Check
- For each controller record, verify all seven mandatory fields under Art. 30(1)(a)-(g) are populated with specific, non-generic content.
- For each processor record, verify all four mandatory fields under Art. 30(2)(a)-(d) are completed.
- Flag entries where purposes are described in overly broad terms (e.g., "business operations" rather than "payroll calculation for employment contract performance").
- Confirm retention periods are expressed as specific durations or criteria rather than "as long as necessary."
- Verify that security measures reference actual implemented controls, not aspirational statements.
Phase 3: Accuracy Verification
- Sample 20% of RoPA entries and conduct interviews with processing owners to verify accuracy of recorded purposes, data categories, and recipients.
- Compare stated data flows against actual system architecture diagrams and data flow maps.
- Validate that international transfer records match the actual data routing observed in network and application logs.
- Confirm that listed recipients still have valid legal basis and contractual arrangements (Art. 28 agreements for processors, Art. 26 arrangements for joint controllers).
Phase 4: Currency Assessment
- Check the last-reviewed date for each RoPA entry against the organisation's defined review cycle (recommended: at least annually, or upon material change).
- Identify entries that reference discontinued systems, former employees as contacts, or expired contracts.
- Verify that new processing activities introduced since the last review cycle have been added to the RoPA.
- Cross-reference against the change management log and DPIA register to identify unrecorded changes to processing.
Phase 5: Reporting and Remediation
- Produce an audit findings report categorising issues by severity: Critical (mandatory field missing), Major (field incomplete or inaccurate), Minor (formatting or administrative issue).
- Assign remediation owners and deadlines for each finding.
- Schedule a follow-up review within 30 days for critical findings and 90 days for major findings.
- Update the RoPA governance procedure to address systemic gaps identified during the audit.
Exemption Considerations
Article 30(5) provides a limited exemption for organisations with fewer than 250 employees, but this exemption does not apply when:
- Processing is likely to result in a risk to data subjects' rights and freedoms
- Processing is not occasional
- Processing includes special categories of data under Art. 9(1) or personal data relating to criminal convictions under Art. 10
In practice, most organisations with any regular customer or employee data processing will not qualify for this exemption.
Common Audit Findings
- Missing processor records: Controllers maintain their own records but fail to ensure their processors maintain Art. 30(2) records.
- Stale contact information: DPO or controller representative details are outdated following organisational restructuring.
- Vague purpose descriptions: Purposes are described at department level rather than per processing activity, failing to demonstrate purpose limitation under Art. 5(1)(b).
- Absent retention schedules: Retention periods recorded as "in accordance with policy" without specifying the actual duration or deletion criteria.
- Incomplete transfer documentation: International transfers recorded without specifying the safeguard mechanism (SCCs, adequacy decision, BCRs, or derogation relied upon).
- No security measure description: The Art. 30(1)(g) field left blank or containing only "encryption" without describing the broader organisational and technical measures in place.
Integration Points
- DPIA Register: Cross-reference RoPA entries flagged as high-risk with the Art. 35 DPIA register.
- Breach Log: Verify that processing activities involved in past breaches have updated security measures in their RoPA entries.
- Vendor Register: Validate that all processors listed in the RoPA have corresponding Art. 28 data processing agreements.
- Training Records: Confirm processing owners have completed required data protection training.
Performing GDPR Controller Self-Assessment
Overview
A controller self-assessment provides structured internal review of GDPR compliance using a standardised questionnaire with scoring, enabling organisations to identify strengths, weaknesses, and maturity trends.
Implementation Approach
Phase 1: Assessment
- Review current state against applicable GDPR articles.
- Identify gaps between current practices and requirements.
- Classify gaps by severity and regulatory risk.
- Document the assessment with evidence references.
Phase 2: Design
- Design measures to address identified gaps.
- Align measures with organisational capacity and risk appetite.
- Obtain DPO and stakeholder review of proposed measures.
- Create implementation timeline with milestones.
Phase 3: Implementation
- Execute the implementation plan according to priority.
- Document all measures implemented with evidence.
- Train relevant staff on new procedures and requirements.
- Validate implementation through testing or review.
Phase 4: Maintenance
- Schedule periodic reviews (minimum annual).
- Monitor for regulatory changes affecting the scope.
- Update measures in response to audit findings or incidents.
- Report on compliance status to the governance structure.
Managing Joint Controller Arrangements
Overview
Article 26 applies when two or more controllers jointly determine the purposes and means of processing. Joint controllers must enter into an arrangement that transparently determines their respective responsibilities for compliance, particularly regarding data subject rights and transparency obligations. The essence of the arrangement must be made available to data subjects.
Determining Joint Controllership
Joint controllership exists when two or more entities:
- Jointly determine the purposes — both entities influence why data is processed.
- Jointly determine the means — both entities influence how data is processed (essential means, not just technical implementation details).
Key Indicators
| Indicator | Points to Joint Controllership | Points Away |
|---|---|---|
| Shared decision on purpose | Both parties decide why data is processed | One party decides purpose; other merely executes |
| Shared platform | Both parties upload/access data on a common platform | One party hosts; other merely provides input |
| Shared dataset | Both parties contribute to and benefit from a combined dataset | One party processes only for the other's purpose |
| Mutual benefit | Both parties derive independent benefit from the processing | Only one party benefits; other is purely a service provider |
| Influence on means | Both parties have a say in essential aspects (what data, how long, who accesses) | One party determines all essential means; other party only implements |
CJEU Case Law Guidance
- Wirtschaftsakademie Schleswig-Holstein (C-210/16): A Facebook fan page admin is a joint controller with Facebook because the admin's creation of the page enables Facebook's processing and the admin benefits from visitor statistics.
- Jehovah's Witnesses (C-25/17): A religious community that organises door-to-door preaching and coordinates personal data collection by its members is a joint controller with those members.
- Fashion ID (C-40/17): A website embedding a Facebook Like button is a joint controller with Facebook for the collection and transmission of data triggered by the plugin.
Art. 26 Arrangement Requirements
The arrangement between joint controllers must determine in a transparent manner:
1. Respective Responsibilities
| Responsibility Area | Allocation Options |
|---|---|
| Lawful basis determination | Which controller is responsible for establishing and documenting the lawful basis |
| Privacy notices (Art. 13-14) | Which controller provides transparency information to data subjects |
| Data subject rights (Art. 15-22) | Which controller serves as the contact point and handles requests |
| Data security (Art. 32) | Which controller implements and maintains security measures |
| Breach notification (Art. 33-34) | Which controller notifies the supervisory authority and data subjects |
| DPIA (Art. 35) | Which controller conducts the DPIA |
| Records of processing (Art. 30) | How both controllers maintain their respective RoPA entries |
2. Contact Point for Data Subjects
The arrangement must designate a contact point for data subjects. Regardless of the arrangement, data subjects may exercise their rights against any of the joint controllers (Art. 26(3)).
3. Transparency
The essence of the arrangement must be made available to data subjects. This does not require publishing the full commercial agreement, but must cover:
- The identity of both joint controllers
- How responsibilities are divided
- How data subjects can exercise their rights
- The designated contact point
Arrangement Template Structure
A compliant Art. 26 arrangement should include:
- Parties and definitions: Legal entity names, registered addresses, roles.
- Scope of joint processing: Specific processing activities covered, personal data categories, data subject categories.
- Purpose determination: How purposes are jointly determined and what each party's interest is.
- Means determination: Which essential means each party determines (data elements, retention, access, security standards).
- Responsibilities allocation: Detailed allocation per the table above.
- Data subject rights: Designated contact point, handling procedures, cooperation obligations.
- Transparency: How the essence of the arrangement is communicated to data subjects.
- Security obligations: Minimum security standards each party commits to.
- Breach management: Notification obligations between the parties and to authorities/data subjects.
- Liability: Internal allocation of liability (note: external liability to data subjects is joint and several per Art. 82(4)-(5)).
- Term and termination: Duration, exit provisions, and data handling upon termination.
Practical Considerations
Joint and Several Liability
Under Art. 82(4), each joint controller is liable for the entire damage caused by processing that infringes the GDPR. A joint controller may be exempted from liability under Art. 82(3) only if it proves it is not responsible for the event giving rise to the damage. Internal liability allocation in the arrangement does not affect the data subject's right to claim against either controller.
Supervisory Authority Actions
Under Art. 26(3), data subjects can exercise their rights against each and any of the joint controllers regardless of the arrangement. The supervisory authority may also investigate any joint controller for the full scope of joint processing.
Relationship with Art. 28
Joint controllership and the controller-processor relationship are mutually exclusive for a given processing activity. If Entity A determines purposes and means and Entity B merely processes on A's instructions, the relationship is controller-processor (Art. 28). If both determine purposes and means, the relationship is joint controllership (Art. 26).
Implementing Lawful Basis Assessment
Overview
Every processing activity under GDPR must have a valid lawful basis established before processing begins. Article 6(1) provides six mutually non-exclusive bases. Selecting the wrong basis creates compliance risk, may invalidate the processing entirely, and can result in enforcement action. This skill provides a systematic methodology for evaluating and documenting the appropriate lawful basis.
The Six Lawful Bases — Art. 6(1)
(a) Consent
The data subject has given consent to the processing of their personal data for one or more specific purposes.
Requirements per Art. 7 and Recital 32:
- Freely given: genuine choice, no imbalance of power, no conditionality (Art. 7(4))
- Specific: granular consent for distinct processing purposes
- Informed: clear plain language about identity, purpose, data types, rights
- Unambiguous: clear affirmative action (no pre-ticked boxes, no silence)
- Withdrawable: as easy to withdraw as to give (Art. 7(3))
Best suited for: Marketing communications, cookies/tracking, research participation, sharing data with third parties for their own purposes.
Not appropriate when: There is a power imbalance (employer-employee, public authority-citizen), processing is necessary for another basis, or withdrawal would be impractical.
(b) Contract Performance
Processing is necessary for the performance of a contract to which the data subject is party, or to take steps at the data subject's request prior to entering into a contract.
Key test: Would the contract be impossible to perform without this specific processing? The processing must be objectively necessary, not merely useful or standard practice.
Best suited for: Delivering purchased goods, processing payments, providing contracted services, pre-contractual enquiries at the data subject's request.
Not appropriate when: Processing is useful but not necessary for the contract (e.g., profiling customers is not necessary to deliver their order).
(c) Legal Obligation
Processing is necessary for compliance with a legal obligation to which the controller is subject.
Requirements:
- The obligation must be laid down by EU or Member State law (not contractual obligations)
- The law must be sufficiently clear about the processing required
- The processing must be limited to what is necessary to comply
Best suited for: Tax reporting, employment law obligations, anti-money laundering checks, regulatory reporting, court orders.
(d) Vital Interests
Processing is necessary to protect the vital interests of the data subject or of another natural person.
Requirements:
- Relates to life-or-death situations or serious medical emergencies
- Cannot be used if another lawful basis is available (Recital 46)
- Very narrow scope in practice
Best suited for: Emergency medical treatment for unconscious patients, disaster response, humanitarian crises.
(e) Public Task
Processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.
Requirements:
- Must have a basis in EU or Member State law
- The specific task or function must be defined in law
- Primarily applies to public authorities and bodies
Best suited for: Public administration, law enforcement, statutory functions of public bodies, public health monitoring.
(f) Legitimate Interests
Processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject.
Requirements (three-part test):
- Purpose test: Is there a legitimate interest? (commercial, societal, or individual)
- Necessity test: Is the processing necessary for that interest? (no less intrusive alternative)
- Balancing test: Do the data subject's interests override the controller's?
Best suited for: Fraud prevention, network security, direct marketing to existing customers, intra-group administrative transfers, internal analytics.
Not available to: Public authorities in the performance of their tasks (Art. 6(1) final paragraph).
Decision Tree for Lawful Basis Selection
Step 1: Is the processing required by law?
- YES → Art. 6(1)(c) Legal Obligation. Identify the specific law and provision.
- NO → Proceed to Step 2.
Step 2: Is the processing necessary to perform a contract with the data subject?
- YES → Art. 6(1)(b) Contract Performance. Verify objective necessity (not just convenience).
- NO → Proceed to Step 3.
Step 3: Is this a life-threatening or medical emergency?
- YES → Art. 6(1)(d) Vital Interests. Document why no other basis applies.
- NO → Proceed to Step 4.
Step 4: Is the controller a public authority performing a statutory function?
- YES → Art. 6(1)(e) Public Task. Identify the legal basis for the task.
- NO → Proceed to Step 5.
Step 5: Does the controller have a legitimate interest that requires this processing?
- YES → Conduct a Legitimate Interest Assessment (three-part test).
- If the LIA concludes the controller's interest is not overridden → Art. 6(1)(f).
- If the LIA concludes the data subject's rights prevail → Consider consent or do not process.
- NO → Proceed to Step 6.
Step 6: Can the data subject provide valid consent?
- Verify: no power imbalance, genuine choice, specific purpose, can withdraw without detriment.
- YES → Art. 6(1)(a) Consent. Implement compliant consent mechanism.
- NO → Processing may not have a valid lawful basis. Do not proceed. Consult the DPO.
Documentation Requirements
For each processing activity, document:
- Processing activity name and RoPA reference: Link to the Art. 30 record.
- Selected lawful basis: Cite the specific Art. 6(1) paragraph.
- Rationale: Explain why this basis was selected and why alternatives were rejected.
- Necessity analysis: Demonstrate why the processing is necessary for the stated basis (not merely useful).
- Supporting evidence: Reference the specific law (for legal obligation), contract (for contract performance), LIA (for legitimate interest), or consent mechanism (for consent).
- Special category data: If Art. 9 data is involved, identify the additional Art. 9(2) condition.
- Criminal offence data: If Art. 10 data is involved, confirm the specific authorisation in EU/Member State law.
- Review date: Set the next review date (recommended: annually or upon material change).
Common Assessment Errors
- Defaulting to consent: Using consent when another basis is more appropriate, creating unnecessary withdrawal risk.
- Stretching contract performance: Claiming processing is necessary for a contract when it is merely beneficial (e.g., profiling for cross-selling is not necessary to fulfil a purchase order).
- Citing non-existent legal obligations: Referencing industry standards or contractual requirements as "legal obligations" when they do not constitute EU or Member State law.
- Ignoring the necessity test: Selecting a basis without demonstrating that the specific processing is necessary (not just the purpose).
- Switching bases post-hoc: Changing the lawful basis after processing has begun when the original basis fails, without valid justification.
- Overlooking power imbalances: Relying on employee consent for workplace processing where genuine free choice is absent.
Integration with Other GDPR Requirements
- Transparency (Art. 13/14): The lawful basis must be communicated to data subjects in the privacy notice.
- Data subject rights: The lawful basis determines which rights are available (e.g., right to erasure is limited where legal obligation applies; right to data portability only applies to consent and contract).
- RoPA (Art. 30): The lawful basis should be recorded alongside each processing activity.
- DPIA (Art. 35): High-risk processing may require a DPIA regardless of which lawful basis is selected.
Performing Legitimate Interest Assessment
Overview
When a controller relies on Art. 6(1)(f) as the lawful basis for processing, a Legitimate Interest Assessment (LIA) must be conducted and documented before processing begins. The LIA consists of three sequential tests derived from the wording of Art. 6(1)(f) and elaborated in WP29 Opinion 06/2014. If any test fails, legitimate interest cannot be relied upon, and an alternative lawful basis must be found or processing must not proceed.
Part 1: Purpose Test
The purpose test establishes whether the controller (or a third party) has a legitimate interest that is real, lawful, and clearly articulated.
Assessment Criteria
-
Identify the interest: What specific interest does the controller or third party pursue? The interest must be concrete and articulated, not vague or hypothetical.
-
Verify legitimacy: The interest must be:
- Lawful (not prohibited by any law)
- Sufficiently specific to be assessed
- Real and present (not speculative or future)
- Consistent with what data subjects would reasonably expect
-
Common legitimate interests recognised by the GDPR:
- Fraud prevention (Recital 47)
- Direct marketing to existing customers (Recital 47)
- Network and information security (Recital 49)
- Intra-group transfers for internal administrative purposes (Recital 48)
- Reporting possible criminal acts or threats to public security (Recital 50)
-
Document the interest: State the interest in a single clear sentence that could be understood by a non-expert.
Purpose Test Outcome
- PASS: A legitimate interest has been clearly identified and is lawful.
- FAIL: No legitimate interest can be articulated, or the interest is prohibited by law. Stop the assessment — Art. 6(1)(f) cannot be relied upon.
Part 2: Necessity Test
The necessity test determines whether the specific processing is necessary to achieve the identified legitimate interest. This is not a test of whether the interest itself is necessary, but whether the processing is necessary for the interest.
Assessment Criteria
-
Could the interest be achieved without processing personal data? If the same outcome can be reached without personal data, the processing fails the necessity test.
-
Could the interest be achieved with less personal data? Apply data minimisation — only the minimum data necessary should be processed.
-
Could the interest be achieved with a less intrusive method? Consider alternatives:
- Anonymisation or aggregation instead of identifiable data
- Pseudonymisation to reduce impact
- Shorter retention periods
- More limited sharing
- Technical restrictions on access
-
Is the processing proportionate to the interest? The scope and intensity of processing should be proportionate to the significance of the interest.
Necessity Test Outcome
- PASS: The processing is necessary for the legitimate interest, no less intrusive alternative achieves the same result, and the scope is proportionate.
- FAIL: A less intrusive alternative exists, or the processing scope exceeds what is necessary. Modify the processing to meet the necessity test, or stop — Art. 6(1)(f) cannot be relied upon.
Part 3: Balancing Test
The balancing test weighs the controller's legitimate interest against the interests, fundamental rights, and freedoms of data subjects. This is the most complex and contextual part of the LIA.
Factors Favouring the Controller
- The interest is strong and compelling (e.g., fraud prevention, security)
- Processing has minimal impact on data subjects
- Data subjects would reasonably expect the processing
- There is an existing relationship between controller and data subject
- Robust safeguards are in place (pseudonymisation, encryption, access controls)
- Data subjects have an easy and effective opt-out mechanism
- Processing uses non-sensitive data
- Data is not shared with third parties
- The controller is transparent about the processing
Factors Favouring the Data Subject
- Special category or sensitive data is involved (even if not Art. 9 data, sensitivity matters)
- Data subjects are vulnerable (children, employees, patients, elderly)
- Processing has significant impact on data subjects (profiling, automated decisions, financial consequences)
- Data subjects would not reasonably expect the processing
- There is no direct relationship between controller and data subject
- Data is shared widely or with third parties
- Processing involves large-scale monitoring or tracking
- No opt-out mechanism is provided
- Data is combined from multiple sources to create profiles
Balancing Methodology
-
Assess the nature of the interest: How important is the controller's interest? Rate from routine (low) to essential (high).
-
Assess the impact on data subjects: What is the likely effect? Consider:
- Physical, material, or financial harm
- Social disadvantage or discrimination
- Loss of control over personal data
- Reputational effects
- Psychological impact
-
Consider reasonable expectations: Would data subjects expect their data to be used this way? The closer the processing is to the original context and the existing relationship, the more likely it meets expectations.
-
Evaluate additional safeguards: Do safeguards sufficiently mitigate the impact? Effective safeguards can tip the balance in the controller's favour.
-
Consider the possibility of objection: Is there a mechanism for data subjects to object under Art. 21? The right to object is a mandatory counterbalance when relying on Art. 6(1)(f).
Balancing Test Outcome
- PASS: The controller's legitimate interest is not overridden by the data subject's interests, rights, and freedoms, taking into account all relevant factors and safeguards.
- FAIL: The data subject's rights outweigh the controller's interest. Consider additional safeguards that could tip the balance, or use a different lawful basis (typically consent), or do not process.
Documentation Requirements
The completed LIA must document:
- Assessment metadata: Date, assessor, processing activity, RoPA reference.
- Purpose test: The identified interest, evidence of legitimacy, outcome.
- Necessity test: Analysis of alternatives, proportionality, outcome.
- Balancing test: Factors considered, weighting rationale, safeguards, outcome.
- Overall conclusion: Whether Art. 6(1)(f) can be relied upon.
- Safeguards committed: Specific measures to mitigate data subject impact.
- Right to object: How the Art. 21 right to object is facilitated.
- Review schedule: When the LIA will be reassessed.
Reassessment Triggers
- Material change in processing scope, purpose, or data categories
- Change in the relationship with data subjects
- New technology or methodology introduced
- Supervisory authority guidance or enforcement action relevant to the processing
- Data subject complaints challenging the legitimate interest basis
- Periodic review (minimum annual)
Sponsors
Details
- Marketplace
- mukul975/Privacy-Data-Protection-Skills
- Source
- plugins/gdpr-compliance-skills
- Author
- Mahipal
- Category
- Compliance
- License
- Apache-2.0
- Keywords
- gdpr, compliance, audit, dpo, certification
More from mukul975/Privacy-Data-Protection-Skills
All 21- global-privacy-regulations-skillsv1.0.0
- healthcare-privacy-skillsv1.0.0
- privacy-audit-skillsv1.0.0
- privacy-by-design-skillsv1.0.0
- privacy-engineering-skillsv1.0.0
- privacy-impact-assessment-skillsv1.0.0
- privacy-skills-completev1.0.0
- records-of-processing-skillsv1.0.0
- us-state-privacy-skillsv1.0.0
- vendor-privacy-management-skillsv1.0.0
- ai-privacy-governance-skillsv1.0.0
- children-privacy-skillsv1.0.0
- consent-management-skillsv1.0.0
- cookie-consent-skillsv1.0.0
- cross-border-transfers-skillsv1.0.0
- data-breach-response-skillsv1.0.0
- data-classification-skillsv1.0.0
- data-retention-skillsv1.0.0
- data-subject-rights-skillsv1.0.0
- employee-privacy-skillsv1.0.0