DataPacts

Maryland: MODPA Ban on Selling Sensitive Data and AI Training Data

Checked

Independent reference. Every buyer is covered on the same terms, every figure carries its source and check date, and no buyer pays to be listed or placed higher.

Request an independent introduction

Tell us what data your company holds. We reply with the buyers that fit and what their terms leave out. Your details reach a buyer only after you agree to a named introduction.

IndependentYour details stay with us until you agreeNot selling is a valid outcome

Maryland regulates AI training data through the Maryland Online Data Privacy Act (MODPA, Md. Code Com.

Law 14-4701 to 14-4714, in effect since October 1, 2025): licensing personal data of Maryland residents for money or other value is a sale, sensitive data may not be sold at all, and sensitive data may only be collected or processed where strictly necessary for a product the consumer asked for.

Status is given as of November 17, 2026; per the Department of Legislative Services fiscal and policy note, the Act is not applied to processing before April 1, 2026. The ban and the minimization rule reach a seller before any buyer is chosen, so they form the strictest Maryland layer of AI training data licensing.

Maryland Rules on a Training Data Deal at a Glance

Eight MODPA rules decide what a seller may license and what a buyer inherits, and the table gives each one's section and its effect on a training data license as of 2026-11-17.

Rule Section Effect on a training data license Source
Thresholds 14-4702 35,000 consumers, or 10,000 plus more than 20 % of revenue from sales mgaleg.maryland.gov
Sale 14-4701(ff) exchange for monetary or other valuable consideration; asset-transfer exception mgaleg.maryland.gov
Sensitive data sale ban 14-4707(a)(2) no sale, no consent route mgaleg.maryland.gov
Strictly necessary 14-4707(a)(1) no collection, processing or sharing of sensitive data beyond a requested product or service mgaleg.maryland.gov
Under-18 data 14-4707(a)(4), (5) no sale, no targeted advertising if known or should have known mgaleg.maryland.gov
New purpose 14-4707(a)(9) consent for incompatible purposes mgaleg.maryland.gov
Deidentified data 14-4401(c); 14-4711(c) outside personal data if three conditions are met; contract oversight mgaleg.maryland.gov
Assessment 14-4710 for selling and for sensitive data, per algorithm mgaleg.maryland.gov

None of sections 14-4701 to 14-4714 mentions AI or model training (read on mgaleg.maryland.gov on 2026-11-17), so every rule applies through its general wording.

Which Companies and Records the Maryland Act Reaches

MODPA reaches companies by volume of Maryland consumers and records by who the person is, so coverage turns on two tests.

The 35,000 and 10,000 Consumer Thresholds

MODPA binds a person that conducts business in Maryland or targets Maryland residents and that, in the preceding calendar year, passed one of two thresholds (14-4702):

  • personal data of at least 35,000 consumers, excluding data processed solely to complete a payment transaction;
  • personal data of at least 10,000 consumers and more than 20 % of gross revenue from the sale of personal data.

A seller below 35,000 consumers can still be covered through the revenue limb.

Staff, Business Contacts and Exempt Records

Employee records and business-contact data fall outside MODPA, because a consumer is a Maryland resident and data processed within an employment or contractor role is exempt (14-4701(h), 14-4703(b)(11)).

The Act also exempts Gramm-Leach-Bliley institutions and data (14-4703(a)(3)), HIPAA protected health information and HIPAA-deidentified health data (14-4703(b)(1), (b)(6)(iii)), FERPA data (14-4703(b)(9)), Fair Credit Reporting Act data (14-4703(b)(7)) and human-subjects research data (14-4703(b)(3), (4)). Other law may still reach a Slack or email archive, as described under employee notice and consent when licensing internal communications.

When Licensing Personal Data for AI Training Is a Sale Under MODPA

A paid license of personal data to an AI developer is a sale, because MODPA defines a sale as the exchange of personal data by a controller, a processor or an affiliate to a third party for monetary or other valuable consideration (14-4701(ff)(1)).

Consumers may opt out of a sale (14-4705(b)(7)). A seller must disclose it clearly and conspicuously with the opt-out method (14-4707(e)) and list the categories of data and of third parties shared with (14-4707(d)(4), (5)).

Six exceptions apply (14-4701(ff)(2)), among them a disclosure to a processor or an affiliate and a transfer as an asset in an actual or proposed merger, acquisition, bankruptcy or other transaction in which the third party assumes control of all or part of the controller's assets.

The text does not say whether that last exception covers a sale of a data set alone. A court-supervised transfer is described under US bankruptcy data sales under Section 363(b)(1).

The Outright Ban on Selling Sensitive Data Under 14-4707(a)(2)

A controller may not sell sensitive data under any condition the statute names: 14-4707(a)(2) states "A controller may not ... Sell sensitive data" without a consent, authorization or notice alternative, in effect since October 1, 2025. Read with the sale definition, a paid training license of Maryland consumers' sensitive data is barred.

Sensitive Categories, Including Inferred Data

Sensitive data under 14-4701(gg) falls in four groups, and data a controller infers to indicate any of them counts too ((gg)(2)):

  • data revealing racial or ethnic origin, religious beliefs, consumer health data, sex life, sexual orientation, status as transgender or nonbinary, national origin, or citizenship or immigration status;
  • genetic data or biometric data;
  • personal data of a consumer the controller knows or has reason to know is a child, where a child is under 13 as in COPPA (14-4701(f));
  • precise geolocation data, within a radius of 1,750 feet (14-4701(x)).

Biometric data excludes photographs and recordings, and data generated from them, unless generated to identify a specific consumer (14-4701(d)(3)), so a voice or image archive turns sensitive once templates are derived.

Consent does not unlock a sale in Maryland, which sets it apart from other states that regulate sensitive data through consent. Virginia requires consent for sensitive data (Va.

Code 59.1-578), Oregon's Department of Justice guidance expects explicit consent before sensitive data trains AI (ORS 646A.578), and Washington allows consumer health data to be sold with a signed authorization naming the buyer (RCW 19.373). MODPA's consent definition (14-4701(g)) matters for other uses, never for this sale.

Strictly Necessary: Data Minimization Before Any Training Use

Maryland limits sensitive data before any sale is in view: a controller may not collect, process or share sensitive data unless it is strictly necessary to provide or maintain a specific product or service the consumer requested (14-4707(a)(1)). Two limits work together:

  • collection of personal data is limited to what is reasonably necessary and proportionate to provide or maintain a specific requested product or service (14-4707(b)(1)(i));
  • sensitive data is collected, processed or shared only where strictly necessary (14-4707(a)(1)).

The statute does not name training a model for a third party as a requested product, or say whether in-house training can meet "strictly necessary".

Using held personal data for a purpose neither reasonably necessary to nor compatible with the disclosed purposes requires the consumer's consent (14-4707(a)(9)). Consent is a clear affirmative act and excludes acceptance of broad terms of use and dark patterns (14-4701(g)).

Revocation stops processing within 30 days (14-4707(b)(2)), and a third party that changes practices against promises made at collection must notify consumers first (14-4709). Collecting it is covered under customer consent and confidentiality clauses before licensing data.

Consumers Under 18: No Sale, No Targeted Advertising

A controller may not sell the personal data of a consumer it knew or should have known is under 18, and may not process it for targeted advertising (14-4707(a)(5), (a)(4)).

The age is 18, above COPPA's under-13 child, and COPPA parental consent satisfies MODPA's parental-consent duties (14-4703(c)), but no consent route exists for the sale. The federal rule is described under COPPA and children's data in AI training.

Deidentified Data Under the Maryland Three-Part Test

Deidentified data is not personal data under MODPA (14-4701(w)(2)), but it qualifies only if it cannot reasonably be used to infer information about or be linked to a consumer and meets three conditions in 14-4401(c):

  • administrative and technical measures that prevent association with a particular consumer;
  • a public commitment to keep it deidentified and not to reidentify it;
  • legally enforceable contract terms that prohibit every recipient from reidentifying it.

A controller that discloses deidentified data must oversee those contracts and act on breaches, and reasonableness is judged by whether the data would be sensitive if reidentified (14-4711(c)).

Publicly available information is also outside personal data, except biometric data collected without the consumer's knowledge (14-4701(cc)(2)). The techniques behind the test are set out under PII removal and de-identification before licensing data.

Buyers, Processors and Who Answers for a Violation

An AI developer that receives personal data and decides how to use it is a controller in its own right, and a processor or third party that begins determining the purposes and means of processing becomes one too (14-4708(d)(4)).

A processor works under a binding contract (14-4708(a)), and a deletion request reaches data obtained about the consumer, answered within 45 days (14-4705(b)(4), (e)(2)).

A discloser is not in violation for a recipient's violation if it had no actual knowledge at disclosure and stayed compliant, and a recipient is not in violation for the discloser's independent misconduct (14-4712(d)). The license should therefore allocate warranties, as explained for AI data licensing agreements.

Data Protection Assessments for Each Algorithm

Selling personal data and processing sensitive data are heightened-risk activities, so a controller must regularly conduct and document a data protection assessment for each, including each algorithm used (14-4710(a), (b)). It weighs benefits against risks and the necessity and proportionality of the processing, and factors in deidentified data (14-4710(c)).

It applies to processing on or after 2025-10-01 (14-4710(h)). The Consumer Protection Division may require it, it stays confidential (14-4710(d)), and an assessment made for another law counts if similar in scope (14-4710(f)).

The table dates the changes a seller tracks, as of 2026-11-17.

Date Change Source
2024-05-09 SB 541 approved by the Governor as Chapter 455 mgaleg.maryland.gov (Chapter 455 text)
2025-10-01 MODPA takes effect; assessments required for processing from this date SB 541 bill page; 14-4710(h)
2026-04-01 Act not applied to personal data processing activities before this date Chapter 455 Section 2; fiscal and policy note
2027-04-01 last date of a violation that can receive a discretionary 60-day cure notice 14-4714(a)

Enforcement: USD 10,000 per Violation and a Cure Window Until April 2027

A MODPA violation is an unfair, abusive or deceptive trade practice under Title 13 of the Commercial Law Article, enforced by the Attorney General's Consumer Protection Division (14-4713(a); 13-101(e)).

As of 2026-11-17 the fines are up to USD 10,000 per violation and up to USD 25,000 per repeated violation (13-410(a), (b)). Section 13-408, private damages under the Consumer Protection Act, is excluded, and other remedies are preserved (14-4713).

For alleged violations on or before 2027-04-01, the Division may first issue a notice of violation where it determines a cure is possible, and the controller or processor then has at least 60 days to cure (14-4714).

The Division weighs seven factors, among them the number of violations and the likelihood of injury to the public.

Benefits, Risks, Downsides and Alternatives for a Seller Under Maryland Law, Including Not Selling

Maryland law lets a company license non-sensitive personal data for AI training as a disclosed sale with an opt-out, but sensitive and under-18 data cannot be sold, so deidentified, exempt or non-Maryland data, or not licensing, remain the choices for those records.

Benefits

  • Deidentified and publicly available data sit outside personal data.
  • Staff and business-contact data are outside the Act.
  • An asset transfer with the business is not a sale.
  • Companies below both thresholds are outside the Act.

Risks

  • Fines of up to USD 10,000 per violation and USD 25,000 per repeated violation (13-410, as of 2026-11-17).
  • A cure period is at the Division's discretion and only for violations up to 2027-04-01.
  • Inferred sensitive data is caught.

Downsides

  • Sensitive and under-18 records must be filtered from a mixed set.
  • A new purpose needs consent.
  • Assessments are required per algorithm.
  • Deidentified data needs contract oversight.

Alternatives

  • License deidentified data under the three-part test.
  • Exclude Maryland residents' sensitive and under-18 records.
  • License only non-sensitive data with disclosure and opt-out.
  • Not selling or licensing at all.

The wider alternatives to selling data to AI labs have their own page.

Beyond Maryland: Other States, Federal Rules and the Seller Process

Maryland is one state layer on top of federal law. The United States AI training data law page compares it with eleven other states.

How This Page Is Sourced and Dated

Every rule here cites the Maryland Code section, Chapter 455 of 2024 or the legislature's fiscal and policy note, with the date it was read. The methodology page explains how we source, date and check every figure. This page is general information about Maryland law, not legal advice for any specific deal.

Frequently Asked Questions

Can a company sell sensitive data for AI training in Maryland?

No. Section 14-4707(a)(2) bars a controller from selling sensitive data, and a paid training license is a sale under 14-4701(ff).

No. The ban has no consent alternative; consent matters for processing personal data for a new, incompatible purpose (14-4707(a)(9)), not for this sale.

Does MODPA apply to deidentified data?

No, if the data meets the three conditions of 14-4401(c), including contracts that bar recipients from reidentifying it.

When did the Maryland Online Data Privacy Act take effect?

October 1, 2025. Per the fiscal and policy note it is not applied to processing before April 1, 2026, and the cure window runs to April 1, 2027.