From lawvable-awesome-legal-skills
Guides GDPR Article 35 DPIA assessments with threshold checks, risk catalogs, mitigations, multi-jurisdictional SA lists, and document generation.
npx claudepluginhub joshuarweaver/cascade-business-ops --plugin lawvable-awesome-legal-skillsThis skill uses the workspace's default tool permissions.
> **Important:** This provides structured GDPR Article 35 guidance based on EDPB Guidelines and national SA requirements. It is not legal advice. Involve your DPO (Art. 35(2)) and qualified counsel for final decisions.
LICENSE.txtREADME.mdreferences/edpb-criteria.mdreferences/jurisdictions/be-apd.mdreferences/jurisdictions/de-dsk.mdreferences/jurisdictions/fr-cnil.mdreferences/jurisdictions/ie-dpc.mdreferences/jurisdictions/it-garante.mdreferences/jurisdictions/nl-ap.mdreferences/jurisdictions/pl-uodo.mdreferences/jurisdictions/whitelists.mdreferences/risk-catalog.mdreferences/scoring.mdreferences/sources.mdreferences/templates.mdCreates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Important: This provides structured GDPR Article 35 guidance based on EDPB Guidelines and national SA requirements. It is not legal advice. Involve your DPO (Art. 35(2)) and qualified counsel for final decisions.
Determine what the user needs and load references accordingly:
| User Need | Load These References | Action |
|---|---|---|
| "Do I need a DPIA?" / threshold question | references/edpb-criteria.md + relevant jurisdiction file(s) | Run threshold assessment |
| Full DPIA | edpb-criteria.md + jurisdiction(s) + references/risk-catalog.md + scoring.md | Walk through assessment phases |
| Document generation (.docx) | references/templates.md + docx generation skill (/mnt/skills/public/docx/SKILL.md in Claude.ai Projects, or docx-processing-anthropic skill in Claude Code; if unavailable, generate well-formatted Markdown as fallback) | Generate Word document |
| Specific legal question | Load relevant reference only | Answer directly |
Jurisdiction selection: Ask two questions: (1) Where is the controller's main establishment? (2) Where are the data subjects located? Load all jurisdiction files that are relevant — this may be multiple files for multi-jurisdictional processing. See references/edpb-criteria.md → "Multi-Jurisdictional DPIA Analysis" for the full decision framework.
Available jurisdiction files:
references/jurisdictions/de-dsk.md — Germanyreferences/jurisdictions/fr-cnil.md — Francereferences/jurisdictions/ie-dpc.md — Irelandreferences/jurisdictions/be-apd.md — Belgiumreferences/jurisdictions/nl-ap.md — Netherlandsreferences/jurisdictions/it-garante.md — Italyreferences/jurisdictions/pl-uodo.md — Polandreferences/jurisdictions/whitelists.md — France, Czech Republic, Spain, AustriaFor jurisdictions not covered by a dedicated file, rely on the EDPB nine-criteria analysis in references/edpb-criteria.md and note that the user should check their national SA's Art. 35(4) list directly.
Threshold → Description → Necessity/Proportionality → Risks → Mitigations → Residual Risk → Art. 36 Check → Documentation
This is the logical sequence, not a rigid script. Adapt to the user: if they provide rich context upfront, skip intake questions. If they're experienced, move faster. If they're new to DPIAs, explain more.
The assessment is iterative: if mitigations in later stages change the processing design, revisit earlier analysis and flag this to the user.
These are areas where Claude's training knowledge may be imprecise. Always apply these rules:
Art. 35(3) triggers are absolute. If any of the three mandatory cases apply (systematic extensive automated evaluation with legal/significant effect; large-scale special category/criminal data; systematic monitoring of publicly accessible areas on large scale), a DPIA is required — no balancing, no judgment call.
The two-criteria rule is a presumption, not a mandate. Meeting 2+ of the 9 EDPB criteria creates a strong presumption a DPIA is needed. But a DPIA may be needed with only 1 criterion, and may be justified as unnecessary with 2 — if thoroughly documented. See WP 248 rev.01, p. 11.
Art. 9 is cumulative with Art. 6. Special category data always needs BOTH a legal basis under Art. 6 AND an exception under Art. 9(2). These are separate legal hurdles.
"Large scale" has no fixed number. The EDPB uses four factors: number of subjects, data volume, duration, geographic extent. An individual doctor is not large scale; a regional hospital is. Never cite a specific numerical threshold.
National blacklists are additive, not exhaustive. Processing not on a blacklist may still require a DPIA. A blacklist entry in the relevant jurisdiction overrides whitelist exemptions from other jurisdictions.
Multi-jurisdictional processing requires checking ALL relevant blacklists. Art. 35(4) lists are territorial — the DPIA obligation is triggered if the processing matches a blacklist in ANY jurisdiction where the controller is established OR where data subjects are located. The one-stop-shop mechanism (Art. 56) governs enforcement jurisdiction, but it does NOT limit which Art. 35(4) lists apply to the DPIA obligation itself. A single DPIA can address multiple jurisdictions, but the threshold analysis must run against each applicable national list. See references/edpb-criteria.md → "Multi-Jurisdictional DPIA Analysis" for details.
DPIA must happen before processing begins (Art. 35(1)). It is a pre-processing obligation, not a retroactive compliance exercise. If processing has already started, the DPIA should still be done but note this as a compliance gap.
AI requires dual-phase analysis (EDPB Opinion 28/2024). Training and deployment are separate processing activities with distinct risk profiles. A deployer cannot simply rely on the model provider's DPIA.
Art. 36 prior consultation is sequential to the DPIA, not part of it. The DPIA identifies residual risk; if that risk remains high after all feasible mitigations, Art. 36 requires consulting the SA before processing begins. The SA has 8 weeks (extendable by 6).
Pseudonymization as risk reducer (EDPB Guidelines 01/2025 on Pseudonymisation, adopted 17 January 2025): Effective pseudonymization with technically separated additional information can meaningfully reduce likelihood scores in risk assessment. But it must be genuine — if re-identification is trivial, it doesn't reduce risk.
Risk assessment is from the data subject's perspective. A DPIA assesses risks to rights and freedoms of natural persons (Recital 75), not corporate/business risks. Identity theft risk to the individual, not reputational risk to the company.
AI Act FRIA is distinct from DPIA. For high-risk AI systems under the AI Act, a Fundamental Rights Impact Assessment (FRIA) may also be required. DPIA (data protection risks) and FRIA (broader fundamental rights) are complementary — one does not replace the other.
Threshold result: Present a clear verdict (DPIA Required / Recommended / Not Required) with the reasoning showing Art. 35(3) check, criteria analysis, and national list check.
Risk register: Table with Risk ID, Description, Rights Category, Likelihood (1-5), Severity (1-5), Score, Level. Use the scoring methodology in references/scoring.md.
Residual risk overview: Summary showing total risks by level before and after mitigation, plus overall position (Acceptable / Acceptable with Conditions / Art. 36 Consultation Required).
Documents: Generate .docx files following references/templates.md. Always read the docx skill first.