Minnesota Stopped Sending Warning Letters

On January 31, 2026, a sentence in the Minnesota Statutes expired right on schedule, and almost nobody noticed.

It’s the last sentence of Minn. Stat. § 325M.20(a). Here’s the paragraph it ends:

(a) In the event that a controller or processor violates sections 325M.10 to 325M.21, the attorney general, prior to filing an enforcement action under paragraph (b), must provide the controller or processor with a warning letter identifying the specific provisions of sections 325M.10 to 325M.21 the attorney general alleges have been or are being violated. If, after 30 days of issuance of the warning letter, the attorney general believes the controller or processor has failed to cure any alleged violation, the attorney general may bring an enforcement action under paragraph (b). This paragraph expires January 31, 2026.

The bolding is mine. The words are the Legislature’s.

That was the Minnesota Consumer Data Privacy Act’s right to cure. It’s gone — 217 days gone as I write this. In its place is § 325M.20(b) and (c): a civil action brought under Minn. Stat. § 8.31, an injunction, “a civil penalty of not more than $7,500 for each violation,” and, if the state wins, “the reasonable value of all or part of the state’s litigation expenses incurred.” No letter. No thirty days. No chance to fix it first.

Every client alert from 2024 and 2025 that told Minnesota businesses they had a cure period is now wrong. The ones sitting in a compliance binder are worse than wrong, because somebody’s relying on them. If there’s a 2024 MCDPA memo in your file, the paragraph that matters most in it has expired.

The Attorney General’s Office announced the change itself. In a February 5, 2026 communication headed “Minnesota Consumer Data Privacy Act takes full effect,” the office reported that in the statute’s first six months it had sent “hundreds of education letters” to companies, received “more than 200 complaints regarding the MCDPA,” and sent “dozens of warning letters to companies that identified problems with privacy policies, procedures for honoring consumer data rights, consent mechanisms for collecting sensitive data, and responses to universal opt-out signals.” Then it said the quiet part right in its own subheadline: “AGO can now bring enforcement actions without providing 30-day notice.”

Dozens of companies got a letter and a chance to clean things up. That door shut in January.

Two things you should know about me

The first is the usual one. My firm sells the work this essay describes — threshold determinations, assessments, vendor contract terms, response protocols. I make money when Minnesota businesses decide they need a lawyer for this. So check the sections yourself. Every one of them is linked at the bottom.

The second isn’t the usual one, and it doesn’t belong in a footer. I was a candidate for Minnesota Attorney General in the 2026 DFL primary. This essay is about that office’s enforcement powers — the $7,500-per-violation authority, the civil investigative demand, the litigation-expense award. If you found that out somewhere else after reading this, you’d be right to feel handled.

So I’m not going to tell you what I’d do with any of it. There’s no prediction here about how that office will or should use its discretion, no proposal, and nothing about the current officeholder beyond the office’s own published account of what it’s already done. What follows is statutes in force today, quoted from the Revisor’s text. They say what they say no matter who reads them out loud.

Subdivision 1, paragraph (g) is the strongest automated-decision right in the country

Here’s what Minnesota business lawyers mostly haven’t priced in. It isn’t the deletion right, and it isn’t the universal opt-out signal. It’s Minn. Stat. § 325M.14, subd. 1(g):

(g) If a consumer’s personal data is profiled in furtherance of decisions that produce legal effects concerning a consumer or similarly significant effects concerning a consumer, the consumer has the right to question the result of the profiling, to be informed of the reason that the profiling resulted in the decision, and, if feasible, to be informed of what actions the consumer might have taken to secure a different decision and the actions that the consumer might take to secure a different decision in the future. The consumer has the right to review the consumer’s personal data used in the profiling. If the decision is determined to have been based upon inaccurate personal data, taking into account the nature of the personal data and the purposes of the processing of the personal data, the consumer has the right to have the data corrected and the profiling decision reevaluated based upon the corrected data.

That’s a right on paper. In practice it’s a job, and the job starts the day a consumer sends in the form. On request, a controller has to be able to state the reason this decision came out the way it did — not the general logic of the system, “the reason that the profiling resulted in the decision.” If feasible, it has to give a counterfactual: what this person could have done differently. It has to show the person the input data. And if the inputs were wrong, it has to fix them and run the decision again.

Explainability, counterfactual explanation, and re-adjudication, in one paragraph, in a state privacy statute, in force since July 31, 2025.

The definitions are what give it teeth. “Profiling,” under § 325M.11(s), means “any form of automated processing of personal data to evaluate, analyze, or predict personal aspects related to an identified or identifiable natural person’s economic situation, health, personal preferences, interests, reliability, behavior, location, or movements.” Any form. A logistic-regression scoring model somebody wrote in 2009 is profiling. So is a spreadsheet with weights in it. The statute doesn’t care whether the vendor’s marketing says “AI.” And § 325M.11(i) defines the decisions that trigger the right — the provision or denial of “financial or lending services, housing, insurance, education enrollment or opportunity, criminal justice, employment opportunities, health care services, or access to essential goods or services.”

Now the parts that cost money.

The clock is 45 days. Section 325M.14, subd. 4(e), requires the controller to tell the consumer what it did on a subdivision 1 request “without undue delay and in any event within 45 days of receipt,” and it can extend that once by 45 more where reasonably necessary. But it has to tell the consumer about the extension inside the original 45 days, “together with the reasons for the delay.”

No browser signal handles this. Subdivision 2(d) lets a consumer name an authorized agent — that’s how global opt-out signals work — but only “to exercise the consumer’s right to opt out of the processing of the consumer’s personal data for purposes of targeted advertising and sale under subdivision 1, paragraph (f).” Paragraph (g) isn’t on that list. Profiling questions come in one at a time from real people, and a human has to work every one.

There’s a mandatory appeal, and a retention rule rides along with it. Under subd. 5(a) a controller “must establish an internal process whereby a consumer may appeal a refusal to take action.” Under subd. 5(d), the controller has to give written reasons, has to “clearly and prominently provide the consumer with information about how to file a complaint with the Office of the Attorney General,” and “must maintain records of all appeals and the controller’s responses for at least 24 months and shall, upon written request by the attorney general as part of an investigation, compile and provide a copy of the records to the attorney general.” Botch these and you’re building the state’s file for it.

The trade-secret out is narrower than vendors tell you. Subdivision 4(j) says “a controller is not required to reveal any trade secret.” That lets you keep a trade secret. It doesn’t let you skip stating the reason the profiling resulted in the decision. Those are two different things, and a vendor that blurs them is describing its own convenience.

And the state isn’t leaving consumers to figure this out on their own. The Attorney General’s Office posted template forms at privacymn.com for consumers to use in asserting these rights. Asking is the easy part now. Answering is on you.

Who’s in

Section 325M.12, subd. 1(a), applies the Act to “legal entities that conduct business in Minnesota or produce products or services that are targeted to residents of Minnesota,” that also cross one of two lines: controlling or processing personal data of 100,000 consumers or more in a calendar year, not counting data handled “solely for the purpose of completing a payment transaction”; or getting over 25 percent of gross revenue from selling personal data while processing or controlling data of 25,000 consumers or more.

Look at what’s missing. There’s no revenue-only threshold. A Minnesota company with half a billion dollars in revenue and forty thousand customers is outside the Act’s main obligations. A company with 100,001 customers and three million dollars in revenue is inside them. Dollars are the wrong question, and it’s the first one most executives ask.

Small businesses as the SBA size standards define them are carved out of most of the Act by § 325M.12, subd. 2(a)(19) — but not out of § 325M.17, which bars a small business from selling “a consumer’s sensitive data without the consumer’s prior consent” and expressly applies the § 325M.20 penalties and enforcement procedures to a violation. No small business is entirely outside this statute. Clause (19) is the only exclusion in subdivision 2(a) that leaves a duty behind, though. Clauses (16) and (18) put state and federally chartered banks, credit unions, and insurance companies entirely outside sections 325M.10 to 325M.21, and the threshold math above never gets to them.

The Legislature wrote the sales pitch, and put it in paragraph (f)

Section 325M.18 is the sleeper. It requires a controller to “conduct and document a data privacy and protection assessment” for five categories of processing. The fifth is the one that matters here — profiling, “where the profiling presents a reasonably foreseeable risk of”:

(i) unfair or deceptive treatment of, or disparate impact on, consumers;

(ii) financial, physical, or reputational injury to consumers;

(iii) a physical or other intrusion upon the solitude or seclusion, or the private affairs or concerns, of consumers, where the intrusion would be offensive to a reasonable person; or

(iv) other substantial injury to consumers.

Minnesota’s privacy statute puts disparate impact into the trigger for a mandatory, written assessment. If your business runs a model that scores people, somebody has to sit down and write out whether that model presents a reasonably foreseeable risk of disparate impact. Then you have to keep what they wrote.

Think about that for a second. The statute makes you create a document whose whole subject is your own legal exposure, and § 325M.18(d) tells you how to write it: the assessment “must identify and weigh the benefits that may flow directly and indirectly from the processing to the controller, consumer, other stakeholders, and the public against the potential risks to the rights of the consumer associated with the processing, as mitigated by safeguards that can be employed by the controller to reduce the potential risks.” That’s a risk memo. Anywhere else, your lawyer would tell you never to write it down.

The Legislature saw the problem. Section 325M.18(f):

(f) As part of a civil investigative demand, the attorney general may request, in writing, that a controller disclose any data privacy and protection assessment that is relevant to an investigation conducted by the attorney general. The controller must make a data privacy and protection assessment available to the attorney general upon a request made under this paragraph. The attorney general may evaluate the data privacy and protection assessments for compliance with sections 325M.10 to 325M.21. Data privacy and protection assessments are classified as nonpublic data, as defined by section 13.02, subdivision 9. The disclosure of a data privacy and protection assessment pursuant to a request from the attorney general under this paragraph does not constitute a waiver of the attorney-client privilege or work product protection with respect to the assessment and any information contained in the assessment.

There are two protections in there. Pull them apart.

The first is a classification. In the Attorney General’s hands, the assessment is “nonpublic data” under Minn. Stat. § 13.02, subd. 9, which defines the term as “data not on individuals made by statute or federal law applicable to the data: (a) not accessible to the public; and (b) accessible to the subject, if any, of the data.” That’s a public-access rule. A competitor, a reporter, or a plaintiff’s lawyer can’t pull your assessment out of the state’s files with a data practices request.

The second is the non-waiver sentence, and it’s the one that decides who should be doing this work. Handing your assessment to the Attorney General under paragraph (f) “does not constitute a waiver of the attorney-client privilege or work product protection with respect to the assessment and any information contained in the assessment.” Normally, voluntarily handing a privileged document to a government investigator is the textbook way to waive the privilege. The Legislature took that off the table for this one production.

Which hands me a sales pitch I didn’t have to make up, because the statute made it for me: the same assessment written by a consultant has no privilege for paragraph (f) to preserve. A consulting deliverable is a business record. It goes to the AG, and the AG reads exactly what it was written to be — the company’s own analysis of the risk that its model treats people unfairly. On that production, paragraph (f) preserves something a consultant never had.

What paragraph (f) doesn’t do

Here’s where a lawyer overselling this in public gets it wrong.

Paragraph (f) doesn’t create a privilege. It preserves one. Non-waiver language assumes something privileged existed before the production, and the threshold question — is this statutorily mandated assessment attorney-client privileged or work product at all? — isn’t answered anywhere in § 325M.18. A document created because a statute makes every covered business create it, on a schedule, as routine compliance, is exactly the document the other side will say was made for a business purpose and not in anticipation of litigation. That argument’s available, and it isn’t frivolous. Whether the assessment is privileged turns on who directed it, why, what it was for, and how the company treated it. Same analysis as always.

It doesn’t let you refuse to hand it over. The second sentence is mandatory: “The controller must make a data privacy and protection assessment available to the attorney general upon a request made under this paragraph.” Privilege survives the production. It doesn’t excuse it. Anybody selling you a privileged assessment as a way to keep the Attorney General from reading it has read the paragraph backwards.

The non-waiver covers one recipient and one request. The sentence protects “disclosure of a data privacy and protection assessment pursuant to a request from the attorney general under this paragraph.” It says nothing about handing it to a federal agency, another state’s attorney general, or a private litigant. Whether counsel’s assessment is protected from a private litigant gets decided by ordinary privilege and work-product law, not by paragraph (f). Selective-waiver doctrine is unfriendly ground generally, and paragraph (f) doesn’t reach past its own words.

And it’s thirteen months old. I haven’t found a Minnesota decision construing paragraph (f), and I wouldn’t tell a client one exists. The plain language is clear enough about what it does. How courts will handle the threshold privilege question for a compelled compliance document is wide open.

So the real pitch is narrower than the one you’ll hear, and it’s still a good one: the statute orders you to write down your own risk, and it takes away the biggest reason not to have a lawyer do the writing. Take the help. Don’t mistake it for a shield.

One more thing in § 325M.18 deserves a sentence. Paragraph (g) says assessments “conducted by a controller for the purpose of compliance with other laws or regulations may qualify under this section if the assessments have a similar scope and effect,” and paragraph (h) says “[a] single data protection assessment may address multiple sets of comparable processing operations that include similar activities.” Scope the work once for the strictest regime that applies and it carries over. Scope it six times and you’ve paid for it six times.

The disparate-impact trigger raises a question I haven’t answered

Section 325M.18(b)(5)(i) puts “unfair or deceptive treatment of, or disparate impact on, consumers” into a Minnesota statute as the trigger for a mandatory written assessment. Separately, § 325M.16, subd. 3(a), bars a controller from processing personal data on the basis of protected characteristics “in a manner that unlawfully discriminates” as to housing, employment, credit, education, or public accommodations.

How those provisions relate to the Minnesota Human Rights Act, Minn. Stat. ch. 363A — whether a § 325M.18 assessment becomes evidence in a chapter 363A case, and what “unlawfully discriminates” in § 325M.16 borrows from chapter 363A — is a real question, and I haven’t researched it. So I’ll flag it and leave it there. If your model makes employment or credit decisions about Minnesotans, that open question is a reason to have this conversation with a lawyer and not a vendor.

Colorado went backward, Europe moved the goalposts, and Minnesota did neither

Got a Colorado deck from 2024 or 2025? Throw it out. The Colorado AI Act everybody in this field spent two years writing about — high-risk AI systems, algorithmic discrimination, a duty of reasonable care — doesn’t exist in that form anymore. SB 24-205, approved May 17, 2024, keyed its duties to February 1, 2026. SB 25B-004, approved August 28, 2025, pushed them to June 30, 2026. Then the Act got challenged in federal court in X.AI LLC v. Weiser, No. 1:26-cv-01515 (D. Colo.), filed April 9, 2026. This comes from the docket, not the orders, so that’s all I’ll say about it. And on May 14, 2026, SB 26-189 repealed and reenacted the whole of part 17 of article 1 of title 6 under a new heading — automated decision-making technology in consequential decisions — effective January 1, 2027 and applying only to consequential decisions made on or after that date.

The citation survived. The statute behind it didn’t. The high-risk-system and algorithmic-discrimination vocabulary is out. The new text is built on automated decision-making technology, covered ADMT, and consequential decisions. Colorado also kept a 60-day notice-and-cure procedure that doesn’t itself sunset until January 1, 2030 — though it’s a break the enforcing authority may choose to give, and a defendant can’t demand it.

Line the two states up and you get a result that surprised me. A Minnesota business has less grace under Minnesota’s privacy statute today than a Colorado business will have under Colorado’s AI statute for its first three years. And on the narrow question of what one person can demand about one automated decision, Minnesota’s § 325M.14, subd. 1(g) — in force since July 2025 — is stronger than what Colorado’s replacement will offer in 2027. Colorado’s version gives human review only to the extent commercially reasonable and expressly doesn’t require correcting opinions, predictions, or scores. Minnesota didn’t pass an AI act. It passed a privacy act with an automated-decision provision in it, and that provision is doing more work than the AI act everybody was watching.

Europe reaches a Minnesota company through one clause, and it has nothing to do with having a European office. Regulation (EU) 2024/1689, article 2(1), applies the AI Act to:

(c) providers and deployers of AI systems that have their place of establishment or are located in a third country, where the output produced by the AI system is used in the Union;

No establishment. No marketing into the Union. No contract with an EU entity. All it takes is the output getting used there. A Minneapolis company whose résumé-ranking model scores applicants for a Dublin subsidiary is a deployer under 2(1)(c).

The dates moved six weeks ago, and most published checklists haven’t caught up. Regulation (EU) 2026/1744, of 8 July 2026, in force 27 July 2026, rewrote article 113. The high-risk obligations people had penciled in for 2026 and 2027 now apply from 2 December 2027 for Annex III systems — employment, credit, education, essential services — and 2 August 2028 for Annex I product systems. What is in force is the general application date of 2 August 2026, which carries the article 50 transparency duties: telling people they’re dealing with an AI system, marking synthetic output as machine-detectable, and disclosing deep fakes. Those have been binding for a month. A US company with EU-facing output is inside them right now, while it waits on a high-risk deadline that just walked away from it.

The ethics layer: one opinion, one FAQ, and a silence

For lawyers, not their clients, there are three things, and that’s it.

ABA Formal Opinion 512, July 29, 2024. Persuasive in Minnesota, not binding — it reads the Model Rules, and Minnesota lawyers answer to the Minnesota Rules of Professional Conduct. Two lines in it pull their weight. On consent under Rule 1.6: “To obtain informed consent when using a GAI tool, merely adding general, boiler-plate provisions to engagement letters purporting to authorize the lawyer to use GAI is not sufficient.” A lot of Minnesota engagement letters picked up exactly that clause in 2024. And on Rule 8.4(c): “Even an unintentional misstatement to a court can involve a misrepresentation under Rule 8.4(c).” There’s no good-faith-hallucination defense. I’ve written elsewhere in this section about what the opinion does to an hourly bill and won’t repeat it here.

The District of Minnesota answered the disclosure question in writing, and the answer is no. Its GenAI FAQ, dated October 1, 2025: “The District of Minnesota does not currently require disclosure of AI use in court filings. Litigants should be aware, however, of AI-use disclosure requirements in other jurisdictions.” The same document puts the burden where it belongs — “pursuant to Fed. R. Civ. P. 11 and 26(g), you are ultimately responsible for the accuracy and sufficiency of the resulting work product” — and asks for more than most firms are doing: “Confirm that GenAI-provided legal research and citations are valid references to existing caselaw, statutes, or regulations that have not been superseded or overruled, and that cited excerpts are not taken out of context.” That’s a citator pass. Checking that the case exists doesn’t cut it. It’s also an FAQ. It isn’t a standing order, and its teeth come from Rule 11, which it says out loud. And it doesn’t replace any individual judge’s practice pointers, which you still have to read case by case.

Minnesota has no Board opinion on it. Check the Lawyers Professional Responsibility Board two ways and you get the same answer: its published list of Board opinions runs 1 through 26 and none of them addresses artificial intelligence, and a site search for “artificial intelligence” returns “Sorry, but nothing matched your search terms.” So Minnesota lawyers are working from the general rules — 1.1, 1.4, 1.5, 1.6, 3.1, 3.3, 5.1, 5.3, 8.4 — and from persuasive out-of-state authority. That’s a gap. If you’re guessing about it, know that you’re guessing.

The contract is where this gets decided

The other essays in this run are about what you can prove about a model’s behavior and its provenance as a file. Both end up in the same spot: the risk is real, nobody’s been assigned it, and almost no vendor agreement assigns it. Here’s how to assign it, with the Minnesota hooks attached.

Per-decision explainability. You owe the consumer “the reason that the profiling resulted in the decision.” If your vendor won’t produce per-decision explanations, you can’t comply — and § 325M.13(f) shuts the obvious workaround: “In no event shall any contract relieve a controller or a processor from the liabilities imposed on a controller or processor by virtue of the controller’s or processor’s roles in the processing relationship under sections 325M.10 to 325M.21.” You can’t contract your way out of the liability. Contract in the capability: explanations on demand within an SLA shorter than 45 days, the input features actually used, a way to re-score corrected data, and a real remedy if the vendor can’t deliver.

Assessment cooperation, which the statute already gives you. Section 325M.13(b)(2) requires the processor to “provide information to the controller necessary to enable the controller to conduct and document any data privacy and protection assessments required by section 325M.18.” Quote that section in the negotiation. Then put it in the contract with a deadline, because a statutory duty owed to you with no contract clock on it is a duty you’ll be litigating in month eleven.

Training data and IP in the outputs. Here’s where it stands: across every jurisdiction surveyed for this piece — Minnesota, Colorado, and the European Union — no statute gives a deployer an indemnity for third-party IP claims arising from a model’s outputs. That’s purely a contract fight, and vendors fight hardest over the difference between indemnifying the model and indemnifying what the model produces. Draft for outputs, separately capped or uncapped, carved out of the general liability cap, with defense control and settlement consent assigned, plus a model-change notice covenant and a right to suspend use.

Your own data, in four questions. Is client or customer data used to train, fine-tune, or improve the vendor’s models? What’s kept, where, and for how long — remembering that § 325M.16, subd. 2(g), bars you from keeping personal data that’s no longer relevant and reasonably necessary, and your vendor’s default retention isn’t a defense? What happens on termination, with a deletion certification and a deadline? And which sub-processors, in which countries, under what flow-down?

One thing you don’t have to negotiate: § 325M.16, subd. 4, voids “[a]ny provision of a contract or agreement of any kind that purports to waive or limit in any way a consumer’s rights” under the Act. Terms-of-service boilerplate can’t touch MCDPA rights, in either direction.

What the work actually is

Strip out the consulting vocabulary and an AI governance engagement in Minnesota comes down to six documents, each tied to a subdivision instead of a framework.

A written applicability determination. One page per jurisdiction, with the citation and the trigger fact, because the triggers have nothing intuitive to do with each other: Minnesota counts consumers (§ 325M.12, subd. 1(a)); the EU counts where the output is used (art. 2(1)(c)); Colorado, from 2027, will count doing business in the state plus one covered individual, with no size floor. Several of the regimes a Minnesota company is likely to bump into have no revenue threshold at all. We’re too small for this isn’t an answer until somebody’s read the applicability sections.

A system inventory that catches the old models. Section 325M.16, subd. 2(c), already requires “the maintenance of an inventory of the data” as part of a controller’s security practices. That’s a statutory inventory duty in force in Minnesota today, AI or no AI. Build it against § 325M.11(s)’s functional definition of profiling, so it catches the scoring spreadsheet and not just whatever procurement bought last year.

The § 325M.18 assessments, scoped once for the strictest regime that applies and reused under paragraph (g).

The profiling response protocol, with templates, the subd. 5 appeal process, and the 24-month retention rule built into the records system — not into a policy document nobody opens.

The vendor contract terms above, in the master agreement, before signature. That’s the only time any of them are cheap.

A written AI use policy with a named human in it. Section 325M.18(a) requires the controller to document and maintain a description of its compliance policies and procedures, and that description has to include, where applicable, “the name and contact information for the controller’s chief privacy officer or other individual with primary responsibility for directing the policies and procedures implemented to comply with the provisions of sections 325M.10 to 325M.21.” The statute has a person in mind, not a committee.

What a lawyer should refuse to sell is a certificate that any of this makes the client compliant. It doesn’t. It cuts risk, it builds a record, and it preserves defenses. Anybody promising more is selling something the statutes don’t contain.

One side item, because it comes up in every one of these conversations and gets answered wrong. Minnesota’s criminal deep fake statute, Minn. Stat. § 617.262, has no private right of action. It’s a criminal statute, period. The civil cause of action is a separate section, Minn. Stat. § 604.32, and it’s a lot better than people expect: general and special damages, disgorgement of “any profit made from the dissemination,” “a civil penalty awarded to the plaintiff of an amount up to $100,000,” and attorney fees. Different subject, different facts. I’ve written about the remedies side of it for clients.

The best case against this essay

Here’s the argument I’d make against everything above, and it’s a good one.

The MCDPA has no private right of action. Section 325M.20(d) shuts that door in terms, “including under section 8.31, subdivision 3a.” So all the enforcement risk sits in one office with a finite number of privacy attorneys and a big docket of everything else. The office’s own February 2026 account describes education letters, warning letters, and complaint intake. That’s the posture of a regulator building a compliance culture, not one filing test cases. A business that figures the risk is low for the next twenty-four months isn’t being crazy.

There’s more. The words “if feasible” in subd. 1(g) are doing real work, and nobody knows how much yet. The trade-secret provision in subd. 4(j) will get litigated, and a company with a genuinely proprietary model will have arguments. And no Minnesota decision construing this statute has turned up, which cuts both ways — the aggressive reading is untested too.

I’ll give all of that up, and it still doesn’t move me. The $7,500 exposure is per violation, and what it takes to operate under subd. 1(g) — per-decision explanation, counterfactual, re-scoring on corrected data — can’t be built in the forty-five days after the first request shows up. It has to be negotiated into a vendor contract that may have three years left on it. Guess wrong about enforcement timing and the price isn’t a fine. It’s finding out in month eleven of a signed agreement that your vendor has no duty to tell you why it said no to somebody.

Here’s how I’d know I blew this one

The Attorney General brings no MCDPA enforcement action in the next two years. If September 2028 comes and goes with no case filed under sections 325M.10 to 325M.21, the expired cure period changed less than I say it did, and I leaned too hard on a statutory sunset and not hard enough on what the office actually does. Watch the lawsuits the office files, not the statute.

A court reads § 325M.18(f) narrowly and the privilege point falls apart. The likeliest path is a holding that a statutorily compelled compliance assessment is a business record made in the ordinary course, so no privilege ever attached and there was nothing for paragraph (f) to preserve. If that happens, the gap between a lawyer’s assessment and a consultant’s shrinks to the gap in the quality of the analysis. That’s a real gap. It’s a lot smaller than the one I’ve claimed here.

Subdivision 1(g) turns out to mean less than it says. If “if feasible” gets read to excuse the counterfactual whenever a model is complicated, and “the reason that the profiling resulted in the decision” is satisfied by a generic description of the system’s logic, then Minnesota’s automated-decision right is a notice requirement in a heavier coat, and I’m wrong that it’s the strongest in the country.

Federal preemption shows up and moots the state layer. If Congress or a court preempts the automated-decision provisions of the state privacy statutes, everything above is history. I’m not predicting that, and I wouldn’t tell a client to wait for it — telling a client to wait is telling a client to sit out of compliance with an in-force statute on a bet nobody can handicap. But if it happens, I built on sand.

I’ve told you my two interests, and they both point the same way: I sell this work, and I ran for the office that enforces it. The statutes are linked below. Read them and decide whether I got them right. That’s the only question that matters here.

Sources

Every Minnesota statute below was retrieved by curl from the Office of the Revisor of Statutes with a browser user-agent and read as raw text, not through a summarizer. The Revisor currently publishes the 2025 edition; each MCDPA section carries the Revisor’s note that it was added by Laws 2024, chapter 121, article 5, and is effective July 31, 2025, except that postsecondary institutions regulated by the Office of Higher Education are not required to comply until July 31, 2029.

• Minn. Stat. § 325M.10 — the short-title provision, which makes sections 325M.10 to 325M.21 citable as the Minnesota Consumer Data Privacy Act. The MCDPA is that section range, not all of chapter 325M, which also contains an older internet-privacy block and the social-media provisions
• Minn. Stat. § 325M.11 — paragraph (s), the functional definition of “profiling”; paragraph (i), “Decisions that produce legal or similarly significant effects concerning the consumer”
• Minn. Stat. § 325M.12 — subd. 1(a)(1)–(2), the 100,000-consumer and 25%-revenue/25,000-consumer thresholds; subd. 2(a)(19), the SBA small-business exclusion
• Minn. Stat. § 325M.13 — paragraph (b)(1)–(2), processor duties to assist with § 325M.14 requests and to supply information for § 325M.18 assessments; paragraph (f), no contract relieves either party of its liabilities
• Minn. Stat. § 325M.14 — subd. 1(f) profiling opt-out; subd. 1(g), quoted in full, the right to question a profiling result, to the reason for it, to a counterfactual “if feasible,” to review the input data, and to re-evaluation on corrected data; subd. 2(d), the authorized-agent mechanism limited to paragraph (f); subd. 4(d)–(e) 45-day clocks and the extension rule; subd. 4(j) trade secret; subd. 5(a) and (d), mandatory appeal, written reasons, AG-complaint information, and 24-month record retention producible to the attorney general
• Minn. Stat. § 325M.16 — subd. 1(b), profiling disclosure and out-of-notice opt-out method; subd. 2(c), the data-inventory requirement; subd. 2(g), the retention prohibition; subd. 3(a), the anti-discrimination provision; subd. 4, waiver of consumer rights is void
• Minn. Stat. § 325M.17 — small businesses may not sell sensitive data without prior consent, and § 325M.20’s penalties apply to a violation
• Minn. Stat. § 325M.18 — paragraph (a), documented policies and a named responsible individual; paragraph (b)(5), quoted in part, mandatory assessments for profiling presenting a reasonably foreseeable risk of “unfair or deceptive treatment of, or disparate impact on, consumers”; paragraph (d), the weighing standard; paragraph (f), quoted in full, the civil-investigative-demand production duty, the nonpublic-data classification, and the non-waiver of attorney-client privilege and work product; paragraphs (g)–(h), reciprocity and consolidation
• Minn. Stat. § 325M.20 — paragraph (a), quoted in full, the warning-letter-and-30-day-cure requirement and its self-executing expiration on January 31, 2026; paragraph (b), civil action under § 8.31 and litigation expenses; paragraph (c), injunction and “a civil penalty of not more than $7,500 for each violation”; paragraph (d), no private right of action
• Minn. Stat. § 13.02 — subd. 9, the definition of “nonpublic data” incorporated by § 325M.18(f)
• Minn. Stat. § 604.32 — subd. 3, the civil remedies for nonconsensual dissemination of a deep fake: general and special damages, disgorgement of profit, “a civil penalty awarded to the plaintiff of an amount up to $100,000,” and fees. Minn. Stat. § 617.262 is the criminal counterpart and contains no civil cause of action
• Office of the Minnesota Attorney General, Minnesota Consumer Data Privacy Act takes full effect (Feb. 5, 2026) — the subheadline “AGO can now bring enforcement actions without providing 30-day notice”; “hundreds of education letters”; “more than 200 complaints regarding the MCDPA” in the first six months; “dozens of warning letters”; the office’s description of the notice period sunsetting January 31, 2026; and the consumer template forms at privacymn.com
• Regulation (EU) 2024/1689, consolidated text as amended through 27 July 2026 — article 2(1)(c), quoted verbatim, the third-country trigger where “the output produced by the AI system is used in the Union”; article 113 as replaced by Regulation (EU) 2026/1744 of 8 July 2026 (OJ L 1744, 24.7.2026), showing Annex III high-risk obligations applying from 2 December 2027, Annex I from 2 August 2028, and articles 102–110 from 27 July 2026, against a general application date of 2 August 2026; article 50, the transparency obligations in force since that general date
• U.S. District Court, District of Minnesota, GenAI FAQ (Oct. 1, 2025) — “The District of Minnesota does not currently require disclosure of AI use in court filings”; the Rule 11 and 26(g) responsibility statement; and the practice pointer to confirm that cited authority has “not been superseded or overruled.” Text extracted from the court’s own PDF; the extraction renders one glyph in place of the “f” in fi/fl ligatures and I restored it, changing nothing else
• ABA Standing Committee on Ethics and Professional Responsibility, Formal Opinion 512, Generative Artificial Intelligence Tools (July 29, 2024) — the boiler-plate engagement-letter holding under Rule 1.6 and the Rule 8.4(c) unintentional-misstatement holding. americanbar.org refuses automated clients; I read the ABA’s own PDF through an Internet Archive capture of that exact URL. ABA formal opinions are persuasive in Minnesota, not binding
• Lawyers Professional Responsibility Board, Board Opinions and the site search for artificial intelligence — Opinions 1 through 26, none addressing artificial intelligence; the search returns “Sorry, but nothing matched your search terms”
• Colorado General Assembly, SB 24-205, SB 25B-004, and SB 26-189 — the original February 1, 2026 duty date, the delay to June 30, 2026, and the May 14, 2026 repeal-and-reenactment of part 17 of article 1 of title 6 as an automated-decision-making-technology framework, effective January 1, 2027. Nothing from Colorado is quoted in this essay: the signed act’s PDF text layer has corrupted intra-word spacing, and I will not put a normalized extraction inside quotation marks. Colorado propositions here are stated in my own words and should be checked against the printed session law
• X.AI LLC v. Weiser, No. 1:26-cv-01515 (D. Colo.), filed April 9, 2026 — docket facts only. I have not read any order in that case and nothing here characterizes one
• Companion essays in this section: The Gap Between Intended and Proven, Executable Code You Are Calling a Model, The Layer That Does Not Relocate, What You Owe the Client You Automated, and The Discovery of Your Prompts. On the client-facing side: AI-Assisted Identity Theft: What the Data Shows and Minnesota Voice and Likeness Cloning Remedies

General information about Minnesota and European law for a professional audience, current as of September 5, 2026 — not legal advice, and reading it creates no attorney–client relationship. The stated falsifiers are the author’s, and no outcome is promised or implied. Two interests are disclosed in the text and bear repeating: this firm sells the services described, and the author was a candidate for Minnesota Attorney General in the 2026 DFL primary. Nothing here predicts or proposes how that office would exercise its enforcement discretion. Minnesota state-court rules on artificial intelligence are outside this essay’s scope and are not addressed; the Minnesota Human Rights Act question raised by § 325M.18(b)(5)(i) is identified and expressly left open. No client information appears in this article. Questions about anything here: Send us a message or 612-470-6529.