Data Protection Monitor
Global Privacy & Data Protection Intelligence

Not every instrument is backed by its official text yet. At least one law or rulebook covered here has no official source (tier 1) retrieved for it yet. No finding on this page is shown with confidence above “Probable” until stronger sources are retrieved.

Denmark Data Protection & Privacy Regulation

DK schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: artificial-intelligence

Last updated · 10 categories · 54 claims · 40 sources in the cumulative register

Denmark's data protection authority, Datatilsynet, cannot impose administrative fines directly under GDPR Article 83; Danish law routes enforcement through the national courts, which impose fines as criminal sanctions under the Article 83(9)/Recital 151 model.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Enforcement & Redress (2 open gaps).

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-10-26

Framework postureRegulated (omnibus)10 of 10 modules populated · AI-synthesised · Tier-1/2 verified
Lead supervisory authorityDatatilsynetPrimary statutory & supervisory perimeter
Next milestone (> 2026-10-26)None scheduledNo dated future statutory milestone on record
Module coverage & confidence10 / 10 modules assessed0 Confirmed · 10 Probable · 0 Uncertain

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

Jurisdiction brief

Latest update · 25 October 2026

Lead Signal

Denmark's central civil registration system has suffered a major unauthorised-access incident. The CPR administration notified Datatilsynet on 4 October 2026 of a security incident in which an unauthorised party, exploiting a Danish company's legitimate automated lookup access to the CPR system, obtained names, addresses and CPR numbers of approximately 8.8 million registered individuals, roughly 80 percent of the register's approximately 11 million entries. The unauthorised access ran intermittently over 21 days and 17 hours, between 10 September and 2 October 2026. Datatilsynet is now investigating how responsibility should be allocated between the CPR administration and the implicated private company, and must assess whether both parties maintained technical and organisational security measures appropriate to the risk under the GDPR's security obligation. The implicated company has stated that the volume of lookups involved far exceeded its own customer base, pointing toward a compromise of its own IT systems as the likely vector rather than misuse of legitimately granted access volumes. No finding or fine recommendation has yet issued from Datatilsynet; the inquiry's outcome, and therefore the ultimate allocation of responsibility, remains open.

Key regulatory facts for Denmark
Regulatory DimensionDenmark Standing Position
JurisdictionDenmark (DK)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 54 sourced findings)
Regulator & FrameworkComprehensive, GDPR-aligned omnibus framework in force with an active, funded regulator.
Lawful Processing & Special DataMultiple national derogations from the GDPR baseline require jurisdiction-specific compliance attention (age threshold, CPR numbers, HR legitimate interest).
Data Subject RightsRights framework is GDPR-standard; enforcement record demonstrates operative supervision.
Controller/Processor DutiesFramework is GDPR-standard but enforcement record shows recurring security/accountability failures driving active supervisory casework.
Primary Instruments CitedIAPP, Secure Privacy, Shattered.io, Tech Insider, dataprotection.gi
Last Confirmed / Updated2026-11-04 (40 sources in cumulative register)

#

Comprehensive, GDPR-aligned omnibus framework in force with an active, funded regulator.

Primary frameworkDatabeskyttelsesloven (Danish Data Protection Act, Act No. 502 of 23 May 2018) implementing/supplementing Regulation (EU) 2016/679 (GDPR)
Supervisory authorityDatatilsynet
Traffic-light rationale — GreenComprehensive, GDPR-aligned omnibus framework in force with an active, funded regulator.

Sub-modules (5)

Regulator And AuthorityGreen

Datatilsynet is Denmark's single DPA, structured as a council plus secretariat, re-enacted from the pre-GDPR Personal Data Act era.

Claims (3):

  • Datatilsynet's council-and-secretariat structure, pre-dating the GDPR, was re-enacted under the 2018 Danish Data Protection Act.
  • Datatilsynet — Administrative GDPR fines directly; refers cases to police with a recommended amount, and a court decides
  • Datatilsynet is Denmark's independent GDPR Art. 51 supervisory authority but cannot impose administrative fines itself; it refers cases to the police for prosecution, with a court ultimately setting any fine.

Act And InstrumentsGreen

Databeskyttelsesloven (2018) is the operative national instrument alongside directly-applicable GDPR.

Claims (2):

  • The Danish Data Protection Act re-enacts to a large extent the pre-existing Personal Data Act and adds specific regulation not covered by the GDPR.
  • Databeskyttelsesloven — Denmark implements the GDPR directly, supplemented by the Danish Data Protection Act (consolidated Act No. 289 of 8 March 2024), which adds national rules on CPR numbers, CCTV, criminal data and age of digital consent.

Material ScopeGreen

The Act extends beyond GDPR to manual disclosures between administrative authorities and to legal-person data processed by credit agencies.

Claims (1):

  • The Act extends to areas not covered by GDPR, including manual disclosure of personal information between administrative authorities and processing of information on legal persons by credit information agencies.

Territorial ScopeGreen

Applies to controllers/processors established in Denmark regardless of where processing occurs, and to non-established controllers targeting or monitoring persons in Denmark.

Claims (1):

  • The Act applies to all processing by controllers or processors established in Denmark regardless of where the processing takes place, and to processing by non-established controllers/processors offering goods or services to, or monitoring, persons in Denmark.

Regulator Registration And FilingAmber

Prior Datatilsynet approval is required before establishing warning registers, credit-rating agencies, and judicial information systems.

Claims (1):

  • Prior approval from Datatilsynet is required before establishing warning registers, credit rating agencies and judicial information systems.

Key findings (1)

  • — source on file
Category narrative 60 words

Denmark implements the GDPR through the Danish Data Protection Act (Databeskyttelsesloven, 2018), enforced by Datatilsynet (the Danish Data Protection Agency), which retains its pre-existing council-plus-secretariat structure. The Act both supplements GDPR derogation options and extends coverage to areas outside GDPR's material scope (manual administrative disclosures, credit-agency processing of legal-person data). Territorial scope tracks GDPR Art 3 but is restated domestically.

No periodic updates recorded in this cycle

Sources and claims (11)
  1. Probable IAPP — Datatilsynet's council-and-secretariat structure, pre-dating the GDPR, was re-enacted under the 2018 Danish Data Protection Act. observed
  2. Probable IAPP — The Danish Data Protection Act re-enacts to a large extent the pre-existing Personal Data Act and adds specific regulation not covered by the GDPR. observed
  3. Probable IAPP — The Act extends to areas not covered by GDPR, including manual disclosure of personal information between administrative authorities and processing of information on legal persons by credit information agencies. observed
  4. Probable IAPP — The Act applies to all processing by controllers or processors established in Denmark regardless of where the processing takes place, and to processing by non-established controllers/processors offering goods or services to, or monitoring, persons in Denmark. observed
  5. Probable IAPP — Prior approval from Datatilsynet is required before establishing warning registers, credit rating agencies and judicial information systems. observed
  6. Probable Secure Privacy — Datatilsynet — Administrative GDPR fines directly; refers cases to police with a recommended amount, and a court decides observed
  7. Probable Shattered.io — Databeskyttelsesloven — Denmark implements the GDPR directly, supplemented by the Danish Data Protection Act (consolidated Act No. 289 of 8 March 2024), which adds national rules on CPR numbers, CCTV, criminal data and age of digital consent. observed
  8. Probable Shattered.io — Datatilsynet is Denmark's independent GDPR Art. 51 supervisory authority but cannot impose administrative fines itself; it refers cases to the police for prosecution, with a court ultimately setting any fine. observed
  9. Probable Shattered.io — Danish CPR (civil registration) system — open_investigation observed
  10. Probable Tech Insider — Technical University of Denmark (DTU) DTUBasen system — open_investigation observed
  11. Probable dataprotection.gi — Datatilsynet — in_force observed

#

Multiple national derogations from the GDPR baseline require jurisdiction-specific compliance attention (age threshold, CPR numbers, HR legitimate interest).

Primary frameworkGDPR Arts 6, 7, 9 as supplemented by Databeskyttelsesloven §§6-13
Supervisory authorityDatatilsynet
Traffic-light rationale — AmberMultiple national derogations from the GDPR baseline require jurisdiction-specific compliance attention (age threshold, CPR numbers, HR legitimate interest).
D2 · Lawful Processing — Full Module Record4 sub-modules · 46 words · 3 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Rights framework is GDPR-standard; enforcement record demonstrates operative supervision.

Primary frameworkGDPR Arts 12-22, directly applicable
Supervisory authorityDatatilsynet
Traffic-light rationale — GreenRights framework is GDPR-standard; enforcement record demonstrates operative supervision.

Sub-modules (5)

Access RightGreen

Datatilsynet has taken enforcement action (JobTeam) against erasure of personal data during the pendency of an access request, holding this defeats the basic GDPR access-right guarantee.

Claims (1):

  • Datatilsynet found that a recruitment company (JobTeam) violated GDPR's lawfulness/fairness/transparency requirements by erasing personal data subject to an access request during the period after the request was submitted and before the reply was given.

Rectification And ErasureGreen

Datatilsynet enforcement (Taxa 4x35) confirms the storage-limitation/erasure duty is actively supervised where retention exceeds necessity.

Claims (1):

  • Datatilsynet proposed a DKK 1.2 million fine against taxi company Taxa 4x35 for retaining customer phone-number data years beyond the stated retention period, holding that data must be deleted once no longer needed.

Restriction And ObjectionGreen

GDPR Arts 18 and 21 apply directly; no Danish derogation identified in this pass.

Data PortabilityGreen

GDPR Art 20 applies directly; no Danish derogation identified.

Deadlines And Response WindowsGreen

Standard GDPR one-month response window applies; the JobTeam case turned on conduct occurring within that window.

Claims (1):

  • Datatilsynet applies the GDPR's statutory response window to access requests, finding it unlawful for a controller to erase data linked to an access request during the pendency of that window.

Key findings (1)

  • — source on file
Category narrative 39 words

Denmark applies GDPR's data-subject-rights framework (Arts 12-22) directly, with no material derogation identified for access, rectification/erasure, restriction, objection, portability, or response deadlines beyond GDPR's one-month standard. Enforcement history (JobTeam, Taxa 4x35) confirms Datatilsynet actively polices access and erasure/retention compliance.

No periodic updates recorded in this cycle

Sources and claims (3)
  1. Probable EDPB — Datatilsynet found that a recruitment company (JobTeam) violated GDPR's lawfulness/fairness/transparency requirements by erasing personal data subject to an access request during the period after the request was submitted and before the reply was given. observed
  2. Probable EDPB — Datatilsynet proposed a DKK 1.2 million fine against taxi company Taxa 4x35 for retaining customer phone-number data years beyond the stated retention period, holding that data must be deleted once no longer needed. observed
  3. Probable EDPB — Datatilsynet applies the GDPR's statutory response window to access requests, finding it unlawful for a controller to erase data linked to an access request during the pendency of that window. observed

#

Framework is GDPR-standard but enforcement record shows recurring security/accountability failures driving active supervisory casework.

Primary frameworkGDPR Arts 5(2), 24, 25, 28, 30, 32-34, 35 as applied by Datatilsynet
Supervisory authorityDatatilsynet
Traffic-light rationale — AmberFramework is GDPR-standard but enforcement record shows recurring security/accountability failures driving active supervisory casework.
Periodic update · new data 2026-10-25

Controller/Processor Duties

The CPR register security incident is the defining controller/processor duties event of this period. The CPR administration notified Datatilsynet on 4 October 2026 of a breach in which an unauthorised party, exploiting a Danish company's legitimate automated lookup access to the CPR system, obtained names, addresses and CPR numbers belonging to approximately 8.8 million registered individuals, roughly 80 percent of the register's approximately 11 million entries. The unauthorised access occurred intermittently across 21 days and 17 hours between 10 September and 2 October 2026. This is a breach of substantial scale touching a large majority of the national population register and the identity credential that underlies much of Denmark's administrative and financial infrastructure.

Datatilsynet has opened an inquiry into allocation of responsibility between the CPR administration and the implicated private company, and must determine whether each maintained technical and organisational measures appropriate to the risk, the core Article 32 security standard. The implicated company has stated publicly that the volume of lookups recorded far exceeded its own customer base, which it points to as evidence that its own IT systems were compromised rather than that the access reflected ordinary, authorised use at an unusual scale. This is the company's own account; Datatilsynet has not yet issued a finding on whether this explanation accounts for the full scope of unauthorised access or whether the CPR administration's own access controls and monitoring also fell short of what Article 32 requires. No finding or fine recommendation has issued from the inquiry as of this period, and responsibility allocation remains genuinely open between the two parties.

Outlook

The central marker to watch is whether Datatilsynet's inquiry results in a formal finding against either or both parties, and what technical and organisational measures the inquiry concludes should have been, but were not, in place. Given Datatilsynet's inability to impose fines directly, any financial consequence of a finding against either party would need to proceed via police referral and a subsequent court decision.

Periodic update · new data 2026-10-18

Controller/Processor Duties

Denmark recorded two significant breach-notification events in early October 2026. The Danish Central Population Register (CPR) suffered unauthorised access arising from misuse of a private company's legitimate search privileges, exposing names, addresses and CPR numbers for roughly 80 percent of the register's approximately 11 million records; individuals with registered address protection were excluded from the exposure. The Ministry responsible for the register notified Datatilsynet on 4 October 2026 and disclosed the breach publicly on 5 October 2026.

Separately, the Technical University of Denmark disclosed on 2 October 2026 a breach of its DTUBasen identity and access-management system, understood to potentially affect up to 200,000 users. DTU notified Datatilsynet and the National Special Crime Unit by 4 October 2026, a timeline consistent with the GDPR Article 33 seventy-two-hour notification standard. The near-simultaneous timing of both notifications, in the same narrow early-October window, marks a concentrated spike in breach-notification activity in Denmark relative to the preceding period.

Outlook

The matters to watch are how Datatilsynet and the National Special Crime Unit respond to both notifications, and whether either matter progresses toward a police referral. Denmark's court-based sanctioning model means any eventual fine would follow a police referral with a recommended penalty rather than a direct administrative fine from Datatilsynet.

Periodic update · new data 2026-09-28

Controller/Processor Duties

Denmark's security-of-processing enforcement is escalating in practical terms this cycle. The Western High Court fined the Region of Southern Denmark DKK 500,000 in a case reported April 2026 for failing to implement appropriate security measures under GDPR. This is probable rather than confirmed on the underlying facts as reported, but the case is instructive as a controller-obligation matter regardless of the fining mechanism's peculiarity in Denmark: it demonstrates that the court-mediated route, activated when Datatilsynet refers a matter with a recommended penalty, remains capable of producing a material fine against a public-sector controller for a security-measures failure. Public authorities and municipalities in Denmark, who handle substantial volumes of sensitive personal data, should read this case as confirming that public-sector status is not itself a mitigating factor in the court's fine-setting exercise.

The case sits within Denmark's broader enforcement architecture, where the regulator's own limited fining power (addressed separately under enforcement and redress) shifts the practical locus of controller accountability toward the courts rather than toward direct administrative regulatory action. For controllers and processors operating in Denmark, this means that a security-of-processing failure carries a genuinely open-ended penalty exposure determined by judicial assessment rather than by a published administrative fining tariff, which may in practice produce less predictability for entities trying to assess their own risk exposure ahead of any incident.

Outlook

The item to watch is whether further security-of-processing cases follow a similar court-referral pattern, and whether the DKK 500,000 figure in the Region of Southern Denmark case becomes a practical reference point for subsequent security-measures fines against Danish public authorities.

D4 · Controller & Processor — Full Module Record7 sub-modules · 37 words · 7 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Transfer mechanisms are fully harmonised EU-level tools; no Denmark-specific gap identified.

Primary frameworkGDPR Arts 44-49 (Chapter V), directly applicable
Supervisory authorityDatatilsynet
Traffic-light rationale — GreenTransfer mechanisms are fully harmonised EU-level tools; no Denmark-specific gap identified.
D5 · Cross-Border & Adequacy — Full Module Record6 sub-modules · 59 words · 2 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Green), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Several sector overlays confirmed (marketing, HR, credit, health); financial, education and insurance overlays remain evidence gaps.

Primary frameworkDatabeskyttelsesloven sector provisions; Danish Marketing Practices Act (Markedsføringsloven)
Supervisory authorityDatatilsynet
Traffic-light rationale — AmberSeveral sector overlays confirmed (marketing, HR, credit, health); financial, education and insurance overlays remain evidence gaps.
Periodic update · new data 2026-10-25

Sectoral Watch

Denmark's sectoral data-governance architecture has consolidated further this period around two separate EU instruments. First, the national implementing statute for the EU Data Act, Act No. 1618 of 16 December 2025, entered into force on 17 December 2025, establishing the national framework supporting Regulation (EU) 2023/2854, which has been directly applicable since 12 September 2025. Digitaliseringsstyrelsen is designated as the competent authority under this national framework, a designation two independent cross-EU legal trackers confirmed as operational as of September 2026, giving the designation a reasonably well-corroborated standing as of this period.

Second, the regulatory architecture governing cookie consent in Denmark continues to rest on a dual-regulator structure. Supervision of the Danish cookie order, the Cookiebekendtgoerelsen, moved from Erhvervsstyrelsen to Digitaliseringsstyrelsen in December 2022, and that allocation remains the operative arrangement. Datatilsynet separately enforces the underlying GDPR and Databeskyttelsesloven basis for the same cookie-banner practices, meaning a single cookie-consent mechanism on a Danish website can in principle draw scrutiny from two different regulators applying two different legal bases, the sector-specific cookie order on one hand and the general data-protection framework on the other.

Outlook

The Digitaliseringsstyrelsen competent-authority role under the EU Data Act is a recently consolidated but already cross-confirmed development; the item to watch is the first substantive exercise of that authority's powers under the Data Act framework. The dual cookie-order and GDPR enforcement structure is a standing feature rather than a new development, but remains relevant background for understanding how Danish cookie-consent enforcement could proceed via either or both regulatory channels.

D6 · Sectoral Watch — Full Module Record7 sub-modules · 50 words · 4 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Core cookie-consent and direct-marketing rules are confirmed; several sub-modules are genuinely inapplicable (US-specific) or unevidenced at Denmark level.

Primary frameworkGDPR Art 6/7 as applied via Datatilsynet cookie guidance; Danish Marketing Practices Act
Supervisory authorityDatatilsynet
Traffic-light rationale — AmberCore cookie-consent and direct-marketing rules are confirmed; several sub-modules are genuinely inapplicable (US-specific) or unevidenced at Denmark level.
Periodic update · new data 2026-09-28

AdTech & Commercial Privacy

Datatilsynet has confirmed cookie-tracking enforcement as a named 2026 supervisory priority, announced 7 January 2026. The regulator's stated practical posture recognises no analytics exemption, meaning that even cookies deployed solely for analytics purposes require valid consent under the joint GDPR and Cookiebekendtgørelsen framework, and requires a Danish-language consent solution for compliance, a specific and testable requirement that goes beyond generic multi-language consent-banner practice common elsewhere in the EU.

That stated priority is understood to have already produced a concrete enforcement referent: Datatilsynet is reported to have reprimanded JP/Politikens Hus and Berlingske, two of Denmark's most prominent media publishers, over colour-coded consent nudging and conditional cookie walls. Colour-coded nudging, using visual weighting such as colour contrast to steer users toward an accept option, and conditional cookie walls, where continued site access is made contingent on cookie acceptance, are both established dark-pattern categories, and their appearance in an enforcement action against major Danish news publishers signals that Datatilsynet is treating consent-interface design, not merely the presence or absence of a consent banner, as within its active enforcement scope.

For digital publishers and advertisers operating in the Danish market, the practical takeaway is that consent-interface design choices previously treated as a commercial optimisation question are now squarely within Datatilsynet's named 2026 priority area, and the JP/Politikens Hus and Berlingske matter demonstrates the regulator is willing to act against major domestic publishers rather than reserving enforcement for smaller or less prominent actors.

Outlook

The item to watch is whether Datatilsynet extends the cookie-tracking priority into further reprimand or fine-referral actions against other Danish publishers or advertising-technology providers beyond the JP/Politikens Hus and Berlingske matter, and whether any subsequent action clarifies the specific design threshold that triggers a dark-pattern finding under the no-analytics-exemption, Danish-language-consent standard.

D7 · AdTech & Marketing — Full Module Record6 sub-modules · 56 words · 5 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Active soft-law/guidance activity on AI and ADM; biometric/genetic sub-modules and state-surveillance carve-outs remain evidence gaps at Denmark-specific level.

Primary frameworkGDPR Art 22 (ADM) directly applicable; EU AI Act (Regulation (EU) 2024/1689) as it enters into force, with national competent authority designation ongoing
Supervisory authorityDatatilsynet
Traffic-light rationale — AmberActive soft-law/guidance activity on AI and ADM; biometric/genetic sub-modules and state-surveillance carve-outs remain evidence gaps at Denmark-specific level.
Periodic update · new data 2026-10-25

Algorithmic, Biometric & Surveillance Governance

Denmark's first implementing measure under the EU AI Act, Act No. 467 of 14 May 2025, entered into force on 2 August 2025 and designates three bodies jointly as national market-surveillance authorities under the regulation: Digitaliseringsstyrelsen, Datatilsynet and Domstolsstyrelsen. This tripartite designation is notable for bringing Denmark's data-protection authority into a formal AI-oversight role alongside its existing GDPR mandate, and for including the courts administration body, Domstolsstyrelsen, reflecting the AI Act's particular concern with AI systems used in judicial and law-enforcement contexts. This claim is sourced from a secondary legal guide rather than the Danish gazette text directly, which is worth noting as a modest caveat on the precise designation language even though the underlying fact of the designation itself is corroborated.

The practical significance of this designation is that Denmark now has an identified institutional structure for AI Act market surveillance, even though the detailed operational division of labour between the three designated authorities, and the specific enforcement powers each will exercise in practice, have not been confirmed at a provision level this period. Datatilsynet's inclusion in this structure means the authority now carries both a data-protection and an AI-governance supervisory role, which could become relevant where an AI system's deployment also raises GDPR-relevant processing questions.

Outlook

The item to watch is confirmation of the designation and division of responsibilities directly from the Danish gazette text or from Digitaliseringsstyrelsen, Datatilsynet or Domstolsstyrelsen themselves, which would upgrade this from a secondary-sourced designation to a primary-confirmed one. How the three authorities coordinate in a case involving both AI Act and GDPR exposure, as could arise from the current CPR-register incident if an automated system were implicated, is also worth monitoring.

Periodic update · new data 2026-10-11

Algorithmic, Biometric & Surveillance Governance

Denmark is participating as one of seven pilot member states in the European Commission's open-source age-verification application, a project intended to enforce the EU's proposed social-media age restrictions for pre-teen users. EU-wide availability of the app is expected by the end of 2026. The pilot's design issues single-use proofs of age through a nationally designated, vetted issuer; the verifying application itself is not designed to retain identity documents or biometric data from the user. This architecture is intended to allow platforms to confirm that a user meets an age threshold without the verifying app becoming a repository of sensitive identity or biometric material in its own right.

Denmark's participation in the pilot sits alongside the domestic draft social-media age-limit bill (see Children & Vulnerable Groups), and the two measures are best read together: the domestic bill sets the substantive age threshold and the obligation it is intended to trigger, while the EU pilot app supplies prospective technical infrastructure for verifying that threshold in practice. Neither measure has yet reached a settled, in-force state as at this cycle; the pilot's EU-wide rollout timeline extends to end-2026, and the domestic bill remains in its post-consultation phase.

Outlook

The EU pilot's progress toward end-2026 EU-wide availability is the principal item to watch for this module, since broader geographic and technical maturity of the app would materially affect how enforceable an age threshold like that proposed in Denmark's draft bill could become in practice. No Danish-specific operational detail on the pilot beyond its member-state participation was located this cycle.

Periodic update · new data 2026-09-28

Algorithmic, Biometric & Surveillance Governance

Denmark's AI-governance framework is emerging as a distinct compliance track alongside GDPR, anchored in Law No. 467/2025, in force since August 2025. The Act provides the national legal basis for administrative enforcement measures giving effect to the EU AI Act, including injunctions, temporary bans, product recalls, and bødeforelæg, administrative fine settlements. Its scope, however, is understood to be limited to enforceability and sanctions for the AI Act's prohibited-practices provisions specifically, rather than the Act's full substantive scope. A comprehensive successor law addressing the complete EU AI Act framework was reported to be under development as of May 2026, meaning the current Danish AI-enforcement architecture is a partial, interim structure rather than a finished transposition.

A structurally notable feature is that, as with GDPR fines, AI Act penalties in Denmark are understood to run through the criminal, court-imposed route rather than a direct administrative fining mechanism, mirroring the same court-mediated pattern that characterises Denmark's general data-protection enforcement architecture under the Recital 151 carve-out. This means the two frameworks, GDPR and the AI Act, share a common national enforcement design philosophy in Denmark even though they derive from entirely separate EU instruments.

For entities deploying AI systems that fall within the AI Act's prohibited-practices category and that operate in or target the Danish market, the current interim law already carries real enforcement teeth, injunctions, temporary bans, and product recalls are all available under it, even though the broader AI Act compliance landscape awaits the successor legislation.

Outlook

The principal item to track is the progress of Denmark's comprehensive AI Act successor law, last reported as under development as of May 2026, and whether it maintains the same court-mediated enforcement philosophy or introduces a direct administrative fining power distinct from the GDPR model.

D8 · AI, Biometrics & Automated — Full Module Record6 sub-modules · 58 words · 6 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Core consent-age derogation confirmed; social-media minimum-age policy is still in development, and dependent-adult/education sub-modules are evidence gaps.

Primary frameworkDatabeskyttelsesloven §6(3) (age of digital consent); prospective Danish 'digital majority' social-media proposals
Supervisory authorityDatatilsynet
Traffic-light rationale — AmberCore consent-age derogation confirmed; social-media minimum-age policy is still in development, and dependent-adult/education sub-modules are evidence gaps.
Periodic update · new data 2026-10-11

Children & Vulnerable Groups

A draft bill was shared for public consultation on 7 September 2026, with the consultation period closing 5 October 2026, proposing a national minimum age of fifteen for children's access to certain social-media and video-sharing services. The prohibition, as drafted, applies to the child rather than to the platform: it is not framed as a direct compliance obligation on covered services, consistent with the fact that platform-level obligations in this area are already fully harmonised at EU level through the Digital Services Act. The draft is designed to apply retroactively to existing accounts, meaning a child already using a covered service below the new age threshold would fall within the prohibition on commencement rather than being grandfathered. Notably, the draft carries no enforcement or sanctions provisions directed at children themselves or at their parents; its practical mechanism instead works indirectly, by giving platforms a domestic Danish age threshold intended to trigger their own age-verification duties under Article 28 of the Digital Services Act.

The draft bill implements a political agreement on digital child protection reached on 7 November 2025, placing this cycle's development as the legislative follow-through on a commitment made roughly ten months earlier. Whether the bill has been tabled in the Folketing following the close of consultation on 5 October 2026, and on what timetable it might come into force, was not located this cycle and is recorded as an open gap.

Outlook

The consultation's close on 5 October 2026 is the immediate marker against which the next procedural step, tabling in the Folketing, should be watched. No expected or legal effective date for the bill's entry into force has yet been identified. The measure's reliance on triggering platforms' existing Digital Services Act Article 28 duties, rather than creating a new direct platform obligation, means its practical effect will also depend on how those EU-level duties are themselves enforced against the platforms operating in Denmark.

D9 · Children's Privacy — Full Module Record5 sub-modules · 48 words · 3 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

#

Active enforcement casework confirmed, but the court-mediated fining process (rather than direct administrative fines) is a structural constraint on Datatilsynet's own powers, and collective-redress specifics remain unevidenced.

Primary frameworkGDPR Art 83(9)/Recital 151 as implemented via Danish criminal-referral procedure; GDPR Arts 77-84
Supervisory authorityDatatilsynet
Traffic-light rationale — AmberActive enforcement casework confirmed, but the court-mediated fining process (rather than direct administrative fines) is a structural constraint on Datatilsynet's own powers, and collective-redress specifics remain unevidenced.
Periodic update · new data 2026-11-04

Enforcement & Redress

Denmark's supervisory posture has shifted toward active investigation following the disclosure of two large-scale breaches within the same window. Unauthorised third-party access to the national civil registration (CPR) system is understood to have occurred intermittently over a period of twenty-one days and seventeen hours between 10 September and 2 October 2026, and Datatilsynet is understood to have moved the matter to a formal investigation on 23 October 2026. Separately, the Technical University of Denmark disclosed on 2 October 2026 a breach of its DTUBasen identity-and-access-management system, potentially affecting up to two hundred thousand users, and is understood to have notified both Datatilsynet and the National Special Crime Unit (NSK) by 4 October 2026. Neither matter has produced a published Datatilsynet decision as at 1 November 2026, and the regulator's own case-file text for either investigation has not been directly retrieved, so the eventual findings, and whether either matter proceeds to referral, remain open.

Denmark's enforcement architecture itself is structurally distinct from most other member states: Datatilsynet does not hold a direct power to impose administrative fines under the General Data Protection Regulation. Enforcement is instead understood to run through the Danish courts, which impose fines as a criminal sanction under the Article 83(9)/Recital 151 model, with Datatilsynet's role limited to referral. This structural feature was not independently re-verified against a primary source in the present period and is carried forward from the standing position recorded under the Danish Data Protection Act (Lov om databeskyttelse) of 2018. It matters directly to how the two open breach matters are likely to be resolved: were either to result in a fine, that fine would be set by a court on referral from Datatilsynet rather than by the regulator directly, a materially longer and more adversarial path than the administrative-fine model used elsewhere.

Outlook

Two simultaneous, large-scale breach investigations opening in close succession point to a heightened Datatilsynet enforcement posture heading into the final quarter of 2026, although the regulatory outcome of either matter cannot yet be determined. Organisations operating in Denmark with exposure to large-scale identity or civil-registration data should expect continued scrutiny of breach-notification timeliness and access controls while these two matters remain open, with any eventual sanction following the slower, court-mediated route distinctive to the Danish enforcement model.

Periodic update · new data 2026-10-25

Enforcement & Redress

The CPR-register breach is this period's lead enforcement and redress development for Denmark, and the political response has been swift. The Minister for Research, Education and Digitalisation, Christina Egelund, publicly acknowledged that security around the CPR system had not been good enough, and requested a formal security review in the wake of the disclosure. Parties in the Folketing were convened for a briefing on the leak, a step reflecting both the scale of the incident, touching roughly 8.8 million individuals, and its sensitivity given the CPR number's role as a foundational identity credential across Danish public and private-sector systems.

Denmark's enforcement architecture means the practical path from this incident to any eventual fine runs through a specific procedural sequence: Datatilsynet, as the independent GDPR supervisory authority, lacks the power to impose administrative fines itself. It can only refer a matter to the police for prosecution, with a court ultimately setting the fine amount following any prosecution. This procedural structure is a standing feature of the Danish enforcement model, not new this period, but it is directly relevant to assessing the realistic timeline for any financial consequence flowing from the CPR incident: a court-mediated fine process is necessarily slower than a direct regulatory penalty decision of the kind available to supervisory authorities in some other EU member states.

No Datatilsynet finding, referral or fine recommendation connected to the CPR incident has issued as of this period. The inquiry into allocation of responsibility remains open, and the ministerial security review ordered in response has not yet reported.

Outlook

The markers to watch are the findings of the ministerial security review, any Datatilsynet decision to refer the CPR matter to the police following its Article 32 inquiry, and, should a referral occur, the eventual court proceeding that would determine any fine. Given the court-mediated structure of Danish GDPR enforcement, a final financial outcome connected to this incident is likely to take considerably longer to materialise than the breach disclosure itself.

Periodic update · new data 2026-09-28

Enforcement & Redress

Denmark's enforcement architecture remains structurally distinctive within the EU: Datatilsynet cannot issue administrative GDPR fines directly. Under the Recital 151 carve-out, a mechanism shared with only one other member state, Datatilsynet refers cases to the police with a recommended fine amount, and a court, not the regulator, imposes any resulting penalty as a criminal sanction. This structural fact is unchanged this cycle, but the practical enforcement environment around it is intensifying: the Western High Court's DKK 500,000 fine against the Region of Southern Denmark for a GDPR security-measures failure, reported April 2026, demonstrates the court-referral route remains an active and consequential enforcement channel rather than a rarely used formality.

On the private-redress side, the Western High Court awarded EUR 335 in non-material Article 82 compensation in August 2025 for the wrongful sharing of health data by a municipality, a modest sum that the claimant has appealed to the Supreme Court on the question of quantum. This case is a live private-right-of-action matter, and the outcome of the Supreme Court appeal will be informative as to how Danish courts calibrate non-material-damage awards under Article 82 relative to other EU member states, where such awards have varied considerably.

Taken together, Denmark's enforcement posture combines an unusual institutional mechanism, court-mediated rather than regulator-imposed fining, with an active and, on the evidence of the Region of Southern Denmark and cookie-enforcement cases, intensifying practical enforcement tempo. The structural mechanism itself creates no reduction in practical exposure for controllers; if anything, the unpredictability of judicial fine-setting, absent a published administrative tariff, may increase uncertainty for entities assessing their own risk.

Outlook

The items to watch are the outcome of the Supreme Court appeal on the EUR 335 Article 82 quantum question, and whether further court-referred cases follow the Region of Southern Denmark pattern in setting reference points for security-of-processing fines against Danish public authorities.

D10 · Enforcement & Redress — Full Module Record6 sub-modules · 81 words · 10 traced claims · Re-verified 2026-11-04

The decision headline, regulatory posture (Amber), primary framework, and supervisory authority above are open on the Free Explore layer. Register free with a business email for 3 full-record passes a month, or unlock all 170 jurisdictions with Single-Monitor or Portfolio Pro (1 seat) or Firm (up to 8 seats + client-advisory rights).

No categories match.

Filters combine as OR inside a group and AND across groups.

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-04. A year-precision row is never promoted into a tighter band.

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

Audit trail

Machine checkChallenged on 3 Nov 2026: not upheld (20 confirmed against the cited source; 3 contradicted by the cited source; 16 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 (37 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. 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. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer mechanisms
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties