Most privacy programs can explain why they collect health or location data.
Maryland asks a narrower question. Was it strictly necessary for something this consumer asked you for?
If you cannot name the product or service the consumer requested, you do not have a weak justification. You have a gap.
What does MODPA's 'strictly necessary' test require before you collect, process or share sensitive data?
Under §14-4607(A) of the Maryland Online Data Privacy Act, a controller may not "collect, process, or share sensitive data concerning a consumer," except where "the collection or processing is strictly necessary to provide or maintain a specific product or service requested by the consumer to whom the personal data pertains."
Read the parts separately, because each one is a test you will have to pass:
→ Strictly necessary. Not useful, not expected, not efficient.
→ A specific product or service. Not "our services" in general.
→ Requested by the consumer. The person whose data it is asked for the thing.
The same subsection adds a second line with no exception attached: a controller may not "sell sensitive data." There is no necessity argument for a sale. That is a flat prohibition.
For the gap assessment, that gives you two questions per flow. Does it pass the necessity gate? And is any part of it a sale?
Which data counts as sensitive data in Maryland, and where does it sit in your systems?
§14-4601 defines "sensitive data" as personal data that includes 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. It also covers genetic data or biometric data, personal data of a consumer "that the controller knows or has reason to know is a child," and precise geolocation data.
Three definitions decide most mapping arguments.
Consumer health data means personal data "that a controller uses to identify a consumer's physical or mental health status." It includes data related to gender-affirming care treatment and reproductive or sexual health care. The trigger is use, so the field name in your schema settles nothing. A purchase history used to infer a condition can qualify.
Biometric data means data generated by automatic measurements of biological characteristics that can be used to uniquely authenticate identity. It excludes a photograph or recording, and data generated from one, "unless the data is generated to identify a specific consumer."
Precise geolocation data means information that can identify a consumer's location "within a radius of 1,750 feet," including GPS-level latitude and longitude.
The practical consequence: sensitive data in Maryland is often derived, not collected. Your inventory has to include inference outputs, analytics segments and location precision settings, not just form fields.
How is 'strictly necessary' different from the 'reasonably necessary and proportionate' rule for all personal data?
MODPA runs two minimization standards side by side.
For all personal data, §14-4607(B)(1)(I) requires a controller to "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 to whom the data pertains."
For sensitive data, the gate is "strictly necessary."
Both standards anchor to the same reference point: a specific product or service the consumer requested. What changes is the margin. "Reasonably necessary and proportionate" leaves room for a weighed judgment. "Strictly necessary" leaves very little.
The statute does not define "strictly necessary." Our working reading: if the requested product or service can be provided or maintained without the element, the element fails. If you are a DPO used to GDPR, resist importing a lawful-basis frame here. The Maryland test does not start from your purpose. It starts from the consumer's request.
How do you run a minimization gap assessment, one data flow at a time?
Work at the level of a single flow: one sensitive data element, moving through one system, for one stated reason. A policy that describes your approach is not the unit of evidence. The flow record is.
For each flow, record:
→ The sensitive data element, and which §14-4601 category it falls into, including derived data.
→ The specific product or service the consumer requested, named as the consumer would recognize it.
→ Why the element is strictly necessary for that product or service, in one or two sentences a reviewer can test.
→ Whether it is shared, and with whom, by named recipient, not by category.
→ Confirmation it is not sold, tested against the §14-4601 definition: an exchange "to a third party for monetary or other valuable consideration."
→ Retention, and when the element stops being necessary for the requested product or service.
→ The linked data protection assessment, by identifier and date.
Then sort. Our view is that three outcomes cover almost every flow:
- Passes. A named requested product or service, and a necessity statement that holds.
- Gap. No named requested product or service. This is the most common finding, and the one the statute makes hardest to defend.
- Overreach. A named product or service, but the element, precision or retention goes beyond what it strictly needs. Coarsen, truncate or delete.
Analytics, model training and internal research flows deserve first attention. They are rarely something a consumer requested.
What evidence shows a flow passes, and how does it feed your data protection assessment?
The flow record and the data protection assessment are the same work viewed from two sides.
§14-4610(A)(3) lists "the processing of sensitive data" as a processing activity that presents a heightened risk of harm to a consumer. Under §14-4610(B), a controller "shall conduct and document, on a regular basis, a data protection assessment" for each such activity, "including an assessment for each algorithm that is used."
§14-4610(C)(1)(II) requires the assessment to weigh "the necessity and proportionality of processing in relation to the stated purpose of the processing." Your necessity statement from the flow record is the input to that weighing. If the flow record says "gap," the assessment cannot honestly say "necessary."
Two provisions reduce duplication. §14-4610(E) lets a single assessment "address a comparable set of processing operations that include similar activities." §14-4610(F) treats an assessment done for another law as satisfying MODPA if it is "reasonably similar in scope and effect." A GDPR DPIA may help, but only if it actually tests necessity against the consumer's request.
Under §14-4610(H), the assessment duty applies to processing activities that occur on or after October 1, 2025.
Why the evidence matters: §14-4610(D) says the Division "may require" a controller to make available an assessment relevant to an investigation, "may evaluate" it for compliance, and the assessment "may be used in an action to enforce this subtitle."
What does the 1 April 2027 line change, and why is a cure notice not a plan?
1 April 2027 is not a compliance deadline. It marks the edge of which alleged violations the cure provision can reach.
§14-4614(A) applies the section to enforcement actions "for an alleged violation that occurs on or before April 1, 2027." Under §14-4614(B), before initiating an action the Division "may issue a notice of violation" to the controller or processor "if the Division determines that a cure is possible."
If a notice is issued, §14-4614(C)(1) gives the controller "at least 60 days to cure the violation after receipt of the notice." If the violation is not cured within the time period the Division specifies, §14-4614(C)(2) says the Division may bring an enforcement action.
Every step depends on Division discretion. The Division may issue a notice. It decides whether a cure is possible. Nothing in the text guarantees either.
A sensitive data flow with no requested product or service behind it is also an awkward thing to cure under time pressure. Fixing it can mean redesigning a feature, unwinding a sharing arrangement or deleting a data set. That work belongs in a plan you run now, not in a 60-day window you may never be offered.
How do you keep the necessity record current after a product changes?
Necessity is tied to a specific product or service. When the product changes, the record can go stale overnight.
Practical triggers to re-test a flow:
→ A feature is retired, but the data collection behind it is not.
→ A new recipient is added to an existing flow.
→ Location precision, retention or inference logic changes.
→ A new algorithm starts using sensitive data, which §14-4610(B) treats as needing its own assessment.
Build those triggers into change management, not an annual review. A dated record that shows when necessity was last tested, and by whom, is what makes the assessment "regular" in practice.
This is where Aigis fits. Each sensitive data flow is held against the §14-4607 text as a dated record, linked to its data protection assessment and its recipients, so a Division request becomes a query, not a project. The obligation mapping is source-grounded: every line traces to the statute it came from. Your agents do the work. Our engine keeps it honest. See the platform, how flow gaps feed risk management, and how recipients sit in third-party risk.
FAQ: MODPA strictly necessary, sensitive data and the cure provision
What does "strictly necessary" mean under MODPA? §14-4607(A) permits collecting or processing sensitive data only where it is "strictly necessary to provide or maintain a specific product or service requested by the consumer to whom the personal data pertains." The term is not defined in the statute.
Can a controller sell sensitive data in Maryland? No. §14-4607(A) states a controller may not "sell sensitive data," with no necessity exception attached to that line.
Is consumer health data in Maryland limited to medical records? No. §14-4601 defines it by use: personal data "that a controller uses to identify a consumer's physical or mental health status," including data related to gender-affirming care treatment and reproductive or sexual health care.
Does the Maryland Online Data Privacy Act cure period guarantee 60 days before enforcement? No. Under §14-4614, for alleged violations on or before April 1, 2027, the Division "may" issue a notice of violation if it "determines that a cure is possible." Only if a notice is issued does the controller have at least 60 days to cure.
A posture you can defend in front of a regulator, a board, or a plaintiff. Inside 60 minutes you'll see your exposure mapped to the obligations that actually apply to you. No call required. agrc.ai


