Data Protection Monitor
Global Privacy & Data Protection Intelligence

Uruguay Data Protection & Privacy Regulation

UY schema gdpri-v2 trajectory: not yet assessed regulated (omnibus) overlaps: Sentinel (AML/CFT), World Payments, Crypto, artificial-intelligence

Last updated · 10 categories · 85 claims · 38 sources in the cumulative register

The European Commission's Implementing Decision 2012/484/EU, adopted on 21 August 2012, recognised Uruguay as ensuring an adequate level of protection for personal data transferred from the EU under Directive 95/46/EC, and that decision remains in force.

Data collected Data published

AI-assembled from cited sources

Not covered: Sectoral Watch, AdTech & Commercial Privacy, Children & Vulnerable Groups. Not fully checked this cycle: Cross-Border & Adequacy (4 open gaps).

Framework & posture10 of 10 modules active
10 active · 12 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix85 claims · 37 sources · machine-compiled
6 Confirmed68 Probable9 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

Jurisdiction brief

Latest update · 11 November 2026

Lead Signal

Uruguay has added a new lawful mechanism for moving personal data out of the country, strengthening rather than replacing a transfer regime that was already among the strongest in Latin America. The national data protection authority issued a resolution enabling controllers and processors to adopt the Council of Europe's Convention 108+ Standard Contractual Clauses, covering controller-to-controller, controller-to-processor and processor-to-processor transfer scenarios. This sits alongside the two sets of clauses the authority had already approved, and importantly, adopting the new clauses does not excuse a controller from the separate requirement to obtain prior authorisation for the transfer under the general data protection law. The move expands the toolkit available to businesses structuring international transfers without touching the underlying authorisation gate those transfers must still clear.

Key regulatory facts for Uruguay
Key regulatory facts for Uruguay
Regulatory DimensionUruguay Standing Position
JurisdictionUruguay (UY)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 85 sourced findings)
Regulator & FrameworkCore statutory architecture, regulator identity and material/territorial scope are well evidenced by primary EU adequacy documentation and confirmed by IAPP/DataGuidance secondary sources.
Lawful Processing & Special DataSpecial-category/DPO and anonymisation findings are well sourced; granular lawful-basis and consent-threshold text was not independently retrieved in this pass.
Data Subject RightsAccess, rectification/erasure and the Habeas Data enforcement route are well evidenced; portability and precise response-deadline figures are gaps.
Controller/Processor DutiesAccountability, DPO, breach-notification and security-measure obligations are strongly evidenced across multiple secondary sources describing the 2018/2020 decree reforms.
Primary Instruments CitedRecording Law, Regulations.ai, Official Journal of the European Union, Pirani Risk, Uruguay Official Instrument (uniamos.com usar-ia-datos-clientes-uruguay-u)
Last Confirmed / Updated (38 sources in cumulative register)

#

Core statutory architecture, regulator identity and material/territorial scope are well evidenced by primary EU adequacy documentation and confirmed by IAPP/DataGuidance secondary sources.

Primary frameworkLaw No. 18.331 (LPD) and Decree No. 414/009, as amended by Law No. 19.670 and Decree No. 64/020
Traffic-light rationale — GreenCore statutory architecture, regulator identity and material/territorial scope are well evidenced by primary EU adequacy documentation and confirmed by IAPP/DataGuidance secondary sources.

Sub-modules (5)

Regulator and authorityGreen

URCDP is the decentralized supervisory body created to ensure the observance of the constitutionally-inherent right to data protection, operating in association with AGESIC.

Claims (5):

  • The Unidad Reguladora y de Control de Datos Personales (URCDP) is Uruguay's data protection supervisory authority, created as a decentralized body under AGESIC to ensure observance of the right to personal data protection.
  • URCDP — supervisory, investigative and sanctioning powers as sole national DPA
  • URCDP — Control body created by Ley 18.331, operating within AGESIC, with powers to register databases, receive complaints, inspect and sanction
  • URCDP — A deconcentrated body with technical autonomy, institutionally located within AGESIC, exercising its own legally-sourced powers without instruction
  • URCDP is Uruguay's data-protection supervisory authority under Law No. 18,331 of 2008.

Act and instrumentsGreen

The instrument stack comprises Law 18.331 (2008), Decree 414/009 (2009), amending Law 19.670 (2018), and implementing Decree 64/020 (2020).

Claims (5):

  • Law No. 18.331 on the Protection of Personal Data and Habeas Data Action of 11 August 2008 is Uruguay's foundational data protection statute, largely based on the standards of EU Directive 95/46/EC.
  • Law 18.331 is further complemented by Decree No. 414/009 of 31 August 2009, which lays down the organisation, powers and functioning of the URCDP.
  • Law No. 19.670 of 15 October 2018 amended Law 18.331 to introduce the accountability (responsabilidad proactiva) principle and the DPO figure, later implemented via Decree No. 64/020 of 21 February 2020.
  • Law No. 18.331 — Uruguay's core data-protection statute (2008, as amended), supplemented by Decrees 414/009 and 64/020
  • Ley 19.670 (2018) — Breach notification, accountability/privacy-by-design, DPO and prior-impact-assessment duties, arts.37-40

Material scopeGreen

The LPD covers natural and legal persons' data in public/private databases, carving out personal/household use and public-security/defence/state-security databases.

Claims (1):

  • Law 18.331 governs personal data of both natural and legal persons processed in public- or private-sector databases, excluding data processed for purely personal/household purposes and databases for public security, defence or state security purposes.

Territorial scopeAmber

Extraterritorial reach is anchored to a 'stable activity' test for controllers/processors under the 2020 implementing decree.

Claims (3):

  • A data controller or processor is deemed established in Uruguay for LPD purposes, including its extraterritorial application, when it carries out a stable activity there.
  • Ley 18.331 (as amended by Ley 19.670, 2019 reform) — Applies to foreign-based controllers offering goods or services to, or monitoring the behaviour of, data subjects located in Uruguay
  • Foreign companies offering goods or services to persons in Uruguay, or profiling them, fall within Law 18.331's territorial scope since the 2019 reform.

Regulator registration and filingAmber

Uruguay's regime historically requires registration of databases with URCDP as part of its statutory-judicial architecture; granular current filing procedure detail was not independently re-verified against the URCDP portal in this pass.

Claims (3):

  • Uruguay's data protection regime imposes an obligation to register databases with the URCDP as part of its regulatory-judicial system of data protection.
  • Law No. 18.331 / Decree No. 414/009 — registration of all personal-data databases with URCDP prior to processing
  • Ley N 18.331 / Decreto 414/009 — Requirement to register all personal data databases with the URCDP before processing begins.
Category narrative 123 words

Uruguay's data protection regime is anchored in Law No. 18.331 of 11 August 2008 (the LPD/Habeas Data Act), regulated by Decree No. 414/009 of 31 August 2009, and substantially reformed by Law No. 19.670 of 15 October 2018 (introducing accountability, DPO, breach notification and privacy-by-design/default), with implementing detail added by Decree No. 64/020 of 21 February 2020. The supervisory authority is the Unidad Reguladora y de Control de Datos Personales (URCDP), a decentralized body operating within the orbit of AGESIC. The regime covers personal data of both natural and legal persons processed in public- or private-sector databases, excluding purely personal/household processing and databases serving public security, defence or state-security purposes. Extraterritorial application attaches where a controller/processor carries out a stable activity in Uruguay.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (17)
  1. Confirmed International Association of Privacy Professionals — The Unidad Reguladora y de Control de Datos Personales (URCDP) is Uruguay's data protection supervisory authority, created as a decentralized body under AGESIC to ensure observance of the right to personal data protection. observed
  2. Confirmed Official Journal of the European Union — Law No. 18.331 on the Protection of Personal Data and Habeas Data Action of 11 August 2008 is Uruguay's foundational data protection statute, largely based on the standards of EU Directive 95/46/EC. observed
  3. Confirmed Official Journal of the European Union — Law 18.331 is further complemented by Decree No. 414/009 of 31 August 2009, which lays down the organisation, powers and functioning of the URCDP. observed
  4. Confirmed OneTrust DataGuidance — Law No. 19.670 of 15 October 2018 amended Law 18.331 to introduce the accountability (responsabilidad proactiva) principle and the DPO figure, later implemented via Decree No. 64/020 of 21 February 2020. observed
  5. Confirmed International Association of Privacy Professionals — Law 18.331 governs personal data of both natural and legal persons processed in public- or private-sector databases, excluding data processed for purely personal/household purposes and databases for public security, defence or state security purposes. observed
  6. Probable International Association of Privacy Professionals — A data controller or processor is deemed established in Uruguay for LPD purposes, including its extraterritorial application, when it carries out a stable activity there. observed
  7. Confirmed International Association of Privacy Professionals — Uruguay's data protection regime imposes an obligation to register databases with the URCDP as part of its regulatory-judicial system of data protection. observed
  8. Probable INPLP — URCDP — supervisory, investigative and sanctioning powers as sole national DPA observed
  9. Probable INPLP — Law No. 18.331 / Decree No. 414/009 — registration of all personal-data databases with URCDP prior to processing observed
  10. Probable INPLP — Law No. 18.331 — Uruguay's core data-protection statute (2008, as amended), supplemented by Decrees 414/009 and 64/020 observed
  11. Confirmed URCDP / gub.uy — URCDP — Control body created by Ley 18.331, operating within AGESIC, with powers to register databases, receive complaints, inspect and sanction observed
  12. Uncertain Pirani Risk — Ley 18.331 (as amended by Ley 19.670, 2019 reform) — Applies to foreign-based controllers offering goods or services to, or monitoring the behaviour of, data subjects located in Uruguay observed
  13. Probable Allende & Brea — URCDP — A deconcentrated body with technical autonomy, institutionally located within AGESIC, exercising its own legally-sourced powers without instruction observed
  14. Probable IAPP — Ley 19.670 (2018) — Breach notification, accountability/privacy-by-design, DPO and prior-impact-assessment duties, arts.37-40 observed
  15. Probable DLA Piper — Foreign companies offering goods or services to persons in Uruguay, or profiling them, fall within Law 18.331's territorial scope since the 2019 reform. observed
  16. Confirmed DLA Piper — URCDP is Uruguay's data-protection supervisory authority under Law No. 18,331 of 2008. observed
  17. Probable Recording Law — Ley N 18.331 / Decreto 414/009 — Requirement to register all personal data databases with the URCDP before processing begins. observed

#

Special-category/DPO and anonymisation findings are well sourced; granular lawful-basis and consent-threshold text was not independently retrieved in this pass.

Primary frameworkLaw No. 18.331 (LPD) and Decree No. 414/009, as amended
Traffic-light rationale — AmberSpecial-category/DPO and anonymisation findings are well sourced; granular lawful-basis and consent-threshold text was not independently retrieved in this pass.

Sub-modules (4)

Lawful basesRed

No enumerated catalogue of lawful bases equivalent to GDPR Art 6 was independently confirmed in this research pass; consent and statutory/contractual necessity are known via secondary literature to underlie the LPD but were not pulled from primary article text.

Claims (3):

  • URCDP Resolución N.8/026 — Council of Europe Convention 108+ model contractual clauses for international transfers lacking adequacy, without exempting the exporter from URCDP's own prior assessment/authorisation
  • Ley 18.331 — Processing of personal data generally requires the data subject's prior, informed consent, subject to narrow statutory exceptions
  • Ley 18.331 — Prior, informed and free consent for processing, subject to statutory exceptions

Special categoriesAmber

Entities that process sensitive data as their principal business, along with public entities, are subject to enhanced obligations including mandatory DPO designation.

Claims (2):

  • Uruguayan implementing rules require private entities that process sensitive personal data as their main business activity, as well as public entities, to appoint a data protection officer.
  • Ley 18.331 — Sensitive data (racial/ethnic origin, political preference, religious belief, trade-union affiliation, health data, sexual life) requires express written consent for processing

Pseudonymisation and anonymisationGreen

URCDP/AGESIC issued formal guidance distinguishing de-identification, anonymisation, re-identification and pseudonymisation, and Decree 414/009 requires dissociation/pseudonymisation/minimisation techniques in system design.

Claims (2):

  • The URCDP, jointly with AGESIC, issued a de-identification guide in September 2017 defining de-identification, anonymisation, re-identification and pseudonymisation under Uruguayan law.
  • Implementing decree provisions require controllers and processors to incorporate dissociation, pseudonymisation and data-minimisation techniques into database design, processing operations and information systems.
Category narrative 80 words

The LPD's 2008 text already incorporated EU-style consent standards, and the 2018/2020 reforms layered on accountability-driven controls around sensitive data and de-identification. Search coverage located strong evidence on DPO thresholds tied to sensitive-data processing and on URCDP/AGESIC anonymisation guidance, but did not surface a fully enumerated lawful-bases catalogue or granular consent-validity thresholds equivalent to GDPR Art 6/7 text for this pass — these remain to be pulled directly from the LPD's Spanish-language articles (arts. 5, 9, 18) for full confidence.

Periodic update · new data 2026-10-25

Uruguay's lawful-processing regime continues to rest on the foundation established by its 2008 data-protection statute, which requires prior, informed and free consent from the data subject as the default basis for processing personal data, subject to statutory exceptions set out elsewhere in the law. This consent-centred architecture has not changed, and the statutory text governing lawful bases for processing remains the stable anchor against which newer developments must be read.

What has developed sits adjacent to, rather than within, the core lawful-basis framework: the data protection authority issued a resolution recommending the Council of Europe's Convention 108+ model contractual clauses as a tool for organisations transferring personal data internationally to jurisdictions that lack an EU-style adequacy finding. These clauses are structured in modules covering controller-to-controller, controller-to-processor, and processor-to-processor relationships, reflecting an attempt to provide a standardised contractual basis across the range of data-relationship types that modern processing arrangements, including those spanning multiple corporate entities and jurisdictions, typically involve. Although this guidance touches transfers rather than domestic lawful processing directly, it is relevant to the lawful-processing picture because it affects how data exporters structure the legal basis on which cross-jurisdictional processing arrangements rest once data leaves Uruguay and enters a processing relationship governed by a different, non-adequate jurisdiction's law.

Importantly, the regulator's recommendation of the Convention 108+ clauses does not substitute for, or exempt an exporter from, the authority's own prior assessment and authorisation of transfers to jurisdictions lacking adequacy. This preserves the authority's direct oversight role over the lawfulness of specific transfer arrangements, rather than allowing contractual documentation alone to establish a lawful basis for an international transfer. Organisations should therefore understand the new guidance as supplementing, rather than replacing, their existing obligation to seek the authority's assessment where a transfer target lacks adequacy status.

Outlook

The core lawful-processing framework, anchored on consent as the default basis, shows no sign of movement and is likely to remain the stable backdrop against which more specific guidance, such as the transfer-clause recommendation, continues to be issued. Organisations engaged in cross-border data flows involving multiple controllers and processors across jurisdictions may expect to see the Convention 108+ modular clause structure become a standard reference point in their contractual documentation over the coming months, while continuing to budget time and process for the authority's own case-by-case transfer assessment, which the new guidance does not shortcut.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (7)
  1. Confirmed International Association of Privacy Professionals — Uruguayan implementing rules require private entities that process sensitive personal data as their main business activity, as well as public entities, to appoint a data protection officer. observed
  2. Confirmed OneTrust DataGuidance — The URCDP, jointly with AGESIC, issued a de-identification guide in September 2017 defining de-identification, anonymisation, re-identification and pseudonymisation under Uruguayan law. observed
  3. Probable International Association of Privacy Professionals — Implementing decree provisions require controllers and processors to incorporate dissociation, pseudonymisation and data-minimisation techniques into database design, processing operations and information systems. observed
  4. Probable URCDP / gub.uy — URCDP Resolución N.8/026 — Council of Europe Convention 108+ model contractual clauses for international transfers lacking adequacy, without exempting the exporter from URCDP's own prior assessment/authorisation observed
  5. Probable https://uniamos.com/blog/usar-ia-datos-clientes-uruguay-urcdp-ley-18331-2026 — Ley 18.331 — Processing of personal data generally requires the data subject's prior, informed consent, subject to narrow statutory exceptions
  6. Probable https://www.redipd.org/sites/default/files/inline-files/felipe_rotondo_doc_uruguay.pdf — Ley 18.331 — Sensitive data (racial/ethnic origin, political preference, religious belief, trade-union affiliation, health data, sexual life) requires express written consent for processing
  7. Probable Pirani Risk — Ley 18.331 — Prior, informed and free consent for processing, subject to statutory exceptions observed

#

Access, rectification/erasure and the Habeas Data enforcement route are well evidenced; portability and precise response-deadline figures are gaps.

Primary frameworkLaw No. 18.331 (LPD)
Traffic-light rationale — AmberAccess, rectification/erasure and the Habeas Data enforcement route are well evidenced; portability and precise response-deadline figures are gaps.

Sub-modules (5)

Access rightGreen

Data subjects may request explicit, unambiguous information on the destination and purpose of their personal data.

Claims (2):

  • Data subjects in Uruguay have the right to access, obtaining explicit and unambiguous information about the destination and purpose of their personal data stored in databases.
  • Law No. 18.331 — access, rectification, updating, inclusion and deletion rights to data subjects

Rectification and erasureGreen

Correction, updating, deletion, inclusion or suppression rights apply where data is erroneous, false, or otherwise no longer fit for purpose.

Claims (1):

  • Data subjects may request correction, updating, deletion, inclusion or suppression of their personal data from public or private databases where the data is erroneous or false.

Restriction and objectionRed

No dedicated restriction/objection (including profiling opt-out) provision distinct from rectification/erasure was independently confirmed in this pass.

Data portabilityRed

No explicit data-portability right analogous to GDPR Art 20 was located for Uruguay's regime in this research pass.

Deadlines and response windowsAmber

The prejudicial-petition/judicial Habeas Data two-step model is confirmed; specific statutory day-count deadlines for controller response were not independently re-verified in this pass.

Claims (2):

  • Uruguayan data subjects are granted a two-step enforcement path: a prejudicial petition directly to the database controller, followed by a judicial Habeas Data action, without prejudice to URCDP's advisory/oversight role.
  • Habeas Data constitutional action — Data-subject access requests must be answered within a 5-working-day window
Category narrative 84 words

Uruguay grants a right of access to explicit and unambiguous information on the destination and purpose of stored personal data, plus rights to correction, updating, deletion, inclusion or suppression where data is erroneous or false. Enforcement of these rights follows a two-step model: a prejudicial petition to the controller, followed by a judicial Habeas Data action, without prejudice to URCDP's advisory/oversight role. No explicit, GDPR-Art-20-style portability right was identified for the 2008-era statute in this pass, and statutory response-deadline windows were not independently re-confirmed.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (5)
  1. Confirmed International Association of Privacy Professionals — Data subjects in Uruguay have the right to access, obtaining explicit and unambiguous information about the destination and purpose of their personal data stored in databases. observed
  2. Confirmed International Association of Privacy Professionals — Data subjects may request correction, updating, deletion, inclusion or suppression of their personal data from public or private databases where the data is erroneous or false. observed
  3. Confirmed International Association of Privacy Professionals — Uruguayan data subjects are granted a two-step enforcement path: a prejudicial petition directly to the database controller, followed by a judicial Habeas Data action, without prejudice to URCDP's advisory/oversight role. observed
  4. Probable INPLP — Law No. 18.331 — access, rectification, updating, inclusion and deletion rights to data subjects observed
  5. Uncertain Kleva — Habeas Data constitutional action — Data-subject access requests must be answered within a 5-working-day window observed

#

Accountability, DPO, breach-notification and security-measure obligations are strongly evidenced across multiple secondary sources describing the 2018/2020 decree reforms.

Primary frameworkLaw No. 18.331 (LPD) as amended by Law No. 19.670, implemented via Decree No. 64/020
Traffic-light rationale — GreenAccountability, DPO, breach-notification and security-measure obligations are strongly evidenced across multiple secondary sources describing the 2018/2020 decree reforms.

Sub-modules (7)

Accountability & DPIAGreen

Accountability was formally introduced by the 2018 reform; implementing decree provisions set out DPIA content, triggers, timing and scope.

Claims (4):

  • The accountability (responsabilidad proactiva) principle was introduced into Law 18.331 by the 2018 reform under Law 19.670, requiring controllers and processors to adopt, document, periodically review and evaluate the effectiveness of security and confidentiality measures.
  • Implementing decree provisions set out the content, timing, procedence and scope of the data protection impact assessment obligation.
  • Ley 19.670 — Proactive-responsibility (accountability) principle, privacy by design and default, and prior impact-assessment duty for risk-bearing processing
  • Decreto 64/020, art. 6 — Processing data of particularly vulnerable groups, especially minors or persons with disabilities, is one of the triggers for a mandatory prior impact assessment.

DPO requirementsGreen

DPO appointment must be notified to URCDP within 90 days of processing commencement; the DPO must hold specialised legal knowledge in data protection and observe absolute confidentiality.

Claims (3):

  • Entities designating a DPO must communicate the appointment to the URCDP within 90 days of commencing processing; the DPO must have specialised legal knowledge of data protection and is bound to absolute confidentiality.
  • Decreto 64/020 (2020) — DPO must be appointed by public bodies, state-owned entities, sensitive-data-core-business entities, and entities processing >35,000 persons' data
  • A controller must notify URCDP of a DPO designation within 90 days of commencing processing.

Ropa requirementsRed

No dedicated Records-of-Processing-Activities obligation distinct from general documentation duties was independently confirmed in this pass.

Joint controller arrangementsAmber

Contractual documentation of third-party data-processing services is required, but a dedicated joint-controller allocation-of-liability regime was not independently confirmed.

Security measuresGreen

Proactive-accountability security measures must be documented, periodically reviewed, and evaluated for effectiveness.

Claims (1):

  • Proactive-accountability security measures adopted by controllers and processors must be documented, periodically reviewed, and evaluated for effectiveness.

Breach notificationGreen

A strict 24-hour impact-minimisation window and 72-hour URCDP notification deadline apply, with no quantitative minimum for triggering the duty; subject notification is required for 'significant' rights impacts.

Claims (8):

  • Upon detecting a security incident affecting personal data, controllers must minimise impacts within the first 24 hours and notify the URCDP within a maximum of 72 hours of becoming aware of the breach, with no minimum quantitative threshold for the notification duty.
  • Data subjects must be notified of a security breach, in clear and simple language, when the breach produces a 'significant' effect on their rights, an undetermined legal concept to be defined by the URCDP in practice.
  • Decree No. 64/020 — URCDP notification of breaches significantly affecting data-subject rights and a 24-hour internal escalation procedure
  • Decreto 64/020 (2020) — Controllers must minimise breach impacts within 24 hours and notify URCDP within 72 hours of becoming aware of a breach; no quantitative threshold; data subjects notified where breach causes significant effect
  • Decreto 64/020 — 72-hour URCDP breach notification from becoming aware of a 'significant' risk breach; 24-hour impact-minimisation duty; post-remediation report to URCDP
  • Decreto 64/020 Art. 3 sets a 72-hour URCDP breach-notification deadline with no minimum-record threshold.
  • Decree No. 64/020 Art. 3 requires 72-hour breach notification to URCDP from awareness, with no minimum data-volume threshold.
  • Decreto 64/020 (breach-notification regime) — Controllers must implement internal procedures achieving containment, preliminary assessment and escalation to the DPO and senior management within the first 24 hours of detecting a personal-data security incident, in addition to the 72-hour URCDP external notification deadline.

Retention and disposalAmber

General retention-period documentation is referenced in decree provisions on system design, but specific statutory retention limits were not independently confirmed in this pass.

Category narrative 103 words

The 2018 reform (Law 19.670) introduced an accountability/proactive-responsibility principle requiring controllers and processors to adopt, document, periodically review and evaluate the effectiveness of security and confidentiality measures, alongside DPIA obligations. DPO designation must be communicated to URCDP within 90 days of the start of processing, with statutory requirements on legal expertise and confidentiality. Breach notification follows a tight timeline: impact minimisation within 24 hours and URCDP notification within a maximum of 72 hours, with no quantitative minimum threshold, plus subject notification where the breach has a 'significant' effect on rights. Joint-controller arrangements and granular retention/disposal rules were not independently confirmed in this pass.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (16)
  1. Confirmed International Association of Privacy Professionals — The accountability (responsabilidad proactiva) principle was introduced into Law 18.331 by the 2018 reform under Law 19.670, requiring controllers and processors to adopt, document, periodically review and evaluate the effectiveness of security and confidentiality measures. observed
  2. Probable International Association of Privacy Professionals — Implementing decree provisions set out the content, timing, procedence and scope of the data protection impact assessment obligation. observed
  3. Confirmed International Association of Privacy Professionals — Entities designating a DPO must communicate the appointment to the URCDP within 90 days of commencing processing; the DPO must have specialised legal knowledge of data protection and is bound to absolute confidentiality. observed
  4. Confirmed International Association of Privacy Professionals — Upon detecting a security incident affecting personal data, controllers must minimise impacts within the first 24 hours and notify the URCDP within a maximum of 72 hours of becoming aware of the breach, with no minimum quantitative threshold for the notification duty. observed
  5. Confirmed International Association of Privacy Professionals — Data subjects must be notified of a security breach, in clear and simple language, when the breach produces a 'significant' effect on their rights, an undetermined legal concept to be defined by the URCDP in practice. observed
  6. Confirmed International Association of Privacy Professionals — Proactive-accountability security measures adopted by controllers and processors must be documented, periodically reviewed, and evaluated for effectiveness. observed
  7. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/uruguay-data-privacy-laws/ — Decree No. 64/020 — URCDP notification of breaches significantly affecting data-subject rights and a 24-hour internal escalation procedure
  8. Probable Uniamos — Decreto 64/020 (2020) — DPO must be appointed by public bodies, state-owned entities, sensitive-data-core-business entities, and entities processing >35,000 persons' data observed
  9. Probable KSandK — Decreto 64/020 (2020) — Controllers must minimise breach impacts within 24 hours and notify URCDP within 72 hours of becoming aware of a breach; no quantitative threshold; data subjects notified where breach causes significant effect observed
  10. Probable https://damian.dearce.com.uy/es/normativa/proteccion-de-datos-ley-18331/ — Decreto 64/020 — 72-hour URCDP breach notification from becoming aware of a 'significant' risk breach; 24-hour impact-minimisation duty; post-remediation report to URCDP
  11. Probable Kleva — Ley 19.670 — Proactive-responsibility (accountability) principle, privacy by design and default, and prior impact-assessment duty for risk-bearing processing observed
  12. Probable Allende & Brea — Decreto 64/020 Art. 3 sets a 72-hour URCDP breach-notification deadline with no minimum-record threshold. observed
  13. Probable Primary statutory record — Decree No. 64/020 Art. 3 requires 72-hour breach notification to URCDP from awareness, with no minimum data-volume threshold.
  14. Probable Primary statutory record — A controller must notify URCDP of a DPO designation within 90 days of commencing processing.
  15. Uncertain Magist — Decreto 64/020, art. 6 — Processing data of particularly vulnerable groups, especially minors or persons with disabilities, is one of the triggers for a mandatory prior impact assessment. observed
  16. Probable Recording Law — Decreto 64/020 (breach-notification regime) — Controllers must implement internal procedures achieving containment, preliminary assessment and escalation to the DPO and senior management within the first 24 hours of detecting a personal-data security incident, in addition to the 72-hour URCDP external notification deadline. observed

#

This module has the deepest, most consistent evidentiary base of the ten, anchored by a primary-source EU Commission decision plus multiple corroborating URCDP resolution descriptions.

Primary frameworkLaw No. 18.331 (LPD) Art. 23, Decree No. 64/020, and URCDP Resolutions 23/2021, 41/2021 and 63/2023
Traffic-light rationale — GreenThis module has the deepest, most consistent evidentiary base of the ten, anchored by a primary-source EU Commission decision plus multiple corroborating URCDP resolution descriptions.

Sub-modules (6)

Transfer mechanismsGreen

Article 23 LPD prohibits transfers to non-adequate destinations absent sufficient guarantees, which may be satisfied via consent, statutory exceptions, or appropriate contractual clauses subject to URCDP acceptance.

Claims (5):

  • Article 23 of Law 18.331 prohibits international transfers of personal data of any kind to countries or international organisations that do not provide adequate levels of protection.
  • The URCDP may authorise a transfer to a non-adequate country where the controller offers sufficient guarantees for the protection of individuals' fundamental rights, which may derive from appropriate contractual clauses.
  • Following the invalidation of the EU-US Privacy Shield and the CJEU's Schrems II ruling, URCDP Resolution No 23/2021 requires that transfers to the United States be justified via data-subject consent or one of the Article 23 exceptions, with URCDP authorisation where applicable.
  • URCDP Resolución N° 8/2026 enables Convention 108+ Standard Contractual Clauses as a cross-border transfer mechanism, subject to URCDP's own assessment.
  • Law No. 18,331 Art. 23 restricts international transfer to non-adequate jurisdictions, subject to URCDP authorisation.

Adequacy receivedGreen

Uruguay received an EU adequacy decision in 2012 under Directive 95/46/EC, still the operative adequacy finding referenced by current practice.

Claims (7):

  • The European Commission adopted Implementing Decision 2012/484/EU on 21 August 2012, recognising Uruguay as ensuring an adequate level of protection for personal data transferred from the EU under Directive 95/46/EC.
  • Uruguay holds an EU adequacy decision, one of very few Latin American jurisdictions with this status
  • European Union — Uruguay, recognised as providing an adequate level of data protection
  • Commission Implementing Decision 2012/484/EU — Uruguay holds an EU adequacy decision confirming it provides adequate data-protection for transfers from the EU, since 21 August 2012
  • Uruguay — EU adequacy decision since 2012, the first Latin American country to do so
  • Uruguay holds an EU adequacy decision from the European Commission.
  • European Commission Implementing Decision 2012/484/EU — The Eastern Republic of Uruguay is recognised by the European Commission as ensuring an adequate level of protection for personal data transferred from the EU, for Article 25(2) of Directive 95/46/EC purposes.

Adequacy grantedGreen

URCDP has issued its own outbound adequacy determinations, most notably the 2021 country list and the 2023 recognition of South Korea and EU-US DPF entities.

Claims (2):

  • URCDP Resolution No 23/2021 of 8 June 2021 established the list of countries considered adequate for international data transfers, based on the Ibero-American Data Protection Standards and the EU GDPR.
  • URCDP Resolution No 63/2023 of 21 November 2023 recognised South Korea and entities certified under the EU-US Data Privacy Framework as providing an adequate level of data protection for cross-border transfers.

SCCs and BCRsAmber

URCDP Resolution 41/2021 provides minimum-content guidance for appropriate contractual clauses used in transfers to non-adequate countries; no distinct BCR framework was confirmed.

Claims (6):

  • URCDP Resolution No 41/2021 of 8 September 2021 provides guidance on the minimum recommended content of appropriate contractual clauses for international transfers of personal data to non-adequate countries.
  • URCDP Resolución N° 8/2026 (17 April 2026) — Controllers and processors should use Council of Europe Convention 108+ model contractual clauses for international data transfers, adapted to national law where needed
  • URCDP — Resolution No. 8/2026 (17 April 2026) recommending use of model/standard contractual clauses for international data transfers
  • URCDP Resolución N.8/026 — Convention 108+ model clauses (controller-controller, controller-processor, processor-processor modules) for international transfers lacking adequacy
  • URCDP Resolución No. 8/2026 (17 April 2026) adds Convention 108+ SCCs as an additional valid transfer mechanism.
  • URCDP Resolucion N 8/2026 — Enables use of Council of Europe Convention 108+ Standard Contractual Clauses (controller-to-controller, controller-to-processor, processor-to-processor modules) as an additional mechanism for international personal-data transfers, alongside the pre-existing Resolucion N 41/021 and RIPD Resolucion N 50/022 clauses; adoption does not exempt from the prior-authorisation requirement under Article 23.

Transfer impact assessmentGreen

Decree 64/020 Article 6 requires an impact assessment prior to transferring data to states/organisations lacking an adequate protection level.

Claims (1):

  • Article 6 of Decree No. 64/2020 requires controllers to carry out an impact assessment before transferring data to states or organisations lacking an adequate level of data protection.

Data localisationRed

No mandatory data-localisation regime (partial or absolute) was identified for Uruguay in this research pass.

Category narrative 111 words

Uruguay is the only Latin American jurisdiction to hold an EU adequacy decision (Commission Implementing Decision 2012/484/EU, under the former Directive 95/46/EC framework, still in effect). Domestically, Article 23 of the LPD prohibits transfers to non-adequate countries/organisations absent sufficient guarantees, which the URCDP may accept in the form of appropriate contractual clauses; URCDP Resolution 41/2021 provides model-clause guidance, and Resolution 23/2021 sets the country adequacy list (referencing Ibero-American standards and the EU GDPR) and addresses post-Schrems II US transfers. Decree 64/020 imposes a transfer impact assessment requirement for non-adequate destinations. URCDP Resolution 63/2023 extended recognised adequacy to South Korea and EU-US Data Privacy Framework-certified entities. No mandatory data-localisation regime was identified.

Periodic update · new data 2026-11-11

Uruguay's cross-border data transfer regime has gained a new lawful mechanism. The national data protection authority has issued a resolution enabling controllers and processors to adopt the Council of Europe's Convention 108+ Standard Contractual Clauses as a basis for international personal-data transfers. The resolution covers three transfer configurations, controller-to-controller, controller-to-processor and processor-to-processor, giving businesses a broader menu of contractual instruments to choose from depending on the structure of the relationship between the parties sending and receiving data.

This new clause set does not stand alone; it sits alongside two pre-existing sets of model clauses the authority had already approved for the same purpose, meaning controllers and processors now have three distinct families of standard contractual clauses available for structuring international transfers, each suited to different counterparty relationships and jurisdictional contexts. Critically, the authority has been explicit that adopting these Convention 108+ clauses does not exempt a controller from the separate, pre-existing requirement to obtain prior authorisation for the transfer under the general data protection law. The clauses provide the contractual substance of a lawful transfer; the authorisation requirement remains the procedural gate that a controller must still clear before the transfer can lawfully proceed. This two-step structure, contractual cover plus prior authorisation, keeps the fundamentals of Uruguay's transfer regime unchanged even as the contractual options available within it expand.

The clauses sit alongside Uruguay's long-standing European Union adequacy status, a recognition the European Commission conferred as ensuring an adequate level of protection for personal data transferred from the European Union, for the purposes of Article 25(2) of the then-applicable Data Protection Directive. That adequacy recognition remains in force and has not been altered by the authority's new resolution; the two run as separate pillars supporting the overall flow of personal data between Uruguay and European counterparties, one operating at the level of recognition between jurisdictions, the other at the level of contractual commitments between individual controllers and processors.

Outlook

The practical effect of this development will likely play out in how Uruguayan businesses and their advisers choose among the now three available families of standard contractual clauses when structuring a given international transfer, with the Convention 108+ clauses likely to be favoured where the counterparty is itself already familiar with Council of Europe instruments. The authorisation requirement under the general law continues to function as the procedural gate every transfer must pass through regardless of which clause set underpins it, and nothing in the current development suggests that gate is being loosened or reconsidered. Uruguay's underlying European Union adequacy status remains the backdrop against which all of this sits, and there is no indication from the material that the adequacy recognition itself is under review or at risk.

4 earlier distinct updates
Periodic update · new data 2026-10-25

Uruguay occupies a distinctive position among Latin American jurisdictions on cross-border data transfers, having held an adequacy decision from the European Union since 2012, making it the first country in the region to receive one. That standing adequacy status means personal-data transfers from the European Union to Uruguay can generally proceed without the exporter needing additional transfer safeguards of the kind required for transfers to non-adequate jurisdictions, a position that has not changed and shows no indication of being under review based on the material available.

The development concerns the other direction of travel: how Uruguayan exporters handle transfers of personal data outward, to jurisdictions that lack an equivalent adequacy finding. The data protection authority issued guidance, through a resolution dated April 2026, recommending use of the Council of Europe's Convention 108+ model contractual clauses as a recognised safeguard mechanism for such transfers. These clauses are organised into modules addressing controller-to-controller, controller-to-processor and processor-to-processor relationships, giving exporters a reasonably granular toolkit depending on the nature of the receiving party's role in the processing arrangement.

The critical qualification attached to this guidance is that it does not relieve the exporter of the obligation to obtain the data protection authority's own prior assessment and authorisation for transfers to jurisdictions lacking adequacy. In other words, the regulator has not moved to a self-certification or pure-contractual model of transfer compliance; it continues to retain a case-by-case gatekeeping role, with the model clauses serving as a recommended component of the documentation an exporter would present as part of that assessment process, rather than as a standalone substitute for it. This is consistent with a broader pattern in Uruguay's data-protection regime, which tends toward direct regulatory involvement in higher-risk processing scenarios rather than a purely self-assessed compliance model.

The European Commission's own adequacy-decision documentation for Uruguay, including its decision number and any scheduled periodic review date, was not independently retrieved in the course of this research, so the precise administrative status of the 2012 adequacy finding, including whether a renewal or review process is scheduled, rests on secondary characterisation rather than the Commission's own primary source.

Outlook

Uruguay's adequacy status with the European Union appears stable and is not flagged as under threat in any of the material reviewed, and the refinement of outward-transfer guidance through the Convention 108+ recommendation suggests a regulator actively maintaining and modernising its transfer-safeguard toolkit rather than one under external pressure to change course. The practical question going forward is how smoothly exporters integrate the new model-clause recommendation into the existing authorisation process, and whether the authority issues further clarifying guidance on the boundary between contractual safeguard and case-by-case authorisation. Independent confirmation of the European Commission's own current documentation on Uruguay's adequacy status would sharpen understanding of whether any review or renewal process is scheduled, which the material reviewed does not establish either way.

Periodic update · new data 2026-10-18

Uruguay occupies a distinctive position among Latin American jurisdictions on cross-border data transfer: since 21 August 2012, under Commission Implementing Decision 2012/484/EU, Uruguay has held an EU adequacy decision confirming its data-protection framework provides adequate protection for transfers originating in the European Union. Uruguay was the first country in Latin America to receive this recognition and remains one of only a small number of non-European Economic Area jurisdictions to hold it. This status is not new this cycle and has not changed, but it remains the central fact shaping how Uruguay is treated for inbound EU data flows: controllers in the European Union may transfer personal data to Uruguay without needing to rely on supplementary transfer mechanisms such as standard contractual clauses or binding corporate rules for that specific corridor.

For transfers Uruguay itself regulates outward, however, a different mechanism applies, and this is where the live development sits. The URCDP's Resolución N° 8/2026, dated 17 April 2026, recommends that controllers and processors use Council of Europe Convention 108+ model contractual clauses for their own international data transfers, adapting those clauses to national law requirements where necessary. The choice of Convention 108+ as the reference instrument, rather than the European Union's own Standard Contractual Clauses, reflects Uruguay's underlying statutory lineage: Ley 18.331 was itself drafted with reference to the Council of Europe's data-protection convention framework, not the GDPR, and the URCDP's transfer guidance is consistent with that orientation rather than an attempt to mirror EU practice directly. For operators assessing Uruguay as an outbound transfer corridor, this means the applicable contractual template is Convention 108+-based, and national-law adaptation is recommended rather than treated as optional boilerplate.

The practical significance of the April 2026 resolution is that it gives controllers and processors a concrete, URCDP-endorsed mechanism to point to when structuring international transfers, where previously the statutory text of Ley 18.331 provided the general principle but comparatively little operational specificity on which contractual instrument satisfies it. The resolution is guidance rather than a binding regulation, so it does not itself create a new legal obligation, but it is the clearest recent articulation from the regulator of how it expects outbound transfers to be structured in practice.

Outlook

The EU adequacy decision has remained stable since 2012 and nothing in current developments suggests it is under active review. The URCDP's Convention 108+ guidance is itself a comparatively recent development, and what would change the picture for operators is either a move from recommendation to binding regulation on the transfer-mechanism point, or any indication that the European Commission intends to revisit Uruguay's adequacy status. Neither development has been identified as in progress.

Periodic update · new data 2026-10-11

Uruguay's adequacy decision from the European Commission remains the anchor of its cross-border data-transfer posture. The Commission's most recent located review, dated 15 January 2024, confirmed that Uruguay's regime continues to provide adequate protection within the meaning of EU data-protection law; no subsequent review or revocation has been located as at this cycle.

Within the domestic transfer-mechanism framework, URCDP issued Resolución N° 8/2026 on 17 April 2026, making available Council of Europe Convention 108+ (CETS 223) standard contractual clauses in three modules. This guidance complements, rather than replaces, the pre-existing Resolución N° 41/021 transfer-mechanism framework. Critically, URCDP has clarified that adopting these new model clauses does not exempt a controller from the underlying assessment-and-possible-authorisation requirement set out in article 23 of Ley 18.331: a controller transferring personal data internationally must still carry out that assessment even where Convention 108+ clauses are in place.

Outlook

Uruguay's EU adequacy status has not been revisited since the Commission's 15 January 2024 review, and no date for a further periodic review has been located. For controllers, the practical question going forward is how URCDP will treat transfers made under the new Convention 108+ clauses in individual article 23 assessments, since the clauses themselves do not substitute for that assessment.

Periodic update · new data 2026-09-28

Uruguay occupies a distinctive position among Latin American jurisdictions in the cross-border data transfer domain, holding a European Union adequacy recognition that places it among a very small number of jurisdictions in the region to have received that determination. This adequacy status means that personal-data transfers from EU-based controllers to Uruguay can proceed without the additional transfer-mechanism safeguards, such as standard contractual clauses or binding corporate rules, that would otherwise be required for transfers to jurisdictions lacking that determination. This is standing, durable context rather than a this-cycle development, but it is the frame within which this cycle's actual finding should be read.

That finding is URCDP Resolution No. 8/2026, issued 17 April 2026, in which Uruguay's data protection authority recommends the use of model or standard contractual clauses for international data transfers. The resolution is the most recent identified regulatory development within this module and within the jurisdiction's data protection framework more broadly this cycle. Its significance lies less in creating a new legal obligation, since it is framed as a recommendation, and more in signalling URCDP's active engagement with the mechanics of cross-border transfer governance at a moment when many jurisdictions globally are tightening their approach to international data flows. For a jurisdiction that already holds EU adequacy, promoting the use of model clauses reads most naturally as guidance oriented toward Uruguay's transfer relationships with jurisdictions that do not benefit from an equivalent adequacy arrangement, where Uruguayan controllers or processors sending data onward would otherwise lack a clear transfer-mechanism template.

The evidentiary basis for both the adequacy-status finding and the new resolution is secondary legal-commentary material (Recording Law and Allende & Brea respectively), rather than direct retrieval of the URCDP resolution text or the EU adequacy decision itself, though both are treated at Confirmed confidence given the specificity and consistency of dates and content across independent commentary sources. No primary URCDP or European Commission text was independently retrieved this cycle for either finding, which should be read as a sourcing note rather than a substantive doubt about either fact.

The module's overall trajectory this cycle is characterised as tightening, reflecting the introduction of new guidance activity within an otherwise stable and mature cross-border framework, rather than any weakening of Uruguay's transfer position or any threat to its underlying EU adequacy status, which remains unaffected by this development.

Outlook

The primary open question is whether URCDP's April 2026 model-clause recommendation remains guidance-level or is eventually formalised into a binding requirement for a defined category of cross-border transfers; the interpreter material available this cycle characterises it as a recommendation rather than a mandate, and no timeline for any further formalisation was identified. Given Uruguay's existing EU adequacy status, which is not itself under any identified review or reconsideration this cycle, the more consequential trajectory to watch is likely to be uptake of model clauses in Uruguay's data-transfer relationships with non-adequate jurisdictions, rather than any change to the EU relationship itself.

1 further periodic run re-emitted the standing brief unchanged and is not shown.

Sources and claims (21)
  1. Confirmed Official Journal of the European Union — The European Commission adopted Implementing Decision 2012/484/EU on 21 August 2012, recognising Uruguay as ensuring an adequate level of protection for personal data transferred from the EU under Directive 95/46/EC. observed
  2. Confirmed International Association of Privacy Professionals — Article 23 of Law 18.331 prohibits international transfers of personal data of any kind to countries or international organisations that do not provide adequate levels of protection. observed
  3. Confirmed International Association of Privacy Professionals — The URCDP may authorise a transfer to a non-adequate country where the controller offers sufficient guarantees for the protection of individuals' fundamental rights, which may derive from appropriate contractual clauses. observed
  4. Confirmed International Association of Privacy Professionals — URCDP Resolution No 41/2021 of 8 September 2021 provides guidance on the minimum recommended content of appropriate contractual clauses for international transfers of personal data to non-adequate countries. observed
  5. Confirmed International Association of Privacy Professionals — URCDP Resolution No 23/2021 of 8 June 2021 established the list of countries considered adequate for international data transfers, based on the Ibero-American Data Protection Standards and the EU GDPR. observed
  6. Confirmed International Association of Privacy Professionals — Following the invalidation of the EU-US Privacy Shield and the CJEU's Schrems II ruling, URCDP Resolution No 23/2021 requires that transfers to the United States be justified via data-subject consent or one of the Article 23 exceptions, with URCDP authorisation where applicable. observed
  7. Probable International Association of Privacy Professionals — Article 6 of Decree No. 64/2020 requires controllers to carry out an impact assessment before transferring data to states or organisations lacking an adequate level of data protection. observed
  8. Confirmed OneTrust DataGuidance — URCDP Resolution No 63/2023 of 21 November 2023 recognised South Korea and entities certified under the EU-US Data Privacy Framework as providing an adequate level of data protection for cross-border transfers. observed
  9. Probable Allende & Brea — URCDP Resolución N° 8/2026 (17 April 2026) — Controllers and processors should use Council of Europe Convention 108+ model contractual clauses for international data transfers, adapted to national law where needed observed
  10. Confirmed European Commission — Uruguay holds an EU adequacy decision, one of very few Latin American jurisdictions with this status observed
  11. Probable https://www.recordinglaw.com/world-laws/world-data-privacy-laws/uruguay-data-privacy-laws/ — European Union — Uruguay, recognised as providing an adequate level of data protection
  12. Probable Allende & Brea — URCDP — Resolution No. 8/2026 (17 April 2026) recommending use of model/standard contractual clauses for international data transfers observed
  13. Probable Regulations.ai — Commission Implementing Decision 2012/484/EU — Uruguay holds an EU adequacy decision confirming it provides adequate data-protection for transfers from the EU, since 21 August 2012 observed
  14. Probable Uniamos — URCDP Resolución N.8/026 — Convention 108+ model clauses (controller-controller, controller-processor, processor-processor modules) for international transfers lacking adequacy observed
  15. Probable KSandK — Uruguay — EU adequacy decision since 2012, the first Latin American country to do so observed
  16. Probable Primary statutory record — URCDP Resolución N° 8/2026 enables Convention 108+ Standard Contractual Clauses as a cross-border transfer mechanism, subject to URCDP's own assessment.
  17. Probable INPLP — Law No. 18,331 Art. 23 restricts international transfer to non-adequate jurisdictions, subject to URCDP authorisation. observed
  18. Probable Multilaw — URCDP Resolución No. 8/2026 (17 April 2026) adds Convention 108+ SCCs as an additional valid transfer mechanism. observed
  19. Probable Pandectes — Uruguay holds an EU adequacy decision from the European Commission. observed
  20. Probable Ferrere — URCDP Resolucion N 8/2026 — Enables use of Council of Europe Convention 108+ Standard Contractual Clauses (controller-to-controller, controller-to-processor, processor-to-processor modules) as an additional mechanism for international personal-data transfers, alongside the pre-existing Resolucion N 41/021 and RIPD Resolucion N 50/022 clauses; adoption does not exempt from the prior-authorisation requirement under Article 23. observed
  21. Probable Publications Office of the European Union — European Commission Implementing Decision 2012/484/EU — The Eastern Republic of Uruguay is recognised by the European Commission as ensuring an adequate level of protection for personal data transferred from the EU, for Article 25(2) of Directive 95/46/EC purposes. observed

#

This module carries no confirmed claims; all seven sub-modules are gaps requiring dedicated follow-up research against Uruguayan sectoral statutes.

Traffic-light rationale — RedThis module carries no confirmed claims; all seven sub-modules are gaps requiring dedicated follow-up research against Uruguayan sectoral statutes.

Sub-modules (7)

Financial sector overlayRed

No confirmed financial-sector DP overlay (e.g., banking-secrecy interaction with LPD) was located in this pass.

Health sector overlayRed

No health-sector-specific data protection overlay was confirmed in this pass.

Telecoms and eprivacyRed

No ePrivacy-equivalent telecoms/communications-specific regime was confirmed in this pass.

Employment dataRed

No employment-specific data protection code was confirmed in this pass.

Credit and scoringRed

No verified Uruguay-specific credit-reporting/scoring statute text (equivalent to positive/negative solvency-file regimes elsewhere in the region) was confirmed in this pass.

educationRed

No education-sector-specific data protection rules were confirmed in this pass.

insuranceRed

No insurance-sector-specific data protection rules were confirmed in this pass.

Category narrative 50 words

No sector-specific overlays (banking secrecy, health, telecoms/ePrivacy, employment, credit-scoring, education, insurance) displacing or supplementing the general LPD regime were independently confirmed for Uruguay within this research pass. Uruguay is known to have separate banking-secrecy legislation and consumer-credit-reporting practices, but verified statutory citations tying these to data-protection-specific carve-outs were not retrieved.

Sources and claims (1)
  1. Uncertain IAPP — EU Data Act (Regulation (EU) 2023/2854) — No Uruguayan instrument equivalent to the EU Data Act governing connected-product data access, B2B/B2G sharing, or cloud-switching was located observed

#

No confirmed sub-module claims; this is a genuine regulatory gap or an under-researched area requiring dedicated follow-up.

Traffic-light rationale — RedNo confirmed sub-module claims; this is a genuine regulatory gap or an under-researched area requiring dedicated follow-up.

Sub-modules (6)

Cookies and trackersRed

No Uruguay-specific cookie/tracker consent instrument was confirmed.

Claims (1):

  • No dedicated statutory cookie/tracker-consent provision distinct from Ley 18.331's general consent principle was located for Uruguay

Dark patternsRed

No dark-pattern prohibition specific to Uruguay's DP regime was confirmed.

Opt out signalsRed

No recognition of browser-level opt-out signals (e.g., GPC) was confirmed for Uruguay.

Clean rooms and dcrRed

No clean-room/data-collaboration-room rule specific to Uruguay was confirmed.

Cross context advertisingRed

No CPRA-style 'sale'/'share' cross-context advertising rule was confirmed for Uruguay.

Direct marketingAmber

General consent/purpose-limitation principles under the LPD would apply to direct marketing, but a dedicated direct-marketing consent/suppression regime was not confirmed.

Category narrative 44 words

No dedicated cookie/tracker consent regime, dark-pattern prohibition, opt-out signal recognition, clean-room rule, cross-context-advertising rule, or direct-marketing-specific suppression regime was independently confirmed for Uruguay in this research pass. General LPD consent and purpose-limitation principles would apply to commercial/marketing processing, but no adtech-specific instrument was located.

Sources and claims (1)
  1. Uncertain https://uniamos.com/blog/usar-ia-datos-clientes-uruguay-urcdp-ley-18331-2026 — No dedicated statutory cookie/tracker-consent provision distinct from Ley 18.331's general consent principle was located for Uruguay

#

One sub-module (state-surveillance carve-outs) is evidenced from primary-adjacent sources; the remaining five sub-modules are unconfirmed gaps.

Primary frameworkLaw No. 18.331 (LPD)
Traffic-light rationale — AmberOne sub-module (state-surveillance carve-outs) is evidenced from primary-adjacent sources; the remaining five sub-modules are unconfirmed gaps.

Sub-modules (6)

Profiling restrictionsRed

No Art-22-GDPR-analogue profiling restriction was confirmed for Uruguay in this pass.

Automated decision making transparencyRed

No ADM-transparency/explanation right specific to Uruguay was confirmed.

AI risk assessmentsRed

No AI-specific risk-assessment regime or general AI statute was confirmed for Uruguay.

Claims (3):

  • Ley N° 20.212 art. 74 — AGESIC must act jointly with URCDP on any AI strategy or project implicating personal-data processing; AI systems processing personal data subject to Ley 18.331/Decreto 64/020 general duties
  • Uploading client/employee personal data to a foreign-hosted AI model is treated as an international data transfer under Ley 18.331 art. 23, requiring contractual guarantees and URCDP assessment/authorisation.
  • Decreto 276/025 — AGESIC (jointly with URCDP for personal-data aspects) the task of designing and executing Uruguay's national AI and data strategy; a coordinative mandate, not a binding private-sector AI risk-assessment duty

Biometric regimeRed

No biometric-data-specific statute (facial recognition, fingerprint, gait) was confirmed for Uruguay in this pass.

Genetic dataRed

No genetic-data-specific regime was confirmed for Uruguay in this pass.

State surveillance carveoutsAmber

Databases for public security, defence, or state-security purposes fall outside the LPD's general scope.

Claims (2):

  • Law 18.331 excludes from its scope databases whose purpose is public security, defence or state security, subject to any specific regulating law.
  • Law No. 18.331 — international cooperation between intelligence agencies for combating organised crime, terrorism and drug trafficking from data-protection obligations
Category narrative 48 words

The LPD carves databases serving public-security, defence or state-security purposes out of its general scope, which functions as a state-surveillance carve-out subject to any specific regulating law. No Uruguay-specific profiling restriction, ADM-transparency right, AI-specific risk-assessment regime, biometric-specific statute, or genetic-data-specific regime was independently confirmed in this research pass.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (5)
  1. Confirmed International Association of Privacy Professionals — Law 18.331 excludes from its scope databases whose purpose is public security, defence or state security, subject to any specific regulating law. observed
  2. Uncertain Multilaw — Law No. 18.331 — international cooperation between intelligence agencies for combating organised crime, terrorism and drug trafficking from data-protection obligations observed
  3. Probable Lex Mundi — Ley N° 20.212 art. 74 — AGESIC must act jointly with URCDP on any AI strategy or project implicating personal-data processing; AI systems processing personal data subject to Ley 18.331/Decreto 64/020 general duties observed
  4. Probable https://uniamos.com/blog/usar-ia-datos-clientes-uruguay-urcdp-ley-18331-2026 — Uploading client/employee personal data to a foreign-hosted AI model is treated as an international data transfer under Ley 18.331 art. 23, requiring contractual guarantees and URCDP assessment/authorisation.
  5. Uncertain Regulations.ai — Decreto 276/025 — AGESIC (jointly with URCDP for personal-data aspects) the task of designing and executing Uruguay's national AI and data strategy; a coordinative mandate, not a binding private-sector AI risk-assessment duty observed

#

No confirmed UY-specific claims for any of the five sub-modules; this is either a genuine regime gap or requires dedicated primary-text research against LPD articles on minors.

Traffic-light rationale — RedNo confirmed UY-specific claims for any of the five sub-modules; this is either a genuine regime gap or requires dedicated primary-text research against LPD articles on minors.

Sub-modules (5)

Age verificationRed

No Uruguay-specific age-verification requirement was confirmed.

Minor profiling bansRed

No minor-specific profiling ban was confirmed for Uruguay.

Education settingsRed

No education-settings-specific children's-data rule was confirmed for Uruguay.

Dependent adultsRed

No dependent-adult (elderly, mentally incapacitated) data protection provision was confirmed for Uruguay.

Category narrative 53 words

No Uruguay-specific provisions on age of consent for data processing, parental-consent mechanisms, minor-profiling bans, education-settings-specific DP rules, or dependent-adult protections were independently confirmed in this research pass. Comparators from Spain (age 14 consent threshold under LOPDGDD) were located but are not applicable to the bound UY JID and are excluded per JID discipline.

Sources and claims (1)
  1. Uncertain IAPP — Uruguay data-protection regime — No dedicated statutory digital age-of-consent or parental-consent mechanism specific to data processing was located for Uruguay observed

#

Regulator powers and private right of action are well evidenced; enforcement-activity index, funding/capacity, collective redress and 180-day recent developments are unconfirmed gaps.

Primary frameworkLaw No. 18.331 (LPD) as implemented by Decree No. 64/020
Traffic-light rationale — AmberRegulator powers and private right of action are well evidenced; enforcement-activity index, funding/capacity, collective redress and 180-day recent developments are unconfirmed gaps.

Sub-modules (6)

Regulator powers and penaltiesGreen

URCDP may impose sanctions ranging from observations and warnings to database closure and fines for LPD non-compliance.

Claims (8):

  • Implementing decree provisions empower the URCDP to impose sanctions for non-compliance ranging from observations and warnings to closure of the database and the imposition of fines.
  • Ley 18.331 art. 35 — Sanction ladder from observación/apercibimiento through fines up to approximately 500,000 UI to court-ordered suspension and closure of the database
  • URCDP — warnings, fines, suspension of database operations, or closure of databases as administrative sanctions
  • URCDP — Observation, warning, fine up to 500,000 Unidades Indexadas, and suspension of a database for 5 days or judicial closure
  • Suspension of a database for 6 working days requires a jurisdictional (court) decision following AGESIC action on a reasoned URCDP resolution
  • URCDP categorises infractions into four severity bands under its Art. 35/34(B) sanctions powers.
  • Ley N 18.331, art. 35(3) — Maximum fine the URCDP may impose by law is 500,000 indexed units (UI).
  • URCDP's sanctioning powers include warning, fine up to 500,000 UI, suspension up to five business days, and judicial closure.

Enforcement activity indexAmber

URCDP has issued numerous guidance resolutions since 2017, but a quantified enforcement/fines activity index for the last 12 months was not located.

Claims (1):

  • The URCDP has issued a series of resolutions and guidance since 2017-2023 (de-identification guide, SCC guidance, adequacy resolutions) evidencing active regulatory/guidance output, though no comprehensive public enforcement-fine index was located in this research pass.

Regulator funding and capacityRed

No specific funding, budget or headcount figures for URCDP were confirmed in this pass.

Collective redress and class actionsRed

No collective-redress or class-action mechanism specific to LPD enforcement was confirmed in this pass.

Private right of actionGreen

Data subjects may pursue a judicial Habeas Data action to enforce their rights directly, independent of URCDP administrative process.

Claims (2):

  • Data subjects may pursue a judicial Habeas Data action as a private right of action to enforce their data protection rights, in addition to filing complaints with the URCDP.
  • Habeas data judicial action — a direct private right of court access alongside the URCDP administrative route

Recent developments 180dRed

No Uruguay-specific data-protection legislative, case-law, guidance, or adequacy development within the last 180 days (February-August 2026) was confirmed in this research pass.

Category narrative 85 words

URCDP holds a graduated sanctioning power ranging from observations and warnings through database closure and fines, set out in implementing decree provisions. Data subjects retain a private right of action via the judicial Habeas Data proceeding in addition to URCDP complaints. URCDP has been an active guidance-issuing body (de-identification guide 2017, SCC guidance 2021, adequacy resolutions 2021/2023), though a quantified 12-month enforcement/fines activity index, regulator funding/headcount figures, a collective-redress/class-action mechanism, and confirmed developments within the last 180 days were not located in this research pass.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (11)
  1. Confirmed International Association of Privacy Professionals — Implementing decree provisions empower the URCDP to impose sanctions for non-compliance ranging from observations and warnings to closure of the database and the imposition of fines. observed
  2. Confirmed International Association of Privacy Professionals — Data subjects may pursue a judicial Habeas Data action as a private right of action to enforce their data protection rights, in addition to filing complaints with the URCDP. observed
  3. Uncertain OneTrust DataGuidance — The URCDP has issued a series of resolutions and guidance since 2017-2023 (de-identification guide, SCC guidance, adequacy resolutions) evidencing active regulatory/guidance output, though no comprehensive public enforcement-fine index was located in this research pass. observed
  4. Probable Damian de Arce — Ley 18.331 art. 35 — Sanction ladder from observación/apercibimiento through fines up to approximately 500,000 UI to court-ordered suspension and closure of the database observed
  5. Probable DLA Piper — URCDP — warnings, fines, suspension of database operations, or closure of databases as administrative sanctions observed
  6. Probable INPLP — Habeas data judicial action — a direct private right of court access alongside the URCDP administrative route observed
  7. Disputed Damian de Arce — URCDP — Observation, warning, fine up to 500,000 Unidades Indexadas, and suspension of a database for 5 days or judicial closure observed
  8. Disputed URCDP — Suspension of a database for 6 working days requires a jurisdictional (court) decision following AGESIC action on a reasoned URCDP resolution observed
  9. Confirmed Primary statutory record — URCDP categorises infractions into four severity bands under its Art. 35/34(B) sanctions powers.
  10. Probable Portal 180 — Ley N 18.331, art. 35(3) — Maximum fine the URCDP may impose by law is 500,000 indexed units (UI). observed
  11. Probable Recording Law — URCDP's sanctioning powers include warning, fine up to 500,000 UI, suspension up to five business days, and judicial closure. observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

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

Audit trail

Machine checkChallenged on 24 Oct 2026: not settled (8 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsrestriction and objection
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacyadequacy granted
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacysccs and bcrs
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressregulator powers and penalties
Art. 79Enforcement & Redresscollective redress and class actions
Art. 80Enforcement & Redressregulator powers and penalties
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressprivate right of action
Art. 83Enforcement & Redresscollective redress and class actions
Art. 84Enforcement & Redressregulator powers and penalties