European Union law applies in LatviaLatvia is a member state of the European Union, whose 223 researched instruments are listed on the European Union page, not here. The law of Latvia, described on this page below, applies here too.European Union law reaches Latvia two ways. A regulation, the EU AI Act and the GDPR among them, binds here as written, though Latvia names its own regulator, sets its own penalties within the EU ceiling and may add rules of its own beside it. A directive binds here only through the act Latvia passes to carry it into national law, and that act, listed on this page, is the one a court in Latvia applies. For a concern in Latvia, read both pages.
33 of 34 named instruments researched to a stage, across nine of the ten areas of law we track: 33 in force. As of .
When each starts32 of 33 carry a date, 1 does not. Earlier is before 2014.
in forcenot yet in forceblocked by a courtproposedno longer in force
The EU AI Act (Regulation (EU) 2024/1689) applies directly in Latvia and is not restated here. Latvia has no single implementing act. The statute of the Consumer Rights Protection Centre (Patērētāju tiesību aizsardzības centrs), as amended by Cabinet Regulation No. 478 of , gives the Centre the single point of contact and competent authority tasks under the AI Act and the supervision of AI systems in products within its competence under the Annex I harmonisation legislation.
The Finanšu tirgus digitālās darbības noturības un mākslīgā intelekta izmantošanas likums (the law on the digital operational resilience of the financial market and the use of artificial intelligence), in force since , makes Latvijas Banka the supervisor of AI use by financial entities under Article 74(6) of the Regulation.
Latvia's own Mākslīgā intelekta centra likums (Law on the Artificial Intelligence Centre), in force since , establishes a state-supported foundation to coordinate national AI policy, run a regulatory sandbox, and advise on AI or deepfake use during elections and Saeima appointment processes, but it imposes no duty on a private developer or deployer of an AI system, so it is described here rather than landed as an instrument.
Latvia does bind private conduct directly through the Krimināllikums (Criminal Law): Section 90.1, in force since , criminalizes producing or disseminating deliberately false, discrediting information about a political party or a Saeima, municipal, or European Parliament candidate using deepfake technology during the pre-election campaign period or on election day, and Section 90.2, in force since , does the same for a state-official appointment process before the Saeima.
The statute of the Consumer Rights Protection Centre (Patērētāju tiesību aizsardzības centrs) gives the Centre the task of supervising AI systems in products, within its competence, in the areas of the Union harmonisation legislation listed in Annex I of the AI Act. It also gives the Centre the tasks of the single point of contact and the competent authority under the AI Act, in line with its competence and the Act's requirements.
Cabinet Regulation No. 478 of added the supervision task for AI systems in products. Cabinet Regulation No. 478 also added the single point of contact and competent authority tasks. Cabinet Regulation No. 478 was published in Latvijas Vēstnesis on . Cabinet regulations enter into force on the day after promulgation unless the legal act sets another term, so an amending regulation published on with no term of its own applied from .
Article 7 applies the AI use requirements of Regulation (EU) 2024/1689 to the financial market participants named in Articles 4 and 5 and to the savings and loan association named in Article 6(1), point 5, in accordance with Article 2 of the Regulation. Article 8(5) makes the Bank of Latvia (Latvijas Banka) the supervisor of those AI use requirements, in accordance with Article 74(6) of the Regulation.
Article 8(6) requires the Bank of Latvia to give the European Central Bank information obtained in that supervision that could be useful for the prudential supervision of a credit institution. Article 8(7) lets the Bank of Latvia set further requirements on the use of AI, and how they are to be met, in areas that directly applicable EU law does not regulate. Article 11(2), point 1 covers breaches of the prohibited AI practices in Article 5 of the Regulation.
Article 11(2), points 2 to 6 cover breaches of the obligations that Articles 16, 22, 23, 24 and 26 of the Regulation place on providers, authorised representatives, importers, distributors and deployers of high-risk AI systems. Article 11(2), point 10 covers breaches of the transparency duties of providers and deployers in Article 50 of the Regulation. Article 11(2), point 11 covers the duty to give the Bank of Latvia and notified bodies correct, complete and truthful information.
Article 10(3), point 5 lets the Bank of Latvia fine a legal person up to EUR 35,000,000 or up to 7 percent of total annual turnover, whichever is higher, for the breach in Article 11(2), point 1. Article 10(3), point 6 sets a fine for a legal person of up to EUR 15,000,000 or up to 3 percent of total annual turnover, whichever is higher, for the breaches in Article 11(2), points 2 to 10.
Under Article 10(6), a small enterprise, medium enterprise or start-up fined under Article 10(3), points 5 to 7 pays the lower of the two amounts. Article 10(4) lets the Bank of Latvia require the responsible person to stop the activity immediately and, for a natural person, impose a temporary ban on specified duties for up to two years. The Law takes effect on the day after its promulgation. The President promulgated the Law on , so it took effect on .
Article 13 of the Ombudsman Law (Tiesībsarga likums) gives the Ombudsman two tasks that concern artificial intelligence systems. Point 15 gives the Ombudsman the task of requesting and accessing the documentation of artificial intelligence systems that a review case needs.
Point 16 gives the Ombudsman the task of submitting to the market surveillance authority, within its competence, a reasoned request to have an artificial intelligence system tested by technical means, where the documentation the review case needs is not sufficient. Points 15 and 16 are in the text of the Ombudsman Law in force on . Article 13 was amended by the law of , which took effect on .
Krimināllikums 90.1 pants (pievienots ar 2024. gada 9. maija likumu, stājas spēkā 22.05.2024.) un 90.2 pants (pievienots ar 2024. gada 26. septembra likumu, stājas spēkā 22.10.2024.).Krimināllikums, official consolidated text, likumi.lv
In force since .Binds public and private bodies.
What this law does
Section 90.1 criminalizes the deliberate production or dissemination of knowingly false, discrediting information about a political organization (party), an association of political organizations, or a candidate for the Saeima, a municipal council, or the European Parliament, using deepfake technology, when committed during the pre-election campaign period or on election day; the maximum penalty is five years' deprivation of liberty, or alternatively short-term deprivation of liberty, probationary supervision, or community service.
Section 90.2 criminalizes the same conduct directed at a candidate for a state office the Saeima elects, appoints, or confirms, when committed during that process, carrying the same maximum penalty. Section 90.2 was added by a separate amending law adopted on , which took effect on .
Article 3.1 requires a clear and unambiguous indication where, during the campaign period, paid pre-election campaigning or campaign material uses an AI-generated likeness of a person or an event that does not correspond to reality, in an image, audio or video. Under Article 31.1(1), where a breach of Article 3.1 is found, the head of the Corruption Prevention and Combating Bureau decides to ban the further distribution of that AI-generated campaign material.
Before deciding, the Bureau obtains an expert opinion and assesses the usefulness, enforceability and proportionality of the decision. The decision can be appealed to the administrative district court, and filing the appeal does not suspend it. Article 3.1 is in the wording of the law of , which took effect on . Article 31.1 is in the same wording of the law of .
Latvia's private-sector regime is the General Data Protection Regulation (GDPR) plus the Personal Data Processing Law (Fizisko personu datu apstrades likums, Latvijas Vestnesis No. 132/2018), which establishes the Data State Inspectorate (DVI) as supervisory authority and supplies the national institutional and procedural layer GDPR leaves to member states.
Article 25(2) of the Law restates GDPR Article 9's special-category list including biometric data, with no illustrative example list and no Latvia-specific narrowing or widening of the biometric category.
A controller must notify the Data State Inspectorate (DVI) without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in Latvia, and must notify affected individuals without undue delay where the breach is likely to result in a high risk to their rights and freedoms.
Latvia's national supplement to the directly applicable General Data Protection Regulation (GDPR), establishing the Data State Inspectorate (DVI) as supervisory authority with GDPR Article 57-58 powers, national procedure for decisions, disputes and appeals, and data protection officer regulation. Beyond that institutional layer it also makes national choices on substance. Article 25(1) of the Law permits processing where at least one ground in GDPR Article 6(1) applies.
Articles 27 to 32 limit data subject rights in specific settings, such as scientific or historical research under Article 31. The Law has no transfer rules of its own, so the transfer rules of GDPR Chapter V apply directly.
Transferring personal data of a person in Latvia 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.
General Data Protection Regulation (GDPR) Article 22 gives a person in Latvia 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 Personal Data Processing Law adds no rule of its own on automated decisions.
General Data Protection Regulation (GDPR) Articles 12 to 21 apply directly in Latvia: access, rectification, erasure, restriction, portability, and objection, exercisable against the controller, generally within one month.
The Personal Data Processing Law adds national limits: its Article 27(1) removes the Article 15 access right where disclosure is barred by national-security, defence, public-security or criminal-law rules, or to protect the state's financial interests in tax enforcement, anti-money-laundering and counter-terrorist-financing work, or financial-market supervision. Articles 28 to 32 of the Law also set aside some of these rights in specific settings, such as official publication under Article 28.
The Data State Inspectorate (DVI) holds the General Data Protection Regulation (GDPR) Article 57-58 toolkit, investigative powers, corrective powers, and administrative fine authority up to the Article 83 tiers. DVI has issued fines under this authority: in the five years from 2018 to 2022 they ranged from EUR 200 to EUR 1.2 million and came to almost EUR 1.6 million in total.
For unlawful acts with personal data by a public-law legal person, and for its failure to meet controller or processor duties, Article 38 of the Personal Data Processing Law provides a warning or a fine on the official of up to 200 fine units. GDPR Article 82 gives any person who suffered material or non-material damage a right to compensation from the controller or processor.
Article 25(2) of the Personal Data Processing Law, confirmed at likumi.lv, restates General Data Protection Regulation (GDPR) Article 9's special-category list and its own biometric-data term mirroring GDPR Article 4(14)'s definition (processing necessary for unique identification). It carries no illustrative list, enumeration, or named example distinguishing facial recognition from voice data or any other biometric modality.
It permits the processing on a ground in GDPR Article 9(2), or where another normative act provides for it under GDPR Article 9(4), and does not narrow or widen the biometric category.
Latvia's Krimināllikums (Criminal Law) makes access to an automated data processing system a crime where it involves breaching the system's protective means, or is carried out without appropriate permission, or by using rights granted to another person, and in every case only where it causes substantial harm; no statutory definition carves an openly served page out of the without-permission ground, and no reported decision has settled whether an ordinary, unauthenticated request meets it.
A further section separately criminalizes unauthorized interference with system data, and another the manufacture or distribution of tools intended to compromise such systems.
The Autortiesību likums (Copyright Law) gives a database maker a sui generis right against extraction or re-utilization of the whole, or a substantial part, of a database reflecting a substantial investment, running fifteen years from completion, alongside a 2023-added, machine-readable-opt-out text-and-data-mining exception transposing the EU Digital Single Market Copyright Directive. Personal-data protection runs on the General Data Protection Regulation (GDPR)-based privacy regime, covered under the privacy topic.
The Konkurences likums (Competition Law) prohibits unfair competition, which its 18. pants defines as conduct that breaches the law or fair business custom and hinders, restricts or distorts competition, and whose listed forms include obtaining, using or distributing a competitor's trade-secret information without consent; that general clause, not a scraping-specific rule, decides whether scraping a competitor's public data is unfair competition.
No statute names robots.txt itself; a rights holder's reservation against mining under 21.1 pants must instead take a machine-readable form. No separate trespass-to-chattels doctrine addresses a server strained by heavy automated requests.
Section 241 makes arbitrary access to the resources of an automated data processing system a crime where it involves breaching the system's protective means, or is carried out without permission, or by using rights granted to another person, and in every case only where it causes substantial harm; the maximum penalty rises from two to four years where the access is for financial gain, and to seven years where committed by an organized group, causing serious consequences, or directed at a system processing state-security-related information.
Section 243 separately criminalizes unauthorized modification, damage, destruction, impairment, or concealment of information in such a system, or knowingly entering false information into it, at penalties up to three years, rising to seven for an organized group or serious consequences.
Section 244 criminalizes the unauthorized manufacture, adaptation, distribution, acquisition, transport, or storage of a tool, device, software, password, or access code intended to influence such a system's resources or to gain access to it for committing a crime, at penalties up to two years, rising to five for an organized group or serious consequences. The current wording of each of these sections took effect on a different day.
Autortiesību likums (scraping) 21.1 pants, pievienots ar 2023. gada 23. marta likumu 'Grozījumi Autortiesību likumā' (Latvijas Vēstnesis, 67, 04.04.2023.), stājas spēkā 05.04.2023.Grozījumi Autortiesību likumā (2023 Copyright Law amendments transposing Directive (EU) 2019/790), official text, likumi.lv
In force since .Binds public and private bodies.
What this law does
Article 21.1 permits reproducing a lawfully accessible work to carry out text and data mining, defined as any automated analytical technique used to analyze text and data digitally to derive information such as patterns, trends, and correlations. Copies made for that purpose may be kept only as long as needed for the mining.
A rights holder can prohibit this use by giving clear notice in an appropriate manner, and a prohibition on the online use of publicly accessible works must be given in machine-readable form, including through metadata. A separate exception at Article 21.2 covers a research organization or a cultural heritage institution mining lawfully accessible works for research purposes, without that opt-out, but Article 21.2(5) excludes computer programs from its scope.
Autortiesību likums IX nodaļa (57.-62. pants), Datubāzes aizsardzības īpatnības (sui generis), grozīta ar 2023. gada 23. marta likumu, stājas spēkā 05.04.2023.Autortiesību likums, official consolidated text, likumi.lv
In force since .Binds public and private bodies.
What this law does
A person or legal entity that has taken the initiative and risk of investment in creating a database, where its creation, verification, or presentation reflects a substantial qualitative or quantitative investment, is recognized as its maker and can prevent extraction, meaning the permanent or temporary transfer of the whole or a substantial part of its content to another medium, and re-utilization, meaning making that content available to the public by distributing, renting, or providing online or other transmission of it.
Repeated and systematic extraction or re-utilization of insubstantial parts is also barred where it conflicts with the database's normal use or unreasonably prejudices the maker's legitimate interests. The right runs fifteen years from the year following completion, restarting on a substantial new investment, and does not reach a lawful user's extraction or re-utilization of an insubstantial part for any purpose, nor extraction for text and data mining permitted under Articles 21.1 and 21.2. The Copyright Law took effect on . The edition in force from that day already contained Articles 57 to 62.
Latvia's NIS2 transposition, the Nacionālās kiberdrošības likums (National Cybersecurity Law, NKDL), was adopted by the Saeima on , published in Latvijas Vēstnesis (128A, 04.07.2024), and entered into force on ; its own transitional provisions repealed the prior Informācijas tehnoloģiju drošības likums (Information Technology Security Law, the 2010 NIS1 transposition) outright on the same date, so no predecessor regime survives alongside it.
A law of , Grozījumi Nacionālās kiberdrošības likumā (Amendments to the National Cybersecurity Law, Latvijas Vēstnesis 115, 17.06.2026), amended the Law from , and its amendment of Article 20(11), which adds a company, foundation or association significant to national security (other than an owner of forest land of at least 10,000 hectares or of agricultural land of at least 4,000 hectares), applies from .
The Law binds a būtisko pakalpojumu sniedzējs (essential service provider, Article 20) or svarīgo pakalpojumu sniedzējs (important service provider, Article 21) by sector and, for most sectors, a large- or medium-enterprise size gate; Article 21(1)(2)(l)-(n) names an online marketplace, an online search engine and a social media platform provider expressly among the medium-or-large digital providers it reaches, and Article 20(8)(s)-(v) separately reaches a large cloud-computing, data-centre, content-delivery-network, or ICT-management or cybersecurity service provider as essential (with the medium tier of the same list important under Article 21(1)(1)), while Article 20(2) makes a domain-name-system service provider essential whatever its size, a sector class no activity in this vocabulary expresses.
The Law also binds direct and indirect state and municipal administration and other public-law bodies (Article 3(1)(2), Article 20(5)(6)(10)), excluding the state security services, so it reaches a government duty-bearer as well as a private one.
Article 27 sets the core risk-management duty (appropriate and proportionate technical and organisational measures), Article 28 requires a written cyber-risk-management and ICT-business-continuity plan with staff training, and Article 26 has the Cabinet set the minimum cybersecurity requirements the plan must meet, done by Cabinet Regulation No. 397 of ; a personnel-security restriction on privileged ICT access by persons convicted of listed intentional crimes, Article 26.1, was inserted by the 2026 amendment.
Article 34 sets NIS2's own graduated incident-notification clock to the competent cyber incident prevention institution (an early warning within 24 hours, an initial report within 72 hours, a final report within one month), but that clock did not itself bind until under the Law's transitional provisions, ten months after the Law's own commencement.
Articles 39 and 40 add a coordinated-vulnerability-disclosure regime distinct from Article 34: any person who discovers a vulnerability in a subject's system must report it within five working days, and the subject must then remediate within a deadline the institution sets, capped at 90 days and extendable to 180 days on request; Article 46's fine, however, defines 'material non-compliance' by a closed three-item list that does not name a missed Article 40 remediation deadline, an open question flagged below rather than an unsupported penalty figure for that duty.
Supervision splits between the Nacionālais kiberdrošības centrs (National Cybersecurity Centre, NKDC, within the Ministry of Defence), which is the Article 41 competent authority for essential and important service providers generally and receives most subjects' incident and vulnerability reports through the Institute of Mathematics and Computer Science of the University of Latvia, and the Satversmes aizsardzības birojs (Constitution Protection Bureau, SAB), which holds the same role for an owner or lawful possessor of ICT critical infrastructure.
Article 46 sets NIS2's own two-tier fine, up to EUR 10,000,000 or, above EUR 500,000,000 turnover, 2 percent of turnover for an essential entity, and up to EUR 7,000,000 or 1.4 percent for an important entity, imposed directly by NKDC or SAB as an administrative fine with no criminal offence and no private right of action, appealable to court by the subject under the Administrative Procedure Law.
Latvia 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 and the Fizisko personu datu apstrādes likums sits in the privacy topic rather than here.
Article 3(3)-(4) exempts a financial entity already subject to Regulation (EU) 2022/2554 (DORA), and any essential or important service provider covered by an equivalent sector-specific EU cybersecurity regime, from the Law's risk-management and supervision provisions to the extent that regime's own requirements are at least equivalent.
4. līdz 6. un 8. līdz 11. pants (DORA daļa) Finanšu tirgus digitālās darbības noturības un mākslīgā intelekta izmantošanas likums (2025. gada 11. septembris)Finanšu tirgus digitālās darbības noturības un mākslīgā intelekta izmantošanas likums (Financial Market Digital Operational Resilience and…
In force since .Binds private bodies.
What this law does
The Finanšu tirgus digitālās darbības noturības un mākslīgā intelekta izmantošanas likums (Financial Market Digital Operational Resilience and Use of Artificial Intelligence Law) was adopted by the Saeima on , published in Latvijas Vēstnesis No. 188 on and took effect on .
Its digital-operational-resilience half applies Regulation (EU) 2022/2554 (DORA) to the 24 classes of financial market participant that Article 4 lists, among them credit institutions, payment institutions, electronic money institutions, investment firms, insurance and reinsurance undertakings, trading venues and crypto-asset service providers.
Article 5 puts the entities that DORA Article 16 covers under the simplified framework, and Article 6(1) takes savings and loan associations, giro settlement institutions, small insurers and small alternative investment fund managers out of DORA while Article 6(3) lets Latvijas Banka set ICT risk-management, information-security and ICT-operations requirements for them.
Article 8 makes Latvijas Banka the supervisor of digital operational resilience under DORA Article 46, gives it the investigatory and sanctioning powers of DORA Article 50(2), and lets it set the methodology for assessing losses from major ICT-related incidents and the way major ICT-related incidents are reported.
A financial market participant covered by Articles 4 and 5 must inform Latvijas Banka of all material changes, including any circumstance that may adversely affect its further operation, and of changes in the information it has given the Bank.
Article 10(1) lets Latvijas Banka issue a warning or fine a legal person up to EUR 5,000,000 or 3 percent of total annual turnover, whichever is higher, and a natural person up to EUR 700,000, for breaching the Regulation (EU) 2022/2554 requirements that Article 11(1) lists. The Law also applies Regulation (EU) 2024/1689 (the AI Act) to the same participants in Article 7 and the provisions that follow it, which is a separate regime from DORA.
Latvijas Bankas noteikumi Nr. 409 Prasības digitālās darbības nepārtrauktības un noturības jomā finanšu tirgus dalībniekiem, kuriem nepiemēro Regulu (ES) 2022/2554 (2026. gada 5. janvāris)Latvijas Bankas noteikumi Nr. 409 (Bank of Latvia Regulations No. 409), likumi.lv, Latvijas Vēstnesis 3, 07.01.2026
In force since .Binds private bodies.
What this law does
The Bank of Latvia's Regulations No. 409 (Latvijas Bankas noteikumi), issued under Article 6(3) of the Financial Market Digital Operational Resilience and Use of Artificial Intelligence Law, set ICT risk-management, information-security, ICT-operations and business-continuity requirements for the financial market participants that Regulation (EU) 2022/2554 (DORA) does not cover.
The regulations were adopted on , published in Latvijas Vēstnesis No. 3 on and took effect on .
They apply to small alternative investment fund managers, small insurers and reinsurers, micro, small and medium-sized insurance intermediaries, the persons in points 2, 3, 4, 6, 7, 9, 12, 13, 15 and 16 of Article 101(7) of the Financial Instrument Market Law, savings and loan associations, small private pension funds with no more than 15 plan members and giro settlement institutions.
A participant must put in place and document an ICT risk-management and control framework for which its management bears overall responsibility, and must draw up, document and implement an information security policy that protects the confidentiality, integrity and availability of data and services. A participant must carry out and document an ICT risk assessment at least once a year.
Cabinet Regulation No. 397 of , Minimālās kiberdrošības prasības (Minimum Cybersecurity Requirements), sets the minimum cybersecurity requirements for an essential service provider, an important service provider and an owner or lawful possessor of ICT critical infrastructure under the National Cybersecurity Law. The regulation was adopted on , published in Latvijas Vēstnesis No. 123 on and took effect on .
Article 8 of the Electronic Communications Law has the Cabinet set the security requirements for public electronic communications networks and the equipment, software and outsourced services used in them, and point 1.6 of this regulation does so. It requires a subject to keep a set of cybersecurity governance documents made up of a cybersecurity policy, a catalogue of ICT resources and information systems, a cyber-risk-management and ICT-business-continuity plan and a cyber incident log.
The subject must review the cybersecurity policy at least once in three years, and must update the ICT-resource catalogue within one month of a change.
The subject must give each information system a confidentiality, integrity and availability security class of A, B or C. The cyber-risk-management and ICT-business-continuity plan must be reviewed and updated at least once a year by an essential service provider that holds a class A system and by an ICT critical infrastructure owner, at least once in two years by another essential service provider, and at least once in three years by an important service provider.
A subject must record each cyber incident in its incident log within 24 hours of detecting it. A subject must report a significant cyber incident to the competent cyber incident prevention institution on electronically signed early warning, initial report, progress report, intermediate report and final report forms, within the clocks of Article 34 of the Law.
A subject must give the staff and officials who use its systems an initial cybersecurity briefing within one month of their user account being registered and a routine briefing at least once a calendar year.
An owner or lawful possessor of ICT critical infrastructure may contract for the purchase of technical resources for a class A information system only if the supplier and the manufacturer meet the conditions of point 94, which for a legal person include registration in a NATO, EU or EFTA member state or a NATO Indo-Pacific partner state.
For a public electronic communications network that was in operation or being built when the regulation took effect, the supplier conditions of point 102 apply from . The technical risk-management requirements apply to a DNS, cloud-computing, data-centre, content-delivery-network, managed-service, online-marketplace, online-search-engine, social-network or trust-service provider only so far as they do not conflict with Commission Implementing Regulation (EU) 2024/2690.
The regulation repealed Cabinet Regulation No. 94 of on security requirements for public electronic communications networks.
Article 27 requires a subject (an essential service provider under Article 20, an important service provider under Article 21, or an owner or lawful possessor of ICT critical infrastructure) to take appropriate and proportionate technical and organisational measures to manage the cyber risks to the security of the electronic communications networks and information systems it uses, and to prevent or minimise the impact of a cyber incident on its service recipients and on other services.
Article 21(1)(2)(l)-(n) names an online marketplace, an online search engine and a social media platform provider expressly among the medium-or-large digital providers this duty reaches as important entities.
Article 28 additionally requires the subject to draft a cyber-risk-management and ICT-business-continuity plan and to train staff on it, with the plan's required content set by the Cabinet under Article 28(2) and the minimum cybersecurity requirements the subject's systems must meet set by Cabinet Regulation No. 397 of ; Article 25 requires the subject's head to appoint a cybersecurity manager (kiberdrošības pārvaldnieks) within three months of the subject's status notification or of the National Cybersecurity Centre's decision on its status under Article 22(5), and Article 26.1, inserted by the law of , bars a person convicted of a listed intentional crime from holding privileged access to the subject's ICT systems unless rehabilitated or cleared, and requires the subject to decide individually on employing such a person.
Article 3(3) applies the Law to a financial entity covered by Regulation (EU) 2022/2554 (DORA) that is an essential service provider only insofar as that Regulation or other law sets no other requirements on cybersecurity, risk management, incident reporting and supervision. Article 3(4) disapplies the Law's requirements, including supervision, for a subject covered by an equivalent sector-specific EU regime, to the extent that regime's requirements are at least equivalent in effect.
The law of amending the National Cybersecurity Law was adopted by the Saeima on , promulgated on and took effect the day after promulgation, . Transitional provision 15 sets as the day its amendment of Article 20(11), which adds a company, foundation or association significant to national security, takes effect.
Article 39 requires any person who discovers a vulnerability in a subject's information system or electronic communications network to report it to the competent cyber incident prevention institution within five working days, and lets that person report anonymously and have their identity kept confidential.
Once the institution has assessed a report as substantiated and relayed it, Article 40 requires the affected subject to take the actions necessary to remediate the vulnerability within the institution's own deadline, capped at 90 days from receiving the information and extendable to 180 days on the subject's request for objective reasons, reporting progress to the institution as it goes. This is a subject-facing remediation clock rather than only a state-run coordination function.
Article 46(5), however, defines a fine-triggering 'material non-compliance' with a closed three-item list (failing to take appropriate measures, repeatedly refusing supervisory information requests, and a late or false significant-incident notification) that does not name a missed Article 40 deadline, so whether that specific failure draws the Article 46 fine, rather than only the non-monetary corrective and suspension powers Article 45 gives generally, is not settled by the text and is recorded as an open question here rather than as a penalty figure.
Article 34 requires a subject to notify the competent cyber incident prevention institution immediately of any cyber incident and to follow its instructions.
For a significant cyber incident, the subject must submit an early warning within 24 hours of becoming aware, an initial report within 72 hours (24 hours for a trust service provider), and, within one month of the initial report, a final report (or, if unresolved, a progress report followed by a final report once resolved); where relevant, the subject must also inform affected service recipients of protective measures and, after coordinating with the institution, of the incident itself.
This is NIS2 Article 23's own clock. Although the Law commenced , its transitional provisions delayed Article 34's paragraphs two through five, the notification clock itself, until .
For most private-sector and civilian public-sector subjects the competent cyber incident prevention institution is the Institute of Mathematics and Computer Science of the University of Latvia, and the Military Intelligence and Security Service holds the same role for the Ministry of Defence, its subordinate bodies and the National Armed Forces. A missed or knowingly false notification is one of Article 46(5)'s three enumerated grounds for a material non-compliance fine.
Latvia carries the ePrivacy Directive (2002/58/EC) in two laws, the Information Society Services Law (Informācijas sabiedrības pakalpojumu likums) and the Electronic Communications Law (Elektronisko sakaru likums), and the General Data Protection Regulation (GDPR) applies directly.
Article 7.1 of the Information Society Services Law allows storing information in a subscriber's or user's terminal equipment, or accessing information stored there, only with consent after clear and comprehensive information, with an exception for network transmission and for the service the user requested.
Article 9 bans commercial notices by automatic calling systems, electronic mail or fax without the recipient's prior free and unambiguous consent, with an exception for a provider's own similar goods or services sold to the recipient, and it applies to notices sent to natural persons; article 8 sets the content and refusal duties for every commercial notice. The Consumer Rights Protection Centre and the State Data Inspectorate supervise those articles.
Article 94 of the Electronic Communications Law bars an electronic communications merchant from disclosing information about an end user or transmitted information without the end user's consent. A data subject's right to object to direct marketing is held in the privacy row for GDPR Articles 15 to 21, Data Subject Rights as Applied in Latvia.
Article 9(1) of the Information Society Services Law bans using automatic calling systems that work without human participation, electronic mail or fax machines, through which individual contact with the recipient is possible, to send a commercial notice unless the recipient has given free and unambiguous consent beforehand.
Article 9(2) lets a service provider that obtained recipients' e-mail addresses in its commercial transactions use them for further commercial notices about its similar goods or services if the recipient did not object at the outset and every later notice gives a clear free-of-charge chance to refuse further use of the address.
Article 9(3) allows other communication through publicly available electronic communications services to send a commercial notice if the recipient has given free and unambiguous consent beforehand, apart from the cases in paragraphs 1 and 2.
Article 9(4) bans sending a commercial notice by electronic mail or other communication through publicly available electronic communications services with an invalid e-mail address, or an invalid telephone or fax number to which the recipient could send a request to stop the communication, or disregarding the recipient's refusal of further notices. Article 9(5) treats each prohibited commercial notice sent as a separate violation.
Article 9(6) applies the bans and restrictions in paragraphs 1, 2 and 3 to commercial notices sent to natural persons.
Article 8(1) requires a commercial notice to meet the general requirements of the Advertising Law, to be clearly recognizable as a commercial notice, to make clear the person on whose behalf it is distributed, to state the offer and the terms of receiving the service precisely, to make discounts, bonuses and prizes and the terms of receiving them clear, to make promotional contests, lotteries and games and their participation terms clear and easy to find, and to give the recipient the chance to refuse further commercial notices.
Article 13(6) obliges the supervisory authority to check compliance with article 9 where one recipient has received at least 10 commercial notices from one provider within a year and has complained to the authority. Article 12(1) has the Consumer Rights Protection Centre (Patērētāju tiesību aizsardzības centrs), the State Data Inspectorate (Datu valsts inspekcija) and other supervisory and control authorities supervise the circulation of information society services within their competence.
Article 13(1) lets a supervisory authority that finds a violation of the Law require the information needed and order the service provider to end the violation or take specific action to remedy it, within a time limit it sets. Article 9 is in the wording of the law of , as amended by the law of , which took effect on . The law of took effect on .
Article 7.1(1) of the Information Society Services Law (Informācijas sabiedrības pakalpojumu likums) allows storing information in a subscriber's or user's terminal equipment, or gaining access to information stored there, only where the subscriber or user has consented after receiving clear and comprehensive information about the purpose of that processing, in accordance with the personal data protection law the provision names.
Article 7.1(2) removes the need for that consent where storing or accessing the information is necessary to ensure the circulation of information in an electronic communications network, or for an intermediary service provider to supply the service the subscriber or user requested. Article 7.1 is in the wording of the law of , as amended by the law of , which took effect on . The law of took effect on .
Article 12(1) has the Consumer Rights Protection Centre (Patērētāju tiesību aizsardzības centrs), the State Data Inspectorate (Datu valsts inspekcija) and other supervisory and control authorities supervise the circulation of information society services within their competence.
Article 13(1) lets a supervisory authority that finds a violation of the Law require the information needed and order the service provider to end the violation or take specific action to remedy it, within a time limit it sets.
Article 94(1) of the Electronic Communications Law (Elektronisko sakaru likums) obliges an electronic communications merchant not to disclose, without the end user's consent, information about the end user or about the electronic communications or value-added services the end user has received, except where the institutions and authorities the Law names need the information for the functions that law sets and for the purposes it sets.
Article 94(2) prohibits an electronic communications merchant from disclosing, without the end user's consent, information that is transmitted or has been transmitted in providing electronic communications services to the end user, except where the authorities the Law names need it for the functions that law sets and for the purposes it sets. The Law was adopted on and took effect on .
Latvia applies the Digital Services Act directly and holds its national layer in Chapter VII.1 of the Information Society Services Act, added by the Act of and in force from . That chapter makes the Consumer Rights Protection Centre the competent authority and digital services coordinator, sets the procedure for proposals, written commitments, interim measures and appeals, and allows fines of up to 6 percent of annual worldwide turnover.
The same Act removed the Act's older Chapter IV on the liability of intermediary service providers. Articles 20 and 21 of the Information Society Services Act set penalties for hosting service providers under the terrorist content Regulation (EU) 2021/784.
Chapter VIII.1 of the Copyright Act makes a provider of an online content-sharing service liable for works its users upload without authorization unless it meets stated conditions, and Chapter XI.1 lets the National Electronic Mass Media Council order providers to stop unlawful publication and restrict access to websites. The Digital Services Act's own duties are held with the European Union's page and are not restated here.
Latvia's rules for electronic mass media, including the protection of minors, are held in the age row. Other national duties of hosting services are not described here.
Article 56.1(1) of the Copyright Act defines an online content-sharing service provider as an information society service provider whose main purpose, or one of whose main purposes, is to store and give the public access to a large number of works or related-rights subject matter uploaded by its users, which it organizes and promotes for profit. Article 56.2(1) requires the provider to obtain the rights holder's authorization for giving the public access to a work uploaded by a user.
Article 56.2(3) makes the provider liable for infringement without authorization unless it proves it made its utmost efforts to obtain authorization, made its utmost efforts to keep unavailable works for which rights holders supplied relevant and necessary information, and acted at once on a substantiated notice to disable access or remove the work and prevent re-upload.
Article 56.2(5) bars the provider from denying access to user uploads whose use does not infringe copyright, including works used under the limitations on economic rights. Article 56.2(7) states that the rules of the article create no general monitoring duty for the provider.
Article 56.3 lets a new provider that has been available in the European Union for under three years with annual turnover under EUR 10 million show only its utmost efforts to obtain authorization and prompt action on a substantiated notice, and adds the duty to prevent re-upload once its average monthly unique visitors exceed five million.
Article 56.4 requires the provider to set an effective and quick procedure to handle users' complaints about disabled access or removal at once and free of charge, with a person reviewing the decision to disable access or remove a work. Article 56.5 requires the provider to give rights holders on request information about its cooperation measures and about the use of works under licences, and to tell users in its terms of service about their options to use works under the limitations on rights.
Article 71.1 of the Copyright Act has the National Electronic Mass Media Council, acting as supervisory authority under the Information Society Services Act, protect rights holders online, including by restricting access to websites that make works public without the rights holder's consent.
Article 71.4(1) requires the Council, after receiving a rights holder's application, to ask the content provider or hosting service provider to submit within seven days documents proving its right to make the works public on the website. Article 71.4(3) has the Council decide that the content provider or hosting service provider must stop making the works public within seven days if it does not stop, does not submit the documents, or cannot be reached.
Article 71.5(1) lets the Council decide to restrict access to a website in Latvia if the unlawful publication has not stopped and no documents proving the right to publish were submitted in time, and it finds that the website obviously infringes copyright or related rights. Article 71.6 allows an appeal against the Council's decisions to the Administrative District Court, and the appeal does not suspend them.
Article 20(1) of the Information Society Services Act provides a warning or a fine for a hosting service provider that fails to restore content or access to it at once under Article 4(7) of Regulation (EU) 2021/784 where restoration is no longer possible, up to 300 fine units for a natural person and up to 3,000 for a legal person.
Article 20(2) provides a warning or a fine up to 400 fine units for a natural person and up to 4,000 for a legal person for not preserving removed or disabled terrorist content and related data for the period set in Article 6 of the Regulation. Article 20(3) applies the same penalties for failing to maintain the technical and organizational safeguards Article 6 of the Regulation requires for preserved content and data.
Article 20(4) applies the same penalties for failing, or failing in good time, to give an investigating authority, a prosecutor, a contact point or Europol the information on terrorist content linked to an imminent threat to life that Article 14(5) of the Regulation requires.
Article 20(5) provides a fine of up to 4 percent of the hosting service provider's total turnover in the previous business year for systematically or persistently failing to remove terrorist content or disable access to it in all Member States within the set time. Article 21 has the State Police conduct administrative violation proceedings for the violations in Article 20.
Article 19.1(1) of the Information Society Services Act makes the Consumer Rights Protection Centre (Patērētāju tiesību aizsardzības centrs) the competent authority under Article 49(1) of the Digital Services Act and the digital services coordinator under Article 49(2). Article 19.1(2) subjects the coordinator to the independence requirements of Article 50 of the Digital Services Act and has it decide independently.
Article 19.2(1) has the Centre perform all the coordinator's tasks and supervise intermediary service providers' compliance with the duties in sections 1 to 4 of Chapter III of the Digital Services Act, unless the European Commission has started proceedings for the same breach against a very large online platform or search engine. Article 19.3(1) lets the coordinator carry out inspections under Article 51(1)(b) of the Digital Services Act without a court's permission.
Article 19.4(1) lets the coordinator propose that a provider ensure compliance by a set deadline or give a written commitment to end the breach. Article 19.4(2) requires the provider to tell the coordinator, at once and within three working days of the end of the deadline, that it has acted on the proposal, with supporting evidence.
Article 19.4(3) lets the coordinator, on finding a breach, order the provider to end it at once or within a set time and impose a fine and a periodic penalty payment. Article 19.5(1) and (2) let the provider give a written commitment to remedy the breach within a set period of no more than three months, unless the nature of the measures justifies a longer one, and the commitment takes effect when the coordinator confirms it.
Article 19.6(1) lets the coordinator fine a provider for breach of the Digital Services Act up to 6 percent of its annual worldwide turnover in the previous financial year, and impose a periodic penalty payment of up to 5 percent of average daily turnover or income for each day. Article 19.6(2) lets the coordinator fine up to 1 percent of annual worldwide turnover for supplying incorrect, incomplete or misleading information, failing to answer or correct it, and refusing an inspection.
Article 19.7(1) lets the coordinator, where recipients may suffer serious harm and urgent action is needed, adopt the decision to end the breach as an interim measure. Article 19.8(1) allows an appeal against the coordinator's decision to the Administrative District Court, which does not suspend the decision except for fines and periodic penalty payments.
The Act of , in force from , removed Chapter IV of the Information Society Services Act, with Articles 10 and 11 on the liability and duties of intermediary service providers.
Product and AI liability law1 instrument, 1 in force
Research summary (153 words)
The Act "Par atbildību par preces un pakalpojuma trūkumiem" (Liability for Defects in Goods and Services) includes, according to its informative reference, legal norms that derive from Directives 85/374/EEC and 1999/34/EC. Section 3(1) applies the Act to any movable corporeal thing, including one that is part of another movable or immovable thing, and to electricity and gas.
Section 3(2) applies the Act to services whose result is that the provider makes a new corporeal thing or improves or alters an existing one or its properties, and to services that have a direct or indirect effect on a person's life or health. No bill transposing Directive (EU) 2024/2853 has been located on likumi.lv, as of . No Latvian statute written for the liability of AI systems or other automated agents has been located.
The National Cybersecurity Law (Nacionālās kiberdrošības likums), which sets the Latvian cybersecurity baseline, is recorded in the security topic.
The Act "Par atbildību par preces un pakalpojuma trūkumiem" (Liability for Defects in Goods and Services) includes, according to its informative reference, legal norms that derive from Directives 85/374/EEC and 1999/34/EC. Section 1 regulates liability for damage done to a person's life, health or property by defects in goods or services. Section 2 leaves untouched the injured person's right to claim compensation under other laws.
Section 3(1) applies the Act to any movable corporeal thing, including one that is part of another movable or immovable thing, and to electricity and gas. Section 3(2) applies the Act to services whose result is that the provider makes a new corporeal thing or improves or alters an existing one or its properties, and to services that have a direct or indirect effect on a person's life or health.
Section 5(1) makes the producer of the goods or the provider of the service liable to compensate the injured person for the damage that defects cause to life, health or property. Section 5(2) makes the producer or service provider liable also where the person bought the goods from a distributor. Section 5(3) forbids reducing or excluding in advance the liability of the producer or service provider for damage to life, health or property. Section 5(4) makes an agreement contrary to section 5 void.
Section 6(1) defines the producer as a natural or legal person who makes the goods or a component, or presents itself as the producer by putting its name, trade mark or another distinguishing mark on the goods, their packaging or their technical documentation. Section 6(2) treats a person who imports goods in the course of its business to put them into circulation in the European Union (the importer) as equal to the producer for liability.
Section 6(3) makes the distributor or any other person who sold or distributed the goods liable where the producer or importer cannot be identified, unless that person gave timely information on the producer, the importer or its own supplier. Section 7(1) treats goods as defective if the safety that a person is entitled to expect is not guaranteed, taking all circumstances into account.
Section 7(2) treats a service as defective if the safety that a person is entitled to expect from it is not guaranteed, taking all circumstances into account. Section 9 makes two or more persons liable for the same damage jointly and severally. Section 10 determines compensation for damage to life or health under the Civil Law.
Section 11(1) allows a claim for damage to property only if another thing than the defective one was damaged, that thing is intended for personal use or consumption and the injured person used it that way, and the damage exceeded 500 euro when it was done. Section 11(2) puts on the injured person the burden of proving the damage, the defect and the causal link between them.
Section 12 allows the producer or service provider to be freed from liability in full or in part where both the defect and the fault of the injured person or another person caused the damage. Section 13(1) frees the producer from liability if it proves that it did not put the goods into circulation. Section 13(1) also frees the producer if it proves that there is reason to believe the defect arose after the goods were put into circulation.
Section 13(1) also frees the producer if it proves that the goods were not made for sale or other distribution for profit, nor made or distributed in the course of business. Section 13(1) also frees the producer if it proves that the state of science and technology when the goods were put into circulation was not advanced enough to allow the defect to be discovered.
Section 13(1) also frees the producer if it proves that the defect arose because the producer complied with requirements set by the State or a municipality. Section 13(3) frees the maker of a component if it proves that the defect is linked to the design of the thing the component was built into or to the instructions of the producer or service provider.
Section 14(1) requires a claim for compensation to be brought within three years from the day the injured person learned, or had reason to know, of the defect, the damage and the person liable to compensate. Section 14(2) bars a claim once ten years have passed from the day the producer put the goods into circulation or the provider gave the service. The Act was adopted by the Saeima on and entered into force on .
Latvia's national age law sits in the Elektronisko plašsaziņas līdzekļu likums (Electronic Mass Media Law), which transposes the EU Audiovisual Media Services Directive's minor-protection and video-sharing-platform provisions.
A broadcast or on-demand audiovisual service carrying content that could harm a minor's physical, mental, or moral development must either keep it outside a 7:00 to 22:00 watershed or provide restricted access control, preceded by an acoustic warning and marked with a visual content symbol; an on-demand catalogue carries the same restricted-access-control duty.
A video-sharing platform provider must take appropriate measures against content and user-generated commercial communications that could harm minors and must publish its own code of conduct addressing communications aimed at or capable of affecting minors' development. No dedicated social-media minimum-age statute or app-store age-verification duty is on the books as of the date below.
Article 24(9) bans distributing audio and audiovisual works depicting physical or psychological violence, bloody or horror scenes, drug use or sexual acts, or containing coarse or indecent language, between 7:00 and 22:00.
Article 24(10) requires an electronic mass medium not observing that watershed for content that could harm a minor's physical, mental, or moral development to instead provide restricted access control, preceded by an acoustic warning signal and marked with a visual symbol describing the content's potentially harmful nature. Article 23(4) imposes the equivalent restricted-access-control duty on an on-demand catalogue offering such content.
Article 24(10.1) bars commercial use of a minor's personal data obtained through that access control, except where necessary to provide the service itself with the data subject's consent.
In the Electronic Mass Media Law, a video-sharing platform service is a service or separable part of one that carries no editorial responsibility, whose essential functionality is mainly to offer the general public programmes and user-generated videos, and whose organization the provider determines, including by automatic means or algorithms.
A video-sharing platform provider must take appropriate measures to protect the public from content and user-generated video or audio commercial communications that could harm minors' physical, mental, or moral development, that could incite violence or hatred, or that constitute a listed criminal offence.
It must publish its own publicly accessible code of conduct addressing commercial communications aimed at or capable of negatively affecting the psychological or physical development of minors, including in children's programming.
Latvia transposed the EU Digital Single Market Copyright Directive's press-publisher neighbouring right and text-and-data-mining exceptions into the Autortiesību likums (Copyright Law) through amendments adopted and in force from .
Article 53.1 gives a press publisher an exclusive right to reproduce and make available online its press publications, running two years from publication, and excluding private or non-commercial use, hyperlinks, and single words or very short extracts.
Article 21.1 permits reproducing a lawfully accessible work, including news content, for text and data mining, unless the rights holder has expressly and machine-readably reserved that use; a separate exception in Article 21.2 covers research organizations and cultural heritage institutions.
Latvia has no compelled platform-to-publisher bargaining regime comparable to Australia's News Media Bargaining Code or Canada's Online News Act, and no hot-news or misappropriation doctrine distinct from ordinary unfair-competition law exists in the primary text.
Autortiesību likums 53.1 pants, pievienots ar 2023. gada 23. marta likumu 'Grozījumi Autortiesību likumā' (Latvijas Vēstnesis, 67, 04.04.2023.), stājas spēkā 05.04.2023.Grozījumi Autortiesību likumā (2023 Copyright Law amendments transposing Directive (EU) 2019/790), official text, likumi.lv
In force since .Binds private bodies.
What this law does
A press publisher holds an exclusive right to reproduce and make available online its press publications, defined as a journalistic compilation published under one title in a periodical or regularly updated edition, exercised against an information-society service provider. The right does not reach private or non-commercial use, hyperlinks, or the use of single words or very short extracts.
It cannot be invoked to prohibit use of works the publisher included under a simple licence, or whose copyright or related-rights term has expired, and runs for two years after the press publication is made public. An author whose work is included in a press publication has a right to a proportionate share of the revenue the publisher earns from this online use.
Autortiesību likums (aggregation) 21.1 pants, pievienots ar 2023. gada 23. marta likumu 'Grozījumi Autortiesību likumā' (Latvijas Vēstnesis, 67, 04.04.2023.), stājas spēkā 05.04.2023.Grozījumi Autortiesību likumā (2023 Copyright Law amendments transposing Directive (EU) 2019/790), official text, likumi.lv
In force since .Binds public and private bodies.
What this law does
Article 21.1 permits reproducing a lawfully accessible work, including a press publication or its fragments, to carry out text and data mining. Copies made for that purpose may be kept only as long as needed for the mining. A rights holder, including a press publisher, can prohibit this use by giving clear notice in an appropriate manner.
A prohibition on the online use of publicly accessible works must be given in machine-readable form, including through metadata, which is the opt-out an aggregator's automated indexing must honor. A separate exception at Article 21.2 covers a research organization or a cultural heritage institution mining lawfully accessible works for scientific research, without that opt-out.
No current case law for Latvia content moderation law
No current case law for Latvia product and AI liability law
No current case law for Latvia digital accessibility law
No current case law for Latvia age gating law
No current case law for Latvia 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 Latvia 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.
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.
Immediately take all action necessary to contain a detected cyber incident, immediately inform the competent cyber incident prevention institution (for most private-sector and civilian public-sector subjects, the Institute of Mathematics and Computer Science of the University of Latvia), and follow its instructions.
For a significant cyber incident, electronically submit an early warning to the competent institution without delay and no later than within 24 hours.
Follow with an initial report without delay and no later than within 72 hours (within 24 hours instead, if you are a trust service provider).
Within one month of the initial report, submit a final report on the incident's resolution, or, if it is still unresolved at that point, a progress report followed by a final report once you have resolved it; submit an intermediate report if the competent institution requests one.
Where relevant, immediately inform your service recipients, including affected network or system users, of protective measures they can take, and, after coordinating with the competent institution, inform them of the significant incident or threat itself, unless disclosure would create a new significant-incident risk or conflict with national security.
Notify the Data State Inspectorate without undue delay, and within 72 hours where feasible, after becoming aware of a personal data breach affecting a person in Latvia, 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.
Where you discover a vulnerability in a subject's information system or electronic communications network, report it to the competent institution within five working days; you may report anonymously and ask that your identity be kept confidential.
The law of the European Union, which applies in Latvia
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)).
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.
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).
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.
Make each notification without undue delay and in any case no later than 24 hours after you become aware of the security breach or disruption (Article 19a(1), point (b)).
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.
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.
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.
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)).
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)).
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)).
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)).
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.
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)).
Where such a system presents a risk within the meaning of Article 79(1), immediately inform the provider or importer and the authorities competent for the system, giving details, in particular, of the non-compliance and of any corrective actions taken (Article 24(4)).
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.
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.
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)).
Transmit the report to the certification body or the national cybersecurity certification authority, in accordance with Article 56(8) of Regulation (EU) 2019/881, without undue delay (Article 35(4)).
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.
AIDrafted 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.