---
title: "District of Columbia, USA Data Protection &amp; Privacy Regulation | Data Protection Monitor"
canonical: https://dataprotection.gi/jurisdictions/district-of-columbia-usa/
source_html: /jurisdictions/district-of-columbia-usa/index.html
description: "District of Columbia, USA data protection and privacy regulation: 10 categories, 77 claims, updated 2026-11-11."
generated_at: 2026-11-17T23:08:35Z
content_sha256: 3a9b8f76d2efc736d84eb35e064328aca74b91a70e45e3c49a9aeb124bbc3d91
generator: "fe-fleet/md-twin@1.0"
---
# District of Columbia, USA Data Protection & Privacy Regulation

schema gdpri-v2
trajectory: not yet assessed regulated (sectoral) overlaps: artificial-intelligence

Last updated 2026-11-11 · 10 categories · 77
claims · 50 sources in the cumulative register

Download report (PDF) Expand all

The District of Columbia&#x27;s data-protection posture is understood to face its most consequential near-term threat from federal legislation rather than local rulemaking.

Data collected 2026-11-11 · Data published 2026-11-11

AI-assembled from cited sources

Not covered: Regulator & Framework, Lawful Processing & Special Data, Data Subject Rights, Controller/Processor Duties, Cross-Border & Adequacy, Sectoral Watch, AdTech & Commercial Privacy, Algorithmic, Biometric & Surveillance Governance, Children & Vulnerable Groups, Enforcement & Redress.

Supervisory authority [District of Columbia Attorney General](https://www.naag.org/)

Next milestone No upcoming dated milestone on record

Record & confidence mix 77 claims · 45 sources · machine-compiled

15 Confirmed 52 Probable 10 Contested / unverified

Evidence re-verified: 2026-11-11 · Position last changed: 2026-11-11 · Record history & provenance &#9662; 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

[Open in Co-Pilot &#8599;](/reports/?type=copilot&j=DISTRICT-OF-COLUMBIA-USA)[Build Report](/reports/?j=DISTRICT-OF-COLUMBIA-USA)[Compare](/compare/?j=DISTRICT-OF-COLUMBIA-USA)

10 Categories

3 Red categories 57 Sub-modules

77 Claims

12 Tier-1 sources

Traffic-light mix 5 amber 3 red 2 n/a
(sums to 10 rendered categories; click to filter)

3 categories flagged red

United States federal law that applies in District of Columbia, USA is covered once, on the [United States](/jurisdictions/united-states/) page. This page covers District of Columbia, USA&#8217;s own layer: its own law, regulators and enforcement.

## Jurisdiction brief

Jurisdiction lead brief 1,040 Full executive summary 557

###### Latest update · 4 November 2026

#### Lead Signal

The District of Columbia&#x27;s data-protection posture has tightened on the enforcement side rather than through a new rights-based statute. D.C. Law 26-187, the Enhancing Consumer Protection Procedures Amendment Act of 2026, took effect on 26 September 2026 and gives the Office of the Attorney General mandatory minimum penalties and asset-freeze injunctive relief in consumer-protection actions brought under the Consumer Protection Procedures Act. The District continues to have no comprehensive private-sector privacy statute; its data-protection posture rests on a strengthened breach-notification and consumer-protection enforcement framework rather than on a GDPR-style rights regime.

#### Other Developments

The operative duty governing personal-information incidents remains the breach-notification regime under D.C. Code section 28-3852. Entities conducting business in the District that own or license computerized personal information of District residents must notify affected residents without unreasonable delay, must notify the Attorney General where a breach affects fifty or more District residents, and must provide free credit monitoring to affected individuals. The statute is reported to carry data-security requirements for covered businesses, though the precise statutory pinpoint for that obligation has not been independently confirmed against current text. Violations expose an entity to treble damages or fifteen hundred dollars per violation, whichever is greater, plus actual damages and attorney fees, enforceable both by the Attorney General and through a private right of action.

#### Cross-Monitor Connections

The same enforcement amendment that strengthens general consumer-protection remedies in the District is also material to crypto-facing consumer conduct, since the Attorney General has already applied the enhanced toolkit against a crypto-kiosk operator; readers following that angle should consult the crypto monitor for the kiosk-specific application. No sectoral overlap into financial-integrity, world-payments, advennt, or artificial-intelligence tracks is indicated by the available material this period.

#### Outlook

With mandatory minimum penalties and asset-freeze powers now in force, entities handling District residents&#x27; personal information should expect the Attorney General to pursue breach-notification and consumer-protection violations more assertively and with less prosecutorial discretion to settle for nominal remedies than before the amendment. The absence of a comprehensive private-sector privacy statute means the breach-notification duty and the strengthened enforcement toolkit remain the two operative pressure points in the District for the foreseeable period, with the government-only Data Privacy and Protection Act bill continuing to sit in committee rather than advancing toward enactment.

5 earlier updates not shown here.

###### Standing brief · as of 26 August 2026

Written before the update above. Where they differ, the update is the more recent position.

#### Lead Signal

The District of Columbia&#x27;s data-protection posture is understood to face its most consequential near-term threat from federal legislation rather than local rulemaking. The SECURE Data Act (H.R. 8413) is understood to have been introduced on April 22, 2026, carrying a broad preemption clause that would reach District sectoral and comprehensive privacy laws; the bill remains in committee and is opposed by a coalition of eighteen state attorneys general.

#### Other Developments

The Security Breach Protection Amendment Act of 2020 (D.C. Code §28-3851 et seq.) remains the primary in-force data-protection instrument in the District, having entered into effect on April 10, 2020. The District has not enacted a comprehensive omnibus consumer-privacy statute. D.C. Bill B26-0670, the District of Columbia Government Data Privacy and Protection Act of 2026, is understood to have been introduced on April 27, 2026 and referred to the Committee on Public Works and Operations on May 5, 2026, with committee testimony recorded June 29, 2026, and to remain pending and unenacted as of the retrieval date. It is understood to supersede the earlier B24-0451, modeled on the ULC Uniform Personal Data Protection Act, which stalled in committee and is no longer the most current pending comprehensive-adjacent proposal.

Entities suffering a breach affecting 50 or more District residents must provide written notice to the Office of the Attorney General, and the Act created security requirements for entities handling District residents&#x27; personal information. The statute&#x27;s protected-information categories were broadened to include biometric identifiers and, separately, genetic print, though only for breach-notification purposes. The statute&#x27;s notice trigger is understood to run on the residency of affected individuals rather than a controller&#x27;s place of establishment, giving it extraterritorial reach over any entity holding District residents&#x27; data.

The FTC&#x27;s Health Breach Notification Rule expressly names the District within its definition of "State," extending its notification duties to non-HIPAA-covered vendors of personal health records operating in the District. The Rule also triggers a media-notice obligation where a breach of unsecured PHR-identifiable health data affects 500 or more District residents.

D.C. Council Bill 25-0114, the Stop Discrimination by Algorithms Act of 2023, would have required notice to individuals whose data is used in algorithmic eligibility determinations. It would also have required covered entities to submit audit reports to the Office of the Attorney General. The bill is understood to have died at the end of the 25th DC Council session (2023-2024) without passage, with no reintroduction confirmed in the 26th Council as of October 2025.

The Office of the Attorney General functions as the District&#x27;s primary consumer-protection and data-breach enforcement authority, coordinating with the FTC. It also holds parens patriae and general consumer-protection enforcement authority, coordinating with the FTC and other state attorneys general on privacy and data-breach matters. The District is understood to have participated in significant multistate privacy enforcement actions, including the AshleyMadison data-breach settlement and joint FTC-state sweeps such as Operation Stop Scam Calls.

#### Cross-Monitor Connections

The lapsed Bill 25-0114 and the pending B26-0670 both touch algorithmic eligibility determinations and audit requirements with framing adjacent to AI-specific regulation; AI-Act-adjacent analysis of those provisions is routed to the artificial-intelligence monitor, while this monitor retains the profiling and automated-decision-making transparency angle proper to data protection.

#### Outlook

The SECURE Data Act&#x27;s preemption clause is understood to be the development most likely to reshape the District&#x27;s data-protection landscape over the coming cycles, given its potential to reach both the existing breach statute and any future comprehensive District privacy law. Whether B26-0670 advances beyond committee in the current 26th Council session remains unresolved and will require monitoring of committee markup schedules in subsequent cycles. Additional District-level developments flagged internally for verification, including sectoral health-data legislation and a possible student-data statute, remain outside this cycle&#x27;s confirmed factual record and will be revisited once independently verified.

Read full brief · 5 min read (1040 words)

###### Latest update · 4 November 2026

#### Regulatory Status

The District of Columbia has no comprehensive private-sector privacy statute. Its data-protection posture rests on two operative pillars: a breach-notification duty under D.C. Code section 28-3852, requiring notice to affected residents without unreasonable delay, notice to the Attorney General for breaches affecting fifty or more residents, and free credit monitoring; and a general consumer-protection enforcement framework administered by the Office of the Attorney General under the Consumer Protection Procedures Act. That enforcement framework was materially strengthened by D.C. Law 26-187, effective 26 September 2026, which adds mandatory minimum penalties and asset-freeze injunctive relief to the Attorney General&#x27;s toolkit. The breach-notification statute also carries a private right of action, allowing affected individuals to sue directly for treble damages or fifteen hundred dollars per violation, whichever is greater, plus attorney fees. A government-only Data Privacy and Protection Act, covering DC government agencies and their third-party data handlers but not the private sector generally, remains pending in the Committee on Public Works and Operations following a public hearing in mid-2026; advocacy testimony has flagged that the bill as introduced does not address government use of personal data to train AI systems.

#### Outlook

The District&#x27;s trajectory is toward intensified enforcement of existing consumer-protection and breach-notification law rather than toward a new comprehensive privacy statute. The pending government-data bill, if enacted, would narrow but not close the gap, since it would not reach private-sector data handling. Entities handling District residents&#x27; personal information should expect the strengthened Attorney General toolkit and the standing private right of action under the breach law to remain the two primary points of legal exposure for the foreseeable period.

1 earlier update not shown here.

###### Standing brief · as of 26 August 2026

#### Regulatory Status

The District of Columbia has no comprehensive omnibus consumer-privacy statute; the Security Breach Protection Amendment Act of 2020 remains the primary in-force data-protection instrument, and the Office of the Attorney General functions as the District&#x27;s primary consumer-protection and data-breach enforcement authority. Two pending 2026 bills, B26-0670 and a health-specific measure, indicate renewed legislative appetite without yet closing the comprehensive-statute gap, and the earlier B24-0451 no longer represents the most current pending proposal. Breach-notification duties under the 2020 Act remain the operative accountability regime: entities suffering a breach affecting 50 or more District residents must notify the Office of the Attorney General, and the statute&#x27;s residency-based trigger gives it extraterritorial reach. At the federal sectoral layer, the FTC&#x27;s Health Breach Notification Rule applies to non-HIPAA-covered health-record vendors operating in the District, and the FTC&#x27;s Section 5 authority remains the only applicable backstop for biometric data, dark-pattern marketing practices, and the algorithmic-discrimination concerns previously raised in the now-lapsed Bill 25-0114. Lawful-basis, data-subject-rights, and cross-border-transfer regimes are structurally absent at the District level, consistent with the design of US state and local privacy law rather than reflecting a research gap.

#### Outlook

The federal SECURE Data Act&#x27;s preemption clause is the most consequential near-term threat to the District&#x27;s data-protection framework, capable of reaching both the 2020 breach statute and any future comprehensive District law; its committee trajectory and the opposition of eighteen state attorneys general warrant continued monitoring, alongside the pending B26-0670 and B26-0525 bills and unresolved questions about a possible District-specific student-data statute.

Read full brief · 3 min read (557 words)

Key regulatory facts for District of Columbia, USA Key regulatory facts for District of Columbia, USA Regulatory Dimension District of Columbia, USA Standing Position

Jurisdiction District of Columbia, USA (US-DC)

Regulatory Scope Data Protection & Privacy Regulation (10 modules, 77 sourced findings)

Regulator & Framework A functioning breach-notification statute and active AG/FTC enforcement exist, but there is no comprehensive material-scope or registration regime beyond breach notification.

Lawful Processing & Special Data No lawful-basis or consent regime exists at the District level; only a federal enforcement-guidance signal on biometric data was identified.

Data Subject Rights No comprehensive statute in force; confirmed absence via seed disambiguation and independent search of DC privacy-law status.

Controller/Processor Duties Security and breach-notification duties are in force and reasonably well-specified; all other accountability duties are absent.

Primary Instruments Cited DC Law Library — DC Code §28-3852, DC Council LIMS, District of Columbia Office of the Chief Technology Officer, District of Columbia, USA Official Instrument (recordinglaw.com district-of-columbia-data-privac), District of Columbia, USA Official Instrument (recordinglaw.com data-breach-notification)

Last Confirmed / Updated 11 November 2026 (50 sources in cumulative register)

10 of 10 categories

Signal
Red
Amber
Green

Density
Comfortable
Compact

Expand all sources
Reset all

Match any filter within a group, and all selected groups. Press / to search.

### Regulator & Framework5 sub-modulesAmberEnacted in forceModule confidence: Probable&#9662;

A functioning breach-notification statute and active AG/FTC enforcement exist, but there is no comprehensive material-scope or registration regime beyond breach notification.

Primary framework FTC Act Section 5 (15 U.S.C. §45) + D.C. Code §28-3851 et seq. (Security Breach Protection Amendment Act of 2020)

Supervisory authority [District of Columbia Office of the Attorney General](https://www.naag.org/venue/district-of-columbia-attorney-general-office/)

Traffic-light rationale — Amber A functioning breach-notification statute and active AG/FTC enforcement exist, but there is no comprehensive material-scope or registration regime beyond breach notification.

#### Sub-modules (5)

#### Regulator and authorityGreen

The D.C. Office of the Attorney General is the District&#x27;s primary consumer-protection/data-breach enforcement authority, operating alongside and in coordination with the FTC.

Claims (6):

- District of Columbia Office of the Attorney General — the District&#x27;s primary consumer-protection and data-breach enforcement authority, coordinating with the FTC
- DC breach-notification statute — Violations of DC&#x27;s breach-notification law may be enforced as unfair or deceptive trade practices, giving the DC Attorney General and consumers a private right of action.
- DC entities must notify the OAG of breaches affecting 50+ residents, with eleven enumerated content items, no later than resident notice.
- DC Office of the Attorney General — DC has no comprehensive consumer data-privacy statute; data-protection matters are enforced by the AG via the general CPPA and the breach-notification statute, not a dedicated DPA.
- DC Attorney General / Consumer Protection Procedures Act — Breach-notification violations as unfair and deceptive trade practices under the CPPA (DC Code §28-3909(b)), with civil penalties up to $5,000 per violation (first) and $10,000 per violation (repeat), plus economic damages, costs and attorneys&#x27; fees.
- D.C. Code § 28-3852 — Notification to affected DC residents of a security breach of computerized personal information in the most expedient time possible and without unreasonable delay, with DC Attorney General notification where 50 or more residents are affected.

#### Act and instrumentsAmber

Primary in-force instrument is the Security Breach Protection Amendment Act of 2020 (D.C. Code §28-3851 et seq.). No comprehensive privacy statute is in force; a 2021/2022 attempt modeled on the Uniform Personal Data Protection Act (B24-0451) stalled in committee.

Claims (10):

- Security Breach Protection Amendment Act of 2020 — the primary in-force data-protection instrument in the District
- District of Columbia — a comprehensive omnibus consumer-privacy statute
- D.C. Bill B24-0451 — stalled in committee; superseded in currency by B26-0670 (2026)
- B26-0670 (District of Columbia Government Data Privacy and Protection Act of 2026) — Referred to Committee on Public Works and Operations; public hearing held 2026-06-29; remains pending and unenacted; would apply to DC government agencies and third-party data handlers only, not the private sector generally
- D.C. Bill B26-0670 — introduced April 27, 2026, pending as of retrieval date
- D.C. Code § 28-3852 — Any person or entity conducting business in DC that owns or licenses electronic personal information and discovers a security breach must promptly notify affected DC residents.
- A pending DC bill would create comprehensive privacy duties for government agencies only; it remains in committee.
- Security Breach Protection Amendment Act of 2020 (DC Law 23-98) — DC&#x27;s breach-notification regime, originally enacted 2007, expanding the definition of &#x27;personal information&#x27; and adding credit-monitoring and AG-notification obligations.
- D.C. Law 23-98 (Security Breach Protection Amendment Act of 2020) — 2020-06-17
- Security Breach Protection Amendment Act of 2020 (D.C. Act 23-268) — An amending instrument to the pre-existing Consumer Security Breach Notification subchapter (D.C. Code §§28-3851 et seq.), not a freestanding comprehensive data-protection statute.

#### Material scopeAmber

Material scope is defined only for breach-notification purposes; the 2020 amendment broadened the categories of protected personal information to include biometric identifiers.

Claims (2):

- Security Breach Protection Amendment Act of 2020 — protected personal information categories to include biometric identifiers
- District of Columbia — DC has no comprehensive consumer data privacy law in force and is absent from IAPP&#x27;s count of 20 US states with such a law as of January 2026; confirmed independently by DataGuidance&#x27;s DC jurisdiction page.

#### Territorial scopeAmber

The breach statute is triggered by the residency of affected individuals rather than the controller&#x27;s place of establishment, giving it extraterritorial reach over any entity holding District residents&#x27; data.

Claims (2):

- D.C. breach-notification statute — residency of affected individuals, giving extraterritorial reach
- D.C. Code § 28-3852 (Consumer Security Breach Notification) — Applies to any person or entity that owns, licenses, maintains, handles, or otherwise possesses electronic data including personal information of a DC resident, regardless of the entity&#x27;s location.

#### Regulator registration and filingAmber

No general controller-registration regime exists; the only filing obligation is written notice to the OAG where a breach affects 50 or more District residents.

Claims (2):

- Entities suffering a breach affecting 50+ District residents — written notice to the OAG
- DC Code §28-3852(b-1) — Written notice to the Office of the Attorney General, in the most expedient manner and no later than notice to affected residents, when a breach affects 50 or more District residents, containing eleven enumerated items.

The District of Columbia has no comprehensive omnibus consumer-privacy statute. The operative regime is a patchwork: (1) the federal FTC Act Section 5 general unfair/deceptive-practices authority, enforced nationally including in DC; (2) the District&#x27;s own data-breach-notification statute, D.C. Code §28-3851 et seq. (Security Breach Protection Amendment Act of 2020), enforced by the D.C. Office of the Attorney General; and (3) applicable federal sectoral statutes (HIPAA, GLBA, COPPA) which are addressed at the US-federal JID. A District bill modeled on the Uniform Law Commission&#x27;s Uniform Personal Data Protection Act (B24-0451) was introduced but did not advance out of committee, and remains the closest DC has come to a comprehensive framework.

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

Sources and claims (22)
- [DC Council LIMS](https://lims.dccouncil.gov/Legislation/B26-0670) — B26-0670 (District of Columbia Government Data Privacy and Protection Act of 2026) — Referred to Committee on Public Works and Operations; public hearing held 2026-06-29; remains pending and unenacted; would apply to DC government agencies and third-party data handlers only, not the private sector generally
- [NAAG](https://www.naag.org/venue/district-of-columbia-attorney-general-office/) — District of Columbia Office of the Attorney General — the District&#x27;s primary consumer-protection and data-breach enforcement authority, coordinating with the FTC
- [Council of the District of Columbia](https://www.dataguidance.com/sites/default/files/act_no._23-268_security_breach_protection_amendment_act_of_2020.pdf) — Security Breach Protection Amendment Act of 2020 — the primary in-force data-protection instrument in the District
- [IAPP](https://iapp.org/resources/article/us-state-privacy-laws-overview) — District of Columbia — a comprehensive omnibus consumer-privacy statute
- [District of Columbia Office of the Chief Technology Officer](https://octo.dc.gov/release/cto-stephen-millers-district-columbia-government-data-privacy-and-protection-act-2026) — D.C. Bill B24-0451 — stalled in committee; superseded in currency by B26-0670 (2026)
- [LegiScan](https://legiscan.com/DC/bill/B26-0670/2025) — D.C. Bill B26-0670 — introduced April 27, 2026, pending as of retrieval date
- [Council of the District of Columbia](https://www.dataguidance.com/sites/default/files/act_no._23-268_security_breach_protection_amendment_act_of_2020.pdf) — Security Breach Protection Amendment Act of 2020 — protected personal information categories to include biometric identifiers
- [DataGuidance](https://www.dataguidance.com/notes/district-columbia-data-breach) — D.C. breach-notification statute — residency of affected individuals, giving extraterritorial reach
- [NAAG](https://www.naag.org/issues/consumer-protection/consumer-protection-101/privacy/data-breaches/) — Entities suffering a breach affecting 50+ District residents — written notice to the OAG
- [DC Council LIMS](https://lims.dccouncil.gov/Legislation/B26-0670) — DC breach-notification statute — Violations of DC&#x27;s breach-notification law may be enforced as unfair or deceptive trade practices, giving the DC Attorney General and consumers a private right of action.
- [DC Law Library — DC Code §28-3852](https://code.dccouncil.gov/us/dc/council/code/sections/28-3852) — D.C. Code § 28-3852 — Any person or entity conducting business in DC that owns or licenses electronic personal information and discovers a security breach must promptly notify affected DC residents.
- [DC Law Library — DC Code §28-3852](https://code.dccouncil.gov/us/dc/council/code/sections/28-3852) — DC entities must notify the OAG of breaches affecting 50+ residents, with eleven enumerated content items, no later than resident notice.
- [DC Council LIMS](https://lims.dccouncil.gov/Legislation/B26-0670) — A pending DC bill would create comprehensive privacy duties for government agencies only; it remains in committee.
- [https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/) — DC Office of the Attorney General — DC has no comprehensive consumer data-privacy statute; data-protection matters are enforced by the AG via the general CPPA and the breach-notification statute, not a dedicated DPA.
- [https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/data-breach-notification/](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/data-breach-notification/) — D.C. Code § 28-3852 (Consumer Security Breach Notification) — Applies to any person or entity that owns, licenses, maintains, handles, or otherwise possesses electronic data including personal information of a DC resident, regardless of the entity&#x27;s location.
- [DC Council LIMS](https://lims.dccouncil.gov/Legislation/B26-0670) — Security Breach Protection Amendment Act of 2020 (DC Law 23-98) — DC&#x27;s breach-notification regime, originally enacted 2007, expanding the definition of &#x27;personal information&#x27; and adding credit-monitoring and AG-notification obligations.
- [DC Law Library — DC Code §28-3852](https://code.dccouncil.gov/us/dc/council/code/sections/28-3852) — DC Attorney General / Consumer Protection Procedures Act — Breach-notification violations as unfair and deceptive trade practices under the CPPA (DC Code §28-3909(b)), with civil penalties up to $5,000 per violation (first) and $10,000 per violation (repeat), plus economic damages, costs and attorneys&#x27; fees.
- [databreachcost.com](https://databreachcost.com/breach-notification-laws/district-of-columbia) — DC Code §28-3852(b-1) — Written notice to the Office of the Attorney General, in the most expedient manner and no later than notice to affected residents, when a breach affects 50 or more District residents, containing eleven enumerated items.
- [DC Law Library — DC Code §28-3852](https://code.dccouncil.gov/us/dc/council/code/sections/28-3852) — D.C. Code § 28-3852 — Notification to affected DC residents of a security breach of computerized personal information in the most expedient time possible and without unreasonable delay, with DC Attorney General notification where 50 or more residents are affected.
- [Council of the District of Columbia](https://code.dccouncil.gov/us/dc/council/laws/23-98) — D.C. Law 23-98 (Security Breach Protection Amendment Act of 2020) — 2020-06-17
- [Council of the District of Columbia](https://code.dccouncil.gov/us/dc/council/laws/23-98) — Security Breach Protection Amendment Act of 2020 (D.C. Act 23-268) — An amending instrument to the pre-existing Consumer Security Breach Notification subchapter (D.C. Code §§28-3851 et seq.), not a freestanding comprehensive data-protection statute.
- [Termly](https://termly.io/us-data-privacy-laws/) — District of Columbia — DC has no comprehensive consumer data privacy law in force and is absent from IAPP&#x27;s count of 20 US states with such a law as of January 2026; confirmed independently by DataGuidance&#x27;s DC jurisdiction page.

### Lawful Processing & Special Data4 sub-modulesRedEnacted in forceModule confidence: Probable&#9662;

No lawful-basis or consent regime exists at the District level; only a federal enforcement-guidance signal on biometric data was identified.

Supervisory authority [Federal Trade Commission](https://www.ftc.gov/)

Traffic-light rationale — Red No lawful-basis or consent regime exists at the District level; only a federal enforcement-guidance signal on biometric data was identified.

#### Sub-modules (4)

#### Lawful basesRed

No District-specific enumerated lawful bases exist.

#### Consent thresholdsRed

No District-specific consent standard (freely-given/informed/revocable) exists outside general FTC deception principles.

Claims (1):

- B26-0525 (Personal Health Data Security Amendment Act of 2025) — Remains in committee after a Committee on Health roundtable hearing on 23 March 2026; would mandate consent before collection, processing or disclosure of personal health data and prohibit geofencing around health-service facilities.

#### Special categoriesAmber

No DC statute enumerates special/sensitive categories; the FTC&#x27;s 2023 biometric policy statement is the only relevant signal, applied via federal Section 5 authority.

Claims (3):

- Federal Trade Commission — identifiable biometric information as sensitive under Section 5
- DC&#x27;s breach-law special-category data list includes genetic, biometric and health-insurance information.
- D.C. Code §28-3851(3)(A)(vi) (definition of personal information) — Biometric data of an individual generated by electronic measurements of physical characteristics is added as a new data element within the statutory definition of &#x27;personal information,&#x27; alongside medical information, genetic information/DNA profile, and health insurance information.

#### Pseudonymisation and anonymisationRed

No District-specific pseudonymisation/anonymisation safe-harbour definitions were identified.

The District has no enacted lawful-basis, consent-threshold, or pseudonymisation/anonymisation framework. The only relevant development is the FTC&#x27;s 2023 biometric-data policy statement, which signals that identifiable biometric information will be treated as sensitive under Section 5 enforcement nationally, including in DC, absent any DC-specific special-category regime.

Sources and claims (4)
- [IAPP](https://iapp.org/news/a/a-view-from-dc-the-ftc-says-if-it-can-be-biometric-data-it-already-is) — Federal Trade Commission — identifiable biometric information as sensitive under Section 5
- [LegiScan](https://legiscan.com/DC/bill/B26-0525/2025) — B26-0525 (Personal Health Data Security Amendment Act of 2025) — Remains in committee after a Committee on Health roundtable hearing on 23 March 2026; would mandate consent before collection, processing or disclosure of personal health data and prohibit geofencing around health-service facilities.
- [RecordingLaw](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/) — DC&#x27;s breach-law special-category data list includes genetic, biometric and health-insurance information.
- [Council of the District of Columbia](https://code.dccouncil.gov/us/dc/council/laws/23-98) — D.C. Code §28-3851(3)(A)(vi) (definition of personal information) — Biometric data of an individual generated by electronic measurements of physical characteristics is added as a new data element within the statutory definition of &#x27;personal information,&#x27; alongside medical information, genetic information/DNA profile, and health insurance information.

### Data Subject Rights5 sub-modulesRedEnacted in forceModule confidence: Probable&#9662;

No comprehensive statute in force; confirmed absence via seed disambiguation and independent search of DC privacy-law status.

Traffic-light rationale — Red No comprehensive statute in force; confirmed absence via seed disambiguation and independent search of DC privacy-law status.

#### Sub-modules (5)

#### Access rightRed

No District-level access right exists outside sectoral federal law.

#### Rectification and erasureRed

No District-level rectification/erasure right exists.

Claims (1):

- B26-0525 — A right to deletion requiring entities to honor verified deletion requests within 183 days as drafted; ACLU-DC testimony on 23 March 2026 urged shortening this to 45 days.

#### Restriction and objectionRed

No District-level restriction/objection right exists.

#### Data portabilityRed

No District-level portability right exists.

#### Deadlines and response windowsRed

No statutory response-window applies absent a rights framework; only the breach-notification &#x27;without unreasonable delay&#x27; standard exists.

Claims (1):

- DC breach-notification statute — DC&#x27;s breach-notification statute requires notice &#x27;in the most expedient time possible and without unreasonable delay,&#x27; with no fixed day-count deadline.

The District confers no general statutory rights of access, rectification, erasure, restriction, objection, or portability. These rights exist only where an applicable federal sectoral statute (e.g., HIPAA) independently grants them, which is addressed at the US-federal JID, not here.

Sources and claims (2)
- [DC Law Library — DC Code §28-3852](https://code.dccouncil.gov/us/dc/council/code/sections/28-3852) — DC breach-notification statute — DC&#x27;s breach-notification statute requires notice &#x27;in the most expedient time possible and without unreasonable delay,&#x27; with no fixed day-count deadline.
- [Electronic Privacy Information Center (EPIC)](https://epic.org/epic-urges-d-c-council-to-strengthen-proposed-government-data-privacy-and-protection-act/) — B26-0525 — A right to deletion requiring entities to honor verified deletion requests within 183 days as drafted; ACLU-DC testimony on 23 March 2026 urged shortening this to 45 days.

### Controller/Processor Duties7 sub-modulesAmberEnacted in forceModule confidence: Probable&#9662;

Security and breach-notification duties are in force and reasonably well-specified; all other accountability duties are absent.

Primary framework D.C. Code §28-3851 et seq. (Security Breach Protection Amendment Act of 2020)

Supervisory authority [District of Columbia Office of the Attorney General](https://www.naag.org/venue/district-of-columbia-attorney-general-office/)

Traffic-light rationale — Amber Security and breach-notification duties are in force and reasonably well-specified; all other accountability duties are absent.

#### Sub-modules (7)

#### Accountability & DPIARed

No DPIA trigger or general accountability principle is codified.

#### DPO requirementsRed

No DPO appointment threshold exists.

#### Ropa requirementsRed

No records-of-processing obligation exists.

#### Joint controller arrangementsRed

No joint-controller framework exists.

#### Security measuresAmber

The 2020 amendment created security requirements for companies handling District residents&#x27; personal information.

Claims (4):

- Security Breach Protection Amendment Act of 2020 — security requirements for entities handling District residents&#x27; personal information
- DC imposes general security-measure requirements on holders of DC residents&#x27; personal information.
- D.C. breach-notification subchapter — Entities holding DC residents&#x27; personal information must implement reasonable security safeguards; GLBA/HIPAA/HITECH compliance is deemed to satisfy the security-requirement limb only
- Security Breach Protection Amendment Act of 2020 (D.C. Act 23-268) — Any person or entity that owns, licenses, maintains, handles, or otherwise possesses personal information of a District resident must implement and maintain reasonable security safeguards appropriate to the nature of the information and the size of the entity, including flow-down security requirements in third-party service provider contracts.

#### Breach notificationGreen

Written notice to the OAG is required where a breach affects 50+ District residents; the amendment entered into effect April 10, 2020.

Claims (9):

- D.C. Code §28-3851 et seq. — written notice to the OAG for breaches affecting 50+ residents
- Security Breach Protection Amendment Act of 2020 — April 10, 2020
- DC breach-notification statute — Organizations reaching 50 or more affected DC residents must notify the DC Attorney General; those notifying 1,000+ individuals must also inform nationwide consumer reporting agencies.
- DC breach law sets individual-notice timing and a 1,000-individual threshold for CRA notice.
- D.C. Code § 28-3852(b-1) — Written notice to the DC Attorney General when a breach affects 50+ District residents, including categories of compromised information, nature of breach, number affected, cause and remedial actions
- D.C. Code § 28-3852 — Notice to affected DC residents without unreasonable delay; notice to the Attorney General for breaches affecting 50+ DC residents; free credit monitoring; treble damages or $1,500 per violation (whichever is greater) plus attorney fees, enforceable by AG and via private right of action
- DC Code §28-3852 — Notification to affected residents &#x27;in the most expedient time possible and without unreasonable delay&#x27; following discovery of a qualifying breach; AG notice no later than resident notice when 50+ residents affected.
- D.C. Code §28-3852(b-1) — An entity experiencing a breach affecting 50 or more District of Columbia residents must provide written notice to the D.C. Office of the Attorney General no later than when notice is given to affected residents, containing the nature and cause of the breach and the number of residents affected.
- D.C. Code § 28-3852(b-1) — An entity required to notify DC residents of a breach must also give written notice to the DC Attorney General if the breach affects 50 or more District residents, no later than when individual notice is provided.

#### Retention and disposalRed

No general retention-limitation or disposal-duty statute was identified.

Outside of breach notification and an implicit security-requirements provision introduced by the 2020 amendment, the District imposes no DPIA, DPO, ROPA, joint-controller, or general retention/disposal duties. The breach statute requires written notice to the OAG where 50+ District residents are affected and creates security requirements for entities handling personal information.

Periodic update · new data 2026-11-04 The operative duty governing personal-information incidents remains the breach-notification regime under D.C. Code section 28-3852. Any entity conducting business in the District that owns or licenses computerized personal information of District residents must notify affected residents without unreasonable delay upon discovery of a breach of the security of the system. Where a breach affects fifty or more District residents, the entity must also notify the Attorney General. Affected individuals must additionally be offered free credit monitoring. The statute is reported to establish data-security requirements for covered businesses, a feature associated with the broader 2020 overhaul of the District&#x27;s breach law, though the precise statutory pinpoint for that data-security obligation has not been independently confirmed against current statutory text and is carried forward here as a noted gap rather than as a settled finding.

This duty applies broadly, reaching both entities that collect personal information directly and those that process it on another&#x27;s behalf, since the statute is framed in terms of ownership or licensing of the data rather than in terms of a controller/processor distinction of the kind found in rights-based privacy statutes elsewhere. There is no DC-specific statute setting out lawful bases, consent thresholds, or data-minimization duties for private-sector processing outside the breach-notification context; the District&#x27;s controller-facing obligations are, in substance, limited to what the breach law requires once an incident has occurred, rather than extending to ongoing processing governance.

#### Outlook

Businesses handling District residents&#x27; personal information should expect the breach-notification duty to remain the primary operative control in the absence of a comprehensive processing-governance statute. The unresolved statutory pinpoint for the data-security requirement reported alongside the breach law is worth continued attention, since confirmation of its scope would clarify whether DC-based or DC-facing controllers carry an ongoing security obligation distinct from the post-breach notification duty itself.

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

Sources and claims (13)
- [RecordingLaw](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/) — DC breach-notification statute — Organizations reaching 50 or more affected DC residents must notify the DC Attorney General; those notifying 1,000+ individuals must also inform nationwide consumer reporting agencies.
- [Council of the District of Columbia](https://www.dataguidance.com/sites/default/files/act_no._23-268_security_breach_protection_amendment_act_of_2020.pdf) — Security Breach Protection Amendment Act of 2020 — security requirements for entities handling District residents&#x27; personal information
- [NAAG](https://www.naag.org/issues/consumer-protection/consumer-protection-101/privacy/data-breaches/) — D.C. Code §28-3851 et seq. — written notice to the OAG for breaches affecting 50+ residents
- [DataGuidance](https://www.dataguidance.com/news/district-columbia-data-breach-law-enters-effect) — Security Breach Protection Amendment Act of 2020 — April 10, 2020
- [RecordingLaw](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/) — DC imposes general security-measure requirements on holders of DC residents&#x27; personal information.
- [RecordingLaw](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/) — DC breach law sets individual-notice timing and a 1,000-individual threshold for CRA notice.
- [Electronic Privacy Information Center (EPIC)](https://epic.org/epic-urges-d-c-council-to-strengthen-proposed-government-data-privacy-and-protection-act/) — D.C. breach-notification subchapter — Entities holding DC residents&#x27; personal information must implement reasonable security safeguards; GLBA/HIPAA/HITECH compliance is deemed to satisfy the security-requirement limb only
- [RecordingLaw](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/) — D.C. Code § 28-3852(b-1) — Written notice to the DC Attorney General when a breach affects 50+ District residents, including categories of compromised information, nature of breach, number affected, cause and remedial actions
- [databreachcost.com](https://databreachcost.com/breach-notification-laws/district-of-columbia) — D.C. Code § 28-3852 — Notice to affected DC residents without unreasonable delay; notice to the Attorney General for breaches affecting 50+ DC residents; free credit monitoring; treble damages or $1,500 per violation (whichever is greater) plus attorney fees, enforceable by AG and via private right of action
- [databreachcost.com](https://databreachcost.com/breach-notification-laws/district-of-columbia) — DC Code §28-3852 — Notification to affected residents &#x27;in the most expedient time possible and without unreasonable delay&#x27; following discovery of a qualifying breach; AG notice no later than resident notice when 50+ residents affected.
- [Jackson Lewis (Workplace Privacy Report)](https://www.workplaceprivacyreport.com/2020/05/articles/consumer-privacy/washington-d-c-significantly-overhauls-its-data-breach-notification-law/) — Security Breach Protection Amendment Act of 2020 (D.C. Act 23-268) — Any person or entity that owns, licenses, maintains, handles, or otherwise possesses personal information of a District resident must implement and maintain reasonable security safeguards appropriate to the nature of the information and the size of the entity, including flow-down security requirements in third-party service provider contracts.
- [Justia](https://law.justia.com/codes/district-of-columbia/title-28/chapter-38/subchapter-ii/section-28-3852/) — D.C. Code §28-3852(b-1) — An entity experiencing a breach affecting 50 or more District of Columbia residents must provide written notice to the D.C. Office of the Attorney General no later than when notice is given to affected residents, containing the nature and cause of the breach and the number of residents affected.
- [Justia](https://law.justia.com/codes/district-of-columbia/title-28/chapter-38/subchapter-ii/section-28-3852/) — D.C. Code § 28-3852(b-1) — An entity required to notify DC residents of a breach must also give written notice to the DC Attorney General if the breach affects 50 or more District residents, no later than when individual notice is provided.

### Cross-Border & Adequacy 6 sub-modules Not assessed &#9662;

No District-level cross-border transfer or adequacy framework exists; this is a structural feature of U.S. sub-state jurisdictions, not a coverage gap in research.

Traffic-light rationale — Not assessed No District-level cross-border transfer or adequacy framework exists; this is a structural feature of U.S. sub-state jurisdictions, not a coverage gap in research.

#### Sub-modules (6)

#### Transfer mechanismsRed

No District-level transfer-mechanism regime.

#### Adequacy receivedRed

Not applicable; DC does not receive adequacy decisions independently of the U.S. federal government.

#### Adequacy grantedRed

Not applicable at sub-state level.

#### SCCs and BCRsRed

No District-level SCC/BCR regime.

#### Transfer impact assessmentRed

No TIA requirement exists at the District level.

#### Data localisationRed

No data-localisation mandate exists.

As a sub-federal U.S. jurisdiction, the District of Columbia does not independently operate transfer mechanisms, adequacy decisions, SCC/BCR regimes, or data-localisation mandates; these matters, to the extent they exist at all for the U.S., sit at the federal level and are out of scope for this District-level baseline.

### Sectoral Watch7 sub-modulesAmberEnacted in forceModule confidence: Probable&#9662;

One federal sectoral rule (HBNR) is confirmed to apply to DC by name; other sector overlays are either federal-only or unconfirmed for DC specifically.

Primary framework FTC Health Breach Notification Rule, 16 CFR Part 318 (federal overlay applicable to DC)

Supervisory authority [Federal Trade Commission](https://www.ftc.gov/)

Traffic-light rationale — Amber One federal sectoral rule (HBNR) is confirmed to apply to DC by name; other sector overlays are either federal-only or unconfirmed for DC specifically.

#### Sub-modules (7)

#### Financial sector overlayRed

No District-specific financial-sector privacy overlay identified; GLBA is federal and addressed at the US-federal JID.

#### Health sector overlayAmber

The FTC Health Breach Notification Rule expressly names DC within its definition of &#x27;State&#x27; and applies its notification duties (including a media-notice trigger at 500+ affected residents) to non-HIPAA-covered vendors of personal health records and related entities operating in the District.

Claims (5):

- FTC Health Breach Notification Rule — DC within its definition of &#x27;State&#x27;
- FTC Health Breach Notification Rule — media-notice obligation at 500+ affected residents
- B26-0525 (Personal Health Data Security Amendment Act of 2025) — Introduced 1 December 2025; would prohibit geofencing within a set radius of health-care facilities and require controller consent before collecting, processing or disclosing personal health data; had a roundtable hearing 23 March 2026 and remains in the Committee on Health with no markup or vote found this cycle.
- DC Office of the Attorney General — OAG testimony on B26-0525 recommended moving from notice-and-consent to purpose-based processing limits, a 45-day deletion timeline, and making violations actionable under the CPPA for both public enforcement and private suits.
- 16 CFR Part 318 (FTC Health Breach Notification Rule) — The District of Columbia is explicitly listed within the Rule&#x27;s definition of &#x27;State,&#x27; confirming D.C. residents count toward the Rule&#x27;s 500-resident media-notice and other State/jurisdiction-based thresholds.

#### Telecoms and eprivacyRed

No District-specific telecoms/ePrivacy-style cookie or communications-privacy overlay identified.

#### Employment dataRed

No District-specific employment-data privacy overlay identified.

#### Credit and scoringRed

No District-specific credit/scoring overlay identified; FCRA is federal.

#### educationRed

No District-specific education-sector data overlay identified; FERPA is federal.

#### insuranceRed

No District-specific insurance-sector data overlay identified.

The clearest District-relevant sectoral overlay identified is the FTC&#x27;s Health Breach Notification Rule (16 CFR Part 318), which by its own terms defines &#x27;State&#x27; to include the District of Columbia and triggers a media-notice obligation where 500+ residents of the District are affected by a breach of unsecured PHR-identifiable health data. A DC AG bill to protect consumer health data was referenced in secondary sources (July 2024) but substantive text could not be retrieved. No DC-specific overlays were identified for financial services, telecoms/ePrivacy, employment, credit-scoring, education, or insurance; these sectors are governed, if at all, by federal sectoral statutes (GLBA, FCRA, FERPA) addressed at the US-federal JID.

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

Sources and claims (5)
- [Federal Trade Commission](https://www.ftc.gov/sites/default/files/documents/federal_register_notices/health-breach-notification-rule-16-cfr-part-318/090825healthbreachrule.pdf) — FTC Health Breach Notification Rule — DC within its definition of &#x27;State&#x27;
- [Federal Trade Commission](https://www.ftc.gov/business-guidance/resources/complying-ftcs-health-breach-notification-rule-0) — FTC Health Breach Notification Rule — media-notice obligation at 500+ affected residents
- [https://legiscan.com/DC/bill/B26-0525/2025](https://legiscan.com/DC/bill/B26-0525/2025) — B26-0525 (Personal Health Data Security Amendment Act of 2025) — Introduced 1 December 2025; would prohibit geofencing within a set radius of health-care facilities and require controller consent before collecting, processing or disclosing personal health data; had a roundtable hearing 23 March 2026 and remains in the Committee on Health with no markup or vote found this cycle.
- [https://citizenportal.ai/articles/9820140/District-of-Columbia/Legislative/Committees/Committee-on-Health/DC-Committee-debates-healthdata-bill-industry-warns-of-implementation-problems-while-privacy-advocates-push-stronger-rules](https://citizenportal.ai/articles/9820140/District-of-Columbia/Legislative/Committees/Committee-on-Health/DC-Committee-debates-healthdata-bill-industry-warns-of-implementation-problems-while-privacy-advocates-push-stronger-rules) — DC Office of the Attorney General — OAG testimony on B26-0525 recommended moving from notice-and-consent to purpose-based processing limits, a 45-day deletion timeline, and making violations actionable under the CPPA for both public enforcement and private suits.
- [Office of the Federal Register / GPO (eCFR)](https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C/part-318) — 16 CFR Part 318 (FTC Health Breach Notification Rule) — The District of Columbia is explicitly listed within the Rule&#x27;s definition of &#x27;State,&#x27; confirming D.C. residents count toward the Rule&#x27;s 500-resident media-notice and other State/jurisdiction-based thresholds.

### AdTech & Commercial Privacy6 sub-modulesRedEnacted in forceModule confidence: Probable&#9662;

No DC-specific adtech/commercial-privacy statute exists; only a general federal deception backstop applies.

Primary framework FTC Act Section 5 (15 U.S.C. §45) [federal backstop only]

Supervisory authority [Federal Trade Commission](https://www.ftc.gov/)

Traffic-light rationale — Red No DC-specific adtech/commercial-privacy statute exists; only a general federal deception backstop applies.

#### Sub-modules (6)

#### Cookies and trackersRed

No DC-specific cookie/tracker consent law.

#### Dark patternsAmber

No DC-specific dark-pattern prohibition; FTC Section 5 enforcement against deceptive negative-option/cancellation design serves as the only applicable backstop.

Claims (2):

- Federal Trade Commission — deceptive negative-option marketing/cancellation flows nationally
- DC now bans drip pricing and hidden fees in consumer transactions.

#### Opt out signalsRed

No DC-specific universal opt-out signal (e.g., GPC) mandate exists.

#### Clean rooms and dcrRed

No DC-specific clean-room/data-collaboration-room rules exist.

#### Cross context advertisingRed

No &#x27;sale&#x27;/&#x27;share&#x27; cross-context-advertising regime exists at the District level.

#### Direct marketingRed

No DC-specific direct-marketing consent/suppression statute exists.

The District has no cookie-consent law, dark-pattern prohibition, opt-out-signal mandate, clean-room regulation, cross-context-advertising &#x27;sale/share&#x27; regime, or direct-marketing consent statute. The only applicable backstop is the FTC&#x27;s general Section 5 authority, which has been used nationally (including in matters touching DC) against deceptive negative-option marketing and burdensome cancellation flows -- a proxy for dark-pattern enforcement absent a DC-specific rule.

No periodic updates recorded in this cycle

Sources and claims (2)
- [Federal Trade Commission](https://www.ftc.gov/) — Federal Trade Commission — deceptive negative-option marketing/cancellation flows nationally
- [databreachcost.com](https://databreachcost.com/breach-notification-laws/district-of-columbia) — DC now bans drip pricing and hidden fees in consumer transactions.

### Algorithmic, Biometric & Surveillance Governance6 sub-modulesAmberEnacted in forceModule confidence: Probable&#9662;

No binding District-level ADM/biometric statute is in force; a substantive bill is pending/stalled and a federal enforcement-guidance signal exists on biometric data.

Primary framework Pending: D.C. Stop Discrimination by Algorithms Act (Bill 25-0114, not enacted); FTC Section 5 biometric guidance (federal, in force)

Supervisory authority [District of Columbia Office of the Attorney General](https://www.naag.org/venue/district-of-columbia-attorney-general-office/)

Traffic-light rationale — Amber No binding District-level ADM/biometric statute is in force; a substantive bill is pending/stalled and a federal enforcement-guidance signal exists on biometric data.

#### Sub-modules (6)

#### Profiling restrictionsRed

No enacted profiling restriction exists at the District level.

Claims (1):

- Surveillance Pricing Prohibition Amendment Act of 2026 (B26-0667) — Introduced 2026-04-20, 26th Council; a public hearing was held 2026-10-19. Would prohibit algorithmic pricing of consumer goods; narrower successor-type measure to the long-dead Stop Discrimination by Algorithms Act (B25-0114, died 2024-12-31).

#### Automated decision making transparencyAmber

Bill 25-0114 would require notice to individuals whose data is used in algorithmic eligibility/information-availability determinations, but remains unenacted.

Claims (1):

- D.C. Council Bill 25-0114 — died at end of 25th Council session (2023-2024); no confirmed reintroduction

#### AI risk assessmentsAmber

Bill 25-0114 would require covered entities to audit algorithmic determinations and submit audit reports to the OAG, but remains unenacted.

Claims (4):

- D.C. Council Bill 25-0114 — died at end of 25th Council session (2023-2024); no confirmed reintroduction
- EPIC — Urged B26-0670 be strengthened to address government use of personal data to train AI systems, since the bill as introduced does not address this.
- B26-0670, District of Columbia Government Data Privacy and Protection Act of 2026 — Introduced 2026-04-27, referred to Committee on Public Works and Operations 2026-05-05, most recent recorded action a public hearing on 2026-06-29; no vote, mark-up or passage recorded as of retrieval.

#### Biometric regimeAmber

No DC-specific biometric statute; the FTC&#x27;s 2023 biometric policy statement is the only applicable (federal) treatment of biometric data as sensitive.

Claims (1):

- Federal Trade Commission — 2023 biometric-data policy statement nationally, including DC

#### Genetic dataAmber

The 2020 breach-statute amendment added genetic print to protected personal-information categories for breach-notification purposes only; no general genetic-data processing regime exists.

Claims (1):

- Security Breach Protection Amendment Act of 2020 — genetic print to protected categories for breach purposes only

#### State surveillance carveoutsRed

No District-specific state-surveillance carve-out or limitation provision was identified.

The District has no enacted profiling-restriction, ADM-transparency, or AI-risk-assessment statute. The DC Attorney General introduced the Stop Discrimination by Algorithms Act (subsequently reintroduced as Council Bill 25-0114 in February 2023), which would require notices, bias audits, and OAG reporting for algorithmic eligibility/information-availability determinations, but the bill remains at committee stage and has not been enacted; its current status in the present Council period could not be confirmed. Separately, the FTC&#x27;s 2023 biometric-data policy statement (federal, Section-5-based) treats facial images and other identifiable bodily measurements as sensitive biometric information nationally, including in DC. The 2020 amendment to DC&#x27;s breach statute added genetic print to the categories of protected personal information for breach-notification purposes.

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

Sources and claims (6)
- [LegiScan](https://legiscan.com/DC/bill/B25-0114/2023) — D.C. Council Bill 25-0114 — died at end of 25th Council session (2023-2024); no confirmed reintroduction
- [IAPP](https://iapp.org/news/a/a-view-from-dc-the-ftc-says-if-it-can-be-biometric-data-it-already-is) — Federal Trade Commission — 2023 biometric-data policy statement nationally, including DC
- [Council of the District of Columbia](https://www.dataguidance.com/sites/default/files/act_no._23-268_security_breach_protection_amendment_act_of_2020.pdf) — Security Breach Protection Amendment Act of 2020 — genetic print to protected categories for breach purposes only
- [Electronic Privacy Information Center (EPIC)](https://epic.org/epic-urges-d-c-council-to-strengthen-proposed-government-data-privacy-and-protection-act/) — EPIC — Urged B26-0670 be strengthened to address government use of personal data to train AI systems, since the bill as introduced does not address this.
- [LegiScan](https://legiscan.com/DC/bill/B26-0670/2025?guid=5KTcHNP6CaBzKtRH0OmTyW) — B26-0670, District of Columbia Government Data Privacy and Protection Act of 2026 — Introduced 2026-04-27, referred to Committee on Public Works and Operations 2026-05-05, most recent recorded action a public hearing on 2026-06-29; no vote, mark-up or passage recorded as of retrieval.
- [LegiScan](https://legiscan.com/DC/bill/B26-0667/2025) — Surveillance Pricing Prohibition Amendment Act of 2026 (B26-0667) — Introduced 2026-04-20, 26th Council; a public hearing was held 2026-10-19. Would prohibit algorithmic pricing of consumer goods; narrower successor-type measure to the long-dead Stop Discrimination by Algorithms Act (B25-0114, died 2024-12-31).

### Children & Vulnerable Groups 5 sub-modules Not assessed &#9662;

No District-specific protections for children or vulnerable groups were identified; only the federal COPPA backstop applies, which is out of scope for this District-level baseline.

Supervisory authority [Federal Trade Commission](https://www.ftc.gov/)

Traffic-light rationale — Not assessed No District-specific protections for children or vulnerable groups were identified; only the federal COPPA backstop applies, which is out of scope for this District-level baseline.

#### Sub-modules (5)

#### Age verificationRed

No District-specific age-verification mandate exists.

#### Parental consentRed

No District-specific parental-consent mechanism beyond federal COPPA (out of scope for this JID).

#### Minor profiling bansRed

No District-specific ban on profiling of minors exists.

#### Education settingsRed

No District-specific education-setting data rule beyond federal FERPA (out of scope).

#### Dependent adultsRed

No District-specific dependent-adult data-protection provision was identified.

The District has no District-specific age-of-consent, parental-consent, minor-profiling-ban, education-setting, or dependent-adult data-protection statute. Federal COPPA (parental consent for under-13s) applies nationally, including in DC, but is addressed at the US-federal JID rather than here.

### Enforcement & Redress6 sub-modulesAmberEnacted in forceModule confidence: Probable&#9662;

Active, coordinated enforcement exists via the OAG and FTC, but DP-specific penalty structure and private-right-of-action status remain unconfirmed; a major pending federal development (SECURE Data Act) could reshape the landscape.

Primary framework D.C. Code §28-3851 et seq. + FTC Act Section 5 + D.C. Attorney General consumer-protection authority

Supervisory authority [District of Columbia Office of the Attorney General](https://www.naag.org/venue/district-of-columbia-attorney-general-office/)

Traffic-light rationale — Amber Active, coordinated enforcement exists via the OAG and FTC, but DP-specific penalty structure and private-right-of-action status remain unconfirmed; a major pending federal development (SECURE Data Act) could reshape the landscape.

#### Sub-modules (6)

#### Regulator powers and penaltiesAmber

The OAG has parens patriae and general consumer-protection enforcement authority and coordinates with the FTC and other state AGs on privacy/data-breach matters.

Claims (11):

- District of Columbia Office of the Attorney General — parens patriae and general consumer-protection enforcement authority
- Office of the Attorney General for the District of Columbia — Enhanced remedies including asset freezes and mandatory minimum penalties in AG consumer-protection enforcement actions
- DC&#x27;s AG enforcement toolkit for data-protection (breach-notification) violations now includes asset freezes and mandatory minimum penalties.
- D.C. Law 26-187 authorizes AG subpoena/interrogatory power and asset freezes.
- D.C. Law 26-187 sets mandatory minimum CPPA penalties.
- DC breach-notification statute — Violations of DC&#x27;s breach-notification law may be treated as an unfair and deceptive trade practice, subjecting entities to treble damages or $1,500 per violation plus actual damages, and requiring free 18-month identity-theft protection for SSN/TIN breaches.
- DC breach-notification law — DC&#x27;s data-breach law requires written notice to the Attorney General when a breach affects 50 or more District residents.
- D.C. Code § 28-3852 — Treble damages or $1,500 per violation (whichever is greater), plus actual damages and attorney fees, enforceable by AG and via private right of action for breach-notification violations
- DC Code §28-3909(b) — Civil penalty of up to $5,000 per violation (first) and up to $10,000 per violation (repeat), plus economic damages, costs and attorneys&#x27; fees.
- D.C. Code § 28-3909(b) — Civil penalty of up to $5,000 per violation for a first breach-notification violation and up to $10,000 per violation for a repeat violation, plus economic damages, costs and fees; organizations reaching 50+ affected DC residents must separately notify the Attorney General.
- D.C. Law 26-187 — Amends AG investigatory/enforcement powers: interrogatories, protective-order sharing with law enforcement, service by any method reasonably calculated to give actual notice, use of sworn statements in perjury prosecutions, asset-freeze injunctive relief without bond and without AG having to prove damages, mandatory minimum penalties ($500 first violation, $1,000 subsequent), aiding-and-abetting liability, cost/fee recovery.

#### Enforcement activity indexAmber

DC has participated in significant multistate privacy enforcement, including the AshleyMadison data-breach settlement and joint FTC-state sweeps such as Operation Stop Scam Calls.

Claims (5):

- District of Columbia — significant multistate privacy enforcement actions
- Google LLC — DC AG&#x27;s $700M multistate settlement with Google over anticompetitive practices in Android app distribution and in-app payment processing, announced Dec 2023, reached final judgment on 18 August 2026.
- DC Office of the Attorney General — Multistate settlements of over $350,000 against Blackbaud (ransomware attack), $600 million against Equifax, and $148 million against Uber over delayed breach notification.
- D.C. Code § 28-3852(a) — Any person or entity conducting business in DC that owns/licenses computerized personal information must notify any DC resident whose personal information was included in a breach -- a combined business-nexus-plus-residency test, not pure residency.
- $700 million multistate Google Play Store antitrust settlement — DC OAG&#x27;s own release references a final-approval hearing set for 2026-04-30; other secondary reporting references an August 2026 final-approval date; sources are inconsistent and not reconciled this cycle. DC&#x27;s reported share of penalties is approximately $2 million.

#### Regulator funding and capacityRed

No specific budget or headcount data for the OAG&#x27;s privacy/consumer-protection function was identified.

#### Collective redress and class actionsRed

No DC-specific data-protection class-action or collective-redress mechanism was confirmed.

#### Private right of actionAmber

It is unclear whether DC&#x27;s breach-notification statute independently confers a private right of action distinct from AG enforcement; IAPP&#x27;s multistate breach-law chart notes that only some (not all) state breach statutes include this feature.

Claims (5):

- D.C. breach-notification statute — whether it independently confers a private right of action
- D.C. Law 26-187 § 28-3905(m)(2)(A) — Private plaintiffs may recover treble damages or $3,000 per violation (whichever is greater), plus attorneys&#x27; fees, punitive damages and injunctions; adjusted annually by greater of 3% or DC CPI
- A law-firm analysis reports D.C. Law 26-187 enhances private CPPA rights of action with treble damages and fee-shifting.
- D.C. Code § 28-3852 — Treble damages or $1,500 per violation (whichever is greater), plus actual damages and attorney fees, enforceable by the DC Attorney General as an unfair/deceptive trade practice or by private right of action.
- D.C. Consumer Security Breach Notification Act (D.C. Code §§ 28-3851-3853, as amended by D.C. Law 23-98) — Breach-notification and data-security-safeguards violations are classified as unfair/deceptive trade practices under § 28-3904(kk); private-right-of-action recovery for these violations is limited to actual damages (not treble/$1,500 minimum) per § 28-3905(k)(2)(A)(ii), plus attorney&#x27;s fees, punitive damages and injunctive relief. Where SSN/taxpayer ID is or may be involved, entity must offer affected DC residents identity-theft protection services free for at least 18 months.

#### Recent developments 180dAmber

The federal SECURE Data Act (H.R. 8413), introduced 22 April 2026 with a broad state-law preemption clause, is the most significant development bearing on DC&#x27;s privacy landscape within the last 180 days; it remains pending in committee and is opposed by an 18-state AG coalition.

Claims (2):

- SECURE Data Act (H.R. 8413) — April 22, 2026, with broad state-law preemption clause; pending committee
- B26-0670 (DC Government Data Privacy and Protection Act of 2026) — Introduced 27 April 2026, referred to Committee on Public Works and Operations, with a public hearing held 29 June 2026; no further action located since, and none within this cycle&#x27;s 18-25 October window.

The D.C. Attorney General enforces the breach-notification statute and general consumer-protection law, frequently acting in coalition with other state AGs and the FTC (e.g., the AshleyMadison multistate settlement, joint telemarketing sweeps). No DP-specific statutory penalty schedule beyond the breach statute&#x27;s enforcement authority was identified, and it is unclear from available secondary sources whether DC&#x27;s breach statute independently confers a private right of action distinct from AG enforcement. The most significant recent development within the last 180 days is the federal SECURE Data Act (H.R. 8413), introduced 22 April 2026, which -- if enacted -- would preempt state and District sectoral/comprehensive privacy laws under a broad &#x27;relates to&#x27; preemption clause; it remains in committee/hearing stage and has drawn opposition from a coalition of 18 state attorneys general.

Periodic update · new data 2026-11-04 The District&#x27;s enforcement and redress landscape for data-protection matters tightened materially with D.C. Law 26-187, the Enhancing Consumer Protection Procedures Amendment Act of 2026, which took effect on 26 September 2026. The amendment adds mandatory minimum penalties and asset-freeze injunctive relief to the Attorney General&#x27;s existing powers under the Consumer Protection Procedures Act. Because data-handling conduct toward District consumers can itself amount to an unfair or deceptive practice under that Act, the strengthened remedies reach data-protection-adjacent enforcement even though the amendment is not a privacy statute as such. Mandatory minimums remove the previous latitude to resolve matters for token penalties, and asset-freeze powers let the Attorney General immobilize proceeds ahead of a final judgment rather than waiting out the ordinary litigation timeline.

The breach-notification statute separately confers a private right of action, so an affected individual may sue directly for treble damages or fifteen hundred dollars per violation, whichever is greater, together with actual damages and attorney fees, independently of any action the Attorney General chooses to bring. This dual-track structure, Attorney General enforcement under the strengthened Consumer Protection Procedures Act on one side and a standing private right of action under the breach-notification statute on the other, gives the District two independent and now more consequential avenues of redress for data-handling failures, even without a dedicated omnibus privacy enforcement authority of the kind found in jurisdictions with a standalone data-protection regulator.

#### Outlook

With the amendment now in force, expect the Attorney General to rely on the mandatory-minimum and asset-freeze toolkit in future data-handling and breach-related enforcement matters, not only in the consumer-facing crypto-kiosk litigation where it has already been applied. The continuing availability of a private right of action under the breach-notification statute means that affected individuals retain a redress route independent of Attorney General priorities, and the two tracks together are likely to produce a more active enforcement tempo than the District has shown previously.

5 earlier distinct updates Periodic update · new data 2026-10-25 The District of Columbia&#x27;s enforcement posture in data protection continues to run through two general-purpose instruments rather than a dedicated privacy statute: the Consumer Protection Procedures Act and the Consumer Security Breach Notification provisions codified in the D.C. Code. The clearest marker of this posture reaching final resolution is the Attorney General&#x27;s multistate settlement with Google LLC, announced in December 2023 and valued at 700 million dollars across participating jurisdictions, which addressed anticompetitive practices in the distribution of Android applications and the processing of in-app payments. That matter reached final judgment on 18 August 2026. Although the underlying conduct sounds principally in competition law, the settlement sits inside this monitor&#x27;s enforcement-and-redress frame because it was the Attorney General, acting under the District&#x27;s general consumer-protection authority, who brought and resolved it, and because the remedies touch data-adjacent platform practices that a dedicated privacy regulator would otherwise address directly.

The District&#x27;s breach-notification statute carries its own distinct enforcement architecture. It applies to any person or entity that owns, licenses, maintains, handles, or otherwise possesses electronic personal information of a District resident, regardless of where that entity is physically located, meaning the statute&#x27;s reach is tied to the residency of the affected individual rather than to the domicile of the regulated entity. Civil penalties attach on a per-violation basis: up to 5,000 dollars for a first violation and up to 10,000 dollars for a repeat violation, with economic damages, costs and fees recoverable in addition. Organizations whose breach affects 50 or more District residents carry a separate, free-standing obligation to notify the Attorney General, independent of their obligation to notify the affected individuals themselves. Together these two instruments, the general consumer-protection statute and the breach-notification statute, constitute the entire enforcement toolkit available to the Attorney General in the absence of an omnibus data-protection law, and the Google resolution demonstrates that toolkit being exercised against a significant commercial actor at meaningful scale notwithstanding that absence.

The pending Personal Health Data Security Amendment Act, still before the Committee on Health since its 23 March 2026 roundtable hearing, is relevant to this frame because Attorney General testimony on that bill recommended extending actionability under the Consumer Protection Procedures Act to health-data violations specifically, including for private suits in addition to public enforcement. That recommendation, if adopted, would formalize what the Google matter already demonstrates in practice: that the District&#x27;s enforcement architecture treats the general consumer-protection statute as the default vehicle for data-related harms, extending its reach sector by sector rather than replacing it with a comprehensive privacy law. No markup or vote on that bill has been identified, so the recommendation remains testimony rather than law.

#### Outlook

With the Google settlement now closed by final judgment, the enforcement question going forward is whether the Attorney General brings a comparable action under the same general-purpose statutes before any omnibus privacy law or health-data-specific statute is enacted. The Personal Health Data Security Amendment Act&#x27;s path through the Committee on Health, and specifically whether the Attorney General&#x27;s recommendation to make health-data violations actionable under the Consumer Protection Procedures Act is incorporated into any committee print, is the development most likely to reshape this enforcement architecture if it moves. Absent that, the District&#x27;s redress mechanism for data-related harm will remain the breach-notification penalty schedule and general consumer-protection litigation, as it has been through this cycle.

Periodic update · new data 2026-10-18 The District of Columbia&#x27;s enforcement posture in data protection continues to run through two general-purpose instruments rather than a dedicated privacy statute: the Consumer Protection Procedures Act and the Consumer Security Breach Notification provisions codified in the D.C. Code. The clearest marker of this posture reaching final resolution this cycle is the Attorney General&#x27;s multistate settlement with Google LLC, announced in December 2023 and valued at 700 million dollars across participating jurisdictions, which addressed anticompetitive practices in the distribution of Android applications and the processing of in-app payments. That matter reached final judgment on 18 August 2026. Although the underlying conduct sounds principally in competition law, the settlement sits inside this monitor&#x27;s enforcement-and-redress frame because it was the Attorney General, acting under the District&#x27;s general consumer-protection authority, who brought and resolved it, and because the remedies touch data-adjacent platform practices that a dedicated privacy regulator would otherwise address directly.

The District&#x27;s breach-notification statute carries its own distinct enforcement architecture. It applies to any person or entity that owns, licenses, maintains, handles, or otherwise possesses electronic personal information of a District resident, regardless of where that entity is physically located, meaning the statute&#x27;s reach is tied to the residency of the affected individual rather than to the domicile of the regulated entity. Civil penalties attach on a per-violation basis: up to 5,000 dollars for a first violation and up to 10,000 dollars for a repeat violation, with economic damages, costs and fees recoverable in addition. Organizations whose breach affects 50 or more District residents carry a separate, free-standing obligation to notify the Attorney General, independent of their obligation to notify the affected individuals themselves. Together these two instruments, the general consumer-protection statute and the breach-notification statute, constitute the entire enforcement toolkit available to the Attorney General in the absence of an omnibus data-protection law, and the Google resolution demonstrates that toolkit being exercised against a significant commercial actor at meaningful scale notwithstanding that absence.

The pending Personal Health Data Security Amendment Act, still before the Committee on Health since its 23 March 2026 roundtable hearing, is relevant to this frame because Attorney General testimony on that bill recommended extending actionability under the Consumer Protection Procedures Act to health-data violations specifically, including for private suits in addition to public enforcement. That recommendation, if adopted, would formalize what the Google matter already demonstrates in practice: that the District&#x27;s enforcement architecture treats the general consumer-protection statute as the default vehicle for data-related harms, extending its reach sector by sector rather than replacing it with a comprehensive privacy law. No markup or vote on that bill has been identified this cycle, so the recommendation remains testimony rather than law.

#### Outlook

With the Google settlement now closed by final judgment, the enforcement question going forward is whether the Attorney General brings a comparable action under the same general-purpose statutes before any omnibus privacy law or health-data-specific statute is enacted. The Personal Health Data Security Amendment Act&#x27;s path through the Committee on Health, and specifically whether the Attorney General&#x27;s recommendation to make health-data violations actionable under the Consumer Protection Procedures Act is incorporated into any committee print, is the development most likely to reshape this enforcement architecture if it moves. Absent that, the District&#x27;s redress mechanism for data-related harm will remain the breach-notification penalty schedule and general consumer-protection litigation, as it has been through this cycle.

Periodic update · new data 2026-10-11 DC&#x27;s data-protection enforcement toolkit was materially expanded by D.C. Law 26-187, effective 26 September 2026. The law expressly authorizes asset freezes as injunctive relief and sets mandatory minimum penalties for violations, together with recovery of costs and fees for enforcement and investigative measures in Attorney General actions. These powers are reported to extend to enforcement of the Consumer Protection Procedures Act&#x27;s breach-notification provisions, meaning the Attorney General&#x27;s office now holds a considerably larger remedial toolkit for pursuing a failure to meet DC&#x27;s existing breach-notice duties under D.C. Code § 28-3852 — which requires notice to affected DC residents in the most expedient time possible and without unreasonable delay, with entities notifying 1,000 or more individuals also required to inform nationwide consumer reporting agencies, and which requires written notice to the Office of the Attorney General, no later than the time notice is sent to affected residents, for breaches affecting 50 or more DC residents, containing eleven enumerated items.

A law-firm analysis of the statute additionally reports that it enhances private rights of action under the CPPA with treble damages and fee-shifting, applicable across covered sectors including financial services. This enhancement has not been independently verified against DC Code text at the specific statutory pinpoint, and is presented here as a reported rather than a confirmed finding pending that verification.

Taken together, DC&#x27;s data-protection enforcement regime now rests on a materially strengthened statutory base, even though the substantive privacy obligations beyond breach notification remain undeveloped relative to comprehensive state privacy laws elsewhere. The breach-notification duty itself, and its content and timing requirements, are unchanged this cycle; what changed is the severity and scope of remedies available against a violation of that duty.

#### Outlook

The next item to resolve for this jurisdiction is independent verification of the reported treble-damages and fee-shifting enhancement to CPPA private rights of action against the DC Code text. No enforcement action has yet been identified under the newly authorized asset-freeze or mandatory-minimum-penalty powers; whether and how the Attorney General&#x27;s office exercises these new powers in a breach-notification matter is the development to watch.

Periodic update · new data 2026-09-28 The District of Columbia&#x27;s enforcement mechanism for data-protection violations operates through its consumer-protection statute rather than a dedicated privacy regulator. The DC Office of the Attorney General enforces the District&#x27;s breach-notification requirements as unfair trade practices under the Consumer Protection Procedures Act, giving breach-notification violations the procedural and remedial character of a consumer-protection matter rather than a bespoke privacy enforcement action. This standing enforcement authority is confirmed and unchanged this cycle.

The statutory basis for the underlying breach-notification duty is the Security Breach Protection Amendment Act (D.C. Law 23-98), which took effect on 17 June 2020 and amended DC Code § 28-3852. This amendment is the current operative version of the District&#x27;s breach-notification law, and the DC Attorney General&#x27;s enforcement authority attaches to obligations set under this amended text.

On the specific mechanics of notification to the regulator, it is understood that the District&#x27;s breach-notification law requires written notice to the Attorney General when a breach affects fifty or more District residents. This particular threshold figure is drawn from a secondary summary source this cycle rather than from independently re-verified primary DC Code text, and is reported here in qualified terms accordingly. Should a future cycle locate the primary statutory provision fixing this exact numerical threshold, this figure could be upgraded to assertive framing.

Taken together, the enforcement and redress picture in DC is one of a functioning, if narrowly scoped, breach-notification enforcement regime: the DC Attorney General has clear statutory authority to treat breach-notification failures as unfair trade practices, but this authority operates alongside the absence of a comprehensive consumer-privacy statute, meaning redress avenues outside the breach-notification context (such as for unlawful processing or denial of data-subject rights) are not established in the District&#x27;s own law.

#### Outlook

The enforcement posture is likely to remain stable absent new DC Council legislation establishing a comprehensive privacy statute. The principal open item is verification of the exact statutory notification threshold, and whether any DC Attorney General enforcement action under this authority has been brought or is pending; neither was independently located this cycle. A future cycle locating either a primary-source confirmation of the fifty-resident threshold, or a specific enforcement action taken under this authority, would sharpen this module&#x27;s assessment.

Periodic update · new data 2026-09-22 The District of Columbia&#x27;s data-protection enforcement architecture is concentrated entirely in its breach-notification statute, which operates through incorporation into the District&#x27;s unfair-and-deceptive-trade-practices regime rather than through any dedicated privacy regulator or standalone penalty structure. Violations of the breach-notification obligation under D.C. Code Section 28-3852 may be enforced as unfair or deceptive trade practices, a mechanism that confers enforcement authority on the DC Attorney General while also creating a private right of action for affected consumers. This dual-track enforcement structure, combining public and private enforcement of the same underlying obligation, is a confirmed and materially significant feature of the District&#x27;s regime, since it means that any covered entity&#x27;s exposure is not limited to regulator-initiated action.

The penalty structure attached to this enforcement mechanism is substantial relative to a purely procedural notification duty. Violations may be treated as an unfair and deceptive trade practice, subjecting entities to treble damages or 1,500 dollars per violation, whichever is greater, plus actual damages, and separately requiring the provision of eighteen months of free identity-theft protection services where the breach involved Social Security numbers or taxpayer identification numbers. This combination of statutory damages, actual damages, and mandatory remediation services gives affected DC residents a meaningfully stronger private-enforcement position than exists under many comparable state breach-notification regimes, several of which limit private recourse or omit a private right of action entirely.

Because DC has no comprehensive omnibus privacy statute, this UDAP-incorporated breach-notification enforcement mechanism functions as the District&#x27;s primary, and effectively only, data-protection enforcement surface identified this cycle. There is no independent DC privacy regulator analogous to a state attorney general&#x27;s dedicated privacy unit or a standalone data-protection authority; enforcement runs through the general consumer-protection enforcement apparatus, applied specifically to breach-notification violations. Federal Trade Commission Section 5 authority operates alongside this District-level mechanism for entities within FTC jurisdiction, though no FTC action specific to DC was identified this cycle.

#### Outlook

Enforcement volume under this UDAP/breach-notification regime over the trailing twelve months was not located this cycle, leaving an open evidentiary gap about how actively the private right of action and the DC Attorney General&#x27;s own enforcement authority are actually being exercised against covered entities. Whether the D.C. Council has introduced any comprehensive consumer-privacy bill that would supplement or supersede this breach-notification-centered enforcement architecture was likewise not established this cycle. Either development, if it surfaced, would materially change the current picture of a District whose entire data-protection enforcement exposure runs through a single statutory mechanism.

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

Sources and claims (23)
- [DC Law Library — DC Code §28-3852](https://code.dccouncil.gov/us/dc/council/code/sections/28-3852) — Office of the Attorney General for the District of Columbia — Enhanced remedies including asset freezes and mandatory minimum penalties in AG consumer-protection enforcement actions
- [DataGuidance](https://www.dataguidance.com/jurisdiction/district-of-columbia) — Google LLC — DC AG&#x27;s $700M multistate settlement with Google over anticompetitive practices in Android app distribution and in-app payment processing, announced Dec 2023, reached final judgment on 18 August 2026.
- [databreachcost.com](https://databreachcost.com/breach-notification-laws/district-of-columbia) — DC&#x27;s AG enforcement toolkit for data-protection (breach-notification) violations now includes asset freezes and mandatory minimum penalties.
- [DC Council LIMS](https://lims.dccouncil.gov/Legislation/B26-0670) — D.C. Law 26-187 authorizes AG subpoena/interrogatory power and asset freezes.
- [CaseGuard](https://caseguard.com/articles/new-data-breach-notification-law-in-washington-d-c/) — D.C. Law 26-187 sets mandatory minimum CPPA penalties.
- [databreachcost.com](https://databreachcost.com/breach-notification-laws/district-of-columbia) — DC breach-notification statute — Violations of DC&#x27;s breach-notification law may be treated as an unfair and deceptive trade practice, subjecting entities to treble damages or $1,500 per violation plus actual damages, and requiring free 18-month identity-theft protection for SSN/TIN breaches.
- [Federal Trade Commission](https://www.ftc.gov/system/files/ftc_gov/pdf/p238400_ftc_collaboration_act_report.pdf) — District of Columbia Office of the Attorney General — parens patriae and general consumer-protection enforcement authority
- [NAAG](https://www.naag.org/issues/consumer-protection/consumer-protection-101/privacy/data-breaches/) — District of Columbia — significant multistate privacy enforcement actions
- [IAPP](https://iapp.org/resources/article/state-data-breach-notification-chart) — D.C. breach-notification statute — whether it independently confers a private right of action
- [IAPP](https://iapp.org/news/a/secure-data-act-analysis-of-the-new-federal-privacy-bill) — SECURE Data Act (H.R. 8413) — April 22, 2026, with broad state-law preemption clause; pending committee
- [RecordingLaw](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/) — DC breach-notification law — DC&#x27;s data-breach law requires written notice to the Attorney General when a breach affects 50 or more District residents.
- [CaseGuard](https://caseguard.com/articles/new-data-breach-notification-law-in-washington-d-c/) — D.C. Code § 28-3852 — Treble damages or $1,500 per violation (whichever is greater), plus actual damages and attorney fees, enforceable by AG and via private right of action for breach-notification violations
- [DC Law Library — DC Code §28-3852](https://code.dccouncil.gov/us/dc/council/code/sections/28-3852) — DC Code §28-3909(b) — Civil penalty of up to $5,000 per violation (first) and up to $10,000 per violation (repeat), plus economic damages, costs and attorneys&#x27; fees.
- [CaseGuard](https://caseguard.com/articles/new-data-breach-notification-law-in-washington-d-c/) — D.C. Law 26-187 § 28-3905(m)(2)(A) — Private plaintiffs may recover treble damages or $3,000 per violation (whichever is greater), plus attorneys&#x27; fees, punitive damages and injunctions; adjusted annually by greater of 3% or DC CPI
- [LegiScan](https://legiscan.com/DC/bill/B26-0525/2025) — A law-firm analysis reports D.C. Law 26-187 enhances private CPPA rights of action with treble damages and fee-shifting.
- [https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/data-breach-notification/](https://www.recordinglaw.com/us-laws/data-privacy-laws/district-of-columbia-data-privacy-laws/data-breach-notification/) — D.C. Code § 28-3909(b) — Civil penalty of up to $5,000 per violation for a first breach-notification violation and up to $10,000 per violation for a repeat violation, plus economic damages, costs and fees; organizations reaching 50+ affected DC residents must separately notify the Attorney General.
- [CaseGuard](https://caseguard.com/articles/new-data-breach-notification-law-in-washington-d-c/) — DC Office of the Attorney General — Multistate settlements of over $350,000 against Blackbaud (ransomware attack), $600 million against Equifax, and $148 million against Uber over delayed breach notification.
- [BillTrack50](https://www.billtrack50.com/billdetail/2001968) — B26-0670 (DC Government Data Privacy and Protection Act of 2026) — Introduced 27 April 2026, referred to Committee on Public Works and Operations, with a public hearing held 29 June 2026; no further action located since, and none within this cycle&#x27;s 18-25 October window.
- [DC Law Library — DC Code §28-3852](https://code.dccouncil.gov/us/dc/council/code/sections/28-3852) — D.C. Code § 28-3852 — Treble damages or $1,500 per violation (whichever is greater), plus actual damages and attorney fees, enforceable by the DC Attorney General as an unfair/deceptive trade practice or by private right of action.
- [Council of the District of Columbia](https://code.dccouncil.gov/us/dc/council/laws/26-187) — D.C. Law 26-187 — Amends AG investigatory/enforcement powers: interrogatories, protective-order sharing with law enforcement, service by any method reasonably calculated to give actual notice, use of sworn statements in perjury prosecutions, asset-freeze injunctive relief without bond and without AG having to prove damages, mandatory minimum penalties ($500 first violation, $1,000 subsequent), aiding-and-abetting liability, cost/fee recovery.
- [Council of the District of Columbia](https://code.dccouncil.gov/us/dc/council/laws/23-98) — D.C. Consumer Security Breach Notification Act (D.C. Code §§ 28-3851-3853, as amended by D.C. Law 23-98) — Breach-notification and data-security-safeguards violations are classified as unfair/deceptive trade practices under § 28-3904(kk); private-right-of-action recovery for these violations is limited to actual damages (not treble/$1,500 minimum) per § 28-3905(k)(2)(A)(ii), plus attorney&#x27;s fees, punitive damages and injunctive relief. Where SSN/taxpayer ID is or may be involved, entity must offer affected DC residents identity-theft protection services free for at least 18 months.
- [DataGuidance](https://www.dataguidance.com/notes/district-columbia-data-breach) — D.C. Code § 28-3852(a) — Any person or entity conducting business in DC that owns/licenses computerized personal information must notify any DC resident whose personal information was included in a breach -- a combined business-nexus-plus-residency test, not pure residency.
- [DC Office of the Attorney General](https://oag.dc.gov/release/attorney-general-schwalb-alerts-district-residents) — $700 million multistate Google Play Store antitrust settlement — DC OAG&#x27;s own release references a final-approval hearing set for 2026-04-30; other secondary reporting references an August 2026 final-approval date; sources are inconsistent and not reconciled this cycle. DC&#x27;s reported share of penalties is approximately $2 million.

## GDPR article map

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

Show article map GDPR article to category mapping Article Category Sub-module

Art. 5 [Controller/Processor Duties](#sec-cat-controller-processor-duties) accountability and dpia

Art. 6 [Lawful Processing & Special Data](#sec-cat-lawful-processing-and-special-data) lawful bases

Art. 7 [Lawful Processing & Special Data](#sec-cat-lawful-processing-and-special-data) consent thresholds

Art. 9 [Lawful Processing & Special Data](#sec-cat-lawful-processing-and-special-data) special categories

Art. 13 [Data Subject Rights](#sec-cat-data-subject-rights) deadlines and response windows

Art. 14 [Data Subject Rights](#sec-cat-data-subject-rights) deadlines and response windows

Art. 15 [Data Subject Rights](#sec-cat-data-subject-rights) access right

Art. 16 [Data Subject Rights](#sec-cat-data-subject-rights) rectification and erasure

Art. 17 [Data Subject Rights](#sec-cat-data-subject-rights) rectification and erasure

Art. 18 [Data Subject Rights](#sec-cat-data-subject-rights) restriction and objection

Art. 19 [Data Subject Rights](#sec-cat-data-subject-rights) rectification and erasure

Art. 20 [Data Subject Rights](#sec-cat-data-subject-rights) data portability

Art. 21 [Data Subject Rights](#sec-cat-data-subject-rights) restriction and objection

Art. 22 [Algorithmic, Biometric & Surveillance Governance](#sec-cat-algorithmic-biometric-and-surveillance-governance) automated decision making transparency

Art. 25 [Controller/Processor Duties](#sec-cat-controller-processor-duties) accountability and dpia

Art. 28 [Controller/Processor Duties](#sec-cat-controller-processor-duties) joint controller arrangements

Art. 30 [Controller/Processor Duties](#sec-cat-controller-processor-duties) ropa requirements

Art. 32 [Controller/Processor Duties](#sec-cat-controller-processor-duties) security measures

Art. 33 [Controller/Processor Duties](#sec-cat-controller-processor-duties) breach notification

Art. 34 [Controller/Processor Duties](#sec-cat-controller-processor-duties) breach notification

Art. 35 [Controller/Processor Duties](#sec-cat-controller-processor-duties) accountability and dpia

Art. 37 [Controller/Processor Duties](#sec-cat-controller-processor-duties) dpo requirements

Art. 38 [Controller/Processor Duties](#sec-cat-controller-processor-duties) dpo requirements

Art. 39 [Controller/Processor Duties](#sec-cat-controller-processor-duties) dpo requirements

Art. 44 [Cross-Border & Adequacy](#sec-cat-cross-border-and-adequacy) transfer mechanisms

Art. 45 [Cross-Border & Adequacy](#sec-cat-cross-border-and-adequacy) adequacy received

Art. 46 [Cross-Border & Adequacy](#sec-cat-cross-border-and-adequacy) adequacy granted

Art. 47 [Cross-Border & Adequacy](#sec-cat-cross-border-and-adequacy) sccs and bcrs

Art. 48 [Cross-Border & Adequacy](#sec-cat-cross-border-and-adequacy) sccs and bcrs

Art. 49 [Cross-Border & Adequacy](#sec-cat-cross-border-and-adequacy) transfer mechanisms

Art. 77 [Enforcement & Redress](#sec-cat-enforcement-and-redress) private right of action

Art. 78 [Enforcement & Redress](#sec-cat-enforcement-and-redress) regulator powers and penalties

Art. 79 [Enforcement & Redress](#sec-cat-enforcement-and-redress) regulator powers and penalties

Art. 80 [Enforcement & Redress](#sec-cat-enforcement-and-redress) regulator powers and penalties

Art. 81 [Enforcement & Redress](#sec-cat-enforcement-and-redress) regulator powers and penalties

Art. 82 [Enforcement & Redress](#sec-cat-enforcement-and-redress) regulator powers and penalties

Art. 83 [Enforcement & Redress](#sec-cat-enforcement-and-redress) collective redress and class actions

Art. 84 [Enforcement & Redress](#sec-cat-enforcement-and-redress) regulator powers and penalties
