Law / Uruguay

Uruguay

19 of 22 named instruments researched to a stage, across four of the ten areas of law we track: 19 in force. As of .

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

in forcenot yet in forceblocked by a courtproposedno longer in force

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

Privacy law10 instruments, 10 in force

Research summary (209 words)

Uruguay's Ley N° 18.331 of , Protección de Datos Personales y Acción de Habeas Data, is a comprehensive, General Data Protection Regulation (GDPR)-comparable regime enforced by the Unidad Reguladora y de Control de Datos Personales (URCDP) and recognized by the European Commission as offering an adequate level of protection.

Ley N° 19.670 of 2018 added extraterritorial reach for a controller established abroad, a security-breach notification duty, and a mandatory data-protection-officer designation for large-scale or state-linked processors, both now regulated in detail by Decreto N° 64/020 of 2020.

Uruguay's definition of sensitive personal data (art. 4, literal E) reaches racial or ethnic origin, political opinion, religious or moral conviction, union affiliation, health, and sexual life, and does not name biometric or genetic data as such; Ley N° 19.924 of 2020 instead added a dedicated biometric-data definition (art. 4, literal Ñ) and a standalone provision, art. 18-BIS, requiring a data-protection impact assessment before any biometric processing, so a service that captures a faceprint or voiceprint answers to that dedicated duty rather than to the sensitive-category rule.

The Act's habeas data action, at arts. 37 to 45, gives any person a judicial remedy to learn what personal data about them a public or private database holds and to demand its correction, inclusion, or deletion.

Biometric privacy

Ley N° 18.331, biometric data

Ley N° 18.331, arts. 4 (literal Ñ) y 18-BIS, según Ley N° 19.924, de 18 de diciembre de 2020 (datos biométricos)Ley N 18.331 de 11 de agosto de 2008, texto consolidado, Direccion Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 4, literal Ñ, added by Ley N° 19.924 art. 86, defines biometric data as personal data obtained from a specific technical process relating to a natural person's physical, physiological, or behavioral characteristics that allow or confirm their unique identification, such as fingerprint data, image recognition, or voice recognition.

Article 18-BIS, added by Ley N° 19.924 art. 87, requires that any processing of biometric data first pass through a data protection impact assessment and fit within one of the lawful bases article 9 allows, a dedicated duty distinct from the sensitive-data list at article 4 literal E, which does not name biometric data.

What it requires

Breach notification

Decreto N° 64/020, personal data breach communication

Decreto N° 64/020, de 17 de febrero de 2020, art. 4 (comunicación de vulneraciones de seguridad)Decreto N° 64/020, de 17 de febrero de 2020, texto actualizado, Dirección Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 4 of Decreto N° 64/020 requires the controller, once it establishes that a security breach affecting data protection has occurred, to communicate it to the Unidad Reguladora y de Control de Datos Personales within a maximum of 72 hours of becoming aware of the breach. The communication must carry relevant information, such as the certain or estimated date of the breach, its nature, the personal data affected and the possible impacts.

A processor that learns of a breach must tell the controller immediately. The controller must also tell the data subjects who suffered a significant effect on their rights, in clear and simple language. Once the breach is resolved, the controller must prepare a detailed report of the breach and the measures adopted and send it to the Unidad Reguladora y de Control de Datos Personales. The decree was promulgated on and published on .

What it requires

Ley N° 19.670, personal data breach notification

Ley N° 19.670, de 15 de octubre de 2018, art. 38, reglamentado por Decreto N° 64/020, de 2020 (notificación de vulneración de seguridad)Ley N° 19.670, de 15 de octubre de 2018, texto consolidado, Dirección Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 38, now regulated by Decreto N° 64/020 of 2020, requires the controller or processor of a database, on becoming aware of a security breach, to inform both the affected data subjects and the Unidad Reguladora y de Control de Datos Personales immediately and in detail, together with the measures adopted, coordinating the response with the Centro Nacional de Respuesta a Incidentes de Seguridad Informática del Uruguay (CERTuy).

The provision states no fixed numeric deadline, only immediacy from the moment the controller or processor becomes aware of the breach, and leaves the detailed content of that notification to the implementing regulation, Decreto N° 64/020. Article 4 of Decreto N° 64/020 sets a maximum of 72 hours from the controller's awareness of a security breach for communicating it to the Unidad Reguladora y de Control de Datos Personales.

What it requires

Comprehensive regime

Ley N° 18.331, Personal Data Protection and Habeas Data Law

Ley N° 18.331, de 11 de agosto de 2008, arts. 9-11, 17, 20, 22, 24 y 29Ley N 18.331 de 11 de agosto de 2008, texto consolidado, Direccion Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 9 requires free, prior, express, and informed consent before processing personal data, documented in writing, subject to narrow exceptions for data drawn from public sources, gathered for a state function, or arising from a contractual, scientific, or professional relationship.

Article 10 requires the responsible party to adopt the security measures needed to prevent unauthorized alteration, loss, consultation, or processing of personal data, and article 11 binds anyone who legitimately accesses another party's database to reserve and professional secrecy, backed by the existing offense at article 302 of the Penal Code.

Article 17 lets personal data be communicated to a third party only for a purpose tied to the sender's and recipient's legitimate interest and only with the data subject's prior consent. Articles 24 and 29 require every public or private database to be registered with the Unidad Reguladora y de Control de Datos Personales before it operates, declaring the categories of data it holds.

Article 22 limits a negative commercial-debt record concerning a natural person to five years from its entry, renewable once, and article 20 requires an operator of a public communications network or electronic communications service to secure that network and warn subscribers of a particular security risk. Ley N° 18.331 states no day of its own entry into force, and article 1 of the Civil Code deems a promulgation known ten days after it takes place in the capital. The Law was promulgated on and published in the Diario Oficial on .

What it requires

Ley N° 19.670, accountability, extraterritorial scope and data-protection officer

Ley N° 19.670, de 15 de octubre de 2018, arts. 37, 39 y 40 (Ley N° 18.331, art. 12)Ley N° 19.670 de 15 de octubre de 2018

In force since . Binds public and private bodies.

What this law does

Article 12 of Ley N° 18.331, as rewritten by Ley N° 19.670 art. 39, imposes a proactive-accountability duty of privacy by design, privacy by default, and a data-protection impact assessment. Ley N° 19.670 art. 37 extends Ley N° 18.331 to a controller or processor established outside Uruguay when its processing relates to offering goods or services to people in Uruguay or analyzing their behavior, when international law or a contract so provides, or when it uses means located in the country.

Ley N° 19.670 art. 40 requires a public entity, a wholly or partly state-owned entity, or a private entity that processes sensitive data as a main line of business or processes large volumes of data, to designate a data-protection officer with technical autonomy. Article 2 of Ley N° 19.670 makes the law govern from , except for provisions that expressly set another date of effect.

What it requires

Cross border transfer

Ley N° 18.331, cross border transfer of personal data

Ley N° 18.331, art. 23 (transferencia internacional de datos personales)Ley N 18.331 de 11 de agosto de 2008, texto consolidado, Direccion Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 23 prohibits transferring personal data of any kind to a country or international body that does not provide an adequate level of protection under international or regional legal standards.

That prohibition does not reach judicial cooperation, medical-data exchange for public health reasons, banking or stock-exchange transactions, a treaty Uruguay is party to, or intelligence cooperation against organized crime, terrorism, or drug trafficking, and it also yields where the data subject unambiguously consents, the transfer is contractually necessary, an important public interest or a legal proceeding requires it, the data subject's vital interest is at stake, or the transfer comes from a register meant to inform the public.

Absent an adequate-protection finding and outside those exceptions, the Unidad Reguladora y de Control de Datos Personales may still authorize a transfer, or a series of transfers, to a country that does not guarantee an adequate level of protection where the controller offers sufficient contractual safeguards for privacy and fundamental rights.

Ley N° 18.331 states no day of its own entry into force, and article 1 of the Civil Code deems a promulgation known ten days after it takes place in the capital. The Law was promulgated on and published in the Diario Oficial on .

What it requires

Data subject rights

Ley N° 18.331, automated decisions

Ley N° 18.331, art. 16, según Ley N° 18.719, de 2010 (automated individual decisions)Ley N° 18.331 de 11 de agosto de 2008, texto consolidado, Dirección Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 16, in the wording given by Ley N° 18.719 of 2010, gives a person the right not to be subjected to a decision with legal effects that significantly affects them, based on automated processing intended to assess aspects of their personality such as work performance, creditworthiness, reliability or conduct.

It lets the affected person challenge an administrative act or a private decision that assesses their conduct where personal-data processing offering a definition of their characteristics or personality is its sole basis, and in that case gives them the right to obtain from the database controller both the assessment criteria and the program used in the processing behind the decision.

What it requires

Ley N° 18.331, rights of data subjects

Ley N° 18.331, arts. 13-15 y 21, según Ley N° 20.075, de 2022, y Ley N° 18.719, de 2010 (derechos de los titulares de los datos)Ley N 18.331 de 11 de agosto de 2008, texto consolidado, Direccion Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force. Binds public and private bodies.

What this law does

Article 13, as rewritten by Ley N° 20.075 art. 62, requires telling a data subject, before or when their data is collected, the purpose of the processing and who may receive it, the existence and identity of the database's controller, whether answering is mandatory, particularly for sensitive data, the consequences of refusing or of inaccuracy, the rights available under articles 14 to 16, whether the data will be transferred internationally, and, for an automated-decision process, the valuation criteria, the process applied, and the technology or program used.

Article 14 gives a data subject free access, at most every six months, to all information about them held in a public or private database, supplied within five business days in clear language, covering the whole record without revealing a third party's data.

Article 15 gives a right to rectification, updating, inclusion, or deletion of erroneous, false, or missing personal data, to be carried out within five business days of the request, or the controller must give the reasons it considers the request does not apply, with any recipient of the data notified of the change within five business days.

Article 21 lets a data subject exercise the right of access free of charge in a marketing, canvassing, or profiling database, and request the withdrawal or blocking of their data from it at any time. The sections this entry groups came into force on different days.

What it requires

Enforcement supervision

Ley N° 18.331, enforcement, sanctions and habeas data

Ley N° 18.331, arts. 31-36 y 37-45 (órgano de control, potestades sancionatorias y acción de habeas data)Ley N 18.331 de 11 de agosto de 2008, texto consolidado, Direccion Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force. Binds public and private bodies.

What this law does

Article 31 creates the Unidad Reguladora y de Control de Datos Personales as a technically autonomous body within AGESIC, and article 34, as rewritten in 2010 and 2022, gives it the power to inspect a controller's or processor's books, documents, and files, demand their appearance to provide information, and, in serious cases, seize materials for up to six business days, with judicial backing for a search of private premises.

Article 35 arms the authority with graduated administrative sanctions for a violation of the law: observation, warning, a fine of up to UI 500,000 (Unidades Indexadas, an inflation-linked accounting unit), a five-day suspension, or closure of the database, and lets it seek judicial closure of a database found to infringe the law.

The Act creates no separate criminal offense of its own; article 11 only cross-references the pre-existing professional-secrecy offense at article 302 of the Penal Code.

Article 37 gives any person the right to bring an effective habeas data judicial action against a public or private database's controller to learn what personal data about them it holds, its purpose and use, and to demand its rectification, inclusion, suppression, or another appropriate remedy where the data is erroneous, false, prohibited from processing, discriminatory, or outdated, with articles 38 to 45 setting the court, standing, and summary procedure for that action. The sections this entry groups came into force on different days.

What it requires

Sensitive categories

Ley N° 18.331, sensitive personal data and health data

Ley N° 18.331, de 2008, arts. 4 (literal E), 18 y 19 (datos sensibles y datos relativos a la salud)Ley N 18.331 de 11 de agosto de 2008, texto consolidado, Direccion Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 18 bars requiring anyone to provide sensitive data (racial or ethnic origin, political opinion, religious or moral conviction, union affiliation, health, or sexual life, as article 4 literal E defines it), and permits its processing only with the data subject's express written consent.

Absent that consent, article 18 allows collection and processing only where an interest-general law authorizes it or the requesting body has a legal mandate, or for statistical or scientific purposes once the data is disassociated from its subject.

Article 18 also bars forming a database whose content directly or indirectly reveals sensitive data, except for a political party, union, church, or other nonprofit body that processes only its own members' data for its own political, religious, or similarly aligned purpose, and never without the member's consent to any further communication of that data.

Article 19 lets a public or private health establishment or a health professional collect and process a patient's physical or mental health data only under the rules of professional secrecy and the specific health-sector regulations, alongside this law. Ley N° 18.331 states no day of its own entry into force, and article 1 of the Civil Code deems a promulgation known ten days after it takes place in the capital. The Law was promulgated on and published in the Diario Oficial on .

What it requires

Scraping law3 instruments, 3 in force

Research summary (263 words)

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

Código Penal art. 297 bis, inserted by Ley N° 20.327 of 2024, criminalises accessing, intercepting, publishing, selling, or transferring another's information held in digital form only when done without authorization and without just cause by computer or telematic means, so a plain reading leaves reading a public, unauthenticated page without defeating any access control outside the offence, and no reported Uruguayan case has tested the point.

No Uruguayan court has ruled on the enforceability of a browsewrap or clickwrap terms-of-service against a scraper, so that dimension is unsettled rather than answered. Ley N° 9.739 of 1937, as amended, protects a compilation of data as a copyright work only for the originality of its selection or arrangement, expressly stating that the protection does not reach the data or materials themselves, and confers no sui generis database right distinct from that compilation copyright.

The same Law has no text-and-data-mining exception; its narrow free-use exceptions permit quoting a work for comment, criticism, or controversy, and reproducing news, reports, or journalistic information of general interest only in their exact, unaltered form with the source credited, which does not obviously reach an aggregator's or a model trainer's use of scraped text.

Uruguay's comprehensive privacy statute, Ley N° 18.331, reaches personal data an app scrapes from a public Uruguayan page, recorded under the privacy topic rather than duplicated here. No Uruguayan statute or reported case establishes a scraping-specific unfair-competition, misappropriation, or trespass doctrine, and none assigns legal weight to a robots.txt directive or imposes an AI-training-specific rule.

Computer misuse

Código Penal arts. 297 bis, 297 ter, 297 quater, 358 quater, and 358 quinquies, computer-offence provisions inserted by Ley N° 20.327

Ley N° 20.327 de 23 de agosto de 2024 (Diario Oficial de 25 de septiembre de 2024), arts. 6 y 8, Código Penal arts. 297 bis, 297 ter, 297 quater, 358 quinquiesOfficial text of Ley N° 20.327 inserting these articles into the Código Penal

In force. Binds public and private bodies.

What this law does

Article 297 bis (acceso ilícito a datos informáticos) punishes with six to twenty-four months' imprisonment anyone who, by computer or telematic means, without authorization and without just cause, accesses, interferes with, discloses, sells, or transfers another's information held on a digital medium; because the offence's trigger is acting without authorization, reading a public, unauthenticated page without defeating any access control falls outside a plain reading of the provision.

Article 297 ter punishes unauthorized interception of non-public data transmissions with the same six-to-twenty-four-month range.

Article 297 quater (vulneración de datos) punishes, with the same six-to-twenty-four-month range, accessing, appropriating, using, or modifying a third party's confidential data held on a digital or other medium without the holder's authorization, and separately punishes disclosing, revealing, or transferring such data to a third party with one to four years' imprisonment, aggravated where the data are personal data protected under Ley N° 18.331.

Article 358 quater (daño informático) punishes destroying, altering, or rendering unusable data or computer systems without authorization and with intent to cause harm with six to twenty-four months' imprisonment. Article 358 quinquies (abuso de los dispositivos) punishes producing, acquiring, importing, marketing, or supplying to a third party a program, system, or access credential unequivocally intended for committing an offence, with the same six-to-twenty-four-month range.

Ley N° 20.327 states no day of its own entry into force; absent a stated day, article 1 of the Civil Code brings an undated law into force ten days after its promulgation is verified in the capital, a computed day rather than one a source states.

What it requires

Copyright and text and data mining (TDM)

Ley N° 9.739 arts. 44-45, illicit-reproduction rule and free-use exceptions for quotation and news

Ley N° 9.739, de 17 de diciembre de 1937, arts. 44 y 45Consolidated, currently updated text of Ley N° 9.739, Centro de Información Oficial (IMPO), Uruguay's official legislative database

In force. Binds public and private bodies.

What this law does

Article 44 treats reproducing, distributing, communicating, or making a work available to the public without the author's consent as illicit reproduction, so copying a copyrighted text found on the open web without permission or an applicable exception infringes unless article 45 covers it. Article 45 numeral 4 excepts a transcription made for the purpose of comment, criticism, or controversy, a general quotation right rather than a text-and-data-mining exception.

Article 45 numeral 3 excepts news, reports, journalistic information, or recordings of general interest, but only where the exact version is preserved and the source is stated, a condition suited to a verbatim press clipping rather than to extracting short snippets or training a model on the underlying text.

Uruguay has no text-and-data-mining exception and no machine-readable opt-out mechanism of that kind; a service that reproduces or trains on scraped copyrighted text rests only on the numeral 4 quotation ground if its use can be characterised as comment, criticism, or controversy. The sections this entry groups came into force on different days.

What it requires

Database right

Ley N° 9.739 art. 5, compilation and database copyright protection

Ley N° 9.739, de 17 de diciembre de 1937, art. 5Consolidated, currently updated text of Ley N° 9.739, Centro de Información Oficial (IMPO), Uruguay's official legislative database

In force. Binds public and private bodies.

What this law does

Article 5 protects a compilation of data or other materials, in any form, as a copyright work when the selection or arrangement of its contents constitutes an intellectual creation, and states expressly that this protection does not extend to the underlying data or materials themselves and is without prejudice to any copyright that subsists in them separately.

Uruguay confers no sui generis database right distinct from this originality-based compilation copyright, so a database whose selection or arrangement is not itself an intellectual creation, such as a routine or exhaustive listing, receives no protection under this article, and copying the underlying facts or data out of a protected compilation does not infringe it. Article 5 in its present wording is the text that Ley N° 17.616 set out anew in its article 3.

Ley N° 17.616 states no day of its own entry into force; absent a stated day, article 1 of the Civil Code brings an undated law into force ten days after its promulgation is verified in the capital, a computed day rather than one a source states.

What it requires

Cybersecurity law5 instruments, 5 in force

Research summary (519 words)

Uruguay has no product-security or market-placement statute reaching a software or connected-device manufacturer and no general reasonable-security or information-security-programme statute covering a business with no sector gate; Ley 20.212 articles 78 to 80 and Decreto 66/025 bind public entities and private entities linked to critical services or sectors, and are filed as rows of their own.

The country's only cyber-resilience apparatus, the Centro Nacional de Respuesta a Incidentes de Seguridad Informatica (National Center for Information Security Incident Response, CERTuy), was created under Article 73 of Ley N. 18.362 of and organized by Decreto 451/009 of within the Agencia de Gobierno Electronico y Sociedad de la Informacion y del Conocimiento (AGESIC).

That decree's own Article 2 states its scope of application is limited "al Estado" (to the State), and its Article 8 duties to report an incident immediately and to adopt efficient security measures for critical information assets are addressed to "los organismos" (State bodies), never to a private company.

The Banco Central del Uruguay's Superintendencia de Servicios Financieros requires financial intermediation institutions to report cybersecurity incidents, a communication filed as a row of its own.

Ley N. 20.327 of , read in full, inserts only criminal offenses into the Codigo Penal (telematic harassment at article 288 bis, computer fraud at article 347 bis, and the unauthorized-access offenses at articles 297 bis, 297 ter, 297 quater, 358 quater and 358 quinquies inserted by the same law); it creates no security duty on an operator or a manufacturer and stays with the jurisdiction's scraping-topic computer-misuse row rather than this one.

Ley N. 18.331's Article 10, its "Principio de seguridad de los datos" (principle of data security), requires a database's controller or user to adopt the measures necessary to guarantee the security and confidentiality of personal data; that is the comprehensive privacy regime's own security-of-processing clause and is described in the jurisdiction's privacy-topic document rather than restated here.

Articles 78 and 79 of Ley 20.212 of require public entities and private entities linked to services or sectors critical to the country to adopt effective security measures to protect their critical information assets. Article 80 of Ley 20.212 requires those entities to communicate a cybersecurity incident to the Agencia para el Desarrollo del Gobierno de Gestión Electrónica y la Sociedad de la Información y del Conocimiento within twenty-four hours of becoming aware of it.

Article 14 of Decreto 66/025 of requires the entities it binds to adopt the Marco de Ciberseguridad developed by the Agencia and to meet the minimum maturity level assigned to their profile. Article 10(g) of Decreto 66/025 requires the entities it binds to communicate the occurrence of a cybersecurity incident to the Centro Nacional de Respuesta a Incidentes de Seguridad Informática within 24 hours of becoming aware of it.

Article 22 of Decreto 66/025 repeals Decrees 451/009 and 452/009 of . Resolución RR-SSF-2021-353 of the Superintendencia de Servicios Financieros requires financial intermediation institutions and larger credit-administering companies to present information on every event affecting technology, systems or information security that meets its thresholds.

Sector security regimes

Decreto 66/025, Cybersecurity Framework Duties of Public and Critical-Sector Entities

Decreto N° 66/025, arts. 10, 11, 14 a 18 y 21Text of Decreto N° 66/025 as published by the Dirección Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 2 of the decree applies it to all public entities and to private entities linked to services or sectors critical to the country. Article 3(j) of the decree defines the critical sectors as health, public order, emergency services, energy, telecommunications, transport, drinking water supply, ecology and environment, agro-industry, industry, public services, banking and financial services and defense, and other sectors the Executive Power determines.

Article 10(a) of the decree requires those entities to adopt effective security measures to protect their critical information assets, following the guidelines of AGESIC. Article 14 of the decree requires the entities it binds to adopt the Marco de Ciberseguridad developed by AGESIC and to meet the minimum maturity level assigned to their profile. Article 16 of the decree requires those entities to carry out audits under the Marco de Ciberseguridad at the periodicity AGESIC defines.

Article 21 of the decree lets AGESIC warn directly an entity that fails to meet the decree. Article 22 of the decree repeals Decrees 451/009 and 452/009 of .

What it requires

Ley 20.212, Cybersecurity Obligations of Public and Critical-Sector Entities

Ley N° 20.212, arts. 78 y 79Text of Ley N° 20.212

In force since . Binds public and private bodies.

What this law does

Article 78(A) of the Act requires public entities and private entities linked to services or sectors critical to the country to adopt effective security measures to protect their critical information assets, following the guidelines AGESIC indicates.

Article 78(B) and (C) of the Act require those entities to designate an information security officer and communicate it to AGESIC, and to plan measures to mitigate and improve existing controls and adopt the prevention measures the regulations determine. Article 78(E) and (F) of the Act require those entities to incorporate the AGESIC cybersecurity framework according to their maturity level and to comply with other measures the Executive Power determines.

Article 79 of the Act empowers AGESIC, for an entity that breaches article 78, to require adjustment of its procedures, to require specific risk-prevention measures, to require supplementary information on incidents, and to issue a warning considering the gravity or repetition of the breach. Article 2 of the Act provides that it governs from except for provisions that expressly set another date.

What it requires

Vulnerability and incident reporting

Decreto 66/025, Cybersecurity Incident Reporting to CERTuy

Decreto N° 66/025, arts. 10(g) y 12Text of Decreto N° 66/025 as published by the Dirección Nacional de Impresiones y Publicaciones Oficiales (IMPO)

In force since . Binds public and private bodies.

What this law does

Article 10(g) of the decree requires the entities it binds to communicate the occurrence of a cybersecurity incident to CERTuy within 24 hours of becoming aware of it, in the form and conditions CERTuy sets. Article 12(a) and (b) of the decree require those entities to report a potential cybersecurity incident fully and immediately under CERTuy criteria and to make available the information CERTuy or the sector computer security incident response team (CSIRT) requires, within the times requested.

Article 12(c) of the decree requires those entities to repair the consequences of incidents that affect critical information assets in accordance with the recommendations informed. Article 21 of the decree lets AGESIC warn directly an entity that fails to meet the decree. The decree was promulgated on and published on .

What it requires

Ley 20.212, Cybersecurity Incident Reporting by Public and Critical-Sector Entities

Ley N° 20.212, arts. 78(D) y 80Text of Ley N° 20.212

In force since . Binds public and private bodies.

What this law does

Article 78(D) of the Act requires public entities and private entities linked to services or sectors critical to the country to report the existence of a potential cybersecurity incident fully and immediately, under the criteria CERTuy sets, and to make available the information CERTuy requires.

Article 80 of the Act requires those entities to communicate the occurrence of a cybersecurity incident to AGESIC within twenty-four hours of becoming aware of it and to complete the information needed for the registry as soon as possible. Article 80 of the Act creates the National Cybersecurity Incident Registry, administered by AGESIC.

Article 79 of the Act empowers AGESIC, for an entity that breaches article 78, to require supplementary information on incidents and to issue a warning considering the gravity or repetition of the breach. Article 2 of the Act provides that it governs from except for provisions that expressly set another date.

What it requires

Superintendencia de Servicios Financieros Communication on Technology, Systems and Information Security Events

Resolución RR-SSF-2021-353 de la Superintendencia de Servicios Financieros Comunicación de eventos vinculados a Tecnología, Sistemas y Seguridad de la InformaciónText of Resolución RR-SSF-2021-353 as published by the Banco Central del Uruguay

In force since . Binds private bodies.

What this law does

Resolución RR-SSF-2021-353 tells financial intermediation institutions and larger credit-administering companies that they must present information on every event that could affect services or clients and that, by its impact, affects operational or reputational risk.

The resolution requires those entities to report as a minimum events that meet its thresholds, including an interruption of a customer channel of 30 minutes or more and exposure of sensitive information and personal data of 5% or more of clients. The resolution requires an emerging event to be communicated as soon as possible after it becomes known and a scheduled event at least 24 hours before it starts. The resolution applies to events detected on or after .

The resolution rests on literal H of article 38 of Ley 16.696 and on articles 490 and 582.1 of the Recopilación de Normas de Regulación y Control del Sistema Financiero. Literal L of article 38 of Ley 16.696 empowers the Superintendencia to apply observations, warnings and fines of up to 10% of the basic net worth of banks to supervised entities that breach the general norms or particular instructions issued to them.

What it requires

Reuse law1 instrument, 1 in force

Research summary (175 words)

Uruguay has no press-publisher neighbouring right, no mandatory platform-to-publisher bargaining regime, no recognized hot-news misappropriation doctrine distinct from ordinary copyright law, and no located statute or case law addressing hyperlinking or framing liability specifically; each of those dimensions is a sourced absence rather than an unresolved question.

Ley N° 9.739 of 1937, as amended, protects expressions but not the ideas, procedures, operating methods, or facts they convey (art. 5), so a bare fact or news item carries no copyright regardless of who reports it first.

The same Law lets a person, without the author's consent, reproduce, distribute, communicate, or make available news, reports, journalistic information, or recordings of general interest, provided the exact version is kept and the source is credited (art. 45, numeral 3); that condition of exactness suits a traditional press clipping and has not been tested against a systematic aggregator's reproduction of headlines and short extracts in a reported Uruguayan decision.

Ley N° 9.739 predates the concept of a machine-readable text-and-data-mining reservation entirely, so no opt-out mechanism of that kind exists either.

Snippet reproduction

Ley N° 9.739 art. 45, numeral 3, news and press-reproduction exception

Ley N° 9.739, de 17 de diciembre de 1937, art. 45, numeral 3Consolidated, currently updated text of Ley N° 9.739, Centro de Información Oficial (IMPO), Uruguay's official legislative database

In force. Binds public and private bodies.

What this law does

Article 45 lists cases that are not illicit reproduction. Numeral 3 excepts news, reports, journalistic information, or recordings of general interest from the consent that article 44 otherwise requires, on the sole conditions that the exact version is preserved and the source is stated.

The exception is not capped at a headline or short-extract length and is not confined to the press industry, but the requirement to keep the exact version suits reproducing a news item whole, the way a press clipping does, rather than obviously covering an aggregator's extraction of a headline or a short snippet distinct from the source's own wording. No reported Uruguayan decision has applied numeral 3 to a systematic news aggregator as opposed to a traditional press review or broadcaster.

Separately, article 5 confines copyright to expressions and excludes ideas, procedures, operating methods, and mathematical concepts as such, so a bare fact or the news of the day is never itself a protected work under Uruguayan law. Uruguay has no separate press-publisher neighbouring right, no compelled platform-to-publisher bargaining regime, no recognized hot-news or misappropriation doctrine distinct from ordinary copyright law, and no located case law on hyperlinking or framed display.

Ley N° 9.739 states no day of its own entry into force; absent a stated day, article 1 of the Civil Code brings an undated law into force ten days after its promulgation is verified in the capital, a computed day rather than one a source states.

What it requires

Where nothing was found2 areas of law

These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.

AI law

Uruguay has no statute in force imposing an AI-transparency, output-labeling, or other AI-specific duty.

The Estrategia Nacional de Inteligencia Artificial 2024-2030, approved by the Presidencia de la República through AGESIC, sets ten guiding principles and lines of action for responsible AI development across the public and private sectors, including calls for disclosure of AI-generated content and of automated decisions, but is a non-binding policy strategy that creates no enforceable legal obligation.

AGESIC has circulated a draft comprehensive AI regulation bill and briefed the General Assembly on its recommendations, and press reporting in 2026 describes both that draft and a further deputy-sponsored proposal on AI-generated non-consensual sexual content, but neither a comprehensive AI bill nor either narrower measure was found recorded on the Parliament's own record as introduced with a bill number and a stage in the legislative process.

Uruguay signed the Council of Europe Framework Convention on Artificial Intelligence and Human Rights, Democracy and the Rule of Law (CETS No. 225) on ; no ratification is recorded as of the date below. The Convention reaches public authorities rather than private actors absent further implementing legislation.

As of .

Age gating law

Uruguay has no adult-content age-verification law, no social-media minor-access restriction, no app-store age-verification requirement, and no age-appropriate design code in force. The Código de la Niñez y la Adolescencia (Ley N° 17.823 of 2004), read in full, sets Uruguay's general framework for children's health, education, family, and labor rights but contains no reference to the internet, an online service, or an age-verification or age-gating duty.

Ley N° 17.815 of 2004 criminalises producing, distributing, and facilitating the distribution of child-sexual-abuse material and paying or contributing to a minor's sexual exploitation, but imposes no age-verification or age-gating duty on a publisher, platform, or app store.

As of September 2026 a bill would set a minimum age of fifteen for holding a social-media account and require platforms to implement reasonable, proportionate, and auditable age-verification mechanisms, introduced in the Chamber of Representatives by a single deputy in August 2026; it had not passed either chamber of the General Assembly.

As of .

Case law

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

Reporting clocks that run here5 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 Uruguay 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.

24 hours
72 hours
Breach notificationprivacy 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 Uruguay

30 minutes

Superintendencia de Servicios Financieros Communication on Technology, Systems and Information Security Events

Resolución RR-SSF-2021-353 de la Superintendencia de Servicios Financieros Comunicación de eventos vinculados a Tecnología, Sistemas y Seguridad de la Informaciónsecurity law, in force since

The sentences the clocks are read from

Report as a minimum any event that warrants a communication to clients, to the Agencia de Gobierno Electrónico y Sociedad de la Información y del Conocimiento (AGESIC) or to any other national entity or authority, that applies your business continuity or disaster recovery plan in whole or in part, that interrupts or affects a customer service channel for 30 minutes or more, that affects services to 10% or more of clients, or that exposes sensitive information and personal data of 5% or more of clients.

Communicate an emerging event as soon as possible after learning of it, even if not all information is available, and complete it in later reports; communicate a scheduled event at least 24 hours before it starts.

24 hours

Decreto 66/025, Cybersecurity Incident Reporting to CERTuy

Decreto N° 66/025, arts. 10(g) y 12security law, in force since

The sentences the clocks are read from

Communicate the occurrence of a cybersecurity incident to CERTuy within 24 hours of becoming aware of it, in the form and conditions CERTuy sets (article 10(g)).

Report the existence of a potential cybersecurity incident fully and immediately, under the criteria CERTuy sets (article 12(a)).

24 hours

Ley 20.212, Cybersecurity Incident Reporting by Public and Critical-Sector Entities

Ley N° 20.212, arts. 78(D) y 80security law, in force since

The sentences the clocks are read from

Report the existence of a potential cybersecurity incident fully and immediately, under the criteria the Centro Nacional de Respuesta a Incidentes de Seguridad Informática (CERTuy) sets, and make available all the information it requires (article 78(D)).

Communicate the occurrence of a cybersecurity incident to AGESIC within twenty-four hours of becoming aware of it, and complete the information needed for the National Cybersecurity Incident Registry as soon as possible (article 80).

72 hours

Decreto N° 64/020, personal data breach communication

Decreto N° 64/020, de 17 de febrero de 2020, art. 4 (comunicación de vulneraciones de seguridad)privacy law, in force since

The sentences the clocks are read from

As controller, once you establish that a security breach affecting data protection has occurred, communicate it to the Unidad Reguladora y de Control de Datos Personales within a maximum of 72 hours of becoming aware of the breach, with the relevant information, such as the certain or estimated date of the breach, its nature, the personal data affected and the possible impacts.

As processor, tell the controller immediately when you learn of a breach.

immediately

Ley N° 19.670, personal data breach notification

Ley N° 19.670, de 15 de octubre de 2018, art. 38, reglamentado por Decreto N° 64/020, de 2020 (notificación de vulneración de seguridad)privacy law, in force since

The sentences the clocks are read from

Notify the affected data subjects immediately and in detail on becoming aware of the breach, describing the measures adopted to address it.

Notify the Unidad Reguladora y de Control de Datos Personales immediately and in detail on becoming aware of the breach, coordinating your response with the national cybersecurity incident response center (CERTuy).

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.