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.

Delaware, USA Data Protection & Privacy Regulation

US-DE schema gdpri-v2 trajectory: not yet assessed hybrid regime overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 98 claims · 53 sources in the cumulative register

Governor Matt Meyer signed HB380 and HB381 on September 2, 2026, in what the Governor's office describes as creating the broadest data protections in the country.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Children & Vulnerable Groups, Enforcement & Redress (3 open gaps).

Framework & posture10 of 10 modules active
10 active · 7 binding instruments
Supervisory authorityDelaware Attorney General
Next milestone
JAN12027
HB 380 DPDPA amendments take effect
Record & confidence mix97 claims · 50 sources · machine-compiled
86 Probable11 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

United States federal law that applies in Delaware, USA is covered once, on the United States page. This page covers Delaware, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 8 November 2026

Lead Signal

Delaware has signed a two-bill package that materially tightens its consumer privacy and breach-notification regime. House Bill 380, signed on 2 September 2026 and effective 1 January 2027, amends the Delaware Personal Data Privacy Act (DPDPA) and lowers the law's applicability threshold from 35,000 to 10,000 Delaware consumers, with the revenue-linked alternative threshold for data sellers also dropping, from 10,000 to 5,000 consumers, where more than 20% of gross revenue derives from selling personal data. Companion House Bill 381, also signed 2 September 2026 and in force on signing, amends the state's breach-notification statute under Title 6, Chapter 12B, adding a requirement to notify the Delaware Attorney General within 60 days of determining a breach occurred, including in cases where affected residents cannot yet be identified, alongside the pre-existing trigger tied to notifying 500 or more residents. The two instruments move on different clocks: the breach-notice changes are already operative, while the substantive privacy-law changes phase in at the start of 2027, so organizations assessing exposure need to track both dates separately rather than treating the package as a single effective date.

Key regulatory facts for Delaware, USA
Key regulatory facts for Delaware, USA
Regulatory DimensionDelaware, USA Standing Position
JurisdictionDelaware, USA (US-DE)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 98 sourced findings)
Regulator & FrameworkCore instrument is fully in force with a clear, functioning regulator and well-documented material/territorial scope; amber-adjacent risk only from the unconfirmed pending amendment tracked separately in enforcement_and_redress.
Lawful Processing & Special DataStructurally divergent from GDPR Art.
Data Subject RightsRights and response windows are clearly documented and in force.
Controller/Processor DutiesCore security/DPIA/breach duties are well documented and in force; DPO and ROPA specifics are gaps.
Primary Instruments CitedDelaware, USA Official Instrument (zwillgen.com delaware-expands-privacy-law-new), Kelley Drye Ad Law Access, National Law Review, National Law Review, National Law Review
Last Confirmed / Updated (53 sources in cumulative register)

#

Core instrument is fully in force with a clear, functioning regulator and well-documented material/territorial scope; amber-adjacent risk only from the unconfirmed pending amendment tracked separately in enforcement_and_redress.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA), 6 Del. C. § 12D-101 et seq.
Traffic-light rationale — GreenCore instrument is fully in force with a clear, functioning regulator and well-documented material/territorial scope; amber-adjacent risk only from the unconfirmed pending amendment tracked separately in enforcement_and_redress.

Sub-modules (5)

Regulator and authorityGreen

Enforcement authority sits with the Delaware DOJ/Attorney General's Consumer Protection Unit; there is no dedicated privacy regulator or rulemaking agency.

Claims (5):

  • The Delaware Personal Data Privacy Act (DPDPA) took effect on January 1, 2025, and is enforced by the Delaware Department of Justice.
  • 6 Del. C. §12D-111(a) — Exclusive DPDPA enforcement authority in the Delaware Attorney General, assisted by the Department of Justice; the Act grants no agency rulemaking authority.
  • Delaware Attorney General / Department of Justice — Enforcement authority under the DPDPA rests exclusively in the Delaware AG/DOJ; the Act authorizes no rulemaking
  • Under 6 Del.C. § 12D-111, the DPDPA is enforced solely by the Delaware Department of Justice; no private right of action exists.
  • Delaware Department of Justice — Section 12D-111(e), as amended by HB380, continues to provide that a DPDPA violation is enforced solely by the Delaware DOJ, with no private right of action.

Act and instrumentsGreen

The DPDPA is the sole omnibus instrument; a separate long-standing Delaware breach-notification statute (6 Del. C. §12B) operates alongside it.

Claims (6):

  • The Delaware Personal Data Privacy Act (DPDPA) took effect on January 1, 2025, and is enforced by the Delaware Department of Justice.
  • House Bill 380 / House Bill 381 — HB 380, signed 2026-09-02, substantially amends the DPDPA, effective 2027-01-01; HB 381, also signed 2026-09-02, separately amends Delaware's breach-notification statute and took effect upon signing.
  • House Bill 380 — Signed by Governor Matt Meyer on September 2, 2026, amending the DPDPA, effective January 1, 2027
  • House Bill 380 — Amends the DPDPA; effective 2027-01-01.
  • House Bill 380, signed 2026-09-02, amends the Delaware Personal Data Privacy Act (DPDPA); effective 2027-01-01.
  • House Bill 381, signed 2026-09-02, amends Delaware's breach-notification statute (Title 6, Chapter 12B); effective on signing.

Material scopeGreen

Material scope is defined by consumer-count/revenue thresholds and a broad personal-data definition, with sectoral exemptions.

Claims (7):

  • The DPDPA applies to persons conducting business in or targeting Delaware residents that, in the preceding calendar year, controlled or processed the personal data of 35,000 or more consumers, or 10,000 or more consumers while deriving more than 20% of gross revenue from selling personal data.
  • The DPDPA does not apply to personal data maintained in compliance with the Gramm-Leach-Bliley Act, HIPAA, or the Fair Credit Reporting Act, nor to certain data processed for specified exempt purposes.
  • DPDPA applicability thresholds — HB 380 lowers the general applicability threshold from 35,000 to 10,000 Delaware consumers, and from 10,000 to 5,000 for businesses deriving >20% of revenue from data sales, with a new third-party-acquirer trigger
  • HB 380 applicability thresholds — General applicability threshold from 35,000 to 10,000 Delaware consumers; data-sale threshold from 20,000/20%-revenue to 5,000 consumers combined with over 20% of gross revenue from data sale; new third trigger for any third party acquiring personal data from a controller, effective 2027-01-01.
  • HB 380, signed 2026-09-02 and effective 2027-01-01, lowers the DPDPA's applicability threshold from 35,000 to 10,000 consumers (5,000 for data-sale-revenue entities).
  • HB 380 narrows the DPDPA's prior broad GLBA entity-level exemption to targeted exemptions for specified financial activities/entities, effective 2027-01-01.
  • DPDPA — HB380 lowers the general applicability threshold from 35,000 to 10,000 Delaware consumers, and the revenue-linked alternative threshold from 10,000 to 5,000 consumers where more than 20% of gross revenue derives from selling personal data, effective 2027-01-01.

Territorial scopeGreen

The Act reaches any entity, regardless of domicile, that targets Delaware residents or conducts business in the state and meets the threshold; the AG has indicated it will pursue out-of-state controllers meeting the threshold.

Claims (1):

  • The Attorney General has stated it will not hesitate to pursue enforcement against out-of-state third parties doing business in Delaware if they meet the DPDPA's applicability threshold.

Regulator registration and filingAmber

No controller registration/filing regime with the Attorney General was identified; compliance is self-assessed against statutory thresholds.

Claims (1):

  • No controller registration or filing obligation with the Delaware Attorney General was located within the DPDPA or AG guidance; compliance appears self-assessed.
Category narrative 103 words

Delaware's comprehensive consumer-privacy regime is the Delaware Personal Data Privacy Act (DPDPA), 6 Del. C. § 12D-101 et seq., signed September 11, 2023 and in force since January 1, 2025, enforced exclusively by the Delaware Department of Justice / Attorney General (no dedicated privacy agency). It applies to entities conducting business in or targeting Delaware residents that meet a 35,000-consumer (or 10,000-consumer plus 20%-revenue-from-sale) processing threshold, with express carve-outs for data governed by GLBA, HIPAA and FCRA. A pending amendment (HB 380, introduced April 2026) would lower thresholds and expand obligations effective January 2027; its enactment status is unconfirmed as of this run.

Periodic update · new data 2026-11-08

Delaware's privacy framework was reshaped by two companion bills, both signed on 2 September 2026. House Bill 380 amends the Delaware Personal Data Privacy Act (DPDPA) and takes effect on 1 January 2027; House Bill 381 amends the state's breach-notification statute under Title 6, Chapter 12B, and took effect immediately on signing. The two instruments therefore sit on separate timelines, with the breach-notice changes already live and the substantive privacy-law changes still pending. Enforcement architecture is unchanged by this package: the DPDPA continues to be enforced solely by the Delaware Department of Justice, with no private right of action created for consumers.

Outlook

The principal date to track is 1 January 2027, when HB380's amendments to the DPDPA become effective; HB381's breach-notice changes require no further waiting, being already in force.

5 earlier distinct updates
Periodic update · new data 2026-11-04

The Delaware Personal Data Privacy Act continues to be enforced exclusively by the Delaware Department of Justice under 6 Del.C. § 12D-111, with no private right of action available to consumers. The most significant development is House Bill 380's amendment of the Act's scope: the general applicability threshold drops from 35,000 to 10,000 Delaware consumers processed or controlled in the preceding calendar year, and the separate data-sale threshold drops from 10,000 to 5,000 consumers for entities deriving more than 20% of gross revenue from personal-data sales. Both changes take effect on 1 January 2027. The amendment also replaces the Act's previous broad, entity-level exemption for institutions regulated under the federal Gramm-Leach-Bliley Act with a narrower set of targeted exemptions covering specified financial, banking and insurance activities and entities, rather than exempting such institutions wholesale.

Outlook

The lowered thresholds represent the most consequential scope change: a materially larger population of companies doing business with Delaware consumers will fall within the Act's compliance perimeter from 1 January 2027, and those currently exempt under the broad GLBA carve-out will need to reassess whether a narrower, activity-specific exemption still applies to them once the amendment takes effect.

Periodic update · new data 2026-10-25

Enforcement authority under the Delaware Personal Data Privacy Act remains exclusively vested in the Delaware Attorney General, assisted by the Department of Justice, with no agency granted rulemaking authority under the Act. This is a standing feature of the framework reconfirmed rather than a new development.

The material development is House Bill 380, signed 2 September 2026 and effective 1 January 2027, which substantially amends the Act. A companion measure, House Bill 381, also signed 2 September 2026, separately amends Delaware's breach-notification statute and took effect upon signing rather than being deferred to 2027. The two measures are distinct instruments addressing different parts of Delaware's privacy architecture: House Bill 380 reworks the core applicability and controller-obligation provisions of the Act itself, while House Bill 381 operates on the separate breach-notification statute. Reading the two together, Delaware has moved on both fronts simultaneously, tightening breach-notice procedure immediately while deferring the Act's broader scope and obligation changes to the start of 2027.

The practical effect of House Bill 380's framework-level changes will not be felt until 1 January 2027, meaning the current operative scope of the Act, including its 35,000-consumer threshold, remains in place for the balance of 2026. Businesses assessing their current obligations should distinguish between what is already in force, the breach-notification changes under House Bill 381 and the enforcement posture described above, and what remains enacted but not yet effective, the House Bill 380 amendments to the Act proper.

Outlook

The principal date to track is 1 January 2027, when House Bill 380's amendments take effect. Confirmation of the exact statutory citations for several of the amendments remains outstanding, and later cycles should be expected to narrow that gap as primary Delaware Code text becomes available for direct citation rather than commentary-sourced description.

Periodic update · new data 2026-10-18

Delaware's Personal Data Privacy Act continues to place exclusive enforcement authority in the Attorney General's Department of Justice, with the Act authorizing no rulemaking power for any regulator. This confirmed structural feature means Delaware has no administrative rulemaking body analogous to those in some other comprehensive state privacy regimes; the statutory text itself, as amended, is the complete source of binding obligation, subject only to DOJ enforcement discretion and judicial interpretation.

The framework itself underwent its most significant expansion since original enactment when Governor Matt Meyer signed House Bill 380 on September 2, 2026, amending the DPDPA with an effective date of January 1, 2027. The amendment's headline change is a substantial lowering of the Act's applicability thresholds: the general threshold drops from 35,000 to 10,000 Delaware consumers, and the data-sales-heavy-business threshold drops from 10,000 to 5,000 consumers for businesses deriving more than 20 percent of revenue from data sales. HB 380 is also understood to add a new third-party-acquirer trigger, a mechanism that appears designed to capture businesses that acquire previously collected consumer data from others, rather than only businesses that directly collect data from Delaware consumers themselves.

The combined effect of these threshold reductions is a material scope expansion. A business that collects or processes personal data for 15,000 Delaware consumers, for example, sits entirely outside the current 35,000-consumer threshold but will fall squarely within scope once the 10,000-consumer threshold takes effect. This scope expansion is the single most consequential structural change in this cycle's Delaware privacy development, because it determines, as a threshold matter, which businesses must comply with every other substantive obligation in the Act at all.

It is understood that HB 380 was not retrieved in full statutory text this cycle; the findings here rest on multiple convergent secondary-commentary sources from law-firm privacy blogs, corroborated by one Tier 1 bill-detail page confirming the bill's existence and status. This sourcing pattern supports confident characterization of the direction and substance of the changes while leaving some statutory pinpoint citations unconfirmed.

Outlook

The effective date of January 1, 2027 is the operative horizon for this entire framework expansion. Businesses currently relying on the 35,000-consumer threshold to remain outside DPDPA scope have a defined window to reassess their position before the lowered thresholds take effect. Given that enforcement remains exclusively with the DOJ and the Act authorizes no implementing regulations, there is no rulemaking process to track separately from the statutory effective date itself; compliance obligations will simply activate as written on January 1, 2027.

Periodic update · new data 2026-10-11

Delaware's Personal Data Privacy Act was amended by House Bill 380, signed by Governor Matt Meyer on September 2, 2026. The amendment excludes individuals acting in a commercial or employment context from the statute's definition of "consumer," narrowing the population of individuals whose personal data processing triggers the Act's consumer-rights obligations. The core framework otherwise remains in force unchanged: the Delaware Personal Data Privacy Act applies to entities that control or process the personal data of not less than 35,000 Delaware residents, or not less than 10,000 residents where more than 20 percent of gross revenue is derived from the sale of personal data, excluding payment-transaction-only data from that threshold calculation. The Delaware Department of Justice remains the sole regulator and enforcement authority for the statute; no change to the regulator's identity or statutory powers was introduced by HB-380.

Outlook

The practical boundaries of the new employment-context exclusion, including how it applies to mixed personal/employment data processing, will likely require Department of Justice interpretive guidance given the absence of a private right of action through which courts could otherwise resolve ambiguity in the carve-out's scope.

Periodic update · new data 2026-10-04

Delaware's privacy framework is anchored entirely in the Delaware Personal Data Privacy Act, enforced exclusively by the Delaware Attorney General; the Act carries no private right of action and no dedicated supervisory agency distinct from the Attorney General's office. This cycle brought the most significant amendment to that framework since the DPDPA's original enactment in 2023, through two companion bills signed September 2, 2026. HB380 amends the DPDPA itself and takes effect January 1, 2027; HB381 amends Delaware's separate breach-notification chapter, 6 Del. C. ch. 12B, and took effect immediately upon signing.

The most consequential structural change in HB380 is scope expansion: it lowers the DPDPA's general applicability threshold from 35,000 to 10,000 Delaware consumers, and lowers the data-sale-revenue threshold from 10,000 to 5,000 consumers for businesses deriving over 20 percent of gross revenue from personal-data sales. It also extends the Act's reach to third parties that acquire personal data from a controller, a provision that pulls data recipients, not just original collectors, within the statute's scope. Taken together, these changes are understood to bring a substantially larger population of small and mid-sized Delaware-facing businesses within the Act's coverage once the amendment takes effect on January 1, 2027.

The framework's enforcement architecture itself is unchanged by this cycle's amendments: the Attorney General remains the sole enforcement authority, and no private right of action has been introduced. This places Delaware alongside most recent state comprehensive-privacy statutes outside California in retaining an AG-only enforcement model even as the Act's substantive scope and obligations are expanded.

Outlook

Whether the Delaware Attorney General will issue implementing rulemaking or guidance ahead of the January 1, 2027 effective date is not yet resolved. Businesses newly brought within scope by the lowered thresholds have a defined runway to the effective date but no published implementing guidance to date on how the Attorney General's office intends to approach enforcement of the expanded scope.

Sources and claims (19)
  1. Probable State of Delaware — The Delaware Personal Data Privacy Act (DPDPA) took effect on January 1, 2025, and is enforced by the Delaware Department of Justice. observed
  2. Probable DataGuidance — The DPDPA applies to persons conducting business in or targeting Delaware residents that, in the preceding calendar year, controlled or processed the personal data of 35,000 or more consumers, or 10,000 or more consumers while deriving more than 20% of gross revenue from selling personal data. observed
  3. Probable State of Delaware — The DPDPA does not apply to personal data maintained in compliance with the Gramm-Leach-Bliley Act, HIPAA, or the Fair Credit Reporting Act, nor to certain data processed for specified exempt purposes. observed
  4. Probable State of Delaware — The Attorney General has stated it will not hesitate to pursue enforcement against out-of-state third parties doing business in Delaware if they meet the DPDPA's applicability threshold. observed
  5. Probable State of Delaware — No controller registration or filing obligation with the Delaware Attorney General was located within the DPDPA or AG guidance; compliance appears self-assessed. observed
  6. Probable https://www.hunton.com/privacy-and-cybersecurity-law-blog/delaware-expands-state-privacy-law — House Bill 380 / House Bill 381 — HB 380, signed 2026-09-02, substantially amends the DPDPA, effective 2027-01-01; HB 381, also signed 2026-09-02, separately amends Delaware's breach-notification statute and took effect upon signing.
  7. Probable WilmerHale — House Bill 380 — Signed by Governor Matt Meyer on September 2, 2026, amending the DPDPA, effective January 1, 2027 observed
  8. Probable RecordingLaw — DPDPA applicability thresholds — HB 380 lowers the general applicability threshold from 35,000 to 10,000 Delaware consumers, and from 10,000 to 5,000 for businesses deriving >20% of revenue from data sales, with a new third-party-acquirer trigger observed
  9. Probable Didomi — 6 Del. C. §12D-111(a) — Exclusive DPDPA enforcement authority in the Delaware Attorney General, assisted by the Department of Justice; the Act grants no agency rulemaking authority. observed
  10. Probable Coverpin — HB 380 applicability thresholds — General applicability threshold from 35,000 to 10,000 Delaware consumers; data-sale threshold from 20,000/20%-revenue to 5,000 consumers combined with over 20% of gross revenue from data sale; new third trigger for any third party acquiring personal data from a controller, effective 2027-01-01. observed
  11. Probable Osano — Delaware Attorney General / Department of Justice — Enforcement authority under the DPDPA rests exclusively in the Delaware AG/DOJ; the Act authorizes no rulemaking observed
  12. Probable Delaware Department of Justice — Under 6 Del.C. § 12D-111, the DPDPA is enforced solely by the Delaware Department of Justice; no private right of action exists. observed
  13. Probable Delaware General Assembly — HB 380, signed 2026-09-02 and effective 2027-01-01, lowers the DPDPA's applicability threshold from 35,000 to 10,000 consumers (5,000 for data-sale-revenue entities). observed
  14. Probable Future of Privacy Forum — HB 380 narrows the DPDPA's prior broad GLBA entity-level exemption to targeted exemptions for specified financial activities/entities, effective 2027-01-01. observed
  15. Probable LegiScan (mirror of Delaware HB380 enacted text) — House Bill 380 — Amends the DPDPA; effective 2027-01-01. observed
  16. Probable RecordingLaw — Delaware Department of Justice — Section 12D-111(e), as amended by HB380, continues to provide that a DPDPA violation is enforced solely by the Delaware DOJ, with no private right of action. observed
  17. Probable LegiScan (mirror of Delaware HB380 enacted text) — House Bill 380, signed 2026-09-02, amends the Delaware Personal Data Privacy Act (DPDPA); effective 2027-01-01. observed
  18. Probable Delaware General Assembly (HB381 bill detail) — House Bill 381, signed 2026-09-02, amends Delaware's breach-notification statute (Title 6, Chapter 12B); effective on signing. observed
  19. Probable McDonald Hopkins — DPDPA — HB380 lowers the general applicability threshold from 35,000 to 10,000 Delaware consumers, and the revenue-linked alternative threshold from 10,000 to 5,000 consumers where more than 20% of gross revenue derives from selling personal data, effective 2027-01-01. observed

#

Structurally divergent from GDPR Art. 6 lawful-basis architecture (amber for interoperability), though the consent standard itself is clearly and consistently defined; pseudonymisation/anonymisation safe-harbour detail was not confirmed.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA)
Traffic-light rationale — AmberStructurally divergent from GDPR Art. 6 lawful-basis architecture (amber for interoperability), though the consent standard itself is clearly and consistently defined; pseudonymisation/anonymisation safe-harbour detail was not confirmed.

Sub-modules (4)

Lawful basesAmber

No enumerated Art. 6-style lawful bases; a notice/purpose-limitation-and-opt-out model governs ordinary processing.

Claims (2):

  • Rather than enumerating GDPR-style lawful bases, the DPDPA relies on a notice-and-purpose-limitation model, requiring affirmative consumer consent only for sensitive-data processing, secondary-purpose processing, and processing following a consumer opt-out.
  • DPDPA — HB380 expands controller data-minimization duties to require that processing, not merely collection, of personal data be reasonably necessary and proportional to its stated purpose.

Special categoriesGreen

Sensitive data (health, biometric, genetic, ethnicity, religion, sexual orientation, immigration status, children's data) requires prior consumer consent.

Claims (6):

  • Sensitive data under the DPDPA includes data revealing racial/ethnic origin, religious beliefs, health diagnoses, sexual orientation/activity, citizenship/immigration status, and genetic or biometric data used to uniquely identify an individual, requiring consumer consent prior to collection or processing.
  • DPDPA sensitive-data definition — HB 380 expands 'sensitive data' to include neural data, government identifiers, financial account credentials, national origin, certain health-treatment information, and inferences revealing such categories
  • DPDPA sensitive-data sales — Sales of sensitive data must be strictly necessary to provide a product/service affirmatively requested by the consumer, requiring contractual third-party-disclosure provisions
  • HB 380 sensitive-data sale limits — Strict new limits on the sale of sensitive personal data, effective 2027-01-01; exact statutory test/pinpoint could not be confirmed this cycle.
  • HB 380 expands the DPDPA's sensitive-data definition to include national origin, health status, neural data, and financial credentials, effective 2027-01-01.
  • HB380 expands the DPDPA's definition of sensitive data to include national origin, certain health information, neural data, financial account credentials and government-issued identification numbers.

Pseudonymisation and anonymisationRed

Detailed pseudonymisation/anonymisation safe-harbour criteria were not confirmed in the reviewed AG guidance.

Category narrative 60 words

The DPDPA does not use a GDPR-style enumerated lawful-basis regime (Art. 6 analogue); instead it operates a notice-and-opt-out model built on purpose limitation and data minimization, layering an affirmative-consent requirement onto sensitive-data processing, secondary-purpose processing, and post-opt-out processing. Sensitive data is broadly defined (race/ethnicity, religion, health, sexual orientation/activity, immigration status, genetic/biometric identifiers, and children's data) and requires consent before collection.

Periodic update · new data 2026-11-08

House Bill 380 expands the DPDPA's definition of sensitive data to include, among other additions, national origin, certain categories of health information, neural data, financial account credentials and government-issued identification numbers, broadening the set of processing activities that will require heightened consent once the amendment takes effect on 1 January 2027. The amendment is also reported to tighten the data-minimization duty, extending it from collection alone to ongoing processing, so that processing activity must be reasonably necessary and proportional to the purpose for which the data was collected, not only the initial act of collecting it.

Outlook

Controllers handling the newly added sensitive-data categories, and those relying on broad processing purposes, have until 1 January 2027 to bring consent and minimization practices into line with the amended standard.

4 earlier distinct updates
Periodic update · new data 2026-11-04

House Bill 380 expands the DPDPA's sensitive-data definition, effective 1 January 2027, to add national origin, mental or physical health condition or status (including pregnancy), neural data generated by measuring the activity of an individual's central nervous system, and financial account or login credentials combined with a password or access code. The amendment also clarifies that an inference revealing a sensitive characteristic about a consumer is itself treated as sensitive data, closing what had been a gap around profiling-derived inferences. Alongside the expanded definition, the amendment moves the rule governing sale of sensitive data from an opt-out standard to an affirmative-consent standard: a controller may not disclose sensitive data in a sale of personal data unless the consumer has affirmatively requested that disclosure, following clear and conspicuous prior notice of the categories of sensitive data involved, the purpose of the sale, and the third parties receiving it.

Outlook

Controllers handling Delaware consumer data will need to review their consent and notice flows for sensitive-data sales well ahead of the 1 January 2027 effective date, since the shift to affirmative consent is a higher bar than a universal opt-out mechanism can satisfy. The expanded sensitive-data categories, particularly neural data and inference-based sensitive data, will also require controllers to re-examine data flows that generate profiling outputs to determine whether those outputs now fall within the sensitive-data perimeter.

Periodic update · new data 2026-10-25

Since 1 January 2026, controllers subject to the Delaware Personal Data Privacy Act have been required to recognize Universal Opt-Out Mechanisms, such as Global Privacy Control, as a valid means by which a consumer may opt out of targeted advertising, the sale of personal data, and certain profiling. This is a standing obligation rather than a new development, and it continues to operate independently of the broader applicability-threshold changes introduced by House Bill 380.

House Bill 380 does introduce a new development for special-category data: strict new limits on the sale of sensitive personal data, effective 1 January 2027. Reports describing this provision are consistent in direction, toward tightening, but the exact statutory test or definitional mechanism by which the limits operate could not be confirmed against primary text. The finding should accordingly be read as a reported tightening of sensitive-data-sale restrictions whose precise legal mechanism is not yet verified, rather than as a settled statement of the new rule's operative language.

Taken together, the lawful-processing picture for Delaware going into 2027 combines a mature, already-operative opt-out-signal recognition regime with a newly tightened, but not yet precisely specified, restriction on sensitive-data sale.

Outlook

Confirming the precise statutory language of the new sensitive-data-sale limits against primary Delaware Code text, once House Bill 380's amendments take effect on 1 January 2027, is the principal open item for this module.

Periodic update · new data 2026-10-18

House Bill 380 substantially broadens the category of information treated as sensitive data under the Delaware Personal Data Privacy Act. It is understood to expand the statutory definition to include neural data, government identifiers, financial account credentials, national origin, certain health-treatment information, and, notably, inferences that reveal such categories, meaning a business cannot avoid sensitive-data obligations merely by processing proxy or inferred data rather than the sensitive category directly. This inference-coverage feature is analytically significant because it closes a common workaround seen in other states' privacy statutes, where sensitive-data protections apply only to directly collected sensitive attributes and not to derived or inferred equivalents.

The lawful basis for processing sensitive data under the amended Act requires two things simultaneously: consumer consent, and a showing that the processing is reasonably necessary and proportionate to the controller's disclosed purposes. This dual standard, consent plus necessity-and-proportionality, is a higher bar than a pure consent-based model, since it is understood to prevent a controller from relying on consent alone to justify sensitive-data processing that exceeds what is proportionate to its stated purpose.

Sales of sensitive data face a further, more restrictive standard. Such sales must be strictly necessary to provide a product or service that the consumer has affirmatively requested. This is reported to make Delaware the second state, after California, to impose this particular restriction on sensitive-data sales, a notable positioning given Delaware's modest population relative to its outsized role in US corporate law generally. The strictly-necessary standard for sales is materially tighter than the consent-plus-proportionality standard for processing generally, reflecting a graduated-risk approach where sale, as the most consequential form of sensitive-data use, receives the most restrictive treatment.

Outlook

These sensitive-data provisions take effect January 1, 2027, alongside the rest of the HB 380 package. The practical compliance challenge for controllers processing Delaware consumer data is likely to center on the inference-coverage feature: businesses relying on behavioral or derived data that reveals a sensitive category, even without directly collecting that category, will need to map their inference pipelines against the expanded definition well ahead of the effective date. The strictly-necessary standard for sensitive-data sales will similarly require controllers currently selling such data under a general consent model to reassess whether that sale activity meets the new, narrower threshold.

Periodic update · new data 2026-10-04

HB380 is reported to expand the DPDPA's definition of sensitive data considerably. The amendment extends the category to include data revealing or identifying national origin, citizenship or immigration status, diagnosis or treatment status, gender identity, neural data, financial account or login credentials, and government-issued identification. This is a substantial broadening relative to the original 2023 DPDPA's special-category list, and it brings Delaware's sensitive-data definition closer to the more expansive categories seen in some other recently amended state privacy statutes, particularly in its explicit inclusion of neural data and immigration-status-related data.

The practical effect of this expansion, once HB380 takes effect on January 1, 2027, is that a wider range of processing activities will trigger the DPDPA's heightened consent and risk-assessment obligations that attach to sensitive-data processing. Businesses processing data that reveals immigration status, gender identity, or financial login credentials, categories not previously enumerated as sensitive under the original DPDPA, will need to evaluate whether their processing now falls within the sensitive-data consent regime.

Outlook

The expanded sensitive-data definition takes effect January 1, 2027, alongside the rest of HB380's amendments. The exact statutory citation and section for this expanded definition has not been independently verified against the engrossed bill text this cycle, so businesses should anticipate confirming the precise boundaries of each newly enumerated category against the final statutory text as the effective date approaches.

Sources and claims (12)
  1. Probable State of Delaware — Rather than enumerating GDPR-style lawful bases, the DPDPA relies on a notice-and-purpose-limitation model, requiring affirmative consumer consent only for sensitive-data processing, secondary-purpose processing, and processing following a consumer opt-out. observed
  2. Probable State of Delaware — Under the DPDPA, consent must be affirmative, freely given, specific, informed, and unambiguous; acceptance of broad terms of service, passive interaction with content, or agreement obtained through deceptive webpage design is not valid consent. observed
  3. Probable State of Delaware — Sensitive data under the DPDPA includes data revealing racial/ethnic origin, religious beliefs, health diagnoses, sexual orientation/activity, citizenship/immigration status, and genetic or biometric data used to uniquely identify an individual, requiring consumer consent prior to collection or processing. observed
  4. Probable Cookiebot — DPDPA Universal Opt-Out Mechanism provision — Since 2026-01-01, DPDPA controllers must recognize Universal Opt-Out Mechanisms such as Global Privacy Control as a valid consumer opt-out of targeted advertising, sale and certain profiling. observed
  5. Probable Inside Privacy — DPDPA sensitive-data processing — Processing of sensitive data must be both consented to and 'reasonably necessary and proportionate' to the controller's disclosed purposes observed
  6. Probable https://www.zwillgen.com/privacy/delaware-expands-privacy-law-new-third-party-due-diligence-requirements/ — DPDPA sensitive-data definition — HB 380 expands 'sensitive data' to include neural data, government identifiers, financial account credentials, national origin, certain health-treatment information, and inferences revealing such categories
  7. Probable Kelley Drye Ad Law Access — DPDPA sensitive-data sales — Sales of sensitive data must be strictly necessary to provide a product/service affirmatively requested by the consumer, requiring contractual third-party-disclosure provisions observed
  8. Uncertain https://www.trustsuperset.com/post/delaware-personal-data-privacy-act-hb-380 — HB 380 sensitive-data sale limits — Strict new limits on the sale of sensitive personal data, effective 2027-01-01; exact statutory test/pinpoint could not be confirmed this cycle.
  9. Probable Kelley Drye Ad Law Access — HB 380 expands the DPDPA's sensitive-data definition to include national origin, health status, neural data, and financial credentials, effective 2027-01-01. observed
  10. Probable Primary statutory record — Under HB 380's amended § 12D-106(a)(12), a controller may not sell sensitive data except as affirmatively requested by the consumer, effective 2027-01-01.
  11. Probable Global Policy Watch (Epstein Becker Green) — HB380 expands the DPDPA's definition of sensitive data to include national origin, certain health information, neural data, financial account credentials and government-issued identification numbers. observed
  12. Probable Morgan Lewis — DPDPA — HB380 expands controller data-minimization duties to require that processing, not merely collection, of personal data be reasonably necessary and proportional to its stated purpose. observed

#

Rights and response windows are clearly documented and in force.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA)
Traffic-light rationale — GreenRights and response windows are clearly documented and in force.

Sub-modules (5)

Access rightGreen

Consumers may access their personal data free of charge once every 12 months; additional requests may incur an administrative fee.

Claims (3):

  • Delaware consumers may request access to personal data a controller has collected about them free of charge once every 12 months; controllers may charge an administrative fee for additional requests.
  • DPDPA access right — Controllers must provide, within 30 days, personal data maintained, sources used in profiling, and third parties that received reports during the preceding 24 months
  • DPDPA — Controllers must provide consumers within 30 days with personal data maintained, sources used in profiling, and third parties receiving reports over the preceding 24 months, while withholding specified elements such as SSNs, financial account numbers, health information and biometric data.

Rectification and erasureGreen

Consumers may correct inaccuracies and delete personal data, including data obtained by controllers from third parties.

Claims (1):

  • Consumers have the right to correct inaccuracies in and delete their personal data, including data a controller collected through third parties.

Restriction and objectionGreen

Consumers may opt out of the sale of personal data to third parties and may designate an authorized agent to do so on their behalf.

Claims (2):

  • Consumers may opt out of the sale of personal data to third parties and may designate a third party to exercise the opt-out on their behalf.
  • DPDPA profiling opt-out — HB 380 removes 'solely' from the profiling opt-out, extending it to decisions including a human step

Data portabilityGreen

Portability is included among the enumerated consumer rights alongside access, correction, erasure and opt-out.

Claims (1):

  • Consumer rights under the DPDPA include information access, data rectification, erasure, portability, and opt-out options for targeted advertising and automated profiling.

Deadlines and response windowsGreen

Controllers have 45 days to respond to a consumer's appeal of a denied rights request.

Claims (2):

  • A controller has 45 days after receipt of a consumer's appeal of a denied rights request to respond in writing, explaining the actions taken and reasons for refusal.
  • HB 380 consumer-report disclosure duty — A business selling consumer reports must, within 30 days of a resident's request, disclose what data it holds on them, where profiling data came from, and who received a report on them in the past 24 months.
Category narrative 36 words

The DPDPA grants Delaware consumers access, correction, deletion, portability, and opt-out (sale/targeted-advertising/profiling) rights, with a free access request permitted once every 12 months and a 45-day window for controllers to respond to appeals of denied requests.

Periodic update · new data 2026-11-08

Under the amended DPDPA, controllers are to provide consumers, on request and within 30 days, with the personal data maintained about them, the sources used in any profiling applied to them, and the identity of third parties that received reports about them over the preceding 24 months. The right carries express limits: specified categories, including Social Security numbers, financial account numbers, health information and biometric data, are withheld from what is disclosed in response to such a request.

Outlook

The revised access right takes effect alongside the rest of HB380 on 1 January 2027, giving controllers a defined window to build the sourcing and third-party-disclosure records the right will require them to produce.

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

House Bill 380 introduces a new consumer-report-specific disclosure right, effective 1 January 2027: a business that sells consumer reports must, within 30 days of a Delaware resident's request, disclose what data it holds on that resident, where any profiling data used about them originated, and who received a report concerning them in the preceding 24 months. This is reported with reasonably strong support, though it should be read as understood to apply along these lines rather than as finally confirmed in every procedural detail, pending direct citation of the implementing statutory text.

This new right sits alongside, rather than replacing, Delaware consumers' existing rights under the Act, and specifically targets a category of data handling, consumer reporting, that had not previously carried a Delaware-specific disclosure obligation distinct from the Act's general access-and-correction rights. The 24-month look-back period for report-recipient disclosure is a notably specific and consumer-favourable feature, giving residents visibility into a particular historical window of third-party data-sharing activity tied to their consumer report.

Outlook

As 1 January 2027 approaches, confirmation of the precise procedural mechanics, such as the form a disclosure request must take and the method of response, will be the key item to track, alongside how this disclosure right interacts with the adverse-action notice and human-review requirements introduced by the same legislation for automated decision-making contexts.

Periodic update · new data 2026-10-18

House Bill 380 expands two distinct data subject rights under the Delaware Personal Data Privacy Act: the access right and the profiling opt-out. On access, controllers must, within 30 days of a verified request, provide the personal data they maintain about the consumer, the sources used in any profiling of the consumer, and the identity of third parties that received reports about the consumer during the preceding 24 months. This is a meaningful broadening beyond a bare data-inventory disclosure; it requires controllers to disclose their profiling methodology sourcing and their downstream disclosure history, giving consumers visibility into both how they were profiled and who received the resulting output.

On automated decision-making, HB 380 is understood to remove the word solely from the Act's profiling opt-out provision. Under the prior text, a consumer's right to opt out of profiling in furtherance of decisions that produce legal or similarly significant effects applied only to decisions made solely through automated processing. Removing solely extends the opt-out right to decisions that combine automated processing with some human involvement, closing a gap that has historically allowed companies to defeat an automated-decision opt-out right simply by inserting a nominal human review step into an otherwise automated decision pipeline. This is a structurally significant expansion because it addresses one of the most commonly identified weaknesses in solely-automated-decision-based opt-out frameworks generally.

Both of these rights expansions are enacted but not yet effective, sharing the broader HB 380 effective date of January 1, 2027. Until that date, the pre-amendment versions of the access right and the profiling opt-out, including the solely qualifier on automated decisions, remain the operative legal standard.

Outlook

Controllers should anticipate that the expanded access right's 24-month third-party-disclosure lookback and profiling-sources disclosure will require meaningful operational preparation, particularly for organizations that have not previously tracked profiling methodology or third-party-disclosure history in a readily retrievable form. The removal of solely from the profiling opt-out will likely require controllers to reassess which of their currently human-reviewed decision processes should now be treated as subject to opt-out, since the human-in-the-loop exemption that previously applied will no longer be available once the amendment takes effect.

Sources and claims (9)
  1. Probable State of Delaware — Delaware consumers may request access to personal data a controller has collected about them free of charge once every 12 months; controllers may charge an administrative fee for additional requests. observed
  2. Probable State of Delaware — Consumers have the right to correct inaccuracies in and delete their personal data, including data a controller collected through third parties. observed
  3. Probable State of Delaware — Consumers may opt out of the sale of personal data to third parties and may designate a third party to exercise the opt-out on their behalf. observed
  4. Probable DataGuidance — Consumer rights under the DPDPA include information access, data rectification, erasure, portability, and opt-out options for targeted advertising and automated profiling. observed
  5. Probable State of Delaware — A controller has 45 days after receipt of a consumer's appeal of a denied rights request to respond in writing, explaining the actions taken and reasons for refusal. observed
  6. Probable National Law Review — DPDPA profiling opt-out — HB 380 removes 'solely' from the profiling opt-out, extending it to decisions including a human step observed
  7. Probable TrustSuperset — HB 380 consumer-report disclosure duty — A business selling consumer reports must, within 30 days of a resident's request, disclose what data it holds on them, where profiling data came from, and who received a report on them in the past 24 months. observed
  8. Probable https://www.zwillgen.com/privacy/delaware-expands-privacy-law-new-third-party-due-diligence-requirements/ — DPDPA access right — Controllers must provide, within 30 days, personal data maintained, sources used in profiling, and third parties that received reports during the preceding 24 months
  9. Probable Delaware General Assembly (HB381 bill detail) — DPDPA — Controllers must provide consumers within 30 days with personal data maintained, sources used in profiling, and third parties receiving reports over the preceding 24 months, while withholding specified elements such as SSNs, financial account numbers, health information and biometric data. observed

#

Core security/DPIA/breach duties are well documented and in force; DPO and ROPA specifics are gaps.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA); Delaware data breach notification statute, 6 Del. C. §12B
Traffic-light rationale — AmberCore security/DPIA/breach duties are well documented and in force; DPO and ROPA specifics are gaps.

Sub-modules (7)

Accountability & DPIAGreen

DPIAs are required for high-risk processing activities.

Claims (3):

  • Controllers must conduct data protection impact assessments (DPIAs) for high-risk processing activities under the DPDPA.
  • HB 380 Data Protection Assessment threshold — DPA threshold lowered from 100,000 to 50,000 Delaware consumers for controllers selling personal data, processing for targeted advertising, or processing sensitive data; effective 2027-01-01.
  • DPDPA data-protection-assessment trigger — HB 380 lowers the DPIA trigger threshold from 100,000 to 50,000 consumers

DPO requirementsRed

No DPO-appointment threshold analogous to GDPR Art. 37 was identified.

Claims (1):

  • No dedicated Data Protection Officer appointment threshold analogous to GDPR Art. 37-39 was identified in the DPDPA or AG guidance.

Ropa requirementsAmber

Controllers/processors document processing relationships contractually; a formal public ROPA filing requirement was not confirmed.

Claims (1):

  • Businesses are directed to inventory personal data collected, identify storage locations, and document access and third-party processor relationships, though no formal public Records-of-Processing-Activities filing requirement was confirmed.

Joint controller arrangementsAmber

The Act distinguishes controller/processor roles by decision-making authority; a processor exercising independent decision-making becomes a controller for that processing.

Claims (3):

  • DPDPA third-party disclosure duties — Controllers must conduct 'reasonable due diligence' of third parties to which personal data is disclosed for sale or targeted advertising, and enter contracts obligating equivalent DPDPA protections
  • HB 380 requires documented due diligence of third parties receiving personal data, going beyond the DPDPA's prior standard-contract requirement, effective 2027-01-01.
  • HB380 creates a third-party due-diligence obligation under which a controller/processor disclosing data to a recipient is not deemed to have violated the DPDPA based on the recipient's independent violation, provided reasonable diligence and oversight were undertaken.

Security measuresGreen

Controllers must employ reasonable data security measures proportionate to the sensitivity of the personal data collected.

Claims (1):

  • The DPDPA requires businesses to employ reasonable data security measures proportionate to the nature and sensitivity of the personal data collected, to prevent unauthorized access.

Breach notificationGreen

Delaware's separate 2018 breach-notification statute requires notice to affected residents and, above 500 residents, to the Attorney General.

Claims (7):

  • Delaware's data breach notification statute, in effect since April 14, 2018, requires notice to affected Delaware residents and, where a breach affects 500 or more residents, additional notice to the Delaware Attorney General.
  • HB 381 AG breach-notice duty — Notice to the Delaware Attorney General within 60 days of determining that a data breach occurred, effective upon signing 2026-09-02.
  • HB 381 HIPAA/GLBA exemption narrowing — Compliance with regulator-established breach procedures under laws such as HIPAA or GLBA now satisfies only the 60-day timing requirement of Delaware's breach law, not the entirety of the state notification statute.
  • Delaware breach-notification law — HB 381 requires AG notice within 60 days of determining a breach occurred, including via substitute notice; already in force
  • Delaware breach-notification statute (Title 6, Ch. 12B) — Requires notice to the Delaware AG within 60 days of determining a breach occurred.
  • Delaware breach-notification statute (Title 6, Ch. 12B) — HB381 requires notice to the Delaware AG within 60 days of determining a breach occurred, including where affected residents cannot yet be identified, in addition to the pre-existing 500-resident trigger.
  • Delaware breach-notification statute (Title 6, Ch. 12B) — HB381 narrows the prior GLBA/HIPAA compliance safe harbor so that compliance with a federal breach-notification procedure now satisfies only the 60-day timing requirement, not the statute's other provisions.

Retention and disposalAmber

No DPDPA-specific retention-period or disposal-duty detail beyond general data-minimization principles was confirmed.

Category narrative 41 words

Controllers must apply data minimization, security, and DPIA obligations for high-risk processing. A long-standing separate breach-notification statute (since 2018) requires consumer notice and, above a 500-resident threshold, Attorney General notice. No DPO-appointment threshold or standalone public ROPA filing requirement was confirmed.

Periodic update · new data 2026-11-08

Two distinct duties were added. House Bill 380 introduces a third-party due-diligence provision under which a controller or processor that discloses personal data to a processor or third-party controller is not deemed to have violated the DPDPA solely because that recipient independently violates the law, provided the discloser exercised reasonable diligence and oversight before and during the disclosure relationship. House Bill 381, already in force, adds a duty to notify the Delaware Attorney General within 60 days of determining that a breach occurred, including where the affected residents cannot yet be identified, layered on top of the pre-existing notification trigger tied to breaches affecting 500 or more residents. HB381 is also reported to narrow the prior compliance safe harbor for GLBA-regulated financial institutions and HIPAA-regulated entities, so that following a federal breach-notification procedure now satisfies only the statute's 60-day timing requirement rather than its other obligations.

Outlook

The breach-notification changes require immediate attention, being already in force; the third-party due-diligence provision becomes relevant to vendor contracting and oversight practices as businesses prepare for the DPDPA amendments taking effect on 1 January 2027.

4 earlier distinct updates
Periodic update · new data 2026-11-04

House Bill 380 introduces a documented due-diligence duty for controllers with respect to third parties that receive personal data, effective 1 January 2027. Where the Act previously relied on a standard-contract requirement between controllers and the parties they share data with, the amendment requires controllers to carry out and document due diligence of those third parties, including the use of vendor questionnaires and review of supporting documentation.

Outlook

The move from a contract-only standard to a documented-diligence standard will require controllers to build or formalise a vendor-assessment process ahead of the 1 January 2027 effective date, since a signed data-processing agreement alone will no longer be sufficient evidence of compliance with the third-party data-sharing requirement.

Periodic update · new data 2026-10-25

Two distinct controller-duty developments arrived through separate instruments. House Bill 381, effective upon signing on 2 September 2026, requires notice to the Delaware Attorney General within 60 days of a controller determining that a data breach has occurred. The same measure narrows a previously broader carve-out: compliance with breach-notification procedures established under sectoral laws such as HIPAA or the Gramm-Leach-Bliley Act now satisfies only the 60-day timing element of Delaware's breach-notification statute, not the statute's full set of requirements. Controllers that had previously treated HIPAA or GLBA compliance as a complete substitute for Delaware's own breach-notice obligations should treat that substitution as now partial rather than total.

Separately, House Bill 380 lowers the threshold at which a controller must conduct a Data Protection Assessment from 100,000 to 50,000 Delaware consumers, for controllers that sell personal data, process it for targeted advertising, or process sensitive data, effective 1 January 2027. This roughly halves the scale at which the assessment obligation attaches and will bring materially more mid-sized controllers within its scope once effective.

The breach-notification changes are already operative; the Data Protection Assessment threshold change is enacted but not yet effective, taking hold only from 1 January 2027. Controllers should treat these as two separate compliance clocks rather than a single unified change date.

Outlook

For the remainder of 2026, the operative controller duty to track is the narrowed sectoral breach-notification carve-out under House Bill 381. From 1 January 2027, the lowered Data Protection Assessment threshold becomes the item to track, bringing a substantially larger population of controllers into its scope.

Periodic update · new data 2026-10-18

House Bill 380 introduces what is likely the most operationally consequential new duty in this cycle's Delaware privacy development: a mandatory third-party due-diligence and contracting regime. Controllers must conduct reasonable due diligence of third parties to which personal data is disclosed for sale or for targeted advertising, and must enter into contracts obligating those third parties to provide equivalent DPDPA protections to the data they receive. This due-diligence duty extends the practical reach of the DPDPA well beyond the controller itself, since a controller's compliance now depends in part on verifying and contractually binding the privacy practices of its data-sale and advertising counterparties.

Alongside this, HB 380 lowers the threshold that triggers a mandatory data protection assessment (DPIA) from 100,000 to 50,000 consumers. This halving of the DPIA trigger threshold means a materially larger population of controllers will need to conduct and document formal risk assessments for processing activities that present a heightened risk of harm, a category that typically includes profiling, sensitive-data processing, and targeted advertising, among others under the Act's existing assessment triggers.

Separately, and already in force rather than pending the January 2027 effective date, Delaware's breach-notification statute (HB 381) requires notice to the Attorney General within 60 days of determining that a breach occurred, with substitute notice available as a compliance mechanism where direct notice is impracticable. This breach-notification duty is confirmed as currently operative, distinguishing it from the HB 380 amendments, which remain enacted but not yet effective.

The combination of these three duties (third-party due diligence and contracting, a lowered DPIA threshold, and an already-active breach-notification regime) collectively raises the operational compliance burden on Delaware-regulated controllers across the full data lifecycle: how data is shared downstream, how high-risk processing is assessed internally, and how breaches are reported externally.

Outlook

The third-party due-diligence and contracting duty is likely to be the most resource-intensive new obligation for controllers to operationalize ahead of the January 1, 2027 effective date, since it requires both a diligence process for vetting data recipients and a contracting update across any existing data-sale or advertising relationships. The lowered DPIA threshold will similarly expand the population of processing activities requiring formal documentation. Because the breach-notification duty under HB 381 is already in force, controllers facing an actual breach event today are already subject to the 60-day Attorney General notice requirement, independent of the broader HB 380 timeline.

Periodic update · new data 2026-10-04

HB380 adds substantial new obligations to Delaware's controller and processor duties, while HB381, already in force, strengthens breach-notification duties specifically. On the HB380 side, the amendment is reported to impose new, prescriptive data protection impact assessment requirements where a controller engages in profiling in furtherance of automated decisions producing legal or similarly significant effects for a consumer. This moves Delaware's DPIA obligation from a more general risk-assessment duty toward a more prescriptive standard specifically targeted at consequential automated-decision profiling.

HB380 is also reported to require binding contracts between a controller and third parties receiving sold or disclosed personal data, specifying limited purposes and obligating the third party to compliance, with controllers required to conduct reasonable due diligence on such third parties before the disclosure. This creates a flow-down obligation that did not previously exist in the same form, placing an affirmative due-diligence burden on the controller rather than relying solely on contractual warranties from the receiving third party.

On the breach-notification side, HB381 is already in force. It requires that where an organization cannot, through reasonable diligence, identify within 60 days which Delaware residents' personal information was involved in a breach, the organization must notify the Delaware Attorney General within 60 days of making that determination, and Attorney General notice is now a required component of substitute notice. HB381 is also reported to have narrowed the prior entity-level GLBA/HIPAA compliance safe harbor, so that a regulated person is now deemed compliant only with the 60-day timing rule of the breach-notification statute's substitute-notice provision, rather than with the breach-notification chapter as a whole. This is a meaningful narrowing: entities that previously relied on a broad GLBA or HIPAA-based safe harbor to satisfy the entirety of Delaware's breach-notification chapter can no longer assume that reliance covers more than the specific 60-day timing rule.

Outlook

HB381's breach-notification changes, including the early Attorney General notice duty and the narrowed safe harbor, are already in force and binding today. HB380's DPIA and third-party contracting duties do not take effect until January 1, 2027. The exact statutory citation and section for HB380's new DPIA and profiling-opt-out provisions has not been independently verified against the engrossed bill text this cycle, so the precise contours of the prescriptive DPIA standard should be confirmed against the final statutory text as the effective date approaches.

Sources and claims (16)
  1. Probable DataGuidance — Controllers must conduct data protection impact assessments (DPIAs) for high-risk processing activities under the DPDPA. observed
  2. Probable State of Delaware — No dedicated Data Protection Officer appointment threshold analogous to GDPR Art. 37-39 was identified in the DPDPA or AG guidance. observed
  3. Probable State of Delaware — Businesses are directed to inventory personal data collected, identify storage locations, and document access and third-party processor relationships, though no formal public Records-of-Processing-Activities filing requirement was confirmed. observed
  4. Probable State of Delaware — The DPDPA requires businesses to employ reasonable data security measures proportionate to the nature and sensitivity of the personal data collected, to prevent unauthorized access. observed
  5. Probable State of Delaware — Delaware's data breach notification statute, in effect since April 14, 2018, requires notice to affected Delaware residents and, where a breach affects 500 or more residents, additional notice to the Delaware Attorney General. observed
  6. Probable TrustSuperset — HB 380 Data Protection Assessment threshold — DPA threshold lowered from 100,000 to 50,000 Delaware consumers for controllers selling personal data, processing for targeted advertising, or processing sensitive data; effective 2027-01-01. observed
  7. Probable https://www.workplaceprivacyreport.com/2026/09/articles/consumer-privacy/delaware-consumer-privacy-and-data-breach-law-updates/ — HB 381 AG breach-notice duty — Notice to the Delaware Attorney General within 60 days of determining that a data breach occurred, effective upon signing 2026-09-02.
  8. Probable Workplace Privacy Report (Jackson Lewis) — HB 381 HIPAA/GLBA exemption narrowing — Compliance with regulator-established breach procedures under laws such as HIPAA or GLBA now satisfies only the 60-day timing requirement of Delaware's breach law, not the entirety of the state notification statute. observed
  9. Probable National Law Review — DPDPA data-protection-assessment trigger — HB 380 lowers the DPIA trigger threshold from 100,000 to 50,000 consumers observed
  10. Probable National Law Review — Delaware breach-notification law — HB 381 requires AG notice within 60 days of determining a breach occurred, including via substitute notice; already in force observed
  11. Probable https://www.morganlewis.com/pubs/2026/10/delaware-significantly-expands-its-consumer-data-privacy-law — DPDPA third-party disclosure duties — Controllers must conduct 'reasonable due diligence' of third parties to which personal data is disclosed for sale or targeted advertising, and enter contracts obligating equivalent DPDPA protections
  12. Probable Primary statutory record — HB 380 requires documented due diligence of third parties receiving personal data, going beyond the DPDPA's prior standard-contract requirement, effective 2027-01-01.
  13. Probable Paubox — Delaware breach-notification statute (Title 6, Ch. 12B) — Requires notice to the Delaware AG within 60 days of determining a breach occurred. observed
  14. Probable ZwillGen — HB380 creates a third-party due-diligence obligation under which a controller/processor disclosing data to a recipient is not deemed to have violated the DPDPA based on the recipient's independent violation, provided reasonable diligence and oversight were undertaken. observed
  15. Probable Paubox — Delaware breach-notification statute (Title 6, Ch. 12B) — HB381 requires notice to the Delaware AG within 60 days of determining a breach occurred, including where affected residents cannot yet be identified, in addition to the pre-existing 500-resident trigger. observed
  16. Probable National Law Review — Delaware breach-notification statute (Title 6, Ch. 12B) — HB381 narrows the prior GLBA/HIPAA compliance safe harbor so that compliance with a federal breach-notification procedure now satisfies only the 60-day timing requirement, not the statute's other provisions. observed

#

No comprehensive transfer-mechanism regime exists in this state statute; explicit gap consistent with the sectoral/hybrid US pattern.

Traffic-light rationale — RedNo comprehensive transfer-mechanism regime exists in this state statute; explicit gap consistent with the sectoral/hybrid US pattern.

Sub-modules (6)

Transfer mechanismsRed

No dedicated transfer-mechanism provisions were located; general contractual/security duties apply irrespective of data destination.

Claims (3):

  • The DPDPA does not contain an adequacy-decision framework, Standard Contractual Clauses regime, Binding Corporate Rules mechanism, or data-localisation mandate; cross-border transfer is governed only indirectly through the Act's general controller/processor contractual and security obligations.
  • DPDPA cross-border transfer provision — The DPDPA contains no cross-border data-transfer mechanism, adequacy test, or SCC/BCR equivalent; Delaware is a US state and operates no adequacy regime.
  • The DPDPA is a domestic statute with no cross-border transfer-control or data-localisation regime.

Adequacy receivedRed

Not applicable; US states do not receive adequacy decisions under this framework.

Adequacy grantedRed

No adequacy-granting mechanism exists under the DPDPA.

SCCs and BCRsRed

No SCC or BCR regime identified under the DPDPA.

Transfer impact assessmentRed

No transfer-impact-assessment requirement identified.

Data localisationRed

No data-localisation mandate identified under the DPDPA.

Category narrative 53 words

The DPDPA, consistent with the general US state-omnibus-privacy pattern, does not contain a GDPR-style cross-border transfer regime. No adequacy-decision mechanism, SCC/BCR framework, transfer-impact-assessment requirement, or data-localisation mandate was identified in the Act or AG guidance; cross-border transfer is regulated only indirectly via the Act's general contractual and security obligations on controllers and processors.

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

Sources and claims (3)
  1. Probable State of Delaware — The DPDPA does not contain an adequacy-decision framework, Standard Contractual Clauses regime, Binding Corporate Rules mechanism, or data-localisation mandate; cross-border transfer is governed only indirectly through the Act's general controller/processor contractual and security obligations. observed
  2. Probable Didomi — DPDPA cross-border transfer provision — The DPDPA contains no cross-border data-transfer mechanism, adequacy test, or SCC/BCR equivalent; Delaware is a US state and operates no adequacy regime. observed
  3. Uncertain Delaware Department of Justice — The DPDPA is a domestic statute with no cross-border transfer-control or data-localisation regime. observed

#

Financial and health carve-outs are clearly documented; several sub-modules (telecoms, credit-scoring, education, insurance) have no DE-specific overlay evidence.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA); federal GLBA/HIPAA/FCRA (deferred-to)
Traffic-light rationale — AmberFinancial and health carve-outs are clearly documented; several sub-modules (telecoms, credit-scoring, education, insurance) have no DE-specific overlay evidence.

Sub-modules (7)

Financial sector overlayAmber

Data maintained in compliance with GLBA is exempt from the DPDPA.

Claims (4):

  • The DPDPA does not apply to personal data maintained in compliance with the Gramm-Leach-Bliley Act, HIPAA, or the Fair Credit Reporting Act, as well as personal data processed for certain specified purposes.
  • HB 380 GLBA exemption narrowing — The DPDPA's Gramm-Leach-Bliley Act entity-level exemption is narrowed, bringing certain previously wholly-exempt financial institutions into partial scope from 2027-01-01; precise statutory conditions not confirmed this cycle.
  • DPDPA GLBA exemption — HB 380 narrows the DPDPA's entity-level exemption for GLBA-regulated financial institutions
  • HB380 narrows the DPDPA's GLBA entity-level exemption; businesses previously relying on it should re-examine applicability ahead of 2027-01-01.

Health sector overlayAmber

Data maintained in compliance with HIPAA is exempt from the DPDPA.

Claims (2):

  • The DPDPA does not apply to personal data maintained in compliance with the Gramm-Leach-Bliley Act, HIPAA, or the Fair Credit Reporting Act, as well as personal data processed for certain specified purposes.
  • HB 380 adds a health-data limited-data-set exemption tied to 45 CFR § 164.514(e), effective 2027-01-01.

Telecoms and eprivacyRed

No Delaware-specific telecoms/ePrivacy overlay was identified.

Employment dataAmber

The DPDPA excludes personal data processed in an employment context (e.g., job applications) from its consumer protections.

Claims (3):

  • The DPDPA applies to Delawareans acting in an individual or household context and does not protect an individual acting in an employment context, such as applying for a job.
  • DPDPA employment-data carve-out — HB 380 brings employee and applicant data back within scope when processed for profiling or reports used in consequential decisions
  • HB 380 narrows the DPDPA's employment-context exclusion as to profiling and reports, effective 2027-01-01.

Credit and scoringAmber

The Fair Credit Reporting Act exemption covers certain credit-related data; no DE-specific credit-scoring overlay beyond this was identified.

Claims (1):

  • The DPDPA does not apply to personal data maintained in compliance with the Gramm-Leach-Bliley Act, HIPAA, or the Fair Credit Reporting Act, as well as personal data processed for certain specified purposes.

educationRed

No Delaware-specific education-sector data overlay was identified.

insuranceRed

No Delaware-specific insurance-sector data overlay was identified.

Category narrative 44 words

The DPDPA exempts data governed by GLBA, HIPAA and FCRA and excludes employment-context personal data (e.g., job applicants) from its consumer-rights framework, deferring to those federal sectoral regimes. No Delaware-specific overlays for telecoms/ePrivacy, credit-scoring, education, or insurance were identified beyond these general federal deferrals.

Periodic update · new data 2026-11-08

House Bill 380 narrows the DPDPA's entity-level exemption for businesses subject to the Gramm-Leach-Bliley Act. Financial institutions that have relied on that exemption to treat themselves as outside the DPDPA's scope are understood to need to re-examine that reliance ahead of the amendment's 1 January 2027 effective date, since the narrowed exemption may no longer cover the full scope of their data processing.

Outlook

Financial-sector entities with Delaware consumer data should reassess GLBA-exemption reliance before the amendment takes effect on 1 January 2027.

5 earlier distinct updates
Periodic update · new data 2026-11-04

Three sector-specific changes arrive together in House Bill 380, each effective 1 January 2027. First, the Act's broad, entity-level exemption for Gramm-Leach-Bliley Act-regulated financial institutions is replaced with narrower, activity-specific exemptions covering specified financial, banking and insurance functions. Second, a new health-data exemption is added for information held in a limited data set protected under the federal regulation at 45 CFR § 164.514(e). Third, the Act's exclusion of employment-context data from the definition of "consumer" is narrowed so that data processed in connection with profiling and reports about employees is no longer automatically carved out.

Outlook

Financial-sector entities that previously relied on blanket GLBA-based exemption will need to identify which of their specific activities still qualify for exemption under the narrower replacement provisions, while employers will need to review whether employee-related profiling and reporting activities now fall within the Act's scope for the first time once the narrowed employment exclusion takes effect.

Periodic update · new data 2026-10-25

Reports indicate that House Bill 380 narrows the Gramm-Leach-Bliley Act entity-level exemption under the Delaware Personal Data Privacy Act, bringing certain financial institutions that had previously been wholly exempt into partial scope of the Act, effective 1 January 2027. This would be a notable sectoral development, since GLBA entity-level exemptions have historically removed entire financial institutions from state comprehensive-privacy-law scope rather than narrowing their coverage incrementally. However, the precise statutory conditions under which this narrowing operates, including which specific financial-institution activities or data categories move into scope, could not be confirmed against primary text, and the finding is accordingly reported as understood rather than settled.

This development, if confirmed as described, would align Delaware with a broader trend among US state comprehensive privacy laws toward narrowing what had been treated as blanket sectoral exemptions, rather than leaving financial institutions entirely outside the reach of general consumer-privacy obligations.

Outlook

Confirming the precise statutory mechanism for the GLBA exemption narrowing, ideally against direct citation to the amended Delaware Code provision, is the clear open item here, and should be prioritised ahead of the 1 January 2027 effective date so that affected financial institutions have clarity on their compliance obligations in time.

Periodic update · new data 2026-10-18

Two sectoral scope changes are reported under House Bill 380, both moving in the direction of narrowing existing carve-outs rather than widening them. First, HB 380 is reported to narrow the DPDPA's entity-level exemption for GLBA-regulated financial institutions. Entity-level exemptions of this kind typically remove a covered entity from the statute's scope entirely based on its regulatory classification, regardless of the specific data-processing activity at issue; a narrowing of this exemption means some financial institutions that previously operated entirely outside DPDPA scope by virtue of GLBA regulation may now find some or all of their Delaware-consumer data processing activity brought within scope. The precise statutory mechanism and pinpoint citation for this narrowing were not located in retrieved commentary this cycle, so this finding is held at probable rather than confirmed confidence.

Second, and confirmed at higher confidence, HB 380 brings employee and applicant data back within the DPDPA's scope when that data is processed for profiling purposes or used in reports that inform consequential decisions about the employee or applicant. This reverses, at least partially, a broader employment-data carve-out that had previously placed most employee and job-applicant data outside the Act's scope regardless of how it was used. The specific carve-back for profiling and consequential-decision contexts suggests the legislature identified employment-related automated decision-making and algorithmic scoring as a particular area of concern meriting renewed statutory coverage, even while leaving other employment-data processing outside scope.

Both changes reflect a broader pattern in this cycle's Delaware privacy developments: narrowing exemptions and lowering thresholds, rather than creating new exemptions or raising thresholds, consistent with the overall tightening trajectory of HB 380 as a package.

Outlook

Financial institutions relying on the GLBA entity-level exemption, and employers relying on the general employment-data carve-out for profiling-adjacent HR processes such as automated candidate screening or performance-based consequential decisions, should reassess their DPDPA exposure ahead of the January 1, 2027 effective date. The GLBA exemption narrowing in particular warrants closer legal review once the precise statutory text becomes available, given the gap identified in this cycle's sourcing.

Periodic update · new data 2026-10-11

House Bill 380's amendment to the Delaware Personal Data Privacy Act operates as a sectoral carve-out: by excluding individuals acting in a commercial or employment context from the statute's "consumer" definition, the amendment removes employment-related personal data processing from the Act's consumer-rights coverage, joining a pattern found in several other state comprehensive privacy statutes that distinguish employment and business-to-business data from ordinary consumer data. The amendment was signed September 2, 2026 and does not alter the Act's general applicability thresholds, which continue to apply to entities controlling or processing the personal data of not less than 35,000 Delaware residents, or not less than 10,000 residents combined with more than 20 percent of gross revenue from data sales.

Outlook

As an amendment narrowing coverage rather than introducing a wholly new sectoral regime, the practical sectoral effect will be concentrated in employment and human-resources data processing by Delaware-covered entities; no additional sector-specific carve-out beyond the employment context was identified this cycle.

Periodic update · new data 2026-10-04

HB380 materially narrows the DPDPA's financial-sector exemption. The amendment removes the Act's prior entity-level GLBA exemption, which had covered any affiliate subject to GLBA regardless of whether the specific data at issue was itself GLBA-regulated, and replaces it with a narrower exemption limited specifically to banks, credit unions and savings associations. In its place, HB380 is reported to create new, distinct exemptions for insurance-related entities and agents, and for broker-dealers and investment-adviser representatives. The data-level GLBA exemption, which exempts specific GLBA-regulated data regardless of the entity holding it, is reported to remain unchanged.

The practical effect of this narrowing is that financial-sector affiliates that previously relied on an entity-wide exemption because some part of their corporate family was GLBA-regulated may no longer qualify for that broad exemption once HB380 takes effect. Instead, exemption eligibility becomes more entity-specific, tied to whether the entity itself is a bank, credit union, savings association, insurance entity or agent, broker-dealer, or investment-adviser representative, rather than tied to corporate affiliation with a GLBA-regulated entity.

Outlook

The narrowed financial-sector exemption takes effect January 1, 2027. Financial-sector entities and their affiliates operating in Delaware that have historically relied on the broad entity-level GLBA exemption should expect to need to reassess their exemption status under the narrower, entity-specific categories HB380 introduces, ahead of that effective date.

Sources and claims (8)
  1. Probable State of Delaware — The DPDPA does not apply to personal data maintained in compliance with the Gramm-Leach-Bliley Act, HIPAA, or the Fair Credit Reporting Act, as well as personal data processed for certain specified purposes. observed
  2. Probable State of Delaware — The DPDPA applies to Delawareans acting in an individual or household context and does not protect an individual acting in an employment context, such as applying for a job. observed
  3. Uncertain TrustSuperset — HB 380 GLBA exemption narrowing — The DPDPA's Gramm-Leach-Bliley Act entity-level exemption is narrowed, bringing certain previously wholly-exempt financial institutions into partial scope from 2027-01-01; precise statutory conditions not confirmed this cycle. observed
  4. Probable National Law Review — DPDPA GLBA exemption — HB 380 narrows the DPDPA's entity-level exemption for GLBA-regulated financial institutions observed
  5. Probable https://natlawreview.com/article/privacy-filter-briefing-privacy-law-and-policy-october-2026 — DPDPA employment-data carve-out — HB 380 brings employee and applicant data back within scope when processed for profiling or reports used in consequential decisions
  6. Probable Delaware General Assembly — HB 380 adds a health-data limited-data-set exemption tied to 45 CFR § 164.514(e), effective 2027-01-01. observed
  7. Probable RecordingLaw — HB 380 narrows the DPDPA's employment-context exclusion as to profiling and reports, effective 2027-01-01. observed
  8. Probable Hunton Andrews Kurth Privacy & Cybersecurity Law Blog (profiling/GLBA reference) — HB380 narrows the DPDPA's GLBA entity-level exemption; businesses previously relying on it should re-examine applicability ahead of 2027-01-01. observed

#

Opt-out signal and dark-pattern provisions are confirmed and in force; clean-room and direct-marketing-specific rules are gaps.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA)
Traffic-light rationale — AmberOpt-out signal and dark-pattern provisions are confirmed and in force; clean-room and direct-marketing-specific rules are gaps.

Sub-modules (6)

Cookies and trackersAmber

No dedicated cookie-consent statute distinct from the general personal-data consent framework was identified.

Dark patternsGreen

Consent obtained through deceptive webpage design is expressly excluded as valid consent.

Claims (1):

  • Acceptance of broad terms of service, hovering over or pausing on content, and agreement obtained through deceptive webpage design ('dark patterns') are not considered valid consent under the DPDPA.

Opt out signalsGreen

Universal opt-out mechanisms must be honored by controllers as valid consumer opt-out requests as of January 1, 2026.

Claims (3):

  • Beginning January 1, 2026, controllers must recognize universal opt-out mechanisms as valid consumer requests to opt out of personal-data processing across multiple websites at once.
  • DPDPA universal opt-out mandate — As of January 1, 2026, controllers must recognize universal opt-out signals such as the Global Privacy Control
  • Under 6 Del.C. § 12D-106(e), controllers must recognise universal opt-out mechanisms as of 2026-01-01.

Clean rooms and dcrRed

No clean-room or data-collaboration-room rules were identified under the DPDPA.

Cross context advertisingGreen

Consumers may opt out of processing for targeted advertising and automated profiling.

Claims (1):

  • Consumer rights under the DPDPA include opt-out options for targeted advertising and automated profiling.

Direct marketingAmber

No DE-specific direct-marketing consent/suppression regime distinct from the general sale/targeted-advertising opt-out was identified.

Category narrative 55 words

Consumers may opt out of the sale of personal data and processing for targeted advertising and profiling. Universal opt-out mechanisms (GPC-style signals) became mandatory for controllers to recognize as of January 1, 2026. Dark-pattern-induced consent is expressly invalid. No dedicated cookie statute, clean-room/data-collaboration rules, or direct-marketing-specific suppression regime beyond the general opt-out right was identified.

No periodic updates recorded in this cycle

Sources and claims (5)
  1. Probable State of Delaware — Acceptance of broad terms of service, hovering over or pausing on content, and agreement obtained through deceptive webpage design ('dark patterns') are not considered valid consent under the DPDPA. observed
  2. Probable State of Delaware — Beginning January 1, 2026, controllers must recognize universal opt-out mechanisms as valid consumer requests to opt out of personal-data processing across multiple websites at once. observed
  3. Probable DataGuidance — Consumer rights under the DPDPA include opt-out options for targeted advertising and automated profiling. observed
  4. Probable Cookiebot — DPDPA universal opt-out mandate — As of January 1, 2026, controllers must recognize universal opt-out signals such as the Global Privacy Control observed
  5. Probable RecordingLaw — Under 6 Del.C. § 12D-106(e), controllers must recognise universal opt-out mechanisms as of 2026-01-01. observed

#

Biometric/genetic and minor-profiling protections are confirmed; AI-specific risk assessment and surveillance-carveout detail are gaps.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA)
Traffic-light rationale — AmberBiometric/genetic and minor-profiling protections are confirmed; AI-specific risk assessment and surveillance-carveout detail are gaps.

Sub-modules (6)

Profiling restrictionsGreen

Consumers may opt out of processing for automated profiling; minors under 18 require opt-in consent for related targeted-advertising/sale processing.

Claims (3):

  • The DPDPA requires controllers to obtain opt-in consent before selling a consumer's personal data or processing personal data for targeted advertising when the consumer is under 18 years old.
  • HB 380 AI-profiling provision — Secondary commentary reports that HB 380 expands Delaware's regime around AI-driven profiling and inferred sensitive information, but the specific DPDPA article was not located and confirmed this cycle.
  • DPDPA — HB380 expands the consumer right to opt out of profiling used in automated decisions and expands the access right to include certain inferences derived from personal data.

Automated decision making transparencyAmber

No explicit ADM-explanation right distinct from the general profiling opt-out was confirmed.

Claims (1):

  • HB 380 adverse-action human-review requirement — A business selling consumer reports used in adverse-action decisions must contractually require the recipient to send the resident an adverse-action notice describing the data relied on, and offer a human review where feasible, effective 2027-01-01.

AI risk assessmentsRed

No AI-specific risk-assessment regime (EU AI Act analogue) was identified; DPIA obligations cover high-risk processing generally.

Claims (1):

  • No AI-system-specific risk-assessment regime akin to the EU AI Act or state AI-transparency statutes was identified within the DPDPA; its DPIA obligations address 'high-risk processing' generally rather than AI systems specifically.

Biometric regimeGreen

Biometric data used to uniquely identify an individual is classified as sensitive data requiring consent.

Claims (1):

  • Genetic and biometric data used to uniquely identify an individual are classified as sensitive data under the DPDPA, requiring consumer consent prior to collection or processing.

Genetic dataGreen

Genetic data used to uniquely identify an individual is classified as sensitive data requiring consent.

Claims (1):

  • Genetic and biometric data used to uniquely identify an individual are classified as sensitive data under the DPDPA, requiring consumer consent prior to collection or processing.

State surveillance carveoutsAmber

The Act permits denial of consumer-rights requests where necessary to comply with federal, state, or local law, functioning as a general legal-compliance carve-out rather than a dedicated national-security exemption.

Claims (1):

  • A controller may deny a consumer's rights request where fulfilling it would restrict the controller's ability to comply with federal, state, or local law.
Category narrative 52 words

Biometric and genetic data used to uniquely identify an individual are classified as sensitive data requiring consent. Minors under 18 receive opt-in-consent protection against profiling-adjacent targeted advertising and data sale. No AI-specific risk-assessment regime distinct from general high-risk-processing DPIAs, and no dedicated state-surveillance carve-out beyond the Act's general legal-compliance exception, were identified.

Periodic update · new data 2026-11-08

House Bill 380 is reported to expand the consumer right to opt out of profiling used in connection with automated decisions, and to extend the access right to cover certain inferences drawn from a consumer's personal data, broadening both the opt-out and transparency dimensions of algorithmic processing oversight under the DPDPA.

Outlook

These profiling and inference-access expansions take effect with the rest of HB380 on 1 January 2027.

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

House Bill 380 introduces a new adverse-action transparency requirement, effective 1 January 2027: a business that sells consumer reports used in adverse-action decisions must contractually require the recipient of that report to send the affected Delaware resident an adverse-action notice describing the data relied upon, and to offer a human review of the decision where feasible. This is the clearest confirmed algorithmic-governance development of the cycle, extending transparency and human-review expectations specifically into the consumer-reporting and adverse-action context.

Separately, secondary commentary reports that House Bill 380 more broadly expands Delaware's regime around AI-driven profiling and inferred sensitive information. This broader characterisation is reported with less confidence: the specific provision of the Act implementing an expanded AI-profiling or inferred-sensitive-information rule was not located and confirmed, and the claim should be read as reported commentary pending that confirmation rather than as a verified statutory feature.

Taken together, the confirmed adverse-action human-review requirement represents a concrete, narrowly scoped algorithmic-transparency obligation tied to consumer reporting, while the broader claim of an AI-profiling expansion remains an open item requiring primary-source verification before it can be treated as a settled feature of Delaware's regime.

Outlook

Locating and confirming the specific statutory provision said to expand AI-profiling and inferred-sensitive-information coverage is the priority open item here, ahead of the 1 January 2027 effective date for the confirmed adverse-action notice and human-review requirement.

Periodic update · new data 2026-10-18

The principal algorithmic-governance development in Delaware this cycle is House Bill 380's removal of the word solely from the DPDPA's profiling opt-out provision. Under the pre-amendment Act, a consumer's right to opt out of profiling used in furtherance of decisions producing legal or similarly significant effects applied only where that decision was made solely through automated processing. By removing solely, HB 380 extends the opt-out right to decisions that are substantially automated but include some human-review step, which is a materially broader conception of what counts as an automated decision for opt-out purposes.

This change addresses a well-documented gap in solely-automated-decision frameworks generally: a business could previously defeat an automated-decision opt-out right by inserting a largely perfunctory human review step into an otherwise fully automated decision pipeline, since the decision would then no longer be made solely through automated processing. Delaware's amendment closes this gap by extending opt-out coverage to decisions with a human-in-the-loop element, provided the decision still produces a legal or similarly significant effect.

No separate biometric-data-specific or surveillance-specific statutory provision was identified in this cycle's Delaware claim set beyond this profiling-opt-out change; the governance development here is specifically an automated-decision-making opt-out expansion rather than a biometric-identifier or surveillance-technology-specific regime.

Outlook

Businesses using decision-making pipelines that combine automated processing with a human review step to produce legal or similarly significant effects on Delaware consumers should reassess whether their human-review step would previously have placed them outside the profiling opt-out's scope, since that basis for exclusion is removed once HB 380 takes effect January 1, 2027. This reassessment is likely to be most relevant for employment, credit, insurance, and similarly consequential decision categories where a human reviewer currently signs off on an otherwise algorithmically generated recommendation.

Periodic update · new data 2026-10-04

HB380 is reported to broaden the scope of profiling activity subject to consumer opt-out rights under the DPDPA. The amendment removes references to decisions being solely automated, which potentially expands opt-out coverage to profiling-based decisions that involve some degree of human review alongside automated processing, rather than only fully automated decisions. HB380 additionally prohibits profiling that violates federal or state anti-discrimination law, an explicit anti-discrimination backstop layered onto the algorithmic-governance framework.

No Delaware-specific biometric-data provision change was identified this cycle. The algorithmic-governance signal is accordingly concentrated on the profiling opt-out expansion and the anti-discrimination prohibition, both of which flow from the same HB380 amendment rather than from distinct biometric or surveillance-specific legislative action.

Outlook

The broadened profiling opt-out and anti-discrimination prohibition take effect January 1, 2027, alongside HB380's other amendments. How far the removal of the solely automated qualifier extends opt-out rights in practice, particularly for hybrid human-and-automated decision processes, is not yet settled and will depend on how the amendment is applied once in force.

Sources and claims (7)
  1. Probable State of Delaware — The DPDPA requires controllers to obtain opt-in consent before selling a consumer's personal data or processing personal data for targeted advertising when the consumer is under 18 years old. observed
  2. Probable DataGuidance — No AI-system-specific risk-assessment regime akin to the EU AI Act or state AI-transparency statutes was identified within the DPDPA; its DPIA obligations address 'high-risk processing' generally rather than AI systems specifically. observed
  3. Probable State of Delaware — Genetic and biometric data used to uniquely identify an individual are classified as sensitive data under the DPDPA, requiring consumer consent prior to collection or processing. observed
  4. Probable State of Delaware — A controller may deny a consumer's rights request where fulfilling it would restrict the controller's ability to comply with federal, state, or local law. observed
  5. Uncertain National Law Review — HB 380 AI-profiling provision — Secondary commentary reports that HB 380 expands Delaware's regime around AI-driven profiling and inferred sensitive information, but the specific DPDPA article was not located and confirmed this cycle. observed
  6. Probable TrustSuperset — HB 380 adverse-action human-review requirement — A business selling consumer reports used in adverse-action decisions must contractually require the recipient to send the resident an adverse-action notice describing the data relied on, and offer a human review where feasible, effective 2027-01-01. observed
  7. Probable Hunton Andrews Kurth Privacy & Cybersecurity Law Blog (profiling/GLBA reference) — DPDPA — HB380 expands the consumer right to opt out of profiling used in automated decisions and expands the access right to include certain inferences derived from personal data. observed

#

Minor-specific protections are clearly documented and in force; education-settings and dependent-adults sub-modules are explicit gaps.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA); federal COPPA (referenced)
Traffic-light rationale — GreenMinor-specific protections are clearly documented and in force; education-settings and dependent-adults sub-modules are explicit gaps.

Sub-modules (5)

Age verificationAmber

No standalone age-verification mandate distinct from the under-18 opt-in-consent trigger was identified.

Claims (1):

  • DPDPA — A secondary source reports HB380 requires a separate consent path for teen privacy, but the pinpoint statutory provision and age threshold were not confirmed against a primary-source excerpt this cycle.

Minor profiling bansGreen

Opt-in consent is required before selling or using a under-18 consumer's data for targeted advertising, restricting default profiling-adjacent uses.

Claims (1):

  • In addition to protections afforded adults, Delaware law provides additional protections for children and teens under 18, including a requirement of opt-in consent before selling their personal data or using it for targeted advertising.

Education settingsRed

No Delaware-specific education-sector/student-data provisions were identified within the DPDPA.

Dependent adultsRed

No Delaware-specific dependent-adult (elderly/incapacitated) protections were identified within the DPDPA.

Category narrative 35 words

Delaware provides children and teens under 18 additional protections beyond adults, including opt-in consent for sale/targeted-advertising processing and parental/guardian exercise of consumer rights, alongside COPPA-referenced parental-consent duties. No DE-specific education-setting or dependent-adult provisions were identified.

No periodic updates recorded in this cycle

Sources and claims (3)
  1. Probable State of Delaware — Where a child's personal data is processed, the child's parent or legal guardian may exercise the DPDPA's consumer rights on the child's behalf, and controllers must follow COPPA parental-consent requirements. observed
  2. Probable State of Delaware — In addition to protections afforded adults, Delaware law provides additional protections for children and teens under 18, including a requirement of opt-in consent before selling their personal data or using it for targeted advertising. observed
  3. Uncertain OneTrust — DPDPA — A secondary source reports HB380 requires a separate consent path for teen privacy, but the pinpoint statutory provision and age threshold were not confirmed against a primary-source excerpt this cycle. observed

#

Enforcement powers and penalties are clear and in force; the pending HB 380 amendment's enactment status is an unresolved material development within the 180-day window, and regulator funding/capacity data is a gap.

Primary frameworkDelaware Personal Data Privacy Act (DPDPA)
Traffic-light rationale — AmberEnforcement powers and penalties are clear and in force; the pending HB 380 amendment's enactment status is an unresolved material development within the 180-day window, and regulator funding/capacity data is a gap.

Sub-modules (6)

Regulator powers and penaltiesGreen

Civil penalties up to $10,000 per violation, plus injunctive relief, restitution, and disgorgement, are available to the Attorney General.

Claims (7):

  • Entities or individuals that violate the DPDPA may face civil penalties up to $10,000 per violation, and the Attorney General can additionally seek injunctive relief, restitution, and/or disgorgement.
  • Delaware Personal Data Privacy Act — The DPDPA's mandatory 60-day cure period expired on January 1, 2026; thereafter the Delaware DOJ may grant cure opportunities at its discretion based on the number, nature, and severity of violations.
  • Delaware Personal Data Privacy Act — fines up to $10,000 per violation, prosecuted under 29 Del. C. Ch. 25, Subch. II
  • DPDPA enforcement framework — Violations are a per se Consumer Fraud Act violation, enforced exclusively by the DOJ with no private right of action; penalties up to $10,000 per violation; mandatory 60-day cure period sunset January 1, 2026
  • DPDPA cure-period sunset — Since 2026-01-01, the DPDPA's mandatory 60-day cure period has sunset; the Delaware DOJ may, at its discretion, offer a cure opportunity before enforcement, weighing violation count, entity size/complexity, and likelihood of consumer harm. Penalties reach up to $10,000 per violation as a per se violation of the Delaware Consumer Fraud Act.
  • A DPDPA violation is a per se violation of the Delaware Consumer Fraud Act, carrying civil penalties up to $10,000 per willful violation.
  • Delaware Consumer Fraud Act (Title 6, Ch. 25, Subch. II) — A DPDPA violation is deemed an unlawful practice under the Consumer Fraud Act; a willful violation can carry civil penalties of up to USD 10,000 per violation, with no DPDPA-specific fine schedule.

Enforcement activity indexAmber

No specific published enforcement actions/fines under the DPDPA were located as of this run; enforcement began January 1, 2025.

Claims (4):

  • Delaware DOJ privacy enforcement — DOJ is conducting an 'intense amount of work' on privacy enforcement not yet publicly disclosed, with announcements possibly forthcoming
  • Delaware DOJ DPDPA enforcement activity — As of the most recent secondary review located, the Delaware DOJ had not publicly announced a formal DPDPA enforcement action; early posture has focused on outreach and compliance education.
  • As of reporting dated to approximately May 2026, the Delaware DOJ had not publicly announced a formal DPDPA enforcement action.
  • Delaware Department of Justice — As of the most recent secondary reporting reached this cycle, the Delaware DOJ has not publicly announced a formal DPDPA enforcement action; early posture has focused on outreach and compliance education.

Regulator funding and capacityRed

No specific headcount or budget figures for DPDPA enforcement within the Consumer Protection Unit were located.

Claims (1):

  • No specific headcount, budget, or staffing figures for DPDPA enforcement within the Delaware DOJ Consumer Protection Unit were located in reviewed sources.

Collective redress and class actionsAmber

Absent a private right of action, collective redress is limited to Attorney General complaint channels rather than consumer-initiated class actions.

Claims (1):

  • Because the DPDPA lacks a private right of action, consumer complaints are channeled to the Attorney General's office ([email protected]) rather than through consumer-initiated class actions.

Private right of actionAmber

The DPDPA does not include a private cause of action; private citizens cannot sue directly under the Act.

Claims (2):

  • The DPDPA does not include a private cause of action; private citizens are not entitled to file lawsuits or enforce legal rights directly under the Act.
  • DPDPA private right of action — The DPDPA creates no private right of action; individuals cannot sue controllers directly and must instead file a complaint with the Delaware DOJ.

Recent developments 180dAmber

HB 380, introduced April 16, 2026, would amend the DPDPA (lower thresholds, expanded rights, January 1, 2027 effective date) and was reported to have passed the Legislature by June 2026; gubernatorial signature is unconfirmed.

Claims (1):

  • House Bill No. 380, introduced to the Delaware House on April 16, 2026, would amend the DPDPA by lowering the applicability threshold to 10,000 consumers (or 5,000 with significant data-sale revenue), expand access and profiling opt-out rights, and take effect January 1, 2027; the bill was reported to have passed the Legislature by June 2026, but gubernatorial signature was not confirmed as of this run.
Category narrative 90 words

The Attorney General may seek civil penalties up to $10,000 per violation plus injunctive relief, restitution and/or disgorgement. A mandatory 60-day right-to-cure period applied through December 31, 2025, after which cure is discretionary. The DPDPA carries no private right of action, so redress runs solely through AG complaint channels rather than class actions. A pending amendment, HB 380 (introduced April 16, 2026; reported passed by the Legislature by June 2026), would lower thresholds and expand rights effective January 1, 2027, but gubernatorial signature was not confirmed as of this run.

Periodic update · new data 2026-11-04

Enforcement of the Delaware Personal Data Privacy Act remains the exclusive province of the Delaware Department of Justice under 6 Del.C. § 12D-111; the Act affords no private right of action. A violation is treated as a per se violation of the Delaware Consumer Fraud Act, carrying civil penalties of up to $10,000 per willful violation. As of the most recent secondary reporting available, dated to approximately May 2026, the Department of Justice had not publicly announced any formal enforcement action under the Act.

Outlook

The absence of announced enforcement activity to date should be read against the Act's broadening scope: as the lowered applicability thresholds and expanded sensitive-data rules take effect from 1 January 2027, a materially larger population of controllers will be within reach of the Department of Justice's exclusive enforcement authority, which may in turn shift the enforcement posture observed to date.

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

Since 1 January 2026, the Delaware Personal Data Privacy Act's mandatory 60-day cure period has sunset. Before that date, the Delaware Department of Justice was required to offer violators a 60-day opportunity to cure before pursuing enforcement; now, the Department may, at its discretion, offer a cure opportunity, weighing the number of violations, the entity's size and complexity, and the likelihood of consumer harm in deciding whether to do so. Penalties for violations reach up to $10,000 per violation, treated as a per se violation of the Delaware Consumer Fraud Act, which gives the Attorney General access to that statute's broader enforcement toolkit.

As of the most recent secondary-source review available, the Delaware Department of Justice had not publicly announced a formal enforcement action under the Act. Its early posture is reported as having focused on outreach and compliance education rather than litigation, though this should be read as a point-in-time observation pending confirmation of whether any enforcement action has since been announced, rather than a settled statement that no action will ever be taken.

The Act continues to create no private right of action: individual Delaware residents cannot sue controllers directly for violations and must instead file a complaint with the Department of Justice, which retains sole discretion over whether and how to pursue a matter. This is a standing structural feature of the Act's enforcement architecture, not a change, but it remains directly relevant context for understanding why enforcement activity, or its absence, rests entirely with the Department of Justice's own priorities rather than with any parallel civil-litigation channel.

Outlook

Whether the Department of Justice announces its first public enforcement action under the Act, now that the mandatory cure period has sunset and discretionary cure decisions depend on case-specific factors, is the principal item to track going forward.

Periodic update · new data 2026-10-18

Enforcement of the Delaware Personal Data Privacy Act rests exclusively with the Delaware Department of Justice. Violations constitute a per se violation of the state's Consumer Fraud Act, a structural choice that ties DPDPA enforcement to an existing, well-established consumer-protection enforcement framework rather than creating a freestanding privacy-enforcement mechanism. The Act provides no private right of action, meaning individual consumers cannot bring their own DPDPA claims; redress runs solely through DOJ enforcement action. Penalties can reach up to $10,000 per violation. A mandatory 60-day cure period, which had given controllers an opportunity to remedy a violation before facing enforcement, sunset on January 1, 2026, meaning the DOJ can now proceed directly to enforcement without first affording a cure opportunity.

Beyond the statutory enforcement architecture, there are indications that the Delaware DOJ is actively engaged in substantial privacy-related enforcement work that has not yet been publicly disclosed, with the possibility of forthcoming public announcements. This signal, while not itself a confirmed enforcement action, suggests that Delaware's enforcement posture may become considerably more visible in the near term, consistent with the broader pattern across HB 380 and HB 381 of a state legislature and enforcement apparatus moving toward a more active privacy-enforcement stance after a comparatively quiet period following the DPDPA's original enactment.

The sunset of the mandatory cure period is itself a meaningful enforcement-posture shift independent of any new statutory amendment: as of January 1, 2026, the DOJ's enforcement discretion is no longer constrained by a mandatory pre-enforcement remedy window, which structurally lowers the practical barrier to bringing an enforcement action for any violation identified going forward.

Outlook

The combination of the cure-period sunset and reported undisclosed DOJ enforcement activity suggests Delaware's privacy enforcement posture is shifting from largely dormant toward potentially active. Any forthcoming public enforcement announcement would be the first visible test of how the DOJ exercises its exclusive, no-private-right-of-action enforcement authority under the current statute, and would likely be closely watched as a bellwether for how aggressively Delaware intends to enforce the substantially expanded HB 380 amendments once they take effect January 1, 2027.

Periodic update · new data 2026-10-11

The Delaware Personal Data Privacy Act's enforcement and redress architecture is unchanged this cycle. The statute sets penalties at up to $10,000 per violation, prosecuted under Title 29 of the Delaware Code, Chapter 25, Subchapter II, with the Delaware Department of Justice holding exclusive enforcement authority. The Act continues to grant consumers no private right of action: an individual who believes the Act has been violated may only file a grievance with the Delaware DOJ rather than initiate a civil suit directly against the controller or processor. This enforcement structure governs the application of the new HB-380 employment-context exclusion as much as it governs the rest of the statute; because no private right of action exists, any dispute over whether a given individual or data-processing activity falls within or outside the new employment-context carve-out would be resolved, if at all, through a DOJ grievance process rather than private litigation.

Outlook

With enforcement concentrated exclusively in the Delaware DOJ and no private right of action available, the practical testing of the HB-380 carve-out's boundaries will depend on DOJ grievance-handling practice and any interpretive guidance the Department chooses to issue, rather than on case law developed through private suits.

Periodic update · new data 2026-10-04

Delaware's enforcement architecture for data protection remains concentrated entirely in the Attorney General's office. The Delaware Personal Data Privacy Act, like most recent state comprehensive-privacy statutes outside California, lacks a private right of action and a dedicated enforcement agency; enforcement runs through the Attorney General's general authority rather than a specialised privacy regulator. This cycle's amendments do not alter that basic architecture, but HB381, already in force since September 2, 2026, strengthens the enforcement surface specifically around breach notification.

HB381's early and independent Attorney General notice duty, triggered when an organization cannot identify affected Delaware residents within 60 days of a breach, gives the Attorney General's office a more timely enforcement trigger than previously existed, since notice to the Attorney General is no longer contingent on the organization first completing its full notification obligations to affected individuals. This is a genuine strengthening of the enforcement surface even though it operates within the existing AG-only enforcement model rather than creating a new enforcement mechanism or right of action.

Outlook

The DPDPA's AG-only enforcement model, with no private right of action, remains the baseline redress architecture for Delaware consumers notwithstanding this cycle's amendments. HB381's early AG breach-notice duty is already operative and gives the Attorney General earlier visibility into breaches affecting Delaware residents than the pre-amendment regime provided.

Sources and claims (16)
  1. Probable State of Delaware — Entities or individuals that violate the DPDPA may face civil penalties up to $10,000 per violation, and the Attorney General can additionally seek injunctive relief, restitution, and/or disgorgement. observed
  2. Uncertain State of Delaware — No specific headcount, budget, or staffing figures for DPDPA enforcement within the Delaware DOJ Consumer Protection Unit were located in reviewed sources. observed
  3. Probable State of Delaware — Because the DPDPA lacks a private right of action, consumer complaints are channeled to the Attorney General's office ([email protected]) rather than through consumer-initiated class actions. observed
  4. Probable State of Delaware — The DPDPA does not include a private cause of action; private citizens are not entitled to file lawsuits or enforce legal rights directly under the Act. observed
  5. Probable DataGuidance — House Bill No. 380, introduced to the Delaware House on April 16, 2026, would amend the DPDPA by lowering the applicability threshold to 10,000 consumers (or 5,000 with significant data-sale revenue), expand access and profiling opt-out rights, and take effect January 1, 2027; the bill was reported to have passed the Legislature by June 2026, but gubernatorial signature was not confirmed as of this run. observed
  6. Probable https://www.privacyon.com/blog/privacy-laws-in-delaware — Delaware Personal Data Privacy Act — The DPDPA's mandatory 60-day cure period expired on January 1, 2026; thereafter the Delaware DOJ may grant cure opportunities at its discretion based on the number, nature, and severity of violations.
  7. Probable Termly — Delaware Personal Data Privacy Act — fines up to $10,000 per violation, prosecuted under 29 Del. C. Ch. 25, Subch. II observed
  8. Probable https://www.osano.com/articles/delaware-personal-data-privacy-act-dpdpa — DPDPA enforcement framework — Violations are a per se Consumer Fraud Act violation, enforced exclusively by the DOJ with no private right of action; penalties up to $10,000 per violation; mandatory 60-day cure period sunset January 1, 2026
  9. Probable Privacy Daily — Delaware DOJ privacy enforcement — DOJ is conducting an 'intense amount of work' on privacy enforcement not yet publicly disclosed, with announcements possibly forthcoming observed
  10. Probable Centraleyes — DPDPA cure-period sunset — Since 2026-01-01, the DPDPA's mandatory 60-day cure period has sunset; the Delaware DOJ may, at its discretion, offer a cure opportunity before enforcement, weighing violation count, entity size/complexity, and likelihood of consumer harm. Penalties reach up to $10,000 per violation as a per se violation of the Delaware Consumer Fraud Act. observed
  11. Uncertain https://www.recordinglaw.com/us-laws/data-privacy-laws/delaware-data-privacy-laws/ — Delaware DOJ DPDPA enforcement activity — As of the most recent secondary review located, the Delaware DOJ had not publicly announced a formal DPDPA enforcement action; early posture has focused on outreach and compliance education.
  12. Probable PrivacyOn — DPDPA private right of action — The DPDPA creates no private right of action; individuals cannot sue controllers directly and must instead file a complaint with the Delaware DOJ. observed
  13. Probable Osano — A DPDPA violation is a per se violation of the Delaware Consumer Fraud Act, carrying civil penalties up to $10,000 per willful violation. observed
  14. Uncertain Primary statutory record — As of reporting dated to approximately May 2026, the Delaware DOJ had not publicly announced a formal DPDPA enforcement action.
  15. Probable RecordingLaw — Delaware Consumer Fraud Act (Title 6, Ch. 25, Subch. II) — A DPDPA violation is deemed an unlawful practice under the Consumer Fraud Act; a willful violation can carry civil penalties of up to USD 10,000 per violation, with no DPDPA-specific fine schedule. observed
  16. Uncertain RecordingLaw — Delaware Department of Justice — As of the most recent secondary reporting reached this cycle, the Delaware DOJ has not publicly announced a formal DPDPA enforcement action; early posture has focused on outreach and compliance education. 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), 98 claim(s) (98 category placement(s)), 53 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 25 Oct 2026: upheld (16 confirmed against the cited source; 2 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 (37 mapped).

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