Data Protection Monitor
Global Privacy & Data Protection Intelligence

Not every instrument is backed by its official text yet. At least one law or rulebook covered here has no official source (tier 1) retrieved for it yet. No finding on this page is shown with confidence above “Probable” until stronger sources are retrieved.

Curaçao Data Protection & Privacy Regulation

CW schema gdpri-v2 trajectory: not yet assessed in transition overlaps: Sentinel (AML/CFT), World Payments

Last updated · 10 categories · 42 claims · 30 sources in the cumulative register

Reports suggest the Curaçao Data Protection Board is not currently operational as the statutory supervisory authority under Ordinance No.

Data collected Data published

AI-assembled from cited sources

Not covered: Data Subject Rights, AdTech & Commercial Privacy, Algorithmic, Biometric & Surveillance Governance, Children & Vulnerable Groups. Not fully checked this cycle: Enforcement & Redress (1 open gap).

Framework & posture10 of 10 modules active
10 active · 5 binding instruments
Next milestoneNo upcoming dated milestone on record
Record & confidence mix52 claims · 29 sources · machine-compiled
33 Probable1 Indicative8 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 · 8 November 2026

Lead Signal

An official Dutch government parliamentary document, dated 14 October 2026, states that Curacao's statutory data protection oversight committee, the College bescherming persoonsgegevens, established under Article 42 of the National Ordinance Personal Data Protection (LBP), remains in oprichting, meaning it is still in the process of being established rather than fully operational. The same document records that Curacao's Council of Ministers received a briefing on that date outlining possible legislative scenarios for implementing the Council of Europe's Convention 108+ in domestic law. No preferred scenario and no submission date to Parliament were announced at that briefing, so the pathway from the current ordinance to a Convention 108+-aligned framework remains at an early, scenario-selection stage rather than a committed legislative timeline.

Key regulatory facts for Curaçao
Key regulatory facts for Curaçao
Regulatory DimensionCuraçao Standing Position
JurisdictionCuraçao (CW)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 42 sourced findings)
Regulator & FrameworkA comprehensive-looking statute exists and is in force, but the absence of an operational supervisory authority and of registration/notification machinery materially weakens practical enforceability.
Lawful Processing & Special DataCoverage gap: no verified sub-module-level detail located for this jurisdiction in this pass; only a general 'modeled on Dutch law' inference is available.
Data Subject RightsNo verified sub-module-level claims located for CW in this pass.
Controller/Processor DutiesTwo concrete, confirmed negative findings (no DPO duty, no breach-notification duty) are informative but the remaining sub-modules are unverified gaps.
Primary Instruments CitedOverheid.nl (official Dutch Kingdom local-regulation database), Curaçao Official Instrument (dlapiperdataprotection.com t-law-c-CW), HBN Law & Tax, Curaçao Official Instrument (curacaochronicle.com curacao-government-examines-new-), Curaçao Official Instrument (lexmundi.com curacao)
Last Confirmed / Updated (30 sources in cumulative register)

#

A comprehensive-looking statute exists and is in force, but the absence of an operational supervisory authority and of registration/notification machinery materially weakens practical enforceability.

Primary frameworkOrdinance No. 84 of 4 September 2010 Laying Down Rules on the Protection of Personal Data (Landsverordening bescherming persoonsgegevens / Data Protection Ordinance)
Supervisory authorityData Protection Board (Curaçao) — provided for by statute but not yet established
Traffic-light rationale — AmberA comprehensive-looking statute exists and is in force, but the absence of an operational supervisory authority and of registration/notification machinery materially weakens practical enforceability.

Sub-modules (5)

Regulator and authorityRed

The Ordinance provides for a Data Protection Board to act as supervisory authority; as of this research pass, that Board has not yet been established, leaving the regime without an operational regulator.

Claims (3):

  • Data Protection Board (Curaçao) is reported to be not currently operational as the statutory supervisory authority under Ordinance No. 84 of 2010. CHALLENGER FOLD (f-001, add_caveat/overstated_confidence): downgraded confidence Probable->Uncertain. Contradicting T4 sources (HBN Law & Tax 2023-02-02; LawGratis 2025-04-12; Neeyamo; Artemis Qualified eLearning) report the Board was established in January 2022 and remained at least nominally operational, with a 2023 government open-records reply indicating members subsequently resigned and seats went unfilled. Correct framing is 'established 2022, lapsed ~2023', not 'never established'.
  • College bescherming persoonsgegevens — Landsverordening bescherming persoonsgegevens Art. 41
  • College bescherming persoonsgegevens — The dedicated oversight committee established under Art. 42 of the National Ordinance Personal Data Protection is reported, in an official Dutch government parliamentary document, as currently 'in oprichting' (in the process of being established) rather than fully operational.

Act and instrumentsAmber

The operative instrument is Ordinance No. 84 of 4 September 2010, described by professional legal-research sources as modeled on the Dutch data-protection implementing act.

Claims (4):

  • Ordinance No. 84 of 4 September 2010 is reported to be modeled on the Dutch data-protection implementing act structure. Single-T2-source characterization; underlying Dutch-language statute text not independently parsed this cycle.
  • Curacao Council of Ministers — possible legislative approaches to implementing Council of Europe Convention 108+
  • Landsverordening bescherming persoonsgegevens (A.B. 2010 no. 84) — 2013-10-01
  • Curacao Council of Ministers — On 14 October 2026 the Council of Ministers received a presentation outlining possible legislative scenarios for implementing the Council of Europe's Convention 108+ in Curacao; no preferred scenario or submission date to Parliament was announced as of that presentation.

Material scopeAmber

The Ordinance is reported to follow the structure of the Dutch implementing act (itself derived from the pre-GDPR EU data protection directive framework), covering automated and structured-file processing of personal data, but the precise scope articles were not independently retrieved in this pass.

Claims (2):

  • Ordinance No. 84 of 4 September 2010 covers automated and structured-file processing of personal data, per the pre-GDPR EU data protection directive-era structure inherited via the Dutch implementing act. Scope articles not independently retrieved; inference from secondary summary only.
  • Landsverordening bescherming persoonsgegevens (LBP) — wholly or partly automated processing of personal data, and non-automated processing forming part of a filing system, including by a controller with no Curacao establishment using means located in Curacao (unless used only for transit)

Territorial scopeRed

No CW-specific provision on extraterritorial application to non-established controllers was located in this research pass.

Claims (2):

  • National Ordinance Personal Data Protection (LBP) — The LBP applies to the processing of personal data in the context of activities of an establishment of a responsible party in Curacao.
  • Landsverordening bescherming persoonsgegevens (LBP) — Controller with no Curacao establishment using means located in Curacao must designate a local representative person or body acting on its behalf, who is then treated as the controller

Regulator registration and filingAmber

The Ordinance does not set out requirements for data processing notifications to a supervisory authority.

Claims (2):

  • Ordinance No. 84 of 4 September 2010 does not set out requirements for data-processing notifications/filings to a supervisory authority. Negative finding (absence of registration/filing machinery) reported by DataGuidance.
  • National Ordinance Personal Data Protection (PB 2010 no. 84) — The Ordinance sets out no data-processing notification, DPO-appointment, or registration/filing requirement.
Category narrative 88 words

Curaçao's data protection regime rests on a single omnibus-style statute — Ordinance No. 84 of 4 September 2010 Laying Down Rules on the Protection of Personal Data — but the supervisory authority the Ordinance itself creates, the Data Protection Board, has never been stood up. This is the textbook 'statute enacted, DPA not operational' pattern: the law is in force, yet there is no functioning regulator to receive filings, hear complaints, or issue guidance. Registration/notification duties, DPO appointment duties and breach-notification duties are all absent from the text.

Periodic update · new data 2026-11-08

Curacao's data protection architecture continues to rest on the National Ordinance Personal Data Protection (LBP), originally enacted in 2010, with its dedicated independent oversight body, the College bescherming persoonsgegevens, established on paper under Article 42 of that ordinance but reported, in an official Dutch government parliamentary document dated 14 October 2026, as still in oprichting. That characterisation means the committee is in the process of being established rather than fully operational, a status that has persisted long enough to be worth stating plainly: the ordinance names a supervisory body that the most recent available official record does not describe as functioning.

Against that backdrop, the Council of Ministers received a presentation on the same date, 14 October 2026, setting out possible legislative approaches to implementing the Council of Europe's Convention 108+ in Curacao. The briefing appears to have been exploratory: no preferred legislative scenario was named, and no date for submission of a Bill to Parliament was announced. This places the prospect of a materially stronger framework, one that could plausibly also resolve the oversight committee's unsettled status, at an early stage where the legislative vehicle and timeline are both still undetermined.

The LBP's current territorial scope is also worth noting as context for how broadly its existing (if incompletely supervised) obligations reach. The ordinance applies to the processing of personal data carried out in the context of the activities of an establishment of a responsible party in Curacao, a scope formulation consistent with pre-GDPR European data protection drafting of the period in which it was enacted.

The practical significance of the committee's unresolved status is that Curacao currently operates a data protection law with a named, but not yet functioning, enforcement and policy body. Any assessment of obligations under the LBP, whether by a responsible party assessing its own compliance posture or by an outside party assessing regulatory risk in dealing with Curacao-based entities, should treat the absence of a fully established oversight authority as a live structural fact, not a historical footnote expected to resolve imminently. The Convention 108+ briefing indicates the government's own attention is directed at a more comprehensive fix rather than at accelerating the existing committee's establishment in isolation.

Outlook

The marker to watch is whether the Council of Ministers moves from scenario presentation to selection of a specific legislative approach for Convention 108+ implementation, a step that the available record suggests could occur as scheduled around the second quarter of 2027. Until a scenario is chosen and a legislative vehicle identified, the operational status of the College bescherming persoonsgegevens remains the clearest open question in Curacao's data protection architecture, and any claim that it has become fully operational should be checked against a dated primary source rather than assumed from the passage of time.

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

Curacao's data-protection framework rests on the Landsverordening bescherming persoonsgegevens, a national ordinance in force since 1 October 2013, which designates the College bescherming persoonsgegevens as the supervisory body under its Article 41. No primary-source confirmation that this body is operationally independent and institutionalised as a dedicated data-protection authority has been identified, a gap that is directly relevant to the external criticism described below.

The principal development is procedural rather than legislative: Curacao's Council of Ministers received a presentation on 14 October 2026, prepared by an inter-ministerial working group, setting out possible legislative approaches to implementing Council of Europe Convention 108+ domestically. This is understood to be a preparatory step only. No bill text has been produced, and no firm timetable for any future legislation exists at this stage. The presentation should be read as evidence that the question of modernising Curacao's data-protection framework is now before the government at a decision-making level, not as evidence that reform has been enacted or is imminent on any confirmed date.

This development sits alongside, and plausibly responds to, the Dutch Data Protection Authority's public warning that Curacao's system for protecting personal data falls significantly short of international and EU-equivalent standards and lacks effective independent oversight. The timing, a formal warning from the Kingdom's own data-protection authority followed within months by a Council of Ministers presentation on Convention 108+ approaches, suggests at minimum that external pressure is a live input into Curacao's domestic legislative agenda, though the presentation itself does not confirm that any specific reform will follow or on what basis.

The practical effect of the developments is to leave the existing 2010/2013 ordinance as the operative law, unchanged, while formally opening a legislative-reform track whose outcome and timetable are both currently unknown.

Outlook

The next concrete marker will be whether the Council of Ministers' consideration of Convention 108+ approaches advances to an actual legislative proposal, and if so, on what timetable. Given the presentation is described as addressing possible approaches rather than a specific drafted instrument, a bill introduction in the near term should not be assumed. A second marker is whether any statement from Curacao's government directly addresses the Dutch AP's independence and oversight-capacity criticism, which the Convention 108+ presentation does not appear to have done directly.

Periodic update · new data 2026-10-04

Curacao's sole data-protection instrument is the National Ordinance Personal Data Protection (Landsverordening Bescherming Persoonsgegevens, PB 2010 no. 84), which entered into force in September 2010. The Ordinance is modelled on the Dutch GDPR-era implementing act and is closely aligned with its principles, including concepts such as a broad definition of personal data, but it is a wholly separate legal instrument from the EU General Data Protection Regulation and has not been updated to incorporate the GDPR's later-generation obligations, such as mandatory breach notification or data-protection-officer appointment.

The most significant finding concerning the framework's institutional structure is that the Data Protection Board, provided for under Article 42 of the Ordinance as the body intended to supervise compliance, is understood not to have been established as an operational independent supervisory authority. The date on which this institutional gap might be resolved, or whether the Board has ever been operational at any point since 2010, was not established this cycle. This leaves open a foundational question about how the Ordinance's substantive provisions, including lawful-processing requirements, security-measures duties, and data-subject access rights, are supervised and enforced in practice, independent of the content of those substantive rules themselves.

Separately, the Ordinance contains no data-processing notification, filing, or registration requirement of the kind found in many GDPR-adjacent regimes, meaning controllers operating in Curacao face no equivalent of a notification-to-regulator step before beginning processing activity. No more recent amending instrument to the Ordinance beyond its original 2010 enactment was located this cycle.

Outlook

Confirmation of whether and when the Data Protection Board has been or will be operationalised is the central open question for this module. Its resolution would clarify whether Curacao's data-protection framework currently operates with functioning independent supervision or principally as an unenforced statutory text pending institutional follow-through.

Sources and claims (14)
  1. Uncertain DataGuidance — Data Protection Board (Curaçao) is reported to be not currently operational as the statutory supervisory authority under Ordinance No. 84 of 2010. CHALLENGER FOLD (f-001, add_caveat/overstated_confidence): downgraded confidence Probable->Uncertain. Contradicting T4 sources (HBN Law & Tax 2023-02-02; LawGratis 2025-04-12; Neeyamo; Artemis Qualified eLearning) report the Board was established in January 2022 and remained at least nominally operational, with a 2023 government open-records reply indicating members subsequently resigned and seats went unfilled. Correct framing is 'established 2022, lapsed ~2023', not 'never established'. observed
  2. Probable DataGuidance — Ordinance No. 84 of 4 September 2010 is reported to be modeled on the Dutch data-protection implementing act structure. Single-T2-source characterization; underlying Dutch-language statute text not independently parsed this cycle. observed
  3. Uncertain DataGuidance — Ordinance No. 84 of 4 September 2010 covers automated and structured-file processing of personal data, per the pre-GDPR EU data protection directive-era structure inherited via the Dutch implementing act. Scope articles not independently retrieved; inference from secondary summary only. observed
  4. Probable DataGuidance — Ordinance No. 84 of 4 September 2010 does not set out requirements for data-processing notifications/filings to a supervisory authority. Negative finding (absence of registration/filing machinery) reported by DataGuidance. observed
  5. Probable https://www.curacaochronicle.com/post/unknown/curacao-government-examines-new-legislation-to-strengthen-personal-data-protection — Curacao Council of Ministers — possible legislative approaches to implementing Council of Europe Convention 108+
  6. Probable Dutch Government (Rijksoverheid) — College bescherming persoonsgegevens — Landsverordening bescherming persoonsgegevens Art. 41 observed
  7. Probable Dutch Government (Rijksoverheid) — Landsverordening bescherming persoonsgegevens (A.B. 2010 no. 84) — 2013-10-01 observed
  8. Probable https://www.lexmundi.com/guides/data-privacy-guide/jurisdictions/caribbean/curacao/ — National Ordinance Personal Data Protection (PB 2010 no. 84) — The Ordinance sets out no data-processing notification, DPO-appointment, or registration/filing requirement.
  9. Probable Primary statutory record — Curacao Council of Ministers — Briefing on Convention 108+ implementation scenarios, 14 October 2026.
  10. Probable Dutch Government (Rijksoverheid) — College bescherming persoonsgegevens — The dedicated oversight committee established under Art. 42 of the National Ordinance Personal Data Protection is reported, in an official Dutch government parliamentary document, as currently 'in oprichting' (in the process of being established) rather than fully operational. observed
  11. Probable https://www.lexmundi.com/guides/data-privacy-guide/jurisdictions/caribbean/curacao/ — National Ordinance Personal Data Protection (LBP) — The LBP applies to the processing of personal data in the context of activities of an establishment of a responsible party in Curacao.
  12. Probable Curacao Chronicle — Curacao Council of Ministers — On 14 October 2026 the Council of Ministers received a presentation outlining possible legislative scenarios for implementing the Council of Europe's Convention 108+ in Curacao; no preferred scenario or submission date to Parliament was announced as of that presentation. observed
  13. Probable Overheid.nl (official Dutch Kingdom local-regulation database) — Landsverordening bescherming persoonsgegevens (LBP) — wholly or partly automated processing of personal data, and non-automated processing forming part of a filing system, including by a controller with no Curacao establishment using means located in Curacao (unless used only for transit) observed
  14. Probable Caribbean Credit Bureau — Landsverordening bescherming persoonsgegevens (LBP) — Controller with no Curacao establishment using means located in Curacao must designate a local representative person or body acting on its behalf, who is then treated as the controller observed

#

Coverage gap: no verified sub-module-level detail located for this jurisdiction in this pass; only a general 'modeled on Dutch law' inference is available.

Primary frameworkOrdinance No. 84 of 4 September 2010 Laying Down Rules on the Protection of Personal Data
Traffic-light rationale — RedCoverage gap: no verified sub-module-level detail located for this jurisdiction in this pass; only a general 'modeled on Dutch law' inference is available.

Sub-modules (4)

Lawful basesRed

Not independently verified for Curaçao in this pass; the Ordinance is reported to be modeled on the Dutch implementing act.

Claims (1):

  • Ordinance No. 84 of 4 September 2010 is inferred (unverified) to follow the Dutch implementing act's lawful-basis structure. No Curaçao-specific enumerated lawful-basis text independently verified this cycle; purely a lineage inference.

Special categoriesRed

No Curaçao-specific special-category (sensitive data) provisions were retrieved in this pass.

Pseudonymisation and anonymisationRed

No Curaçao-specific pseudonymisation/anonymisation safe-harbour text was retrieved.

Category narrative 65 words

No Curaçao-specific text on enumerated lawful bases, consent thresholds, special-category rules, or pseudonymisation/anonymisation safe-harbours was retrieved in this research pass. Professional summaries indicate the Ordinance follows the Dutch implementing-act model (itself derived from the EU data protection directive era), which would imply an analogous lawful-basis and sensitive-data structure, but this was not independently verified against the Curaçao statutory text, which is only available in Dutch.

No periodic updates recorded in this cycle

Sources and claims (1)
  1. Speculative DataGuidance — Ordinance No. 84 of 4 September 2010 is inferred (unverified) to follow the Dutch implementing act's lawful-basis structure. No Curaçao-specific enumerated lawful-basis text independently verified this cycle; purely a lineage inference. observed

#

No verified sub-module-level claims located for CW in this pass.

Primary frameworkOrdinance No. 84 of 4 September 2010 Laying Down Rules on the Protection of Personal Data
Traffic-light rationale — RedNo verified sub-module-level claims located for CW in this pass.

Sub-modules (5)

Access rightRed

Not independently verified for CW in this pass.

Claims (1):

  • Landsverordening bescherming persoonsgegevens (LBP) — Data subject may request confirmation in writing within four weeks whether their personal data are being processed

Rectification and erasureRed

Not independently verified for CW in this pass.

Restriction and objectionRed

Not independently verified for CW in this pass.

Data portabilityRed

Not independently verified for CW in this pass; the source statute predates the GDPR-era portability right by design lineage.

Deadlines and response windowsRed

Not independently verified for CW in this pass.

Category narrative 30 words

No Curaçao-specific detail on access, rectification/erasure, restriction/objection, portability, or statutory response deadlines was retrieved in this research pass; the underlying Ordinance text is Dutch-only and was not independently parsed article-by-article.

Sources and claims (1)
  1. Probable The Information Collective — Landsverordening bescherming persoonsgegevens (LBP) — Data subject may request confirmation in writing within four weeks whether their personal data are being processed observed

#

Two concrete, confirmed negative findings (no DPO duty, no breach-notification duty) are informative but the remaining sub-modules are unverified gaps.

Primary frameworkOrdinance No. 84 of 4 September 2010 Laying Down Rules on the Protection of Personal Data
Supervisory authorityData Protection Board (Curaçao) — not yet established
Traffic-light rationale — AmberTwo concrete, confirmed negative findings (no DPO duty, no breach-notification duty) are informative but the remaining sub-modules are unverified gaps.

Sub-modules (7)

Accountability & DPIARed

No Curaçao-specific DPIA-trigger text was retrieved.

Claims (1):

  • National Ordinance Personal Data Protection (LBP) — The LBP (2010/consolidated 2013) does not provide for mandatory Data Protection Officers or Data Protection Impact Assessments, per secondary legal commentary.

DPO requirementsAmber

The Ordinance does not set out requirements for DPO appointments.

Claims (2):

  • Ordinance No. 84 of 4 September 2010 does not set out requirements for DPO appointments. Confirmed negative finding per professional legal-research source.
  • College bescherming persoonsgegevens (CBP) — No general registration of personal-data processing with the CBP is required; the LBP contains no clauses on registration/filing with any public agency and does not mandate a data protection officer

Ropa requirementsRed

No Curaçao-specific ROPA obligation text was retrieved.

Joint controller arrangementsRed

No Curaçao-specific joint-controller provisions were retrieved.

Security measuresRed

No Curaçao-specific technical/organisational security-measures text was independently retrieved.

Claims (1):

  • Landsverordening bescherming persoonsgegevens (LBP) — Controller must implement appropriate technical and organisational measures to secure personal data against loss or unlawful processing

Breach notificationAmber

The Ordinance does not set out requirements for data breach notification, to either the (non-existent) supervisory authority or affected data subjects.

Claims (4):

  • Ordinance No. 84 of 4 September 2010 does not set out requirements for data breach notification to a supervisory authority or affected data subjects. Confirmed negative finding per professional legal-research source; compounded by non-operational regulator (CLM-CW-019) which would in any case receive no such notification.
  • National Ordinance Personal Data Protection — No statutory breach-notification duty (to a regulator or to affected data subjects), threshold, or deadline analogous to GDPR Arts 33-34 was located under the 2010 Ordinance, and no Personal Data Protection Committee response to the 2026 CGA licensing-portal breach was identified.
  • National Ordinance Personal Data Protection (PB 2010 no. 84) — The National Ordinance Personal Data Protection does not provide for any notification requirement for incidents and/or data breaches, nor for mandatory DPO appointment.
  • Landsverordening bescherming persoonsgegevens — general personal-data breach-notification duty to regulator or affected individuals

Retention and disposalRed

No Curaçao-specific retention-limit or disposal-duty text was retrieved.

Category narrative 30 words

Professional legal-research sources are explicit that the Curaçao Ordinance does not set out DPO-appointment requirements or data-breach-notification requirements. Accountability/DPIA, ROPA, joint-controller, general security-measures and retention/disposal specifics were not independently retrieved.

Periodic update · new data 2026-10-18

The standing statutory duty on controllers, termed responsible parties under the 2010 National Ordinance Personal Data Protection, is set out at Article 13: a responsible party must execute appropriate technical and organizational measures to secure personal data against loss or any form of unlawful processing, with the level of security guaranteed calibrated to the state of the art, cost of execution, and the risks associated with the processing. This duty is confirmed and unchanged this cycle. What is new, and material, is what appears absent around it. The breach of the Curacao Gaming Authority's online licensing portal, confirmed by the CGA on 7 October 2026, exposed approximately 40,000 documents covering beneficial-ownership and identification data for nearly 650 licensed companies. No statutory breach-notification duty to a regulator or to affected data subjects, of the kind found in GDPR Articles 33 and 34, has been located under the 2010 Ordinance, and no response from the Personal Data Protection Committee to this breach has been identified. These two findings together describe a controller-duties landscape with a security-measures obligation on paper but no confirmed notification mechanism or regulatory follow-through observed in this specific instance.

Outlook

Whether the Personal Data Protection Committee responds to the CGA breach, and whether any notification duty is identified on fuller review of the Ordinance's primary text, are the two open questions carried forward from this cycle.

Sources and claims (8)
  1. Probable DataGuidance — Ordinance No. 84 of 4 September 2010 does not set out requirements for DPO appointments. Confirmed negative finding per professional legal-research source. observed
  2. Probable DataGuidance — Ordinance No. 84 of 4 September 2010 does not set out requirements for data breach notification to a supervisory authority or affected data subjects. Confirmed negative finding per professional legal-research source; compounded by non-operational regulator (CLM-CW-019) which would in any case receive no such notification. observed
  3. Uncertain https://www.dlapiperdataprotection.com/?t=law&c=CW — National Ordinance Personal Data Protection — No statutory breach-notification duty (to a regulator or to affected data subjects), threshold, or deadline analogous to GDPR Arts 33-34 was located under the 2010 Ordinance, and no Personal Data Protection Committee response to the 2026 CGA licensing-portal breach was identified.
  4. Probable https://www.lexmundi.com/guides/data-privacy-guide/jurisdictions/caribbean/curacao/ — National Ordinance Personal Data Protection (PB 2010 no. 84) — The National Ordinance Personal Data Protection does not provide for any notification requirement for incidents and/or data breaches, nor for mandatory DPO appointment.
  5. Probable Licentium — Landsverordening bescherming persoonsgegevens — general personal-data breach-notification duty to regulator or affected individuals observed
  6. Probable Licentium — National Ordinance Personal Data Protection (LBP) — The LBP (2010/consolidated 2013) does not provide for mandatory Data Protection Officers or Data Protection Impact Assessments, per secondary legal commentary. observed
  7. Probable DLA Piper — College bescherming persoonsgegevens (CBP) — No general registration of personal-data processing with the CBP is required; the LBP contains no clauses on registration/filing with any public agency and does not mandate a data protection officer observed
  8. Probable DLA Piper — Landsverordening bescherming persoonsgegevens (LBP) — Controller must implement appropriate technical and organisational measures to secure personal data against loss or unlawful processing observed

#

The core adequacy-based transfer restriction is confirmed and binding; downstream transfer-mechanism detail (SCCs, BCRs, TIA, localisation) is an unverified gap.

Primary frameworkOrdinance No. 84 of 4 September 2010 Laying Down Rules on the Protection of Personal Data
Supervisory authorityData Protection Board (Curaçao) — not yet established
Traffic-light rationale — AmberThe core adequacy-based transfer restriction is confirmed and binding; downstream transfer-mechanism detail (SCCs, BCRs, TIA, localisation) is an unverified gap.

Sub-modules (6)

Transfer mechanismsAmber

The Ordinance regulates international data transfers and limits transfers to countries providing adequate protection of personal data.

Claims (5):

  • Ordinance No. 84 of 4 September 2010 restricts cross-border transfer of personal data to countries not assessed as providing adequate protection. Single T2 anchor only; not elevated to Confirmed per two-anchor rule.
  • National Ordinance Personal Data Protection (PB 2010 no. 84) — The Ordinance regulates international transfers of personal data and limits transfers to countries providing an adequate level of protection of personal data.
  • Dutch Data Protection Authority — Curacao's data-protection oversight falls short of EU-equivalent standards; Kingdom parliamentarians warn divergent legislation could restrict cross-border law-enforcement data-sharing absent Convention 108+ harmonisation.
  • National Ordinance Personal Data Protection (LBP) — Personal data may be transferred to another country only if that country guarantees an appropriate level of protection; the Ordinance's explanatory memorandum sets out reference points for assessing that adequacy.
  • Landsverordening bescherming persoonsgegevens (LBP) — Personal data may only be transferred to another country if that country guarantees an adequate level of protection, subject to derogations under Art 52

Adequacy receivedRed

No adequacy decision received by Curaçao from another regime (e.g., EU/UK) was located.

Claims (1):

  • Autoriteit Persoonsgegevens (Netherlands) — The Dutch data protection authority has publicly stated that Curacao, Aruba and Sint Maarten provide a lower level of data protection than exists under European Dutch legislation and lack effective independent supervisory enforcement, creating legal sensitivity around intra-Kingdom personal-data transfers pending Convention 108+ implementation.

Adequacy grantedRed

No formal Curaçao-granted adequacy determination toward other regimes was located.

SCCs and BCRsRed

No Curaçao-specific SCC/BCR forms or uptake data were located.

Transfer impact assessmentRed

No formal TIA requirement was located for Curaçao.

Data localisationRed

No data-localisation mandate was located for Curaçao.

Category narrative 44 words

The Ordinance affirmatively regulates cross-border transfers, restricting transfer of personal data to countries assessed as providing adequate protection. No confirmed adequacy decisions received from or granted to other regimes, SCC/BCR uptake, formal TIA requirement, or data-localisation mandate were located for Curaçao in this pass.

No periodic updates recorded in this cycle

Sources and claims (6)
  1. Probable DataGuidance — Ordinance No. 84 of 4 September 2010 restricts cross-border transfer of personal data to countries not assessed as providing adequate protection. Single T2 anchor only; not elevated to Confirmed per two-anchor rule. observed
  2. Probable Dutch Government (Rijksoverheid) — National Ordinance Personal Data Protection (PB 2010 no. 84) — The Ordinance regulates international transfers of personal data and limits transfers to countries providing an adequate level of protection of personal data. observed
  3. Probable https://coincub.com/blog/curacao-gaming-license/ — Dutch Data Protection Authority — Curacao's data-protection oversight falls short of EU-equivalent standards; Kingdom parliamentarians warn divergent legislation could restrict cross-border law-enforcement data-sharing absent Convention 108+ harmonisation.
  4. Probable https://www.lexmundi.com/guides/data-privacy-guide/jurisdictions/caribbean/curacao/ — National Ordinance Personal Data Protection (LBP) — Personal data may be transferred to another country only if that country guarantees an appropriate level of protection; the Ordinance's explanatory memorandum sets out reference points for assessing that adequacy.
  5. Probable https://www.curacaochronicle.com/post/unknown/dutch-privacy-authority-warns-curacao-lacks-effective-data-protection-oversight — Autoriteit Persoonsgegevens (Netherlands) — The Dutch data protection authority has publicly stated that Curacao, Aruba and Sint Maarten provide a lower level of data protection than exists under European Dutch legislation and lack effective independent supervisory enforcement, creating legal sensitivity around intra-Kingdom personal-data transfers pending Convention 108+ implementation.
  6. Probable Caribbean Credit Bureau — Landsverordening bescherming persoonsgegevens (LBP) — Personal data may only be transferred to another country if that country guarantees an adequate level of protection, subject to derogations under Art 52 observed

#

One confirmed financial-sector/AML-adjacent finding; remaining sectoral sub-modules are unverified gaps.

Primary frameworkOrdinance No. 84 of 4 September 2010 Laying Down Rules on the Protection of Personal Data
Traffic-light rationale — AmberOne confirmed financial-sector/AML-adjacent finding; remaining sectoral sub-modules are unverified gaps.

Sub-modules (7)

Financial sector overlayAmber

Curaçao is a CFATF member but is viewed as having limited effective AML and tax-enforcement measures, which bears on financial-sector data-sharing and due-diligence obligations.

Claims (1):

  • Curaçao is a member of the Caribbean Financial Action Task Force (CFATF), viewed by international supervisory bodies as having limited effective AML/tax-enforcement measures, bearing on financial-sector data-sharing and due-diligence practices. General AML-posture characterization, not tied to a specific retrieved URL this cycle; flagged cross-monitor to financial-integrity. No source_url populated — see absent_field_provenance.

Health sector overlayRed

No CW-specific health-sector DP overlay was located.

Telecoms and eprivacyRed

No CW-specific telecoms/ePrivacy overlay was located.

Employment dataRed

No CW-specific employment-data overlay was located.

Credit and scoringRed

No CW-specific credit-scoring overlay was located.

educationRed

No CW-specific education-sector overlay was located.

insuranceRed

No CW-specific insurance-sector overlay was located.

Category narrative 52 words

Curaçao is a member of the Caribbean Financial Action Task Force (CFATF) and is viewed by international supervisory bodies as having limited effective AML/tax-enforcement measures, a fact relevant to financial-sector data-sharing and customer due-diligence practices. No CW-specific health, telecoms/ePrivacy, employment, credit-scoring, education, or insurance sector DP overlays were located in this pass.

No periodic updates recorded in this cycle

Sources and claims (1)
  1. Uncertain Primary statutory record — Curaçao is a member of the Caribbean Financial Action Task Force (CFATF), viewed by international supervisory bodies as having limited effective AML/tax-enforcement measures, bearing on financial-sector data-sharing and due-diligence practices. General AML-posture characterization, not tied to a specific retrieved URL this cycle; flagged cross-monitor to financial-integrity. No Source url populated — see absent_field_provenance.

#

No sub-module findings located; comprehensive gap for this module in this jurisdiction.

Traffic-light rationale — Not assessedNo sub-module findings located; comprehensive gap for this module in this jurisdiction.

Sub-modules (6)

Cookies and trackersRed

No CW-specific cookie/tracker regime located.

Dark patternsRed

No CW-specific dark-pattern prohibition located.

Opt out signalsRed

No CW-specific opt-out signal recognition (e.g., GPC) located.

Clean rooms and dcrRed

No CW-specific clean-room/data-collaboration rules located.

Cross context advertisingRed

No CW-specific cross-context-advertising ('sale'/'share') rule located.

Direct marketingRed

No CW-specific direct-marketing consent/suppression rule located.

Category narrative 23 words

No Curaçao-specific cookie/tracker consent regime, dark-pattern prohibition, opt-out-signal recognition, clean-room rules, cross-context-advertising rules, or direct-marketing consent/suppression rules were located in this research pass.

#

No sub-module findings located; comprehensive gap for this module in this jurisdiction.

Traffic-light rationale — RedNo sub-module findings located; comprehensive gap for this module in this jurisdiction.

Sub-modules (6)

Profiling restrictionsRed

No CW-specific profiling-restriction rule located.

Automated decision making transparencyRed

No CW-specific ADM-transparency rule located.

AI risk assessmentsRed

No CW-specific AI-risk-assessment regime located.

Biometric regimeRed

No CW-specific biometric-data regime located.

Genetic dataRed

No CW-specific genetic-data regime located.

State surveillance carveoutsRed

No CW-specific state-surveillance carve-out text located.

Claims (1):

  • Curacao Gaming Authority (CGA) — Unauthorised access to the CGA's online licensing portal between December 2025 and September 2026 exposed confidential ownership/UBO and licensing data of LOK licensees; the CGA permanently discontinued the portal, launched a temporary in-house replacement, commissioned an independent forensic investigation, and filed criminal complaints in Curacao, Germany and the Netherlands.
Category narrative 16 words

No Curaçao-specific profiling-restriction, ADM-transparency, AI-risk-assessment, biometric-regime, genetic-data-regime, or state-surveillance-carveout text was located in this research pass.

No periodic updates recorded in this cycle

Sources and claims (1)
  1. Probable Gamblingclub.be — Curacao Gaming Authority (CGA) — Unauthorised access to the CGA's online licensing portal between December 2025 and September 2026 exposed confidential ownership/UBO and licensing data of LOK licensees; the CGA permanently discontinued the portal, launched a temporary in-house replacement, commissioned an independent forensic investigation, and filed criminal complaints in Curacao, Germany and the Netherlands. observed

#

No sub-module findings located; comprehensive gap for this module in this jurisdiction.

Traffic-light rationale — Not assessedNo sub-module findings located; comprehensive gap for this module in this jurisdiction.

Sub-modules (5)

Age verificationRed

No CW-specific age-verification rule located.

Minor profiling bansRed

No CW-specific minor-profiling ban located.

Education settingsRed

No CW-specific education-setting DP rule located.

Dependent adultsRed

No CW-specific dependent-adult protection rule located.

Category narrative 18 words

No Curaçao-specific age-of-consent, parental-consent mechanism, minor-profiling ban, education-setting rule, or dependent-adult protection was located in this research pass.

#

No operational regulator and no confirmed enforcement track record under the Ordinance.

Primary frameworkOrdinance No. 84 of 4 September 2010 Laying Down Rules on the Protection of Personal Data
Supervisory authorityData Protection Board (Curaçao) — not yet established
Traffic-light rationale — RedNo operational regulator and no confirmed enforcement track record under the Ordinance.

Sub-modules (6)

Regulator powers and penaltiesRed

No dedicated DP regulator is currently exercising investigative or enforcement powers, as the Data Protection Board has never been established.

Claims (5):

  • Curaçao Data Protection Board is reported to not currently be exercising investigative or enforcement powers under the Data Protection Ordinance. CHALLENGER FOLD (f-001, add_caveat/overstated_confidence): downgraded confidence Probable->Uncertain. Same establishment-then-lapse caveat as CLM-CW-019 applies — a Board that existed 2022-c.2023 with vacant seats since is a different enforcement-capacity picture than a Board that was never constituted.
  • Personal Data Protection Committee (CBP) — The CBP's enforcement powers include issuing warnings, ordering corrective measures and imposing administrative fines that can reach up to XCG 10,000 per violation.
  • Landsverordening bescherming persoonsgegevens — administrative fines up to NAf./Cg 10,000 (Art. 54); criminal offence up to 6 months' imprisonment for intentional breach (Art. 63)
  • National Ordinance Personal Data Protection (LBP) — Secondary commentary reports the LBP's current maximum statutory penalty at NAf 10,000, described as low by comparison to GDPR-model fine structures.
  • College bescherming persoonsgegevens (CBP) — Administrative fine of at most XCG 10,000 per breach of Art 4(3), 27, 28 or 64(1) LBP; potential criminal prosecution up to 6 months imprisonment for intentional breach

Enforcement activity indexRed

No confirmed DP-specific enforcement action under the Ordinance was located in the last 12 months.

Claims (2):

  • Personal Data Protection Committee — As of the most recent available legal guide, no local key decisions applying the Personal Data Protection Ordinance were known to the contributing firm.
  • Curacao Gaming Authority licensing portal — The September-October 2026 CGA licensing-portal breach exposed personal and confidential information (including Personal History Disclosure Forms, passports and tax returns of UBOs, directors, trustees, financiers and key persons of licensed operators); no LBP data-protection-authority enforcement response to this incident was identified this cycle.

Regulator funding and capacityRed

No funding/headcount data exists for a body that has not been established.

Claims (3):

  • Dutch Data Protection Authority (Autoriteit Persoonsgegevens) — Curacao's system for protecting personal data falls significantly short of international/EU-equivalent standards and lacks effective independent oversight
  • Dutch Data Protection Authority (Autoriteit Persoonsgegevens) — Curacao's data protection oversight framework is a lower-protection patchwork lacking effective independent oversight, with enforcement effectively non-existent; AP intends to intensify supervision of international data flows to Curacao
  • College bescherming persoonsgegevens (CBP) / Personal Data Protection Board — Board established January 2022 but, per a 2025 law-firm note, not yet actively supervising compliance with the LBP even though complaints can already be lodged

Collective redress and class actionsRed

No CW-specific collective-redress or class-action mechanism for data-protection claims was located.

Private right of actionRed

No CW-specific private-right-of-action provision was located.

Recent developments 180dRed

No new legislation, case law, guidance, or adequacy determination affecting Curaçao's data-protection regime was identified in the 180 days preceding this run.

Category narrative 84 words

Because the Data Protection Board provided for under the Ordinance has never been established, there is no dedicated data-protection regulator currently exercising investigative or enforcement powers under the Curaçao Data Protection Ordinance. No confirmed DP-specific enforcement activity, regulator funding/capacity data, collective-redress mechanism, private-right-of-action, or 180-day development was located for this jurisdiction. A 2021-dated Public Prosecutor penalty item surfaced in search but its substantive connection to the Data Protection Ordinance could not be confirmed from available content, so it was not cited as a claim.

Periodic update · new data 2026-11-08

Secondary legal commentary reports the LBP's current maximum statutory penalty at NAf 10,000, a figure not independently verified against the gazetted ordinance text and described in that commentary as low when compared against fine structures modelled on the EU General Data Protection Regulation. Taken on its own terms, a capped penalty of that order sets a materially different deterrence profile than the percentage-of-turnover fine structures used in larger comparator regimes, though the figure should be treated as reported rather than confirmed pending direct verification against the ordinance itself.

That penalty structure takes on more immediate significance in light of a breach event affecting Curacao's licensed gambling sector. Between September and October 2026, a breach of the Curacao Gaming Authority's licensing portal exposed personal and confidential information belonging to the beneficial owners, directors, trustees, financiers and other key persons of licensed gambling operators, including Personal History Disclosure Forms, passport copies and tax returns. No enforcement or supervisory response to this incident by an LBP data protection authority has been identified. The absence of an identified response is itself a data point: it is consistent with, though not conclusively explained by, the committee's still-unestablished operational status described elsewhere in this framework, since a committee that is not yet fully functioning is poorly placed to open and conclude an enforcement inquiry regardless of the severity of the underlying incident.

No prior enforcement precedent under the LBP has been identified, meaning this breach would, if it does eventually draw a formal regulatory response, represent new enforcement ground for the ordinance rather than the continuation of an established practice. That absence of precedent is worth stating directly as a gap in the public record rather than inferred to mean enforcement has never occurred.

Outlook

The marker to watch is whether any enforcement or supervisory response to the gaming-portal breach materialises, whether from the College bescherming persoonsgegevens once it becomes operational or through some interim mechanism. Given the sensitivity of the exposed material, passport and tax documentation tied to the beneficial ownership of a large regulated licensee population, a continued absence of any identified regulatory response over the coming months would itself be a significant data point about the practical reach of Curacao's enforcement framework, independent of whatever the eventual statutory penalty structure turns out to be once the NAf 10,000 figure is confirmed against primary legislative text.

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

Curacao's data-protection ordinance provides for administrative fines of up to NAf./Cg 10,000 under Article 54, alongside a criminal offence carrying up to six months imprisonment for intentional breach under Article 63. These penalty levels are unchanged and represent the standing enforcement architecture under the 2010/2013 statute.

The more significant development in this domain is not a change to the penalty provisions themselves but the Dutch Data Protection Authority's explicit characterisation of Curacao's oversight capacity as lacking. The Dutch AP has warned that Curacao's system for protecting personal data falls significantly short of international and EU-equivalent standards and lacks effective independent oversight. Read against the modest administrative-fine ceiling and the absence of any confirmed general breach-notification duty, this criticism suggests the enforcement and redress architecture available under the current ordinance may be under-resourced relative to the scale and sensitivity of personal data now processed in and through Curacao, though no primary-source information on actual enforcement activity, case volumes, or the supervisory body's budget or staffing has been identified to confirm this directly.

This criticism arrives in the same period as a separate, though unconnected within this domain, demonstration of oversight-capacity strain: a prolonged unauthorised-access incident at a Curacao sector regulator's licensing system. While that incident falls outside this module's scope and is addressed elsewhere, its timing lends some concrete texture to the Dutch AP's otherwise general warning about oversight adequacy.

Outlook

The principal marker to watch is whether Curacao's government responds formally to the Dutch AP's criticism, whether through the Convention 108+ legislative track or through some other confirmation of the College bescherming persoonsgegevens' resourcing and independence. Absent such a response, the existing fine and criminal-penalty framework, together with an unconfirmed supervisory-independence status, remains the operative enforcement picture.

Periodic update · new data 2026-10-18

The most significant data-protection-relevant development of the past 180 days for Curacao is the absence of an enforcement or redress response, not its presence. The Personal Data Protection Committee, Curacao's designated data-protection authority under Article 42 of the 2010 National Ordinance Personal Data Protection, has not been identified as having issued any statement, opened any investigation, or taken any enforcement step in response to the Curacao Gaming Authority's licensing-portal breach, which exposed roughly 40,000 documents including ownership and identity data for nearly 650 licensed companies. Separately, as of the most recent available legal guide reviewed, no local key decisions applying the Personal Data Protection Ordinance were known to the contributing firm, a finding that reflects the absence of a known enforcement record as of that source's publication date rather than a confirmed current-state absence. Taken together, these findings reinforce a standing concern that Curacao's data-protection regulator has not demonstrated confirmed independent institutional enforcement capacity, a concern now sharpened by its apparent non-engagement with a breach of significant scale.

Outlook

The item to watch is whether the Personal Data Protection Committee breaks its apparent silence on the CGA breach. Continued non-engagement would further reinforce the standing capacity concern; any public statement or investigation would be the first identified enforcement-adjacent activity from the Committee in the material reviewed.

Sources and claims (10)
  1. Uncertain DataGuidance — Curaçao Data Protection Board is reported to not currently be exercising investigative or enforcement powers under the Data Protection Ordinance. CHALLENGER FOLD (f-001, add_caveat/overstated_confidence): downgraded confidence Probable->Uncertain. Same establishment-then-lapse caveat as CLM-CW-019 applies — a Board that existed 2022-c.2023 with vacant seats since is a different enforcement-capacity picture than a Board that was never constituted. observed
  2. Probable ConsentStack — Personal Data Protection Committee (CBP) — The CBP's enforcement powers include issuing warnings, ordering corrective measures and imposing administrative fines that can reach up to XCG 10,000 per violation. observed
  3. Uncertain https://www.lexmundi.com/guides/data-privacy-guide/jurisdictions/caribbean/curacao/ — Personal Data Protection Committee — As of the most recent available legal guide, no local key decisions applying the Personal Data Protection Ordinance were known to the contributing firm.
  4. Probable Licentium — Landsverordening bescherming persoonsgegevens — administrative fines up to NAf./Cg 10,000 (Art. 54); criminal offence up to 6 months' imprisonment for intentional breach (Art. 63) observed
  5. Probable Primary statutory record — Dutch Data Protection Authority (Autoriteit Persoonsgegevens) — Curacao's system for protecting personal data falls significantly short of international/EU-equivalent standards and lacks effective independent oversight
  6. Uncertain ConsentStack — National Ordinance Personal Data Protection (LBP) — Secondary commentary reports the LBP's current maximum statutory penalty at NAf 10,000, described as low by comparison to GDPR-model fine structures. observed
  7. Probable LegalBison — Curacao Gaming Authority licensing portal — The September-October 2026 CGA licensing-portal breach exposed personal and confidential information (including Personal History Disclosure Forms, passports and tax returns of UBOs, directors, trustees, financiers and key persons of licensed operators); no LBP data-protection-authority enforcement response to this incident was identified this cycle. observed
  8. Probable Curacao Chronicle — Dutch Data Protection Authority (Autoriteit Persoonsgegevens) — Curacao's data protection oversight framework is a lower-protection patchwork lacking effective independent oversight, with enforcement effectively non-existent; AP intends to intensify supervision of international data flows to Curacao observed
  9. Probable College bescherming persoonsgegevens (CBP) Curacao — College bescherming persoonsgegevens (CBP) — Administrative fine of at most XCG 10,000 per breach of Art 4(3), 27, 28 or 64(1) LBP; potential criminal prosecution up to 6 months imprisonment for intentional breach observed
  10. Uncertain HBN Law & Tax — College bescherming persoonsgegevens (CBP) / Personal Data Protection Board — Board established January 2022 but, per a 2025 law-firm note, not yet actively supervising compliance with the LBP even though complaints can already be lodged 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), 42 claim(s) (42 category placement(s)), 30 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 17 Nov 2026: upheld (16 confirmed against the cited source; 20 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 (14 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. 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. 35Controller/Processor Dutiesaccountability and dpia
Art. 13-22Data Subject Rightsaccess right
Art. 32-34Controller/Processor Dutiessecurity measures
Art. 37-39Controller/Processor Dutiesdpo requirements
Art. 44-49Cross-Border & Adequacytransfer mechanisms
Art. 77-84Enforcement & Redressregulator powers and penalties