Skip to content
RiskTemplates · The Daily Brief Sunday, November 15, 2026
Wire DOJ WHIP Whistleblower Rewards Put a 120-Day Clock on Internal Investigations OCT 20

Feature Data Privacy

Delaware Just Narrowed the GLBA Privacy Exemption. Run the Applicability Test Before January 1.

Delaware HB 380 takes effect January 1, 2027, cuts the threshold to 10,000 consumers, and strips the entity-level GLBA exemption from fintechs. Scope it now.

By Rebecca Leung · November 14, 2026 ·
Table of Contents

TL;DR

  • Delaware HB 380 was signed September 2, 2026 and takes effect January 1, 2027 — 48 days from today. It cuts the DPDPA threshold from 35,000 Delaware consumers to 10,000, and 5,000 where 20 percent or more of gross revenue comes from selling personal data.
  • The headline for financial services is the exemption, not the threshold. HB 380 keeps the exemption for GLBA-regulated data but narrows the entity-level exemption to banks, insurers, and securities firms. Fintechs, non-bank lenders, servicers, and payment processors that leaned on the old blanket exemption mostly lose it.
  • Third parties receiving personal data become directly subject to the statute, and controllers owe contracts plus due diligence on them — a procurement and vendor-management workstream, not a privacy-policy edit.
  • The companion bill, HB 381, is already in force: 60 days to notify the Delaware AG after determining a breach, including where the business cannot yet identify which residents were affected.

Delaware is a small state and a large jurisdiction. It is the incorporation home of a meaningful share of the fintechs, non-bank lenders, and trust companies that sell into the rest of the country. That is why a consumer privacy statute in Wilmington lands harder than the population count suggests, and why the September 2 signing deserves a scoping memo rather than a line in a regulatory change log.

The bill’s own synopsis says out loud what it is for: to “more closely align the DPDPA with similar consumer data protection laws enacted in other states,” and to narrow the financial-institution exemption by “limiting entity-level exemptions specifically to banks and insurers and their respective affiliates.”

If your entity is a fintech with a sponsor bank, a non-bank installment lender, a mortgage servicer, or a payment processor, that second clause is about you.

The threshold changed. The exemption changed more.

Threshold movement gets the attention because it is easy to quote. Falling from 35,000 to 10,000 Delaware consumers moves a lot of small and mid-size companies into scope, and the 5,000-consumer figure applies where 20 percent or more of gross revenue comes from selling personal data. Both numbers are lower than most compliance teams would guess, and Delaware’s population means a company can hit 10,000 residents without Delaware being a named market.

The exemption change is the one that re-shapes portfolios. Under the prior text, any financial institution subject to GLBA Title V could claim an entity-level exemption. HB 380 splits that in two:

Entity typeEntity-level exemption after HB 380Practical read
Federally or state-chartered bank, credit union, savings association, plus affiliates principally in financial activitiesRetainedBank-side BaaS programs stay largely out at entity level
Insurer, plus qualifying affiliatesRetainedOut at entity level
Securities firm, plus qualifying affiliatesRetainedOut at entity level
Fintech, non-bank lender, servicer, payment processor, money transmitterNot in the enumerated categoriesRe-test applicability; non-GLBA data is squarely in scope
Any entity, for data that is GLBA-regulatedData-level exemption retainedGLBA data stays exempt, and GLBA’s Safeguards and Privacy Rules still govern it

Two consequences follow immediately.

First, the data-level exemption is doing real work and it is narrower than it sounds. It covers data regulated by GLBA. It does not cover the marketing site, the app’s behavioral analytics, the referral program, or the targeted advertising pixel — the exact surfaces where a fintech’s own revenue operations live.

Second, the enumerated list creates a partner-bank asymmetry. Your sponsor bank is exempt at entity level. You are probably not. When the bank’s vendor questionnaire arrives asking for your privacy posture, “we’re a financial institution” is no longer a complete answer.

The synopsis still says 15,000

A detail worth flagging because it will bite someone. The bill’s original synopsis describes the threshold as “not less than 15,000 consumers.” The engrossed text, and every law-firm summary published since — Hunton Andrews Kurth, Morgan Lewis, Troutman Pepper Locke — says 10,000. Scoping to 15,000 because the synopsis is the first document that loads is the fast way to be wrong by 5,000 consumers.

The applicability test, in three questions

Run it in writing, per legal entity, and keep the memo. Examiners and acquirers will both want it, and the second one will want it faster.

  1. Does the entity conduct business in Delaware, or produce products or services targeted at Delaware residents? Targeting is doing the work here. Delaware geo-targeted paid media, Delaware shipping, Delaware-licensed lending, or a Delaware charter all point the same direction.
  2. Does the entity control or process personal data of 10,000 or more Delaware consumers — or 5,000 if 20 percent or more of gross revenue comes from selling personal data? Count consumers, not records and not sessions.
  3. Is the entity within the retained exemption categories, and if so, which data falls outside the GLBA data exemption? Being bank-adjacent is not the test. Being a bank is.

Three “yes” answers where the entity is a fintech is usually in scope. Note the direction of the burden: the exemption is an exception to prove, not a default to assume.

What the statute now requires

The obligations are unremarkable individually and brutal collectively, because most of them are evidence-generating.

AreaRequirementArtifact that proves it
Sensitive dataConsent before processing and processing reasonably necessary and proportionate to the purpose disclosed at collectionPurpose-to-category mapping; consent records tied to the disclosure text shown
Selling sensitive dataDisclosure must be strictly necessary to a product the consumer affirmatively requested, plus conspicuous notice naming categories, purpose, and recipients, plus consentSale inventory per data element; notice versions; five-year consent retention
Profiling opt-outApplies to profiling supporting automated decisions with legal or similar effects — no longer only “solely automated”Profiling register with decision descriptions and opt-out handling
Data protection assessmentsTriggered at 50,000 consumers annually for covered profiling, down from 100,000Current DPIA per covered activity, covering harms, inputs, limits, monitoring
Bias evidenceProactive anti-bias testing is relevant to defenses; so is its absenceTest plans, results, and remediation records, dated
Third-party disclosureContract with limited purposes, DPDPA-level protections, oversight and remediation rights, and a duty on the third party to notify the controller when it stops complying; plus reasonable due diligenceExecuted clauses; diligence file per recipient; notification log
Consumer requestsSpecified disclosures within 30 days, including third parties that received reports in the preceding 24 monthsRequest log with clocks and response copies
Minors 13–18Consent before targeted advertising, sale, or covered profiling where the controller knows or willfully disregards ageAge signal documentation; consent capture

The sensitive-data definition expanded too: national origin, certain health information including pregnancy status, transgender or nonbinary status, citizenship or immigration status, neural data, financial account credentials, specified government identifiers, and sensitive inferences. Financial account credentials landing inside “sensitive data” is the change that touches every fintech’s authentication flow.

Setting the clause, not just the review

If third-party contracts sit in a queue behind a legal team with a twelve-week backlog, a January 1 effective date is already a problem. Pull the highest-data-access agreements first and amend rather than renegotiate. Starting language for the four required elements:

Purpose limitation. “Vendor shall process Personal Data solely for the limited purposes of [named services] and shall not sell, share for cross-context behavioral advertising, or repurpose Personal Data for any other purpose without Controller’s prior written consent.”

Standard of protection. “Vendor shall provide protections at least as protective as those required of Controller under the Delaware Personal Data Privacy Act, 6 Del. C. ch. 12D, including with respect to sensitive data, consumer requests, and profiling.”

Oversight and remediation. “Controller may audit Vendor’s compliance on reasonable notice, require a remediation plan for any deficiency, and suspend processing on material breach.”

Self-reporting. “Vendor shall notify Controller in writing within five business days of determining it can no longer meet its obligations under this section.”

The self-reporting clause is the one most paper lacks and the one that matters most, because it converts a vendor’s internal problem into a notice you can act on. Without it, you learn at renewal.

Where this stalls in practice

Procurement will say the vendor paper is standard and the vendor will say nobody else asks for this. Both are true and neither is a reason. Two workable moves: attach the clauses as a privacy addendum that rides the existing MSA instead of reopening commercial terms, and set a documented tier — full addendum for recipients of sensitive data, GLBA, or account credentials; notice-and-diligence-only for low-volume marketing vendors. A tiered rule you can defend beats a uniform rule nobody reaches.

Sales will push on the sensitive-data sale test specifically, because “strictly necessary” narrows what can be packaged into partner deals. Get the analysis per data element rather than per deal. Some elements will survive it. The ones that don’t need notice and consent before the next contract cycle, not after.

The 48 days

By November 30 — scope

  • Written applicability memo per legal entity, all three questions, with the consumer count method stated.
  • Entity-by-entity look at the retained exemption categories; stop assuming the old blanket covers you.
  • Inventory sensitive data against the expanded definition, starting with account credentials and any neural or health-adjacent data.

By December 15 — paper

  • Execute the privacy addendum on every recipient of sensitive data, GLBA data, or account credentials.
  • Diligence file per recipient: security posture, subprocessor list, breach history, and the assessment that produced the tier.
  • Notice and consent updates drafted for any sensitive-data disclosure that fails the strictly necessary test.

By December 31 — evidence

  • DPIAs current for every covered profiling activity over the new 50,000 threshold.
  • Anti-bias test plan scheduled with owners and dates — the absence is now explicitly relevant.
  • Request workflow tested end to end against the 30-day clock, including the 24-month recipient report.
  • Five-year retention configured for sensitive-data consent records, with a retrieval test.

Already live — HB 381. The 60-day outer limit and the AG notice duty are in force today. Confirm the AG contact sits in the breach response plan beside the consumer notice path, and that the trigger is written as “determination that a breach occurred,” not “confirmed scope of affected residents.” The provision specifically covers the case where a business cannot identify affected residents inside 60 days: it still owes the AG notice within 60 days of the determination, unless it uses substitute notice.

The takeaway

Delaware did not write a bank privacy law. It wrote a consumer privacy law with a bank-shaped hole, and it narrowed the hole on purpose. Institutions that re-run their entity-level scoping over the next six weeks will find either a clean memo or a workstream, and both are survivable. Institutions that keep reciting “we’re regulated under GLBA” will discover the gap when a sponsor bank, an acquirer, or the Delaware Department of Justice asks which category they fall into.

Start with the memo. It is the cheapest artifact and everything else sizes off it.

The Data Privacy Compliance Kit carries the working pieces: data inventory and mapping, purpose-to-category tables, assessment templates, third-party privacy clauses, and a request-handling log with clock tracking.

Related: the 50-state breach notification comparison, AI consumer data rights under state privacy laws, and scoping Global Privacy Control signals by state.

◆ Need the working template?

Start with the source guide.

These answer-first guides summarize the required fields, evidence, and implementation steps behind the templates practitioners search for.

◆ Immaterial Findings · Weekly

Sharp risk & compliance insights. No fluff.

◆ FAQ

Frequently asked questions.

Does Delaware HB 380 apply to banks?
Traditional banks, credit unions, savings associations, insurers, and securities firms keep an entity-level exemption, and all data regulated by GLBA is exempt from the DPDPA regardless of entity. A fintech, non-bank lender, mortgage servicer, or payment processor that previously relied on the old blanket entity-level financial-institution exemption generally loses it and has to re-test applicability.
What are the new thresholds under HB 380?
The DPDPA applies to entities conducting business in Delaware or targeting Delaware residents that control or process the personal data of 10,000 or more consumers, down from 35,000. Where at least 20 percent of gross revenue comes from selling personal data, the threshold drops to 5,000 consumers, down from 10,000. HB 380 takes effect January 1, 2027.
What does HB 381 change?
HB 381 amends Chapter 12B of Title 6 to put a 60-day outer limit on notice after determining a breach, and to require notice to the Delaware Attorney General within 60 days of the determination in the case where a business could not, through reasonable diligence, identify within 60 days that residents' personal information was included — unless it gives substitute notice. It took effect immediately when signed on September 2, 2026, so it is already live. The existing 500-resident trigger for Attorney General notification is unchanged; HB 381 adds the clock and closes the can't-identify gap.
What are the third-party contract requirements?
Where controllers disclose personal data to third parties, including for sale or targeted advertising, contracts must limit purposes, require DPDPA-level protections, preserve controller oversight and remediation rights, and require the third party to notify the controller when it stops meeting its obligations. Controllers also owe reasonable due diligence on those third parties, and third parties that receive data are themselves subject to DPDPA provisions.
When is a data protection assessment required?
HB 380 lowers the assessment trigger for covered profiling tied to automated decisions with legal or similarly significant effects from 100,000 to 50,000 consumers processed annually. Assessments must be documented and kept current, covering intended uses, deployment context, foreseeable harms, inputs and outputs, performance, limitations, transparency, monitoring, and safeguards.
Rebecca Leung

Author

Rebecca Leung

Rebecca Leung has 8+ years of risk and compliance experience across first and second line roles at commercial banks, asset managers, and fintechs. Former management consultant advising financial institutions on risk strategy. Founder of RiskTemplates.

◆ Related framework

Data Privacy Compliance Kit

Which of the 23 state privacy laws apply to your fintech after GLBA, plus the GLBA checklist, request tracker, assessments and vendor terms to comply.

Immaterial Findings · Newsletter

The brief, in your inbox.

Enforcement of the week, a framework breakdown, and the prompts that are actually worth running. Delivered to your inbox. Free.