Data Protection Monitor
Global Privacy & Data Protection Intelligence

Michigan, USA Data Protection & Privacy Regulation

US-MI schema gdpri-v2 trajectory: not yet assessed regulated (sectoral) overlaps: Sentinel (AML/CFT), World Payments, artificial-intelligence

Last updated · 10 categories · 69 claims · 43 sources in the cumulative register

Michigan's data-protection posture remains sectoral and federal-dependent, and the pending Personal Data Privacy Act (Senate Bill 359) is the state's first credible path to an omnibus privacy statute.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Algorithmic, Biometric & Surveillance Governance, Enforcement & Redress (3 open gaps).

Framework & posture10 of 10 modules active
10 active · 7 binding instruments
Supervisory authorityMichigan Attorney General
Next milestoneNo upcoming dated milestone on record
Record & confidence mix69 claims · 36 sources · machine-compiled
14 Confirmed44 Probable10 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 Michigan, USA is covered once, on the United States page. This page covers Michigan, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 26 October 2026

Lead Signal

Michigan's Attorney General continued an active enforcement-adjacent posture despite the state's continued absence of a comprehensive consumer-privacy statute, relying instead on sectoral and general consumer-protection authority. The most significant single item is the state's September 29, 2026 announcement of a $2.3 million multistate settlement with Laboratory Corporation of America resolving an investigation into the 2019 AMCA data breach, which affected sensitive health data of tens of thousands of Michigan residents; the settlement imposes vendor-management, incident-response-plan, and data-minimization requirements on Labcorp going forward.

Key regulatory facts for Michigan, USA
Key regulatory facts for Michigan, USA
Regulatory DimensionMichigan, USA Standing Position
JurisdictionMichigan, USA (US-MI)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 69 sourced findings)
Regulator & FrameworkNo comprehensive regulator/statute, but active federal (FTC) and state AG sectoral enforcement plus a pending state Kids Code Act create a partially-regulated, evolving picture rather than a total gap.
Lawful Processing & Special DataAbsence of a general lawful-basis/consent/special-category framework in state law; only sectoral federal consent rules apply.
Data Subject RightsNo omnibus rights statute; gap is explicit and confirmed by seed disambiguation and searches.
Controller/Processor DutiesGeneral accountability/DPIA/DPO/ROPA obligations are absent, but sector-specific security and breach duties are confirmed and in force.
Primary Instruments CitedMichigan Legislature (Act 452 of 2004 index), Michigan Legislature (Act 452 full text PDF), DataGuidance, Michigan, USA Official Instrument (recordinglaw.com michigan-data-privacy-laws), DataGuidance
Last Confirmed / Updated (43 sources in cumulative register)

#

No comprehensive regulator/statute, but active federal (FTC) and state AG sectoral enforcement plus a pending state Kids Code Act create a partially-regulated, evolving picture rather than a total gap.

Primary frameworkFTC Act Section 5 (federal) + Michigan Identity Theft Protection Act (Act 452 of 2004) (breach notification only)
Supervisory authorityMichigan Attorney General
Traffic-light rationale — AmberNo comprehensive regulator/statute, but active federal (FTC) and state AG sectoral enforcement plus a pending state Kids Code Act create a partially-regulated, evolving picture rather than a total gap.

Sub-modules (5)

Regulator and authorityAmber

The Michigan Attorney General holds general consumer-protection enforcement authority; the FTC holds concurrent federal unfair/deceptive-practices authority reaching Michigan-based conduct.

Claims (4):

  • Michigan has no comprehensive consumer-privacy statute; data-protection enforcement rests on the FTC's Section 5 authority, the Michigan Attorney General's general consumer-protection powers, and applicable federal sectoral laws.
  • Michigan has no comprehensive consumer-privacy statute; data-related enforcement runs through the Attorney General's general consumer-protection authority and the ITPA, which addresses breach notification only.
  • Michigan has no comprehensive consumer-privacy statute; the Identity Theft Protection Act governs data-breach notification only.
  • The Michigan Attorney General holds general consumer-protection enforcement authority over data-handling conduct; FTC holds concurrent federal Section 5 authority. No dedicated state DPA exists.

Act and instrumentsAmber

Primary instruments are the federal FTC Act Section 5 and Michigan's Identity Theft Protection Act (Act 452 of 2004).

Claims (4):

  • Section 5 of the FTC Act prohibits unfair or deceptive acts and practices in or affecting commerce and is the FTC's primary legal authority over privacy and data-security conduct nationally, including in Michigan.
  • Michigan's breach-notification statute is the Identity Theft Protection Act, Public Act 452 of 2004, which has been the subject of subsequent amendment bills (e.g., SB 0672 of 2021).
  • Michigan Personal Data Privacy Act (SB 359) — Introduced 5 June 2025; referred to Senate Finance, Insurance, and Consumer Protection Committee; no enactment located this cycle; data-broker registry provision's drafted 1 February 2026 start date has passed with no registry operating
  • Identity Theft Protection Act, Act 452 of 2004 (MCL 445.61-445.79c) — Sec. 12 (MCL 445.72) requires notice to affected Michigan residents without unreasonable delay, subject to a no-substantial-harm exception.

Material scopeRed

Material scope is narrow: the ITPA covers only breach notification for defined personal identifying information; no general processing-scope statute exists.

Claims (1):

  • Michigan's data-protection material scope is limited to breach-notification obligations for defined personal identifying information; no statute governs general collection, use, or processing of personal data.

Territorial scopeAmber

FTC Section 5 authority is not geographically limited and reaches conduct affecting Michigan consumers regardless of the entity's location.

Claims (1):

  • FTC Section 5 authority is not limited by the location of the entity and reaches practices affecting commerce, including Michigan consumers, regardless of where the controller is established.

Regulator registration and filingRed

No controller registration or filing obligation exists under Michigan law.

Claims (3):

  • No controller/processor registration or filing regime exists under Michigan law.
  • SB 360-364 passed the Senate on 2025-08-26 and remain pending in the House.
  • Senate Bills 359-364 (Personal Privacy Data Act package) — Would create a Personal Privacy Data Act and amend the breach law, including annual data-broker registration with the AG beginning Feb 1, 2026 if enacted; SB 360 passed the Senate and sat in the House Committee on Government Operations, with SB 359 showing less momentum.
Category narrative 62 words

Michigan has no comprehensive omnibus consumer-privacy statute. Data-protection matters in Michigan are governed by a patchwork: (1) the federal FTC Act Section 5 unfair/deceptive-practices authority, enforced by the Federal Trade Commission nationally including against Michigan-domiciled entities; (2) the Michigan Attorney General's general consumer-protection authority; and (3) Michigan's Identity Theft Protection Act (breach notification only). No Michigan-specific data-protection regulator or registration/filing regime exists.

Periodic update · new data 2026-10-04

Michigan has not yet enacted a comprehensive privacy and data protection act. In the absence of a dedicated state data-protection authority, the Michigan Attorney General holds general enforcement authority over the state's data-breach-notification statute and over consumer-protection matters implicating personal data. This general-authority arrangement is understood to be the operative accountability structure today, though it falls well short of the dedicated-regulator model found in comprehensive state privacy regimes elsewhere.

The principal legislative vehicle for change is Senate Bill 359, the Personal Data Privacy Act, introduced June 12, 2025. As introduced, it would create Michigan's first comprehensive consumer-privacy framework, including a requirement that data brokers register annually with the Attorney General, beginning February 1 of the year following enactment, supported by a public registry and a $100-per-day penalty for non-registration. Violations of the bill's substantive provisions would carry civil fines of $7,500 each, to be deposited into a proposed Consumer Privacy Fund. The bill has not been enacted and remains in the Committee of the Whole; whether it advances before the end of the legislative session is unresolved.

Outlook

The Committee of the Whole's handling of Senate Bill 359 is the single most consequential open question for Michigan's regulator and framework posture. Enactment would create Michigan's first comprehensive privacy statute and, with it, the state's first dedicated data-broker registration regime; continued inaction would leave the Attorney General's general enforcement authority as the operative structure for the foreseeable future.

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

Sources and claims (13)
  1. Confirmed NAAG — Michigan has no comprehensive consumer-privacy statute; data-protection enforcement rests on the FTC's Section 5 authority, the Michigan Attorney General's general consumer-protection powers, and applicable federal sectoral laws. observed
  2. Confirmed FTC — Section 5 of the FTC Act prohibits unfair or deceptive acts and practices in or affecting commerce and is the FTC's primary legal authority over privacy and data-security conduct nationally, including in Michigan. observed
  3. Confirmed DataGuidance — Michigan's breach-notification statute is the Identity Theft Protection Act, Public Act 452 of 2004, which has been the subject of subsequent amendment bills (e.g., SB 0672 of 2021). observed
  4. Confirmed NAAG — Michigan's data-protection material scope is limited to breach-notification obligations for defined personal identifying information; no statute governs general collection, use, or processing of personal data. observed
  5. Probable FTC — FTC Section 5 authority is not limited by the location of the entity and reaches practices affecting commerce, including Michigan consumers, regardless of where the controller is established. observed
  6. Confirmed NAAG — No controller/processor registration or filing regime exists under Michigan law. observed
  7. Probable Vote Smart (SB 360 synopsis) — Michigan Personal Data Privacy Act (SB 359) — Introduced 5 June 2025; referred to Senate Finance, Insurance, and Consumer Protection Committee; no enactment located this cycle; data-broker registry provision's drafted 1 February 2026 start date has passed with no registry operating observed
  8. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/michigan-data-privacy-laws/ — Michigan has no comprehensive consumer-privacy statute; data-related enforcement runs through the Attorney General's general consumer-protection authority and the ITPA, which addresses breach notification only.
  9. Confirmed Michigan Legislature (Act 452 of 2004 index) — Michigan has no comprehensive consumer-privacy statute; the Identity Theft Protection Act governs data-breach notification only. observed
  10. Probable Vote Smart (SB 360 synopsis) — SB 360-364 passed the Senate on 2025-08-26 and remain pending in the House. observed
  11. Probable Michigan Legislature (Act 452 of 2004 index) — The Michigan Attorney General holds general consumer-protection enforcement authority over data-handling conduct; FTC holds concurrent federal Section 5 authority. No dedicated state DPA exists. observed
  12. Probable Vote Smart (SB 360 synopsis) — Identity Theft Protection Act, Act 452 of 2004 (MCL 445.61-445.79c) — Sec. 12 (MCL 445.72) requires notice to affected Michigan residents without unreasonable delay, subject to a no-substantial-harm exception. observed
  13. Probable Michigan Legislature (Act 452 full text PDF) — Senate Bills 359-364 (Personal Privacy Data Act package) — Would create a Personal Privacy Data Act and amend the breach law, including annual data-broker registration with the AG beginning Feb 1, 2026 if enacted; SB 360 passed the Senate and sat in the House Committee on Government Operations, with SB 359 showing less momentum. observed

#

Absence of a general lawful-basis/consent/special-category framework in state law; only sectoral federal consent rules apply.

Traffic-light rationale — RedAbsence of a general lawful-basis/consent/special-category framework in state law; only sectoral federal consent rules apply.

Sub-modules (4)

Lawful basesRed

No enumerated lawful-bases framework exists in Michigan law.

Claims (1):

  • Michigan law contains no enumerated lawful-basis framework analogous to GDPR Article 6; processing is governed only by sector-specific notice/consent rules.

Special categoriesAmber

No Michigan special-category statute; federal FTC guidance treats biometric/genetic data as sensitive for enforcement purposes.

Claims (1):

  • The FTC's Policy Statement on Biometric Information signals federal enforcement priority around biometric data as sensitive, though Michigan itself has no state-level biometric or special-category statute (unlike Illinois, Texas, or Washington).

Pseudonymisation and anonymisationRed

No statutory definitions or safe harbours for pseudonymisation or anonymisation exist under Michigan law.

Category narrative 35 words

Michigan has no GDPR-style enumerated lawful-bases regime, no general consent standard, and no state-defined special-category rules. Consent-type obligations exist only in narrow federal sectoral contexts (e.g., COPPA parental consent). Pseudonymisation/anonymisation are undefined in Michigan statute.

Sources and claims (3)
  1. Confirmed NAAG — Michigan law contains no enumerated lawful-basis framework analogous to GDPR Article 6; processing is governed only by sector-specific notice/consent rules. observed
  2. Confirmed FTC — COPPA requires operators of commercial websites/online services directed to children under 13, or with actual knowledge of collecting data from a child, to obtain verifiable parental consent before collecting, using, or disclosing the child's personal information. observed
  3. Confirmed FTC — The FTC's Policy Statement on Biometric Information signals federal enforcement priority around biometric data as sensitive, though Michigan itself has no state-level biometric or special-category statute (unlike Illinois, Texas, or Washington). observed

#

No omnibus rights statute; gap is explicit and confirmed by seed disambiguation and searches.

Traffic-light rationale — RedNo omnibus rights statute; gap is explicit and confirmed by seed disambiguation and searches.

Sub-modules (5)

Access rightRed

No statutory access right exists for Michigan consumers generally.

Claims (1):

  • Michigan law confers no general statutory data-subject rights of access, rectification, erasure, restriction, objection, or portability; such rights are absent absent a comprehensive state privacy statute.

Rectification and erasureRed

No statutory rectification or erasure right exists.

Claims (1):

  • Michigan law confers no general statutory data-subject rights of access, rectification, erasure, restriction, objection, or portability; such rights are absent absent a comprehensive state privacy statute.

Restriction and objectionRed

No statutory restriction or objection right exists.

Claims (1):

  • Michigan law confers no general statutory data-subject rights of access, rectification, erasure, restriction, objection, or portability; such rights are absent absent a comprehensive state privacy statute.

Data portabilityRed

No statutory portability right exists.

Claims (1):

  • Michigan law confers no general statutory data-subject rights of access, rectification, erasure, restriction, objection, or portability; such rights are absent absent a comprehensive state privacy statute.

Deadlines and response windowsRed

No general statutory response-window regime exists outside the ITPA's breach-notification timing.

Category narrative 23 words

Michigan confers no general statutory rights of access, rectification, erasure, restriction, objection, or portability. No comprehensive deadline/response-window regime exists outside the breach-notification context.

Sources and claims (1)
  1. Confirmed NAAG — Michigan law confers no general statutory data-subject rights of access, rectification, erasure, restriction, objection, or portability; such rights are absent absent a comprehensive state privacy statute. observed

#

General accountability/DPIA/DPO/ROPA obligations are absent, but sector-specific security and breach duties are confirmed and in force.

Primary frameworkMichigan Identity Theft Protection Act (Act 452 of 2004); Michigan Insurance Data Security Act (2018, amending Insurance Code, MCL 500.3101 et seq.)
Supervisory authorityMichigan Attorney General
Traffic-light rationale — AmberGeneral accountability/DPIA/DPO/ROPA obligations are absent, but sector-specific security and breach duties are confirmed and in force.

Sub-modules (7)

Accountability & DPIARed

No general accountability principle or DPIA-trigger statute exists in Michigan law.

Claims (1):

  • No general accountability principle or DPIA-trigger obligation exists in Michigan statute.

DPO requirementsRed

No DPO appointment threshold exists under Michigan law.

Claims (1):

  • No DPO appointment threshold or independence requirement exists under Michigan law.

Ropa requirementsRed

No ROPA (records of processing) requirement exists under Michigan law.

Claims (1):

  • No records-of-processing-activities requirement exists under Michigan law.

Joint controller arrangementsRed

Michigan law does not define controller/processor roles or joint-controller arrangements.

Claims (1):

  • Michigan law does not define controller/processor roles nor regulate joint-controller arrangements.

Security measuresAmber

The Michigan Insurance Data Security Act requires licensees to maintain risk-based written information-security programs; no general economy-wide security-measures statute exists.

Claims (2):

  • The Michigan Insurance Data Security Act requires licensees (licensed insurers or producers) to develop, implement, and maintain a comprehensive written information-security programme based on the licensee's risk assessment, following the NAIC Insurance Data Security Model Law with Michigan-specific modifications.
  • SB 360 — Pending (House Committee on Government Operations as of August 2026); would add civil fines up to $2,000 for failing to maintain required security procedures or investigate a potential breach.

Breach notificationAmber

The Identity Theft Protection Act requires notification of security breaches involving personal identifying information, consistent with the general pattern of US state breach laws.

Claims (5):

  • Consistent with the general pattern across US state breach laws, Michigan's Identity Theft Protection Act requires organizations to notify individuals in the case of a data breach involving certain personal identifying information.
  • Michigan's ITPA requires breach notification without unreasonable delay but has no fixed deadline and no AG-notification trigger.
  • Senate Bills 888-892 would impose a 45-day AG breach-notification deadline for breaches affecting 100+ Michigan residents.
  • MCL 445.72(1) — A person or agency that owns or licenses data in a database and discovers a security breach must provide notice to each affected Michigan resident without unreasonable delay.
  • MCL 445.72(1) requires breach notice to affected Michigan residents without unreasonable delay.

Retention and disposalRed

No general retention/disposal duty statute exists outside sector-specific contexts (e.g., insurance).

Claims (2):

  • No general economy-wide data-retention or disposal-duty statute exists in Michigan outside sector-specific regimes such as insurance data security.
  • Michigan Identity Theft Protection Act (MCL 445.72a) — Any entity maintaining a database of personal information must destroy that data when removed from the database absent another lawful purpose for retention; violations carry misdemeanor penalties up to $250 per violation.
Category narrative 42 words

No general accountability, DPIA, DPO, ROPA, or joint-controller framework exists in Michigan law. Sector-specific security and breach-notification duties do exist: the Identity Theft Protection Act requires breach notification, and the Michigan Insurance Data Security Act imposes risk-based information-security-program duties on insurance licensees.

Periodic update · new data 2026-10-26

Michigan's controller and processor duties currently run through the Identity Theft Protection Act (MCL 445.72), which requires a person or agency owning or licensing a database containing personal information to notify affected Michigan residents of a security breach involving unencrypted or unredacted personal information without unreasonable delay. The statute sets no fixed-day deadline for notification, imposes no current duty to notify the Attorney General, and caps penalties at $250 per failed notification up to $750,000 per breach event; it creates no private right of action.

That framework is under active reform pressure. Senate Bills 888-892 would require notification to the Attorney General of any data breach affecting 100 or more Michigan residents within 45 days, would expand consumer-notice triggers, and would grant the Attorney General's office investigative authority over data breaches. The Michigan Attorney General's office testified in support of the package before the Senate Committee on Finance, Insurance, and Consumer Protection, signaling active executive-branch backing for the reform, though the bills remain at the proposed stage with current committee status beyond the testified hearing not established.

Outlook

Whether SB 888-892 advances out of committee following the Attorney General's supportive testimony is the development to watch; its enactment would materially shorten notification timelines and introduce a regulator-notification duty that does not currently exist under Michigan law.

Sources and claims (13)
  1. Confirmed NAAG — No general accountability principle or DPIA-trigger obligation exists in Michigan statute. observed
  2. Confirmed NAAG — No DPO appointment threshold or independence requirement exists under Michigan law. observed
  3. Confirmed NAAG — No records-of-processing-activities requirement exists under Michigan law. observed
  4. Confirmed NAAG — Michigan law does not define controller/processor roles nor regulate joint-controller arrangements. observed
  5. Confirmed DataGuidance — The Michigan Insurance Data Security Act requires licensees (licensed insurers or producers) to develop, implement, and maintain a comprehensive written information-security programme based on the licensee's risk assessment, following the NAIC Insurance Data Security Model Law with Michigan-specific modifications. observed
  6. Probable NAAG — Consistent with the general pattern across US state breach laws, Michigan's Identity Theft Protection Act requires organizations to notify individuals in the case of a data breach involving certain personal identifying information. observed
  7. Confirmed NAAG — No general economy-wide data-retention or disposal-duty statute exists in Michigan outside sector-specific regimes such as insurance data security. observed
  8. Probable RecordingLaw.com — Michigan's ITPA requires breach notification without unreasonable delay but has no fixed deadline and no AG-notification trigger. observed
  9. Probable Legal 500 — Senate Bills 888-892 would impose a 45-day AG breach-notification deadline for breaches affecting 100+ Michigan residents. observed
  10. Probable Michigan Legislature (Act 452 full text PDF) — SB 360 — Pending (House Committee on Government Operations as of August 2026); would add civil fines up to $2,000 for failing to maintain required security procedures or investigate a potential breach. observed
  11. Confirmed Michigan Legislature — Michigan Identity Theft Protection Act (MCL 445.72a) — Any entity maintaining a database of personal information must destroy that data when removed from the database absent another lawful purpose for retention; violations carry misdemeanor penalties up to $250 per violation. observed
  12. Confirmed Michigan Legislature (MCL 445.72) — MCL 445.72(1) — A person or agency that owns or licenses data in a database and discovers a security breach must provide notice to each affected Michigan resident without unreasonable delay. observed
  13. Confirmed Michigan Legislature (MCL 445.72) — MCL 445.72(1) requires breach notice to affected Michigan residents without unreasonable delay. observed

#

No state mechanism exists; federal mechanism status requires further verification given historical Safe Harbor/Privacy Shield invalidations.

Supervisory authorityFederal Trade Commission
Traffic-light rationale — RedNo state mechanism exists; federal mechanism status requires further verification given historical Safe Harbor/Privacy Shield invalidations.

Sub-modules (6)

Transfer mechanismsAmber

FTC enforces companies' cross-border privacy-framework commitments under Section 5; no Michigan-specific transfer mechanism exists.

Claims (1):

  • The FTC enforces companies' compliance with cross-border privacy-framework commitments (e.g., the former EU-U.S. Privacy Shield and successor frameworks) as deceptive-practice violations under Section 5, applicable nationally including to Michigan-based entities.

Adequacy receivedAmber

The EU-U.S. Data Privacy Framework operates as the federal adequacy-equivalent mechanism for US recipients, including Michigan entities; current litigation status requires independent verification.

Claims (1):

  • A federal EU-US adequacy-equivalent transfer framework (Privacy Shield and its successors) has historically operated to permit EU-to-US personal data transfers, with the FTC as enforcement authority; current framework status and any pending legal challenges require independent verification.

Adequacy grantedRed

The concept of a US state 'granting' adequacy to other regimes does not apply; no Michigan or federal adequacy-granting mechanism exists.

SCCs and BCRsRed

SCCs/BCRs are EU-side mechanisms; Michigan law does not independently regulate their use domestically.

Transfer impact assessmentRed

No Michigan TIA requirement exists.

Data localisationRed

No Michigan data-localisation mandate exists.

Category narrative 46 words

Michigan has no state-level transfer-mechanism, adequacy, SCC/BCR, TIA, or data-localisation regime. Cross-border data-transfer governance operative for Michigan-based entities occurs at the federal level via FTC Section 5 enforcement of commitments under frameworks such as the EU-U.S. Data Privacy Framework (successor to the defunct Privacy Shield/Safe Harbor).

Sources and claims (2)
  1. Probable FTC — The FTC enforces companies' compliance with cross-border privacy-framework commitments (e.g., the former EU-U.S. Privacy Shield and successor frameworks) as deceptive-practice violations under Section 5, applicable nationally including to Michigan-based entities. observed
  2. Uncertain FTC — A federal EU-US adequacy-equivalent transfer framework (Privacy Shield and its successors) has historically operated to permit EU-to-US personal data transfers, with the FTC as enforcement authority; current framework status and any pending legal challenges require independent verification. observed

#

Sectoral overlays are well-established at the federal level and confirmed for insurance at state level; employment data privacy remains a gap.

Primary frameworkGLBA; HIPAA; FCRA; FERPA; TCPA; Michigan Insurance Data Security Act
Supervisory authorityFederal Trade Commission
Traffic-light rationale — AmberSectoral overlays are well-established at the federal level and confirmed for insurance at state level; employment data privacy remains a gap.

Sub-modules (7)

Financial sector overlayGreen

GLBA governs financial institutions' handling of consumer financial data nationally, enforced in part by the FTC.

Claims (1):

  • The FTC has authority to enforce the Gramm-Leach-Bliley Act as a sector-specific financial-privacy law applicable nationally, including to Michigan financial institutions.

Health sector overlayGreen

HIPAA and the FTC's Health Breach Notification Rule govern health data nationally.

Claims (2):

  • The FTC enforces the Health Breach Notification Rule and reviews the GLB Safeguards regime as sector-specific health/financial-data-security tools that supplement HIPAA nationally.
  • Laboratory Corporation of America — On 2026-09-29, Michigan's Attorney General announced a $2.3 million multistate settlement with Labcorp resolving an investigation into the 2019 AMCA data breach affecting tens of thousands of Michigan residents' sensitive health data, imposing vendor-management, incident-response-plan, and data-minimization requirements.

Telecoms and eprivacyAmber

The federal Telemarketing Sales Rule and Do Not Call Registry govern telemarketing/robocall practices nationally; no Michigan-specific ePrivacy law exists.

Claims (1):

  • The FTC's Do Not Call Registry and Telemarketing Sales Rule prohibit abusive telemarketing practices nationally, including calling numbers on the DNC Registry and use of illegal robocalls; the registry includes more than 241 million registrations.

Employment dataRed

No Michigan-specific employment-data privacy statute was identified.

Claims (1):

  • No Michigan-specific employment-data privacy statute was identified; employment data is governed by general federal nondiscrimination and workplace law only.

Credit and scoringGreen

FCRA governs consumer reporting/credit scoring nationally, with FTC enforcement of furnisher accuracy duties.

Claims (1):

  • The FTC enforces the Fair Credit Reporting Act's Furnisher Rule requiring companies that report consumer information to consumer reporting agencies to maintain accuracy policies, as illustrated by a 2026 FTC settlement with an auto-finance furnisher.

educationGreen

FERPA governs student education-record privacy nationally.

Claims (1):

  • The federal Family Educational Rights and Privacy Act (20 U.S.C. §1232g) governs student education-record privacy nationally.

insuranceGreen

The Michigan Insurance Data Security Act imposes NAIC Model Law-based security-programme duties on insurance licensees.

Claims (1):

  • The Michigan Insurance Data Security Act requires licensees (licensed insurers or producers) to develop, implement, and maintain a comprehensive written information-security programme based on the licensee's risk assessment, following the NAIC Insurance Data Security Model Law with Michigan-specific modifications.
Category narrative 50 words

Michigan-based entities are subject to multiple federal sectoral overlays (GLBA for financial institutions, HIPAA/FTC Health Breach Notification Rule for health data, FCRA for credit reporting/scoring, FERPA for education records, TCPA/Telemarketing Sales Rule for telecoms/direct contact) plus the state-specific Michigan Insurance Data Security Act. No Michigan-specific employment-data privacy statute was identified.

Periodic update · new data 2026-10-26

The principal sectoral development is the $2.3 million multistate settlement announced September 29, 2026 between the Michigan Attorney General and Laboratory Corporation of America, resolving an investigation into the 2019 AMCA data breach that affected sensitive health data belonging to tens of thousands of Michigan residents. The settlement imposes going-forward requirements on Labcorp covering vendor management, maintenance of an incident-response plan, and data minimization, reflecting the health sector's continued exposure to third-party vendor risk arising from a single upstream breach event (the American Medical Collection Agency breach) that generated liability for multiple downstream healthcare entities.

The settlement is enforced through the Attorney General's general consumer-protection and multistate-coordination authority rather than through any Michigan-specific health-privacy statute, consistent with the state's continued reliance on sectoral and general enforcement tools in the absence of a comprehensive privacy law.

Outlook

Further multistate settlements tied to the AMCA breach, or new health-sector vendor-risk enforcement actions following the Labcorp template, are the pattern to watch for in this sector.

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

The health sector is where Michigan's enforcement activity concentrated this period. On 29 September 2026 the Attorney General announced a $2.3 million multistate settlement with Laboratory Corporation of America over the 2019 AMCA data breach, an incident involving a billing-collections vendor used across the medical-testing industry. The settlement imposes going-forward requirements on Labcorp covering vendor-management practices, an incident-response plan, and data-minimization commitments, each functioning as an enforceable compliance obligation notwithstanding that Michigan has no dedicated health-sector privacy statute of its own.

This is a multistate action, meaning Michigan's $2.3 million recovery is one state's share of a coordinated settlement negotiated jointly with other attorneys general, and the settlement terms were formalized in a filed agreement rather than through litigated judgment. The settlement is the clearest evidence this period that sectoral health-data obligations in Michigan are being shaped through multistate attorney-general coordination and negotiated settlement terms rather than through a comprehensive state health-privacy statute. The vendor-management and data-minimization conditions attached to the settlement function, for Labcorp specifically, as a forward-looking compliance baseline in a way that ordinary statutory breach-notification duties do not.

Outlook

Whether this settlement structure becomes a template the Attorney General applies to other health-sector or vendor-breach matters, or remains a one-off resolution tied to the specific AMCA incident, is not yet established. The multistate settlement model, however, offers Michigan's Attorney General a mechanism for imposing structural compliance terms on regulated entities that the state's current statute book does not otherwise authorize directly.

Sources and claims (7)
  1. Confirmed FTC — The FTC has authority to enforce the Gramm-Leach-Bliley Act as a sector-specific financial-privacy law applicable nationally, including to Michigan financial institutions. observed
  2. Confirmed FTC — The FTC enforces the Health Breach Notification Rule and reviews the GLB Safeguards regime as sector-specific health/financial-data-security tools that supplement HIPAA nationally. observed
  3. Confirmed FTC — The FTC's Do Not Call Registry and Telemarketing Sales Rule prohibit abusive telemarketing practices nationally, including calling numbers on the DNC Registry and use of illegal robocalls; the registry includes more than 241 million registrations. observed
  4. Uncertain NAAG — No Michigan-specific employment-data privacy statute was identified; employment data is governed by general federal nondiscrimination and workplace law only. observed
  5. Confirmed FTC — The FTC enforces the Fair Credit Reporting Act's Furnisher Rule requiring companies that report consumer information to consumer reporting agencies to maintain accuracy policies, as illustrated by a 2026 FTC settlement with an auto-finance furnisher. observed
  6. Confirmed Virginia General Assembly — The federal Family Educational Rights and Privacy Act (20 U.S.C. §1232g) governs student education-record privacy nationally. observed
  7. Probable Michigan Department of Attorney General — Laboratory Corporation of America — On 2026-09-29, Michigan's Attorney General announced a $2.3 million multistate settlement with Labcorp resolving an investigation into the 2019 AMCA data breach affecting tens of thousands of Michigan residents' sensitive health data, imposing vendor-management, incident-response-plan, and data-minimization requirements. observed

#

General adult-facing adtech regulation is absent at state level; federal FTC enforcement provides a partial backstop; minor-specific restrictions are pending, not yet law.

Supervisory authorityFederal Trade Commission
Traffic-light rationale — AmberGeneral adult-facing adtech regulation is absent at state level; federal FTC enforcement provides a partial backstop; minor-specific restrictions are pending, not yet law.

Sub-modules (6)

Cookies and trackersAmber

No Michigan cookie-consent law; FTC Section 5 reaches deceptive tracking practices, illustrated by the pending FTC v. Kochava matter.

Claims (1):

  • The FTC's ongoing enforcement action against Kochava (filed and continuing as of mid-2026) illustrates federal Section 5 enforcement reaching location-data/tracking practices nationally, in the absence of a Michigan-specific tracker-consent law.

Dark patternsAmber

No general adult dark-pattern statute exists; Michigan's pending minor-focused bills (HB 5357, SB 758) would prohibit dark patterns directed at minors.

Claims (1):

  • Michigan's pending Age-Appropriate Design Code bill (HB 5357) would prohibit profiling minors unless strictly necessary, selling minors' personal information, using dark patterns, and facilitating targeted advertising to minors, but the bill remains pending.

Opt out signalsRed

No Michigan requirement to honour universal opt-out signals (e.g., GPC) exists.

Claims (1):

  • No Michigan statute requires recognition of universal opt-out preference signals such as Global Privacy Control.

Clean rooms and dcrRed

No Michigan-specific regulation of data clean rooms exists.

Cross context advertisingRed

Michigan law does not codify 'sale'/'share' cross-context-advertising concepts as in CPRA.

Claims (1):

  • Michigan law does not define or regulate 'sale' or 'share' of personal information for cross-context behavioural advertising as under CPRA-style statutes.

Direct marketingAmber

Federal Telemarketing Sales Rule/DNC Registry governs direct-marketing suppression nationally; a pending Michigan Consumer Protection Act amendment (SB 759) could add state-level enhancements.

Claims (1):

  • The FTC's Do Not Call Registry and Telemarketing Sales Rule prohibit abusive telemarketing practices nationally, including calling numbers on the DNC Registry and use of illegal robocalls; the registry includes more than 241 million registrations.
Category narrative 51 words

Michigan has no state-level cookie-consent, opt-out-signal, clean-room, or cross-context-advertising ('sale'/'share') statute. FTC Section 5 enforcement against location-data brokers and adtech (e.g., Kochava) applies nationally. Michigan's pending Age-Appropriate Design Code (HB 5357) and Kids Code Act (SB 758) would introduce dark-pattern and targeted-advertising restrictions specific to minors if enacted, but remain proposed.

Sources and claims (4)
  1. Probable FTC — The FTC's ongoing enforcement action against Kochava (filed and continuing as of mid-2026) illustrates federal Section 5 enforcement reaching location-data/tracking practices nationally, in the absence of a Michigan-specific tracker-consent law. observed
  2. Probable DataGuidance — Michigan's pending Age-Appropriate Design Code bill (HB 5357) would prohibit profiling minors unless strictly necessary, selling minors' personal information, using dark patterns, and facilitating targeted advertising to minors, but the bill remains pending. observed
  3. Confirmed NAAG — No Michigan statute requires recognition of universal opt-out preference signals such as Global Privacy Control. observed
  4. Confirmed NAAG — Michigan law does not define or regulate 'sale' or 'share' of personal information for cross-context behavioural advertising as under CPRA-style statutes. observed

#

Federal biometric/genetic protections exist as enforcement priorities/anti-discrimination law; Michigan-specific ADM/AI/biometric/surveillance statutes remain pending or unconfirmed.

Supervisory authorityFederal Trade Commission
Traffic-light rationale — AmberFederal biometric/genetic protections exist as enforcement priorities/anti-discrimination law; Michigan-specific ADM/AI/biometric/surveillance statutes remain pending or unconfirmed.

Sub-modules (6)

Profiling restrictionsAmber

No general Michigan profiling-restriction statute; pending Kids Code Act/AADC bills would restrict profiling of minors.

Claims (1):

  • Michigan's pending Age-Appropriate Design Code bill (HB 5357) would prohibit profiling minors unless strictly necessary, selling minors' personal information, using dark patterns, and facilitating targeted advertising to minors, but the bill remains pending.

Automated decision making transparencyRed

A Michigan bill addressing automated decisions and electronic matters was identified but its substantive text/status could not be confirmed from available sources.

Claims (1):

  • A Michigan legislative bill addressing the use of automated decisions and electronic matters was introduced/reported as of early March 2026; substantive provisions and enactment status could not be confirmed from available sources.

AI risk assessmentsRed

A Michigan AI Safety and Security Transparency Act bill was identified but its substantive text/status could not be confirmed from available sources.

Claims (3):

  • A Michigan 'AI Safety and Security Transparency Act' bill was referenced in secondary sources as of mid-2025; substantive provisions and enactment status could not be confirmed from available sources.
  • Michigan joined a multistate AG coalition bankruptcy-court filing seeking enforceable privacy and child-safety protections from Character.AI.
  • Eli Savit, Michigan Attorney General-elect — Pledged to use MCPA rulemaking authority within first 100 days in office (term begins January 2027) to issue rules addressing misuse of artificial intelligence; no rule yet proposed or adopted.

Biometric regimeAmber

No Michigan biometric-privacy statute exists; the FTC's Biometric Policy Statement (2023) reflects federal enforcement posture but is non-binding guidance.

Claims (1):

  • The FTC's Policy Statement on Biometric Information reflects federal enforcement priority on biometric data protection; Michigan has no comparable state biometric-privacy statute analogous to Illinois's BIPA.

Genetic dataAmber

No Michigan-specific genetic-privacy statute exists; the federal Genetic Information Nondiscrimination Act (GINA) and FTC Section 5 enforcement against DNA-testing companies apply nationally.

Claims (1):

  • The FTC has brought Section 5 enforcement actions against direct-to-consumer genetic-testing companies (e.g., 1Health.io/Vitagene) for failing to protect the privacy and security of DNA data, applicable nationally including Michigan consumers; federal GINA separately prohibits genetic discrimination in employment and health insurance.

State surveillance carveoutsRed

A Michigan bill on regulating automatic license-plate readers was identified but its substantive text/status could not be confirmed from available sources.

Claims (1):

  • A Michigan bill on regulating automatic license-plate readers was identified in early 2026; substantive provisions and enactment status could not be confirmed from available sources.
Category narrative 54 words

Michigan has no state biometric-privacy statute (unlike Illinois BIPA), no genetic-data-specific statute, and no enacted ADM-transparency or AI-risk-assessment law. Pending bills exist on automated decisions/electronic matters, an AI Safety and Security Transparency Act, and automatic license-plate-reader regulation, but none were confirmed enacted. Federally, the FTC's Biometric Policy Statement and GINA (genetic non-discrimination) apply nationally.

Periodic update · new data 2026-11-15

Michigan has no enacted statute governing algorithmic decision-making, biometric processing, or automated surveillance tools as such. The development worth recording is political rather than regulatory: Eli Savit, elected Michigan Attorney General on 3 November 2026 for a term beginning in January 2027, is reported to have pledged to use the Michigan Consumer Protection Act's rulemaking authority within his first hundred days in office to issue rules addressing misuse of artificial intelligence. No rule has been proposed or adopted, and the pledge itself has not been tested against the scope of existing statutory authority. The Michigan Consumer Protection Act is a general consumer-protection statute, not a bespoke algorithmic-governance framework, so any rule issued under it would necessarily be bounded by that acts existing coverage and exemptions rather than creating a freestanding AI-specific regime.

The practical significance for organizations deploying algorithmic or AI-driven tools that reach Michigan residents is that a new enforcement posture is possible from January 2027 onward, built on an existing consumer-protection statute rather than new primary legislation. Reports suggest the incoming administration intends to extend its enforcement attention toward AI products marketed to or affecting minors and toward automated or dynamic pricing practices, framed under the same general consumer-protection authority. None of this has yet produced a proposed rule, a consultation, or a enforcement action, and the underlying statutory authority being invoked is the states existing consumer-protection law rather than a new biometric or algorithmic-specific instrument. Organizations operating algorithmic systems touching Michigan residents have, at this stage, a signal to monitor rather than an obligation to meet.

Outlook

The window to watch opens in January 2027, when the incoming Attorney Generals term begins and the pledged hundred-day rulemaking period would run its course if pursued on the stated timeline. As scheduled, any resulting rule would be the first Michigan-specific instrument addressing algorithmic or AI misuse, issued under existing consumer-protection rulemaking authority rather than new legislation. Whether a rule is actually proposed, and what it would cover, is not yet known, and the current absence of any Michigan-specific algorithmic-governance statute remains the operative position until a rule is issued.

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

Michigan has no state algorithmic-governance statute, but the Attorney General's office engaged with algorithmic-system risk through a different channel: a multistate coalition filing, joined by Michigan on October 15, 2026, in the bankruptcy proceedings of Character Technologies, Inc. (Character.AI). The filing identifies safety and privacy-practice concerns with the company's AI-companion product and calls for enforceable privacy and child-safety protections to be made binding conditions on any purchaser of the company's assets, including removal of professional-impersonating characters and data access and deletion rights for users.

This is a bankruptcy-court filing rather than a state statute, regulation, or settlement with binding force in its own right; whether it results in enforceable conditions on a purchaser or remains advisory has not been established. It nonetheless signals that Michigan's enforcement attention is extending to algorithmic consumer products through available procedural channels even without dedicated legislative authority.

Outlook

The outcome of the Character.AI bankruptcy sale process, and whether the coalition's proposed conditions attach to any purchaser, is the development to watch; it would be the clearest signal yet of how far existing consumer-protection and bankruptcy-notice tools can be stretched to cover algorithmic-product governance absent a dedicated statute.

Periodic update · new data 2026-10-25

Michigan's most significant algorithmic-governance activity this period arose not from state rulemaking but from a multistate bankruptcy-court filing. On 15 October 2026, a coalition of attorneys general from 38 states and the District of Columbia, Michigan among them, filed a notice in the bankruptcy proceedings of Character Technologies, Inc., the operator of the Character.AI conversational-AI platform, seeking enforceable privacy and child-safety protections from any purchaser of the company's assets. The filing responds to what the coalition characterizes as serious concerns about the platform's safety and privacy practices.

The filing is procedurally distinct from a consent decree or a settled enforcement action: it is a notice filed within an ongoing bankruptcy proceeding, asking the court to attach conditions to whatever sale process disposes of the company's assets. It carries no binding force on its own. Its significance lies in its scope and timing — a bankruptcy sale is one of the few moments at which a multistate coalition can seek to impose structural conditions on an AI platform's future ownership and operating practices, something none of the coalition states, including Michigan, could otherwise compel through existing statute given the absence of comprehensive algorithmic-governance law in most of the participating states.

Outlook

The open question is whether the bankruptcy court treats the coalition's filing as grounds for binding conditions on a purchaser or allows the sale to proceed without such conditions attached. That determination, expected as the bankruptcy process advances, will decide whether this filing produces an enforceable instrument governing the platform's future privacy and safety practices or remains a statement of attorney-general position with no binding effect.

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

Sources and claims (7)
  1. Uncertain DataGuidance — A Michigan legislative bill addressing the use of automated decisions and electronic matters was introduced/reported as of early March 2026; substantive provisions and enactment status could not be confirmed from available sources. observed
  2. Uncertain DataGuidance — A Michigan 'AI Safety and Security Transparency Act' bill was referenced in secondary sources as of mid-2025; substantive provisions and enactment status could not be confirmed from available sources. observed
  3. Confirmed FTC — The FTC's Policy Statement on Biometric Information reflects federal enforcement priority on biometric data protection; Michigan has no comparable state biometric-privacy statute analogous to Illinois's BIPA. observed
  4. Confirmed FTC — The FTC has brought Section 5 enforcement actions against direct-to-consumer genetic-testing companies (e.g., 1Health.io/Vitagene) for failing to protect the privacy and security of DNA data, applicable nationally including Michigan consumers; federal GINA separately prohibits genetic discrimination in employment and health insurance. observed
  5. Uncertain DataGuidance — A Michigan bill on regulating automatic license-plate readers was identified in early 2026; substantive provisions and enactment status could not be confirmed from available sources. observed
  6. Probable Michigan Department of Attorney General — Michigan joined a multistate AG coalition bankruptcy-court filing seeking enforceable privacy and child-safety protections from Character.AI. observed
  7. Uncertain WilmerHale — Eli Savit, Michigan Attorney General-elect — Pledged to use MCPA rulemaking authority within first 100 days in office (term begins January 2027) to issue rules addressing misuse of artificial intelligence; no rule yet proposed or adopted. observed

#

Federal COPPA/FERPA baseline is in force; state-level minor-specific enhancements are actively progressing through the legislature but not yet law; dependent-adult protection is an explicit gap.

Primary frameworkCOPPA (federal); pending Michigan Kids Code Act (SB 758) and Age-Appropriate Design Code (HB 5357)
Supervisory authorityFederal Trade Commission
Traffic-light rationale — AmberFederal COPPA/FERPA baseline is in force; state-level minor-specific enhancements are actively progressing through the legislature but not yet law; dependent-adult protection is an explicit gap.

Sub-modules (5)

Age verificationGreen

The FTC issued a COPPA enforcement-discretion policy statement (Feb 2026) regarding age-verification technologies used solely to determine user age.

Claims (2):

  • The FTC issued a policy statement (February 25, 2026) announcing it will not bring COPPA Rule enforcement actions against operators that collect, use, and disclose personal information solely to determine a user's age via age-verification technologies.
  • The multistate coalition filing seeks age-verification measures beyond self-reported birthdates given the number of minors using Character.AI.

Minor profiling bansAmber

Michigan's pending Kids Code Act (SB 758) and Age-Appropriate Design Code (HB 5357) would restrict profiling, targeted advertising, and data-minimization practices for minors; both remain unenacted.

Claims (4):

  • Michigan Senate Bill No. 758 (the Kids Code Act) passed the Senate on April 29, 2026, requiring covered online service providers to set default privacy settings to the highest level for minors, restrict targeted advertising, and submit annual audit reports, with civil fines up to $50,000 per violation; its effective date of July 1, 2026 is contingent on enactment of companion Senate Bill No. 759, and as of dispatch the bill was pending before the House Committee on Communication and Technology.
  • Michigan's pending Age-Appropriate Design Code bill (HB 5357) would prohibit profiling minors unless strictly necessary, selling minors' personal information, using dark patterns, and facilitating targeted advertising to minors, but the bill remains pending.
  • Michigan Kids Code Act (SB 758/759) — Drafted 1 July 2026 effective date passed without confirmed House passage; status disputed between secondary trackers
  • TAKE IT DOWN Act (Pub. L. 119-12) — Covered platforms, beginning May 19, 2026, to maintain an NCII reporting system and remove reported content and known identical copies within 48 hours, enforced by the FTC.

Education settingsGreen

FERPA governs student education-record privacy nationally, including Michigan schools.

Claims (1):

  • The federal Family Educational Rights and Privacy Act (20 U.S.C. §1232g) governs student education-record privacy nationally.

Dependent adultsRed

No Michigan-specific dependent-adults (elderly/incapacitated) data-privacy statute was identified.

Claims (1):

  • No Michigan-specific statute addressing data-privacy protections for dependent adults (elderly or mentally incapacitated individuals) was identified.
Category narrative 59 words

Federal COPPA governs children's data nationally, including Michigan, requiring verifiable parental consent. Michigan has two significant pending minor-protection bills: the Kids Code Act (SB 758, passed the Senate April 29, 2026, pending House committee) and an Age-Appropriate Design Code (HB 5357, introduced December 2025), neither yet enacted. FERPA governs education-record privacy nationally. No Michigan-specific dependent-adults data-privacy statute was identified.

Periodic update · new data 2026-10-26

The same multistate Character.AI bankruptcy filing that Michigan joined on October 15, 2026 carries a specific children's-protection component: the coalition's filing seeks, as a condition on any purchaser of the company's assets, age-verification measures that go beyond self-reported birthdates, citing the large number of minors reported to be using Character.AI. This is the state's most concrete child-protection-adjacent action and arises through a bankruptcy-notice mechanism rather than through dedicated state children's-privacy legislation.

No Michigan-specific statutory age-verification or minors'-data requirement exists outside this filing; the state continues to rely on general consumer-protection authority and multistate coordination where child-safety concerns intersect with a specific company's circumstances, as here.

Outlook

Whether the age-verification condition sought in the Character.AI filing becomes a binding term of any asset sale, or remains an unenforceable request, will determine whether this episode produces a lasting protection for Michigan minors or remains a one-off advisory position.

3 earlier distinct updates
Periodic update · new data 2026-10-25

Within the multistate Character.AI bankruptcy filing of 15 October 2026, the coalition — joined by Michigan — specifically sought age-verification measures that go beyond self-reported birthdates as a condition attaching to any purchaser of the company's assets. The coalition grounded this demand in the number of minors reported to be using the Character.AI platform, treating self-declared age as an inadequate control given that usage profile.

This is a notable escalation in the age-verification conversation: rather than proposing new state legislation mandating verification standards, the coalition is attempting to use the leverage available at a bankruptcy sale to impose a verification standard as a binding condition on a specific platform's ownership transition. No Michigan-specific legislative or regulatory age-verification standard accompanies this filing; the demand exists only within the bankruptcy proceeding and would bind only a purchaser of Character.AI's assets, not the broader population of platforms serving minors in Michigan.

Outlook

Whether the bankruptcy court adopts an age-verification standard beyond self-reported birthdates as a binding sale condition will determine whether this filing has any precedential value for future multistate action against other platforms serving minors. Absent that outcome, the demand remains a stated coalition position rather than an enforceable requirement.

Periodic update · new data 2026-10-11

The Michigan Kids Code Act, carried under Senate Bill 758 and its tie-barred companion Senate Bill 759, was drafted with a 1 July 2026 effective date for its core provisions and a 1 January 2027 start date for a civil-fine mechanism of up to $50,000 per violation. Both dates have now passed or are approaching without the bill's enactment status being confirmed. The primary legislative-history record available this cycle shows the bill's last action as a House referral on 29 April 2026, with no record of subsequent passage, while separate secondary trackers have reported conflicting signals suggesting the bill may have advanced further. This discrepancy has not been resolved.

The practical consequence is genuine uncertainty, not merely pending status: a bill whose own drafted effective date has passed without confirmed enactment leaves open the question of what minor-data-protection obligations, if any, currently bind covered entities operating in Michigan under this specific instrument. This is distinct from a simple pending-bill scenario, where no obligation could yet be said to apply; here, the drafted timeline itself has lapsed, and the enactment question is disputed rather than settled in either direction.

No other Michigan-specific children's-data development was located this cycle.

Outlook

The unresolved question of SB 758/759's enactment status is the single item of highest consequence in this module. Confirmation one way or the other — whether through the Michigan Legislature's own updated bill-history record or through a corroborated secondary source — would resolve whether the Kids Code Act's minor-profiling restrictions and civil-fine exposure are currently operative in Michigan or remain prospective.

Periodic update · new data 2026-10-04

The Kids Code Act, enacted as Senate Bill 758, is the most material children's-privacy development in Michigan this period. It mandates high privacy settings by default and limits data collection and targeted advertising directed at minors on online services, with an effective date of July 1, 2026. This is a material new instrument in the minors'-privacy space, reaching data-collection and advertising practice in a way that Michigan's general breach-notification statute does not.

A second, related measure, Senate Bill 760, would regulate companion chatbots for minors specifically to prevent the chatbots from encouraging harmful behavior or serving as unsupervised mental-health therapy tools. SB 760 has passed the Michigan Senate; its disposition in the House has not been confirmed this period, so its ultimate enactment status remains open.

Outlook

The practical operation and enforcement posture of the Kids Code Act following its July 1, 2026 effective date is the near-term item to observe, since the Act's obligations are now live but their enforcement in practice has not yet been reported. Separately, whether Senate Bill 760 advances through the House and is enacted would add a second, complementary children's-privacy instrument specifically targeting companion-chatbot services.

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

Sources and claims (6)
  1. Confirmed FTC — The FTC issued a policy statement (February 25, 2026) announcing it will not bring COPPA Rule enforcement actions against operators that collect, use, and disclose personal information solely to determine a user's age via age-verification technologies. observed
  2. Probable DataGuidance — Michigan Senate Bill No. 758 (the Kids Code Act) passed the Senate on April 29, 2026, requiring covered online service providers to set default privacy settings to the highest level for minors, restrict targeted advertising, and submit annual audit reports, with civil fines up to $50,000 per violation; its effective date of July 1, 2026 is contingent on enactment of companion Senate Bill No. 759, and as of dispatch the bill was pending before the House Committee on Communication and Technology. observed
  3. Uncertain NAAG — No Michigan-specific statute addressing data-privacy protections for dependent adults (elderly or mentally incapacitated individuals) was identified. observed
  4. Disputed Michigan Legislature (MCL 445.72) — Michigan Kids Code Act (SB 758/759) — Drafted 1 July 2026 effective date passed without confirmed House passage; status disputed between secondary trackers observed
  5. High Michigan Legislature (Act 452 of 2004 index) — TAKE IT DOWN Act (Pub. L. 119-12) — Covered platforms, beginning May 19, 2026, to maintain an NCII reporting system and remove reported content and known identical copies within 48 hours, enforced by the FTC. observed
  6. Probable Michigan Department of Attorney General — The multistate coalition filing seeks age-verification measures beyond self-reported birthdates given the number of minors using Character.AI. observed

#

Federal enforcement activity is robust and well-documented; state-specific private-right-of-action and regulator-capacity data remain partially unconfirmed.

Primary frameworkFTC Act Section 5
Supervisory authorityFederal Trade Commission
Traffic-light rationale — AmberFederal enforcement activity is robust and well-documented; state-specific private-right-of-action and regulator-capacity data remain partially unconfirmed.

Sub-modules (6)

Regulator powers and penaltiesGreen

FTC Section 5 empowers investigation and enforcement against unfair/deceptive practices nationally.

Claims (3):

  • Section 5 of the FTC Act prohibits unfair or deceptive acts and practices in or affecting commerce and is the FTC's primary legal authority over privacy and data-security conduct nationally, including in Michigan.
  • Civil fines of up to $250 per failed notification, capped at $750,000 per breach event, apply under the ITPA.
  • Identity Theft Protection Act, MCL 445.72 — Civil fine of up to $250 per failed notification for knowing failure to provide required breach notification, reported by secondary sources as aggregating to a cap around $750,000 per breach event; the aggregate cap could not be confirmed against the primary statutory text this cycle.

Enforcement activity indexGreen

Recent 2026 FTC actions (RentGrow, Amazon, Kochava, Illuminate Education) evidence continued national enforcement activity.

Claims (1):

  • Recent FTC privacy/security enforcement actions in 2026 include U.S. v. RentGrow, Inc. (July 9, 2026), U.S. v. Amazon.com, Inc. (June 30, 2026), FTC v. Kochava, Inc. (June 26, 2026), and In the Matter of Illuminate Education, Inc. (June 5, 2026), demonstrating continued active national enforcement applicable to Michigan consumers.

Regulator funding and capacityRed

No specific data on Michigan AG privacy-unit funding or headcount was identified.

Claims (1):

  • No specific data on the Michigan Attorney General's dedicated privacy-enforcement unit funding or headcount was identified in available sources.

Collective redress and class actionsAmber

The Michigan Attorney General participates in multistate breach-related settlements (e.g., Uber Technologies) alongside other state AGs.

Claims (1):

  • State attorneys general, including Michigan's, frequently collaborate on multistate data-breach settlements, with recent examples including a settlement involving Uber Technologies, Inc.

Private right of actionAmber

Whether Michigan's Identity Theft Protection Act itself confers a private right of action for breach-notification failures could not be confirmed; most, but not all, state breach statutes provide one.

Claims (4):

  • Some, but not all, US state breach-notification statutes provide a private right of action for noncompliance; whether Michigan's Identity Theft Protection Act specifically confers such a right could not be confirmed from available sources.
  • MCL 445.72(15) preserves other civil remedies but does not itself create a private right of action for notification failures.
  • Michigan Identity Theft Protection Act — Does not include a private right of action but explicitly does not eliminate other remedies available by law.
  • Michigan Identity Theft Protection Act (MCL 445.72) — Requires notification to affected residents without unreasonable delay after discovering a security breach, unless determined not likely to cause substantial loss, injury or identity theft; no private right of action; no current AG notification duty

Recent developments 180dAmber

Within the last 180 days, Michigan's Kids Code Act (SB 758) passed the Senate (April 29, 2026) and is pending House committee review; the companion Consumer Protection Act amendment (SB 759) was reported favorably out of committee (March 24, 2026).

Claims (4):

  • Michigan Senate Bill No. 759, amending the Michigan Consumer Protection Act, was reported favorably without amendment out of the Committee on Finance, Insurance, and Consumer Protection on March 24, 2026 and referred to the Committee of the Whole; it was introduced December 17, 2025.
  • SB 360 — Remains pending in the Michigan House Committee on Government Operations with no further action recorded since its August 2025 referral, as of August 2026.
  • Michigan Senate Bill 360 — Would require notification to affected Michigan residents and to the Attorney General (for breaches affecting 100+ residents) within 45 days of determining a breach occurred, replacing the current 'without unreasonable delay' standard
  • Eli Savit (D) defeated Doug Lloyd (R) in the Nov 3, 2026 Michigan Attorney General election; incoming-AG client alerts report expected expansion of consumer-protection enforcement into data privacy, algorithmic/dynamic pricing, and AI products aimed at minors once his term begins January 2027.
Category narrative 63 words

The FTC's Section 5 authority provides the principal enforcement lever nationally, with recent 2026 actions (RentGrow, Amazon, Kochava, Illuminate Education) demonstrating ongoing activity relevant to Michigan consumers. The Michigan Attorney General participates in multistate breach-related settlements. Michigan's Kids Code Act (SB 758) and Consumer Protection Act amendment (SB 759) are the most significant recent developments, both still pending as of the dispatch date.

Periodic update · new data 2026-11-15

The Michigan Attorney General holds general consumer-protection enforcement authority over data-handling conduct, with the Federal Trade Commission holding concurrent federal authority under Section 5; Michigan has no dedicated state data-protection authority separate from this general consumer-protection office. The notable development is the 3 November 2026 election of Eli Savit as Michigan Attorney General, who defeated Doug Lloyd for the office with a term beginning in January 2027. Client-alert commentary covering the incoming-AG transition reports an expectation that Savit will expand consumer-protection enforcement attention into data privacy, algorithmic and dynamic pricing practices, and AI products aimed at minors once his term begins. The election outcome itself is a confirmed fact; the enforcement-priority expansion is, at this stage, a reported expectation rather than an announced program, and no enforcement action, investigation, or rule has yet followed from it.

On the penalty side, Michigans Identity Theft Protection Act sets a civil fine of up to two hundred fifty dollars per failed notification for a knowing failure to provide a required breach notification under the statute. Secondary commentary reports this aggregating to a cap in the region of seven hundred fifty thousand dollars per breach event, but that aggregate figure could not be confirmed against the primary statutory text and should be read as a secondary-sourced estimate rather than a verified statutory ceiling. The per-notification figure itself rests on the same statute that has governed Michigan breach notification since 2005 and has not changed.

Outlook

The period to watch is the opening months of 2027, when the incoming Attorney General takes office and any shift in enforcement priorities toward data privacy, algorithmic pricing, or AI products aimed at minors would first become visible in practice rather than in campaign or transition commentary. As scheduled, the underlying enforcement authority remains the states general consumer-protection statute; what may change is which conduct the office chooses to prioritize under that existing authority, not the authority itself.

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

Michigan's enforcement and redress landscape showed notable activity across three fronts: the $2.3 million Labcorp multistate settlement announced September 29, 2026; the Attorney General's testimony in support of Senate Bills 888-892 before the Senate Committee on Finance, Insurance, and Consumer Protection, which would grant the office new breach-investigation authority; and the October 15, 2026 multistate filing in the Character.AI bankruptcy proceedings. Each reflects the Attorney General's continued reliance on general consumer-protection authority, sectoral statutes, and available procedural channels such as bankruptcy notices, rather than on a comprehensive privacy statute, which Michigan still lacks.

On redress specifically, the Identity Theft Protection Act's breach-notification provision (MCL 445.72) does not create a private right of action for notification failures; its own subsection (15) preserves other civil remedies but does not itself confer one, meaning enforcement for notification failures runs through the Act's own civil fines rather than through a Michigan Consumer Protection Act claim or private litigation.

Outlook

The pending SB 888-892 package would, if enacted, materially expand the Attorney General's investigative authority over data breaches; combined with the active Labcorp and Character.AI matters, this cycle shows an Attorney General's office pressing the limits of existing tools while a comprehensive statutory mandate remains absent.

Periodic update · new data 2026-10-25

Michigan's redress architecture for data-protection matters runs almost entirely through the Attorney General rather than through private litigation. The Identity Theft Protection Act, at MCL 445.72(15), preserves other civil remedies that might independently exist but does not itself create a private right of action for a notification failure. That means a resident harmed by a late or absent breach notice cannot sue specifically for the notification failure under this statute; the available lever is the Attorney General's own civil-fine authority, capped at $250 per failed notice and $750,000 per breach.

This period's enforcement record illustrates how much weight that Attorney General-centered model carries in practice. The $2.3 million multistate Labcorp/AMCA settlement, announced 29 September 2026, is a direct exercise of that authority, recovering a monetary settlement and imposing vendor-management and data-minimization terms without need of a private suit. The Character.AI bankruptcy coalition filing of 15 October 2026 is a different enforcement posture again: not a direct action under Michigan statute at all, but participation in a multistate advocacy filing within a federal bankruptcy proceeding, seeking protections no single state's consumer-protection statute could compel on its own. Taken together, this period shows the Attorney General using three distinct mechanisms — statutory civil-fine enforcement, negotiated multistate settlement, and coalition bankruptcy-court advocacy — in the absence of a comprehensive state privacy statute or an individual private right of action.

Outlook

The pending Senate Bills 888-892 would add investigative authority for the Attorney General specific to breach matters, reinforcing the state-enforcement-only model rather than introducing a private right of action. Separately, the proposed Michigan Consumer Privacy Act (House Bill 5989) would create data-subject rights enforceable exclusively by the Attorney General, again preserving the absence of individual litigation as a redress mechanism. Both proposals, if enacted, would expand the Attorney General's toolkit without altering the structural absence of a private right of action in Michigan's data-protection regime.

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

Sources and claims (13)
  1. Confirmed FTC — Recent FTC privacy/security enforcement actions in 2026 include U.S. v. RentGrow, Inc. (July 9, 2026), U.S. v. Amazon.com, Inc. (June 30, 2026), FTC v. Kochava, Inc. (June 26, 2026), and In the Matter of Illuminate Education, Inc. (June 5, 2026), demonstrating continued active national enforcement applicable to Michigan consumers. observed
  2. Uncertain NAAG — No specific data on the Michigan Attorney General's dedicated privacy-enforcement unit funding or headcount was identified in available sources. observed
  3. Probable NAAG — State attorneys general, including Michigan's, frequently collaborate on multistate data-breach settlements, with recent examples including a settlement involving Uber Technologies, Inc. observed
  4. Uncertain IAPP — Some, but not all, US state breach-notification statutes provide a private right of action for noncompliance; whether Michigan's Identity Theft Protection Act specifically confers such a right could not be confirmed from available sources. observed
  5. Probable DataGuidance — Michigan Senate Bill No. 759, amending the Michigan Consumer Protection Act, was reported favorably without amendment out of the Committee on Finance, Insurance, and Consumer Protection on March 24, 2026 and referred to the Committee of the Whole; it was introduced December 17, 2025. observed
  6. Probable RecordingLaw.com — MCL 445.72(15) preserves other civil remedies but does not itself create a private right of action for notification failures. observed
  7. Confirmed Davis Wright Tremaine — Michigan Identity Theft Protection Act — Does not include a private right of action but explicitly does not eliminate other remedies available by law. observed
  8. Confirmed Michigan Legislature (Act 452 full text PDF) — SB 360 — Remains pending in the Michigan House Committee on Government Operations with no further action recorded since its August 2025 referral, as of August 2026. observed
  9. Probable Michigan Legislature (Act 452 of 2004 index) — Michigan Senate Bill 360 — Would require notification to affected Michigan residents and to the Attorney General (for breaches affecting 100+ residents) within 45 days of determining a breach occurred, replacing the current 'without unreasonable delay' standard observed
  10. Probable Vote Smart (SB 360 synopsis) — Michigan Identity Theft Protection Act (MCL 445.72) — Requires notification to affected residents without unreasonable delay after discovering a security breach, unless determined not likely to cause substantial loss, injury or identity theft; no private right of action; no current AG notification duty observed
  11. Probable Michigan Legislature — Civil fines of up to $250 per failed notification, capped at $750,000 per breach event, apply under the ITPA. observed
  12. Uncertain databreachcost.com — Identity Theft Protection Act, MCL 445.72 — Civil fine of up to $250 per failed notification for knowing failure to provide required breach notification, reported by secondary sources as aggregating to a cap around $750,000 per breach event; the aggregate cap could not be confirmed against the primary statutory text this cycle. observed
  13. Probable WilmerHale — Eli Savit (D) defeated Doug Lloyd (R) in the Nov 3, 2026 Michigan Attorney General election; incoming-AG client alerts report expected expansion of consumer-protection enforcement into data privacy, algorithmic/dynamic pricing, and AI products aimed at minors once his term begins January 2027. 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), 69 claim(s) (69 category placement(s)), 43 source(s) in the cumulative register.

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

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 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 & Adequacydata localisation
Art. 49Cross-Border & Adequacytransfer impact assessment
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redresscollective redress and class actions
Art. 80Enforcement & Redressregulator powers and penalties
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redressregulator powers and penalties
Art. 83Enforcement & Redresscollective redress and class actions
Art. 84Enforcement & Redressregulator powers and penalties