Gdpr Dsgvo Expert

GDPR/DSGVO Expert

Tools and guidance for EU General Data Protection Regulation (GDPR) and German Bundesdatenschutzgesetz (BDSG) compliance.

Table of Contents

• Tools
  • GDPR Compliance Checker
  • DPIA Generator
  • Data Subject Rights Tracker
• Reference Guides
• Workflows

Tools

GDPR Compliance Checker

Scans codebases for potential GDPR compliance issues including personal data patterns and risky code practices.

# Scan a project directory
python scripts/gdpr_compliance_checker.py /path/to/project

# JSON output for CI/CD integration
python scripts/gdpr_compliance_checker.py . --json --output report.json

Detects:

• Personal data patterns (email, phone, IP addresses)
• Special category data (health, biometric, religion)
• Financial data (credit cards, IBAN)
• Risky code patterns:
  • Logging personal data
  • Missing consent mechanisms
  • Indefinite data retention
  • Unencrypted sensitive data
  • Disabled deletion functionality

Output:

• Compliance score (0-100)
• Risk categorization (critical, high, medium)
• Prioritized recommendations with GDPR article references

DPIA Generator

Generates Data Protection Impact Assessment documentation following Art. 35 requirements.

# Get input template
python scripts/dpia_generator.py --template > input.json

# Generate DPIA report
python scripts/dpia_generator.py --input input.json --output dpia_report.md

Features:

• Automatic DPIA threshold assessment
• Risk identification based on processing characteristics
• Legal basis requirements documentation
• Mitigation recommendations
• Markdown report generation

DPIA Triggers Assessed:

• Systematic monitoring (Art. 35(3)(c))
• Large-scale special category data (Art. 35(3)(b))
• Automated decision-making (Art. 35(3)(a))
• WP29 high-risk criteria

Data Subject Rights Tracker

Manages data subject rights requests under GDPR Articles 15-22.

# Add new request
python scripts/data_subject_rights_tracker.py add \
  --type access --subject "John Doe" --email "john@example.com"

# List all requests
python scripts/data_subject_rights_tracker.py list

# Update status
python scripts/data_subject_rights_tracker.py status --id DSR-202601-0001 --update verified

# Generate compliance report
python scripts/data_subject_rights_tracker.py report --output compliance.json

# Generate response template
python scripts/data_subject_rights_tracker.py template --id DSR-202601-0001

Supported Rights:

Features:

• Deadline tracking with overdue alerts
• Identity verification workflow
• Response template generation
• Compliance reporting

Reference Guides

GDPR Compliance Guide

references/gdpr_compliance_guide.md

Comprehensive implementation guidance covering:

• Legal bases for processing (Art. 6)
• Special category requirements (Art. 9)
• Data subject rights implementation
• Accountability requirements (Art. 30)
• International transfers (Chapter V)
• Breach notification (Art. 33-34)

German BDSG Requirements

references/german_bdsg_requirements.md

German-specific requirements including:

• DPO appointment threshold (§ 38 BDSG - 20+ employees)
• Employment data processing (§ 26 BDSG)
• Video surveillance rules (§ 4 BDSG)
• Credit scoring requirements (§ 31 BDSG)
• State data protection laws (Landesdatenschutzgesetze)
• Works council co-determination rights

DPIA Methodology

references/dpia_methodology.md

Step-by-step DPIA process:

• Threshold assessment criteria
• WP29 high-risk indicators
• Risk assessment methodology
• Mitigation measure categories
• DPO and supervisory authority consultation
• Templates and checklists

Workflows

Workflow 1: New Processing Activity Assessment

Step 1: Run compliance checker on codebase
        → python scripts/gdpr_compliance_checker.py /path/to/code

Step 2: Review findings and compliance score
        → Address critical and high issues

Step 3: Determine if DPIA required
        → Check references/dpia_methodology.md threshold criteria

Step 4: If DPIA required, generate assessment
        → python scripts/dpia_generator.py --template > input.json
        → Fill in processing details
        → python scripts/dpia_generator.py --input input.json --output dpia.md

Step 5: Document in records of processing activities

Workflow 2: Data Subject Request Handling

Step 1: Log request in tracker
        → python scripts/data_subject_rights_tracker.py add --type [type] ...

Step 2: Verify identity (proportionate measures)
        → python scripts/data_subject_rights_tracker.py status --id [ID] --update verified

Step 3: Gather data from systems
        → python scripts/data_subject_rights_tracker.py status --id [ID] --update in_progress

Step 4: Generate response
        → python scripts/data_subject_rights_tracker.py template --id [ID]

Step 5: Send response and complete
        → python scripts/data_subject_rights_tracker.py status --id [ID] --update completed

Step 6: Monitor compliance
        → python scripts/data_subject_rights_tracker.py report

Workflow 3: German BDSG Compliance Check

Step 1: Determine if DPO required
        → 20+ employees processing personal data automatically
        → OR processing requires DPIA
        → OR business involves data transfer/market research

Step 2: If employees involved, review § 26 BDSG
        → Document legal basis for employee data
        → Check works council requirements

Step 3: If video surveillance, comply with § 4 BDSG
        → Install signage
        → Document necessity
        → Limit retention

Step 4: Register DPO with supervisory authority
        → See references/german_bdsg_requirements.md for authority list

Key GDPR Concepts

Legal Bases (Art. 6)

• Consent: Marketing, newsletters, analytics (must be freely given, specific, informed)
• Contract: Order fulfillment, service delivery
• Legal obligation: Tax records, employment law
• Legitimate interests: Fraud prevention, security (requires balancing test)

Special Category Data (Art. 9)

Requires explicit consent or Art. 9(2) exception:

• Health data
• Biometric data
• Racial/ethnic origin
• Political opinions
• Religious beliefs
• Trade union membership
• Genetic data
• Sexual orientation

Data Subject Rights

All rights must be fulfilled within 30 days (extendable to 90 for complex requests):

• Access: Provide copy of data and processing information
• Rectification: Correct inaccurate data
• Erasure: Delete data (with exceptions for legal obligations)
• Restriction: Limit processing while issues are resolved
• Portability: Provide data in machine-readable format
• Object: Stop processing based on legitimate interests

German BDSG Additions

Cross-Reference: CCPA/CPRA US Privacy Comparison

When operating across EU and US jurisdictions, align GDPR compliance with California Consumer Privacy Act (CCPA) as amended by CPRA. Key differences to manage:

Practical alignment: Build a unified privacy program that satisfies the stricter GDPR requirements by default, then layer CCPA/CPRA-specific mechanisms (e.g., "Do Not Sell or Share My Personal Information" link, annual metrics disclosure).

See also: ../ccpa-cpra-specialist/SKILL.md for full CCPA/CPRA compliance workflows and tools.

Infrastructure Privacy Controls

Cookie Consent and Tracking

Implement compliant cookie consent per GDPR Art. 6 + ePrivacy Directive:

Implementation requirements:

• Banner must block all non-essential cookies until explicit consent
• Pre-checked boxes are NOT valid consent (Planet49 ruling, CJEU C-673/17)
• Consent must be as easy to withdraw as to give
• Record consent proof (timestamp, version, choices made)
• Re-consent on material changes to cookie policy

Global Privacy Control (GPC) Signal

Per CCPA/CPRA regulations and emerging EU guidance:

• Detect Sec-GPC: 1 HTTP header and navigator.globalPrivacyControl JavaScript API
• Treat GPC as valid opt-out signal for CCPA/CPRA
• For GDPR: GPC can serve as a signal of objection under Art. 21 — evaluate on a case-by-case basis
• Log GPC signal detection and honor it automatically

Data Localization and Cross-Border Transfers

Transfer Impact Assessment (TIA) requirements for SCCs:

1. Map the data flow (what data, to whom, where)
2. Assess recipient country legal framework (surveillance laws, access by authorities)
3. Evaluate supplementary measures needed (encryption, pseudonymization, contractual)
4. Document assessment and review annually

AI-Specific GDPR Requirements

Automated Decision-Making (Art. 22)

Art. 22 restricts decisions based solely on automated processing that produce legal or similarly significant effects:

AI transparency checklist:

• Document algorithmic logic in plain language
• Implement human-in-the-loop for high-stakes decisions (credit, employment, insurance)
• Provide opt-out mechanism for fully automated decisions
• Conduct and document bias testing (protected characteristics under Art. 9)
• Log all automated decisions with reasoning for auditability
• Include AI decision-making in privacy notice (Art. 13(2)(f), Art. 14(2)(g))

AI Training Data Requirements

Enhanced DPIA Methodology with EU AI Act Integration

When DPIA + AI Act Conformity Assessment Overlap

For AI systems processing personal data, both GDPR Art. 35 DPIA and EU AI Act conformity assessment may apply:

Enhanced DPIA Process for AI Systems

Step 1: AI System Classification
        → Classify under EU AI Act risk levels
        → Map to GDPR Art. 35(3) triggers

Step 2: Data Flow and Processing Analysis
        → Document training data sources and legal basis
        → Map inference data flows
        → Identify automated decision points (Art. 22)

Step 3: AI-Specific Risk Assessment
        → Bias and discrimination risk (protected groups)
        → Accuracy and reliability risk
        → Explainability and transparency gaps
        → Data quality and representativeness
        → Model drift and ongoing monitoring needs

Step 4: Fundamental Rights Impact
        → Right to non-discrimination
        → Right to privacy and data protection
        → Freedom of expression (content moderation AI)
        → Right to an effective remedy

Step 5: Combined Mitigation Measures
        → Technical: differential privacy, federated learning, model cards
        → Organizational: AI ethics board, human oversight procedures
        → Contractual: AI-specific DPA clauses with processors
        → Monitoring: continuous bias monitoring, performance drift detection

Step 6: DPO and Supervisory Authority Consultation
        → Consult DPO on combined assessment
        → Prior consultation with SA if high residual risk (Art. 36)
        → Notify national AI authority if high-risk AI system

Privacy by Design Technical Controls

Data Minimization Techniques

Pseudonymization Implementation (Recital 26, Art. 4(5))

Key management for pseudonymization:

• Store re-identification keys separately from pseudonymized data
• Apply strict access controls to key material (minimum two-person rule)
• Document key rotation schedule
• Log all re-identification events

Encryption Standards

Cross-Framework Privacy Mapping

Cross-references: See ../information-security-manager-iso27001/SKILL.md for ISO 27001 security controls, and ../mdr-745-specialist/SKILL.md for healthcare device data protection under MDR.

Cross-Framework Privacy Integration

GDPR ↔ CCPA/CPRA Comparison

AI-Specific GDPR Requirements

• Automated Decision-Making (Art. 22): Right not to be subject to decisions based solely on automated processing with legal/significant effects
• AI Training Data: Legitimate interest or consent required; purpose limitation applies to model training
• Profiling: Requires explicit consent for automated profiling with significant effects
• EU AI Act Integration: High-risk AI systems processing personal data require DPIA per Art. 35 GDPR
• Cross-reference: See eu-ai-act-specialist for AI-specific compliance

Infrastructure Privacy Controls

• Cookie Consent: TCF 2.2 compliant consent management platform (CMP)
• Global Privacy Control (GPC): Must honor GPC browser signals (also CCPA requirement)
• Data Localization: EU data residency requirements, Schrems II adequacy decisions
• Cross-Border Transfers: Standard Contractual Clauses (SCCs), adequacy decisions, binding corporate rules
• Privacy by Design Controls: Data minimization, pseudonymization, encryption at rest/transit, access logging