Ad Tech Compliance
Maryland Online Data Privacy Act (MODPA) and sensitive data: what advertisers can and cannot do
Published · Last updated
Next scheduled review:
The Maryland Online Data Privacy Act bars controllers from collecting, processing or sharing sensitive data, including consumer health data, unless it is strictly necessary for a product or service the consumer requested. It bans the sale of sensitive data outright, and its text offers no consent route around either rule (Com. Law 14-4707).
Most state privacy laws let a business process health data once the person opts in. Maryland does not. This page sets out the rule, the 2026 amendment that widened it, and what each part of an ad stack meets under the text. The state health privacy law tracker shows how far Maryland sits from the other states.
Contents
Key facts
- Effective 1 October 2025. Chapter 455 of 2024 (SB 541) was approved on 9 May 2024 with that effective date (Maryland General Assembly, SB 541).
- Processing before 1 April 2026 is outside it. The uncodified Section 2 of the chapter says the act may not apply to "any personal data processing activities before April 1, 2026" (Chapter 455).
- Strictly necessary or not at all. Sensitive data may be collected, processed or shared only where "strictly necessary to provide or maintain a specific product or service requested by the consumer" (14-4707(a)(1)).
- No sales of sensitive data. A controller may not "sell sensitive data" (14-4707(a)(2)).
- Inferences count from 1 July 2026. Chapter 874 of 2026 added inferred data and data processed to identify a sensitive attribute to the definition (Chapter 874).
- Fines up to $10,000 per violation. Repeat violations carry up to $25,000 each (Com. Law 13-410). A 60-day cure may be offered for violations up to 1 April 2027 (14-4714).
Definition
Sensitive data, under MODPA as enacted, is personal data that includes data revealing listed traits, among them consumer health data, sex life, sexual orientation and transgender or nonbinary status. It also covers genetic or biometric data, a known child's data, and precise geolocation data (14-4701(gg)). Consumer health data is "personal data that a controller uses to identify a consumer's physical or mental health status" (14-4701(i)). The glossary compares that term with other states'.
A note on section numbers. Chapter 455 placed the act at sections 14-4601 to 14-4614. The General Assembly's statute database now publishes it at 14-4701 to 14-4714, and 14-4601 is an unrelated provision (statute database, 14-4701). This page uses the current numbers.
The 2026 amendment: sensitive attributes and inferences
What changed. Chapter 874 of 2026 (HB 711) took effect on 1 July 2026 (Maryland General Assembly, HB 711). It renamed the listed traits "sensitive attributes" and added that the definition includes data a controller infers that, "alone or in combination with other data, is used to indicate" any of them. It then defined sensitive data as personal data that includes a sensitive attribute "or any other personal data processed for the purpose of identifying a sensitive attribute" (Chapter 874, 14-4701(gg)-(hh)).
It also extended "precise geolocation data" to the location of "a mobile device, or a vehicle" within 1,750 feet (Chapter 874, 14-4701(x)). Other sections added limits on selling data for immigration enforcement. The bill record says it was "Enacted under Article II, Section 17(c) of the Maryland Constitution".
Why it matters for ads. Before July 2026, a company could argue that an interest segment such as "researching arthritis care" was not data "revealing" a health status. The new text reaches data inferred from behaviour and any data processed to identify a health trait. That describes how most health interest segments are built.
On 9 November 2026 the statute database still displayed the pre-amendment definition. The chapter text is the source this page relies on for the amendment.
The strictly necessary rule against common ad uses
What the statute says. A controller may not collect, process or share sensitive data except where it is "strictly necessary to provide or maintain a specific product or service requested by the consumer to whom the personal data pertains" (14-4707(a)(1)). The statute does not define "strictly necessary". Consent appears elsewhere in 14-4707, for new purposes and revocation, but not as an alternative in paragraph (a)(1).
Each row below applies the text to a common use. The last column is a reading of the text, not a ruling.
6 of 6 rows
Showing an ad on a third-party site based on a health interest segment | Is targeting needed to provide a product the consumer requested? | Hard to fit; the consumer did not request the ad |
Building a lookalike audience from people who bought a health product | Same; plus "share" with the platform | Hard to fit |
Sending a "prescription ordered" conversion event to an ad platform | Measurement is not a product the consumer requested | Hard to fit |
Order confirmation email for a requested prescription refill | Needed to deliver the requested service | Fits the exception |
Ads chosen from the page's content, with no profile | Not "targeted advertising" under 14-4701(hh); no sensitive data processed | Outside the rule |
Selling a health segment to a data marketplace | Sale of sensitive data, 14-4707(a)(2) | Prohibited by the text |
Showing an ad on a third-party site based on a health interest segment
- What the text turns on
Is targeting needed to provide a product the consumer requested?
- Reading
Hard to fit; the consumer did not request the ad
Building a lookalike audience from people who bought a health product
- What the text turns on
Same; plus "share" with the platform
- Reading
Hard to fit
Sending a "prescription ordered" conversion event to an ad platform
- What the text turns on
Measurement is not a product the consumer requested
- Reading
Hard to fit
Order confirmation email for a requested prescription refill
- What the text turns on
Needed to deliver the requested service
- Reading
Fits the exception
Ads chosen from the page's content, with no profile
- What the text turns on
Not "targeted advertising" under 14-4701(hh); no sensitive data processed
- Reading
Outside the rule
Selling a health segment to a data marketplace
- What the text turns on
Sale of sensitive data, 14-4707(a)(2)
- Reading
Prohibited by the text
Table by AdSovereign, CC BY 4.0.
Targeted advertising, defined. The term covers ads "displayed to a consumer or on a device identified by a unique identifier", selected from activity across unaffiliated sites or apps. It excludes ads based on the current page or search, ads based on activity within the controller's own sites, and processing solely to measure frequency, performance or reach (14-4701(hh)). That exclusion for measurement does not lift the separate limit on sensitive data.
Minors. A controller may not process personal data for targeted advertising, or sell it, if it "knew or should have known" the consumer is under 18 (14-4707(a)(4)-(5)).
What practitioners do (practice, not law). Many advertisers treat Maryland residents as excluded from health-interest and health-lookalike audiences and serve them contextual targeting instead. Some move health measurement into a clean room that returns only aggregates.
Data minimisation applies to all personal data
Even outside sensitive data, a controller must "limit the collection of personal data to what is reasonably necessary and proportionate to provide or maintain a specific product or service requested by the consumer" (14-4707(b)(1)(i)). Using data for a purpose that is neither reasonably necessary to, nor compatible with, the disclosed purposes needs consent (14-4707(a)(8)).
Controllers that sell data or run targeted ads must disclose it clearly and explain the opt-out (14-4707(e)). The text provides for opt-out preference signals from 1 October 2025 (14-4707(f)(3)). Targeted advertising, sales and sensitive data processing each need a documented data protection assessment (14-4710).
The geofence ban and other health data duties
What the statute says. Section 14-4704 binds any "person", not only controllers that meet the thresholds. A person may not use a geofence "within 1,750 feet of any mental health facility or reproductive or sexual health facility" for listed purposes (14-4704(3)). The purposes are to identify, track, collect data from or notify a consumer about the consumer's health data. A covered facility is one where at least 70% of services are mental health, or reproductive or sexual health, care (14-4701(v) and (ee)).
The same section requires confidentiality duties for staff and contractors with access to consumer health data. It also bars giving a processor access unless both sides comply with the processor contract rules in 14-4708.
Who the act covers, and the HIPAA question
Thresholds. The act applies to a person that does business in Maryland, or targets its residents, and in the prior year handled personal data of at least 35,000 consumers. It also applies at 10,000 consumers where more than 20% of gross revenue came from selling personal data (14-4702). Data handled only to complete payments does not count toward the first threshold. A consumer is a Maryland resident (14-4701(h)).
Exemptions. Financial institutions and their affiliates under GLBA are exempt as entities. Protected health information under HIPAA is exempt as data, not the covered entity itself (14-4703). A hospital's marketing data that is not PHI, such as website analytics, can therefore fall under MODPA. PHI itself follows the HIPAA marketing rule.
Retail media. A pharmacy chain's front-store loyalty data is personal data; its prescription data may be PHI. Any segment that reveals or infers a health trait is sensitive data under MODPA. The pharmacy retail media guide covers how networks separate those sources.
Enforcement, penalties and the cure period
The statute. A violation is an unfair, abusive or deceptive trade practice under Title 13. It is subject to Title 13's enforcement and penalty provisions "except for § 13-408", the private damages action (14-4713). The section adds that it "does not prevent a consumer from pursuing any other remedy provided by law". Title 13 sets civil penalties of up to $10,000 per violation and $25,000 for each repeat (13-410).
The cure period. For violations occurring on or before 1 April 2027, the Consumer Protection Division "may" issue a notice of violation where it finds a cure possible, with at least 60 days to cure (14-4714). The cure is discretionary.
What enforcers have done. We found no public MODPA enforcement action as of 9 November 2026.
Dates that matter
5 of 5 rows
9 May 2024 | Governor approves SB 541 as Chapter 455 | |
1 Oct 2025 | Act takes effect; opt-out signal date in 14-4707(f)(3) | |
1 Apr 2026 | Processing from this date is within the act (uncodified Section 2) | |
1 Jul 2026 | Chapter 874: sensitive attributes, inferences, device and vehicle location | |
1 Apr 2027 | Last date of violations eligible for the discretionary cure |
9 May 2024
- Event
Governor approves SB 541 as Chapter 455
- Source
1 Oct 2025
- Event
Act takes effect; opt-out signal date in 14-4707(f)(3)
- Source
1 Apr 2026
- Event
Processing from this date is within the act (uncodified Section 2)
- Source
1 Jul 2026
- Event
Chapter 874: sensitive attributes, inferences, device and vehicle location
- Source
1 Apr 2027
- Event
Last date of violations eligible for the discretionary cure
- Source
Table by AdSovereign, CC BY 4.0.
What the text means for each part of an ad stack
7 of 7 rows
Health interest and lookalike segments | 14-4707(a)(1); Chapter 874 | Inferred health traits are sensitive data; use only where strictly necessary for a requested product |
Data sales and marketplaces | 14-4707(a)(2) | No sale of sensitive data |
Conversion APIs and measurement | 14-4707(a)(1) | Health events count as processing and sharing of sensitive data |
Location products | 14-4701(x); 14-4704(3) | Device and vehicle location is sensitive; no geofence within 1,750 feet of covered facilities |
Under-18 audiences | 14-4707(a)(4)-(5) | No targeted ads or sales where the controller knew or should have known |
Collection on sites and apps | 14-4707(b)(1)(i) | Only what is reasonably necessary and proportionate for the requested product |
Assessments | 14-4710 | Documented assessment for targeted ads, sales and sensitive data |
Health interest and lookalike segments
- Section
14-4707(a)(1); Chapter 874
- What changes under the text
Inferred health traits are sensitive data; use only where strictly necessary for a requested product
Data sales and marketplaces
- Section
14-4707(a)(2)
- What changes under the text
No sale of sensitive data
Conversion APIs and measurement
- Section
14-4707(a)(1)
- What changes under the text
Health events count as processing and sharing of sensitive data
Location products
- Section
14-4701(x); 14-4704(3)
- What changes under the text
Device and vehicle location is sensitive; no geofence within 1,750 feet of covered facilities
Under-18 audiences
- Section
14-4707(a)(4)-(5)
- What changes under the text
No targeted ads or sales where the controller knew or should have known
Collection on sites and apps
- Section
14-4707(b)(1)(i)
- What changes under the text
Only what is reasonably necessary and proportionate for the requested product
Assessments
- Section
14-4710
- What changes under the text
Documented assessment for targeted ads, sales and sensitive data
Table by AdSovereign, CC BY 4.0.
Connecticut keeps a consent route for the same data; compare Connecticut's consumer health data rules. California offers a right to limit instead; see California CMIA and CCPA health data rules. The ad tech compliance hub lists the federal and state pages together.
FAQ
When did the Maryland Online Data Privacy Act take effect?
Can consent make health-based targeting lawful under MODPA?
Can a company sell health data about Maryland residents?
Is geofencing banned in Maryland?
Can consumers sue under MODPA?
How this works on owned infrastructure
Maryland's text turns the usual question around. Instead of asking whether a person consented, a team has to show that a health-related use was strictly necessary for something the person requested, and that no health segment was sold. That evidence is easier to produce when the residency flag, the segment logic and the outbound feeds sit in one system. AdSovereign is designed to run audience building and bidding on the operator's own servers, so a rule can hold Maryland residents out of any segment tagged as health-derived before a bid request is formed. The rule and its exceptions stay in the operator's code. The architecture page describes the deployment, and use cases covers health and pharmacy setups.
Sources
- Maryland General Assembly, SB 541 (2024 Regular Session), Maryland Online Data Privacy Act of 2024, bill record (Chapter 455, effective 1 October 2025). https://mgaleg.maryland.gov/mgawebsite/Legislation/Details/sb0541?ys=2024RS
- Maryland General Assembly, Chapter 455 of 2024 (text, including uncodified Sections 2 to 4). https://mgaleg.maryland.gov/2024RS/Chapters_noln/CH_455_sb0541e.pdf
- Maryland Code, Commercial Law 14-4701, Definitions (statute database), checked 9 November 2026. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4701&enactments=false
- Maryland Code, Commercial Law 14-4702, Applicability. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4702&enactments=false
- Maryland Code, Commercial Law 14-4703, Exemptions. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4703&enactments=false
- Maryland Code, Commercial Law 14-4704, Consumer health data and geofencing. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4704&enactments=false
- Maryland Code, Commercial Law 14-4707, Controller duties. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4707&enactments=false
- Maryland Code, Commercial Law 14-4708, Processor contracts. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4708&enactments=false
- Maryland Code, Commercial Law 14-4710, Data protection assessments. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4710&enactments=false
- Maryland Code, Commercial Law 14-4713, Enforcement. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4713&enactments=false
More sources (4)
- Maryland Code, Commercial Law 14-4714, Notice of violation and cure. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=14-4714&enactments=false
- Maryland Code, Commercial Law 13-410, Civil penalties. https://mgaleg.maryland.gov/mgawebsite/Laws/StatuteText?article=gcl§ion=13-410&enactments=false
- Maryland General Assembly, HB 711 (2026 Regular Session), bill record (Chapter 874, effective 1 July 2026). https://mgaleg.maryland.gov/mgawebsite/Legislation/Details/hb0711?ys=2026RS
- Maryland General Assembly, Chapter 874 of 2026 (text). https://mgaleg.maryland.gov/2026RS/Chapters_noln/CH_874_hb0711t.pdf
Changelog
- 9 November 2026: page created from the state tracker's Maryland entry; statute read at its current section numbers; Chapter 874 of 2026 added.