Law / Slovakia

Slovakia

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

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

in forcenot yet in forceblocked by a courtproposedno longer in force

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

AI law2 instruments, 1 in force, 1 proposed

Research summary (190 words)

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

Slovakia's implementing law, which would designate the Act's national supervisory authorities and set national penalties, is a draft: the Ministry of Investments, Regional Development and Informatization (MIRRI) submitted an integrated draft act for inter-departmental comment on , and MIRRI's release of states that the reworked draft does not provide for a new central state authority, and the Government adopted resolution No. 349/2026 on the bill on , after which the bill was delivered to the National Council on as parliamentary print 1447, where it stands at first reading.

Slovakia's Trestny zakon (Criminal Code) defines child pornography, at section 132(4), to include a simulated depiction of sexual activity with a child or with a person appearing to be a child, so its distribution and possession offences at sections 369 and 370 reach a simulated depiction and are not limited to an actual sexual act with a real child; the Code does not say in terms whether a wholly computer-generated image is covered.

AI governance

Draft Act on Organisation of Public Administration in the Field of Artificial Intelligence

Integrated draft act (Government material UV-23232/2026, delivered to the National Council of the Slovak Republic on as parliamentary print 1447; earlier registered with the Legislative Council of the Government as LRV-22028/2026 on ; first submitted by MIRRI for inter-departmental comment on ); would amend Act 575/2001 Coll. and related actsMinistry of Investments, Regional Development and Informatization of the Slovak Republic (MIRRI), press releases on the draft act

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

Binds public and private bodies.

What this law does

The Ministry of Investments, Regional Development and Informatization (MIRRI) submitted the draft for inter-departmental comment on to implement the EU AI Act's institutional arrangements in Slovakia. In February 2026 MIRRI stated that oversight of the Act in Slovakia would be provided by a new Office for Digital Integrity established under MIRRI. In its release of MIRRI states that the reworked draft does not provide for a new central state authority.

The key role in state administration in the field of artificial intelligence and in central data management falls to MIRRI together with other competent authorities. According to that release the draft goes next to the Legislative Council of the Government and then to the Economic and Social Council.

The Government's portal lists the draft act on state administration in the field of artificial intelligence and European data regulation as material LRV-22028/2026, registered on and placed as agenda item 2 of the 51st meeting of the Legislative Council of the Government. MIRRI states that the draft is then to be submitted to the Government. The Government adopted resolution No. 349/2026 on the bill at its 151st session on .

The Government's bill was delivered to the National Council on as parliamentary print 1447. The National Council's page for the print shows the stage of the legislative process as first reading. By resolution the National Council assigned the Committee on Public Administration and Regional Development as lead committee, with a deadline of .

What it requires

AI prohibited practices

Trestný zákon, Child Pornography Including Simulated Depictions

Act 300/2005 Coll. (Trestny zakon), ss. 132(4), 368-370Official consolidated text of the Trestny zakon, Slov-Lex (Ministry of Justice of the Slovak Republic)

In force since . Binds public and private bodies.

What this law does

Section 132(4) defines child pornography, for the purposes of the Trestny zakon, as a depiction of real or simulated sexual intercourse, another form of sexual contact, or similar sexual activity with a child or a person appearing to be a child, or a depiction of the exposed body parts of a child or a person appearing to be a child for sexual purposes.

Because that definition reaches a simulated act and a person merely appearing to be a child, it is not limited to a depiction of an actual sexual act with a real child; the Code does not say in terms whether a wholly computer-generated image is covered.

Section 368 punishes using, obtaining, offering or otherwise exploiting a child for the production of child pornography or a child-pornographic performance, or otherwise taking part in such production, with imprisonment of four to ten years, rising to seven to twelve years, ten to fifteen years, or twelve to twenty years for aggravated forms.

Section 369 punishes reproducing, transporting, procuring, making accessible, or otherwise distributing child pornography with imprisonment of one to five years, rising to three to eight years, four to ten years, or seven to twelve years for aggravated forms. Section 370 punishes possessing child pornography, or acting with intent to access it through an electronic communication service, with imprisonment of up to two years.

What it requires

Privacy law7 instruments, 7 in force

Research summary (84 words)

Slovakia gives the General Data Protection Regulation (GDPR) domestic effect through Act No. 18/2018 Coll. on the Protection of Personal Data. Section 16 restates the prohibition on processing special categories of personal data, which include biometric data, and Section 78(5) lets a controller process genetic, biometric and health data on the legal basis of a special regulation or an international agreement that binds Slovakia.

Section 78(4) limits use of the generally usable identifier, which is the birth number, and Sections 40 and 41 repeat the breach notification rules.

Breach notification

GDPR Articles 33-34, Breach Notification

Regulation (EU) 2016/679, Arts. 33-34GDPR Arts. 33-34

In force since . Binds public and private bodies.

What this law does

A controller must notify the Office for Personal Data Protection of the Slovak Republic without undue delay and, where feasible, not later than 72 hours after becoming aware of a personal-data breach, and notify the affected individual without undue delay where the breach is likely to result in a high risk.

Section 40(1) of Act No. 18/2018 Coll. states a 72-hour deadline from the time the controller becomes aware, which does not apply where the breach is unlikely to result in a risk to the rights of a natural person, and Section 40(2) requires a controller that misses it to give reasons for the delay. Section 41(1) requires the controller to tell the data subject without undue delay where the breach may lead to a high risk to the rights of a natural person.

What it requires

Comprehensive regime

Act on the Protection of Personal Data

Zakon c. 18/2018 Z. z. o ochrane osobnych udajov a o zmene a doplneni niektorych zakonovAct No. 18/2018 Coll., consolidated text on static.slov-lex.sk

In force since . Binds public and private bodies.

What this law does

Slovakia gives the General Data Protection Regulation (GDPR) domestic effect through Act No. 18/2018 Coll. on the Protection of Personal Data, effective . Section 13(1) lists the legal bases on which processing is lawful, including the data subject's consent, a contract, a special regulation or an international agreement that binds Slovakia, and the legitimate interests of the controller or a third party.

What it requires

Cross border transfer

GDPR Chapter V, Cross-Border Transfer Restrictions

Regulation (EU) 2016/679, Arts. 44-49GDPR Arts. 44-49, 83(5)(c)

In force since . Binds public and private bodies.

What this law does

A transfer of personal data outside the EEA requires an adequacy decision, appropriate safeguards, or a narrow Article 49 derogation, backed by the Article 83(5)(c) top fine tier. Section 48(1) and (2) of Act No. 18/2018 Coll. allow a transfer to a third country where the Commission has decided that it ensures an adequate level of protection, and otherwise only where appropriate safeguards are provided.

Section 48(4) adds that safeguards may also rest on contractual clauses between the controller or processor and a recipient in the third country, on the authorisation of the Office. Section 51(1) allows a transfer with neither only in the listed special situations, such as the data subject's explicit consent after being told of the risks.

What it requires

Data subject rights

GDPR Article 22, Automated Decisions in Slovakia

Regulation (EU) 2016/679, Arts. 13(2)(f), 14(2)(g), 15(1)(h) and 22; Zákon č. 18/2018 Z. z., § 28Official 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 Slovakia 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.

Section 28 of Act No. 18/2018 Z. z. restates this rule without adding an authorisation or safeguard.

What it requires

GDPR Articles 12-21, Data Subject Rights in Slovakia

Regulation (EU) 2016/679, Arts. 12-21; Zákon č. 18/2018 Z. z.Official 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 Slovakia 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.

Act No. 18/2018 Z. z. restates these rights and, in Section 78(8) and (9), allows a separate law or treaty to restrict access, rectification, restriction and objection, and for archiving also portability, for research, statistics and archiving under safeguards; it never allows erasure or the automated-decision right to be restricted that way.

What it requires

Enforcement supervision

Office for Personal Data Protection Enforcement and GDPR Article 82

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

In force since . Binds public and private bodies.

What this law does

Urad na ochranu osobnych udajov Slovenskej republiky (Office for Personal Data Protection of the Slovak Republic) is the supervisory authority under section 81(1) of the Slovak Personal Data Protection Act of 2018. Section 104(2) of that Act lets the Office fine up to EUR 20,000,000, or for an undertaking up to 4 percent of total worldwide annual turnover for the preceding financial year, whichever is higher. General Data Protection Regulation (GDPR) Article 82 arms an individual with a direct private right of action against the controller or processor.

What it requires

Sensitive categories

GDPR Article 9 and Act Section 78, National Birth Number

Regulation (EU) 2016/679, Art. 9; Zakon c. 18/2018 Z. z., section 78Act No. 18/2018 Coll., Sections 16 and 78, consolidated text on static.slov-lex.sk

In force since . Binds public and private bodies.

What this law does

General Data Protection Regulation (GDPR) Article 9(1) treats biometric data processed for unique identification as a special category. Section 16(1) of Act No. 18/2018 Coll. restates the prohibition on processing special categories of personal data, which include biometric data. Section 78(5) lets a controller process genetic, biometric and health data on the legal basis of a special regulation or an international agreement that binds Slovakia, a general enabling clause rather than a biometric-specific rule.

Section 78(4) allows the generally usable identifier to be used to identify a person only where that use is necessary for the purpose, requires consent to its processing to be explicit, and prohibits publishing it unless the data subject publishes it themself. The special regulation that the generally usable identifier points to is Act 301/1995 Coll. on the birth number (rodne cislo).

What it requires

Scraping law3 instruments, 3 in force

Research summary (413 words)

Slovakia's Trestný zákon (Criminal Code), Act No. 300/2005 Coll., criminalises unauthorised access to a computer system at section 247 only where the offender overcomes a security measure, so crawling a public, unauthenticated page without defeating any access control falls outside a plain reading of the provision.

Sections 247a to 247d punish unauthorised interference with a system's functioning, unauthorised damage to computer data, unauthorised interception of a non-public transmission, and the production or possession of an access device with intent to commit one of those offences; none of them reaches the ordinary reading or copying of data that a page openly serves, so plain crawling of public content sits outside sections 247 to 247d as a group, and no separate civil doctrine treats heavy automated traffic to a server, on its own, as an actionable trespass distinct from the data-damage conduct sections 247a and 247b already cover.

The Autorský zákon (Copyright Act), Act No. 185/2015 Coll., as amended by Act No. 71/2022 Coll. transposing the EU Digital Single Market Copyright Directive, gives a library, archive, museum, school or statutory depositary a text-and-data-mining exception for research at section 51b that carries no rightsholder opt-out, and a general text-and-data-mining exception for any person at section 51c, defeated by an express rightsholder reservation that the text ties to no particular form, so a robots.txt directive can serve as that reservation.

General contract-formation rules under the Občiansky zákonník bind a crawler only to terms it actually had notice of and accepted: section 43c treats a timely act from which consent can be inferred, such as agreeing at signup, as acceptance, while section 44 keeps silence or inaction on its own outside that rule, so terms posted only via a link a crawler never encountered do not bind it under this rule.

The Obchodný zákonník's section 273 lets general terms bind by reference, but that part of the Code governs only obligations between entrepreneurs that evidently concern their business activity, so it reaches a website's terms only where both the site operator and the crawler operator act as entrepreneurs in their business.

The Autorský zákon also gives the maker of a database that shows a substantial investment the exclusive right to consent to extraction or reutilization of its whole contents or a substantial part (Sections 135 to 139). No Slovak court decision addresses a sui generis database right's application to scraped content, or whether a cease-and-desist letter alone, without a security measure, changes what section 247 treats as authorised.

Computer misuse

Trestný zákon, Unauthorized Access to a Computer System and Related Offences

Act 300/2005 Coll. (Trestny zakon), ss. 247-247dOfficial consolidated text of the Trestny zakon, Slov-Lex (Ministry of Justice of the Slovak Republic)

In force since . Binds public and private bodies.

What this law does

Section 247 punishes a person who overcomes a security measure and thereby obtains unauthorized access to a computer system or part of it with imprisonment of up to two years, rising to six months to three years where the act is committed in a more serious manner or causes significant damage, and to one to five years where it causes large-scale damage or is committed as a member of a dangerous grouping.

Because the offence applies only where a security measure is overcome, reading a public, unauthenticated page without defeating any access control falls outside the wording of this section.

Section 247a punishes unauthorized interference with a computer system's operation, section 247b unauthorized interference with computer data, section 247c unauthorized interception of non-public computer-data transmissions, and section 247d the production, import, or sale of a device, password, or access code created for unauthorized access to a computer system, each with escalating tiers.

The most serious forms of sections 247a, 247b and 247c carry two to eight years' imprisonment, and the most serious form of section 247d carries one to five years.

What it requires

Copyright and text and data mining (TDM)

Autorský zákon, TDM Exception

Act 185/2015 Coll., ss. 51b-51c (as amended by Act 71/2022 Coll.), scrapingOfficial consolidated text of the Autorsky zakon, Slov-Lex (Ministry of Justice of the Slovak Republic)

In force since . Binds public and private bodies.

What this law does

Section 51b, inserted by Act 71/2022 Coll., lets a library, archive, museum, school, or statutory depositary reproduce a work for text-and-data-mining for research purposes without the author's consent, with no rightsholder opt-out. It lets the reproduction be retained for research purposes, including verifying the research results. Section 51c gives any person a general text-and-data-mining exception, defeated where the rightsholder has expressly reserved that use.

A reproduction made under section 51c may be kept only as long as needed for the mining. Section 51b(2) defines data mining, for the purposes of the Act, as any automated analytical technique aimed at analysing data in digital form to obtain patterns, trends, correlations, or similar results.

What it requires

Database right

Autorský zákon, Special Right to a Database (Sections 135 to 139)

Act 185/2015 Coll. (Autorský zákon), ss. 135-139Slov-Lex, consolidated text of Act No. 185/2015 Coll. in force from (Ministry of Justice of the Slovak Republic)

In force since . Binds public and private bodies.

What this law does

A database that shows a qualitatively or quantitatively substantial investment in obtaining, verifying or presenting its contents gives its maker the exclusive right to use the database and to consent to extraction or reutilization of its whole contents or of a qualitatively or quantitatively substantial part. The maker is the person who initiated and secured the making of the database.

Extraction is the permanent or temporary making of a copy of the database by transferring its whole contents or a substantial part to another medium by any means in any form. Reutilization is any way of making the whole contents of the database or a substantial part available to the public, including distributing copies by transfer of ownership and by rental.

Repeated and systematic extraction or reutilization of insubstantial parts of the contents is prohibited if it conflicts with the normal use of the database and unreasonably interferes with the maker's legally protected interests. A user may extract or reutilize a qualitatively and quantitatively insubstantial part of the contents for any purpose without the maker's consent.

A user of a publicly accessible database must not use it against the normal use of the database or unreasonably interfere with the maker's legally protected interests. Extraction or reutilization by use under Sections 49a, 51b and 51c is among the listed exceptions to the special right. The right lasts 15 years from the making of the database or from the day public access to it was allowed, whichever came later. The right ends on the last day of the calendar year in which the 15 years expire. The Act entered into force on .

What it requires

Cybersecurity law5 instruments, 5 in force

Research summary (430 words)

Slovakia transposed the NIS2 Directive (Directive (EU) 2022/2555) on time through Zákon č. 366/2024 Z. z., approved by the National Council on and in force since , amending the existing Zákon č. 69/2018 Z. z. o kybernetickej bezpečnosti (Cybersecurity Act) rather than restating it in a fresh instrument; two further amendments (Zákon č. 318/2025 Z. z. and Zákon č.

67/2026 Z. z., effective and respectively) have since adjusted the same consolidated text.

The amended Act binds an essential-service operator (prevádzkovateľ základnej služby), a category that reaches a medium or larger enterprise in a named sector and a public-administration body alike, and it expressly names the digital providers: a DNS, domain-registration, cloud computing, data-centre, content-delivery-network, managed-service, security-service, online marketplace, online-search-engine or social-networking-platform provider.

Its Section 19 and Section 20 set a general security-measures duty across 18 named domains, backstopped by a National Security Authority (Národný bezpečnostný úrad, NBÚ) Decree that specifies their manner and scope, and its Section 24 sets NIS2's own graduated notification clock (24-hour early warning, 72-hour notification, one-month final report), extended to a significant threat, a near-miss and an unremediated vulnerability in the operator's own networks.

Rather than adopting NIS2's "essential entity"/"important entity" labels, the Act layers a "critical basic service" (kritická základná služba) designation, broadly a large-enterprise or specially critical subset of essential-service operators under Section 18, onto the same register: an operator without that designation faces an administrative fine of up to the greater of EUR 7,000,000 or 1.4% of worldwide turnover for breaching these duties, one with it up to the greater of EUR 10,000,000 or 2%, mirroring NIS2 Article 34's own two tiers in substance if not in name.

A separate provision gives the Authority's national computer security incident response team (CSIRT) unit, not the manufacturer, the coordinated-vulnerability-disclosure role for a vulnerability reported about an ICT product or service.

No located Slovak instrument sets a product-security or market-placement duty on a manufacturer independent of the directly applicable EU Cyber Resilience Act, which is documented at the European Union level and is not restated here, and no located instrument sets a general reasonable-security or information-security-programme duty with no sector gate; the closest general duty is General Data Protection Regulation (GDPR) Article 32's security-of-processing obligation and the GDPR Article 33-34 breach-notification duty to the Úrad na ochranu osobných údajov (Office for Personal Data Protection) that Zákon č.

18/2018 Z. z. gives effect to, both of which sit in the privacy topic rather than here. The Act also reaches the broader sector classes by designation (energy, transport, banking, health, water, digital infrastructure and public administration).

Sector security regimes

Vyhláška MD SR č. 111/2026 Z. z., Transport Sector Security Measures

Vyhláška Ministerstva dopravy Slovenskej republiky č. 111/2026 Z. z. o sektorových bezpečnostných opatreniach (25. mája 2026)Zbierka zákonov Slovenskej republiky, 111/2026 Z. z., Slov-lex, časová verzia účinná od 01.07.2026

In force since . Binds public and private bodies.

What this law does

Decree 111/2026 of the Ministry of Transport (Vyhláška Ministerstva dopravy Slovenskej republiky) sets the sector security measures in the Ministry's remit, was approved on , promulgated on and took effect on . Section 1 sets the sector cyber security measures for rail transport in Annex 1 and for road transport in Annex 2. The Ministry issues the decree in cooperation with the National Security Authority under Section 32(2) of Act 69/2018.

What it requires

Vyhláška NBÚ č. 227/2025 Z. z., Security Measures and Security Documentation

Vyhláška Národného bezpečnostného úradu č. 227/2025 Z. z. o bezpečnostných opatreniach (26. augusta 2025), § 1 až 6Zbierka zákonov Slovenskej republiky, 227/2025 Z. z., Slov-lex, časová verzia účinná od 01.09.2025

In force since . Binds public and private bodies.

What this law does

Decree 227/2025 of the National Security Authority on security measures (Vyhláška Národného bezpečnostného úradu o bezpečnostných opatreniach) was approved on , promulgated on and took effect on , and repealed Decree 362/2018.

It sets the content of the security measures, the scope of the general security measures for networks, information systems and operational technologies, and the content and structure of the security documentation under Section 20 of Act 69/2018.

The security documentation contains an approved cyber security strategy, approved security policies, a classification of information, the assignment of networks and information systems to a category, a risk analysis with the level of identified, accepted and residual risks and a list of assets, a documented determination of the security measures adopted and not adopted with reasons, and the last final audit report.

Risk management includes asset identification, risk identification, risk analysis, risk assessment, adoption of security measures with reasons for any measure not adopted, and a review of the identified risks at least once a year. The operator keeps a centrally managed register of assets, made up of primary assets, supporting assets, asset owners and the persons responsible for identifying and recording the assets.

Section 20(3) of Act No. 69/2018 has security measures adopted and carried out in the scope and manner this decree sets, or that a special regulation sets where one has been issued. The Act's note 24 to that special regulation gives Regulation (EU) 2022/2554 (DORA) as its first example. Section 29(9) has an essential-service operator that DORA covers verify the effectiveness of its security measures under DORA.

What it requires

Zákon o kybernetickej bezpečnosti (Cybersecurity Act), Risk-Management Measures

Zákon č. 69/2018 Z. z. o kybernetickej bezpečnosti a o zmene a doplní niektorých zákonov, v znení zákona č. 366/2024 Z. z., §§ 17 až 20Consolidated text of Zákon č. 69/2018 Z. z., Slov-Lex, version effective from (amended by Zákon č. 67/2026 Z. z.)

In force since . Binds public and private bodies.

What this law does

Section 17 requires a person the sector annexes reach, including a central state-administration body and a digital provider named at Section 2(2) (DNS, domain-name registration, cloud computing, data centre, content delivery network, managed service, security service, online marketplace, online search engine or social-networking-services platform), to register as an essential-service operator (prevádzkovateľ základnej služby); a person meeting at least the medium-enterprise size threshold in an Annex 1 or Annex 2 sector registers under Section 17(1)(e).

Section 19(1) then requires the operator to adopt, maintain and carry out general security measures, within 12 months of registration and graded by its own risk analysis, covering at minimum the 18 domains Section 20(2) lists (security governance, vulnerability and threat management, asset and risk management, incident handling, business continuity and backup, secure development and acquisition, compliance monitoring, cryptography, human-resources security, identity and access management, network operations security, malware and unwanted-content protection, system, network and communications security, event logging and monitoring, physical and endpoint security, records and privacy protection, supply-chain security, and the use of certified ICT products, services and processes), and Section 19(6)(h) requires the operator to build an effective mechanism for promptly informing its statutory body and responsible senior staff about cyber threats, incidents, near-misses and risk-treatment status.

Section 18 defines a "critical basic service" (kritická základná služba) to include the exercise of a central state-administration body's functions.

It also includes, broadly, a large enterprise (above the medium-enterprise threshold) active in an Annex 1 sector other than public administration, and separately a qualified trust service, a top-level domain (TLD) registry, a DNS service, or an at-least-medium-sized public electronic communications network or service; an operator with this status must itself report it to the Authority, and it draws a higher administrative-penalty tier for the same duties.

The Act transposes NIS2 Article 21 without adopting NIS2's own "essential entity"/"important entity" labels; the National Security Authority's implementing Vyhláška (Decree) on security measures, referenced at Section 20(3), specifies the manner and scope in which these measures are carried out.

What it requires

Vulnerability and incident reporting

Vyhláška NBÚ č. 226/2025 Z. z., Details of Cyber Security Reports

Vyhláška Národného bezpečnostného úradu č. 226/2025 Z. z. o podrobnostiach o hláseniach (26. augusta 2025)Zbierka zákonov Slovenskej republiky, 226/2025 Z. z., Slov-lex, časová verzia účinná od 01.09.2025

In force since . Binds public and private bodies.

What this law does

Decree 226/2025 of the National Security Authority (Vyhláška Národného bezpečnostného úradu) sets the details of reports under Act 69/2018 on cyber security, was approved on , promulgated on and took effect on .

Annex 1 defines the criteria for a serious disruption of the operation of an essential service operator, among them a complete outage of more than 30 minutes for an operator of a critical essential service or 60 minutes for another essential service operator, an impairment of more than 60 or 180 minutes, an economic loss above 0.1 percent of gross domestic product and a loss to at least one user above EUR 250,000.

Annex 2 sets what a report of a serious cyber security incident under Section 24(3)(a) and (b) of the Act contains, namely the reporter's identity and contact data and the time of detection, a description of the incident and its consequences or expected scope, whether it may have been caused by unlawful conduct, whether it may have cross-border impact and the effect on trust services, and, in the follow-up report, updated information and the status and reactive measures taken.

Annex 3 sets what a report of a significant cyber threat, a near miss or a vulnerability under Section 24(5), and a report of an incident, threat or near miss under Section 24(6), contains, and for a vulnerability also the identification or description of the ICT product, ICT service or operational technology concerned and its manufacturer or provider where known to the reporter.

Section 24(8) of Act No. 69/2018, whose reports this decree details, has an essential-service operator that Regulation (EU) 2022/2554 (DORA) covers meet its reporting duty by reporting a major ICT-related incident through DORA's competent authority, in the scope, manner and time limits DORA sets.

What it requires

Zákon o kybernetickej bezpečnosti (Cybersecurity Act), Incident and Vulnerability Notification

Zákon č. 69/2018 Z. z. o kybernetickej bezpečnosti a o zmene a doplní niektorých zákonov v znení zákona č. 366/2024 Z. z., § 24 a § 5 ods. 5Consolidated text of Zákon č. 69/2018 Z. z., Slov-Lex, version effective from (amended by Zákon č. 67/2026 Z. z.)

In force since . Binds public and private bodies.

What this law does

Section 24(1) requires an essential-service operator to report every significant cyber security incident (závažný kybernetický bezpečnostný incident), defined at (2) as a large-scale incident, or one that has caused or may cause serious disruption to the operator or large-scale damage or lost profit, or that has affected or may affect others with significant harm.

Section 24(3) sets the graduated clock NIS2 Article 23 requires, beginning with an early warning reported without undue delay and no later than 24 hours from detection. No later than 72 hours from detection, the operator must report a notification updating that early warning with an initial severity and impact assessment, and must report further updates on the computer security incident response team (CSIRT) unit's request. A final report is due no later than one month after that 72-hour notification.

Where an incident with cross-border impact is still ongoing when that final report is due, an updated final report is due within 30 days of restoring normal network and system operation, and where any significant incident is still ongoing when the final report is submitted, further information and an updated final report are due within 30 days of its resolution.

Section 24(5) extends the same reporting channel to a significant cyber threat the operator becomes aware of, a near-miss event that could have caused a significant incident, and a vulnerability in the operator's own publicly available networks or systems that it could not remediate or mitigate in reasonable time.

Section 24(8) lets an operator that is a financial entity under the EU Digital Operational Resilience Regulation (Regulation (EU) 2022/2554) satisfy this duty instead by reporting a major ICT-related incident through DORA's own competent-authority channel.

Separately, Section 5(5) gives the Authority, acting through its national CSIRT unit, a coordinator role for communication about a discovered or reported vulnerability among the essential-service operator, the manufacturer or supplier of the affected ICT product or ICT service, and other affected persons, a duty the Act places on the Authority rather than on the manufacturer directly.

What it requires

Communications law4 instruments, 4 in force

Research summary (186 words)

Slovakia regulates direct marketing, cookies and telecommunications secrecy in zákon č. 452/2021 Z. z. o elektronických komunikáciách (Electronic Communications Act). Section 116 allows automated calling systems, telefax, e-mail, SMS and MMS for direct marketing only with provable prior consent, with an exemption for a person's own similar goods and services sold to the recipient, and keeps a list of telephone numbers that may not be called for direct marketing.

Section 109, paragraph 8 allows storing or accessing information on a user's terminal device only with provable consent, with exceptions for transmission and for a service the user expressly requests. Section 117 requires everyone who comes into contact with the content of messages, traffic data and location data to maintain their secrecy.

The Regulatory Authority for Electronic Communications and Postal Services imposes fines of up to 5 percent of turnover for breaches of sections 116 and 109, paragraph 8, and up to 10 percent for breaches of section 117, paragraph 2. A data subject's right to object to direct marketing is held in the privacy row for General Data Protection Regulation (GDPR) Articles 12 to 21, Data Subject Rights in Slovakia.

Commercial messages

Electronic Communications Act, Section 116, Paragraphs 3 to 6 and 14 to 16, Consent, Withdrawal and Opt-out for Direct Marketing

Zákon 452/2021 Z. z., § 116 ods. 3-6 a 14-16Text of zákon č. 452/2021 Z. z. o elektronických komunikáciách

In force since . Binds public and private bodies.

What this law does

Section 116, paragraph 3 of the Electronic Communications Act allows the use of automated calling and communication systems without human intervention, telefax, e-mail, SMS and MMS for direct marketing to a subscriber or user only with their provable consent obtained before contacting them. Section 116, paragraph 4 prohibits calling, and using automated calling and communication systems without human intervention, telefax, e-mail, SMS and MMS, for the purpose of obtaining that consent.

Section 116, paragraph 5 requires the person to whom consent was given to keep a durable medium recording the provable consent for at least four years from its withdrawal. Section 116, paragraph 5 also requires a person doing direct marketing to state, when obtaining consent, how the consent can easily be withdrawn.

Section 116, paragraph 6 lets a subscriber or user withdraw consent or object to calls at any time, and requires the person concerned to confirm the withdrawal or objection provably within 30 days and to keep the confirmation on a durable medium for at least four years.

Section 116, paragraph 15 removes the prior consent requirement for e-mail, SMS and MMS direct marketing of the person's own similar goods and services where the person obtained the contact details in connection with a sale, and for marketing addressed to the published contact details of a subscriber or user who is a sole trader or a legal person.

Section 116, paragraph 15 requires that the recipient be given a possibility to refuse that use of contact details easily and free of charge at any time, when the details are collected and in every message delivered, if the recipient has not refused before.

Section 116, paragraph 15 prohibits sending e-mail from which the identity and address of the sender, to which the recipient can send a request to end such messages, are not known, and encouraging a visit to a website in breach of a special regulation. Section 116, paragraph 16 allows contact details obtained in connection with a sale to be used under paragraphs 14 and 15 for one year after the end of the contractual relationship.

Section 124, paragraph 3 makes a breach of section 116, paragraphs 3 to 6, 8, 12 and 14 to 16 punishable by a fine of EUR 200 up to 5 percent of turnover for the previous accounting period. Section 124, paragraph 6 limits the fine under paragraphs 1 to 3 to EUR 300,000 where the person had no turnover for the previous accounting period or the turnover cannot be calculated.

Section 134 provides that the Act takes effect on , except that paragraph 12 of section 116 takes effect on and paragraphs 7 to 10 of section 116 take effect on .

What it requires

Device storage and tracking consent

Electronic Communications Act, Section 109, Paragraph 8, Consent for Storing or Accessing Information on a User's Terminal Device

Zákon 452/2021 Z. z., § 109 ods. 8Text of zákon č. 452/2021 Z. z. o elektronických komunikáciách

In force since . Binds public and private bodies.

What this law does

Section 109, paragraph 8 of the Electronic Communications Act allows anyone who stores information in a user's terminal device, or gains access to information stored there, to do so only if the user has given provable consent meeting the requirements of a special regulation. The duty to obtain consent does not apply to a law enforcement authority or another state authority.

The consent duty does not prevent technical storage of data or access to it whose only purpose is the transmission or facilitation of the transmission of a message through a network, or that is unconditionally necessary for the provider of an information society service to provide a service the user expressly requests. Section 124, paragraph 3 makes a breach of section 109, paragraph 8 punishable by a fine of EUR 200 up to 5 percent of turnover for the previous accounting period.

Section 124, paragraph 6 limits the fine under paragraphs 1 to 3 to EUR 300,000 where the person had no turnover for the previous accounting period or the turnover cannot be calculated.

What it requires

Interception and recording consent

Electronic Communications Act, Section 117, Paragraphs 1 and 2, Telecommunications Secrecy

Zákon 452/2021 Z. z., § 117 ods. 1-2Text of zákon č. 452/2021 Z. z. o elektronických komunikáciách

In force since . Binds public and private bodies.

What this law does

Section 117, paragraph 1 of the Electronic Communications Act makes the content of transmitted messages, data about the communicating party, traffic data and location data the object of telecommunications secrecy. Section 117, paragraph 2 requires everyone who comes into contact with the object of telecommunications secrecy, in the provision of networks and services, in the use of services, by chance or otherwise, to maintain it.

Section 124, paragraph 1 makes a breach of section 117, paragraph 2 punishable by a fine of EUR 200 up to 10 percent of turnover for the previous accounting period. Section 124, paragraph 6 limits the fine under paragraphs 1 to 3 to EUR 300,000 where the person had no turnover for the previous accounting period or the turnover cannot be calculated.

What it requires

Telephone contact

Electronic Communications Act, Section 116, Paragraphs 7 to 14, Telephone List of Objections to Direct Marketing Calls

Zákon 452/2021 Z. z., § 116 ods. 7-14Text of zákon č. 452/2021 Z. z. o elektronických komunikáciách

In force since . Binds public and private bodies.

What this law does

Section 116, paragraph 7 of the Electronic Communications Act requires the Authority to set up and run on its website a list of the telephone numbers that subscribers or users have entered to express disagreement with calls for direct marketing. Section 116, paragraph 8 prohibits any call for direct marketing if the subscriber or user has entered the telephone number in the list or has objected to such calls to the person for whom the marketing is done.

The prohibition in paragraph 8 does not apply if the subscriber or user gave the person for whom the marketing is done consent after the last update of the entry in the list. Section 116, paragraph 9 gives the subscriber or user the right at any time to enter a telephone number in the list or update the entry free of charge.

Section 116, paragraph 10 requires the person doing direct marketing to check the entry of a telephone number or group of numbers in the list on the Authority's website and to pay the fee the Authority sets for the check.

Section 116, paragraph 12 requires a person doing direct marketing by calls, automated calling and communication systems, telefax, SMS or MMS, or obtaining prior consent to such calls, to use for that purpose only numbers identified by the national destination code for it in the numbering plan. That duty does not apply to direct marketing calls made to the published contact details of a subscriber or user who is a sole trader or a legal person.

Section 116, paragraph 14 provides that paragraphs 8 and 12 do not apply to direct marketing of the person's own similar goods and services where the person obtained the contact details in connection with a sale or has a contractual relationship with the subscriber or user, or to a subscriber or user who requested such communication in advance in a provable way.

Section 116, paragraph 14 requires that the subscriber or user be given a possibility to refuse that use of contact details easily and free of charge at any time, when the details are collected and at every contact for direct marketing. Section 124, paragraph 3 makes a breach of section 116, paragraphs 3 to 6, 8, 12 and 14 to 16 punishable by a fine of EUR 200 up to 5 percent of turnover for the previous accounting period.

Section 134 provides that the Act takes effect on , except that paragraph 12 of section 116 takes effect on and paragraphs 7 to 10 of section 116 take effect on .

What it requires

Content moderation law1 instrument, 1 in force

Research summary (136 words)

Slovakia applies the Digital Services Act directly and holds its national layer in the Act on Media Services (zákon č. 264/2022 Z. z.), into which the Act of 2024 (zákon č. 203/2024 Z. z.) inserted the provisions on intermediary services.

The Act makes the Council for Media Services (Rada pre mediálne služby), called the regulator, the digital services coordinator, gives it powers of information requests, on-site inspection, interim measures, binding commitments and action plans, and sets fines of up to 6 percent of annual worldwide turnover and daily penalties of up to 5 percent of average daily turnover. Slovakia's rules for video-sharing platforms, including the protection of minors, are held in the age topic for the same Act. The Digital Services Act's own duties are held with the European Union's page and are not restated here.

Transparency and process

Zákon č. 264/2022 Z. z. o mediálnych službách (Act on Media Services), Digital Services Act Supervision, Information Duties and Fines

Zákon č. 264/2022 Z. z. o mediálnych službách, § 110 ods. 3 písm. w) až y), §§ 133a až 133g, § 145b a § 150 ods. 11 až 13Consolidated text of Act No. 264/2022 Coll., in force from , Slov-Lex (the Slovak Republic's legal information system)

In force since . Binds private bodies.

What this law does

Section 110(3)(w) and (x) make the regulator, the Council for Media Services (Rada pre mediálne služby), perform the tasks of the digital services coordinator and take part in the work of the European Board for Digital Services. Section 110(3)(y) has the regulator decide on the certification of out-of-court dispute settlement bodies, on the granting, suspension and withdrawal of trusted flagger status, and on vetted researcher status and access to data.

Section 133b(1) lets the regulator require a provider of an intermediary service, and any other person acting in the course of business who may reasonably be expected to have information on a suspected infringement, to provide that information free of charge within the time the regulator sets. Section 133b(3) obliges the provider, such a person, their employees and persons acting on their behalf to give the regulator cooperation and correct, complete and true information and explanations.

Section 133d lets the regulator impose a proportionate interim measure on a provider where recipients of the service face a risk of serious harm, for up to four weeks at a time, with an objection in ten days that has no suspensive effect. Section 133e(1) lets the regulator suspend the proceedings and declare a commitment offered by a provider to ensure compliance binding on it.

Section 145b(1)(a) obliges the regulator to fine a provider of an intermediary service up to 6 percent of annual worldwide turnover in the preceding accounting period for breaching the listed provisions of Regulation (EU) 2022/2065. Section 145b(1)(b) obliges the regulator to fine a provider of online intermediation services or an online search engine EUR 100 to EUR 50,000 for breaching the listed provisions of Regulation (EU) 2019/1150.

Section 145b(3) lets the regulator fine a provider of online intermediation services or an online search engine EUR 50 to EUR 10,000 where, in supervision, it fails to give information on a suspected infringement, gives incorrect, incomplete or misleading information, does not correct it when called upon, does not submit to supervision, or does not meet a commitment declared binding on it.

Section 145b(2) lets the regulator fine a provider of an intermediary service up to 1 percent of annual income or worldwide turnover where it fails to give information on a suspected infringement, gives incorrect, incomplete or misleading information, does not correct it when called upon, or does not submit to supervision.

Section 145b(4) lets the regulator impose a periodic penalty of up to 5 percent of average daily worldwide turnover or income to compel a provider to give correct and complete information, submit to supervision, comply with an interim measure, a commitment or an action plan, or comply with a corrective measure.

Section 150(11) requires the regulator, where its review shows that a complaint concerns an intermediary service under the jurisdiction of another Member State's digital services coordinator, to forward the complaint to that coordinator. Section 150(13) gives the complainant and the provider of the intermediary service the right to be heard and to receive adequate information on the state of the complaint.

The amending Act of , number 203/2024 of the Collection of Laws, inserted these provisions into the Act and took effect on the day of its promulgation, , except for points 4, 5, 19 and 22 of its Article I.

What it requires

Product and AI liability law2 instruments, 1 in force, 1 not yet in force

Research summary (195 words)

Act No. 294/1999 Z. z. on liability for damage caused by a defective product is Slovakia's product liability act in force today. EUR-Lex lists the Act among the national measures implementing Directive 85/374/EEC. Section 2(1) of that Act treats electricity and gas intended for consumption as a product. Act No. 242/2026 Z. z. on liability for damage caused by a defective product was promulgated on and takes effect on .

The annex to that Act lists Directive (EU) 2024/2853 as the act it transposes. Section 19 of the new Act repeals Act No. 294/1999 Z. z. Section 17(2) of the new Act keeps the earlier law in force for a product placed on the market or put into service up to . Section 2(a) of the new Act counts software as a product. Section 3(2) of the new Act leaves the right to damages under other law untouched.

Act No. 69/2018 Z. z. on cybersecurity, which sets the Slovak cybersecurity baseline, is recorded in the security topic. The draft Act on the organization of public administration in the field of artificial intelligence is recorded in the ai topic.

Product liability

Zákon o zodpovednosti za škodu spôsobenú vadným výrobkom (Act on Liability for Damage Caused by a Defective Product), No. 242/2026 Z. z., Transposition of Directive (EU) 2024/2853

Zákon č. 242/2026 Z. z. o zodpovednosti za škodu spôsobenú vadným výrobkomText of Act No. 242/2026 Z. z. in the version effective from , as published by Slov-Lex

Not yet in force. from , in 5 weeks It starts to bind on .

Binds private bodies.

What this law does

Section 20 provides that the Act takes effect on . The annex to the Act lists Directive (EU) 2024/2853 as the act it transposes. Section 17(1) applies the Act to damage caused by a defective product placed on the market or put into service from . Section 17(2) leaves the rules in force up to governing the liability for a product placed on the market or put into service up to that day.

Section 19 repeals Act No. 294/1999 Z. z. Section 2(a) counts electricity, a digital manufacturing file, a raw material and software as a product. Section 1(2)(a) excludes free and open-source software that was developed or supplied outside a business activity. Section 3(1) gives a natural person to whom a defective product caused damage the right to compensation. Section 4(1)(a) covers death or damage to health, including medically recognized damage to psychological health.

Section 4(1)(b) covers damage to or destruction of property, except the defective product itself, a product damaged by a defective component that the manufacturer integrated or connected or that is under its control, and property used exclusively for business or professional purposes. Section 4(1)(c) covers destruction or corruption of data, except data used for business or professional purposes.

Section 5(1) makes a product defective if it does not provide the safe use that can reasonably be expected or that special provisions lay down. Section 5(2)(c) weighs in judging a defect the effect of the product's ability to keep learning or to acquire new features after it is placed on the market or put into service. Section 5(2)(f) weighs in judging a defect the relevant product-safety requirements, including cybersecurity requirements that relate to the safety of the product.

Section 6(1) makes the manufacturer of a product liable for damage caused by a defective product. Section 6(2) makes the manufacturer of a defective component that is integrated into or connected with the product under the manufacturer's control liable together with the manufacturer of the product.

Section 6(3) makes the importer, the authorized representative and, where neither is established in a Member State, the provider of logistics services liable in addition where the manufacturer is not established in a Member State. Section 6(4) makes the distributor liable where no liable person established in a Member State can be identified and the distributor does not name one within one month of the injured person's request.

Section 6(5) extends section 6(4) to the provider of an online platform that allows a consumer to conclude a distance contract with a trader, where the provider is not an economic operator and the conditions of a special provision are met. Section 6(6) makes a person who makes a product available on the market or puts it into service after a substantial modification outside the manufacturer's control liable.

Section 7(1)(e) releases a liable person on proof that the objective state of scientific and technical knowledge did not allow the defect to be discovered. Section 7(4) denies the release for a defect that arose after the product was placed on the market where a related service, software including its updates or upgrades, a missing software update or upgrade needed to maintain safety, or a substantial modification under the manufacturer's control caused the defect.

Section 8 bars excluding or limiting the liability towards the injured person and makes a unilateral declaration or an agreement that does so void. Section 9 makes two or more liable persons liable jointly and severally. Section 12 time-bars the claim three years after the injured person learned or could have learned of the damage, the defect and the identity of the liable person.

Section 13(1) extinguishes the right to compensation if the injured person does not claim it within ten years of the day the defective product was placed on the market or put into service. Section 13(2) extends that period to 25 years where a delayed manifestation of injury to health prevented the injured person from claiming within ten years.

Section 14(1) has the court order the defendant, on the claimant's application, to disclose relevant evidence in its control once the claimant presents facts and evidence sufficient to support the plausibility of the claim. Section 15(2)(a) presumes the product defective where the defendant does not disclose the relevant evidence it holds.

Section 15(2)(b) presumes the product defective where the claimant shows that it does not meet product-safety requirements under special provisions that are meant to protect against the damage suffered. Section 15(4) has the court presume the defect, the causal link or both where the claimant has excessive difficulty in proving them because of technical or scientific complexity and shows that they are probable.

What it requires

Zákon o zodpovednosti za škodu spôsobenú vadným výrobkom (Act on Liability for Damage Caused by a Defective Product), No. 294/1999 Z. z. (Directive 85/374/EEC)

Zákon č. 294/1999 Z. z. o zodpovednosti za škodu spôsobenú vadným výrobkomText of Act No. 294/1999 Z. z. in the version effective from to

In force since . Binds public and private bodies.

What this law does

Section 1(1) makes the producer liable for damage a defective product causes to the health or life of the injured person, or to a thing other than the defective product that is ordinarily intended for personal use or consumption and served the injured person mainly for that purpose. Section 1(1) leaves the injured person to prove the defect, the damage and the causal link between the defective product and the damage.

Section 1(2) covers damage to a thing other than the defective product only where the damage exceeds 20,000 Slovak korunas. Section 2(1) defines a product as any movable thing that was made, extracted or otherwise obtained and is intended to be placed into circulation. Section 2(1) also treats electricity and gas intended for consumption as a product.

Section 3(1) makes a product defective if it does not guarantee the safety of its use that can reasonably be expected, having regard in particular to its presentation and the information given about it, its expected use and purpose, and the time it was placed into circulation. Section 3(2) provides that a product is not defective only because a more perfect product was placed into circulation.

Section 4(1) makes the producer the person who made, extracted or otherwise obtained the product, or who presents itself as the producer by its name, trade mark or another distinguishing mark. Section 4(2) also treats as a producer whoever imports a product from abroad for sale, hire or another form of use in the course of its business.

Section 4(3) treats every supplier as the producer where the producer cannot be identified, unless the supplier names the producer or its own supplier to the injured person within one month of the claim. Section 4(3) applies the same rule to an imported product whose importer cannot be identified, even where the producer is known. Section 5(1)(a) releases the producer from liability on proof that it did not place the product into circulation.

Section 5(1)(b) releases the producer on proof that, according to the circumstances that preceded the damage, the product can be taken to have been free of the defect when it was placed into circulation or that the defect arose later. Section 5(1)(c) releases the producer on proof that it did not make the product for sale or other use for business purposes and did not distribute it in the course of its business.

Section 5(1)(d) releases the producer on proof that the defect results from compliance with a duty arising from a generally binding legal provision. Section 5(1)(e) releases the producer on proof that the state of scientific and technical knowledge when the product was placed into circulation did not allow the defect to be discovered.

Section 5(2) releases the producer of a component on proof that the overall design of the product, the requirements of the producer of the overall product or the instructions for use of the overall product caused the defect. Section 6(2) limits the producer's liability to 3,500 million Slovak korunas where the same defect in identical products injured the health or life of several persons.

Section 6(3) reduces the compensation where the producer proves that the fault of the injured person also contributed to the damage. Section 6(4) makes two or more liable producers liable jointly and severally. Section 7(1) keeps the producer liable for the whole damage where an act or omission of a third person also contributed to it. Section 8 bars excluding or limiting the producer's liability in advance by contract.

Section 9(1) time-bars the claim three years after the day the injured person learned or could have learned of the damage and of the identity of the producer. Section 9(2) time-bars the claim at the latest ten years after the day the producer placed the defective product into circulation. Section 10 disapplies the Act to damage caused by a nuclear event governed by a special provision. Section 12 provides that the Act takes effect on . The Act was promulgated on .

Section 19 of Act No. 242/2026 Z. z. repeals the Act. Section 17(2) of Act No. 242/2026 Z. z. keeps the Act in force for a product placed on the market or put into service up to .

What it requires

Age gating law1 instrument, 1 in force

Research summary (103 words)

Slovakia transposed the EU Audiovisual Media Services Directive's video-sharing platform protections through sections 48 to 50 of the zakon o medialnych sluzbach (Media Services Act), Act No. 264/2022 Coll., which took effect .

A video-sharing platform provider must adopt appropriate measures to protect minors from content that may impair their physical, psychological, or moral development, and the measures a regulator may find suitable include a user-controlled parental-control system and an age-verification system tied to that content, alongside complaint-handling, content-flagging, and media-literacy measures.

Slovakia has no dedicated adult-content age-verification statute, social-media minor-access statute, or app-store age-verification statute distinct from this platform-protection regime.

Age-appropriate design code

Media Services Act, Video-Sharing Platform Public-Protection Measures

Act 264/2022 Coll. (zakon o medialnych sluzbach), ss. 48-50Official consolidated text of the zakon o medialnych sluzbach, Slov-Lex (Ministry of Justice of the Slovak Republic)

In force since . Binds public and private bodies.

What this law does

Section 48(1)(a) requires a video-sharing platform provider to adopt appropriate measures to protect minors from programmes, user-created videos, and audiovisual commercial communications that may impair their physical, psychological, or moral development.

Section 49 lists measures the provider may take depending on the case, including embedding the protective rules in the platform's terms of use, a reporting and flagging mechanism for content covered by section 48, a complaints procedure, and media-literacy tools. Among those listed measures is a parental-control system controlled by the user. Section 49 also lists an age-verification system for users in relation to content that may impair minors' development.

Section 50 lets the regulator request data from the provider to assess whether its measures are suitable, and to request further information where the data supplied does not let the regulator make that assessment. Personal data collected under the parental-control or age-verification measures may not be processed for commercial purposes.

What it requires

Reuse law2 instruments, 2 in force

Research summary (142 words)

Slovakia transposed the EU Digital Single Market Copyright Directive's press-publisher neighbouring right through sections 129a to 129h of the Autorsky zakon (Copyright Act), Act No. 185/2015 Coll., inserted by Act 71/2022 Coll. and running for two years from a periodical's publication.

The right exempts hyperlinking and the use of a headline, individual words, or a very short extract incapable of substituting for the periodical, and does not apply to a periodical first published before .

The same amendment inserted a general text-and-data-mining exception at section 51c, defeated by an express rightsholder reservation, alongside an unconditional exception for libraries, archives, museums, schools, and statutory depositaries at section 51b. Slovakia 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 has been located.

Press publishers' right

Autorský zákon, Press Publisher Right

Act 185/2015 Coll., ss. 129a-129h (as amended by Act 71/2022 Coll.)Official consolidated text of the Autorsky zakon, Slov-Lex (Ministry of Justice of the Slovak Republic)

In force since . Binds private bodies.

What this law does

Section 129c(1) to (2), inserted by Act 71/2022 Coll. transposing Article 15 of the EU Digital Single Market Copyright Directive, gives a periodical's publisher the exclusive right to use the periodical and to authorise its use, so an information-society service provider may reproduce or make the periodical available online only with the publisher's consent unless the Act provides otherwise.

Section 129c(4) exempts an individual user's private, non-commercial use, hyperlinking, and the use of a headline, individual words, or a very short extract incapable of substituting for the whole periodical. Section 129d limits the right's duration to two years from the periodical's publication, ending on the last day of the calendar year in which that term lapses.

A transitional provision excludes any periodical first published before from section 129c. Section 129h requires the publisher to pay rightsholders whose works are included in the periodical an appropriate share of the remuneration it receives from licensing an information-society service provider, within six months of the right's expiry.

What it requires

Text and data mining (TDM) opt-out

Autorský zákon, TDM Exception (Aggregation)

Act 185/2015 Coll., s. 51c (as amended by Act 71/2022 Coll.), aggregationOfficial consolidated text of the Autorsky zakon, Slov-Lex (Ministry of Justice of the Slovak Republic)

In force since . Binds public and private bodies.

What this law does

Section 51c, inserted by Act 71/2022 Coll. transposing Article 4 of the EU Digital Single Market Copyright Directive, does not require an author's consent to reproduce a work for text-and-data-mining, unless the rightsholder has expressly reserved that use. A reproduction made under the exception may be retained only for as long as the mining requires it.

Section 51b gives a library, archive, museum, school, or statutory depositary a separate, unconditional exception for text-and-data-mining carried out for research.

What it requires

Case law

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

Reporting clocks that run here21 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 Slovakia 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
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 Slovakia

24 hours72 hours1 month

Zákon o kybernetickej bezpečnosti (Cybersecurity Act), Incident and Vulnerability Notification

Zákon č. 69/2018 Z. z. o kybernetickej bezpečnosti a o zmene a doplní niektorých zákonov v znení zákona č. 366/2024 Z. z., § 24 a § 5 ods. 5security law, in force since

The sentences the clocks are read from

Report without undue delay, and no later than 24 hours after becoming aware of it, an early warning of a significant cyber security incident, stating in particular whether it may have been caused by unlawful conduct or may have a cross-border effect.

No later than 72 hours after becoming aware of it, report a notification updating and completing the early warning, in particular an initial assessment of the incident's severity and impact.

If you are also a trust service provider, report a significant cyber security incident, with its effect on your trust services, without undue delay and no later than 24 hours after discovering it, in place of the later notification (Section 24(3)(b)).

No later than one month after the 72-hour notification, report a final report describing the incident, its severity and impact, the threat type or probable root cause, the mitigating measures taken and under way, and any cross-border impact.

Where an incident with cross-border impact is still ongoing when the final report is due, report an updated final report within 30 days of restoring normal network and system operation; where any significant incident is still ongoing when you submit the final report, report further information and an updated final report within 30 days of its resolution.

72 hours

GDPR Articles 33-34, Breach Notification

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

The sentences the clocks are read from

Notify the Slovak Office for Personal Data Protection without undue delay and, where feasible, within 72 hours of becoming aware of a personal-data breach affecting a person in Slovakia, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons, and notify affected individuals without undue delay where the breach is likely to result in a high risk to them.

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)).

The law of the European Union, which applies in Slovakia

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.