Data Protection Monitor
Global Privacy & Data Protection Intelligence

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

Maryland, USA Data Protection & Privacy Regulation

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

Last updated · 10 categories · 102 claims · 55 sources in the cumulative register

Maryland's Online Data Privacy Act (MODPA) sensitive-data perimeter expanded this cycle through House Bill 711, which became law on May 31, 2026 without the Governor's signature and took effect July 1, 2026.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Lawful Processing & Special Data, Data Subject Rights (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 12 binding instruments
Supervisory authorityMaryland Attorney General
Next milestone
APR12027
MODPA 60-day cure period sunsets
Record & confidence mix102 claims · 45 sources · machine-compiled
1 Confirmed87 Probable11 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

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

Jurisdiction brief

Latest update · 4 November 2026

Lead Signal

Maryland's data-protection regime has moved decisively into a tightening posture as its Online Data Privacy Act (MODPA) is joined by two 2026 legislative amendments and a new sector-specific statute curbing AI-driven personalized pricing. The Maryland Attorney General holds exclusive enforcement authority over MODPA, and the statute does not grant consumers a private right of action. Effective July 1, 2026, Chapter 874 (HB 711) widened the inferred-sensitive-data test and added protections tied to the sale of personal data connected to immigration enforcement. A further amendment, Chapter 435 (HB 264), took effect October 1, 2026, though its substantive content has not been independently verified beyond a single aggregator citation. Separately, the Protection From Predatory Pricing Act (HB 895) entered into force on October 1, 2026, prohibiting food retailers and third-party delivery services from engaging in personalized "dynamic pricing" based on consumer personal data, and from using protected-class data to withhold a pricing advantage.

Key regulatory facts for Maryland, USA
Key regulatory facts for Maryland, USA
Regulatory DimensionMaryland, USA Standing Position
JurisdictionMaryland, USA (US-MD)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 102 sourced findings)
Regulator & FrameworkComprehensive statute is in force, but enforcement runs through a general AG office with no dedicated agency, and companion Kids Code faces First-Amendment-style litigation risk seen in peer states.
Lawful Processing & Special DataStrong substantive protections exist for sensitive data, but pseudonymisation/anonymisation safe-harbour provisions were not located in available sources.
Data Subject RightsCore rights are confirmed but the specific response-deadline figure is unverified against primary statutory text in this run.
Controller/Processor DutiesCore accountability and breach-notification duties are confirmed; DPO and retention-specific provisions are unconfirmed absences.
Primary Instruments CitedMaryland, USA Official Instrument (enzuzo.com maryland-online-data-privacy-act), DataGuidance (legacy), OneTrust, Morgan Lewis, Didomi
Last Confirmed / Updated (55 sources in cumulative register)

#

Comprehensive statute is in force, but enforcement runs through a general AG office with no dedicated agency, and companion Kids Code faces First-Amendment-style litigation risk seen in peer states.

Primary frameworkMaryland Online Data Privacy Act (MODPA), 2024
Traffic-light rationale — AmberComprehensive statute is in force, but enforcement runs through a general AG office with no dedicated agency, and companion Kids Code faces First-Amendment-style litigation risk seen in peer states.

Sub-modules (5)

Regulator and authorityAmber

The Maryland AG holds exclusive enforcement authority over MODPA; there is no separate privacy supervisory authority.

Claims (6):

  • The Maryland Attorney General has exclusive authority to enforce MODPA, with no dedicated state data protection authority.
  • Maryland Online Data Privacy Act (MODPA) — Enforceable solely by the Maryland Attorney General's Consumer Protection Division; a violation is treated as an unfair, abusive, or deceptive trade practice under the Maryland Consumer Protection Act; no private right of action.
  • Consumer Protection Division, Office of the Attorney General of Maryland — MODPA is enforced exclusively by the Consumer Protection Division of the Maryland Attorney General's Office, with violations treated as unfair, abusive, or deceptive trade practices under the Maryland Consumer Protection Act.
  • The Maryland Attorney General has exclusive enforcement authority over MODPA; MODPA creates no private right of action.
  • Maryland Attorney General, Consumer Protection Division — MODPA is enforced exclusively by the Maryland AG's Consumer Protection Division; no private right of action exists.
  • Maryland Online Data Privacy Act (MODPA) — MODPA Com. Law §14-4713 treats a violation as an unfair, abusive, or deceptive trade practice under the Maryland Consumer Protection Act Title 13, enforceable exclusively by the Attorney General's Consumer Protection Division; there is no private right of action.

Act and instrumentsGreen

Core instruments are MODPA, the Maryland Kids Code, and the pre-existing PIPA breach-notification statute.

Claims (10):

  • MODPA was signed May 9, 2024, came into effect October 1, 2025, but does not apply to processing occurring before April 1, 2026.
  • The Maryland Kids Code (Age-Appropriate Design Code / Online Child Protection Act), effective October 1, 2024, remains fully in effect despite ongoing constitutional litigation of the kind seen against peer-state AADC laws.
  • Maryland's Personal Information Protection Act (PIPA), Md. Code Ann., Comm. Law §14-3504, is a pre-existing breach-notification statute enforced by the AG, operating independently of MODPA.
  • MODPA — Took effect 2025-10-01; processing obligations apply only to activity on or after 2026-04-01.
  • Chapter 435 of 2026 (HB264) further amended MODPA, effective October 1, 2026.
  • House Bill 711 (2026) — Effective 2026-07-01, amends MODPA to restrict selling personal data in connection with immigration enforcement and widens the sensitive-data definition.
  • HB711/Ch.874, effective July 1, 2026, amended MODPA to widen protections around sale of personal data and the inferred-sensitive-data test.
  • MODPA (SB541/HB567, 2024) took effect October 1, 2025; HB711 (Ch.874 of 2026) amended it effective July 1, 2026, recodifying sections from Subtitle 46 to Subtitle 47 (§§14-4701-14-4714).
  • HB711 (Chapter 874 of 2026) — HB711 amended MODPA effective July 1, 2026 to expand the definition of sensitive data to include inferred sensitive data and to restrict sale of personal data to government entities that have recently engaged in or supported immigration enforcement, subject to a valid-court-warrant exception.
  • Maryland Online Data Privacy Act of 2024 — Approved by Governor Wes Moore May 9, 2024 as SB 541 (cross-filed HB 567), Chapter 455 of the 2024 Regular Session

Material scopeAmber

MODPA applies on population/revenue thresholds and carves out government entities and several federally-regulated data types.

Claims (5):

  • MODPA applies to controllers/processors that controlled or processed personal data of at least 35,000 consumers (excluding payment-transaction-only processing) or at least 10,000 consumers while deriving over 20% of gross revenue from selling personal data.
  • MODPA excludes Maryland state and local government entities, courts, and businesses/data already subject to the Gramm-Leach-Bliley Act, HIPAA, or FERPA.
  • MODPA — Applies to businesses that controlled/processed personal data of at least 35,000 Maryland consumers in the preceding year, or at least 10,000 if more than 20% of gross revenue derives from the sale of personal data.
  • MODPA applies to organizations that process the personal data of at least 35,000 consumers annually (excluding pure payment-transaction data) or that process data of at least 10,000 consumers and derive 20% or more of gross revenue from selling personal data.
  • MODPA applies to a controller that controlled or processed the personal data of at least 35,000 Maryland consumers in the preceding calendar year, or at least 10,000 consumers while deriving more than 20% of gross revenue from the sale of personal data.

Territorial scopeGreen

MODPA uses an effects-based test keyed to targeting of Maryland residents rather than establishment.

Claims (1):

  • MODPA applies to individuals/businesses providing products or services targeted to Maryland residents, an effects-based territorial test rather than one requiring in-state establishment.

Regulator registration and filingAmber

No general registration/filing regime exists; the AG may compel confidential DPIAs from controllers on request.

Claims (1):

  • MODPA does not create a general controller registration/filing regime; instead, the AG may request confidential DPIAs from controllers, shielded from disclosure under the Maryland Public Information Act.
Category narrative 66 words

Maryland's data-protection landscape is anchored by the Maryland Online Data Privacy Act (MODPA), enacted May 9, 2024 and effective October 1, 2025, enforced exclusively by the Maryland Attorney General with no dedicated privacy regulator. A companion Maryland Kids Code (Age-Appropriate Design Code) and a pre-existing breach-notification statute (Personal Information Protection Act, PIPA) round out the framework. There is no state privacy agency analogous to California's CPPA.

Periodic update · new data 2026-11-04

The Maryland Attorney General has exclusive enforcement authority over MODPA; the statute creates no private right of action, placing all enforcement discretion in the Attorney General's hands. The framework has been amended twice during 2026. Chapter 874 of 2026 (HB 711), effective July 1, 2026, widened the inferred-sensitive-data test and added protections around the sale of personal data tied to immigration enforcement. Chapter 435 of 2026 (HB 264) further amended the Act effective October 1, 2026, though the substance of that amendment reaches this record only through a single aggregator citation and has not been independently verified against the bill text; readers should treat its described effect as provisional pending confirmation at primary source.

Outlook

With two amendments now in force in a single year, Maryland's statutory framework is in a period of active legislative refinement rather than settled administration. The unverified scope of the October amendment is a near-term watch item, as is whether the Attorney General issues interpretive guidance on the "reasonably necessary and proportionate" standard that the amendments touch.

Sources and claims (23)
  1. Probable DataGuidance — The Maryland Attorney General has exclusive authority to enforce MODPA, with no dedicated state data protection authority. observed
  2. Probable DataGuidance — MODPA was signed May 9, 2024, came into effect October 1, 2025, but does not apply to processing occurring before April 1, 2026. observed
  3. Probable IAPP — The Maryland Kids Code (Age-Appropriate Design Code / Online Child Protection Act), effective October 1, 2024, remains fully in effect despite ongoing constitutional litigation of the kind seen against peer-state AADC laws. observed
  4. Probable Maryland Attorney General — Maryland's Personal Information Protection Act (PIPA), Md. Code Ann., Comm. Law §14-3504, is a pre-existing breach-notification statute enforced by the AG, operating independently of MODPA. observed
  5. Probable DataGuidance (legacy) — MODPA applies to controllers/processors that controlled or processed personal data of at least 35,000 consumers (excluding payment-transaction-only processing) or at least 10,000 consumers while deriving over 20% of gross revenue from selling personal data. observed
  6. Probable DataGuidance (legacy) — MODPA excludes Maryland state and local government entities, courts, and businesses/data already subject to the Gramm-Leach-Bliley Act, HIPAA, or FERPA. observed
  7. Probable DataGuidance (legacy) — MODPA applies to individuals/businesses providing products or services targeted to Maryland residents, an effects-based territorial test rather than one requiring in-state establishment. observed
  8. Probable DataGuidance (legacy) — MODPA does not create a general controller registration/filing regime; instead, the AG may request confidential DPIAs from controllers, shielded from disclosure under the Maryland Public Information Act. observed
  9. Probable OneTrust — Maryland Online Data Privacy Act (MODPA) — Enforceable solely by the Maryland Attorney General's Consumer Protection Division; a violation is treated as an unfair, abusive, or deceptive trade practice under the Maryland Consumer Protection Act; no private right of action. observed
  10. Probable EdLaw — MODPA — Took effect 2025-10-01; processing obligations apply only to activity on or after 2026-04-01. observed
  11. High PrivacyLawMap — Consumer Protection Division, Office of the Attorney General of Maryland — MODPA is enforced exclusively by the Consumer Protection Division of the Maryland Attorney General's Office, with violations treated as unfair, abusive, or deceptive trade practices under the Maryland Consumer Protection Act. observed
  12. Probable OneTrust — The Maryland Attorney General has exclusive enforcement authority over MODPA; MODPA creates no private right of action. observed
  13. Probable EdLaw — Chapter 435 of 2026 (HB264) further amended MODPA, effective October 1, 2026. observed
  14. Probable Morgan Lewis — House Bill 711 (2026) — Effective 2026-07-01, amends MODPA to restrict selling personal data in connection with immigration enforcement and widens the sensitive-data definition. observed
  15. Probable CC Office Solutions — MODPA — Applies to businesses that controlled/processed personal data of at least 35,000 Maryland consumers in the preceding year, or at least 10,000 if more than 20% of gross revenue derives from the sale of personal data. observed
  16. Probable EdLaw — HB711/Ch.874, effective July 1, 2026, amended MODPA to widen protections around sale of personal data and the inferred-sensitive-data test. observed
  17. Probable Didomi — Maryland Attorney General, Consumer Protection Division — MODPA is enforced exclusively by the Maryland AG's Consumer Protection Division; no private right of action exists. observed
  18. Probable Morgan Lewis — MODPA applies to organizations that process the personal data of at least 35,000 consumers annually (excluding pure payment-transaction data) or that process data of at least 10,000 consumers and derive 20% or more of gross revenue from selling personal data. observed
  19. Probable https://mgaleg.maryland.gov/mgawebsite/Legislation/Details/hb0711?ys=2026RS — MODPA (SB541/HB567, 2024) took effect October 1, 2025; HB711 (Ch.874 of 2026) amended it effective July 1, 2026, recodifying sections from Subtitle 46 to Subtitle 47 (§§14-4701-14-4714).
  20. Probable OneTrust — Maryland Online Data Privacy Act (MODPA) — MODPA Com. Law §14-4713 treats a violation as an unfair, abusive, or deceptive trade practice under the Maryland Consumer Protection Act Title 13, enforceable exclusively by the Attorney General's Consumer Protection Division; there is no private right of action. observed
  21. Probable EdLaw — HB711 (Chapter 874 of 2026) — HB711 amended MODPA effective July 1, 2026 to expand the definition of sensitive data to include inferred sensitive data and to restrict sale of personal data to government entities that have recently engaged in or supported immigration enforcement, subject to a valid-court-warrant exception. observed
  22. Probable Morgan Lewis — MODPA applies to a controller that controlled or processed the personal data of at least 35,000 Maryland consumers in the preceding calendar year, or at least 10,000 consumers while deriving more than 20% of gross revenue from the sale of personal data. observed
  23. Probable Maryland General Assembly — Maryland Online Data Privacy Act of 2024 — Approved by Governor Wes Moore May 9, 2024 as SB 541 (cross-filed HB 567), Chapter 455 of the 2024 Regular Session observed

#

Strong substantive protections exist for sensitive data, but pseudonymisation/anonymisation safe-harbour provisions were not located in available sources.

Primary frameworkMaryland Online Data Privacy Act (MODPA), 2024
Traffic-light rationale — AmberStrong substantive protections exist for sensitive data, but pseudonymisation/anonymisation safe-harbour provisions were not located in available sources.

Sub-modules (4)

Lawful basesAmber

MODPA substitutes a data-minimization necessity/proportionality test for an enumerated lawful-bases list.

Claims (5):

  • MODPA requires controllers to limit collection of personal data to what is reasonably necessary and proportionate to provide or maintain the product or service requested by the consumer, functioning as the primary processing-legitimacy standard in place of an enumerated lawful-bases regime.
  • MODPA — Requires businesses to limit data collection to what is strictly/reasonably necessary to provide a requested product or service.
  • Maryland Online Data Privacy Act (as amended by Ch. 874/HB 711, 2026) — Sale of personal data to governmental units engaged in civil immigration enforcement within preceding 6 months
  • Maryland Online Data Privacy Act — Controllers must limit collection of personal data to what is reasonably necessary and proportionate to the specific product/service requested; this duty has no consent-based exception (distinct from the separate §14-4707(a)(8) purpose-compatibility consent gateway)
  • Maryland Online Data Privacy Act (as amended by Ch. 874/HB 711, 2026) — Controller may not knowingly sell personal data to a federal, State, or local governmental unit that, within the 6 months preceding the sale, engaged in or supported civil immigration enforcement through personnel or material resources

Special categoriesGreen

Sensitive data is broadly defined and subject to a strict-necessity standard, an absolute sale ban, and health-facility geofencing restrictions.

Claims (7):

  • MODPA's 'sensitive data' definition includes racial/ethnic origin, religious beliefs, consumer health data, sexual orientation, transgender or non-binary status, citizenship/immigration status, genetic and biometric data, precise geolocation, and personal data known to belong to a child.
  • Rather than a consent-based model, MODPA bans collection, processing, or sharing of sensitive data unless 'strictly necessary' to provide the requested product/service, and separately prohibits the sale of sensitive data outright under section 14-4607, with no consent exception.
  • MODPA bans geofencing within 1,750 feet of a mental-health facility or reproductive/sexual-health facility for purposes of identifying, tracking, or targeting consumers in relation to consumer health data.
  • MODPA bans sale of sensitive data unconditionally and permits its collection/processing only when strictly necessary, regardless of consent.
  • HB 711 amends MODPA to expand the definition of sensitive data to include data inferred by a controller, alone or in combination with other data, to indicate a category of sensitive data, and restricts sale of personal data to governmental entities engaged in or supporting civil immigration enforcement within the preceding six months.
  • MODPA — Blanket prohibition on selling sensitive data (health, biometric, geolocation, and inferred sensitive data), which consent does not override.
  • MODPA §14-4707 — As amended by Ch.874 (HB711), effective July 1, 2026: controllers may not knowingly sell personal data to a government unit that engaged in or supported civil immigration enforcement within the preceding six months; 'sensitive data' expanded to include data a controller infers to indicate a protected category.

Pseudonymisation and anonymisationRed

No MODPA-specific pseudonymisation or anonymisation safe-harbour provision was located in the sources retrieved for this run.

Category narrative 43 words

MODPA departs from the GDPR/CCPA-style enumerated-lawful-basis model, instead imposing a substantive data-minimization standard ('reasonably necessary and proportionate') for ordinary personal data and a stricter 'strictly necessary' standard plus an outright sale ban for sensitive data, with no general consent override for sensitive-data sales.

Periodic update · new data 2026-10-13

Maryland's lawful-processing framework tightened on July 1, 2026 with the entry into force of House Bill 711 (Chapter 874 of 2026), which amends the Maryland Online Data Privacy Act (MODPA) and recodifies its provisions from Subtitle 46 to Subtitle 47 of the Commercial Law Article, now sections 14-4701 through 14-4714. The amendment introduces two distinct, substantively significant restrictions on controller conduct, both confirmed against the primary legislative text.

The first is a novel prohibition on knowingly selling personal data to a government unit that engaged in or supported civil immigration enforcement within the preceding six months. This is a conditional, time-bound restriction: it does not prohibit sale to any government unit in the abstract, but ties the prohibition to a specific category of government conduct, civil immigration enforcement, within a defined six-month look-back window. A controller selling personal data to a government purchaser must therefore assess, at the point of sale, whether that purchaser engaged in or supported civil immigration enforcement activity within the preceding six months, a factual inquiry that did not previously form part of MODPA's data-sale compliance analysis.

The second change expands the statutory definition of sensitive data to include data a controller infers to indicate that a consumer belongs to a protected category. This moves Maryland's special-category regime beyond data a data subject affirmatively discloses, extending it to the outputs of a controller's own analytical or profiling processes. Where a controller's inference engine concludes that a given individual likely falls within a protected category, whether or not the individual disclosed that status directly, the resulting inferred data point is now treated as sensitive data under MODPA, triggering whatever heightened consent, processing-restriction, or disclosure obligations attach to sensitive data elsewhere in the statute.

Both changes are confirmed at Confirmed confidence against a Tier-1 primary legislative source (the Maryland General Assembly's record of House Bill 711), and both are in force as of July 1, 2026. Taken together, they represent a substantive expansion of the obligations a controller must satisfy before engaging in either a data sale involving a government purchaser or any processing activity that generates inferred classifications of individuals.

Outlook

The principal open question is how Maryland's Attorney General applies the immigration-enforcement data-sale prohibition in practice: specifically, how a controller is expected to determine, at the point of a prospective data sale, whether a government-unit purchaser meets the six-month look-back condition, and what evidentiary standard the Attorney General's Consumer Protection Division would apply in any enforcement matter testing that determination. A second open question is how broadly the inferred-sensitive-data expansion is read in practice, particularly for ordinary analytics or personalization processing that was not designed to classify individuals into protected categories but may nonetheless generate outputs that fall within the expanded definition.

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

MODPA imposes a mandatory data-minimization duty on controllers, requiring collection to be limited to what is reasonably necessary and proportionate to the specified processing purpose; this duty is understood to apply regardless of whether the consumer has given consent, meaning consent does not expand the scope of permissible collection beyond what is reasonably necessary for the stated purpose. On special data, MODPA prohibits the sale of sensitive personal data outright, and consumer consent does not override that prohibition. The statute's concept of sensitive data is understood to extend to data that a controller infers and that indicates a sensitive category, rather than being limited to data collected directly in a sensitive category.

Outlook

The specific statutory pinpoint sections establishing the data-minimization standard and the scope of the inferred-sensitive-data concept have not been independently retrieved against primary MODPA text this period; the duty and the prohibition are reported consistently across secondary commentary but remain to be checked against the statute itself.

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

Sources and claims (15)
  1. Probable IAPP — MODPA requires controllers to limit collection of personal data to what is reasonably necessary and proportionate to provide or maintain the product or service requested by the consumer, functioning as the primary processing-legitimacy standard in place of an enumerated lawful-bases regime. observed
  2. Probable IAPP — Under MODPA, 'consent' requires an unambiguous affirmative action by the consumer, and the law's minimization-first design leaves consent as a comparatively residual legal basis. observed
  3. Probable IAPP — MODPA's 'sensitive data' definition includes racial/ethnic origin, religious beliefs, consumer health data, sexual orientation, transgender or non-binary status, citizenship/immigration status, genetic and biometric data, precise geolocation, and personal data known to belong to a child. observed
  4. Probable IAPP — Rather than a consent-based model, MODPA bans collection, processing, or sharing of sensitive data unless 'strictly necessary' to provide the requested product/service, and separately prohibits the sale of sensitive data outright under section 14-4607, with no consent exception. observed
  5. Probable IAPP — MODPA bans geofencing within 1,750 feet of a mental-health facility or reproductive/sexual-health facility for purposes of identifying, tracking, or targeting consumers in relation to consumer health data. observed
  6. Probable CC Office Solutions — MODPA bans sale of sensitive data unconditionally and permits its collection/processing only when strictly necessary, regardless of consent. observed
  7. High Covington & Burling — HB 711 amends MODPA to expand the definition of sensitive data to include data inferred by a controller, alone or in combination with other data, to indicate a category of sensitive data, and restricts sale of personal data to governmental entities engaged in or supporting civil immigration enforcement within the preceding six months. observed
  8. Probable Open Class Actions — MODPA — Requires businesses to limit data collection to what is strictly/reasonably necessary to provide a requested product or service. observed
  9. Probable Ketch — MODPA — Blanket prohibition on selling sensitive data (health, biometric, geolocation, and inferred sensitive data), which consent does not override. observed
  10. Probable Morgan Lewis — MODPA requires a data-minimization standard applying even where consent has been given. observed
  11. Probable https://mgaleg.maryland.gov/mgawebsite/Legislation/Details/hb0711?ys=2026RS — MODPA §14-4707 — As amended by Ch.874 (HB711), effective July 1, 2026: controllers may not knowingly sell personal data to a government unit that engaged in or supported civil immigration enforcement within the preceding six months; 'sensitive data' expanded to include data a controller infers to indicate a protected category.
  12. Probable Morgan Lewis — MODPA bans the sale of sensitive personal data under any circumstances; consumer consent does not override this prohibition. observed
  13. Probable Maryland General Assembly — Maryland Online Data Privacy Act (as amended by Ch. 874/HB 711, 2026) — Sale of personal data to governmental units engaged in civil immigration enforcement within preceding 6 months observed
  14. Probable Maryland General Assembly (mgaleg.maryland.gov) — Maryland Online Data Privacy Act — Controllers must limit collection of personal data to what is reasonably necessary and proportionate to the specific product/service requested; this duty has no consent-based exception (distinct from the separate §14-4707(a)(8) purpose-compatibility consent gateway) observed
  15. Probable Maryland General Assembly — Maryland Online Data Privacy Act (as amended by Ch. 874/HB 711, 2026) — Controller may not knowingly sell personal data to a federal, State, or local governmental unit that, within the 6 months preceding the sale, engaged in or supported civil immigration enforcement through personnel or material resources observed

#

Core rights are confirmed but the specific response-deadline figure is unverified against primary statutory text in this run.

Primary frameworkMaryland Online Data Privacy Act (MODPA), 2024
Traffic-light rationale — AmberCore rights are confirmed but the specific response-deadline figure is unverified against primary statutory text in this run.

Sub-modules (5)

Access rightGreen

Consumers may request access to personal data held by a controller.

Claims (1):

  • MODPA authorizes consumers to exercise rights regarding their personal data and requires controllers to establish a method for consumers to exercise those rights, encompassing access, correction, deletion, and portability.

Rectification and erasureGreen

Consumers may request correction and deletion of personal data.

Claims (1):

  • MODPA authorizes consumers to exercise rights regarding their personal data and requires controllers to establish a method for consumers to exercise those rights, encompassing access, correction, deletion, and portability.

Restriction and objectionAmber

Consumers may opt out of targeted advertising and sale; MODPA uniquely makes universal opt-out mechanism recognition optional rather than mandatory.

Claims (1):

  • MODPA describes universal opt-out mechanisms as an alternative to, rather than a mandatory replacement for, a conspicuous 'do not sell' link — the first instance of a state making universal opt-out signal recognition optional.

Data portabilityGreen

Consumers may obtain a portable copy of their personal data.

Claims (1):

  • MODPA authorizes consumers to exercise rights regarding their personal data and requires controllers to establish a method for consumers to exercise those rights, encompassing access, correction, deletion, and portability.

Deadlines and response windowsRed

Controllers must maintain an appeal process for denied requests; the exact response-window in days was not confirmed in this run's sources.

Claims (4):

  • MODPA requires controllers to establish an appeal process for consumers regarding controller decisions on rights requests.
  • The specific statutory number of days within which a Maryland controller must respond to a consumer rights request under MODPA was not confirmed against primary statutory text in this run; comparable Virginia-modeled state laws commonly use a 45-day window with a possible 45-day extension, but this has not been verified as MODPA's exact figure.
  • MODPA — Controller must offer a conspicuously available appeal process and respond in writing within 60 days of receiving the appeal under §14-4705(F).
  • MODPA — Controller must respond to a rights request within 45 days under §14-4705(E)(2), with one additional 45-day extension where reasonably necessary.
Category narrative 47 words

MODPA grants Maryland consumers access, correction, deletion, and portability rights, plus opt-outs from targeted advertising, sale, and certain profiling, with a mandatory controller-side appeal process for denied requests. The precise statutory response-window (days) for rights requests could not be confirmed from the sources retrieved in this run.

No periodic updates recorded in this cycle

Sources and claims (6)
  1. Probable DataGuidance — MODPA authorizes consumers to exercise rights regarding their personal data and requires controllers to establish a method for consumers to exercise those rights, encompassing access, correction, deletion, and portability. observed
  2. Probable IAPP — MODPA describes universal opt-out mechanisms as an alternative to, rather than a mandatory replacement for, a conspicuous 'do not sell' link — the first instance of a state making universal opt-out signal recognition optional. observed
  3. Probable DataGuidance (legacy) — MODPA requires controllers to establish an appeal process for consumers regarding controller decisions on rights requests. observed
  4. Uncertain IAPP — The specific statutory number of days within which a Maryland controller must respond to a consumer rights request under MODPA was not confirmed against primary statutory text in this run; comparable Virginia-modeled state laws commonly use a 45-day window with a possible 45-day extension, but this has not been verified as MODPA's exact figure. observed
  5. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/maryland-data-privacy-laws/ — MODPA — Controller must offer a conspicuously available appeal process and respond in writing within 60 days of receiving the appeal under §14-4705(F).
  6. Probable Fisher Phillips — MODPA — Controller must respond to a rights request within 45 days under §14-4705(E)(2), with one additional 45-day extension where reasonably necessary. observed

#

Core accountability and breach-notification duties are confirmed; DPO and retention-specific provisions are unconfirmed absences.

Primary frameworkMaryland Online Data Privacy Act (MODPA); Maryland Personal Information Protection Act (PIPA)
Traffic-light rationale — AmberCore accountability and breach-notification duties are confirmed; DPO and retention-specific provisions are unconfirmed absences.

Sub-modules (7)

Accountability & DPIAGreen

DPIAs are required for heightened-risk processing from October 1, 2025, and are confidential when requested by the AG.

Claims (3):

  • MODPA requires controllers to conduct data protection impact assessments for processing activities presenting a heightened risk of harm to consumers, applicable to processing occurring on or after October 1, 2025.
  • DPIAs requested by the Maryland AG under MODPA are confidential and exempt from disclosure under the Maryland Public Information Act.
  • MODPA — Requires controllers to conduct and document a data protection assessment for heightened-risk processing, uniquely requiring assessment of each algorithm used.

DPO requirementsRed

No MODPA provision mandating a formal Data Protection Officer appointment was located; this is consistent with most US state comprehensive privacy laws.

Claims (1):

  • No MODPA provision was located requiring controllers to appoint a formal Data Protection Officer; this omission is typical of the US state comprehensive-privacy-law model.

Ropa requirementsRed

No explicit records-of-processing-activities requirement distinct from the DPIA obligation was located in this run's sources.

Joint controller arrangementsGreen

MODPA requires a written, binding controller-processor contract with specified terms.

Claims (1):

  • MODPA requires controllers and processors to enter into a written, binding contract containing specified data-processing terms whenever a controller engages a processor.

Security measuresAmber

MODPA imposes a confidentiality obligation as part of core controller duties.

Claims (1):

  • MODPA imposes confidentiality obligations on covered businesses as part of its core set of controller duties.

Breach notificationGreen

PIPA (Md. Code Ann., Comm. Law §14-3504) requires notice to affected residents and the AG following a security breach.

Claims (1):

  • Maryland's Personal Information Protection Act requires businesses to notify affected Maryland residents and the Attorney General's Identity Theft Unit following a breach of personal information, operating independently of MODPA.

Retention and disposalRed

No explicit stand-alone retention-limit or disposal-duty provision beyond purpose-based minimization was located in this run's sources.

Category narrative 26 words

MODPA imposes DPIA, confidentiality, and processor-contract obligations on controllers, while the separate PIPA statute governs breach notification. No DPO-appointment requirement or explicit retention-limit provision was located.

No periodic updates recorded in this cycle

Sources and claims (7)
  1. Probable DataGuidance — MODPA requires controllers to conduct data protection impact assessments for processing activities presenting a heightened risk of harm to consumers, applicable to processing occurring on or after October 1, 2025. observed
  2. Probable DataGuidance (legacy) — DPIAs requested by the Maryland AG under MODPA are confidential and exempt from disclosure under the Maryland Public Information Act. observed
  3. Uncertain DataGuidance — No MODPA provision was located requiring controllers to appoint a formal Data Protection Officer; this omission is typical of the US state comprehensive-privacy-law model. observed
  4. Probable DataGuidance (legacy) — MODPA requires controllers and processors to enter into a written, binding contract containing specified data-processing terms whenever a controller engages a processor. observed
  5. Probable DataGuidance — MODPA imposes confidentiality obligations on covered businesses as part of its core set of controller duties. observed
  6. Probable Maryland Attorney General — Maryland's Personal Information Protection Act requires businesses to notify affected Maryland residents and the Attorney General's Identity Theft Unit following a breach of personal information, operating independently of MODPA. observed
  7. Probable PrivacyLawMap — MODPA — Requires controllers to conduct and document a data protection assessment for heightened-risk processing, uniquely requiring assessment of each algorithm used. observed

#

No comprehensive cross-border transfer regime exists at the Maryland state level; this is an explicit and legitimate absence, not an omission.

Traffic-light rationale — RedNo comprehensive cross-border transfer regime exists at the Maryland state level; this is an explicit and legitimate absence, not an omission.

Sub-modules (6)

Transfer mechanismsRed

No MODPA-specific transfer mechanism provision was located.

Claims (1):

  • MODPA does not establish a cross-border data-transfer mechanism, adequacy determination process, SCC/BCR framework, transfer-impact-assessment requirement, or data-localisation mandate; such matters remain governed, where applicable, by federal sectoral law.

Adequacy receivedRed

Not applicable; US states do not receive adequacy decisions.

Claims (1):

  • Maryland's state privacy regime has no adequacy-decision mechanism.

Adequacy grantedRed

Not applicable; Maryland does not grant adequacy decisions.

SCCs and BCRsRed

No state-level SCC/BCR framework exists under MODPA.

Transfer impact assessmentRed

No transfer-impact-assessment requirement was located under MODPA.

Data localisationRed

No data-localisation mandate was located under MODPA.

Claims (1):

  • MODPA (as amended by HB711) — Effective July 1, 2026, MODPA prohibits knowingly selling a consumer's personal data to a government unit that, in the previous six months, took part in or supported civil immigration enforcement, or to any buyer known or reasonably suspected of seeking it for immigration enforcement.
Category narrative 50 words

MODPA, like other US state comprehensive privacy laws, contains no EU-style cross-border transfer mechanism, adequacy regime, SCC/BCR framework, transfer-impact-assessment requirement, or data-localisation mandate. Such matters for Maryland-resident data remain governed, if at all, by federal sectoral law (e.g., HIPAA, GLBA) or general contract, which fall outside this state-level JID's scope.

No periodic updates recorded in this cycle

Sources and claims (3)
  1. Probable DataGuidance — MODPA does not establish a cross-border data-transfer mechanism, adequacy determination process, SCC/BCR framework, transfer-impact-assessment requirement, or data-localisation mandate; such matters remain governed, where applicable, by federal sectoral law. observed
  2. Uncertain OneTrust — Maryland's state privacy regime has no adequacy-decision mechanism. observed
  3. Probable Open Class Actions — MODPA (as amended by HB711) — Effective July 1, 2026, MODPA prohibits knowingly selling a consumer's personal data to a government unit that, in the previous six months, took part in or supported civil immigration enforcement, or to any buyer known or reasonably suspected of seeking it for immigration enforcement. observed

#

Sectoral carve-outs are well-documented; telecoms/eprivacy and insurance-specific overlays were not located in this run.

Primary frameworkMaryland Online Data Privacy Act (MODPA), 2024
Traffic-light rationale — AmberSectoral carve-outs are well-documented; telecoms/eprivacy and insurance-specific overlays were not located in this run.

Sub-modules (7)

Financial sector overlayGreen

GLBA-regulated financial institutions and GLBA-covered data are excluded from MODPA.

Claims (1):

  • MODPA excludes financial institutions and data subject to Title V of the Gramm-Leach-Bliley Act from its scope.

Health sector overlayGreen

HIPAA-covered data is excluded from MODPA scope, while MODPA separately regulates non-HIPAA consumer health data with geofencing bans.

Claims (1):

  • MODPA excludes HIPAA-covered data from its scope while separately regulating non-HIPAA 'consumer health data' with heightened protections including facility geofencing bans.

Telecoms and eprivacyRed

No Maryland-specific telecoms/eprivacy overlay distinct from MODPA was located.

Employment dataRed

No Maryland-specific employment-data privacy overlay was located.

Credit and scoringGreen

FCRA-covered consumer-reporting-agency activity is excluded from MODPA's sensitive-data sale restrictions.

Claims (1):

  • MODPA excludes consumer-reporting-agency activity covered by the Fair Credit Reporting Act from its sensitive-data sale restrictions.

educationGreen

FERPA-covered education records are excluded from MODPA.

Claims (1):

  • MODPA excludes data covered by the Family Educational Rights and Privacy Act from its scope.

insuranceRed

No Maryland-specific insurance-sector privacy overlay was located.

Category narrative 36 words

MODPA carves out several federally-regulated sectors: GLBA-covered financial institutions, HIPAA-covered health data, FCRA-covered consumer-reporting activity, and FERPA-covered education records are excluded from MODPA's scope, while MODPA itself separately regulates non-HIPAA 'consumer health data' with heightened protections.

No periodic updates recorded in this cycle

Sources and claims (4)
  1. Probable IAPP — MODPA excludes financial institutions and data subject to Title V of the Gramm-Leach-Bliley Act from its scope. observed
  2. Probable IAPP — MODPA excludes HIPAA-covered data from its scope while separately regulating non-HIPAA 'consumer health data' with heightened protections including facility geofencing bans. observed
  3. Probable IAPP — MODPA excludes consumer-reporting-agency activity covered by the Fair Credit Reporting Act from its sensitive-data sale restrictions. observed
  4. Probable IAPP — MODPA excludes data covered by the Family Educational Rights and Privacy Act from its scope. observed

#

Targeted-advertising restrictions for minors and UOOM treatment are confirmed; cookie, dark-pattern, and clean-room specifics are unconfirmed.

Primary frameworkMaryland Online Data Privacy Act (MODPA), 2024
Traffic-light rationale — AmberTargeted-advertising restrictions for minors and UOOM treatment are confirmed; cookie, dark-pattern, and clean-room specifics are unconfirmed.

Sub-modules (6)

Cookies and trackersRed

No MODPA-specific cookie/tracker consent provision distinct from general consent standards was located.

Dark patternsAmber

MODPA's consent definition requiring 'unambiguous affirmative action' implicitly disfavours dark-pattern-obtained consent, consistent with peer state laws.

Claims (1):

  • MODPA defines consent as requiring an 'unambiguous affirmative action,' a standard that implicitly excludes consent obtained via manipulative interface design (dark patterns).

Opt out signalsAmber

MODPA treats universal opt-out mechanism recognition as optional rather than mandatory, a notable departure from most peer states.

Claims (6):

  • MODPA recognizes universal opt-out mechanisms as an optional alternative to a conspicuous 'do not sell' link rather than mandating recognition of such signals.
  • MODPA requires controllers to recognize a universal opt-out preference signal, such as Global Privacy Control, for opt-out of data sale and targeted advertising.
  • Maryland Online Data Privacy Act (MODPA) — Since MODPA's 2025-10-01 effective date, a controller must honor a universal opt-out preference signal (functionally equivalent to Global Privacy Control) as a valid opt-out from targeted advertising and the sale of personal data.
  • MODPA — Controllers must recognize universal opt-out preference signals such as Global Privacy Control (GPC); required on or before 2025-10-01.
  • Maryland Online Data Privacy Act — Controller may satisfy opt-out duty via website link or opt-out preference signal (permissive, not mandatory per statute text)
  • Maryland Online Data Privacy Act — Controller may satisfy the opt-out duty either via a clear and conspicuous website link, or (as of October 1, 2025) by honoring an opt-out preference signal; the statutory text frames this as permissive (two alternative compliance routes), not a standalone mandatory GPC duty, contrary to several vendor compliance guides that describe it as mandatory

Clean rooms and dcrRed

No clean-room or data-collaboration-room-specific provision was located under MODPA.

Cross context advertisingGreen

MODPA bans targeted advertising to consumers a controller knew or should have known are under 18.

Claims (1):

  • MODPA bans processing personal data for targeted advertising where the controller knew or should have known the consumer is under 18, applying an expanded constructive-knowledge standard.

Direct marketingRed

No MODPA provision specific to direct-marketing consent/suppression distinct from the general sale/targeted-advertising opt-out was located.

Category narrative 35 words

MODPA's commercial-privacy provisions center on an under-18 targeted-advertising ban, an optional (not mandatory) universal opt-out mechanism, and an 'unambiguous affirmative action' consent standard that implicitly disfavours dark-pattern-obtained consent. No cookie-specific or clean-room-specific provisions were located.

No periodic updates recorded in this cycle

Sources and claims (8)
  1. Probable IAPP — MODPA defines consent as requiring an 'unambiguous affirmative action,' a standard that implicitly excludes consent obtained via manipulative interface design (dark patterns). observed
  2. Probable IAPP — MODPA recognizes universal opt-out mechanisms as an optional alternative to a conspicuous 'do not sell' link rather than mandating recognition of such signals. observed
  3. Probable IAPP — MODPA bans processing personal data for targeted advertising where the controller knew or should have known the consumer is under 18, applying an expanded constructive-knowledge standard. observed
  4. High PrivacyLawMap — MODPA requires controllers to recognize a universal opt-out preference signal, such as Global Privacy Control, for opt-out of data sale and targeted advertising. observed
  5. Probable Fisher Phillips — Maryland Online Data Privacy Act (MODPA) — Since MODPA's 2025-10-01 effective date, a controller must honor a universal opt-out preference signal (functionally equivalent to Global Privacy Control) as a valid opt-out from targeted advertising and the sale of personal data. observed
  6. Probable Osano — MODPA — Controllers must recognize universal opt-out preference signals such as Global Privacy Control (GPC); required on or before 2025-10-01. observed
  7. Disputed Maryland General Assembly (mgaleg.maryland.gov) — Maryland Online Data Privacy Act — Controller may satisfy opt-out duty via website link or opt-out preference signal (permissive, not mandatory per statute text) observed
  8. Disputed Maryland General Assembly (mgaleg.maryland.gov) — Maryland Online Data Privacy Act — Controller may satisfy the opt-out duty either via a clear and conspicuous website link, or (as of October 1, 2025) by honoring an opt-out preference signal; the statutory text frames this as permissive (two alternative compliance routes), not a standalone mandatory GPC duty, contrary to several vendor compliance guides that describe it as mandatory observed

#

Biometric/genetic protections are confirmed via the sensitive-data regime; ADM transparency, profiling restrictions, and AI risk-assessment mandates are unconfirmed or still proposed.

Primary frameworkMaryland Online Data Privacy Act (MODPA), 2024
Traffic-light rationale — AmberBiometric/genetic protections are confirmed via the sensitive-data regime; ADM transparency, profiling restrictions, and AI risk-assessment mandates are unconfirmed or still proposed.

Sub-modules (6)

Profiling restrictionsRed

No MODPA provision establishing a general profiling-restriction regime akin to GDPR Art. 22 was located.

Claims (2):

  • Protection From Predatory Pricing Act (HB 895, 2026) — Prohibits dynamic pricing based on personal data and use of protected-class data to withhold advantages, effective Oct 1, 2026.
  • The Protection From Predatory Pricing Act prohibits AI-driven personalized pricing using personal data in food retail/delivery, effective Oct 1, 2026.

Automated decision making transparencyRed

No ADM-transparency/explanation-right provision was located under MODPA.

AI risk assessmentsRed

Maryland is considering, but has not enacted, dedicated AI risk-assessment legislation separate from MODPA.

Claims (4):

  • Maryland lawmakers are considering AI-specific bills distinct from MODPA, including Senate Bill 827 on chatbot/generative-AI liability and House Bill 956 establishing an AI-implementation workgroup, indicating an emerging but not-yet-comprehensive state AI-governance overlay.
  • Maryland Senate Bill 827 proposes comprehensive consumer-protection and liability rules for chatbots and generative-AI systems.
  • Maryland Online Data Privacy Act (MODPA) — Comparative commentary identifies MODPA as requiring an algorithmic assessment (unlike most peer state laws), but the specific statutory test, trigger threshold and transparency duty were not independently retrieved this cycle.
  • Senate Bill 827 (2026) 'Curbing Harmful AI Technology Act' — Consumer-protection and product-liability framework for chatbots (generative AI with natural-language interface), covering affirmative consent, under-13 protections, AI-disclosure warnings, monthly safety testing, and product liability; failed to advance past committee in 2026 and did not become law

Biometric regimeGreen

Biometric data is included in MODPA's sensitive-data category, subject to strict-necessity and sale-ban rules.

Claims (1):

  • MODPA includes biometric and genetic data within its 'sensitive data' definition, subjecting their collection, processing, and sharing to the 'strictly necessary' standard and an outright sale ban.

Genetic dataGreen

Genetic data is likewise included in MODPA's sensitive-data category under the same strict-necessity and sale-ban rules.

Claims (1):

  • MODPA includes biometric and genetic data within its 'sensitive data' definition, subjecting their collection, processing, and sharing to the 'strictly necessary' standard and an outright sale ban.

State surveillance carveoutsRed

No MODPA-specific national-security or state-surveillance carve-out provision was located in this run's sources.

Category narrative 48 words

MODPA treats biometric and genetic data as sensitive data subject to strict-necessity and sale-ban rules, but contains no GDPR Art.22-style profiling-restriction or automated-decision-making-transparency regime. Maryland is separately considering (but has not yet enacted as of this run) AI-specific legislation such as chatbot/generative-AI liability and an AI oversight workgroup.

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

Sources and claims (7)
  1. Uncertain DataGuidance — Maryland lawmakers are considering AI-specific bills distinct from MODPA, including Senate Bill 827 on chatbot/generative-AI liability and House Bill 956 establishing an AI-implementation workgroup, indicating an emerging but not-yet-comprehensive state AI-governance overlay. observed
  2. Probable IAPP — MODPA includes biometric and genetic data within its 'sensitive data' definition, subjecting their collection, processing, and sharing to the 'strictly necessary' standard and an outright sale ban. observed
  3. Probable Open Class Actions — Protection From Predatory Pricing Act (HB 895, 2026) — Prohibits dynamic pricing based on personal data and use of protected-class data to withhold advantages, effective Oct 1, 2026. observed
  4. Assessed OneTrust DataGuidance — Maryland Senate Bill 827 proposes comprehensive consumer-protection and liability rules for chatbots and generative-AI systems. observed
  5. Probable Open Class Actions — The Protection From Predatory Pricing Act prohibits AI-driven personalized pricing using personal data in food retail/delivery, effective Oct 1, 2026. observed
  6. Uncertain https://www.recordinglaw.com/us-laws/data-privacy-laws/maryland-data-privacy-laws/ — Maryland Online Data Privacy Act (MODPA) — Comparative commentary identifies MODPA as requiring an algorithmic assessment (unlike most peer state laws), but the specific statutory test, trigger threshold and transparency duty were not independently retrieved this cycle.
  7. Probable Maryland General Assembly, Department of Legislative Services — Senate Bill 827 (2026) 'Curbing Harmful AI Technology Act' — Consumer-protection and product-liability framework for chatbots (generative AI with natural-language interface), covering affirmative consent, under-13 protections, AI-disclosure warnings, monthly safety testing, and product liability; failed to advance past committee in 2026 and did not become law observed

#

Minor-targeted-advertising and Kids Code protections are confirmed; parental-consent, education-setting, and dependent-adult sub-modules are unconfirmed absences.

Primary frameworkMaryland Online Data Privacy Act (MODPA); Maryland Kids Code (Age-Appropriate Design Code)
Traffic-light rationale — AmberMinor-targeted-advertising and Kids Code protections are confirmed; parental-consent, education-setting, and dependent-adult sub-modules are unconfirmed absences.

Sub-modules (5)

Age verificationAmber

MODPA uses a 'knew or should have known' constructive-knowledge standard rather than mandating affirmative age verification, though commentators note this could functionally require age-assurance practices.

Claims (1):

  • MODPA bans processing personal data for targeted advertising and prohibits the sale of personal data belonging to consumers the controller knew or should have known are under 18.

Minor profiling bansGreen

MODPA bans targeted advertising and sale of data belonging to consumers known or reasonably known to be minors under 18.

Claims (5):

  • MODPA bans processing personal data for targeted advertising and prohibits the sale of personal data belonging to consumers the controller knew or should have known are under 18.
  • MODPA extends its protections to all consumers under 18, prohibiting the sale of their personal data and barring targeted advertising directed at minors.
  • MODPA — Prohibits selling a consumer's personal data or using it for targeted advertising if the controller knew or should have known the consumer is under 18.
  • MODPA prohibits processing minors' data for advertising/profiling/sale purposes under age 18; HB711 (2026) removed an earlier floor that had set the protected age at 13, extending protection to everyone under 18 with no lower limit.
  • Maryland Online Data Privacy Act — Controller may not process personal data for targeted advertising or sale where it knew or should have known the consumer is under 18 (constructive-knowledge standard, no 13-year floor, not a strict/absolute standard)

Education settingsRed

No Maryland-specific education-settings privacy rule beyond the general FERPA carve-out was located.

Dependent adultsRed

No Maryland-specific dependent-adult data-protection provision was located in this run's sources.

Category narrative 63 words

Maryland protects minors' data through two instruments: MODPA's ban on targeted advertising/sale for consumers a controller knew or should have known are under 18, and the separate Maryland Kids Code requiring Privacy by Design/Default for products reasonably likely to be accessed by children, in force despite litigation risk. No Maryland-specific parental-consent mechanism distinct from federal COPPA, education-setting rule, or dependent-adult protection was located.

Periodic update · new data 2026-10-25

Maryland's protections for minors under the Online Data Privacy Act were extended with House Bill 711's 2026 amendments, which are understood to have removed an earlier floor that had set the protected age for MODPA's minor-related advertising, profiling, and sale restrictions at 13. Prior to this amendment, the statute's prohibition on processing a minor's personal data for targeted advertising, certain profiling, or sale is reported to have applied to individuals the controller knew or should have known were aged 13 to under 18, consistent with the statute's original October 1, 2025 commencement. With the age-13 floor removed, the restriction is reported to extend protection to any individual under 18, without the lower bound that previously excluded the youngest minors from this particular set of restrictions.

This development is sourced at Probable confidence from a secondary compliance-industry publication rather than confirmed directly against the primary chaptered bill text, and the precise mechanism of the floor's removal, whether through an explicit statutory amendment to the age range or through a definitional change elsewhere in the recodified Subtitle 47, has not been independently verified against primary legislative text. The substantive direction of the change, an expansion of the protected population to include minors under 13 who were previously outside this specific set of restrictions, is nonetheless a material tightening for any controller whose services may be used by younger children.

For controllers operating online services directed at or reasonably likely to be accessed by children, this extension removes a line that previously could have been used to argue that a restriction applied only to minors aged 13 and above. Whether this change interacts with, or duplicates, any existing federal children's-privacy framework applicable to the same population has not been assessed.

Outlook

The most useful confirming step for a future cycle would be direct verification of the age-floor removal against the primary chaptered text of House Bill 711 or its codified form in Subtitle 47, since the current sourcing rests on secondary compliance commentary rather than the statute itself. Beyond that confirmation, the item to monitor is whether the Maryland Attorney General's Consumer Protection Division issues any guidance specific to the expanded protected-minor population, or whether any enforcement matter tests the boundaries of the extended age range.

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

Maryland's protections for minors under the Online Data Privacy Act were extended with House Bill 711's 2026 amendments, which are understood to have removed an earlier floor that had set the protected age for MODPA's minor-related advertising, profiling, and sale restrictions at 13. Prior to this amendment, the statute's prohibition on processing a minor's personal data for targeted advertising, certain profiling, or sale is reported to have applied to individuals the controller knew or should have known were aged 13 to under 18, consistent with the statute's original October 1, 2025 commencement. With the age-13 floor removed, the restriction is reported to extend protection to any individual under 18, without the lower bound that previously excluded the youngest minors from this particular set of restrictions.

This development is sourced at Probable confidence from a secondary compliance-industry publication rather than confirmed directly against the primary chaptered bill text this cycle, and the precise mechanism of the floor's removal, whether through an explicit statutory amendment to the age range or through a definitional change elsewhere in the recodified Subtitle 47, has not been independently verified against primary legislative text in this cycle. The substantive direction of the change, an expansion of the protected population to include minors under 13 who were previously outside this specific set of restrictions, is nonetheless a material tightening for any controller whose services may be used by younger children.

For controllers operating online services directed at or reasonably likely to be accessed by children, this extension removes a line that previously could have been used to argue that a restriction applied only to minors aged 13 and above. Whether this change interacts with, or duplicates, any existing federal children's-privacy framework applicable to the same population has not been assessed this cycle.

Outlook

The most useful confirming step for a future cycle would be direct verification of the age-floor removal against the primary chaptered text of House Bill 711 or its codified form in Subtitle 47, since the current sourcing rests on secondary compliance commentary rather than the statute itself. Beyond that confirmation, the item to monitor is whether the Maryland Attorney General's Consumer Protection Division issues any guidance specific to the expanded protected-minor population, or whether any enforcement matter tests the boundaries of the extended age range.

Periodic update · new data 2026-10-05

MODPA prohibits selling the personal data of a consumer known, or that the controller should have known, to be under the age of 18, and separately prohibits processing such a consumer's data for targeted advertising. The should-have-known standard is notable because it does not require a controller to have actual knowledge of a consumer's age; a controller that reasonably should have inferred a consumer's minor status from the data or context available to it falls within the prohibition's reach even absent explicit age disclosure.

Outlook

The specific statutory pinpoint for the should-have-known standard and any associated safe-harbour or compliance mechanism have not been independently retrieved against primary MODPA text this period; the prohibition and its should-have-known trigger are reported consistently in secondary commentary.

Sources and claims (6)
  1. Probable IAPP — MODPA bans processing personal data for targeted advertising and prohibits the sale of personal data belonging to consumers the controller knew or should have known are under 18. observed
  2. Uncertain DataGuidance — MODPA itself does not impose a distinct parental-consent mechanism; federal COPPA continues to apply concurrently for children under 13, and this interaction remains outside MODPA's own text as reviewed. observed
  3. High RecordingLaw.com — MODPA extends its protections to all consumers under 18, prohibiting the sale of their personal data and barring targeted advertising directed at minors. observed
  4. Probable Davis+Gilbert LLP — MODPA — Prohibits selling a consumer's personal data or using it for targeted advertising if the controller knew or should have known the consumer is under 18. observed
  5. Probable https://www.enzuzo.com/blog/maryland-online-data-privacy-act — MODPA prohibits processing minors' data for advertising/profiling/sale purposes under age 18; HB711 (2026) removed an earlier floor that had set the protected age at 13, extending protection to everyone under 18 with no lower limit.
  6. Probable RecordingLaw.com — Maryland Online Data Privacy Act — Controller may not process personal data for targeted advertising or sale where it knew or should have known the consumer is under 18 (constructive-knowledge standard, no 13-year floor, not a strict/absolute standard) observed

#

Core enforcement powers and no-private-right-of-action posture are confirmed; regulator funding/capacity data and collective-redress interactions with the general Consumer Protection Act are unconfirmed.

Primary frameworkMaryland Online Data Privacy Act (MODPA); Maryland Consumer Protection Act (Title 13, Commercial Law)
Traffic-light rationale — AmberCore enforcement powers and no-private-right-of-action posture are confirmed; regulator funding/capacity data and collective-redress interactions with the general Consumer Protection Act are unconfirmed.

Sub-modules (6)

Regulator powers and penaltiesAmber

AG enforcement runs through Consumer Protection Act unfair/deceptive-trade-practice provisions, with a discretionary 60-day cure right sunsetting in 2027.

Claims (10):

  • MODPA violations are treated as unfair, abusive, or deceptive trade practices subject to the enforcement and penalty provisions of Title 13 of the Maryland Commercial Law Article (Consumer Protection Act).
  • The AG may issue a notice of violation triggering a 60-day cure period before bringing an enforcement action, retains discretion over whether to grant the cure opportunity considering factors including violation volume and entity size, and this cure right sunsets in 2027.
  • Maryland Attorney General — Consumer Protection Division — MODPA violations carry penalties of up to $10,000 per violation and up to $25,000 per repeat violation; no private right of action for consumers.
  • MODPA violations carry civil penalties of up to $10,000 for a first violation and $25,000 for each repeat violation, enforced exclusively by the Attorney General's Consumer Protection Division.
  • MODPA violations carry civil penalties up to $10,000 (first) / $25,000 (subsequent), with a cure period until April 1, 2027.
  • Maryland Attorney General — A MODPA violation is treated as an unfair/abusive/deceptive trade practice under the Maryland Consumer Protection Act; AG may seek civil penalties up to $10,000 per violation, $25,000 per repeat violation, plus injunctive relief, restitution and disgorgement; 60-day discretionary cure period sunsets April 1, 2027; no private right of action.
  • MODPA — For an alleged violation occurring on or before 2027-04-01, the Consumer Protection Division may issue a notice of violation with at least 60 days to cure before enforcement; after that date no statutory cure period applies.
  • MODPA penalties reach up to $10,000 for a first violation and up to $25,000 for each subsequent violation, with a 60-day cure period available through April 1, 2027.
  • MODPA civil penalties under the Maryland Consumer Protection Act are up to $10,000 per violation for a first violation and up to $25,000 per violation for subsequent violations; the Attorney General may also seek injunctive relief, restitution, economic damages and disgorgement.
  • Maryland Consumer Protection Act — Civil fine up to $10,000 for a first violation and up to $25,000 for each subsequent repeat violation, applied to MODPA violations via §14-4713 incorporation

Enforcement activity indexAmber

Pre-MODPA multistate breach enforcement (e.g., the Inmediata settlement) illustrates the AG's active data-security enforcement track record under PIPA/CPA/HIPAA.

Claims (3):

  • In 2023, the Maryland AG joined a 33-state settlement with health-data clearinghouse Inmediata over a data exposure affecting 1.5 million consumers (16,423 in Maryland), resolving alleged violations of the Maryland Consumer Protection Act, PIPA, and HIPAA.
  • No formal MODPA enforcement actions had been publicly announced as of a May 2026 secondary-source snapshot.
  • Maryland Attorney General — As of the most recent reporting located this cycle (dated on or around August 2026, pre-dating this window), no formal MODPA enforcement action had been publicly announced.

Regulator funding and capacityRed

No specific budget or headcount data for the AG's privacy-enforcement capacity was located in this run's sources.

Claims (1):

  • Maryland Attorney General, Consumer Protection Division — As of early 2026, had only one attorney dedicated to privacy enforcement, compared to multi-attorney teams in states like Connecticut, Delaware, and Oregon.

Collective redress and class actionsRed

No MODPA-specific collective-redress mechanism was located; its interaction with general Maryland Consumer Protection Act private-action provisions remains unresolved in the sources reviewed.

Claims (1):

  • No MODPA-specific collective-redress or class-action mechanism was located; whether general Maryland Consumer Protection Act private-action provisions apply to MODPA-predicated claims was not resolved in the sources reviewed.

Private right of actionGreen

MODPA does not create a private right of action; enforcement runs exclusively through the AG.

Claims (6):

  • MODPA does not create a private cause of action for violations; the Maryland Office of the Attorney General is responsible for enforcement.
  • MODPA does not provide consumers with a private right of action.
  • Violations are routed to Consumer Protection Act enforcement machinery while expressly excluding that Act's private-action section; consumers cannot sue directly for a MODPA violation.
  • MODPA grants no private right of action; enforcement rests exclusively with the Attorney General.
  • Consumers do not have a private right of action under MODPA; they cannot bring lawsuits directly, leaving enforcement entirely to the state.
  • Maryland Online Data Privacy Act — Private right of action; enforcement vested exclusively in the Attorney General's Consumer Protection Division under Title 13 (excluding §13-408)

Recent developments 180dAmber

A 2026 amendment strengthened MODPA's sensitive-data and immigration-related protections effective July 1, 2026; further AI-liability and surveillance-pricing bills remain in progress.

Claims (2):

  • In 2026, Maryland enacted amendments strengthening MODPA's sensitive-data and immigration-enforcement-related protections, effective July 1, 2026.
  • Additional 2026 Maryland legislative proposals extend the state's data/AI agenda beyond MODPA, including Senate Bill 827 (chatbot/generative-AI liability), House Bill 895 (ban on surveillance-based dynamic pricing in grocery stores), and House Bill 956 (AI-implementation workgroup); their enactment status was not confirmed in this run.
Category narrative 52 words

The Maryland AG has exclusive MODPA enforcement authority operating through the state Consumer Protection Act framework, including a discretionary 60-day cure period sunsetting in 2027, and no private right of action. A 2026 amendment strengthened sensitive-data and immigration-related protections effective July 1, 2026, and further AI/pricing-related bills are in the legislative pipeline.

Periodic update · new data 2026-11-04

MODPA grants no private right of action; enforcement rests exclusively with the Attorney General. A MODPA violation is understood to be treated as an unfair, abusive, or deceptive trade practice, with civil penalties reported at up to $10,000 for a first violation and up to $25,000 for subsequent violations; a cure period is understood to apply generally, becoming discretionary after April 1, 2027, rather than guaranteed as it is today. The newer Protection From Predatory Pricing Act carries a parallel but distinct enforcement structure, with its own 45-day cure period and no private right of action, also administered by the Attorney General's Consumer Protection Division. Reports suggest that, as of a May 2026 secondary-source snapshot, no formal MODPA enforcement actions had been publicly announced; this observation has not been refreshed since and should be read as dated rather than current.

Outlook

The shift of the MODPA cure period from a general requirement to a discretionary matter after April 1, 2027, will materially change the Attorney General's leverage in future matters, removing the current practical buffer for first-time violators. Whether the office begins bringing public enforcement actions before that date, and how it treats the new predatory-pricing statute's parallel cure mechanism, are the central open questions for this jurisdiction's enforcement posture.

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

MODPA enforcement is the exclusive province of the Maryland Attorney General, and enforcement against processing activity has been active since 1 April 2026. Violations carry penalties of up to $10,000 per violation and up to $25,000 per repeat violation; there is no private right of action for consumers. A 60-day cure period currently applies to violations occurring on or before 1 April 2027, giving a controller found in apparent violation an opportunity to remedy the issue before the Attorney General proceeds to enforcement. After 1 April 2027, that cure opportunity sunsets, and the Attorney General may proceed directly to enforcement with no cure period available.

No specific MODPA enforcement action brought since the 1 April 2026 enforcement start was independently located this period, and whether the Attorney General has issued implementing rulemaking or guidance since that date was not established this period.

Outlook

The date to watch is 1 April 2027, when the 60-day cure period sunsets and the Attorney General's enforcement posture hardens from a cure-first approach to one permitting direct enforcement action.

Periodic update · new data 2026-09-28

MODPA enforcement is structurally centralized: the statute is enforced exclusively by the Consumer Protection Division of the Maryland Attorney General's Office, with violations treated as unfair or deceptive trade practices under Maryland's general consumer-protection law rather than through a dedicated privacy-enforcement mechanism. Enforcement began April 1, 2026. Penalties reach up to ten thousand dollars for a first violation and up to twenty-five thousand dollars for each subsequent violation. A sixty-day cure period is available to covered entities, but only through April 1, 2027, after which the cure right sunsets and the Attorney General may proceed to enforcement without first affording an opportunity to cure.

A structurally significant feature of MODPA's redress architecture is the complete absence of a private right of action: consumers cannot bring lawsuits directly under the statute, leaving enforcement entirely in the hands of the state. This concentrates enforcement discretion, and litigation risk, exclusively with the Attorney General's Consumer Protection Division, in contrast to state privacy statutes elsewhere that afford consumers a direct cause of action for at least a subset of violations.

Outlook

The sixty-day cure period's April 1, 2027 sunset is the key date to track: enforcement exposure for covered entities increases materially once that cure right expires, since the Attorney General will then be able to proceed to penalty enforcement without a mandatory opportunity to remediate first. Whether the Attorney General has yet brought or settled any MODPA enforcement action since the April 1, 2026 enforcement start date was not established this cycle.

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

Sources and claims (23)
  1. Probable DataGuidance — MODPA violations are treated as unfair, abusive, or deceptive trade practices subject to the enforcement and penalty provisions of Title 13 of the Maryland Commercial Law Article (Consumer Protection Act). observed
  2. Probable IAPP — The AG may issue a notice of violation triggering a 60-day cure period before bringing an enforcement action, retains discretion over whether to grant the cure opportunity considering factors including violation volume and entity size, and this cure right sunsets in 2027. observed
  3. Probable Maryland Attorney General — In 2023, the Maryland AG joined a 33-state settlement with health-data clearinghouse Inmediata over a data exposure affecting 1.5 million consumers (16,423 in Maryland), resolving alleged violations of the Maryland Consumer Protection Act, PIPA, and HIPAA. observed
  4. Uncertain DataGuidance — No MODPA-specific collective-redress or class-action mechanism was located; whether general Maryland Consumer Protection Act private-action provisions apply to MODPA-predicated claims was not resolved in the sources reviewed. observed
  5. Probable DataGuidance (legacy) — MODPA does not create a private cause of action for violations; the Maryland Office of the Attorney General is responsible for enforcement. observed
  6. Probable DataGuidance — In 2026, Maryland enacted amendments strengthening MODPA's sensitive-data and immigration-enforcement-related protections, effective July 1, 2026. observed
  7. Uncertain DataGuidance — Additional 2026 Maryland legislative proposals extend the state's data/AI agenda beyond MODPA, including Senate Bill 827 (chatbot/generative-AI liability), House Bill 895 (ban on surveillance-based dynamic pricing in grocery stores), and House Bill 956 (AI-implementation workgroup); their enactment status was not confirmed in this run. observed
  8. Probable EdLaw — Maryland Attorney General — Consumer Protection Division — MODPA violations carry penalties of up to $10,000 per violation and up to $25,000 per repeat violation; no private right of action for consumers. observed
  9. High PrivacyLawMap — MODPA violations carry civil penalties of up to $10,000 for a first violation and $25,000 for each repeat violation, enforced exclusively by the Attorney General's Consumer Protection Division. observed
  10. High Koley Jessen — MODPA does not provide consumers with a private right of action. observed
  11. Probable Ketch — MODPA violations carry civil penalties up to $10,000 (first) / $25,000 (subsequent), with a cure period until April 1, 2027. observed
  12. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/maryland-data-privacy-laws/ — Maryland Attorney General — A MODPA violation is treated as an unfair/abusive/deceptive trade practice under the Maryland Consumer Protection Act; AG may seek civil penalties up to $10,000 per violation, $25,000 per repeat violation, plus injunctive relief, restitution and disgorgement; 60-day discretionary cure period sunsets April 1, 2027; no private right of action.
  13. Probable https://openagreements.org/practice-guides/privacy/us/maryland — MODPA — For an alleged violation occurring on or before 2027-04-01, the Consumer Protection Division may issue a notice of violation with at least 60 days to cure before enforcement; after that date no statutory cure period applies.
  14. Uncertain https://www.recordinglaw.com/us-laws/data-privacy-laws/maryland-data-privacy-laws/ — Maryland Attorney General, Consumer Protection Division — As of early 2026, had only one attorney dedicated to privacy enforcement, compared to multi-attorney teams in states like Connecticut, Delaware, and Oregon.
  15. Probable OpenAgreements — Violations are routed to Consumer Protection Act enforcement machinery while expressly excluding that Act's private-action section; consumers cannot sue directly for a MODPA violation. observed
  16. Uncertain Fisher Phillips — No formal MODPA enforcement actions had been publicly announced as of a May 2026 secondary-source snapshot. observed
  17. Probable OneTrust — MODPA grants no private right of action; enforcement rests exclusively with the Attorney General. observed
  18. Probable Ketch — MODPA penalties reach up to $10,000 for a first violation and up to $25,000 for each subsequent violation, with a 60-day cure period available through April 1, 2027. observed
  19. Probable Ketch — Consumers do not have a private right of action under MODPA; they cannot bring lawsuits directly, leaving enforcement entirely to the state. observed
  20. Probable Fisher Phillips — MODPA civil penalties under the Maryland Consumer Protection Act are up to $10,000 per violation for a first violation and up to $25,000 per violation for subsequent violations; the Attorney General may also seek injunctive relief, restitution, economic damages and disgorgement. observed
  21. Uncertain Primary statutory record — Maryland Attorney General — As of the most recent reporting located this cycle (dated on or around August 2026, pre-dating this window), no formal MODPA enforcement action had been publicly announced.
  22. Probable RecordingLaw.com — Maryland Online Data Privacy Act — Private right of action; enforcement vested exclusively in the Attorney General's Consumer Protection Division under Title 13 (excluding §13-408) observed
  23. Probable Maryland General Assembly (mgaleg.maryland.gov) — Maryland Consumer Protection Act — Civil fine up to $10,000 for a first violation and up to $25,000 for each subsequent repeat violation, applied to MODPA violations via §14-4713 incorporation observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 102 claim(s) (102 category placement(s)), 55 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 24 Oct 2026: upheld (3 confirmed against the cited source; 12 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

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

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