Data Protection Monitor
Global Privacy & Data Protection Intelligence

Germany Data Protection & Privacy Regulation

DE schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 86 claims · 71 sources in the cumulative register

Germany's federal data protection authority closed out a high-intensity enforcement stretch while confirming a leadership succession that will steer the regulator through the remainder of 2026.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Enforcement & Redress (3 open gaps).

Framework & posture10 of 10 modules active
10 active · 12 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix91 claims · 55 sources · machine-compiled
12 Confirmed68 Probable6 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Law made at European Economic Area (Bloc) level that applies in Germany is covered once, on the European Economic Area (Bloc) page. This page covers Germany’s own layer: implementation, national authorities, national options and local enforcement.

Jurisdiction brief

Latest update · 18 October 2026

Lead Signal

Germany's data-protection-adjacent regulatory environment moved on two structural fronts this cycle. First, the KI-MIG (Gesetz zur Durchführung der KI-Verordnung), promulgated in BGBl. 2026 I Nr. 233 on 28 July 2026 and in force from 29 July 2026, names the Bundesnetzagentur as the central AI market-surveillance and complaints authority for compliance with the EU AI Regulation, except where a sectoral regulator applies. The same instrument establishes, under its Article 20, a non-public register of certain high-risk AI systems maintained by the Bundesnetzagentur and mandates at least one AI regulatory sandbox. This is a significant piece of institutional architecture: Germany now has a named, central AI supervisory authority operating alongside the existing federated data-protection authority structure, in which the BfDI itself does not supervise private-sector GDPR compliance nationally, each of the sixteen Länder instead maintaining its own data-protection authority for private-sector processing.

Key regulatory facts for Germany
Key regulatory facts for Germany
Regulatory DimensionGermany Standing Position
JurisdictionGermany (DE)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 86 sourced findings)
Regulator & FrameworkComprehensive, mature, directly-applicable EU omnibus regime with a stable national implementing act; only amber-adjacent risk is the ongoing BfDI leadership transition and EU Digital Omnibus reform uncertainty.
Lawful Processing & Special DataCore GDPR bases are firmly in force (green), but §26 BDSG's acknowledged normative imprecision on special-category employee data and the absence of a dedicated Employee Data Protection Act create interpretive uncertainty, justifying an amber rating for this module overall.
Data Subject RightsDirectly-applicable EU rights regime with detailed, current BfDI operational guidance; only narrow, well-defined statutory exceptions exist.
Controller/Processor DutiesRobust, CJEU-tested accountability framework with clear national thresholds and multiple layered breach-notification regimes; no material gaps identified.
Primary Instruments Citedeco - Association of the Internet Industry, BfDI, EUR-Lex / CJEU, EUR-Lex / European Commission, European Commission
Last Confirmed / Updated (71 sources in cumulative register)

#

Comprehensive, mature, directly-applicable EU omnibus regime with a stable national implementing act; only amber-adjacent risk is the ongoing BfDI leadership transition and EU Digital Omnibus reform uncertainty.

Primary frameworkRegulation (EU) 2016/679 (GDPR) as implemented and supplemented by the Bundesdatenschutzgesetz (BDSG-neu)
Traffic-light rationale — GreenComprehensive, mature, directly-applicable EU omnibus regime with a stable national implementing act; only amber-adjacent risk is the ongoing BfDI leadership transition and EU Digital Omnibus reform uncertainty.

Sub-modules (5)

Regulator and authorityGreen

BfDI supervises federal public bodies and federally-regulated private-sector entities (post, telecoms); 17 Land DPAs supervise private-sector and Land-level public bodies.

Claims (6):

  • BfDI supervises federal public bodies and federally-regulated private-sector entities (post and telecoms sectors). Core supervisory-competence allocation.
  • 17 Land data protection authorities supervise private-sector processing and Land-level public bodies (Bavaria splits public/private-sector oversight). Federated supervisory structure.
  • BfDI requires: Prof. Dr. Moritz Hennemann took office as Federal Commissioner for Data Protection and Freedom of Information on 1 October 2026, succeeding Prof. Dr. Louisa Specht-Riemenschneider, after election by the Bundestag (June 2026) and appointment by Federal President Frank-Walter Steinmeier (29 September 2026).
  • BfDI (Hennemann priorities) proposes: Commentary frames Hennemann's priorities as including a planned reform of Germany's data-protection supervisory structure consolidating the federal/Laender 17-body system, and a prospective 'Data Code'; neither has produced enacted legislative text as of this cycle.
  • BfDI does not supervise private-sector GDPR compliance nationally; each of the 16 Länder has its own DPA for private-sector processing.
  • BfDI — Moritz Hennemann became Bundesbeauftragter für den Datenschutz und die Informationsfreiheit on 1 October 2026, succeeding Louisa Specht-Riemenschneider who resigned for health reasons; elected by the Bundestag June 2026, appointed by Bundespräsident Steinmeier on 29 September 2026

Act and instrumentsGreen

BDSG-neu is the national GDPR implementing act; TTDSG is lex specialis for telecom/telemedia and cookies.

Claims (3):

  • Bundesdatenschutzgesetz (BDSG-neu) supplements the GDPR as a subsidiary national implementing act, applying only where the GDPR permits derogation or leaves gaps.
  • TTDSG (now TDDDG) functions as lex specialis for telecom/telemedia and cookie/tracking consent matters. TTDSG renamed TDDDG following Digital Services Act adaptation.
  • Germany's KI-MIG (Gesetz zur Durchführung der KI-Verordnung), promulgated in BGBl. 2026 I Nr. 233 on 28 July 2026, entered into force 29 July 2026, naming the Bundesnetzagentur as the central AI market-surveillance and complaints authority except where a sectoral regulator applies.

Material scopeGreen

GDPR Art 2 material scope covers wholly/partly automated processing and structured manual filing systems, directly applicable in Germany.

Claims (1):

  • GDPR Article 2 defines material scope covering wholly/partly automated processing and structured manual filing systems, directly applicable in Germany.

Territorial scopeGreen

GDPR Art 3(2) extends to non-EU controllers targeting or monitoring individuals in Germany/the EU.

Claims (1):

  • GDPR Article 3(2) extends territorial scope to non-EU controllers targeting or monitoring individuals in Germany/the EU.

Regulator registration and filingGreen

DPO contact details for federally-supervised entities must be filed with BfDI via a dedicated notification form/portal.

Claims (1):

  • Federally-supervised entities must file DPO contact details with BfDI via a dedicated notification form/portal.

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 104 words

Germany applies the GDPR directly, supplemented by the federal Bundesdatenschutzgesetz (BDSG-neu) which is subsidiary and applies only where the GDPR permits national derogation or leaves gaps. Supervision is federated: the Bundesbeauftragte für den Datenschutz und die Informationsfreiheit (BfDI) supervises federal public bodies and certain federally-regulated private sectors (post, telecoms), while 17 Land-level authorities (16 Länder, with Bavaria splitting public/private-sector oversight) supervise private-sector and Land public-sector processing. A leadership transition is underway: Prof. Dr. Moritz Hennemann has been elected by the Bundestag as incoming BfDI, succeeding Prof. Dr. Louisa Specht-Riemenschneider, who remains in office in a transitional capacity until 30 September 2026 for health reasons.

Periodic update · new data 2026-11-10

Germany's federal data-protection authority has changed leadership. Moritz Hennemann became Bundesbeauftragter für den Datenschutz und die Informationsfreiheit on 1 October 2026, taking over from Louisa Specht-Riemenschneider, who resigned the post for health reasons. The succession followed an election by the Bundestag in June 2026 and a formal appointment by Bundespräsident Frank-Walter Steinmeier on 29 September 2026, ahead of Hennemann's assumption of office two days later.

The authority's public statement marking his arrival sets out a programme centred on data-protection-compliant modernisation of the state, the digital sovereignty of both Germany and the European Union, and the early data-protection assessment of significant technological leaps. Commentary from industry representatives around the transition has expressed an expectation, rather than a confirmed commitment, that the incoming leadership will actively help shape a previously announced reorganisation of data-protection supervision and bring a broader modernisation of data law. No enacted instrument accompanies these statements: the reorganisation referred to in that commentary remains at the stage of political and stakeholder discussion, not legislation, and nothing about the authority's statutory powers, jurisdiction or enforcement mandate has changed as a result of the leadership transition itself.

Outlook

The immediate significance of this development is institutional: a new commissioner is now in place, with a stated policy emphasis on technology assessment and digital sovereignty, but the legal framework under which the authority operates is unaltered. Whether the themes flagged around his appointment — supervisory reorganisation and broader modernisation of data law — translate into a concrete proposal is the development to watch for in the period ahead; until a text is published, the authority's existing statutory basis and current enforcement posture remain the operative position.

4 earlier distinct updates
Periodic update · new data 2026-10-18

Germany's data-protection supervisory architecture remains federated: the BfDI, the federal commissioner, does not supervise private-sector GDPR compliance at national level, and each of the sixteen Länder maintains its own data-protection authority for private-sector processing within its territory. This structural fact is unchanged and stands as confirmed background against which this cycle's development sits.

The material development this cycle is institutional rather than within the core GDPR supervisory structure itself: the KI-MIG, Germany's implementing act for the EU AI Regulation, was promulgated in the Federal Law Gazette (BGBl. 2026 I Nr. 233) on 28 July 2026 and entered into force the following day, 29 July 2026. The KI-MIG names the Bundesnetzagentur as the central AI market-surveillance and complaints authority for compliance with Regulation (EU) 2024/1689, except in areas where a sectoral regulator already has competence. This creates a second major German data-and-technology regulator operating alongside the federated data-protection authority structure, with its own statutory mandate specific to AI systems rather than personal data processing generally, though the two regimes will frequently overlap in practice given that much high-risk AI activity involves personal data processing.

The practical significance of this development for the data-protection landscape is that controllers and processors operating AI systems in Germany now face two potentially overlapping supervisory touchpoints: their relevant Land data-protection authority for GDPR compliance, and the Bundesnetzagentur for AI Act compliance specifically. How these two supervisory tracks will coordinate in practice, including whether the Bundesnetzagentur and the Land DPAs have agreed any formal cooperation mechanism, was not established this cycle.

Outlook

The near-term matter to watch is how the Bundesnetzagentur's new AI market-surveillance mandate interacts in practice with the existing Land-level data-protection authority structure, particularly for AI systems that process personal data and therefore sit at the intersection of both regimes. Any formal coordination guidance or memorandum between the Bundesnetzagentur and the Land DPAs, or the Datenschutzkonferenz more broadly, would be a significant marker of how this dual-authority structure is intended to function.

Periodic update · new data 2026-10-04

Germany's federal data-protection supervisory authority has completed a leadership transition. Prof. Dr. Moritz Hennemann took office as Federal Commissioner for Data Protection and Freedom of Information on 1 October 2026, succeeding Prof. Dr. Louisa Specht-Riemenschneider. The succession followed election by the Bundestag in June 2026 and formal appointment by Federal President Frank-Walter Steinmeier on 29 September 2026. This sequence, election followed by presidential appointment, is the established constitutional procedure for filling the role, and the transition itself is confirmed by the BfDI's own official announcement, corroborated by independent third-party reporting.

Beyond the confirmed fact of the succession, industry-body commentary has begun to frame expectations for Hennemann's tenure. Reported anticipated priorities include a reform of Germany's data-protection supervisory structure, which today spans the federal BfDI alongside sixteen separate Land-level data-protection authorities, a fragmented arrangement that has drawn longstanding commentary about coordination costs and inconsistent enforcement approaches across German states. Commentary also anticipates a prospective consolidated data-protection code, sometimes referred to as a Datengesetzbuch, intended to bring together currently scattered sectoral and general data-protection provisions. Neither the supervisory-structure reform nor the prospective data code has produced enacted legislative text, a published government bill, or even a formal consultation document as of this cycle; both remain at the level of informed anticipation from an industry association rather than confirmed regulatory developments, and should be read with that caveat attached.

It is worth being precise about what is and is not established here. The institutional fact of Hennemann's appointment is confirmed at a high confidence level, directly sourced from the regulator's own publication. The forward-looking policy agenda attributed to him is, by contrast, sourced from a single industry trade-association commentary piece reacting to the appointment, and carries no confirmation from the BfDI itself, from the federal government, or from any legislative body that such reforms are actually planned, scheduled, or drafted. Readers should not treat the reform agenda as though it were an announced government policy; it is, at most, an informed expectation from a stakeholder group.

The broader institutional context for Germany's data-protection framework remains otherwise unchanged this cycle. The division of competences between the Bundesnetzagentur and the BfDI under the Digital Services Act-adjacent national implementing framework, established in a prior cycle, continues to apply, though it was not independently re-verified against primary text this cycle and is not itself new information for this reporting period.

Outlook

The clearest near-term indicator to watch is whether any of the reform priorities attributed to Hennemann by industry commentary, consolidation of the federal/Laender supervisory structure or the prospective data code, advance to the stage of a published government position, draft bill, or formal consultation. Until one of those concrete steps occurs, the existing seventeen-body supervisory structure remains the operative institutional arrangement, and the reform agenda should be treated as an open question rather than a pending change. The appointment itself is now a settled fact and requires no further monitoring beyond observing how the new Commissioner's early public statements, if any, begin to confirm or depart from the priorities industry commentary has attributed to him.

Periodic update · new data 2026-09-28

Germany's data-protection enforcement remains divided across 17 independent supervisory authorities: the federal BfDI and 16 Land-level data protection authorities, coordinated by the non-binding Datenschutzkonferenz (DSK). This structural feature of the German system is unchanged this cycle, but it now sits alongside a newly-created cross-cutting supervisory allocation under the German Data Act Implementation Act (DADG), which entered into force on 30 May 2026. Under the DADG, the Federal Network Agency (Bundesnetzagentur) becomes the central supervisory and enforcement authority for the EU Data Act, while the BfDI retains its existing responsibility for personal-data processing by non-public bodies under the GDPR.

The practical significance of the DADG's entry into force is that it introduces a second federal-level regulator into Germany's data-governance landscape without altering the existing 17-body GDPR structure: the Bundesnetzagentur's Data Act mandate and the BfDI's GDPR mandate are understood to be distinct in scope, with the Bundesnetzagentur handling Data Act matters and the BfDI continuing its narrower personal-data role. Where the boundary between these two mandates will fall in practice, particularly for data-sharing arrangements that touch both personal data and the broader data-access provisions the Data Act addresses, has not yet been tested and remains to be seen as the DADG's practical application develops.

Outlook

The practical division of labour between the Bundesnetzagentur and the BfDI under the newly-in-force DADG is the primary item to watch, since the boundary between Data Act supervision and GDPR personal-data supervision has not yet been tested in a live case. Any early guidance or joint statement from the two authorities clarifying their respective jurisdictions would be the next material development in this area.

Periodic update · new data 2026-09-13

Germany's federal data-protection authority undergoes a confirmed leadership transition this cycle. Prof. Dr. Louisa Specht-Riemenschneider announced her resignation as BfDI for health reasons, remaining in office through 30 September 2026, and the Bundestag has elected Prof. Dr. Moritz Hennemann as her successor. This transition coincides with a material expansion of the BfDI's remit: under the DADG, the BfDI has supervised the Data Act's personal-data aspects for businesses and federal public bodies since the law entered into force on 30 May 2026, with the Bundesnetzagentur serving as the Data Act's general central supervisory and enforcement authority. This is a confirmed, Tier-1-sourced, binding, in-force competence grant rather than a proposal.

The combination of a change in leadership and a substantively new area of statutory competence makes this a material-change cycle for the regulator-and-framework module specifically. The dual-regulator model — BfDI for personal-data aspects, Bundesnetzagentur for the Data Act generally — is a structural feature that will define how German Data Act enforcement operates going forward, distinct from Germany's prior single-authority approach to data-protection matters generally.

Outlook

Watch the formal handover date and Hennemann's early priorities once he assumes office around 30 September 2026, and whether the new BfDI/Bundesnetzagentur dual-regulator model for the Data Act produces early jurisdictional friction or, conversely, the intended consistency and speed benefits the DADG was designed to deliver.

Sources and claims (12)
  1. Probable Bundesbeauftragte für den Datenschutz und die Informationsfreiheit — BfDI supervises federal public bodies and federally-regulated private-sector entities (post and telecoms sectors). Core supervisory-competence allocation. observed
  2. Probable Bundesbeauftragte für den Datenschutz und die Informationsfreiheit — 17 Land data protection authorities supervise private-sector processing and Land-level public bodies (Bavaria splits public/private-sector oversight). Federated supervisory structure. observed
  3. Probable BfDI — Bundesdatenschutzgesetz (BDSG-neu) supplements the GDPR as a subsidiary national implementing act, applying only where the GDPR permits derogation or leaves gaps. observed
  4. Probable OneTrust DataGuidance — TTDSG (now TDDDG) functions as lex specialis for telecom/telemedia and cookie/tracking consent matters. TTDSG renamed TDDDG following Digital Services Act adaptation. observed
  5. Probable BfDI — GDPR Article 2 defines material scope covering wholly/partly automated processing and structured manual filing systems, directly applicable in Germany. observed
  6. Probable BfDI — GDPR Article 3(2) extends territorial scope to non-EU controllers targeting or monitoring individuals in Germany/the EU. observed
  7. Probable BfDI — Federally-supervised entities must file DPO contact details with BfDI via a dedicated notification form/portal. observed
  8. Confirmed BfDI — BfDI requires: Prof. Dr. Moritz Hennemann took office as Federal Commissioner for Data Protection and Freedom of Information on 1 October 2026, succeeding Prof. Dr. Louisa Specht-Riemenschneider, after election by the Bundestag (June 2026) and appointment by Federal President Frank-Walter Steinmeier (29 September 2026). observed
  9. Uncertain eco - Association of the Internet Industry — BfDI (Hennemann priorities) proposes: Commentary frames Hennemann's priorities as including a planned reform of Germany's data-protection supervisory structure consolidating the federal/Laender 17-body system, and a prospective 'Data Code'; neither has produced enacted legislative text as of this cycle. observed
  10. Probable BfDI — Germany's KI-MIG (Gesetz zur Durchführung der KI-Verordnung), promulgated in BGBl. 2026 I Nr. 233 on 28 July 2026, entered into force 29 July 2026, naming the Bundesnetzagentur as the central AI market-surveillance and complaints authority except where a sectoral regulator applies. observed
  11. Confirmed BfDI — BfDI does not supervise private-sector GDPR compliance nationally; each of the 16 Länder has its own DPA for private-sector processing. observed
  12. Confirmed BfDI — BfDI — Moritz Hennemann became Bundesbeauftragter für den Datenschutz und die Informationsfreiheit on 1 October 2026, succeeding Louisa Specht-Riemenschneider who resigned for health reasons; elected by the Bundestag June 2026, appointed by Bundespräsident Steinmeier on 29 September 2026 observed

#

Core GDPR bases are firmly in force (green), but §26 BDSG's acknowledged normative imprecision on special-category employee data and the absence of a dedicated Employee Data Protection Act create interpretive uncertainty, justifying an amber rating for this module overall.

Primary frameworkGDPR Articles 6-9, as supplemented by BDSG §§22, 26
Supervisory authorityBfDI
Traffic-light rationale — AmberCore GDPR bases are firmly in force (green), but §26 BDSG's acknowledged normative imprecision on special-category employee data and the absence of a dedicated Employee Data Protection Act create interpretive uncertainty, justifying an amber rating for this module overall.

Sub-modules (4)

Lawful basesAmber

Six Art 6(1) GDPR bases apply; §26 BDSG (Art 88 opening clause) governs employment-context processing but is considered too imprecise by BfDI/DSK.

Claims (2):

  • GDPR Article 6(1) provides six lawful bases for processing personal data.
  • §26 BDSG governs employment-context data processing under the Art 88 GDPR opening clause; criticized by BfDI/DSK as too imprecise, prompting calls for a standalone Employee Data Protection Act. Interpretive uncertainty flagged by DSK; see gaps_register on Employee Data Protection Act status.

Special categoriesAmber

Art 9(2)(a) explicit consent required for sensitive data; §26(3) BDSG imposes additional employment-context conditions.

Claims (2):

  • GDPR Article 9(2)(a) requires explicit consent for processing special-category (sensitive) data absent another statutory exception.
  • §26(3) BDSG imposes additional conditions on processing special-category data in the employment context.

Pseudonymisation and anonymisationGreen

TTDSG §19(2) requires telemedia providers to enable anonymous/pseudonymous use where technically feasible and reasonable.

Claims (1):

  • TTDSG §19(2) requires telemedia providers to enable anonymous or pseudonymous use of services where technically feasible and reasonable.

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 70 words

Lawful processing follows the six GDPR Art 6(1) bases, with Germany exercising the Art 8 opening clause to set the digital-consent age at 16 and the Art 88 opening clause to enact §26 BDSG for employment-context processing (criticized by BfDI/DSK as too imprecise, prompting calls for a standalone Employee Data Protection Act). Special-category processing requires explicit consent or a statutory exception; TTDSG imposes an ancillary pseudonymisation/anonymous-use obligation on telemedia providers.

Periodic update · new data 2026-10-18

German law continues to treat B2B email marketing more strictly than the presumed-consent model sometimes assumed from a purely commercial perspective. Under Section 7(2) No. 2 of the UWG (Gesetz gegen den unlauteren Wettbewerb), prior express consent is required for email marketing regardless of whether the recipient is a consumer or a business. This is a materially stricter position than might be assumed by analogy to the presumed-consent rule that does apply to business recipients for telephone marketing under Section 7(2) No. 1 of the same statute; the two marketing channels are treated differently under German law, and the telephone-marketing presumption does not extend to email.

A relevant interpretive development affecting the soft opt-in exception comes from the Court of Justice of the European Union's ruling in C-654/23 (Inteligo Media), understood to have been handed down around 13 November 2025. The ruling is understood to hold that a free account can count as obtaining a customer's contact details "in the context of the sale of a product or service" for soft-opt-in purposes, where the ostensibly free service is in fact indirectly paid for through an associated paid-subscription business model. This interpretation is binding on Germany as an EU member state, though the precise pinpoint paragraph of the judgment has not been independently verified against the court's own text this cycle. For German controllers relying on the soft opt-in under the implementing provisions of the ePrivacy framework, this ruling is relevant to any freemium or indirectly-monetised service model where contact details are collected through a nominally free tier.

Outlook

Controllers operating freemium or tiered-subscription services in Germany should consider how the Inteligo Media interpretation of "in the context of the sale of a service" applies to their own soft opt-in reliance, particularly where a free tier functions as a lead-generation mechanism for a paid tier. The exact scope of the ruling, including whether German courts or the data-protection authorities issue any domestic guidance applying it, was not established this cycle and is worth monitoring.

Sources and claims (9)
  1. Probable BfDI — GDPR Article 6(1) provides six lawful bases for processing personal data. observed
  2. Probable DSK — §26 BDSG governs employment-context data processing under the Art 88 GDPR opening clause; criticized by BfDI/DSK as too imprecise, prompting calls for a standalone Employee Data Protection Act. Interpretive uncertainty flagged by DSK; see Gaps register on Employee Data Protection Act status. observed
  3. Probable BfDI — Consent under GDPR requires an unambiguous, active affirmative act by the data subject. observed
  4. Probable BfDI — Germany (GDPR Art 8 opening clause) sets digital-consent age at 16. observed
  5. Probable BfDI — GDPR Article 9(2)(a) requires explicit consent for processing special-category (sensitive) data absent another statutory exception. observed
  6. Probable BfDI — §26(3) BDSG imposes additional conditions on processing special-category data in the employment context. observed
  7. Probable OneTrust DataGuidance — TTDSG §19(2) requires telemedia providers to enable anonymous or pseudonymous use of services where technically feasible and reasonable. observed
  8. Confirmed Bundesministerium der Justiz — UWG §7(2) Nr. 2 requires prior express consent for B2B email marketing just as for B2C; the presumed-consent rule for business recipients applies only to telephone marketing under §7(2) Nr. 1. observed
  9. Probable BfDI — CJEU C-654/23 (Inteligo Media) — A free account can count as obtaining contact details 'in the context of the sale of a service' for soft-opt-in purposes where the free service is indirectly paid for via a paid subscription business model. observed

#

Directly-applicable EU rights regime with detailed, current BfDI operational guidance; only narrow, well-defined statutory exceptions exist.

Primary frameworkGDPR Articles 12-22, as narrowed by BDSG §§35-36
Supervisory authorityBfDI
Traffic-light rationale — GreenDirectly-applicable EU rights regime with detailed, current BfDI operational guidance; only narrow, well-defined statutory exceptions exist.

Sub-modules (5)

Access rightGreen

Art 15 GDPR access right is free of charge save for manifestly unfounded/excessive requests.

Claims (1):

  • GDPR Article 15 access right is free of charge save for manifestly unfounded or excessive requests.

Rectification and erasureGreen

Erasure right applies subject to §35 BDSG statutory exceptions.

Claims (1):

  • §35 BDSG carves out narrow national exceptions to the GDPR Art 17 erasure right.

Restriction and objectionGreen

Restriction (Art 18) and objection (Art 21, narrowed by §36 BDSG) rights are operative.

Claims (2):

  • GDPR Article 18 restriction right is operative and directly applicable in Germany.
  • §36 BDSG narrows the GDPR Art 21 objection right via national statutory exception.

Data portabilityGreen

Portability right (Art 20) does not apply to processing necessary for a public-interest task.

Claims (1):

  • GDPR Article 20 data portability right does not apply to processing necessary for the performance of a task carried out in the public interest.

Deadlines and response windowsGreen

One-month response window, extendable by up to two further months for complex/numerous requests, with reasons communicated within the first month.

Claims (1):

  • GDPR Article 12(3) response deadline sets a one-month response window, extendable by up to two further months for complex or numerous requests, with reasons communicated within the first month.

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 44 words

The full GDPR rights catalogue (access, rectification, erasure, restriction, objection, portability) applies directly, with BfDI publishing detailed procedural guidance (e.g., on Art 15 access-request handling, one-month response deadlines, and identity-verification practice). BDSG carves out narrow national exceptions to erasure (§35) and objection (§36) rights.

No periodic updates recorded in this cycle

Sources and claims (6)
  1. Probable BfDI — GDPR Article 15 access right is free of charge save for manifestly unfounded or excessive requests. observed
  2. Probable BfDI — §35 BDSG carves out narrow national exceptions to the GDPR Art 17 erasure right. observed
  3. Probable BfDI — GDPR Article 18 restriction right is operative and directly applicable in Germany. observed
  4. Probable BfDI — §36 BDSG narrows the GDPR Art 21 objection right via national statutory exception. observed
  5. Probable BfDI — GDPR Article 20 data portability right does not apply to processing necessary for the performance of a task carried out in the public interest. observed
  6. Probable BfDI — GDPR Article 12(3) response deadline sets a one-month response window, extendable by up to two further months for complex or numerous requests, with reasons communicated within the first month. observed

#

Robust, CJEU-tested accountability framework with clear national thresholds and multiple layered breach-notification regimes; no material gaps identified.

Primary frameworkGDPR Articles 24-39, supplemented by BDSG §§6, 38, 65, 70 and TKG §169
Supervisory authorityBfDI
Traffic-light rationale — GreenRobust, CJEU-tested accountability framework with clear national thresholds and multiple layered breach-notification regimes; no material gaps identified.

Sub-modules (7)

Accountability & DPIAGreen

Art 35 GDPR DPIA duties apply generally; §67(1) BDSG imposes an analogous risk-screening threshold analysis for federal bodies in JI-Directive scope.

Claims (1):

  • §67(1) BDSG imposes an analogous risk-screening threshold-analysis obligation on federal bodies in JI-Directive scope, alongside GDPR Art 35 DPIA duties.

DPO requirementsGreen

National 20-person threshold (§38 BDSG) plus GDPR Art 37 material triggers; enhanced DPO dismissal protection upheld by CJEU.

Claims (3):

  • §38 BDSG sets a national DPO-appointment headcount threshold of 20 persons regularly engaged in automated processing. Threshold raised from 10 to 20 by 2019 BDSG amendment.
  • German DPOs benefit from enhanced statutory dismissal protection beyond the GDPR Art 38(3) baseline.
  • CJEU (Case C-534/20, Leistritz) upheld Germany's enhanced DPO dismissal protection as compatible with EU law. Single primary anchor; recency_date approximate.

Ropa requirementsGreen

Art 30 GDPR ROPA duty generally applies; §70 BDSG imposes a stricter ROPA duty with no de-minimis exemption for JI-Directive-scope federal processing.

Claims (1):

  • §70 BDSG imposes a stricter records-of-processing (ROPA) duty for federal-public-body processing in JI-Directive scope, with no de-minimis exemption, compared to GDPR Art 30.

Joint controller arrangementsAmber

No DE-specific derogation from Art 26/28 GDPR joint-controller/processor rules was identified in this research pass.

Security measuresGreen

Art 32 GDPR technical/organisational measures apply, including breach-detection capability as a core element.

Claims (1):

  • GDPR Article 32 requires technical and organisational security measures, including breach-detection capability as a core element.

Breach notificationGreen

72-hour Art 33 GDPR notification rule plus Art 34 high-risk subject notification; stricter 24-hour sectoral rule for telecom breaches under §169 TKG.

Claims (4):

  • GDPR Article 33 requires controllers to notify the supervisory authority of a personal data breach within 72 hours of becoming aware of it.
  • GDPR Article 34 requires notification to affected data subjects where a breach is likely to result in a high risk to their rights and freedoms.
  • §169 TKG imposes a stricter 24-hour breach-notification rule for telecommunications-sector data breaches. Also underpins 5-year telecom breach-log retention duty (see data_localisation).
  • Lower Saxony DPA — 1,245 personal-data-breach notifications in H1 2026, a 58% increase year-on-year, already exceeding the full-year 2025 total; most cases involved misdirected mailings and accidental disclosures, with a rising share from hacking and phishing.

Retention and disposalAmber

General GDPR storage-limitation principle applies; telecom breach records must be logged for five years under §169(3) TKG. No further DE-specific general retention statute was identified.

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 90 words

Germany layers national specifics onto the GDPR accountability regime: BDSG §38 sets a national DPO-appointment headcount threshold (20 persons regularly engaged in automated processing) in addition to the GDPR Art 37 material triggers, and grants DPOs enhanced dismissal protection (upheld as compatible with EU law by the CJEU in Leistritz, C-534/20). Breach notification follows the general 72-hour Art 33 GDPR rule, with a stricter 24-hour sectoral rule for telecom-sector breaches under §169 TKG. Federal-public-body ROPA duties under §70 BDSG (JI-Directive scope) are stricter than the Art 30 GDPR de-minimis threshold.

Periodic update · new data 2026-10-18

The Lower Saxony data-protection authority is reported to have recorded 1,245 personal-data-breach notifications in the first half of 2026 alone, a year-on-year increase of 58%, a volume reported already to exceed the authority's full-year 2025 total. The majority of reported cases involved misdirected mailings and accidental disclosures, consistent with a persistent pattern of human-error-driven breach events, though the reporting also notes a rising share attributable to hacking and phishing activity, suggesting a gradual shift in the breach-cause mix toward more deliberate attack vectors alongside the continuing baseline of accidental disclosure.

It is important to be precise about what has and has not changed here: the underlying legal test under Articles 33 and 34 GDPR, governing when a breach must be notified to the supervisory authority and, where relevant, to affected data subjects, is unchanged. What this data point reflects is operational volume and pressure on the breach-notification and incident-response functions of controllers operating in or reporting to Lower Saxony, not a change in the substantive legal threshold for notification. The figure is specific to one Land's authority and should not be assumed to be representative of breach-notification volumes nationally without corroborating data from other Länder authorities.

Outlook

Whether the rising hacking-and-phishing share of breach causes reported in Lower Saxony continues, and whether other Länder authorities report comparable year-on-year increases, will be useful indicators of whether this is a genuinely national trend or a Lower-Saxony-specific reporting or enforcement artefact. Controllers should treat the volume increase as an operational signal to review incident-response and breach-detection capacity rather than as evidence of any change to the legal notification threshold itself.

2 earlier distinct updates
Periodic update · new data 2026-09-28

The BfDI imposed a combined 45 million euro fine on Vodafone GmbH, split across two distinct controller-duty failures. The larger component, 30 million euros, was imposed under Article 32(1) GDPR for authentication-security deficiencies in the combined use of the MeinVodafone customer portal and Vodafone's telephone hotline, a combination that enabled unauthorised third parties to gain access to customer eSIM profiles. The second component, 15 million euros, was imposed under Article 28(1) GDPR for Vodafone's failure to adequately review and monitor partner sales agencies acting on its behalf, a processor-oversight failure distinct from the security-of-processing failure underlying the larger fine.

Both components of the fine are directly sourced from the BfDI's own press release and represent the largest BfDI enforcement action on record this cycle. Read together, they identify two separate controller obligations that BfDI is treating as independently enforceable: the security-of-processing obligation under Article 32, which requires technical and organisational measures appropriate to risk, including robust authentication where combined channels (portal plus hotline) create an elevated attack surface; and the processor and agent-oversight obligation under Article 28, which requires a controller to adequately vet and monitor third parties acting on its behalf, including sales agencies rather than only formally-designated data processors in the strict contractual sense.

Outlook

BfDI's planned follow-up remediation review of Vodafone in 2026 is the concrete marker to watch, since it will indicate whether the fine has produced measurable improvements to authentication controls and partner-agency oversight. The scale of this fine and its dual-component structure may also serve as a template other German controllers in sectors with combined-channel authentication risk or extensive third-party sales-agency networks should examine when assessing their own Article 28 and Article 32 exposure.

Periodic update · new data 2026-09-13

A significant judicial constraint on the BfDI's practical enforcement capacity landed this cycle. The Bundesverwaltungsgericht dismissed as inadmissible the BfDI's suit to enforce inspection rights over the Bundesnachrichtendienst (case 6 A 2.24, decided 4 March 2026), holding that the BfDI has no enforceable legal position to litigate BND access refusals. Its only recourse against such a refusal is now a non-binding Beanstandung addressed to the Chancellery — a materially weaker enforcement tool than direct judicial enforcement of inspection rights. This is a confirmed, Tier-1-sourced, binding, in-force ruling that narrows the BfDI's practical oversight mechanism against one of Germany's most significant public-sector processors.

Set against this narrowing of enforcement reach, the accountability workload facing controllers and processors more broadly is rising sharply: the BfDI recorded 11,824 total inputs (complaints and inquiries) in 2025, approximately 36 percent more than the prior year and over 52 percent more than 2023, with complaint numbers having more than doubled within two years. The confirmed finding here is a growing volume of citizen-facing complaint and inquiry activity that controllers and processors should expect to generate more scrutiny and correspondence, even as the BfDI's enforcement toolkit against the most powerful public-sector processor category has just been narrowed by the courts.

Outlook

The key tension to watch is whether the BfDI's narrowed enforcement position against public-sector processors like the BND translates into any legislative or procedural fix, and whether the sharply rising complaint volume prompts a resourcing response from the BfDI as it also absorbs its new Data Act competence.

Sources and claims (10)
  1. Probable BfDI — §67(1) BDSG imposes an analogous risk-screening threshold-analysis obligation on federal bodies in JI-Directive scope, alongside GDPR Art 35 DPIA duties. observed
  2. Probable BfDI — §38 BDSG sets a national DPO-appointment headcount threshold of 20 persons regularly engaged in automated processing. Threshold raised from 10 to 20 by 2019 BDSG amendment. observed
  3. Probable BfDI — German DPOs benefit from enhanced statutory dismissal protection beyond the GDPR Art 38(3) baseline. observed
  4. Probable EUR-Lex / CJEU — CJEU (Case C-534/20, Leistritz) upheld Germany's enhanced DPO dismissal protection as compatible with EU law. Single primary anchor; Recency date approximate. observed
  5. Probable BfDI — §70 BDSG imposes a stricter records-of-processing (ROPA) duty for federal-public-body processing in JI-Directive scope, with no de-minimis exemption, compared to GDPR Art 30. observed
  6. Probable BfDI — GDPR Article 32 requires technical and organisational security measures, including breach-detection capability as a core element. observed
  7. Probable BfDI — GDPR Article 33 requires controllers to notify the supervisory authority of a personal data breach within 72 hours of becoming aware of it. observed
  8. Probable European Data Protection Board — GDPR Article 34 requires notification to affected data subjects where a breach is likely to result in a high risk to their rights and freedoms. observed
  9. Probable BfDI — §169 TKG imposes a stricter 24-hour breach-notification rule for telecommunications-sector data breaches. Also underpins 5-year telecom breach-log retention duty (see Data localisation). observed
  10. Probable BfDI — Lower Saxony DPA — 1,245 personal-data-breach notifications in H1 2026, a 58% increase year-on-year, already exceeding the full-year 2025 total; most cases involved misdirected mailings and accidental disclosures, with a rising share from hacking and phishing. observed

#

Fully harmonised EU transfer regime with no national derogation gaps identified; rated green reflecting legal certainty, though DE-specific granularity is inherently limited because the mechanism operates at EU level.

Primary frameworkGDPR Chapter V (Articles 44-49), as applied uniformly across EU Member States
Traffic-light rationale — GreenFully harmonised EU transfer regime with no national derogation gaps identified; rated green reflecting legal certainty, though DE-specific granularity is inherently limited because the mechanism operates at EU level.

Sub-modules (6)

Transfer mechanismsGreen

Germany relies on the EU Chapter V toolkit (adequacy, SCCs, BCRs, Art 49 derogations); no national bilateral mechanism exists.

Claims (2):

  • Germany relies on the EU Chapter V transfer toolkit (adequacy decisions, SCCs, BCRs, Art 49 derogations) with no independent national bilateral transfer mechanism.
  • noyb sent a letter to the European Commission on 30 June 2026 calling for an 'orderly withdrawal' from the DPF and has threatened a separate CJEU annulment challenge; no confirmed challenge filed as of publication.

Adequacy receivedGreen

Adequacy decisions are adopted by the European Commission and apply uniformly to Germany as an EU Member State; Germany does not receive separate national adequacy determinations.

Claims (1):

  • European Commission adopts GDPR Art 45 adequacy decisions centrally, binding Germany uniformly with all EU Member States; Germany has no independent national adequacy-granting or -receiving competence. Cited source is the 2016 EU-US Privacy Shield adequacy decision, invalidated by Schrems II (2020); used here only as an illustrative example of Commission adequacy-decision practice, not as evidence of a currently valid mechanism. Also covers the adequacy_granted sub-module point (Germany does not grant national adequacy).

Adequacy grantedGreen

Germany does not grant national adequacy; this competence sits exclusively with the European Commission under Art 45 GDPR.

Claims (2):

  • European Commission adopts GDPR Art 45 adequacy decisions centrally, binding Germany uniformly with all EU Member States; Germany has no independent national adequacy-granting or -receiving competence. Cited source is the 2016 EU-US Privacy Shield adequacy decision, invalidated by Schrems II (2020); used here only as an illustrative example of Commission adequacy-decision practice, not as evidence of a currently valid mechanism. Also covers the adequacy_granted sub-module point (Germany does not grant national adequacy).
  • EU-US Data Privacy Framework — The DPF and its UK Extension remain in force but are under growing pressure following the US Supreme Court's Trump v. Slaughter decision (29 June 2026), which undermines the FTC independence the Commission's adequacy decision relied on; EDPB sent a 31 July 2026 letter to Commissioner McGrath asking the Commission to assess the ruling's effect; no suspension or annulment has occurred.

SCCs and BCRsAmber

SCCs and BCRs are used under the EU-harmonised forms; no DE-specific supplementary form was identified in this pass.

Claims (1):

  • European Commission SCC Q&A — The 2021 SCCs cannot be used for data importers already directly subject to GDPR under Article 3(2); the Commission is still developing an additional SCC set for that scenario, not yet adopted as of 1 October 2026.

Transfer impact assessmentGreen

TIA practice for SCC-based transfers derives from CJEU Schrems case law rather than German-specific statute.

Claims (1):

  • Transfer Impact Assessment (TIA) practice derives from the CJEU's Schrems line of case law rather than a German-specific statute. No specific Schrems-judgment source independently retrieved this pass; asserted from general practitioner knowledge.

Data localisationGreen

No general personal-data localisation mandate exists; narrow sectoral retention/logging duties apply (e.g., five-year telecom breach-incident log under §169(3) TKG).

Claims (1):

  • Germany has no general personal-data localisation mandate; narrow sectoral retention/logging duties apply (e.g., five-year telecom breach-incident log under §169(3) TKG).

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 85 words

As an EU Member State, Germany has no independent national adequacy or bilateral-transfer mechanism: adequacy decisions are adopted centrally by the European Commission under GDPR Art 45 and bind Germany uniformly with all other Member States. Transfer tooling (SCCs, BCRs, Art 49 derogations) is likewise governed at EU level; Transfer Impact Assessment practice traces to the CJEU's Schrems line of case law rather than German statute. No general data-localisation mandate for personal data was identified; only narrow sectoral retention/logging duties exist (e.g., telecom breach records).

Periodic update · new data 2026-10-18

The EU-US Data Privacy Framework, the principal transfer mechanism many German controllers rely on for personal-data flows to the United States, remains formally in force, together with its UK Extension, but is understood to be under growing legal and institutional pressure. The proximate trigger is the US Supreme Court's decision in Trump v. Slaughter, handed down 29 June 2026, which is understood to undermine the independence of the Federal Trade Commission, an independence on which the European Commission's original adequacy decision for the DPF substantially relied. In direct response, the European Data Protection Board sent a letter to Commissioner McGrath on 31 July 2026 formally asking the European Commission to assess the effect of the ruling on the adequacy finding. As of publication, no suspension or annulment of the adequacy decision has occurred, and whether the Commission has yet issued any formal response to the EDPB's letter has not been established this cycle.

Separately, and reinforcing the same pressure point, the advocacy organisation noyb sent its own letter to the European Commission on 30 June 2026, calling for what it terms an "orderly withdrawal" from the DPF, and has indicated it may bring a separate annulment challenge before the Court of Justice of the European Union. No such challenge has been confirmed as filed as of this cycle. For German controllers, the combined effect of the EDPB's institutional letter and noyb's advocacy position, while neither has yet produced a formal legal change to the adequacy decision, represents a genuine escalation in the credibility of the underlying legal basis for US transfers compared to the position earlier in 2026.

A separate, more narrowly technical but confirmed gap affects the Standard Contractual Clauses regime. The Commission's own SCC guidance confirms that the 2021 SCCs cannot be used for transfers where the data importer is already directly subject to the GDPR under Article 3(2), a scenario that arises, for example, where a German exporter transfers personal data to a non-EU group entity that itself falls within the GDPR's extraterritorial scope. The Commission is understood to still be developing an additional SCC set specifically for this scenario, which had not been adopted as of 1 October 2026. German controllers in corporate groups with non-EU entities that are themselves GDPR-caught under Article 3(2) currently have no SCC-based transfer tool specifically designed for that configuration and must rely on alternative mechanisms in the interim.

Outlook

The single most consequential item to track is whether the European Commission responds formally to the EDPB's 31 July 2026 letter, and separately whether noyb proceeds to file its threatened CJEU annulment challenge against the DPF adequacy decision; either development would materially change the risk calculus for German controllers relying on the DPF for US transfers. On the SCC gap, the Commission's timeline for adopting the additional clause set for Article 3(2)-caught importers remains the key date to track, with no adoption confirmed as of 1 October 2026.

Sources and claims (7)
  1. Probable BfDI — Germany relies on the EU Chapter V transfer toolkit (adequacy decisions, SCCs, BCRs, Art 49 derogations) with no independent national bilateral transfer mechanism. observed
  2. Uncertain EUR-Lex / European Commission — European Commission adopts GDPR Art 45 adequacy decisions centrally, binding Germany uniformly with all EU Member States; Germany has no independent national adequacy-granting or -receiving competence. Cited source is the 2016 EU-US Privacy Shield adequacy decision, invalidated by Schrems II (2020); used here only as an illustrative example of Commission adequacy-decision practice, not as evidence of a currently valid mechanism. Also covers the Adequacy granted sub-module point (Germany does not grant national adequacy). observed
  3. Uncertain Bundesbeauftragte für den Datenschutz und die Informationsfreiheit — Transfer Impact Assessment (TIA) practice derives from the CJEU's Schrems line of case law rather than a German-specific statute. No specific Schrems-judgment source independently retrieved this pass; asserted from general practitioner knowledge. observed
  4. Probable BfDI — Germany has no general personal-data localisation mandate; narrow sectoral retention/logging duties apply (e.g., five-year telecom breach-incident log under §169(3) TKG). observed
  5. Confirmed EDPB — EU-US Data Privacy Framework — The DPF and its UK Extension remain in force but are under growing pressure following the US Supreme Court's Trump v. Slaughter decision (29 June 2026), which undermines the FTC independence the Commission's adequacy decision relied on; EDPB sent a 31 July 2026 letter to Commissioner McGrath asking the Commission to assess the ruling's effect; no suspension or annulment has occurred. observed
  6. Probable noyb — noyb sent a letter to the European Commission on 30 June 2026 calling for an 'orderly withdrawal' from the DPF and has threatened a separate CJEU annulment challenge; no confirmed challenge filed as of publication. observed
  7. Confirmed European Commission — European Commission SCC Q&A — The 2021 SCCs cannot be used for data importers already directly subject to GDPR under Article 3(2); the Commission is still developing an additional SCC set for that scenario, not yet adopted as of 1 October 2026. observed

#

Telecom/eprivacy and health overlays are well-developed and green; credit-scoring/Art 22 interface remains actively contested at CJEU level, and education/insurance sub-modules lack identified DE-specific overlays, justifying an overall amber rating.

Primary frameworkTTDSG/TDDDG (telecoms/telemedia); §31 BDSG (credit scoring); §26 BDSG (employment); sector health statutes
Traffic-light rationale — AmberTelecom/eprivacy and health overlays are well-developed and green; credit-scoring/Art 22 interface remains actively contested at CJEU level, and education/insurance sub-modules lack identified DE-specific overlays, justifying an overall amber rating.

Sub-modules (7)

Financial sector overlayAmber

No dedicated DE financial-sector DP overlay beyond GDPR/BDSG and credit-scoring rules (§31 BDSG) was identified separately from credit_and_scoring.

Health sector overlayGreen

Mandatory electronic patient record (ePA) obligation for statutory health insurers since 15 Jan 2025, with active BfDI guidance/regulatory sandbox activity (ReguLab, §25b SGB V).

Claims (1):

  • Statutory health-insurance members subject to mandatory electronic patient record (ePA) processing since 15 January 2025. No dedicated ePA-specific document independently retrieved this pass.

Telecoms and eprivacyGreen

TTDSG/TDDDG cookie-consent regime plus Consent Management Ordinance (April 2025).

Claims (2):

  • TTDSG/TDDDG §25(1)/(2) requires consent for storage of or access to information on end-user terminal equipment, subject to a narrow strict-necessity exception.
  • Consent Management Ordinance became effective 1 April 2025, establishing centralized consent-service recognition procedures.

Employment dataAmber

§26 BDSG plus ancillary labour statutes govern employment-context processing.

Claims (1):

  • §26 BDSG plus ancillary labour statutes govern employment-context personal data processing in Germany.

Credit and scoringAmber

§31 BDSG credit-scoring practice intersects with Art 22 GDPR automated-decision prohibition; actively before the CJEU (SCHUFA line of cases).

Claims (1):

  • §31 BDSG credit-scoring rules intersect with GDPR Art 22 automated-decision-making prohibition, actively litigated at CJEU level (SCHUFA line of cases). See also M8 profiling_restrictions / automated_decision_making_transparency claims for the CJEU dimension.

educationRed

No DE-specific education-sector DP overlay distinct from general GDPR/BDSG was identified.

insuranceRed

No DE-specific insurance-sector DP overlay distinct from general GDPR/BDSG was identified beyond credit/scoring intersections.

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 109 words

Telecoms/telemedia is the most developed sectoral overlay: TTDSG (as amended into the TDDDG) supplies a lex specialis cookie/tracking consent regime and a Consent Management Ordinance (effective 1 April 2025) for centralized consent-service recognition. Health-sector data protection is intensifying around the mandatory electronic patient record (ePA) rollout for statutory health-insurance members since 15 January 2025. Employment data processing is governed by §26 BDSG plus a patchwork of labour statutes. Credit-scoring (SCHUFA-style) automated decision-making sits at the direct intersection of §31 BDSG and Art 22 GDPR, actively litigated at CJEU level. Education and insurance-sector-specific DP overlays were not identified as materially distinct from the general GDPR/BDSG regime in this research pass.

Periodic update · new data 2026-10-18

Germany has designated the Bundesnetzagentur as its single competent authority and point of contact for the EU Data Act, which has been in force since 12 September 2025. This designation carries with it a significant penalty structure: the top tier of sanction under the Data Act's German enforcement architecture reaches up to 5,000,000 fixed or up to 2% of global turnover for undertakings exceeding 250,000,000 in worldwide turnover in the prior financial year. No new enforcement action under this framework has been identified this cycle; the designation and penalty-tier structure stand as confirmed background rather than as the subject of any new dated development.

This designation is worth reading alongside the Bundesnetzagentur's separate new role under the KI-MIG as Germany's central AI market-surveillance authority (see Algorithmic, Biometric & Surveillance Governance). The Bundesnetzagentur is accumulating a broadening data-and-technology regulatory portfolio in Germany, spanning data-access-and-sharing obligations under the Data Act and AI market-surveillance under the KI-MIG, in addition to its original telecommunications-sector mandate. This concentration of competence in a single authority is a structural fact about the German regulatory landscape that is likely to be relevant to future sectoral-watch developments as the Data Act's practical enforcement record develops.

Outlook

No enforcement action under the Data Act has yet been identified for Germany; whether the Bundesnetzagentur initiates any such action, and how it coordinates data-access-and-sharing enforcement under the Data Act with its AI market-surveillance role under the KI-MIG given the overlapping subject matter in AI systems that rely on shared or accessed data, are both worth monitoring going forward.

1 earlier distinct update
Periodic update · new data 2026-09-13

The DADG's entry into force on 30 May 2026 is understood, per law-firm commentary, to centralise personal-data supervision under the EU Data Act with the BfDI specifically, in order to ensure consistent decisions and shorter complaint-handling procedures and to avoid divergent enforcement across Germany's seventeen data-protection supervisory authorities. This is a probable, Tier-3-sourced characterisation of the government's intent behind the law rather than a Tier-1 confirmed statement, though it is consistent with the confirmed Tier-1 finding that the BfDI now holds this competence in force. The Data Act itself sits at the intersection of data-protection and broader data-economy regulation, making this a genuinely cross-sectoral development: the BfDI's jurisdiction here covers the Data Act's personal-data aspects specifically, while the Bundesnetzagentur retains general central supervisory and enforcement authority over the Data Act as a whole.

This dual-regulator model for a single EU instrument is the notable sectoral-watch feature of this cycle: rather than a fragmented multi-Land approach, Germany has chosen a two-federal-body split specifically to concentrate personal-data-related Data Act enforcement in one authority, avoiding the divergence risk that fragmented Länder-level supervision might otherwise create for this particular instrument.

Outlook

Watch for the first concrete BfDI enforcement or guidance action taken under its new Data Act personal-data competence, which would be the first practical test of whether the centralisation rationale behind the DADG's dual-regulator design delivers the intended consistency and speed benefits.

Sources and claims (6)
  1. Uncertain Bundesbeauftragte für den Datenschutz und die Informationsfreiheit — Statutory health-insurance members subject to mandatory electronic patient record (ePA) processing since 15 January 2025. No dedicated ePA-specific document independently retrieved this pass. observed
  2. Probable BfDI — TTDSG/TDDDG §25(1)/(2) requires consent for storage of or access to information on end-user terminal equipment, subject to a narrow strict-necessity exception. observed
  3. Probable OneTrust DataGuidance — Consent Management Ordinance became effective 1 April 2025, establishing centralized consent-service recognition procedures. observed
  4. Probable BfDI — §26 BDSG plus ancillary labour statutes govern employment-context personal data processing in Germany. observed
  5. Probable EUR-Lex / CJEU — §31 BDSG credit-scoring rules intersect with GDPR Art 22 automated-decision-making prohibition, actively litigated at CJEU level (SCHUFA line of cases). See also M8 Profiling restrictions / Automated decision making transparency claims for the CJEU dimension. observed
  6. Probable DLA Piper — Germany designated the Bundesnetzagentur as its single competent authority and point of contact for the EU Data Act (in force since 12 September 2025); top penalty tier up to €5,000,000 fixed or up to 2% of global turnover for undertakings exceeding €250,000,000 prior-year worldwide turnover. observed

#

Cookie/tracker consent regime is mature and green, but clean-room and cross-context-advertising sub-modules have no identified DE-specific statutory basis, and dark-pattern guidance rests on DSK soft-law rather than binding statute.

Primary frameworkTTDSG/TDDDG §25 (cookies/trackers); GDPR Art 21 (direct marketing objection)
Traffic-light rationale — AmberCookie/tracker consent regime is mature and green, but clean-room and cross-context-advertising sub-modules have no identified DE-specific statutory basis, and dark-pattern guidance rests on DSK soft-law rather than binding statute.

Sub-modules (6)

Cookies and trackersGreen

TTDSG §25(1) consent requirement for terminal-equipment storage/access, narrow §25(2) strict-necessity exception.

Claims (2):

  • TTDSG/TDDDG §25(1) requires consent for storage of or access to information on end-user terminal equipment regardless of whether personal data processing occurs.
  • TTDSG/TDDDG §25(2) provides a narrow strict-necessity exception to the cookie/tracker consent requirement.

Dark patternsAmber

DSK guidance treats cookie walls as non-compliant, though this rests on soft-law/regulatory guidance rather than a codified statutory prohibition.

Claims (1):

  • DSK (Konferenz der unabhängigen Datenschutzaufsichtsbehörden) treats cookie walls as non-compliant, per soft-law guidance rather than a codified statutory prohibition. No DSK-specific cookie-wall guidance document independently retrieved this pass; general Telemedien Rundschreiben used as proxy.

Opt out signalsRed

No DE-specific statutory recognition of Global Privacy Control or equivalent opt-out signals was identified.

Clean rooms and dcrRed

No DE-specific clean-room/data-collaboration-room statutory regime was identified.

Cross context advertisingAmber

No CPRA-style statutory 'sale'/'share' concept exists in German law; cross-context advertising is governed by general GDPR consent/legitimate-interest rules.

Direct marketingGreen

Art 21(2) GDPR absolute objection right to direct-marketing processing, operationalised via BfDI model objection letters.

Claims (2):

  • GDPR Article 21(2) grants an absolute objection right to direct-marketing processing, operationalised via BfDI model objection correspondence.
  • UWG §7(2) Nr. 2 — Advertising via electronic post (treated as including email, SMS, WhatsApp, social-media DMs) is always an unreasonable nuisance and unlawful absent prior express consent; no presumed-consent route exists for electronic post, and no B2B carve-out applies

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 70 words

TTDSG §25 supplies Germany's core cookie/tracker consent rule, requiring consent for any storage of or access to information on end-user terminal equipment regardless of whether personal data processing occurs, with a narrow strict-necessity exception. Cookie walls are treated by German DPAs as non-compliant. Direct-marketing objection rights under Art 21(2) GDPR are operationalised via BfDI model correspondence. Dedicated clean-room/data-collaboration-room and cross-context-advertising (CPRA-style) rules were not identified as part of German law.

No periodic updates recorded in this cycle

Sources and claims (5)
  1. Probable BfDI — TTDSG/TDDDG §25(1) requires consent for storage of or access to information on end-user terminal equipment regardless of whether personal data processing occurs. observed
  2. Probable OneTrust DataGuidance — TTDSG/TDDDG §25(2) provides a narrow strict-necessity exception to the cookie/tracker consent requirement. observed
  3. Uncertain BfDI — DSK (Konferenz der unabhängigen Datenschutzaufsichtsbehörden) treats cookie walls as non-compliant, per soft-law guidance rather than a codified statutory prohibition. No DSK-specific cookie-wall guidance document independently retrieved this pass; general Telemedien Rundschreiben used as proxy. observed
  4. Probable BfDI — GDPR Article 21(2) grants an absolute objection right to direct-marketing processing, operationalised via BfDI model objection correspondence. observed
  5. Confirmed Bundesministerium der Justiz — UWG §7(2) Nr. 2 — Advertising via electronic post (treated as including email, SMS, WhatsApp, social-media DMs) is always an unreasonable nuisance and unlawful absent prior express consent; no presumed-consent route exists for electronic post, and no B2B carve-out applies observed

#

Art 22 GDPR framework is in force and actively enforced/litigated (green core), but AI-specific risk-assessment rules, biometric-specific statute, and genetic-data-specific statute are all absent or still in guidance/proposal stage, and state-surveillance oversight architecture is itself subject to unresolved reform proposals.

Primary frameworkGDPR Article 22, interfacing with the EU AI Act; no DE-specific biometric/genetic statute identified
Supervisory authorityBfDI
Traffic-light rationale — AmberArt 22 GDPR framework is in force and actively enforced/litigated (green core), but AI-specific risk-assessment rules, biometric-specific statute, and genetic-data-specific statute are all absent or still in guidance/proposal stage, and state-surveillance oversight architecture is itself subject to unresolved reform proposals.

Sub-modules (6)

Profiling restrictionsGreen

Art 22 GDPR restricts solely-automated, significant-effect decisions including profiling.

Claims (1):

  • GDPR Article 22 restricts solely-automated decisions with legal or similarly significant effect, including profiling; CJEU litigation (Case C-484/24, continuing the SCHUFA line) tests whether a scoring controller's own process itself constitutes such a decision even where a third party formally decides. Also directly informs the automated_decision_making_transparency sub-module (same underlying CJEU litigation); precise holding of C-484/24 not independently confirmed this pass — see gaps_register.

Automated decision making transparencyAmber

CJEU litigation (SCHUFA line) tests whether a scoring controller's process itself constitutes an Art 22 'decision' even where a third party formally decides.

Claims (1):

  • GDPR Article 22 restricts solely-automated decisions with legal or similarly significant effect, including profiling; CJEU litigation (Case C-484/24, continuing the SCHUFA line) tests whether a scoring controller's own process itself constitutes such a decision even where a third party formally decides. Also directly informs the automated_decision_making_transparency sub-module (same underlying CJEU litigation); precise holding of C-484/24 not independently confirmed this pass — see gaps_register.

AI risk assessmentsAmber

BfDI issues non-binding AI guidance and co-runs an AI Reallabor sandbox; no binding DE AI-specific risk-assessment statute exists yet.

Claims (5):

  • BfDI issues non-binding AI guidance for federal administration and co-runs an AI Reallabor regulatory sandbox with the Bundesnetzagentur and Hesse's digital ministry. No dedicated AI Reallabor source page independently retrieved this pass.
  • BfDI — 'ReguLab' data-protection sandbox at the start of 2026, first competitive call on a healthcare-digitalisation use case opening Q1 2026; distinct from a separate AI-Reallabor pilot with Bundesnetzagentur and Hesse's digital ministry.
  • KI-MIG §20 — KI-MIG establishes a non-public register of certain high-risk AI systems at the Bundesnetzagentur under its §20, and mandates at least one AI regulatory sandbox.
  • KI-MIG — BNetzA designated default AI Act market-surveillance authority, in force 29 July 2026
  • KI-MIG (AI Market Surveillance and Innovation Promotion Act) — Germany's EU AI Act implementing act designates the Bundesnetzagentur (BNetzA) as default market-surveillance authority for Regulation (EU) 2024/1689, except where BaFin is competent for AI systems connected to regulated financial activity, or where Länder retain competence for media-sector and Land public-authority AI use; published in the Bundesgesetzblatt 28 July 2026, in force 29 July 2026

Biometric regimeAmber

No dedicated biometric-specific German statute identified beyond GDPR Art 9; enforcement gaps alleged (noyb v. HmbBfDI re PimEyes).

Claims (1):

  • noyb has litigated alleged under-enforcement by Hamburg's HmbBfDI regarding unlawful facial-recognition (PimEyes) processing.

Genetic dataRed

No DE-specific genetic-data statute beyond GDPR Art 9 special-category rules was identified in this pass.

State surveillance carveoutsAmber

BfDI retains oversight of federal intelligence-service processing; opposes a proposed UKRat transfer of this supervision as duplicative and likely to weaken oversight.

Claims (1):

  • BfDI opposes a proposed transfer of federal intelligence-service data-processing oversight functions to the already-operating Unabhängiger Kontrollrat (UKRat), an oversight body established via the 2021 BNDG amendment and operational since the turn of 2021/2022, whose remit the 2026 reform proposal seeks to expand. Corrected per Challenger fold f-002: original text mischaracterised UKRat as a new body; UKRat is existing (est. 2021 BNDG amendment), reform proposal expands its remit.

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 129 words

Germany applies the GDPR Art 22 restriction on solely-automated decisions with legal/significant effect, actively tested via CJEU litigation on SCHUFA-style credit scoring where a controller's own scoring process may itself constitute a prohibited automated decision even where a third party makes the final lending decision. BfDI has issued non-binding AI guidance for federal administration and co-runs an AI Reallabor sandbox with the Bundesnetzagentur and Hesse's digital ministry, but no AI-specific statutory risk-assessment regime beyond EU AI Act interfaces exists yet. BfDI currently retains oversight of federal intelligence-service data processing and opposes a proposed transfer of this supervision to a new Unabhängiger Kontrollrat (UKRat). No dedicated German biometric-specific or genetic-data-specific statute beyond GDPR Art 9 was identified; noyb has litigated alleged under-enforcement by Hamburg's HmbBfDI against unlawful facial-recognition (PimEyes) processing.

Periodic update · new data 2026-10-18

The KI-MIG (Gesetz zur Durchführung der KI-Verordnung), Germany's implementing act for the EU AI Regulation, entered into force on 29 July 2026, having been promulgated in the Federal Law Gazette (BGBl. 2026 I Nr. 233) the previous day. Beyond naming the Bundesnetzagentur as the central AI market-surveillance and complaints authority, the KI-MIG establishes, under its Article 20, a non-public register of certain high-risk AI systems to be maintained by the Bundesnetzagentur, and mandates the establishment of at least one AI regulatory sandbox.

The non-public character of this high-risk AI system register is itself a notable design choice: unlike some public AI-system registers maintained at EU level under the AI Act's own Article 71 database provisions, Germany's national register under KI-MIG Article 20 is not publicly accessible, meaning external stakeholders, including affected data subjects, civil-society organisations, and researchers, will not be able to independently verify which systems are registered or inspect the register's contents. This has implications for transparency and external accountability around high-risk AI deployment in Germany that sit alongside, but are distinct from, the GDPR's own transparency and data-subject-rights framework.

The mandated regulatory sandbox is a further structural element of the KI-MIG package, intended to provide a supervised testing environment for AI systems, though the operational details of how the sandbox will function, including eligibility criteria and the scope of any regulatory flexibility offered to participants, were not established this cycle.

Outlook

The practical operation of both the non-public high-risk AI register and the mandated regulatory sandbox will be important to revisit once the Bundesnetzagentur has had time to establish operational procedures. Given the register's non-public status, any future disclosure of aggregate statistics (such as the number of registered systems, by sector) by the Bundesnetzagentur, even without individual system detail, would be a meaningful transparency marker worth tracking.

1 earlier distinct update
Periodic update · new data 2026-09-13

The BfDI launched its "ReguLab" regulatory sandbox at the start of 2026, a confirmed, Tier-1-sourced institutional development. Its first competitive call concerned a healthcare-digitalisation use case, opening in the first quarter of 2026. Notably, ReguLab is distinct from a separate AI-Reallabor pilot the BfDI runs jointly with the Bundesnetzagentur and Hesse's state digital ministry — two parallel sandbox-style initiatives operating simultaneously, one BfDI-led and general-purpose, the other multi-agency and AI-Act-specific.

Both developments represent new institutional tooling rather than binding rule changes: neither ReguLab nor the AI-Reallabor pilot creates a new compliance obligation this cycle. Their significance lies in signalling how the BfDI intends to engage with algorithmic and data-driven innovation — through supervised experimentation frameworks rather than through ex ante binding rulemaking alone. The healthcare-digitalisation focus of ReguLab's first call suggests the BfDI is prioritising a sector where data-protection and algorithmic-governance questions intersect particularly acutely.

Outlook

Watch for the outcome of ReguLab's first healthcare-digitalisation competitive call and whether it produces published learnings or guidance that could inform binding rulemaking. Similarly watch for any output from the AI-Reallabor pilot with the Bundesnetzagentur and Hesse, which would be the first substantive signal of how the BfDI expects to apply data-protection principles within an AI-Act sandbox context.

Sources and claims (8)
  1. Probable EUR-Lex / CJEU — GDPR Article 22 restricts solely-automated decisions with legal or similarly significant effect, including profiling; CJEU litigation (Case C-484/24, continuing the SCHUFA line) tests whether a scoring controller's own process itself constitutes such a decision even where a third party formally decides. Also directly informs the Automated decision making transparency sub-module (same underlying CJEU litigation); precise holding of C-484/24 not independently confirmed this pass — see gaps_register. observed
  2. Uncertain Bundesbeauftragte für den Datenschutz und die Informationsfreiheit — BfDI issues non-binding AI guidance for federal administration and co-runs an AI Reallabor regulatory sandbox with the Bundesnetzagentur and Hesse's digital ministry. No dedicated AI Reallabor source page independently retrieved this pass. observed
  3. Probable OneTrust DataGuidance — noyb has litigated alleged under-enforcement by Hamburg's HmbBfDI regarding unlawful facial-recognition (PimEyes) processing. observed
  4. Probable Primary statutory record — BfDI opposes a proposed transfer of federal intelligence-service data-processing oversight functions to the already-operating Unabhängiger Kontrollrat (UKRat), an oversight body established via the 2021 BNDG amendment and operational since the turn of 2021/2022, whose remit the 2026 reform proposal seeks to expand. Corrected per Challenger fold f-002: original text mischaracterised UKRat as a new body; UKRat is existing (est. 2021 BNDG amendment), reform proposal expands its remit.
  5. Confirmed BfDI — BfDI — 'ReguLab' data-protection sandbox at the start of 2026, first competitive call on a healthcare-digitalisation use case opening Q1 2026; distinct from a separate AI-Reallabor pilot with Bundesnetzagentur and Hesse's digital ministry. observed
  6. Probable Bundesnetzagentur — KI-MIG §20 — KI-MIG establishes a non-public register of certain high-risk AI systems at the Bundesnetzagentur under its §20, and mandates at least one AI regulatory sandbox. observed
  7. Probable Bundesministerium der Justiz / Bundesamt für Justiz — KI-MIG — BNetzA designated default AI Act market-surveillance authority, in force 29 July 2026 observed
  8. Probable Bundesministerium der Justiz / Bundesamt für Justiz — KI-MIG (AI Market Surveillance and Innovation Promotion Act) — Germany's EU AI Act implementing act designates the Bundesnetzagentur (BNetzA) as default market-surveillance authority for Regulation (EU) 2024/1689, except where BaFin is competent for AI systems connected to regulated financial activity, or where Länder retain competence for media-sector and Land public-authority AI use; published in the Bundesgesetzblatt 28 July 2026, in force 29 July 2026 observed

#

The core Art 8 consent-age rule is settled and green, but minor-profiling-specific bans, education-settings-specific rules, and dependent-adult-specific protections were not identified as distinct DE statutory sub-regimes, and BfDI itself flags the EU reform track as currently under-addressing children's data protection.

Primary frameworkGDPR Article 8 (digital consent age fixed at 16 in Germany)
Supervisory authorityBfDI
Traffic-light rationale — AmberThe core Art 8 consent-age rule is settled and green, but minor-profiling-specific bans, education-settings-specific rules, and dependent-adult-specific protections were not identified as distinct DE statutory sub-regimes, and BfDI itself flags the EU reform track as currently under-addressing children's data protection.

Sub-modules (5)

Age verificationAmber

Digital-consent age of 16 diverges from the age-7 threshold for general contractual capacity under German civil law, complicating age-verification design.

Claims (3):

  • Germany's GDPR Art 8 digital-consent age (16) diverges from the age-7 threshold for general 'everyday' contractual capacity under German civil law, complicating age-verification design.
  • The JMStV (version in force 1 December 2025) grades content into three tiers: absolutely prohibited; closed adult-user-group content requiring identification plus per-use authentication; and development-impairing content controlled through age bands, time limits, technical means or labelling.
  • JMStV §5(1) — Providers of development-impairing content must ensure children/young people of the affected age tier do not ordinarily perceive it; five age tiers apply (no restriction, 6, 12, 16, 18 years) following the Sixth Interstate Amending Treaty

Minor profiling bansAmber

No standalone statutory ban on profiling of minors beyond general Art 22 GDPR exists; BfDI criticizes the EU Digital Omnibus for insufficient children's-data safeguards.

Claims (2):

  • BfDI criticizes the EU Digital Omnibus reform proposal for not adequately strengthening children's-data protection. No standalone DE minor-profiling ban beyond general Art 22 GDPR was identified.
  • JMStV §4(1) — Absolutely prohibits content regardless of age-gating: propaganda against the free democratic basic order (§86 StGB), unconstitutional-organisation symbols (§86a StGB), incitement to hatred (Volksverhetzung), and denial/trivialisation of Nazi-era genocide under §§6-7 Völkerstrafgesetzbuch

Education settingsRed

No DE-specific federal education-settings DP statute was identified; school data protection is generally a Land-law matter outside this federal-focused pass.

Dependent adultsRed

No DE-specific dependent-adult DP statute distinct from general GDPR/BDSG was identified.

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 71 words

Germany fixes the GDPR Art 8 digital-consent age at 16; below that age, parental consent is required for information-society-service processing. This diverges from general German civil-law contractual capacity, under which minors may conclude 'everyday' contracts from age 7, creating friction in age-verification design. No standalone minor-specific profiling ban or dedicated education/dependent-adult DP statute was identified; BfDI has publicly criticized the EU Digital Omnibus reform proposal for not adequately strengthening children's-data protection.

No periodic updates recorded in this cycle

Sources and claims (6)
  1. Probable BfDI — Germany's GDPR Art 8 digital-consent age (16) diverges from the age-7 threshold for general 'everyday' contractual capacity under German civil law, complicating age-verification design. observed
  2. Probable BfDI — Parental consent is required for information-society-service processing of a child's data below the age of 16. observed
  3. Probable BfDI — BfDI criticizes the EU Digital Omnibus reform proposal for not adequately strengthening children's-data protection. No standalone DE minor-profiling ban beyond general Art 22 GDPR was identified. observed
  4. Probable KJM — The JMStV (version in force 1 December 2025) grades content into three tiers: absolutely prohibited; closed adult-user-group content requiring identification plus per-use authentication; and development-impairing content controlled through age bands, time limits, technical means or labelling. observed
  5. Probable Niedersachsen VORIS — JMStV §4(1) — Absolutely prohibits content regardless of age-gating: propaganda against the free democratic basic order (§86 StGB), unconstitutional-organisation symbols (§86a StGB), incitement to hatred (Volksverhetzung), and denial/trivialisation of Nazi-era genocide under §§6-7 Völkerstrafgesetzbuch observed
  6. Probable Die Medienanstalten — JMStV §5(1) — Providers of development-impairing content must ensure children/young people of the affected age tier do not ordinarily perceive it; five age tiers apply (no restriction, 6, 12, 16, 18 years) following the Sixth Interstate Amending Treaty observed

#

Well-resourced, actively enforcing regulator network with recent multi-million-euro fines and detailed activity reporting; rated green notwithstanding the leadership transition and open EU-level reform debate, since core enforcement capacity remains fully operative.

Primary frameworkGDPR Articles 58, 77-84, as applied by BfDI and the 17 Land DPAs
Supervisory authorityBfDI
Traffic-light rationale — GreenWell-resourced, actively enforcing regulator network with recent multi-million-euro fines and detailed activity reporting; rated green notwithstanding the leadership transition and open EU-level reform debate, since core enforcement capacity remains fully operative.

Sub-modules (6)

Regulator powers and penaltiesGreen

Art 58 GDPR investigative/corrective powers and Art 83 fining maxima apply, exercised via formal Anhörung (hearing) procedure before any supervisory measure.

Claims (5):

  • BfDI and the 17 Land DPAs hold full GDPR Art 58 investigative and corrective powers, including administrative fines up to the Art 83 GDPR maxima, exercised via a formal Anhörung (hearing) procedure before any supervisory measure.
  • Germany (GDPR Art 83(5)) sets: The maximum administrative fine under GDPR Art 83(5) as applied in Germany remains EUR 20 million or 4% of worldwide annual group turnover, whichever is higher.
  • CJEU (OWiG §30 interpretation) — A fine may be imposed directly on an undertaking for a culpable infringement committed by persons acting on its behalf, without the infringement needing to be attributed to a legal representative's own conduct as previously required under §30 of the German OWiG.
  • Vodafone GmbH — EUR 45m BfDI fine, 3 June 2025
  • Vodafone GmbH — BfDI imposed two fines totalling EUR 45 million on 3 June 2025: EUR 15m for insufficient vetting/monitoring of partner agencies under Art 28(1) sentence 1 GDPR, and EUR 30m for authentication security deficiencies in the MeinVodafone portal/hotline combination exposing eSIM data to unauthorised third parties

Enforcement activity indexGreen

2025: 80 on-site + 40 written inspections, 129 supervisory measures (BfDI); €15m/€30m Vodafone fines (BfDI); €775k/€492k/€900k Hamburg fines (HmbBfDI).

Claims (6):

  • BfDI conducted 80 on-site and 40 written inspections and 129 supervisory measures in 2025, per its 34th Activity Report.
  • BfDI fined Vodafone GmbH €15 million and €30 million plus a reprimand in 2025 for Art 28/32 GDPR violations. Corroborated by two distinct T1 anchors (EDPB national-news summary and BfDI's own 34th Activity Report).
  • Hamburg's HmbBfDI imposed multiple fines (€775,000; €492,000; €900,000) across 2024-2025.
  • BfDI / Vodafone GmbH imposes: The BfDI imposed two fines totalling EUR 45 million on Vodafone GmbH on 3-4 June 2025: EUR 15 million under Art 28(1) GDPR for inadequate oversight of partner agencies, and EUR 30 million under Art 32(1) GDPR for authentication security flaws in the combined MeinVodafone-portal/hotline process enabling unauthorised eSIM-profile access, plus a formal reprimand.
  • Vodafone GmbH accepted: Vodafone accepted both fine notices and paid the full EUR 45 million to the federal treasury; the BfDI announced follow-up checks to verify the effectiveness of remedial measures.
  • In 2024-2026 the centre of gravity of German GDPR enforcement shifted toward higher-frequency, lower-value fines against SMEs, with average sanction around €50,000-€200,000 (5-10x higher than 2020).

Regulator funding and capacityGreen

BfDI is supported by approximately 380 staff across Bonn and Berlin.

Claims (1):

  • BfDI is supported by approximately 380 staff across Bonn and Berlin.

Collective redress and class actionsAmber

No dedicated statutory GDPR class-action mechanism identified beyond general German collective-action law; third-party advocacy (noyb) supplements individual redress via complaints and litigation against DPAs.

Claims (1):

  • Germany lacks a dedicated statutory GDPR class-action mechanism; third-party advocacy (noyb) supplements individual redress via complaints and litigation against DPAs.

Private right of actionGreen

Art 82 GDPR gives data subjects a harmonised, directly enforceable right to compensation for material/non-material damage.

Claims (2):

  • GDPR Article 82 gives data subjects a harmonised, directly enforceable right to compensation for material or non-material damage.
  • Germany is the most developed market for tracking-specific non-material damages claims under GDPR Art. 82; the BGH's roughly €100 figure for a simple loss-of-control case is neither a tariff nor a cap, and Meta Business Tools tracking cases have produced awards ranging €500 to €10,000.

Recent developments 180dGreen

BfDI leadership transition to Prof. Dr. Moritz Hennemann (2026) and BfDI's public critique of the EU Digital Omnibus reform package on data-broker, children's-data, and AI-specific gaps.

Claims (2):

  • Prof. Dr. Moritz Hennemann elected as incoming BfDI, succeeding Prof. Dr. Louisa Specht-Riemenschneider, who remains in office in a transitional capacity until 30 September 2026 for health reasons. Corroborated by two distinct T1 anchors (BfDI Hennemann press release and BfDI Rückzug press release). Forward date extracted to regulatory_horizon.
  • BfDI publicly critiques the EU Digital Omnibus reform package for gaps on data-broker regulation, children's-data protection, and AI-specific issues.

Key findings (3)

  • — source on file
  • — source on file
  • — source on file
Category narrative 133 words

BfDI and the 17 Land DPAs hold full Art 58 GDPR investigative and corrective powers, including administrative fines up to the Art 83 GDPR maxima. Enforcement activity is materially active: BfDI's 34th Activity Report records 80 on-site and 40 written inspections and 129 supervisory measures in 2025, and BfDI fined Vodafone GmbH €15m and €30m plus a reprimand in 2025 for Art 28/32 violations; Hamburg's HmbBfDI separately imposed multiple six-to-seven-figure fines (€775,000; €492,000; €900,000) across 2024-2025. Data subjects benefit from the harmonised Art 82 GDPR compensation right, directly enforceable in German courts; collective advocacy (e.g., noyb litigation against HmbBfDI) supplements individual redress absent a dedicated statutory GDPR class-action mechanism. Recent 180-day developments include the BfDI leadership transition to Prof. Dr. Moritz Hennemann and BfDI's public critique of the EU Digital Omnibus reform package.

Periodic update · new data 2026-10-18

A reported interpretation affecting the German Act on Regulatory Offences (OWiG) is understood to have lowered the bar for attributing corporate liability in the data-protection enforcement context. Previously, under Section 30 OWiG as applied in this area, a fine against an undertaking required the underlying infringement to be attributed to the conduct of a legal representative specifically. The reported development holds that a fine may instead be imposed directly on an undertaking for a culpable infringement committed by persons acting on its behalf, without that representative-attribution requirement. This is reported via a European regulatory tracker rather than independently confirmed against the originating court's own publication this cycle, and the precise case citation and effective date remain to be verified.

Alongside this doctrinal development, the broader enforcement trend in Germany between 2024 and 2026 is reported to show a shift in the centre of gravity toward higher-frequency, lower-value fines against small and medium-sized enterprises, with average sanctions in the range of roughly 50,000 to 200,000, reported to be five to ten times higher than typical 2020-era sanctions. This is a trend observation rather than a single dated enforcement event, and should be read as a directional signal about enforcement posture rather than a precise, independently-verified statistical finding.

On private rights of action, Germany continues to be the most developed market for tracking-specific non-material damages claims under GDPR Article 82. The Bundesgerichtshof's figure of approximately 100 for a simple loss-of-control case, arising from a decision reported around 18 November 2024, functions as neither a fixed tariff nor a cap on such claims; Meta Business Tools tracking cases specifically have produced awards ranging from 500 to 10,000, reflecting a wide range depending on case-specific factors.

Outlook

If the lowered corporate-fine attribution bar under OWiG Section 30 is confirmed against the originating court's own publication, this would be a materially significant development for how German data-protection fines against undertakings are calculated and defended going forward, and is worth independent verification in a future cycle. The continuing SME-fine-frequency trend and the range of Article 82 damages awards in tracking cases are both worth monitoring for whether they continue on their reported trajectories.

2 earlier distinct updates
Periodic update · new data 2026-09-28

The combined 45 million euro BfDI fine against Vodafone GmbH is the dominant enforcement development for Germany this cycle, and it stands as the largest GDPR enforcement action on record within the scope of this cycle's evidence. The fine was structured as two separate penalties: 30 million euros under Article 32(1) for authentication-security deficiencies enabling unauthorised eSIM access, and 15 million euros under Article 28(1) for inadequate oversight of partner sales agencies. Both figures and their underlying legal bases are drawn directly from the BfDI's own published press release, giving this finding a high degree of primary-source confidence.

The maximum statutory penalty available to German supervisory authorities under GDPR Article 83(5) remains 20 million euros or 4% of worldwide group annual turnover, whichever is higher; the Vodafone fine's individual components fall within this ceiling when assessed against Vodafone's global turnover, though the combined 45 million euro total across two separate infringement findings illustrates how a single enforcement action can produce a headline figure exceeding the per-infringement statutory maximum when multiple distinct violations are found and penalised separately.

Outlook

The BfDI's planned 2026 remediation follow-up review of Vodafone is the next concrete enforcement-and-redress marker to watch. More broadly, this fine is likely to be read across the German telecommunications sector as an indicator of the authentication and processor-oversight standard BfDI now expects, and other operators with comparable combined-channel authentication architectures or extensive partner-agency networks may face comparable scrutiny.

Periodic update · new data 2026-09-13

This cycle's defining enforcement-and-redress development is the Bundesverwaltungsgericht's dismissal of the BfDI's suit to enforce inspection rights over the Bundesnachrichtendienst, decided 4 March 2026 (case 6 A 2.24). The court held the BfDI has no enforceable legal position to litigate BND access refusals, leaving only a non-binding Beanstandung to the Chancellery as recourse. This confirmed, Tier-1-sourced ruling materially narrows the BfDI's practical redress mechanism against one of the most consequential public-sector processors in Germany, with implications for how any future BND-related complaint or oversight gap can practically be pursued.

Against this narrowing of judicial enforcement reach, the BfDI's own complaint-and-inquiry volume rose sharply: 11,824 total inputs in 2025, approximately 36 percent more than the prior year and over 52 percent more than 2023, with complaint numbers having more than doubled within two years. Separately, marking twenty years of the federal Freedom of Information Act, the BfDI published Germany's first nationwide representative survey on public perceptions of freedom of information, presented at the 8th Symposium on Freedom of Information (2-3 June 2026); roughly one in ten respondents reported having made an IFG request. This transparency-culture milestone sits within the same enforcement-and-redress remit as the BND ruling and rising complaint volumes, together describing a system facing growing citizen-facing demand even as one significant enforcement avenue against a powerful public-sector actor has just been closed off judicially.

Outlook

The central question for the next cycle is whether the BND ruling's narrowing of the BfDI's enforcement position prompts any legislative response strengthening the BfDI's inspection-enforcement powers, and whether the rising complaint volume is matched by any resourcing or procedural adaptation at the BfDI as it also takes on its new Data Act competence.

Sources and claims (17)
  1. Probable BfDI — BfDI and the 17 Land DPAs hold full GDPR Art 58 investigative and corrective powers, including administrative fines up to the Art 83 GDPR maxima, exercised via a formal Anhörung (hearing) procedure before any supervisory measure. observed
  2. Probable BfDI — BfDI conducted 80 on-site and 40 written inspections and 129 supervisory measures in 2025, per its 34th Activity Report. observed
  3. Confirmed European Data Protection Board — BfDI fined Vodafone GmbH €15 million and €30 million plus a reprimand in 2025 for Art 28/32 GDPR violations. Corroborated by two distinct T1 anchors (EDPB national-news summary and BfDI's own 34th Activity Report). observed
  4. Probable OneTrust DataGuidance — Hamburg's HmbBfDI imposed multiple fines (€775,000; €492,000; €900,000) across 2024-2025. observed
  5. Probable BfDI — BfDI is supported by approximately 380 staff across Bonn and Berlin. observed
  6. Probable OneTrust DataGuidance — Germany lacks a dedicated statutory GDPR class-action mechanism; third-party advocacy (noyb) supplements individual redress via complaints and litigation against DPAs. observed
  7. Probable BfDI — GDPR Article 82 gives data subjects a harmonised, directly enforceable right to compensation for material or non-material damage. observed
  8. Confirmed BfDI — Prof. Dr. Moritz Hennemann elected as incoming BfDI, succeeding Prof. Dr. Louisa Specht-Riemenschneider, who remains in office in a transitional capacity until 30 September 2026 for health reasons. Corroborated by two distinct T1 anchors (BfDI Hennemann press release and BfDI Rückzug press release). Forward date extracted to regulatory_horizon. observed
  9. Probable BfDI — BfDI publicly critiques the EU Digital Omnibus reform package for gaps on data-broker regulation, children's-data protection, and AI-specific issues. observed
  10. Probable https://smtpedia.com/germany-data-protection-authority-bfdi/ — Germany (GDPR Art 83(5)) sets: The maximum administrative fine under GDPR Art 83(5) as applied in Germany remains EUR 20 million or 4% of worldwide annual group turnover, whichever is higher.
  11. Probable Heuking Kühn Lüer Wojtek — BfDI / Vodafone GmbH imposes: The BfDI imposed two fines totalling EUR 45 million on Vodafone GmbH on 3-4 June 2025: EUR 15 million under Art 28(1) GDPR for inadequate oversight of partner agencies, and EUR 30 million under Art 32(1) GDPR for authentication security flaws in the combined MeinVodafone-portal/hotline process enabling unauthorised eSIM-profile access, plus a formal reprimand. observed
  12. Probable keyed.de — Vodafone GmbH accepted: Vodafone accepted both fine notices and paid the full EUR 45 million to the federal treasury; the BfDI announced follow-up checks to verify the effectiveness of remedial measures. observed
  13. Probable Gibson Dunn — CJEU (OWiG §30 interpretation) — A fine may be imposed directly on an undertaking for a culpable infringement committed by persons acting on its behalf, without the infringement needing to be attributed to a legal representative's own conduct as previously required under §30 of the German OWiG. observed
  14. Probable WebLegal.ai — In 2024-2026 the centre of gravity of German GDPR enforcement shifted toward higher-frequency, lower-value fines against SMEs, with average sanction around €50,000-€200,000 (5-10x higher than 2020). observed
  15. Probable Bundesgerichtshof (BGH) — Germany is the most developed market for tracking-specific non-material damages claims under GDPR Art. 82; the BGH's roughly €100 figure for a simple loss-of-control case is neither a tariff nor a cap, and Meta Business Tools tracking cases have produced awards ranging €500 to €10,000. observed
  16. Confirmed BfDI — Vodafone GmbH — EUR 45m BfDI fine, 3 June 2025 observed
  17. Confirmed BfDI — Vodafone GmbH — BfDI imposed two fines totalling EUR 45 million on 3 June 2025: EUR 15m for insufficient vetting/monitoring of partner agencies under Art 28(1) sentence 1 GDPR, and EUR 30m for authentication security deficiencies in the MeinVodafone portal/hotline combination exposing eSIM data to unauthorised third parties observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 86 claim(s) (86 category placement(s)), 71 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 3 Nov 2026: upheld (12 confirmed against the cited source; 8 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (34 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 8Children & Vulnerable Groupsparental consent
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsdeadlines and response windows
Art. 14Data Subject Rightsdeadlines and response windows
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties