Data Protection Monitor
Global Privacy & Data Protection Intelligence

Dominican Republic Data Protection & Privacy Regulation

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

Last updated · 10 categories · 44 claims · 25 sources in the cumulative register

The Dominican Republic's data-protection landscape saw a notable, if aspirational, development this cycle: Agenda Digital 2030, a national digital-transformation policy framework, contemplates a comprehensive reform of the Data Protection Law, Ley 172-13.

Data collected Data published

AI-assembled from cited sources

Not covered: Lawful Processing & Special Data, Data Subject Rights, Cross-Border & Adequacy, Algorithmic, Biometric & Surveillance Governance, Children & Vulnerable Groups. Not fully checked this cycle: Regulator & Framework (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 3 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix43 claims · 22 sources · machine-compiled
4 Confirmed36 Probable3 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 lead brief

Latest update · 11 October 2026

Lead Signal

The Dominican Republic's data-protection enforcement posture has strengthened through the criminal law rather than through dedicated data-protection legislation. A new Dominican Penal Code establishes offences against the private information of individuals registered in catalogues, files or automated data systems, and extends potential liability to legal entities and corporations that collect or use personal data without express prior consent. This is understood to have taken effect around August 2026, though the exact article numbers and penalty figures have not been located. The development is structurally significant because it addresses a gap that the jurisdiction's principal data-protection instrument, Ley No. 172-13 of 2013, left open: that statute's data-protection provisions are oriented primarily toward credit-reporting and credit-history information sourced from regulated financial-intermediation entities, rather than toward general-purpose personal-data processing. Criminal exposure, including for corporate entities, now sits alongside that narrower civil and administrative regime.

Key regulatory facts for Dominican Republic
Key regulatory facts for Dominican Republic
Regulatory DimensionDominican Republic Standing Position
JurisdictionDominican Republic (DO)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 44 sourced findings)
Regulator & FrameworkA comprehensive statute exists and is in force, but institutional enforcement is fragmented and there is no dedicated supervisory authority, which weakens practical oversight.
Lawful Processing & Special DataCore consent and special-category concepts are present by general regional pattern but granular basis-by-basis detail is unverified from available sources.
Data Subject RightsCore ARCO-style rights are plausible under the habeas data framework but explicit textual confirmation of scope and deadlines is incomplete.
Controller/Processor DutiesA security principle exists (confirmed), but modern accountability tooling (DPIA/DPO/ROPA) and mandatory breach notification are absent, indicating a materially lighter-touch regime than GDPR-aligned jurisdictions.
Primary Instruments CitedPellerano Nadal Law & Consulting, DLA Piper Data Protection Laws of the World, Dominican Republic Official Instrument (ofar.com.do derecho-y-tecnologia-la-protecci), Oficina Nacional de Estadística (hosting primary text), Dirección General de Migración
Last Confirmed / Updated (25 sources in cumulative register)

#

A comprehensive statute exists and is in force, but institutional enforcement is fragmented and there is no dedicated supervisory authority, which weakens practical oversight.

Primary frameworkLaw No. 172-13 on the Comprehensive Protection of Personal Data (2013)
Traffic-light rationale — AmberA comprehensive statute exists and is in force, but institutional enforcement is fragmented and there is no dedicated supervisory authority, which weakens practical oversight.

Sub-modules (5)

Regulator and authorityAmber

No single dedicated DPA exists, but INDOTEL's supervisory role over regulated entities rests on a formal instrument (Resolution No. 055-06, Complementary Regulation to Law 126-02) granting inspection and sanctioning authority, not a purely informal arrangement; Pro Consumidor and the Superintendencia de Bancos exercise adjacent, non-exclusive oversight, and courts hear habeas data claims. Primary-instrument scope verification remains outstanding.

Claims (4):

  • The Dominican Republic has no single dedicated data protection authority; enforcement-adjacent functions are shared informally among INDOTEL, Pro Consumidor and sector regulators such as the Superintendencia de Bancos.
  • Ley No. 172-13 designates INDOTEL as responsible for supervising compliance and sanctioning violations, but this is an adjacent authority rooted in INDOTEL's telecoms mandate, not a dedicated general-purpose data-protection regulator.
  • Dominican Republic data-protection enforcement architecture — No dedicated data-protection supervisory authority exists in DO; enforcement of Ley 172-13 is minimal and dispersed across sectoral bodies (e.g. Superintendencia de Bancos for credit bureaus).
  • The Dominican Republic has no dedicated data-protection authority; INDOTEL's role is derivative of its telecoms mandate.

Act and instrumentsGreen

Law No. 172-13 (2013) is the principal comprehensive instrument governing personal data processing in archives, registries, databases and reporting systems, public or private.

Claims (5):

  • Law No. 172-13 (2013) is the Dominican Republic's principal comprehensive data protection statute.
  • Ley No. 172-13 sobre Protección de Datos Personales — Ley 172-13 regulates Sociedades de Información Crediticia (SIC), which per Article 30 require prior authorisation from the Junta Monetaria to provide credit-reference services.
  • New Dominican Penal Code — Offences against the private information of individuals registered in catalogues, files or automated data systems, with penalties extending to legal entities/corporations that collect or use personal data without express prior consent.
  • Ley 172-13 sobre Proteccion Integral de los Datos Personales — Ley 172-13 obliges any DO company collecting personal data via its website to clearly disclose its use, obtain the data subject's consent, keep the data secure, and allow access, rectification or deletion.
  • Dominican data-protection rights derive constitutional foundation from Article 44.

Material scopeGreen

The Law applies to personal data contained in archives, public registries, databases or other technical means of data processing used for reporting, whether held by public or private entities.

Claims (2):

  • Law 172-13 applies to personal data contained in archives, public registries, databases or other technical means of data processing used for reporting, whether public or private.
  • Ley 172-13 provides integral protection of personal data in files/registries intended to furnish reports, with machinery oriented to SICs.

Territorial scopeRed

No explicit extraterritorial-application clause analogous to GDPR Art. 3 has been identified in Law 172-13 from the sources reviewed.

Regulator registration and filingRed

No confirmed general controller-registration/filing obligation with a central authority was identified for Law 172-13 in the sources reviewed; this module element requires primary-text verification.

Category narrative 78 words

The Dominican Republic's data-protection regime rests on Law No. 172-13 (2013), a comprehensive statute covering personal data held in archives, public registries, databases and other technical processing means used for reporting purposes, whether public or private. Unlike GDPR-style regimes, the DR has no single dedicated data protection authority; enforcement responsibility is fragmented across INDOTEL (telecommunications regulator), Pro Consumidor (consumer protection body) and sectoral bodies such as the Superintendencia de Bancos, with ultimate recourse via judicial habeas data/amparo actions.

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

Sources and claims (11)
  1. Probable DataGuidance — The Dominican Republic has no single dedicated data protection authority; enforcement-adjacent functions are shared informally among INDOTEL, Pro Consumidor and sector regulators such as the Superintendencia de Bancos. observed
  2. Confirmed DataGuidance — Law No. 172-13 (2013) is the Dominican Republic's principal comprehensive data protection statute. observed
  3. Confirmed DataGuidance — Law 172-13 applies to personal data contained in archives, public registries, databases or other technical means of data processing used for reporting, whether public or private. observed
  4. Confirmed DLA Piper Data Protection Laws of the World — Ley No. 172-13 sobre Protección de Datos Personales — Ley 172-13 regulates Sociedades de Información Crediticia (SIC), which per Article 30 require prior authorisation from the Junta Monetaria to provide credit-reference services. observed
  5. Confirmed DLA Piper Data Protection Laws of the World — Ley 172-13 provides integral protection of personal data in files/registries intended to furnish reports, with machinery oriented to SICs. observed
  6. Probable Multilaw — New Dominican Penal Code — Offences against the private information of individuals registered in catalogues, files or automated data systems, with penalties extending to legal entities/corporations that collect or use personal data without express prior consent. observed
  7. Probable https://ofar.com.do/al-derecho/persona-familia-al-derecho/derecho-y-tecnologia-la-proteccion-de-datos-personales-en-la-republica-dominicana-2/ — Ley No. 172-13 designates INDOTEL as responsible for supervising compliance and sanctioning violations, but this is an adjacent authority rooted in INDOTEL's telecoms mandate, not a dedicated general-purpose data-protection regulator.
  8. Probable Multilaw — Dominican Republic data-protection enforcement architecture — No dedicated data-protection supervisory authority exists in DO; enforcement of Ley 172-13 is minimal and dispersed across sectoral bodies (e.g. Superintendencia de Bancos for credit bureaus). observed
  9. Probable DLA Piper Data Protection Laws of the World — Ley 172-13 sobre Proteccion Integral de los Datos Personales — Ley 172-13 obliges any DO company collecting personal data via its website to clearly disclose its use, obtain the data subject's consent, keep the data secure, and allow access, rectification or deletion. observed
  10. Probable Pellerano Nadal Law & Consulting — The Dominican Republic has no dedicated data-protection authority; INDOTEL's role is derivative of its telecoms mandate. observed
  11. Probable Pellerano Nadal Law & Consulting — Dominican data-protection rights derive constitutional foundation from Article 44. observed

#

Core consent and special-category concepts are present by general regional pattern but granular basis-by-basis detail is unverified from available sources.

Primary frameworkLaw No. 172-13 on the Comprehensive Protection of Personal Data (2013)
Traffic-light rationale — AmberCore consent and special-category concepts are present by general regional pattern but granular basis-by-basis detail is unverified from available sources.

Sub-modules (4)

Lawful basesAmber

Law 172-13 is understood to require a lawful basis (typically consent, legal obligation, or public-source data) for processing, consistent with regional habeas-data statutes, though an explicit enumerated list akin to GDPR Art. 6 was not directly confirmed in the sources reviewed.

Special categoriesAmber

Sensitive/special category data (health, ideology, sexual life, criminal record) is understood to receive heightened protection under Latin American habeas-data statutes of this era; specific DR statutory text confirming this was not directly retrieved in this run.

Claims (2):

  • Art. 75 restricts collection of sensitive data absent free, conscious and voluntary consent.
  • Ley 172-13 sobre Proteccion Integral de los Datos Personales — Ley 172-13 includes a category of especially-protected data (datos especialmente protegidos) subject to heightened treatment rules, per secondary legal commentary; the exact pinpoint article was not independently re-confirmed against the statute text this cycle.

Pseudonymisation and anonymisationRed

No pseudonymisation/anonymisation definitions or safe-harbour provisions were identified for Law 172-13 in the sources reviewed.

Category narrative 49 words

Law 172-13, as a habeas-data-style Latin American statute, embeds consent as the central lawful basis for processing, with heightened protection for sensitive/special categories of data. Detailed enumerated lawful bases equivalent to GDPR Art. 6, and formal pseudonymisation/anonymisation safe-harbours, were not confirmed in the sources reviewed and require primary-text verification.

Sources and claims (3)
  1. Probable Oficina Nacional de Estadística (hosting primary text) — Ley 172-13, Art. 30 — Regulates the provision of credit-reporting/credit-history information services sourced from regulated financial-intermediation entities and other economic agents. observed
  2. Confirmed Pellerano — Art. 75 restricts collection of sensitive data absent free, conscious and voluntary consent. observed
  3. Uncertain H&A — Ley 172-13 sobre Proteccion Integral de los Datos Personales — Ley 172-13 includes a category of especially-protected data (datos especialmente protegidos) subject to heightened treatment rules, per secondary legal commentary; the exact pinpoint article was not independently re-confirmed against the statute text this cycle. observed

#

Core ARCO-style rights are plausible under the habeas data framework but explicit textual confirmation of scope and deadlines is incomplete.

Primary frameworkLaw No. 172-13 on the Comprehensive Protection of Personal Data (2013)
Traffic-light rationale — AmberCore ARCO-style rights are plausible under the habeas data framework but explicit textual confirmation of scope and deadlines is incomplete.

Sub-modules (5)

Access rightAmber

A right of access to one's personal data is expected under the habeas-data constitutional tradition underlying Law 172-13; explicit statutory text was not directly retrieved this run.

Claims (2):

  • Ley 172-13, Art. 30(7) — Access, rectification, cancellation and opposition rights, requiring identification of the services/units before which they may be exercised; no statutory response deadline stated.
  • Ley 172-13 / Constitucion Art. 44 (habeas data) — Ley 172-13 recognises rights of access, rectification, updating and suppression, exercisable via the constitutional habeas data action grounded in Art. 44 on the right to privacy and honour.

Rectification and erasureAmber

Rectification/erasure rights are typical of habeas-data statutes in the region; independent confirmation of DR-specific statutory text was not obtained this run.

Claims (1):

  • Constitution of the Dominican Republic, Art. 44 — Every person has the right to decide on the use of data existing about them and their property, and may access it freely and demand its update, rectification or destruction.

Restriction and objectionRed

No confirmed statutory restriction-of-processing or objection/profiling opt-out mechanism was located for Law 172-13 in this run.

Data portabilityRed

No data portability right was identified in Law 172-13, consistent with it predating the GDPR-era portability concept (law enacted 2013).

Deadlines and response windowsRed

No confirmed statutory response-window/deadline for controller responses to data subject requests was located for Law 172-13 in this run.

Claims (1):

  • Dominican law gives data subjects a five-business-day response window for access/rectification/cancellation/opposition requests.
Category narrative 44 words

Law 172-13 is rooted in the constitutional habeas data tradition and is expected to afford data subjects access, rectification and objection-style rights; however, granular statutory deadlines, an explicit portability right, and a restriction-of-processing right were not independently confirmed in the sources retrieved this run.

Sources and claims (4)
  1. Confirmed Pellerano — Constitution of the Dominican Republic, Art. 44 — Every person has the right to decide on the use of data existing about them and their property, and may access it freely and demand its update, rectification or destruction. observed
  2. Probable Oficina Nacional de Estadística (hosting primary text) — Ley 172-13, Art. 30(7) — Access, rectification, cancellation and opposition rights, requiring identification of the services/units before which they may be exercised; no statutory response deadline stated. observed
  3. Probable H&A — Ley 172-13 / Constitucion Art. 44 (habeas data) — Ley 172-13 recognises rights of access, rectification, updating and suppression, exercisable via the constitutional habeas data action grounded in Art. 44 on the right to privacy and honour. observed
  4. Probable Dirección General de Migración — Dominican law gives data subjects a five-business-day response window for access/rectification/cancellation/opposition requests. observed

#

A security principle exists (confirmed), but modern accountability tooling (DPIA/DPO/ROPA) and mandatory breach notification are absent, indicating a materially lighter-touch regime than GDPR-aligned jurisdictions.

Primary frameworkLaw No. 172-13 on the Comprehensive Protection of Personal Data (2013)
Traffic-light rationale — AmberA security principle exists (confirmed), but modern accountability tooling (DPIA/DPO/ROPA) and mandatory breach notification are absent, indicating a materially lighter-touch regime than GDPR-aligned jurisdictions.

Sub-modules (7)

Accountability & DPIARed

No DPIA obligation or general accountability/documentation regime analogous to GDPR Art. 5/35 was identified for Law 172-13.

DPO requirementsRed

No statutory Data Protection Officer appointment threshold was identified for Law 172-13.

Ropa requirementsRed

No confirmed records-of-processing (ROPA) obligation was located for Law 172-13 in this run.

Joint controller arrangementsRed

No joint-controller framework analogous to GDPR Art. 26 was identified for Law 172-13.

Security measuresGreen

Law 172-13 establishes a security principle applicable to data controllers, requiring appropriate safeguards for personal data held in archives, registries and databases.

Claims (2):

  • Law 172-13 establishes a security principle applicable to data controllers with respect to personal data held in archives, registries and databases.
  • Companies managing customer databases in DO — Companies managing customer databases are legally required under Ley 172-13 to guarantee security, confidentiality and proper treatment of client data, adopting technical measures against alteration, loss or unauthorised access.

Breach notificationRed

Law 172-13 does not impose an obligation on controllers to notify data subjects or any administrative/judicial authority of a data breach; any such notice is voluntary and considered good practice rather than a legal duty.

Claims (5):

  • Law 172-13 does not impose an obligation on data controllers to notify a data breach to the data subject or to any administrative or judicial authority; notice is voluntary/best-practice only.
  • No statutory breach-notification duty exists; remedy runs through Ley 53-07 and habeas data.
  • Dominican data-protection framework — Ley 172-13 and Ley 53-07 provide criminal/civil remedies after a breach occurs (habeas data, high-technology-crimes law), but no instrument imposes a proactive breach-notification duty to a regulator or affected individuals.
  • Ley 172-13 — No general breach-notification regime for most sectors.
  • Dominican law imposes no proactive breach-notification duty on data controllers.

Retention and disposalRed

No confirmed statutory retention-limit or disposal-duty provision was located for Law 172-13 in this run.

Category narrative 52 words

Law 172-13 establishes a general security-of-processing principle for controllers but does not impose a breach-notification obligation to data subjects or authorities; breach notice is voluntary/best-practice only. DPIA, DPO, ROPA and joint-controller obligations analogous to GDPR were not confirmed in the sources reviewed and likely do not exist in the current 2013-era statute.

Sources and claims (7)
  1. Confirmed DataGuidance — Law 172-13 establishes a security principle applicable to data controllers with respect to personal data held in archives, registries and databases. observed
  2. Confirmed DataGuidance — Law 172-13 does not impose an obligation on data controllers to notify a data breach to the data subject or to any administrative or judicial authority; notice is voluntary/best-practice only. observed
  3. Probable Multilaw — No statutory breach-notification duty exists; remedy runs through Ley 53-07 and habeas data. observed
  4. Probable Hoy — Dominican data-protection framework — Ley 172-13 and Ley 53-07 provide criminal/civil remedies after a breach occurs (habeas data, high-technology-crimes law), but no instrument imposes a proactive breach-notification duty to a regulator or affected individuals. observed
  5. Probable Pellerano — Companies managing customer databases in DO — Companies managing customer databases are legally required under Ley 172-13 to guarantee security, confidentiality and proper treatment of client data, adopting technical measures against alteration, loss or unauthorised access. observed
  6. Probable DominicanLaw — Ley 172-13 — No general breach-notification regime for most sectors. observed
  7. Probable DominicanLaw — Dominican law imposes no proactive breach-notification duty on data controllers. observed

#

No confirmed transfer-mechanism framework, adequacy status, or localisation mandate was located; this is a genuine regulatory gap rather than an omission, consistent with the statute's 2013-era scope.

Primary frameworkLaw No. 172-13 on the Comprehensive Protection of Personal Data (2013)
Traffic-light rationale — RedNo confirmed transfer-mechanism framework, adequacy status, or localisation mandate was located; this is a genuine regulatory gap rather than an omission, consistent with the statute's 2013-era scope.

Sub-modules (6)

Transfer mechanismsRed

No specific cross-border data transfer mechanism (adequacy, SCCs, BCRs, derogations) was identified in Law 172-13.

Adequacy receivedRed

The Dominican Republic has not been identified as a recipient of an EU adequacy decision in the sources reviewed.

Claims (3):

  • Dominican Republic cross-border transfer regime — No EU adequacy decision exists for the Dominican Republic.
  • Dominican Republic cross-border data transfer regime — DO has no EU adequacy decision; Ley 172-13 restricts cross-border movement of personal data under conditions not independently re-verified against the statute text this cycle.
  • No EU adequacy decision exists for the Dominican Republic.

Adequacy grantedRed

No mechanism by which the Dominican Republic grants adequacy status to other jurisdictions was identified.

SCCs and BCRsRed

No SCC or BCR framework was identified under Law 172-13.

Transfer impact assessmentRed

No transfer impact assessment requirement was identified under Law 172-13.

Data localisationRed

No general data-localisation mandate was identified for personal data under Law 172-13; sector-specific banking-data location rules under the financial regulator were not independently confirmed in this run.

Category narrative 45 words

Law 172-13 predates the modern SCC/BCR/TIA transfer-mechanism architecture, and no confirmed cross-border transfer regime, adequacy decision (received or granted), or data-localisation mandate specific to general personal data was identified in the sources reviewed. The Dominican Republic does not appear on published EU adequacy decision lists.

Sources and claims (3)
  1. Probable INDOTEL — Dominican Republic cross-border transfer regime — No EU adequacy decision exists for the Dominican Republic. observed
  2. Uncertain Multilaw — Dominican Republic cross-border data transfer regime — DO has no EU adequacy decision; Ley 172-13 restricts cross-border movement of personal data under conditions not independently re-verified against the statute text this cycle. observed
  3. Confirmed Instituto Dominicano de las Telecomunicaciones (INDOTEL) — No EU adequacy decision exists for the Dominican Republic. observed

#

Financial and credit-reporting overlays are reasonably well evidenced; other sectoral overlays (health, employment, education, insurance) remain unconfirmed gaps.

Primary frameworkLaw No. 172-13 (2013); Monetary and Financial Law No. 183-02
Supervisory authoritySuperintendencia de Bancos de la República Dominicana
Traffic-light rationale — AmberFinancial and credit-reporting overlays are reasonably well evidenced; other sectoral overlays (health, employment, education, insurance) remain unconfirmed gaps.

Sub-modules (7)

Financial sector overlayAmber

Monetary and Financial Law No. 183-02 establishes the regulatory and institutional framework for the Dominican monetary and financial system, under which the Superintendencia de Bancos oversees confidentiality of banking-related personal/financial data.

Claims (2):

  • Monetary and Financial Law No. 183-02 establishes the regulatory and institutional framework for the Dominican monetary and financial system, under which banking-sector personal/financial data confidentiality is supervised.
  • Ley 172-13 Art. 30 conditions credit-reporting services on information sourced from regulated financial-intermediation entities, placing credit-bureau oversight functionally with the Superintendencia de Bancos.

Health sector overlayRed

No health-sector-specific data protection overlay was confirmed in the sources reviewed for this run.

Telecoms and eprivacyAmber

INDOTEL, the Dominican Telecommunications Institute, exercises a regulatory role touching on data/consumer protection in electronic commerce, evidenced by its joint 2019 e-commerce guidance with Pro Consumidor addressing personal and financial data safeguards for online consumers.

Claims (2):

  • INDOTEL and Pro Consumidor jointly released e-commerce guidance in November 2019 outlining best practices for consumers to protect personal and financial data and prevent data/identity theft in online transactions.
  • On 3 September 2026, INDOTEL made available for public consultation a draft General Telecommunications, Digital Infrastructure and Connectivity Law.

Employment dataRed

No employment-sector-specific data protection code was confirmed for the Dominican Republic in this run.

Credit and scoringAmber

Law 172-13's formal title references its application to databases used for reporting, indicating the statute's origins are closely tied to credit-bureau/credit-reporting data practices.

Claims (2):

  • Law 172-13's formal title covers databases used for reporting, indicating the statute's close historical linkage to credit-bureau/credit-reporting data practices.
  • Only Junta Monetaria-authorised SICs may provide credit-reporting services in the Dominican Republic.

educationRed

No education-sector-specific data protection rules were confirmed for the Dominican Republic in this run.

insuranceRed

No insurance-sector-specific data protection rules were confirmed for the Dominican Republic in this run.

Category narrative 66 words

The financial sector is overlaid by Monetary and Financial Law No. 183-02, which establishes the regulatory and institutional framework for the Dominican monetary and financial system including bank confidentiality obligations. Law 172-13's own title indicates a strong original focus on databases used for credit reporting. Telecommunications-related data practices intersect with INDOTEL's mandate. Health, employment, education and insurance sector-specific data overlays were not confirmed in this run.

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

Sources and claims (6)
  1. Probable DataGuidance (hosted translated primary text) — Monetary and Financial Law No. 183-02 establishes the regulatory and institutional framework for the Dominican monetary and financial system, under which banking-sector personal/financial data confidentiality is supervised. observed
  2. Confirmed DataGuidance — INDOTEL and Pro Consumidor jointly released e-commerce guidance in November 2019 outlining best practices for consumers to protect personal and financial data and prevent data/identity theft in online transactions. observed
  3. Confirmed DataGuidance — Law 172-13's formal title covers databases used for reporting, indicating the statute's close historical linkage to credit-bureau/credit-reporting data practices. observed
  4. Probable Oficina Nacional de Estadística (hosting primary text) — Ley 172-13 Art. 30 conditions credit-reporting services on information sourced from regulated financial-intermediation entities, placing credit-bureau oversight functionally with the Superintendencia de Bancos. observed
  5. Probable El Globo Independiente — On 3 September 2026, INDOTEL made available for public consultation a draft General Telecommunications, Digital Infrastructure and Connectivity Law. observed
  6. Probable Guzmán Ariza (DRLawyer) — Only Junta Monetaria-authorised SICs may provide credit-reporting services in the Dominican Republic. observed

#

No binding adtech-specific commercial privacy framework exists; only non-binding consumer guidance was located.

Traffic-light rationale — RedNo binding adtech-specific commercial privacy framework exists; only non-binding consumer guidance was located.

Sub-modules (6)

Cookies and trackersAmber

No binding cookie/tracker consent regime was identified; the 2019 INDOTEL/Pro Consumidor e-commerce guide recommends consumer awareness of supplier privacy policies but does not impose binding cookie-consent obligations.

Claims (1):

  • The 2019 INDOTEL/Pro Consumidor e-commerce guide recommends that consumers be informed about supplier privacy policies, but does not impose a binding cookie-consent obligation on businesses.

Dark patternsRed

No dark-pattern prohibition was identified for the Dominican Republic in this run.

Opt out signalsRed

No recognized opt-out signal framework (e.g. Global Privacy Control) was identified as legally recognized in the Dominican Republic.

Clean rooms and dcrRed

No clean-room/data-collaboration-room regulation was identified for the Dominican Republic in this run.

Cross context advertisingRed

No cross-context advertising / sale-or-share framework analogous to CPRA was identified for the Dominican Republic in this run.

Direct marketingRed

No direct-marketing-specific consent/suppression regime was confirmed for the Dominican Republic beyond the general consent principles implied by Law 172-13.

Category narrative 48 words

No ePrivacy-style cookie/tracker consent statute, dark-pattern prohibition, recognized opt-out signal framework, clean-room regime, or cross-context-advertising rule was identified for the Dominican Republic. The closest identified artifact is the 2019 joint INDOTEL/Pro Consumidor e-commerce guidance, which recommends consumer-facing privacy-policy awareness practices but is non-binding guidance rather than binding law.

Sources and claims (1)
  1. Probable DataGuidance — The 2019 INDOTEL/Pro Consumidor e-commerce guide recommends that consumers be informed about supplier privacy policies, but does not impose a binding cookie-consent obligation on businesses. observed

#

No sources located confirming any algorithmic, biometric, or AI-specific governance framework distinct from the general 2013 data protection statute.

Traffic-light rationale — AmberNo sources located confirming any algorithmic, biometric, or AI-specific governance framework distinct from the general 2013 data protection statute.

Sub-modules (6)

Profiling restrictionsRed

No profiling-restriction provision analogous to GDPR Art. 22 was identified for the Dominican Republic.

Automated decision making transparencyRed

No automated-decision-making transparency or explanation right was identified for the Dominican Republic.

AI risk assessmentsRed

No AI-specific risk-assessment law or state-level AI transparency mandate was identified for the Dominican Republic.

Claims (2):

  • Dominican Republic AI governance — No AI-specific statute is in force; AI is governed by the non-binding 2023 National AI Strategy, Ley 172-13, sectoral rules, and ordinary constitutional/administrative law.
  • Dominican Republic AI governance landscape — DO has no AI-specific law in force; AI deployments involving personal data are governed by Ley 172-13 and general constitutional/administrative law, per secondary legal-tech commentary.

Biometric regimeAmber

No dedicated biometric-data protection regime (facial recognition, fingerprint, gait) distinct from the general Law 172-13 framework was confirmed for the Dominican Republic in this run.

Genetic dataRed

No dedicated genetic-data regime was confirmed for the Dominican Republic; genetic data would likely fall under any general sensitive-category treatment of Law 172-13, which itself was not independently verified in this run.

State surveillance carveoutsRed

No codified state-surveillance carve-out or national-security exemption text was confirmed for Law 172-13 in this run.

Category narrative 43 words

No profiling-restriction, automated-decision-making transparency right, AI-specific risk-assessment regime, dedicated biometric-data regime, genetic-data regime, or codified state-surveillance carve-out was identified for the Dominican Republic in the sources reviewed. This is treated as a genuine regulatory gap for this module rather than a silent omission.

Sources and claims (2)
  1. Probable Levellers AI — Dominican Republic AI governance — No AI-specific statute is in force; AI is governed by the non-binding 2023 National AI Strategy, Ley 172-13, sectoral rules, and ordinary constitutional/administrative law. observed
  2. Probable Primary statutory record — Dominican Republic AI governance landscape — DO has no AI-specific law in force; AI deployments involving personal data are governed by Ley 172-13 and general constitutional/administrative law, per secondary legal-tech commentary.

#

No sources located confirming any children- or vulnerable-group-specific data protection provisions; genuine regulatory gap.

Traffic-light rationale — Not assessedNo sources located confirming any children- or vulnerable-group-specific data protection provisions; genuine regulatory gap.

Sub-modules (5)

Age verificationRed

No statutory age-of-consent threshold for data processing was identified for the Dominican Republic.

Minor profiling bansRed

No minor-profiling ban was identified for the Dominican Republic.

Education settingsRed

No education-setting-specific data protection rule was identified for the Dominican Republic.

Dependent adultsRed

No dependent-adult (elderly/incapacitated) data protection provision was identified for the Dominican Republic.

Category narrative 30 words

No age-of-consent threshold, parental-consent mechanism (COPPA/GDPR Art. 8 analogue), minor-profiling ban, education-setting-specific rule, or dependent-adult protection provision was identified for the Dominican Republic's data protection framework in the sources reviewed.

#

A private judicial right of action exists, but there is no confirmed administrative penalty regime, enforcement activity index, or regulator capacity data, and no material recent developments were found.

Primary frameworkLaw No. 172-13 on the Comprehensive Protection of Personal Data (2013)
Traffic-light rationale — AmberA private judicial right of action exists, but there is no confirmed administrative penalty regime, enforcement activity index, or regulator capacity data, and no material recent developments were found.

Sub-modules (6)

Regulator powers and penaltiesAmber

No confirmed administrative investigative or fining power vested in a single DP regulator was identified for the Dominican Republic; redress instead runs through civil courts.

Claims (3):

  • No single Dominican data protection regulator holds administrative investigative or fining powers over Law 172-13 violations comparable to GDPR-style DPAs; redress instead runs through civil courts.
  • Ley 172-13, Art. 30(2) — Administrative sanctions may be imposed for violations of established rules; specific fine-maximum figure not located this cycle.
  • The Superintendencia de Bancos sanctions SIC breaches under Art. 81 and supervises SICs under Art. 36 of Ley 172-13.

Enforcement activity indexRed

No significant recent enforcement decisions or fines specific to Law 172-13 were identified in the sources reviewed for the last 12 months.

Regulator funding and capacityRed

No funding or headcount data is applicable given the absence of a dedicated DPA; this is a structural gap rather than an omission.

Collective redress and class actionsRed

No confirmed collective-redress or class-action mechanism specific to data protection violations was identified for the Dominican Republic in this run; Pro Consumidor's general consumer-complaint/conciliation channel was noted but not confirmed as DP-specific.

Private right of actionGreen

Data subjects whose rights are violated under Law 172-13, including in connection with a data breach, may bring a direct civil suit against the liable party, since the Law does not channel redress exclusively through an administrative regulator.

Claims (3):

  • Data subjects whose rights are violated due to a data breach may sue the liable person directly, since Law 172-13 does not channel breach-related redress exclusively through an administrative authority.
  • Constitutional habeas data action — The habeas data route is frequently the effective practical remedy for data-protection violations, given INDOTEL's limited general-processing supervisory and enforcement footprint.
  • Habeas data is the primary enforcement/redress route in absence of a dedicated DPA.

Recent developments 180dRed

No material Dominican Republic-specific data protection legislative, regulatory, or case-law developments were identified within the 180 days preceding this run (searches for a new DR data protection bill, dedicated DPA creation, or amendments in 2025-2026 returned no confirming results).

Claims (1):

  • Agenda Digital 2030 proposes a series of reforms supporting digital transformation, among which it contemplates a comprehensive reform of the Data Protection Law in the Dominican Republic.
Category narrative 66 words

Law 172-13 does not establish an administrative-fine regime comparable to GDPR; redress is primarily judicial. Data subjects whose rights are violated (including via a data breach) may sue the liable party directly through civil/habeas-data litigation, rather than through an empowered administrative regulator issuing penalties. No significant recent DR-specific data protection enforcement actions or legislative developments were identified within the last 180 days of the run date.

Periodic update · new data 2026-11-11

Enforcement and redress in the Dominican Republic's data-protection framework now operates across three channels. Ley 172-13, Article 30(2), empowers administrative sanctions for violations of established rules, a confirmed power, though the specific maximum fine figure has not been located. Separately, the constitutional habeas data action is understood to function, in practice, as the more frequently effective remedy for data-protection violations, a role that has grown in practical importance precisely because INDOTEL's general-processing supervisory and enforcement footprint under Ley 172-13 is limited relative to a dedicated data-protection authority. This means that an individual seeking redress for a data-protection violation in the Dominican Republic is, as a practical matter, often better served by the constitutional habeas data route than by a complaint to INDOTEL under the statutory administrative-sanctions power.

The third and newest channel is the Penal Code's criminal offence regime, understood to have taken effect around August 2026, which extends liability — including to legal entities and corporations — for unauthorised collection or use of personal data registered in catalogues, files or automated data systems. This materially expands the enforcement perimeter beyond Ley 172-13's civil and administrative remedies, introducing criminal exposure where previously only administrative sanctions and the habeas data constitutional route were available. The precise article numbers and penalty figures for this new criminal exposure have not yet been located, which limits assessment of how severe or how readily invoked this new channel will be in practice. </br> Taken together, these three channels — administrative sanctions under Ley 172-13, the habeas data constitutional remedy, and the new Penal Code criminal offences — now constitute a materially more layered enforcement and redress landscape than existed before the Penal Code development, even though the DNFBP-style dedicated regulatory capacity associated with a standalone data-protection authority is still absent.

Outlook

The principal item to watch is confirmation of the Penal Code's exact article numbers, penalty figures, and any early indication of how prosecutorial authorities intend to apply the new offences in practice, since this would determine whether the criminal channel becomes a materially used enforcement route or remains a largely dormant statutory addition alongside the already-established administrative and habeas data channels.

1 earlier distinct update
Periodic update · new data 2026-10-11

Enforcement and redress in the Dominican Republic's data-protection framework now operates across three channels. Ley 172-13, Article 30(2), empowers administrative sanctions for violations of established rules, a confirmed power, though the specific maximum fine figure has not been located this cycle. Separately, the constitutional habeas data action is understood to function, in practice, as the more frequently effective remedy for data-protection violations, a role that has grown in practical importance precisely because INDOTEL's general-processing supervisory and enforcement footprint under Ley 172-13 is limited relative to a dedicated data-protection authority. This means that an individual seeking redress for a data-protection violation in the Dominican Republic is, as a practical matter, often better served by the constitutional habeas data route than by a complaint to INDOTEL under the statutory administrative-sanctions power.

The third and newest channel is the Penal Code's criminal offence regime, understood to have taken effect around August 2026, which extends liability — including to legal entities and corporations — for unauthorised collection or use of personal data registered in catalogues, files or automated data systems. This materially expands the enforcement perimeter beyond Ley 172-13's civil and administrative remedies, introducing criminal exposure where previously only administrative sanctions and the habeas data constitutional route were available. The precise article numbers and penalty figures for this new criminal exposure have not yet been located, which limits assessment of how severe or how readily invoked this new channel will be in practice. </br> Taken together, these three channels — administrative sanctions under Ley 172-13, the habeas data constitutional remedy, and the new Penal Code criminal offences — now constitute a materially more layered enforcement and redress landscape than existed before the Penal Code development, even though the DNFBP-style dedicated regulatory capacity associated with a standalone data-protection authority is still absent.

Outlook

The principal item to watch is confirmation of the Penal Code's exact article numbers, penalty figures, and any early indication of how prosecutorial authorities intend to apply the new offences in practice, since this would determine whether the criminal channel becomes a materially used enforcement route or remains a largely dormant statutory addition alongside the already-established administrative and habeas data channels.

Sources and claims (7)
  1. Probable DataGuidance — No single Dominican data protection regulator holds administrative investigative or fining powers over Law 172-13 violations comparable to GDPR-style DPAs; redress instead runs through civil courts. observed
  2. Confirmed DataGuidance — Data subjects whose rights are violated due to a data breach may sue the liable person directly, since Law 172-13 does not channel breach-related redress exclusively through an administrative authority. observed
  3. Uncertain Multilaw — Agenda Digital 2030 proposes a series of reforms supporting digital transformation, among which it contemplates a comprehensive reform of the Data Protection Law in the Dominican Republic. observed
  4. Probable Oficina Nacional de Estadística (hosting primary text) — Ley 172-13, Art. 30(2) — Administrative sanctions may be imposed for violations of established rules; specific fine-maximum figure not located this cycle. observed
  5. Probable OFAR — Constitutional habeas data action — The habeas data route is frequently the effective practical remedy for data-protection violations, given INDOTEL's limited general-processing supervisory and enforcement footprint. observed
  6. Confirmed Pellerano — Habeas data is the primary enforcement/redress route in absence of a dedicated DPA. observed
  7. Probable Guzmán Ariza (DRLawyer) — The Superintendencia de Bancos sanctions SIC breaches under Art. 81 and supervises SICs under Art. 36 of Ley 172-13. 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), 44 claim(s) (44 category placement(s)), 25 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: upheld (4 confirmed against the cited source; 10 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 Rightsrectification and erasure
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 & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacytransfer impact assessment
Art. 49Cross-Border & Adequacytransfer mechanisms
Art. 77Enforcement & Redressregulator powers and penalties
Art. 78Enforcement & Redressregulator powers and penalties
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressprivate right of action
Art. 82Enforcement & Redressregulator powers and penalties
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties