Law / Luxembourg

Luxembourg

All 28 named instruments researched to a stage, across nine of the ten areas of law we track: 27 in force and 1 proposed. As of .

When each starts27 of 28 carry a date, 1 does not. Earlier is before 2014.
Before 2014: 7 instruments (7 in force) earlier 2014: 0 instruments 2015: 0 instruments ’15 2016: 0 instruments 2017: 0 instruments 2018: 8 instruments (8 in force) 2019: 0 instruments 2020: 0 instruments ’20 2021: 1 instrument (1 in force) 2022: 4 instruments (4 in force) 2023: 0 instruments 2024: 2 instruments (2 in force) 2025: 3 instruments (3 in force) 2026: 2 instruments (2 in force) ’26 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law 1
  2. Privacy law 9
  3. Scraping law 3
  4. Cybersecurity law 4
  5. Communications law 4
  6. Content moderation law 3
  7. Product and AI liability law 1
  8. Digital accessibility law not researched
  9. Age gating law 1
  10. Reuse law 2

AI law1 instrument, 1 proposed

Research summary (169 words)

The EU AI Act (Regulation (EU) 2024/1689) applies directly in Luxembourg and is not restated here as Luxembourg law.

The national law the AI Act requires to designate Luxembourg's notifying authorities, market surveillance authorities and single point of contact, and to set national administrative-fine ceilings and procedure, is the subject of the Government's Projet de loi 8476, deposited , which would designate the Commission nationale pour la protection des donnees (CNPD) as the default market surveillance authority and single point of contact, with sector derogations to the judicial control authority, the Commission de surveillance du secteur financier, the Commissariat aux assurances, ILNAS, the Institut luxembourgeois de regulation, the Agence luxembourgeoise des medicaments et produits de sante, and the Autorite luxembourgeoise independante de l'audiovisuel (ALIA) for the synthetic-content marking and disclosure duties of Article 50(2) and Article 50(4).

The Conseil d'Etat delivered its opinion on , and as of the Chambre des Deputes' dossier shows the bill in committee with no vote recorded.

AI governance

Projet de loi 8476, National Designation of AI Act Authorities and Penalties

Projet de loi 8476 portant mise en oeuvre de certaines dispositions du reglement (UE) 2024/1689 (Luxembourg, depose le 23 decembre 2024, avis du Conseil d'Etat du 10 juillet 2026)Chambre des Deputes, official consolidated legislative dossier for Projet de loi 8476

Proposed. proposed Not law. It binds no one unless it is enacted.

In committee, dated , as of . Binds public and private bodies.

What this law does

The bill would designate the Commission nationale pour la protection des donnees (CNPD) as Luxembourg's default AI Act market surveillance authority and single point of contact, with derogations to the judicial control authority for AI systems used by the courts, the Commission de surveillance du secteur financier and the Commissariat aux assurances for AI systems placed on the market, put into service or used by an entity each of them supervises, the Institut luxembourgeois de la normalisation (ILNAS) for the product markets in points 1 to 10 of Annex I and for point 2 of Annex III, the Institut luxembourgeois de regulation for deployers of point 2 Annex III systems that are essential or important entities under the cybersecurity law, the Agence luxembourgeoise des medicaments et produits de sante for the medical-device markets in points 11 and 12 of Annex I, and the Autorite luxembourgeoise independante de l'audiovisuel (ALIA) for the synthetic-content marking and disclosure duties of Article 50(2) and Article 50(4).

It would empower each market surveillance authority to impose a warning, a reprimand, or an administrative fine, and would set a fine of up to 35,000,000 euros or 7 percent of worldwide annual turnover for a breach of the Article 5 prohibited-practices ban, up to 15,000,000 euros or 3 percent for a breach of the other operator and notified-body obligations the bill lists, and up to 7,500,000 euros or 1 percent for supplying incorrect, incomplete or misleading information to a notified body or national authority.

The bill also requires the CNPD to stand up at least one AI regulatory sandbox by . As of the Chambre des Deputes' own consolidated dossier, the Conseil d'Etat delivered its opinion on and no vote or adoption is recorded.

What it requires

Privacy law9 instruments, 9 in force

Research summary (124 words)

Luxembourg's private-sector regime is the General Data Protection Regulation (GDPR) plus the Act of on the organisation of the National Data Protection Commission (CNPD) and the general data protection framework, in effect from . The Act's chapter headed "Processing of special categories of personal data" consists of one article, which prohibits processing genetic data for the controller's rights in labour law and insurance (Article 66).

A voiceprint or faceprint captured for identification is governed by GDPR Article 9. A CNPD decision taken under the Act can be appealed to the Administrative Tribunal, which rules on the merits (Article 55). As at , the latest consolidated text of the Act of is the version applicable from .

Breach notification

GDPR Articles 33-34, Breach Notification in Luxembourg

Regulation (EU) 2016/679, Arts. 33-34Official Journal text, EUR-Lex, Regulation (EU) 2016/679

In force since . Binds public and private bodies.

What this law does

A controller must notify the CNPD without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in Luxembourg, and must notify affected individuals without undue delay where the breach is likely to result in a high risk to their rights and freedoms. No Act of derogation from this timeline is identified.

What it requires

Comprehensive regime

Act of 1 August 2018 on the Organisation of the CNPD and the General Data Protection Framework

Loi du 1er août 2018 portant organisation de la Commission nationale pour la protection des données et du régime général sur la protection… des données (Mémorial A n° 686 du 16 août 2018)CNPD official PDF (cnpd.public.lu)

In force since . Binds public and private bodies.

What this law does

Luxembourg's private-sector regime is the General Data Protection Regulation (GDPR) plus the Act of on the organisation of the National Data Protection Commission (CNPD) and the general data protection framework, in effect from , which repealed the prior data protection law. The Act supplies domestic derogations and procedural rules and establishes the CNPD's own organisation.

Its chapter on special categories of personal data prohibits processing genetic data for the controller's rights in labour law and insurance (Article 66); see the sensitive-categories instrument below.

What it requires

Labour Code Article L.261-1, Monitoring of Employees and Personal Data in the Employment Relationship

Code du travail, Art. L.261-1 (Titre VI, loi du 1er août 2018)Legilux, Code du travail, Article L.261-1

In force since . Binds private bodies.

What this law does

An employer may process personal data to monitor employees in the employment relationship only in the cases of General Data Protection Regulation (GDPR) Article 6(1)(a) to (f) and in accordance with the article.

The employer must first inform the joint committee or, failing it, the staff delegation or, failing that, the Labour and Mines Inspectorate, and for statutory staff the staff representation bodies, with a detailed description of the purpose, how the system works, any retention period or criteria and a formal commitment not to use the data for another purpose.

Where the monitoring serves safety and health needs, production or performance control that is the only means to determine exact pay, or flexible working hours, Articles L.211-8, L.414-9 and L.423-1 apply unless a legal obligation requires the processing.

The staff delegation or, failing it, the employees concerned may within fifteen days of the prior information ask the Commission nationale pour la protection des données for an opinion on the project, which suspends the project during the month the Commission has to reply. Employees may complain to the Commission, and a complaint is neither a serious nor a legitimate ground for dismissal.

What it requires

Cross border transfer

GDPR Chapter V, Cross-Border Transfer of Personal Data from Luxembourg

Regulation (EU) 2016/679, Arts. 44-49Official Journal text, EUR-Lex, Regulation (EU) 2016/679

In force since . Binds public and private bodies.

What this law does

Transferring personal data of a person in Luxembourg outside the European Economic Area requires a European Commission adequacy decision, Standard Contractual Clauses, Binding Corporate Rules, or a narrow Article 49 derogation, backed by the Article 83(5) top fine tier. The Act of exempts processing carried out for the sole purpose of journalism or academic, artistic or literary expression from Chapter V of the General Data Protection Regulation (GDPR) (Article 62).

What it requires

Data subject rights

GDPR Article 22, Automated Decisions as Applied in Luxembourg

Regulation (EU) 2016/679, Arts. 13(2)(f), 14(2)(g), 15(1)(h) and 22Official Journal text, EUR-Lex, Regulation (EU) 2016/679

In force since . Binds public and private bodies.

What this law does

General Data Protection Regulation (GDPR) Article 22 gives a person in Luxembourg the right not to be subject to a decision based solely on automated processing, including profiling, that produces legal effects or similarly significantly affects them, unless the decision is necessary for a contract with them, authorised by a law that safeguards their rights, or based on their explicit consent.

Where it rests on a contract or consent, the controller must at least let the person obtain human intervention, express their point of view and contest the decision.

Under Article 22(4), such a decision may not rest on the special categories of personal data in Article 9(1) unless the person gave explicit consent or the processing is necessary for reasons of substantial public interest on the basis of proportionate Union or Member State law, with suitable safeguards in place.

Articles 13(2)(f), 14(2)(g) and 15(1)(h) require the controller to tell the person that such decision-making takes place, with meaningful information about the logic involved and its significance and envisaged consequences for them, at collection, within the Article 14(3) period where the data came from another source, and on an access request.

The Loi du 1er aout 2018 adds no rule of its own on automated decisions.

What it requires

GDPR Articles 12-21 and Loi du 1er août 2018 Article 63, Data Subject Rights in Luxembourg

Regulation (EU) 2016/679, Arts. 12-21; Loi du 1er aout 2018, Arts. 63, 65Official Journal text, EUR-Lex, Regulation (EU) 2016/679

In force since . Binds public and private bodies.

What this law does

Under General Data Protection Regulation (GDPR) Articles 12 to 21, a person in Luxembourg can ask a controller for access to their personal data and for its rectification, erasure, restriction or portability, or object to its processing, and the controller must answer within one month, a period it may extend by two further months for complex or numerous requests.

The Loi du 1er aout 2018 narrows these rights for research: a controller processing for scientific or historical research or for statistics may depart from the rights of access, rectification, restriction and objection to the extent they would make that purpose impossible or seriously impair it, provided it takes the additional safeguards Article 65 lists.

What it requires

Enforcement supervision

GDPR Articles 82-83 and CNPD Enforcement in Luxembourg

Regulation (EU) 2016/679, Arts. 82-83GDPR Arts. 82-83

In force since . Binds public and private bodies.

What this law does

Under Article 48(1) of the Act the CNPD imposes administrative fines as set out in General Data Protection Regulation (GDPR) Article 83, save against the State and municipalities. A CNPD decision taken under the Act can be appealed to the Administrative Tribunal, which rules on the merits (Article 55).

What it requires

Sensitive categories

GDPR Article 9, Special Categories of Personal Data as Applied in Luxembourg

Regulation (EU) 2016/679, Art. 9GDPR Art. 9(1)

In force since . Binds public and private bodies.

What this law does

General Data Protection Regulation (GDPR) Article 9(1) classifies biometric data processed for unique identification as a special category. The Act of has a chapter headed "Processing of special categories of personal data" that consists of one article, which prohibits processing genetic data for the controller's rights in labour law and insurance (Article 66). A voiceprint or faceprint captured for identification purposes is therefore governed in Luxembourg by GDPR Article 9 alone.

What it requires

Insurance Sector Law Article 181-3, Lawful Processing of Health Data by Insurers and Reinsurers

Loi du 6 février 2025 modifiant la loi modifiée du 7 décembre 2015 sur le secteur des assurances, Art. 181-3Legilux, Loi du 6 février 2025, Mémorial A n° 37

In force since . Binds private bodies.

What this law does

Processing of health data other than genetic data is lawful, under General Data Protection Regulation (GDPR) Article 9(2)(g), when necessary for pre-contractual measures in insurance or reinsurance or for performing an insurance or reinsurance contract, subject to professional secrecy and to appropriate measures.

The measures are a data protection officer, impact assessments, anonymization or pseudonymization or functional separation, encryption in transit with state-of-the-art key management, access restrictions, logging of the reason, date, time and person for each access, staff awareness, regular independent audit, sectoral codes of conduct and an internal policy on the principles of GDPR Article 5.

Each controller and processor must document and justify internally any exclusion of the data protection officer, impact assessment, anonymization, audit or code of conduct measures and keep the documentation available to the Commission nationale pour la protection des données. In no case may a controller or processor derogate from the measures in letters d), e), f), g) and j).

What it requires

Scraping law3 instruments, 3 in force

Research summary (502 words)

Luxembourg has no scraping-specific statute, so general law governs each dimension separately.

The Code penal's articles 509-1 to 509-7 punish whoever fraudulently accesses or remains in an automated or non-automated data-processing or transmission system, with a heavier tier where the access or remaining suppresses or alters data or disrupts the system's functioning, the same tier for producing, selling, holding or distributing a device or key meant to commit the offence, and the completed offence's own penalty for an attempt or a preparatory association.

The provision carries no security-measure element: reading a public, unauthenticated page without deceit falls outside a plain reading of the fraudulent-access limb, while a crawler that keeps requesting pages once told the operator no longer wants it there risks the separate fraudulent-remaining limb, and no reported Luxembourg judgment yet applies either limb to a scraper.

Luxembourg's copyright statute, as amended in 2022 to transpose the Digital Single Market Directive, adds a national text-and-data-mining exception at article 10, points 15 and 16, permitting reproduction and extraction of lawfully accessible works for mining unless the rightholder has expressly and appropriately reserved that use, including by a machine-readable means for content available online, a reservation research organizations and public libraries, museums, archives and film or sound heritage institutions need not observe.

That reservation, where made, has direct legal force: a disallow expressed through it removes the exception's protection for the content it reaches. The same statute confers a sui generis database right at article 67, letting a database producer forbid extraction or reuse of the whole or a substantial part of its contents.

Regulation (EU) 2024/1689 (the AI Act), directly applicable in Luxembourg, binds a provider of a general-purpose AI model placed on the EU market to a policy respecting that same reservation under its article 53.

The Code civil's general rule on pre-drafted general conditions, article 1135-1, decides terms-of-service enforceability generally: a website's terms bind a visitor only if the visitor could know them when it signed up and must, given the circumstances, be taken to have accepted them, so terms actively agreed to at account creation bind a crawler while terms merely posted behind a link bind only if the crawler had that notice.

Luxembourg recognizes no separate trespass-to-chattels claim for server strain caused by crawling; ordinary delictual liability under the Code civil remains a separate avenue for proven harm.

Luxembourg's former general unfair-competition clause, the loi modifiée du 30 juillet 2002, article 14, was repealed effective by the loi du 23 décembre 2016 sur les ventes en soldes et sur trottoir et la publicité trompeuse et comparative, whose own scope reaches only sales periods, street vending and misleading or comparative advertising, without reenacting a general unfair-competition clause; no statute currently states one, so a scraping competitor dispute would rest on ordinary delictual liability under the Code civil, the same avenue as a server-strain claim.

Personal data scraped from a Luxembourg website remains subject to General Data Protection Regulation (GDPR) duties, addressed under this jurisdiction's privacy topic and not restated here.

Computer misuse

Code penal, Computer Misuse Offences (Unauthorized Access, Interference, Data Introduction, Devices, Attempt, Association)

C.pen. arts. 509-1 a 509-7Code penal, official consolidated text, Journal officiel du Grand-Duche de Luxembourg (Legilux)

In force since . Binds public and private bodies.

What this law does

Article 509-1 punishes fraudulently accessing or remaining in all or part of an automated or non-automated data-processing or transmission system with two months to two years of imprisonment and a fine of 500 to 25,000 euros, rising to four months to two years and 1,250 to 25,000 euros where data is suppressed or modified or the system's functioning is altered.

A second paragraph, added by the Loi du 29 juillet 2023, punishes with the same penalties a person who holds authorisation to access a system processing personal data but processes that data for purposes other than those for which the access was granted. Because the offence's trigger is fraudulent access, a scraper reading a public, unauthenticated page without defeating any access control falls outside a plain reading of the provision.

Article 509-2 punishes intentionally interfering with or falsifying the functioning of an automated or non-automated data-processing or transmission system, and article 509-3 punishes intentionally introducing, suppressing or altering its data, each with three months to three years of imprisonment and 1,250 to 12,500 euros.

Article 509-3 also punishes, with the same penalties, intentionally intercepting data during non-public transmissions to, from or within such a system, a paragraph the Loi du 18 juillet 2014 added.

Article 509-4 raises the penalty to four months to five years and 1,250 to 30,000 euros where any of these offences causes a transfer of money or monetary value for economic gain, and a amendment added the same penalty for committing any of the article 509-1 to 509-3 offences against an information system of a critical infrastructure, or causing serious harm to such a system by committing them; article 509-5 punishes producing, selling, holding or distributing a device or electronic key intended to commit these offences at the same level.

Attempt and participation in an association formed to commit these offences are punished the same as the completed offence, under articles 509-6 and 509-7. Article V of the Loi du 15 juillet 1993 inserted into the Code penal a section on certain computer offenses, Articles 509-1 to 509-7. That Law took effect on .

What it requires

Copyright and text and data mining (TDM)

Loi du 18 avril 2001 sur les droits d'auteur, Text and Data Mining Exception (Art. 10, points 15 and 16)

Loi du 18 avril 2001 sur les droits d'auteur les droits voisins et les bases de donnees, art. 10, points 15 et 16, ajoutes par la loi du 1er avril 2022 portant transposition de la directive (UE) 2019/790Loi du 18 avril 2001 sur les droits d'auteur

In force since . Binds public and private bodies.

What this law does

Article 10, point 16, added by the Loi du 1er avril 2022 transposing the Digital Single Market Directive, permits reproductions and extractions of lawfully accessible works for text and data mining without the rightholder's authorization, unless the rightholder has expressly and appropriately reserved that use, including by machine-readable means for content made available online.

Article 10, point 15 gives research organizations and publicly accessible libraries, museums, archives and film or sound heritage institutions the same permission for scientific research text and data mining, without being subject to that reservation. The statute defines text and data mining as any automated analytical technique to analyze text and data in digital form in order to generate information such as patterns, trends and correlations.

What it requires

Database right

Loi du 18 avril 2001 sur les droits d'auteur, Sui Generis Database Right (Art. 67)

Loi du 18 avril 2001 sur les droits d'auteur, les droits voisins et les bases de donnees, art. 67Loi du 18 avril 2001 sur les droits d'auteur

In force since . Binds public and private bodies.

What this law does

A database producer may forbid extraction or reuse of the whole, or a qualitatively or quantitatively substantial part, of the database's contents, and may also forbid the repeated and systematic extraction or reuse of insubstantial parts where that conflicts with normal exploitation of the database or unreasonably prejudices the producer's legitimate interests.

Extraction is defined as the permanent or temporary transfer of all or a substantial part of the contents to another medium by any means, and reuse as any form of making the contents available to the public, excluding public lending in both cases. The right is part of the original Loi du 18 avril 2001, which transposed the EU Database Directive.

The Loi du 1er avril 2022, which transposed the Digital Single Market Directive, added to article 68 new paragraphs 2 to 4, the first of which applies the exceptions of article 10, points 15 and 16, among others, to the rights of a database producer.

What it requires

Cybersecurity law4 instruments, 4 in force

Research summary (462 words)

Luxembourg's NIS2 transposition, the loi du 5 mai 2026 concernant des mesures destinées à assurer un niveau élevé de cybersécurité, is enacted and in force. Signed on , published in the Journal officiel (Mémorial A, No. 225) on , and in force since , it repeals (Article 30) the prior NIS1 transposition, the loi du 28 mai 2019, outright.

Article 12 binds an entité essentielle or entité importante, as Article 11 defines them against the Annexe I and Annexe II sector lists together with the medium-enterprise size threshold of Commission Recommendation 2003/361/EC, to appropriate and proportionate cybersecurity risk-management measures across ten baseline categories, transposing NIS2 Article 21; Article 14 binds the same entities to a graduated incident-notification clock to the competent authority (a 24-hour early warning, a 72-hour notification, and a final report within one month), transposing NIS2 Article 23.

Annexe II point 6 names an online-marketplace provider, an online-search-engine provider and a social-networking-services-platform provider among the digital providers both duties reach expressly, alongside the wider sector classes (energy, transport, health, digital infrastructure, banking, financial-market infrastructure, public administration and others).

The Institut luxembourgeois de régulation (ILR) is the general competent authority for cybersecurity and supervision under the law (Article 3); the Commission de surveillance du secteur financier (CSSF) is the competent authority instead for the banking sector and the financial-market-infrastructure sector, and for the digital-infrastructure and ICT-service-management sectors as far as CSSF's own supervision reaches, which is where DORA-covered financial entities are supervised, under the national layer the Loi du 1er juillet 2024 sets.

Violation of Article 12 or Article 14 carries an administrative fine of up to EUR 10,000,000 or 2 percent of worldwide annual turnover for an essential entity, and up to EUR 7,000,000 or 1.4 percent of turnover for an important entity, whichever is higher in each case (Article 26(4)-(5)), mirroring NIS2 Article 34's two-tier structure exactly; the competent authority may also attach a daily astreinte capped at EUR 1,250 and EUR 25,000 in total (Article 26(7)), and enforcement runs through an administrative appeal (recours en réformation) to the tribunal administratif rather than through any private right of action or criminal offence.

Luxembourg has no general reasonable-security or information-security-programme statute with no sector gate; the closest general duty is General Data Protection Regulation (GDPR) Article 32's security-of-processing obligation, and personal-data breach notification under GDPR Articles 33-34 sits in the privacy topic rather than here, as does the Act of on the organisation of the CNPD.

A related but separate law of the same date, the loi du 5 mai 2026 sur la résilience des entités critiques, transposes the CER Directive's physical-resilience duties for critical entities and is not restated here; it feeds Article 11(1)(6)'s essential-entity designation but does not itself carry a cybersecurity duty.

Sector security regimes

Loi du 1er juillet 2024, DORA Competent Authorities, Sanctions and ICT Continuity Duties of Financial Firms

Art. 5 et 20-21 à 20-25, Loi du 1er juillet 2024 (Mémorial A n° 271)Legilux, Loi du 1er juillet 2024 (Mémorial A n° 271 de 2024), Articles 5, 20-22, 20-24, 20-25 and 26

In force since . Binds public and private bodies.

What this law does

The Commission de surveillance du secteur financier (CSSF) and the Commissariat aux assurances (CAA) are the competent authorities in Luxembourg under Article 46 of the DORA Regulation (Regulation (EU) 2022/2554), each for the persons it supervises (Article 20-22).

CRR institutions must have adequate contingency and business continuity policies and plans, including ICT business continuity policies and plans and ICT response and recovery plans, which they establish, manage and test in accordance with Article 11 of the DORA Regulation (Article 5, inserting Article 53-21(2)).

For a breach of the DORA Regulation provisions the law lists, the CSSF and the CAA may order the person to stop and not repeat the conduct, order the cessation of a practice, fine a legal person up to 5,000,000 euro or up to 10 percent of its annual turnover, fine a natural person up to 5,000,000 euro, and make a public statement (Article 20-24).

They may fine from 250 to 250,000 euro a person who obstructs their supervisory powers, ignores their orders or knowingly gives them inaccurate or incomplete information (Article 20-24(3)). Their decisions may be challenged within one month before the administrative tribunal, which rules on the merits (Article 20-25). The law entered into force on (Article 26).

What it requires

Loi du 5 mai 2026 relative à la cybersécurité (NIS2), Risk-Management Measures for Essential and Important Entities

Loi du 5 mai 2026 concernant des mesures destinées à assurer un niveau élevé de cybersécurité, Art. 11, 12, 13Loi du 5 mai 2026, Journal officiel du Grand-Duché de Luxembourg (Legilux), Art. 12

In force since . Binds public and private bodies.

What this law does

Article 12 requires an entité essentielle (essential entity) or entité importante (important entity) to take technical, operational and organisational measures appropriate and proportionate to the risks threatening the security of the network and information systems it uses for its activities or services, and to eliminate or reduce the impact of incidents on the recipients of its services and on other services.

The measures must follow an all-hazards approach and cover at least ten categories: risk-analysis and information-system-security policy, incident handling, business continuity including backup and crisis management, supply-chain security, security in the acquisition, development and maintenance of systems including vulnerability handling and disclosure, evaluating the measures' own effectiveness, basic cyber-hygiene and training, cryptography and encryption policy, human-resources security, access control and asset management, and multi-factor or continuous authentication and secure communications, transposing NIS2 Article 21.

Annexe II point 6 names an online-marketplace provider, an online-search-engine provider and a social-networking-services-platform provider among the digital providers this duty reaches expressly. Annexe I point 10 separately reaches public-administration entities, as defined by Article 2. Article 13 requires the entity's management body to approve these measures and oversee their implementation, and states that the body may be held liable for the entity's violation of Article 12.

Article 1(8) disapplies the relevant provisions of this Law, including supervision and enforcement under Chapter 6, to an essential or important entity that a sector-specific Union legal act requires to adopt cybersecurity risk-management measures or to notify significant incidents with at least equivalent effect.

Regulation (EU) 2022/2554 (DORA) is, by its Article 1(2), the sector-specific Union legal act under Article 4 of Directive (EU) 2022/2555 for the financial entities identified as essential or important under national rules transposing that Directive.

What it requires

Vulnerability and incident reporting

Loi du 20 décembre 2024, Cybersecurity Certification Authority and Vulnerability Notices

Art. 1, 5 et 6, Loi du 20 décembre 2024 (Mémorial A n° 604)Legilux, Loi du 20 décembre 2024 (Mémorial A n° 604 de 2024), Articles 1, 5 and 6 and notice box

In force since . Binds private bodies.

What this law does

ILNAS is designated as the national cybersecurity certification authority responsible for the supervision tasks under Article 58 of the Cybersecurity Act (Regulation (EU) 2019/881) and for certification tasks for European cybersecurity certificates at the high assurance level (Article 1).

Holders of European cybersecurity certificates, issuers of EU declarations of conformity and conformity assessment bodies must inform the authority in writing within 72 hours of learning of a vulnerability or irregularity that may affect compliance with the security requirements of the certification of a product, service or process (Article 5(2)).

They must give the authority access to any document, person, equipment, premises, installation, site and means of transport it needs for its tasks (Article 5(1)). An accredited conformity assessment body must inform the authority of its accreditation, and of the certificates it issues, within 72 hours (Article 6). The law entered into force on .

What it requires

Loi du 5 mai 2026 relative à la cybersécurité (NIS2), Incident Notification

Loi du 5 mai 2026 concernant des mesures destinées à assurer un niveau élevé de cybersécurité, Art. 14Loi du 5 mai 2026, Journal officiel du Grand-Duché de Luxembourg (Legilux), Art. 14

In force since . Binds public and private bodies.

What this law does

Article 14 requires an entité essentielle or entité importante to notify the competent authority, without undue delay, of any incident with a significant impact on the provision of its services (an incident important), and, where appropriate, to notify the recipients of its services of a significant incident likely to affect the supply of those services.

An incident is significant if it has caused or is capable of causing severe operational disruption or financial loss to the entity, or has affected or is capable of affecting other natural or legal persons through considerable material, physical or moral damage.

The notification runs on a graduated clock: an early warning within 24 hours of becoming aware of the incident, a fuller notification within 72 hours giving an initial assessment of its severity and impact and any indicators of compromise, an intermediate report on request, and a final report within one month of the 72-hour notification (or a progress report followed by a final report if the incident is still ongoing at that point), transposing NIS2 Article 23.

A trust-service provider, by derogation from the 72-hour notification, notifies a significant incident affecting its trust services within 24 hours of becoming aware of it. The mere act of notifying an incident does not itself increase the notifying entity's liability, and the competent authority forwards the notification to the relevant computer security incident response team (CSIRT) and the single point of contact upon receiving it.

Article 1(8) disapplies the relevant provisions of this Law, including supervision and enforcement under Chapter 6, to an essential or important entity that a sector-specific Union legal act requires to adopt cybersecurity risk-management measures or to notify significant incidents with at least equivalent effect.

Regulation (EU) 2022/2554 (DORA) is, by its Article 1(2), the sector-specific Union legal act under Article 4 of Directive (EU) 2022/2555 for the financial entities identified as essential or important under national rules transposing that Directive.

What it requires

Communications law4 instruments, 4 in force

Research summary (203 words)

Luxembourg law on contacting a person and capturing a communication sits in the amended Act of on the protection of personal data in the electronic communications sector, which transposes the ePrivacy Directive.

Article 4 requires service providers and operators to guarantee the confidentiality of communications, prohibits anyone other than the user concerned from listening to, intercepting or storing communications without the user's consent, allows recording in lawful professional practice to prove a commercial transaction after the parties are informed, and allows storing or reading information on a subscriber's or user's terminal equipment only with consent given after clear and complete information.

Article 11 allows automated calling systems, fax machines and electronic mail to be used for direct marketing only with the recipient's prior consent, with a soft opt-in for a seller's own similar products or services, and extends the consent requirement to other means of unsolicited marketing communications. Both articles carry the same criminal penalty, and the National Commission for Data Protection is charged with their application.

A data subject's right to object to direct marketing is held in the privacy row for General Data Protection Regulation (GDPR) Articles 12-21 and the Act of Article 63, Data Subject Rights in Luxembourg.

Commercial messages

Act of 30 May 2005, Article 11(1), (2) and (4) to (6), Unsolicited Communications for Direct Marketing by Electronic Mail

Art. 11, paragraphes (1), (2) et (4) à (6), loi modifiée du 30 mai 2005Consolidated text of the amended Act of , published by the Service central de législation (legilux.public.lu)

In force since . Binds public and private bodies.

What this law does

Article 11, paragraph 1 of the Act of allows the use of automated calling and communication systems without human intervention, fax machines or electronic mail for direct marketing only where it targets a subscriber or user who has given prior consent.

Under paragraph 2, a provider that obtained its customers' electronic contact details in the course of a sale of a product or service may use them for direct marketing of its own similar products or services, provided that the customers are clearly and expressly given the right to object, free of charge and in a simple manner, when the details are collected and in each message, unless they refused such use from the outset.

Paragraph 4 prohibits sending electronic messages for direct marketing that disguise, conceal or misrepresent the identity of the sender on whose behalf the communication is made, or that give no valid address to which the recipient can send a request to stop such communications. Paragraph 5 applies paragraphs 1 and 3 to a subscriber who is a natural person.

What it requires

Device storage and tracking consent

Act of 30 May 2005, Article 4(3)(e), Consent for Storing or Reading Information on Terminal Equipment

Art. 4, paragraphe (3), lettre (e), loi modifiée du 30 mai 2005Consolidated text of the amended Act of , published by the Service central de législation (legilux.public.lu)

In force since . Binds public and private bodies.

What this law does

Article 4, paragraph 3, point (e) of the Act of provides that the prohibition on interception in paragraph 2 does not apply to storing information in, or obtaining access to information already stored in, the terminal equipment of a subscriber or user, on condition that the subscriber or user has given consent after receiving clear and complete information, among other things on the purposes of the processing.

Where technically possible and effective, the consent may be expressed through the appropriate settings of a browser or another application. The provision does not prevent technical storage or access whose sole purpose is to carry out the transmission of a communication over an electronic communications network, or that is strictly necessary for the provider to supply an information society service expressly requested by the subscriber or user. The Act of replaced point (e) with the consent wording. That Act entered into force on .

What it requires

Interception and recording consent

Act of 30 May 2005, Article 4(1) to (3), Confidentiality of Communications and Recording in Professional Practice

Art. 4, paragraphes (1) à (3), loi modifiée du 30 mai 2005Consolidated text of the amended Act of , published by the Service central de législation (legilux.public.lu)

In force since . Binds public and private bodies.

What this law does

Article 4, paragraph 1 of the Act of requires every service provider or operator to guarantee the confidentiality of communications made over a public communications network and publicly available electronic communications services, and of the related traffic data.

Paragraph 2 prohibits any person other than the user concerned from listening to, intercepting or storing the communications and the related traffic data, or subjecting them to any other means of interception or surveillance, without the consent of the user concerned. Paragraph 2 does not prevent the technical storage necessary for the routing of a communication.

Paragraph 2 does not affect the recording of communications and the related traffic data when it is carried out in lawful professional practice to provide proof of a commercial transaction or of any other commercial communication. The parties to the transactions or other commercial communications must be informed beforehand that recordings may be made, of the reason or reasons for recording, and of the maximum retention period of the recordings.

Recorded communications must be deleted as soon as the purpose is achieved and in any event when the legal period for challenging the transaction expires.

What it requires

Telephone contact

Act of 30 May 2005, Article 11(1), (3), (5) and (6), Unsolicited Calls and Automated Calling Systems for Direct Marketing

Art. 11, paragraphes (1), (3), (5) et (6), loi modifiée du 30 mai 2005Consolidated text of the amended Act of , published by the Service central de législation (legilux.public.lu)

In force since . Binds public and private bodies.

What this law does

Article 11, paragraph 1 of the Act of allows the use of automated calling systems without human intervention for direct marketing only where it targets a subscriber or user who has given prior consent. Paragraph 3 allows the sending of unsolicited communications for direct marketing by means other than those in paragraphs 1 and 2 only if the subscriber or user concerned has given prior consent. Paragraph 5 applies paragraphs 1 and 3 to a subscriber who is a natural person.

What it requires

Content moderation law3 instruments, 3 in force

Research summary (200 words)

Luxembourg applies the Digital Services Act directly and adds a national layer in the Loi du 4 avril 2025, which designates the Autorité de concurrence (Competition Authority) as the digital services coordinator, sets its powers of information request, inspection and action plan, and sets administrative fines of up to 6 percent of worldwide turnover and daily penalty payments of up to 5 percent of average daily turnover.

The same law repeals title VI of the loi modifiée du 14 août 2000 relative au commerce électronique, the title on the liability of intermediary service providers that held the hosting exemption in article 62, so the exemption now comes from the Digital Services Act itself.

The Loi du 24 juillet 2024 implements the Terrorist Content Online Regulation: the minister responsible for the Grand-Ducal Police issues removal and blocking orders, the Haut-Commissariat à la protection nationale supervises specific measures, and breaches carry prison terms and fines. The Loi du 18 avril 2001 on copyright, in article 70 bis inserted by the Loi du 1er avril 2022, holds the liability regime for online content-sharing service providers. The Digital Services Act's own duties are held with the European Union's page and are not restated here.

Notice and action

Loi du 18 avril 2001 sur les droits d’auteur, article 70 bis (Online Content-Sharing Service Providers)

Loi du 18 avril 2001 sur les droits d’auteur, les droits voisins et les bases de données, article 70 bisConsolidated text of the Loi du 18 avril 2001 applicable from , Legilux (the official journal of the Grand Duchy of Luxembourg)

In force since . Binds private bodies.

What this law does

Article 70 bis(2) treats a provider of online content-sharing services that gives the public access to protected works uploaded by its users as communicating those works to the public, and requires it to obtain authorization from the rights holders.

Article 70 bis(5) makes the provider liable for unauthorized communication to the public unless it shows its best efforts to obtain authorization, to ensure the unavailability of specific works for which rights holders supplied information, and to act promptly on a sufficiently substantiated notice.

Article 70 bis(7) limits those conditions for a new provider whose services have been available to the public in the Union for less than three years and whose annual turnover is below a stated threshold. Article 70 bis(9) states that the article creates no general obligation to monitor, and requires the provider to give rights holders adequate information on its cooperation on request.

Article 70 bis(10) requires the provider to put in place an effective and expeditious complaint and redress mechanism for users whose uploads are blocked or removed, with human review of the decisions. Article 41, point i) defines the online content-sharing service provider and excludes services such as non-profit online encyclopedias, open source software platforms, online marketplaces and business-to-business cloud services. The article was inserted by the Loi du 1er avril 2022 and took effect on .

What it requires

Specific illegal content

Loi du 24 juillet 2024 portant mise en oeuvre du règlement (UE) 2021/784 (Law of 24 July 2024 Implementing the Terrorist Content Online Regulation)

Loi du 24 juillet 2024 portant mise en oeuvre du règlement (UE) 2021/784, Mémorial A n° 310 de 2024Text of the Loi du 24 juillet 2024 as published in the Mémorial A, Legilux (the official journal of the Grand Duchy of Luxembourg)

In force since . Binds private bodies.

What this law does

Article 1 makes the minister responsible for the Grand-Ducal Police competent to issue the removal or blocking order provided for in Article 3(1) and (4) of Regulation (EU) 2021/784. Article 3 makes the Haut-Commissariat à la protection nationale (HCPN) competent to decide under Article 5(4)(a) of the Regulation that a hosting service provider is exposed to terrorist content.

Article 5 requires every communication between a hosting service provider and the competent authorities to be made by electronic means in French, German or English, and gives the provider three working days to confirm receipt of any communication from them.

Article 6(1) punishes a hosting service provider that fails to remove terrorist content or block access to it within one hour of receiving an order, or fails to inform the competent authorities immediately of content presenting an imminent threat to life, with imprisonment of one to five years and a fine of EUR 25,000 to 350,000, or either penalty alone.

Article 6(2) lets the rate of that fine rise to 4 percent of the provider's worldwide turnover for the preceding year where the failure to meet the one-hour obligation is systematic or persistent. Article 7(1) lets the minister impose an administrative fine of EUR 5,000 to 350,000 on a provider that, after a formal notice, still fails to meet the obligations in Article 3(6), Article 4(7) and Articles 11, 15 and 17 of the Regulation.

Article 7(2) lets the HCPN impose an administrative fine of EUR 5,000 to 350,000 on a provider that, after a formal notice, still fails to meet the obligations in Article 5(1), (2), (3) and (5) and Articles 6, 7 and 10 of the Regulation, or a decision under Article 5(6). The Act took effect on .

What it requires

Transparency and process

Loi du 4 avril 2025 portant mise en oeuvre du règlement (UE) 2022/2065 (Law of 4 April 2025 Implementing the Digital Services Act), Coordinator, Powers and Fines

Loi du 4 avril 2025 portant mise en oeuvre du règlement (UE) 2022/2065, Mémorial A n° 125 de 2025Text of the Loi du 4 avril 2025 as published in the Mémorial A, Legilux (the official journal of the Grand Duchy of Luxembourg)

In force since . Binds private bodies.

What this law does

Article 2(1) designates the Autorité de concurrence (Competition Authority) as the competent authority and the digital services coordinator for the purposes of Regulation (EU) 2022/2065. Article 6(1) lets the Authority require a provider of intermediary services, and any other person acting for the purposes of a trade, business, craft or profession who is reasonably likely to know of relevant information, to provide information without delay.

Article 7(1) requires the Authority to apply to the investigating judge of the Luxembourg district court for authorization before it carries out an inspection. Article 14(1) lets the Authority order the management body of a provider of intermediary services to examine the situation, adopt and submit an action plan, ensure the measures are taken and report on them.

Article 15(2) sets the maximum fine at 6 percent of worldwide turnover in the last closed financial year for a breach of the listed provisions of Regulation (EU) 2022/2065. Article 15(3) sets the maximum fine at 1 percent of worldwide turnover where a provider or other person gives incorrect, incomplete or misleading information, fails to answer an information decision, fails to rectify information or refuses an inspection.

Article 16(1) lets the Authority impose daily penalty payments of up to 5 percent of average daily worldwide turnover to compel a provider to supply information, submit to an inspection, appear, or respect a cessation order or interim measures. Article 30 repeals title VI of the amended Act of on electronic commerce. The Act took effect on .

What it requires

Product and AI liability law1 instrument, 1 in force

Research summary (112 words)

The Loi du 21 avril 1989 relative à la responsabilité civile du fait des produits défectueux transposes Directive 85/374/EEC, according to the Legilux record of the Act. Article 2, point 1 defines a product as any movable good, even one incorporated into another movable or into an immovable, and the term also covers electricity. No bill transposing Directive (EU) 2024/2853 appears in the register of bills on the Legilux portal, as of .

No Luxembourg statute written for the liability of AI systems or other automated agents has been located. The Law of on cybersecurity, which sets the Luxembourg cybersecurity baseline, is recorded in the security topic.

Product liability

Loi du 21 avril 1989 relative à la responsabilité civile du fait des produits défectueux, Liability for Defective Products (Directive 85/374/EEC)

Loi du 21 avril 1989 relative à la responsabilité civile du fait des produits défectueuxText of the Act in the Mémorial A n° 25 of 1989 on the Legilux portal of the Journal officiel du Grand-Duché de Luxembourg

In force since . Binds public and private bodies.

What this law does

The Loi du 21 avril 1989 relative à la responsabilité civile du fait des produits défectueux transposes Directive 85/374/EEC, according to the Legilux record of the Act. Article 1 makes the producer liable for the damage caused by a defect in its product. Article 2, point 1 defines a product as any movable good, even one incorporated into another movable or into an immovable, and the term also covers electricity.

Article 2, point 2 treats as producer the manufacturer of a finished product, the producer of a raw material, the manufacturer of a component and anyone who presents itself as producer by putting its name, trade mark or another distinguishing mark on the product. Article 2, point 2 also treats as producer a person who imports a product into the European Economic Community for sale, hire, leasing or another form of distribution in the course of its business.

Article 2, point 2 treats each supplier as the producer where the producer cannot be identified, unless the supplier names the producer or its own supplier to the victim within a reasonable time. Article 2, point 2 applies the same rule to a product imported from a State outside the Community that does not name its importer, even if the producer is named.

Article 2, point 3 defines a defect as the failure of a product to offer the safety that one can legitimately expect, taking all circumstances into account. Article 2, point 4 excludes damage to the defective product itself from the damage the Act covers. In the text published in Mémorial A n° 25 of 1989, Article 2, point 4 repairs damage to things only after deduction of an amount of 500 Ecus, converted into Luxembourg francs at the rate on the day the damage occurred.

The Law of on civil liability for nuclear accident damage replaced Article 2, point 4, letter a, so that the exclusion of nuclear accident damage refers to that Law. Article 3 puts on the victim the burden of proving the damage, the defect and the causal link between them. Article 4(a) frees the producer who proves that it had not put the product into circulation.

Article 4(b) frees the producer who proves that the defect did not yet exist when it put the product into circulation or arose afterwards. Article 4(c) frees the producer who proves that the product was neither made for sale or another form of distribution with an economic purpose nor made or distributed in the course of its professional activity. Article 4(d) frees the producer who proves that the defect is due to the product complying with mandatory rules issued by the public authorities.

Article 4(e) frees the manufacturer of a component who proves that the defect is attributable to the design of the product into which the component was incorporated or to the instructions of the manufacturer of that product. Article 5 limits the producer to liability for the extent to which the defect contributed to the damage where the fault of the victim, or of a person for whom the victim is responsible, also caused it.

Article 5 does not let the producer escape liability by proving that the damage was caused jointly by a defect and by the intervention of a third party. Article 5 bars limiting or excluding the producer's liability toward the victim by a limiting or exonerating clause. Article 6 makes several persons liable for the same damage jointly and severally.

Article 7 sets a limitation period of three years from the day the victim knew or should have known of the damage, the defect and the identity of the producer. Article 7 also extinguishes the victim's right to compensation ten years after the producer put the defective product into circulation, unless the victim started court proceedings against the producer within that period.

Article 8 leaves untouched the victim's rights under the general law of contractual or non-contractual liability or under another special liability regime. Article 10 excludes products put into circulation before the Act entered into force. The Act entered into force on .

What it requires

Age gating law1 instrument, 1 in force

Research summary (97 words)

Luxembourg's principal age-gating duty was inserted into the loi modifiée du 27 juillet 1991 sur les médias électroniques by the loi du 26 février 2021 transposing the revised Audiovisual Media Services Directive, binding providers of audiovisual media services and providers of video-sharing platforms within Luxembourg's jurisdiction to restrict minors' access to harmful content, including through age-verification tools.

Digital Services Act Article 28, which imposes a separate platform-wide minor-protection duty, applies directly and is covered at EU level rather than restated here. Luxembourg has no app-store-level age-verification statute and no age-appropriate design code distinct from this audiovisual framework.

Adult content age verification (AV)

Loi modifiée du 27 juillet 1991 sur les médias électroniques, art. 27ter et art. 28 septies (protection des mineurs / plateformes de partage de vidéos)

Loi modifiée du 27 juillet 1991 sur les médias électroniques art. 27ter et art. 28 septies, tels qu'insérés par la loi du 26 février 2021 (Mémorial A n° 174 de 2021) transposant la directive (UE) 2018/1808Loi du 26 février 2021 portant modification de la loi modifiée du 27 juillet 1991 sur les médias électroniques

In force since . Binds private bodies.

What this law does

A provider of audiovisual media services must ensure that programs likely to harm minors' physical, mental or moral development are made available only under conditions that normally prevent minors from seeing or hearing them. A grand-ducal regulation sets the specific measures, which may include age-verification tools.

A provider of a video-sharing platform within Luxembourg's jurisdiction must take proportionate measures to protect minors from harmful programs, user-generated videos and audiovisual commercial communications. Those measures include systems to verify the age of users for content likely to cause such harm. Minors' personal data collected under either duty may not be processed for commercial purposes such as profiling or targeted advertising.

What it requires

Reuse law2 instruments, 2 in force

Research summary (292 words)

Luxembourg transposed the EU Digital Single Market Directive's press-publisher neighbouring right and text-and-data-mining exceptions through the Loi du 1er avril 2022, amending the Loi du 18 avril 2001 sur les droits d'auteur, les droits voisins et les bases de donnees.

New articles 56 bis and 56 ter give a press publisher established online reproduction and making-available rights over its publications, exempting hyperlinks and the use of single words or very short extracts, for a term of two years from the January following first publication, and give the authors of works in a press publication an appropriate share of the revenue the publisher receives from online service providers.

New points 15 and 16 of article 10 create a general text-and-data-mining exception subject to a rightholder opt-out, alongside a separate, non-waivable exception for research organizations and public libraries, museums and archives.

Article 10 of the 2001 statute, as enacted, provides that the author of a work lawfully made accessible to the public may not prohibit short quotations justified by the critical, polemical, educational, scientific or informational character of the work into which they are incorporated (point 1). It likewise lets the public reproduce and communicate to the public, for information, short fragments of works, or visual works in full, on the occasion of reports on current events (point 3).

Point 9 lists, among the uses the author may not prohibit, the news of the day and miscellaneous news items that have the character of mere press information. Luxembourg has no compelled platform-to-publisher bargaining regime comparable to Australia's News Media Bargaining Code or Canada's Online News Act.

No Luxembourg misappropriation doctrine distinct from the article 10 exceptions, and no Luxembourg case law on inline framing or hyperlinking distinct from the general EU position, is identified.

Press publishers' right

Loi du 18 avril 2001 sur les droits d'auteur, Press Publisher Neighbouring Right (Art. 56 bis and 56 ter)

Loi du 18 avril 2001 sur les droits d'auteur les droits voisins et les bases de donnees, arts. 56 bis et 56 ter, ajoutes par la loi du 1er avril 2022 portant transposition de la directive (UE) 2019/790Loi du 18 avril 2001 sur les droits d'auteur

In force since . Binds private bodies.

What this law does

Article 56 bis gives press publishers the reproduction and making-available rights of articles 43 and 44 for the online use of their press publications by information-society service providers. The right does not reach private or non-commercial use by individual users, acts of hyperlinking, or the use of isolated words or very short extracts of a press publication.

It expires two years after publication, counted from the January 1 following the date of first publication, and does not apply to a press publication first published before .

Authors of works integrated in a press publication are entitled to an appropriate share of the revenue the publisher receives from information-society service providers, and article 56 ter makes any transfer or licence of an author's rights to a publisher a sufficient legal basis for the publisher to claim a share of statutory-exception compensation for uses of the work.

What it requires

Text and data mining (TDM) opt-out

Loi du 18 avril 2001 sur les droits d'auteur, Text and Data Mining Exception for News Content (Art. 10, points 15 and 16)

Art. 10 points 15 et 16 (contenus de presse), de la loi du 18 avril 2001 sur les droits d'auteur, les droits voisins et les bases de donnees, ajoutes par la loi du 1er avril 2022 portant transposition de la directive (UE) 2019/790Loi du 18 avril 2001 sur les droits d'auteur

In force since . Binds public and private bodies.

What this law does

Article 10, point 16 permits reproductions and extractions of lawfully accessible works, including news articles, for text and data mining without the rightholder's authorization, unless the rightholder has expressly reserved that use by an appropriate means, including a machine-readable reservation for content made available online.

Article 10, point 15 gives research organizations and public libraries, museums, archives and film or sound heritage institutions the same permission for scientific-research text and data mining, without being subject to that reservation. Point 16 is not mandatory, and it does not affect the application of point 15.

What it requires

Case law

  • No current case law for Luxembourg AI law
  • No current case law for Luxembourg privacy law
  • No current case law for Luxembourg scraping law
  • No current case law for Luxembourg cybersecurity law
  • No current case law for Luxembourg communications law
  • No current case law for Luxembourg content moderation law
  • No current case law for Luxembourg product and AI liability law
  • No current case law for Luxembourg digital accessibility law
  • No current case law for Luxembourg age gating law
  • No current case law for Luxembourg reuse law

Reporting clocks that run here22 instruments

The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Luxembourg comes first, then the law of the bodies above it that applies here.

Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.

48 hours
Serious-incident reporthigh-risk AI law
72 hours
Breach notificationprivacy law
10 days
Serious-incident reporthigh-risk AI law
14 days
Final reportsecurity law
15 days
Serious-incident reporthigh-risk AI law
1 month
Final reportsecurity law
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.

The law of Luxembourg

24 hours72 hours1 month

Loi du 5 mai 2026 relative à la cybersécurité (NIS2), Incident Notification

Loi du 5 mai 2026 concernant des mesures destinées à assurer un niveau élevé de cybersécurité, Art. 14security law, in force since

The sentences the clocks are read from

Notify the competent authority, without undue delay, of any incident with a significant impact on the provision of your services: treat an incident as significant where it has caused or is capable of causing severe operational disruption or financial loss to you, or considerable material, physical or moral damage to another person.

Submit an early warning within 24 hours of becoming aware of the significant incident, stating whether it is suspected to result from unlawful or malicious acts or could have cross-border effect.

Follow with a fuller incident notification within 72 hours of becoming aware, updating the early warning and giving an initial assessment of the incident's severity and impact and, where available, indicators of compromise.

Submit an intermediate report if a computer security incident response team (CSIRT) or the competent authority requests one, and a final report within one month of the 72-hour notification, or, if the incident is still ongoing at that point, a progress report followed by a final report within one month of the handling of the incident (Article 14, paragraph 4).

Where appropriate, notify the recipients of your services, without undue delay, of a significant incident likely to affect the services they receive from you, and of any measures or corrections they can apply in response to a significant cyber threat.

If you are a trust-service provider, notify a significant incident affecting your trust services within 24 hours of becoming aware of it, in place of the 72-hour incident notification; the early warning, the intermediate report and the final report still apply.

72 hours

GDPR Articles 33-34, Breach Notification in Luxembourg

Regulation (EU) 2016/679, Arts. 33-34privacy law, in force since

The sentences the clocks are read from

Notify the CNPD without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in Luxembourg, unless the breach is unlikely to risk their rights and freedoms.

If you process personal data on behalf of a controller, notify the controller without undue delay after becoming aware of a personal data breach (Article 33(2)).

Notify affected individuals without undue delay where a breach is likely to result in a high risk to their rights and freedoms.

72 hours

Loi du 20 décembre 2024, Cybersecurity Certification Authority and Vulnerability Notices

Art. 1, 5 et 6, Loi du 20 décembre 2024 (Mémorial A n° 604)security law, in force since

The sentences the clocks are read from

If you hold a European cybersecurity certificate, issue an EU declaration of conformity, or are a conformity assessment body, inform ILNAS in writing within 72 hours of learning of a vulnerability or irregularity that may affect compliance with the security requirements linked to the certification of a product, service or process (Loi du 20 décembre 2024, Article 5(2)).

If you are an accredited conformity assessment body, inform ILNAS of your accreditation and of the certificates you issue within 72 hours (Article 6).

The law of the European Union, which applies in Luxembourg

4 hours

Commission Delegated Regulation (EU) 2024/1366, Cybersecurity Network Code for Cross-Border Electricity Flows: Information Sharing on Cyber-Attacks and Threats

Commission Delegated Regulation (EU) 2024/1366, Art. 38security law, in force since

The sentences the clocks are read from

Share relevant information related to a reportable cyber-attack with your computer security incident response teams (CSIRTs) and your competent authority without undue delay and no later than four hours of becoming aware that the incident is reportable; a cyber-attack is reportable when you assess its criticality as ranging from high to critical on the classification scale methodology under Article 37(8) (Article 38(3) and (4)).

Provide your computer security incident response teams (CSIRTs) without undue delay with any information related to a reportable cyber threat that may have a cross-border effect (Article 38(6)).

4 hours24 hours72 hours1 month

DORA, Article 19 (reporting of major ICT-related incidents), with the time limits of Delegated Regulation (EU) 2025/301

Regulation (EU) 2022/2554, Article 19security law, in force since

The sentences the clocks are read from

Report a major ICT-related incident to the competent authority your sector's Union law designates under Article 46, the European Central Bank through your national supervisor if you are a credit institution classified as significant, using the templates referred to in Article 20, and submit an initial notification as early as possible and in any case within four hours of classifying the incident as major, and no later than 24 hours from becoming aware of it.

Where classification as major comes later than that, submit the initial notification within four hours of the classification instead.

Submit an intermediate report within 72 hours of the initial notification, and submit an updated intermediate report without undue delay and in any case when you have recovered regular activities.

Submit a final report no later than one month after the intermediate report, or your latest updated one, once you know the root cause and the actual impact figures.

If you cannot meet one of those deadlines, tell the competent authority without undue delay and before the deadline lapses, explaining why. A deadline falling on a weekend or bank holiday moves to noon of the next working day, unless you are a credit institution, a central counterparty, a trading venue operator, or an entity your Member State has designated essential or important under the NIS2 Directive, none of which get that extension for an initial notification or intermediate report.

Your competent authority may also decide, and notify you, that the extension does not apply to you if you are a financial entity that is significant or has a systemic character for the financial sector at national or Union level.

Notifying a significant cyber threat under Article 19(2) is voluntary, only where you judge it relevant to the financial system, service users, or your clients. Where a major ICT-related incident affects your clients' financial interests, tell them without undue delay as soon as you become aware of it, describing the incident and the mitigation measures you took, and, for a significant cyber threat, tell a potentially affected client of protection measures it could take, where applicable.

24 hours3 days

Commission Regulation on Personal Data Breach Notification by Electronic Communications Providers (Regulation (EU) No 611/2013)

Regulation (EU) No 611/2013privacy law, in force since

The sentences the clocks are read from

If you provide a publicly available electronic communications service, notify every personal data breach to the competent national authority (Article 2(1)), no later than 24 hours after its detection, where feasible, with the information set out in Annex I; detection is deemed to have taken place when you have acquired sufficient awareness that a security incident has occurred that led to personal data being compromised (Article 2(2)).

Where all the information in Annex I is not available and further investigation is required, you may make an initial notification no later than 24 hours after detection containing the information in Section 1 of Annex I, and you must then make a second notification as soon as possible and at the latest within three days following the initial notification, containing the information in Section 2 of Annex I (Article 2(3)).

If you cannot provide all the information within the three-day period, notify as much as you have within it, submit to the competent national authority a reasoned justification for the late notification of the remaining information, and notify the remaining information as soon as possible (Article 2(3)).

Notify the subscriber or individual without undue delay after detection of the breach, whether or not you have yet notified the competent national authority (Article 3(3)).

If you have a direct contractual relationship with the end user and, despite reasonable efforts, cannot identify within the timeframe all the individuals likely to be adversely affected, you may notify them through advertisements in major national or regional media in the relevant Member States within that timeframe, containing the Annex II information where necessary in a condensed form, and you must continue all reasonable efforts to identify and notify them as soon as possible (Article 3(7)).

If you are contracted to deliver part of the electronic communications service without a direct contractual relationship with subscribers, immediately inform the contracting provider in the case of a personal data breach (Article 5).

24 hours72 hours14 days1 month

Cyber Resilience Act, Manufacturer Reporting Obligations

Regulation (EU) 2024/2847, Art. 14security law, in force since

The sentences the clocks are read from

Notify the computer security incident response team (CSIRT) designated as coordinator for your main establishment and ENISA, through the single reporting platform, of any actively exploited vulnerability you become aware of in your product: an early warning within 24 hours of becoming aware, a vulnerability notification within 72 hours, and a final report no later than 14 days after a corrective or mitigating measure becomes available, the notification and the final report each unless the relevant information has already been provided.

Notify the same recipients of any severe incident affecting the security of your product on the same 24-hour early warning and 72-hour incident notification clock, followed by a final report within one month of the incident notification; the incident notification and the final report each apply unless the relevant information has already been provided. For either an exploited vulnerability or a severe incident, give the computer security incident response team (CSIRT) an intermediate report on relevant status updates if it asks for one.

24 hours72 hours1 month

NIS2 Directive, Reporting Obligations

Directive (EU) 2022/2555, Art. 23security law, in force since

The sentences the clocks are read from

Notify your computer security incident response team (CSIRT), or the competent authority where applicable, of any incident with a significant impact on the provision of your services: an early warning within 24 hours of becoming aware, an incident notification within 72 hours of becoming aware (24 hours if you are a trust service provider), an intermediate report on relevant status updates if your CSIRT or competent authority asks for one, and a final report no later than one month after the incident notification, or, for an incident still ongoing at that point, a progress report then and a final report within one month of its handling.

Where appropriate, notify, without undue delay, the recipients of your services who a significant incident is likely to adversely affect, and communicate to recipients potentially affected by a significant cyber threat any measures or remedies they can take.

48 hours

AI Act, Article 26(10) (post-remote biometric identification authorisation)

Regulation (EU) 2024/1689, Article 26(10)high-risk AI law, not yet in force, from

The sentence the clocks are read from

If you are a law enforcement deployer using a high-risk AI system for post-remote biometric identification in a targeted search for a suspected or convicted person, request authorisation from a judicial authority or a binding, judicially reviewable administrative authority, in advance or without undue delay and no later than 48 hours, unless you are using the system only for the initial identification of a potential suspect on objective and verifiable facts directly linked to the offence.

2 days10 days15 days

AI Act, Article 73 (reporting of serious incidents)

Regulation (EU) 2024/1689, Article 73high-risk AI law, not yet in force, from

The sentences the clocks are read from

Report a serious incident not later than 15 days after you become aware of it, or immediately once you establish a causal link between your AI system and the incident, or the reasonable likelihood of one, whichever is sooner.

Report immediately, and not later than 2 days after becoming aware of it, a widespread infringement or a serious incident causing a serious and irreversible disruption to the management or operation of critical infrastructure.

Report a serious incident involving the death of a person not later than 10 days after becoming aware of it, and immediately once you establish, or suspect, a causal link between your AI system and the incident.

If you are a deployer of a high-risk AI system and identify a serious incident, Article 26(5) requires you to immediately inform first the provider, then the importer or distributor, and the relevant market surveillance authority; if you cannot reach the provider, report the incident yourself under the same rules that bind a provider. This does not require you to disclose sensitive operational data if you are a law enforcement authority.

After reporting a serious incident, without delay investigate it, including a risk assessment and corrective action, and cooperate with the competent authorities; do not alter the AI system in a way that could affect the investigation before telling the authorities.

2 days10 days15 days

AI Act, Articles 60 and 61 (testing in real world conditions outside AI regulatory sandboxes, with informed consent)

Regulation (EU) 2024/1689, Articles 60 and 61high-risk AI law, in force since

The sentences the clocks are read from

Let a subject, or the subject's legally designated representative, withdraw from the testing at any time by revoking informed consent, without detriment and without having to provide any justification, and on request delete the subject's personal data immediately and permanently; the withdrawal does not affect the activities already carried out (Article 60(5)).

Report any serious incident identified in the course of the testing to the national market surveillance authority in accordance with Article 73, which requires the report immediately after a causal link, or the reasonable likelihood of one, is established and in any event not later than 15 days after you become aware of the incident, not later than two days for a widespread infringement or a serious and irreversible disruption of the management or operation of critical infrastructure, and not later than 10 days after you become aware of it where a person has died (Article 60(7)).

72 hours

Commission Delegated Regulation (EU) 2022/1645, External Reporting of Information Security Incidents and Vulnerabilities (IS.D.OR.230)

Commission Delegated Regulation (EU) 2022/1645, IS.D.OR.230security law, in force since

The sentence the clocks are read from

Submit a notification as soon as you know of the condition, and a report as soon as possible and not exceeding 72 hours from the time you know of it unless exceptional circumstances prevent this, in the form your competent authority defines (point IS.D.OR.230(c), points (1) and (2)).

72 hours

Commission Implementing Regulation (EU) 2023/203, External Reporting of Information Security Incidents and Vulnerabilities in Aviation (IS.I.OR.230)

Commission Implementing Regulation (EU) 2023/203, IS.I.OR.230security law, in force since

The sentence the clocks are read from

Submit a notification as soon as you know of the condition, and a report as soon as possible and not exceeding 72 hours from the time you know of it unless exceptional circumstances prevent this, in the form your competent authority defines (point IS.I.OR.230(c), points (1) and (2)).

3 days

European Health Data Space Regulation, Serious-Incident Reporting by Manufacturers of EHR Systems

Regulation (EU) 2025/327, Art. 44(7)security law, not yet in force, from

The sentence the clocks are read from

Make the report immediately after you have established a causal link between the EHR system and the serious incident or the reasonable likelihood of such a link and, in any event, not later than three days after you become aware of the serious incident (Article 44(7)).

immediately

AI Act, Article 20 (corrective actions and duty of information)

Regulation (EU) 2024/1689, Article 20high-risk AI law, not yet in force, from

The sentence the clocks are read from

Where the system presents a risk to the health or safety, or to fundamental rights, of persons within the meaning of Article 79(1) and you become aware of that risk, immediately investigate the causes, in collaboration with the reporting deployer where applicable, and inform the market surveillance authorities competent for the system and, where applicable, the notified body that issued its certificate under Article 44, in particular of the nature of the non-compliance and of any relevant corrective action taken.

immediately

AI Act, Article 22 (authorised representative of a provider established in a third country: appointment, mandate, tasks and termination)

Regulation (EU) 2024/1689, Article 22(1), (2), (3) except points (b) and (c), and (4)high-risk AI law, not yet in force, from

The sentence the clocks are read from

Terminate the mandate if you consider or have reason to consider that the provider is acting contrary to its obligations under the Regulation, and immediately inform the relevant market surveillance authority and, where applicable, the relevant notified body of the termination and the reasons for it (Article 22(4)).

without undue delay

AI Act, Article 26(1) to (5) (deployer use, human oversight, input data and monitoring)

Regulation (EU) 2024/1689, Article 26(1) to (5)high-risk AI law, not yet in force, from

The sentences the clocks are read from

Where you have reason to consider that using the system per its instructions may present a risk to health, safety or fundamental rights, inform the provider or distributor and the relevant market surveillance authority without undue delay, and suspend use of the system.

Where you have identified a serious incident, immediately inform first the provider, then the importer or distributor and the relevant market surveillance authorities; if you cannot reach the provider, report the incident yourself as Article 73 requires of a provider.

without undue delay

AI Act, Article 55 (obligations for providers of general-purpose AI models with systemic risk)

Regulation (EU) 2024/1689, Article 55frontier-model AI law, in force since

The sentence the clocks are read from

Keep track of, document, and report to the AI Office, and as appropriate to national competent authorities, without undue delay, relevant information about serious incidents involving your model and any corrective measures you have taken or plan to take. The Regulation states no fixed number of days for this report and no explicit moment its clock starts from, only that it must be made without undue delay.

without undue delay

ePrivacy Directive, Article 4(3) to (5), Personal Data Breach Notification

Directive 2002/58/EC, Art. 4(3)-(5)privacy law, in force since

The sentences the clocks are read from

If you provide a publicly available electronic communications service and a personal data breach occurs, notify the breach to the competent national authority without undue delay (Article 4(3)).

Where the breach is likely to adversely affect the personal data or privacy of a subscriber or individual, also notify that subscriber or individual of the breach without undue delay (Article 4(3)).

Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

This page covers the instruments LexLint has researched to a stage. Instruments named in the law library but not yet researched are counted in the head and are not listed here. Every entry carries its own primary source on its note page. This is a research index, not legal advice.