Law / United States / Minnesota

Minnesota

Minnesota has 1 local jurisdiction That local jurisdiction has law of its own, on a page of its own, listed below.

31 of 32 named instruments researched to a stage, across five of the ten areas of law we track: 29 in force and 2 not yet in force. As of .

When each starts26 of 31 carry a date, 5 do not. Earlier is before 2015.
Before 2015: 9 instruments (9 in force) earlier 2015: 0 instruments 2016: 0 instruments 2017: 0 instruments 2018: 0 instruments 2019: 0 instruments 2020: 0 instruments ’20 2021: 5 instruments (5 in force) 2022: 0 instruments 2023: 2 instruments (2 in force) 2024: 1 instrument (1 in force) 2025: 6 instruments (6 in force) ’25 2026: 1 instrument (1 in force) 2027: 2 instruments (2 not yet in force) ’27 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law 5
  2. Privacy law 18
  3. Scraping law 3
  4. Cybersecurity law 4
  5. Communications law not researched
  6. Content moderation law not researched
  7. Product and AI liability law not researched
  8. Digital accessibility law not researched
  9. Age gating law 1
  10. Reuse law

AI law5 instruments, 4 in force, 1 not yet in force

Research summary (272 words)

Minnesota diverges from the federal position, which has no general AI-generated content labeling duty, with four distinct outright prohibitions and one sector-specific human-oversight mandate, rather than a disclosure regime: a ban on disseminating a non-consented, election-injuring deep fake of a candidate; a paired civil and criminal ban on disseminating a non-consensual deep fake depicting intimate parts or a sexual act; a 2026 first-in-the-nation ban on nudification technology, tools that generate a fake nude image or video from a clothed photograph without the depicted person's consent; and a 2025 expansion of the child sexual abuse material statutes to reach an AI-generated depiction of an identifiable minor that is obscene, paired with a narrow platform immunity for that category alone.

None of Minnesota's enacted AI statutes impose a general duty to disclose that content is AI-generated; each is a targeted criminal or civil prohibition, or a sector-specific human-oversight rule.

A fifth instrument requires a clinician, not automated processing alone, to make an adverse determination in health insurance utilization review: House File 2500 and Senate File 1856, the two bills that would have enacted this duty directly, both stalled in committee without a floor vote, but the same duty reached the statute book through a conference committee substitute in House File 4188, an omnibus commerce policy bill enacted as 2026 Minnesota Session Law chapter 124, article 3, section 6, amending Minn. Stat. section 62M.09, effective .

A general-purpose AI chatbot disclosure bill (SF 1886) remains in a Senate committee with no floor vote in either chamber as of the date shown and is not catalogued here because it has not cleared a chamber.

AI prohibited practices

AI-Generated Child Sexual Abuse Material

Minn. Stat. §§ 617.246, subd. 1(f)(2)(iv), .247, .2471 (2025 c 35 art 4 ss 12-13; art 5 s 21)official text, Office of the Revisor of Statutes (revisor.mn.gov)

In force since . Binds public and private bodies.

What this law does

A 2025 amendment expanded Minnesota's definition of child sexual abuse material at section 617.246 to reach a visual depiction that has been created, adapted, or modified to appear that an identifiable minor is engaging in sexual conduct, including one created by generative artificial intelligence or other computer technology processing data-input prompts, where the depicted individual is indistinguishable from an actual minor and the material is obscene.

Because section 617.247's dissemination and possession offenses incorporate section 617.246's definition, this AI-generated category carries the same felony exposure as other child sexual abuse material: up to seven years and a $10,000 fine for dissemination (up to 15 years and $20,000 with an aggravating factor), and up to five years and a $5,000 fine for possession (up to ten years and $10,000 with an aggravating factor).

A companion immunity provision, section 617.2471, bars civil or criminal liability under sections 617.246 or 617.247 for material that qualifies as child sexual abuse material solely because it is an AI-generated depiction, from being imposed on an interactive computer service, an information or telecommunications service provider, or their employees, for actions taken to detect, report, or respond to such material, or for content provided by another person.

What it requires

Election Deepfake Prohibition and Candidate Forfeiture

Minn. Stat. § 609.771; § 211B.17, .18 (2023 c 58 s 2; 2024 c 112 art 2 ss 76-78)official text, Office of the Revisor of Statutes (revisor.mn.gov)

In force since . Binds public and private bodies.

What this law does

It is a crime to knowingly or recklessly disseminate a deep fake, or to enter a contract to disseminate one, without the depicted individual's consent, with intent to injure a candidate or influence an election result, within 90 days before a party nominating convention or after the start of absentee voting before a primary or general election. There is no disclosure safe harbor; the offense turns on lack of consent and electoral intent, not on whether the item is labeled synthetic.

A 2024 amendment added that a convicted candidate forfeits the nomination or office and is disqualified from appointment to another office, and armed the attorney general, a county or city attorney, the depicted individual, or an injured candidate with a civil action for injunctive or equitable relief.

What it requires

Nonconsensual Deepfake Sexual Imagery, Civil and Criminal Liability

Minn. Stat. §§ 604.32, 617.262 (2023 c 58 ss 1, 3)official text, Office of the Revisor of Statutes (revisor.mn.gov)

In force since . Binds public and private bodies.

What this law does

It is a crime under section 617.262 to intentionally disseminate a deep fake that realistically depicts a person's intimate parts, artificially generated intimate parts presented as the depicted individual's, or the depicted individual engaging in a sexual act, knowing or with reason to know the depicted individual did not consent, where the individual is identifiable.

The base offense is a gross misdemeanor; it becomes a felony punishable by up to three years and a $5,000 fine where an aggravating factor applies, including that the actor profited, ran a website for the purpose of disseminating the material, obtained it by hacking, or has a prior conviction under the chapter.

A parallel civil cause of action at section 604.32, enacted the same day, lets the depicted individual sue for general and special damages, disgorgement of the disseminator's profit, a civil penalty of up to $100,000, and injunctive relief, with a civil fine of up to $1,000 per day for violating an order under the section.

Both sections exempt dissemination for law-enforcement, medical-treatment, newsworthy, scientific, or legal-proceeding purposes, and section 617.262 immunizes interactive computer services and telecommunications providers for content provided by another person.

What it requires

Nudification Technology Prohibition

Minn. Stat. § 325E.91 (2026 c 72)enrolled bill text, Minnesota House of Representatives and Office of the Revisor of Statutes

In force since . Binds public and private bodies.

What this law does

A person who owns or controls a website, application, software, program, or other service must not allow a user to access, download, or use it to nudify an image or video of an identifiable individual, or nudify one on the user's behalf, and must not advertise or promote a service that does either.

Nudifying means altering or generating an image or video so that it depicts an identifiable individual's intimate part or so realistically appears to that a reasonable person would believe it belongs to that individual. An exemption applies where the service requires the user's own substantial technical or artistic skill to produce the result.

The attorney general may enforce the section and a person who violates it is subject to a civil penalty of up to $500,000 for each unlawful access, download, or use; an individual may also bring a civil action against the violator for compensatory damages of up to three times the actual damages sustained, punitive damages, injunctive relief, and attorney fees.

House File 1606 was enrolled as 2026 Minnesota Session Law chapter 72, presented to the governor and approved by the governor .

What it requires

AI sector rules

Utilization Review, AI-Only Adverse Determination Prohibition

Minn. Stat. § 62M.09, subd. 3(f) (2026 Minn. Laws ch. 124, art. 3, § 6)session law text, 2026 Minn. Laws ch. 124, art. 3, § 6, Office of the Revisor of Statutes (revisor.mn.gov)

Not yet in force. from , in 2 months It starts to bind on .

Binds private bodies.

What this law does

A 2026 amendment to the utilization review act adds paragraph (f) to section 62M.09, subdivision 3, barring a utilization review organization from using any form of automated processing alone, without a clinician review by an appropriate health professional as the rest of the subdivision already requires, when making an adverse determination on a health care service, admission, or extension of stay.

A utilization review organization under this chapter is a private entity, such as an insurance company, prepaid limited health service organization, or health plan company, rather than a state agency. The amendment reached enactment as section 6 of House File 4188, an omnibus commerce policy bill, after a conference committee substituted new language for the entire bill (a delete-everything amendment).

House File 2500, a stand-alone bill on the same subject, was introduced in 2025 and never advanced past its initial committee referral. Its companion, Senate File 1856, was amended in committee in 2026 but received no recommendation and no floor vote in either chamber. The House repassed the conference report 121-13 on , and the Senate 49-15 on ; the governor approved the act, filed as 2026 Minnesota Session Law chapter 124, on .

The amendment's own effective-date clause makes it effective , applying to health plans offered, sold, issued, or renewed on or after that date.

What it requires

Privacy law18 instruments, 18 in force

Research summary (518 words)

Minnesota's comprehensive private-sector privacy law is the Minnesota Consumer Data Privacy Act (MCDPA), codified at Minn. Stat. §§ 325M.10 to 325M.21 (the surrounding Chapter 325M also holds two unrelated statutes, an older internet-service-provider disclosure law and a separate social-media-manipulation act, so the MCDPA citation is narrower than the bare chapter number).

MCDPA took effect for most controllers, with postsecondary institutions regulated by the Office of Higher Education deferred to . MCDPA claws back a recording-derived biometric identifier the moment it is generated to identify a specific individual, follows the ordinary multi-state opt-in consent model for sensitive data rather than Maryland's outright sale ban, and gives consumers a distinctive right to a list of the specific third parties their data was disclosed to.

Breach notification is a separate, older statute, Minn. Stat. § 325E.61, using a reasonableness standard with no fixed numeric deadline. MCDPA's own 30-day cure opportunity has already sunset (), and MCDPA bars any private right of action, including through the general private-attorney-general mechanism in Minn. Stat. § 8.31.

The Minnesota Insurance Fair Information Reporting Act binds insurers, insurance agents and insurance-support organizations that collect, receive or maintain information in connection with insurance transactions that pertains to Minnesota residents. Section 60A.9853 requires a licensee of the Department of Commerce or the Department of Health to notify the commissioner of a cybersecurity event no later than five business days from a determination that one has occurred, when its criteria are met.

Section 72A.139, the Genetic Discrimination Act, bars a health plan company from requiring or requesting a genetic test of an individual or a blood relative in connection with the offer, sale or renewal of a health plan. Section 325F.995, the Genetic Information Privacy Act, requires a direct-to-consumer genetic testing company to obtain a consumer's express consent to collect, use, and disclose the consumer's genetic data.

Section 13.386 allows genetic information to be collected by a government entity or any other person only with the written informed consent of the individual, unless a law expressly provides otherwise. Section 181.974 bars an employer or employment agency from administering a genetic test, or requesting, requiring or collecting protected genetic information, as a condition of employment.

Section 325E.59 bars a person or entity, not including a government entity, from publicly posting or publicly displaying an individual's Social Security number in any manner. The Minnesota Health Records Act bars a provider, or a person who receives health records from a provider, from releasing a patient's health records without a signed and dated consent, specific authorization in Minnesota law, or a representation from a provider that holds a signed and dated consent.

Section 13.32, subdivision 13 bars a technology provider from selling, sharing or disseminating educational data, except as the section provides. Sections 325M.01 to 325M.09 bar an Internet service provider from knowingly disclosing personally identifiable information concerning a consumer, except as the sections allow.

Section 325I.02 makes a videotape service provider or videotape seller who knowingly discloses personally identifiable information concerning any consumer to any person liable to the consumer, except as the section allows.

Breach notification

Insurance data security law: notification of a cybersecurity event to the commissioner and to consumers

Minn. Stat. § 60A.9853Official Minnesota statute text, Office of the Revisor of Statutes, section 60A.9853

In force since . Binds private bodies.

What this law does

Section 60A.9853 requires each licensee to notify the commissioner of commerce or commissioner of health, whichever otherwise regulates the licensee, without unreasonable delay and no later than five business days from a determination that a cybersecurity event has occurred when the section's criteria are met.

One of the criteria is that the licensee reasonably believes the nonpublic information involved is of 250 or more consumers residing in Minnesota and that the event is one of which notice must be given to a government or supervisory body, or has a reasonable likelihood of materially harming a consumer or normal operations.

A licensee required to report to the commissioner must notify any consumer residing in Minnesota whose nonpublic information was or is reasonably believed to have been acquired by an unauthorized person where there is a reasonable likelihood of material harm, in the most expedient time possible and without unreasonable delay.

A licensee must treat a cybersecurity event in a system maintained by a third-party service provider, of which it has become aware, as it would under subdivision 1 unless the third-party service provider provides the notice. An assuming insurer must notify its affected ceding insurers and the commissioner of its state of domicile within three business days of making the determination that a cybersecurity event involving nonpublic information has occurred.

A licensee is a person licensed, authorized to operate or registered, or required to be, by the Department of Commerce or the Department of Health under the chapters the section lists. A licensee subject to and in compliance with Health Insurance Portability and Accountability Act (HIPAA) is considered to comply with section 60A.9853, subdivisions 3 to 5 if it submits a written statement certifying its compliance with HIPAA. A licensee that violates sections 60A.985 to 60A.9856 may be penalized in accordance with section 60A.052.

Section 60A.052 lets the commissioner impose a civil penalty as provided for in section 45.027, subdivision 6. Section 45.027, subdivision 6 lets the commissioner impose a civil penalty not to exceed $10,000 per violation upon a person who violates any law, rule or order related to the commissioner's duties unless a different penalty is specified. The session law that enacted the section makes it effective .

What it requires

Insurance data security law: records of cybersecurity events, kept five years and produced on the commissioner's demand

Minn. Stat. § 60A.9852, subd. 4Official Minnesota statute text, Office of the Revisor of Statutes, section 60A.9852

In force since . Binds private bodies.

What this law does

Under section 60A.9852, subdivision 4, a licensee must maintain records concerning all cybersecurity events for a period of at least five years from the date of the cybersecurity event and must produce those records upon demand of the commissioner. A licensee is any person licensed, authorized to operate, or registered, or required to be licensed, authorized, or registered by the Department of Commerce or the Department of Health under the chapters section 60A.985 lists.

A licensee that violates sections 60A.985 to 60A.9856 may be penalized in accordance with section 60A.052. Section 60A.052 lets the commissioner impose a civil penalty as provided for in section 45.027, subdivision 6. Section 45.027, subdivision 6 lets the commissioner impose a civil penalty not to exceed $10,000 per violation upon a person who violates any law, rule or order related to the commissioner's duties unless a different penalty is specified. The session law that enacted the section makes it effective .

What it requires

Insurance data security law: retention of documents disclosed to the commissioner about a cybersecurity event

Minn. Stat. § 60A.9855, subd. 4Official Minnesota statute text, Office of the Revisor of Statutes, section 60A.9855

In force since . Binds private bodies.

What this law does

Under section 60A.9855, subdivision 4, any document, material, or information disclosed to the commissioner under that section about a cybersecurity event must be retained and preserved by the licensee for five years. Subdivision 1 classifies the documents, materials and information a licensee furnishes under the listed sections as confidential, protected nonpublic, or both, and not subject to subpoena.

A licensee is any person licensed, authorized to operate, or registered, or required to be licensed, authorized, or registered by the Department of Commerce or the Department of Health under the chapters section 60A.985 lists. A licensee that violates sections 60A.985 to 60A.9856 may be penalized in accordance with section 60A.052. Section 60A.052 lets the commissioner impose a civil penalty as provided for in section 45.027, subdivision 6.

Section 45.027, subdivision 6 lets the commissioner impose a civil penalty not to exceed $10,000 per violation upon a person who violates any law, rule or order related to the commissioner's duties unless a different penalty is specified. The session law that enacted the section makes it effective .

What it requires

Minnesota breach notification

Minn. Stat. § 325E.61official Minnesota statute text, Minn. Stat. § 325E.61, Office of the Revisor of Statutes

In force since . Binds private bodies.

What this law does

Minnesota's breach notification duty, a separate and pre-existing chapter from MCDPA, was originally enacted by 2005 Minn. Laws ch. 167, section 1, and has since been amended by 2006 Minn. Laws ch. 212, article 1, sections 17 and 24, and ch. 233, sections 7 and 8. Section 1 of the 2005 act, which enacted the section, is effective , and the section is currently in force.

A person or business must disclose a breach of the security of the system, following discovery or notification of the breach, to any Minnesota resident whose unencrypted personal information was or is reasonably believed to have been acquired by an unauthorized person, made in the most expedient time possible and without unreasonable delay.

Unlike Maryland's or Tennessee's fixed-day deadlines, Minnesota uses a reasonableness standard with no numeric cap; a data maintainer that does not own the information must notify the owner immediately upon discovery.

What it requires

Comprehensive regime

Minnesota Consumer Data Privacy Act (MCDPA), general applicability

Minn. Stat. §§ 325M.10 to 325M.21official Minnesota statute text, Minn. Stat. Chapter 325M, Office of the Revisor of Statutes

In force since . Binds private bodies.

What this law does

MCDPA governs private-sector processing of Minnesota residents' personal data, enacted as Laws of Minnesota 2024, chapter 121, article 5. A controller must limit collection to what is adequate, relevant, and reasonably necessary for the disclosed processing purpose, and must obtain consent before processing for an undisclosed, incompatible secondary purpose.

The general effective date, , binds every controller except postsecondary institutions regulated by the Office of Higher Education, which are not required to comply until , per the statute's own history note.

What it requires

Data subject rights

Internet service provider customer information: limits on disclosure of personally identifiable information

Minn. Stat. §§ 325M.01 to 325M.09Official Minnesota statute text, Office of the Revisor of Statutes, sections 325M.01 to 325M.09

In force since . Binds private bodies.

What this law does

Sections 325M.01 to 325M.09 apply to Internet service providers in the provision of services to consumers in this state. An Internet service provider is a business or person who provides consumers authenticated access to, or presence on, the Internet by means of a switched or dedicated telecommunications channel on which the provider provides transit routing of Internet Protocol packets for and on behalf of the consumer.

An Internet service provider does not include the offering, on a common carrier basis, of telecommunications facilities or of telecommunications by means of these facilities. Except as sections 325M.03 and 325M.04 provide, an Internet service provider may not knowingly disclose personally identifiable information concerning a consumer of the provider.

An Internet service provider shall disclose personally identifiable information concerning a consumer to the consumer who is the subject of the information, upon written or electronic request and upon payment of a fee not to exceed the actual cost of retrieving the information.

Personally identifiable information is information that identifies a consumer by physical or electronic address or telephone number, as having requested or obtained specific materials or services from the provider, by the sites visited, or by the contents of the consumer's data-storage devices.

An Internet service provider may disclose personally identifiable information concerning a consumer to any person with the authorization of the consumer, or to any person if the disclosure is incident to the ordinary course of business of the provider. The Internet service provider must take reasonable steps to maintain the security and privacy of a consumer's personally identifiable information.

A consumer who prevails or substantially prevails in an action under sections 325M.01 to 325M.09 is entitled to the greater of $500 or actual damages. No class action may be brought under sections 325M.01 to 325M.09. The session law that enacted the sections makes article 1 effective .

The session law provides that article 1 expires on the effective date of federal legislation that preempts state regulation of the release of personally identifiable information by Internet service providers.

What it requires

Minnesota Consumer Data Privacy Act, consumer rights and profiling

Minn. Stat. § 325M.14official Minnesota statute text, Minn. Stat. Chapter 325M, Office of the Revisor of Statutes

In force since . Binds private bodies.

What this law does

MCDPA grants a Minnesota consumer the rights to confirm processing, access, correct, delete, port their personal data, and opt out of targeted advertising, sale, and certain profiling, with an appeal right for denials.

A consumer may also demand a list of the specific third parties a controller disclosed their personal data to, going further than the multi-state model's usual categories-only disclosure, and may opt out of automated profiling for decisions with legal or similarly significant effects, question such a decision, receive an explanation, and have it reevaluated if based on inaccurate data.

A controller must respond within 45 days of receipt, extendable once by 45 additional days, and must respond to an appeal within 45 days, extendable by 60 additional days.

What it requires

Minnesota Insurance Fair Information Reporting Act

Minn. Stat. §§ 72A.49 to 72A.505Official Minnesota statute text, Office of the Revisor of Statutes, sections 72A.49 to 72A.505

In force since . Binds public and private bodies.

What this law does

The Minnesota Insurance Fair Information Reporting Act is the short title of sections 72A.49 to 72A.505 of the Minnesota Statutes. The Act applies to an insurer, insurance agent or insurance-support organization that collects, receives or maintains information in connection with insurance transactions that pertains to Minnesota residents, or that engages in insurance transactions with applicants, individuals or policyholders who are Minnesota residents.

For the Act, an insurer includes a joint self-insurance plan or multiple employer trust regulated under chapter 60F, 62H, or section 471.617, subdivision 2. Section 471.617, subdivision 2 lets two or more statutory or home rule charter cities, counties, towns, school districts, watershed districts, watershed management organizations, or instrumentalities of them that together have more than 100 employees jointly self-insure for employee health benefits.

The Act does not apply to insurance transactions involving property and casualty insurance primarily for business or professional needs. Section 72A.494 requires each insurer or insurance agent to provide a notice relating to information practices to each applicant or policyholder.

Section 72A.494 exempts from the notice a group policy that is not individually underwritten and a renewal, reinstatement or change in benefits where no personal information is to be collected other than from the applicant, policyholder or public records.

On a written request after proper identification, an insurer, insurance agent or insurance-support organization must within 30 business days tell the individual the nature and substance of the personal information it holds, permit the individual to see and copy it, and disclose to whom it was disclosed within the previous two years.

Within 30 business days of a written request to correct, amend or delete personal information, the holder must correct, amend or delete the disputed portion or notify the individual of its refusal, the reasons and the right to appeal to the commissioner. After an adverse underwriting decision, the insurer or insurance agent responsible must provide in writing the specific reasons for the decision and a summary of the person's rights of access and correction.

An insurer, insurance agent or insurance-support organization may not disclose personal or privileged information about a person collected or received in connection with an insurance transaction without the person's authorization except as section 72A.502 allows.

An insurer, insurance agent or insurance-support organization that discloses personal or privileged information requiring the person's written authorization must notify the person in writing within ten days of the date the information was disclosed.

An insurer, insurance agent or insurance-support organization may not obtain information in connection with an insurance transaction by pretending to be someone else, pretending to represent a person, misrepresenting the true purpose of the interview or refusing to provide identification on request.

An insurer, insurance agent or insurance-support organization that violates the Act is liable to the aggrieved person to the same extent as civil remedies are allowed in section 13.08, subdivision 1 for violations of chapter 13 by a government body. Section 13.08, subdivision 1 makes a government entity liable, in the case of a willful violation, for exemplary damages of not less than $1,000 and not more than $15,000 for each violation.

Any person who knowingly and willfully obtains information about a person in violation of section 72A.493 is subject to a fine not to exceed $3,000 or imprisonment not to exceed 364 days, or both. The session law that enacted the Act makes sections 1 to 5 and 7 to 17 effective . The session law that enacted the Act makes the notice section effective .

What it requires

Enforcement supervision

Minnesota Consumer Data Privacy Act, Attorney General enforcement

Minn. Stat. § 325M.20official Minnesota statute text, Minn. Stat. Chapter 325M, Office of the Revisor of Statutes

In force since . Binds private bodies.

What this law does

The Minnesota Attorney General may bring a civil action to enforce MCDPA under the general false-advertising and consumer-protection statute, Minn. Stat. § 8.31, with a civil penalty of up to $7,500 per violation plus litigation costs and injunctive relief. MCDPA expressly bars any private right of action, including one brought under § 8.31's own private-attorney-general provision.

A discretionary warning-letter and 30-day cure opportunity existed but has already sunset, expiring ; the Attorney General may now sue directly without first offering a cure window.

What it requires

Sensitive categories

Educational data: technology providers and school-issued devices

Minn. Stat. § 13.32, subdivisions 13 to 15Official Minnesota statute text, Office of the Revisor of Statutes, section 13.32

In force. Binds public and private bodies.

What this law does

A technology provider is a person who contracts with a public educational agency or institution to provide a school-issued device for student use and who creates, receives or maintains educational data pursuant or incidental to the contract. A technology provider is subject to the provisions of section 13.05, subdivision 11.

Section 13.05, subdivision 11 makes data a private person collects under a government contract subject to chapter 13, and requires the private person to comply as if it were a government entity. A technology provider must not sell, share or disseminate educational data, except as the section provides or as part of a valid delegation or assignment of its contract with a public educational agency or institution.

A technology provider must not use educational data for any commercial purpose, including marketing or advertising to a student or parent. Within 90 days of the expiration of the contract, a technology provider must destroy or return to the public educational agency or institution all educational data created, received or maintained under the contract, unless renewal is reasonably anticipated.

A technology provider whose educational data are subject to a breach of the security of the data must disclose to the public educational agency or institution all information necessary to fulfill the requirements of section 13.055. A government entity or technology provider must not electronically access or monitor a school-issued device's location-tracking feature, its audio or visual features, or student interactions with it, except in the circumstances the subdivision lists.

A postsecondary institution is exempt from subdivisions 13 and 14, and the exemption extends to a technology provider for purposes of a contract with a postsecondary institution. Section 13.09 makes a person who willfully violates the provisions of chapter 13 guilty of a misdemeanor. The section of the session law that added the technology provider definition makes that section effective for the 2022-2023 school year and later.

Section 2 of that session law, which added subdivision 13 of section 13.32, makes that section effective for the 2022-2023 school year and later. Section 3 of that session law, which added subdivision 14 of section 13.32, makes that section effective for the 2022-2023 school year and later. Section 4 of that session law, which added subdivision 15 of section 13.32, makes that section effective for the 2022-2023 school year and later.

What it requires

Genetic Discrimination Act

Minn. Stat. § 72A.139Official Minnesota statute text, Office of the Revisor of Statutes, section 72A.139

In force since . Binds private bodies.

What this law does

Section 72A.139 may be cited as the Genetic Discrimination Act. A health plan company may not require or request that an individual or a blood relative take a genetic test, inquire whether one was taken or refused or what the results were, or take into consideration the fact or the results of a genetic test, in connection with the offer, sale or renewal of a health plan.

A life insurance company or fraternal benefit society that requires a genetic test to determine insurability must obtain the individual's written informed consent for the test. A life insurance company or fraternal benefit society must notify an individual of a genetic test result by notifying the individual or the individual's designated physician.

A life insurance company or fraternal benefit society may not require an individual to submit to a genetic test unless the insurer pays the cost of the test. A violation of section 72A.139 is subject to the investigative and enforcement authority of the commissioner, who must enforce the section. The session law that enacted the section makes it effective , and applicable to applications for coverage made on or after that date.

What it requires

Genetic Information Privacy Act: direct-to-consumer genetic testing companies

Minn. Stat. § 325F.995Official Minnesota statute text, Office of the Revisor of Statutes, section 325F.995

In force. Binds private bodies.

What this law does

Section 325F.995 is titled the Genetic Information Privacy Act. A direct-to-consumer genetic testing company is an entity that offers consumer genetic testing products or services directly to consumers, or that collects, uses or analyzes genetic data collected through such a product or service and provided to it by a consumer.

The section does not apply to protected health information collected by a covered entity or business associate, to a public or private institution of higher education, or to an entity owned or operated by one. A company must obtain a consumer's express consent to collect, use and disclose the consumer's genetic data, including separate express consent naming the recipient for each transfer to a person other than its vendors and service providers.

A company may not disclose genetic data to law enforcement or any other governmental agency without the consumer's express written consent unless the disclosure is made under a valid search warrant or court order. A company may not disclose a consumer's genetic data without the consumer's written consent to an entity offering health insurance, life insurance, disability insurance or long-term care insurance, or to the consumer's employer.

A company must develop, implement and maintain a comprehensive security program and measures to protect a consumer's genetic data against unauthorized access, use or disclosure. A company must provide a process for a consumer to access the consumer's genetic data, delete the consumer's account and genetic data, and request and obtain destruction of the consumer's biological sample.

A company must honor a consumer's revocation of consent as soon as practicable, but not later than 30 days after the consumer revokes it, and must destroy a biological sample within 30 days of receipt of revocation of consent to store the sample.

A contract between a company and a service provider must prohibit the service provider from retaining, using or disclosing any biological sample, extracted genetic material, genetic data or consumer identity information for any purpose other than the specific services in the contract. The commissioner of commerce may enforce the section under section 45.027.

Section 45.027, subdivision 6 lets the commissioner impose a civil penalty not to exceed $10,000 per violation upon a person who violates any law, rule or order related to the commissioner's duties unless a different penalty is specified.

What it requires

Genetic information held by government entities and other persons: written informed consent to collect, use, store and disseminate

Minn. Stat. § 13.386Official Minnesota statute text, Office of the Revisor of Statutes, section 13.386

In force since . Binds public and private bodies.

What this law does

Section 13.386 addresses the treatment of genetic information held by government entities and other persons. Genetic information is information about an identifiable individual derived from the presence, absence, alteration or mutation of a gene, or the presence or absence of a specific DNA or RNA marker, obtained from analysis of the individual's or a relative's biological information or specimen.

Genetic information also means medical or biological information collected from an individual about a particular genetic condition that is or might be used to provide medical care to the individual or the individual's family members. Unless a law expressly provides otherwise, genetic information about an individual may be collected by a government entity or any other person only with the written informed consent of the individual.

Genetic information may be used only for purposes to which the individual has given written informed consent, stored only for the period of time to which the individual has given written informed consent, and disseminated only with the individual's written informed consent or if necessary to accomplish the consented purposes.

A consent to disseminate genetic information must be signed and dated and, unless otherwise provided by law, is valid for one year or for a lesser period specified in the consent. Newborn screening activities conducted under sections 144.125 to 144.128 are subject to the consent rules of paragraph (a) of section 13.386, subdivision 3, and other programs and activities governed under section 144.192 are not.

The history of section 13.386 records that subdivision 3 was amended by chapter 82, section 3 of the 2013 session laws. The 2013 amendment of section 13.386, subdivision 3 took effect on . The 2013 amendment designated the existing text of section 13.386, subdivision 3 as paragraph (a). Section 13.09 makes a person who willfully violates the provisions of chapter 13 guilty of a misdemeanor.

The session law that added the section makes it effective , and applicable to genetic information collected on or after that date.

What it requires

Genetic testing in employment: limits on employers and employment agencies

Minn. Stat. § 181.974Official Minnesota statute text, Office of the Revisor of Statutes, section 181.974

In force. Binds public and private bodies.

What this law does

Section 181.974 governs genetic testing in employment. An employer is any person having one or more employees in Minnesota, and includes the state and its political subdivisions. Protected genetic information is information about a person's genetic test or about a genetic test of a blood relative of the person.

No employer or employment agency may directly or indirectly administer a genetic test or request, require or collect protected genetic information regarding a person as a condition of employment. No employer or employment agency may affect the terms or conditions of employment or terminate the employment of any person based on protected genetic information. No person may provide or interpret for any employer or employment agency protected genetic information on a current or prospective employee.

A person aggrieved by a violation may bring a civil action in which the court may award up to three times the actual damages, punitive damages, reasonable costs and attorney fees, and injunctive or other equitable relief. The history note of section 181.974 records its enactment by section 1 of chapter 154, Laws of 2001, and an amendment by article 13, section 20 of chapter 9, First Special Session 2001. The act that enacted section 181.974 was signed by the governor on .

Section 181.974 defines a genetic test as the analysis of human DNA, RNA, chromosomes, proteins, or certain metabolites in order to detect disease-related genotypes or mutations.

What it requires

Minnesota Consumer Data Privacy Act, sensitive data and biometric consent

Minn. Stat. §§ 325M.11, 325M.16official Minnesota statute text, Minn. Stat. Chapter 325M, Office of the Revisor of Statutes

In force since . Binds private bodies.

What this law does

MCDPA classifies data revealing racial or ethnic origin, religious beliefs, a mental or physical health condition or diagnosis, sexual orientation, or citizenship or immigration status; the processing of biometric data or genetic information to uniquely identify an individual; a known child's data; and precise geolocation data as sensitive data, processable only with the consumer's opt-in consent, the ordinary multi-state model rather than Maryland's outright sale ban.

"Biometric data" means data generated by automatic measurement of biological characteristics used to identify a specific individual, and it excludes a bare photograph, video, or audio recording, but claws that exclusion back the moment data generated from one is used to identify a specific individual.

What it requires

Minnesota Health Records Act

Minn. Stat. §§ 144.291 to 144.298Official Minnesota statute text, Office of the Revisor of Statutes, sections 144.291 to 144.298

In force. Binds public and private bodies.

What this law does

Sections 144.291 to 144.298 may be cited as the Minnesota Health Records Act. A provider is a person who furnishes health care services and is regulated under the chapters the section lists, a licensed home care provider, a health care facility licensed under chapter 144 or 144A, or a licensed assisted living facility.

A provider, or a person who receives health records from a provider, may not release a patient's health records without a signed and dated consent, specific authorization in Minnesota law, or a representation from a provider that holds a signed and dated consent. A consent to release health records is valid for one year or for a period specified in the consent or for a different period provided by Minnesota law, except as the section otherwise provides.

Upon request, a provider must supply a patient within 30 calendar days of a written request complete and current information concerning any diagnosis, treatment and prognosis of the patient. A provider must furnish copies of the patient's health record, at a reasonable cost to the patient, within 30 calendar days of receiving a written request.

A provider must give patients, in a clear and conspicuous manner, a written notice concerning practices and rights with respect to access to health records. Health records may be released to an external researcher solely for purposes of medical or scientific research only as section 144.295 provides. A health information exchange maintaining a record locator or patient information service must maintain an audit log of providers accessing information in the service.

A person who negligently or intentionally requests or releases a health record in violation of sections 144.291 to 144.297 is liable to the patient for compensatory damages caused by an unauthorized release, plus costs and reasonable attorney fees. A violation of sections 144.291 to 144.298 may be grounds for disciplinary action against a provider by the appropriate licensing board or agency. Section 144.335 was repealed by chapter 147, article 10, section 16 of the Laws of 2007.

Section 144.293, subdivision 7 was amended by chapter 127, article 1, section 29 of the Laws of 2026. The 2026 amendment of section 144.293, subdivision 7 removes the words "or the Health Data Institute under chapter 62J" from the exception to consent for release to the commissioner of health. Section 144.294, subdivision 2 was amended by chapter 121, article 8, section 2 of the Laws of 2026.

The amendment of section 144.294, subdivision 2 will replace the cross-reference to section 256B.0624, subdivision 2, paragraph (j) with section 245I.24, subdivision 2, paragraph (g) in the definition of a mental health crisis. The 2026 amendment of section 144.294, subdivision 2 takes effect , the effective date of the article that carries it.

What it requires

Use of Social Security numbers: limits on businesses

Minn. Stat. § 325E.59Official Minnesota statute text, Office of the Revisor of Statutes, section 325E.59

In force since . Binds public and private bodies.

What this law does

Section 325E.59 bars a person or entity, not including a government entity, from publicly posting or publicly displaying an individual's Social Security number in any manner. A person or entity may not print an individual's Social Security number on any card required for the individual to access products or services provided by the person or entity.

A person or entity may not require an individual to transmit the individual's Social Security number over the Internet unless the connection is secure or the number is encrypted. A person or entity may not require an individual to use the individual's Social Security number to access an Internet website unless a password or unique personal identification number or other authentication device is also required.

A person or entity may not print a number that it knows to be an individual's Social Security number on materials mailed to the individual, unless state or federal law requires the number to be on the document.

A person or entity may not assign or use a number as the primary account identifier that is identical to or incorporates an individual's complete Social Security number, except in conjunction with an employee or member retirement or benefit plan or human resource or payroll administration. A person or entity may not sell Social Security numbers obtained from individuals in the course of business.

A person or entity must restrict access to the individual Social Security numbers it holds so that only its employees, agents or contractors who require access in order to perform their job duties have access to the numbers.

Social Security numbers may be included in applications and forms sent by mail, including documents sent as part of an application or enrollment process, or to establish, amend, or terminate an account, contract, or policy, or to confirm the accuracy of the number, notwithstanding paragraph (a), clauses (1) to (5).

Section 325E.59 does not prevent the collection, use, or release of a Social Security number as required by state or federal law, for a purpose specifically authorized by a law that restricts use and release of information on individuals, or the use of a number for internal verification or administrative purposes. The section does not apply to documents that are recorded or required to be open to the public under chapter 13 or by other law.

For the section, a government entity has the meaning given in section 13.02, subdivision 7a, but does not include the Minnesota State Colleges and Universities or the University of Minnesota. The section applies only to the use of Social Security numbers on or after .

What it requires

Videotape service provider and videotape seller records: limits on disclosure of personally identifiable information

Minn. Stat. §§ 325I.01 to 325I.03Official Minnesota statute text, Office of the Revisor of Statutes, sections 325I.01 to 325I.03

In force. Binds private bodies.

What this law does

A videotape service provider is a person engaged in the business of rental of prerecorded videocassette tapes or similar audiovisual materials, or a person to whom a disclosure is made by a videotape service provider under section 325I.02, but only with respect to the information contained in the disclosure.

Personally identifiable information is information that identifies a person as having requested or obtained specific video materials or services from a videotape service provider or videotape seller. Except as subdivisions 2 and 3 provide, a videotape service provider or videotape seller who knowingly discloses personally identifiable information concerning any consumer to any person is liable to the consumer for the relief provided in section 325I.03.

To obtain a consumer's written informed consent to a disclosure, a videotape service provider or videotape seller must obtain a signed statement conforming to the notice contained in section 325I.02, subdivision 4.

A person subject to section 325I.02 shall destroy personally identifiable information as soon as practicable, but no later than one year from the date the information is no longer necessary for the purpose for which it was collected and there are no pending requests or orders for access to the information. A videotape service provider or videotape seller may not require a consumer to execute a consent as a condition of providing videotape goods or services to the consumer.

The public and private remedies in section 8.31 apply to violations of section 325I.02. Section 8.31, subdivision 3 entitles the attorney general, on behalf of the state, to sue for injunctive relief against a violation and to sue to recover a civil penalty in an amount determined by the court, not in excess of $25,000.

Section 8.31, subdivision 3a lets any person injured by a violation of the laws referred to in subdivision 1 bring a civil action and recover damages, together with costs and disbursements, including costs of investigation and reasonable attorney's fees. A consumer who prevails or substantially prevails in an action under section 325I.03 is entitled to a minimum of $500 in damages, regardless of the amount of actual damage proved, plus costs, disbursements and reasonable attorney fees.

What it requires

Scraping law3 instruments, 3 in force

Research summary (889 words)

Minnesota has two computer-crime offenses that can reach a crawler, and it defines authorization by statute. Computer or electronic data theft (Minn. Stat. § 609.89) punishes intentionally and without authorization or claim of right accessing a computer, system or network for the purpose of obtaining services or property, and accessing or copying electronic data without authorization or claim of right and then using, altering, transferring, retaining or publishing it. The loss sets only the penalty tier, the lowest being up to 90 days and a fine of up to $1,000.

Unauthorized computer access (§ 609.891) is narrower. It punishes intentionally and without authorization attempting to or penetrating a computer security system or electronic terminal. Section 609.87 defines a computer security system as a software program or computer device intended to protect the confidentiality and secrecy of data and information stored in or accessible through the computer system. An open page behind no security system has nothing to penetrate under this section.

Section 609.87, subdivision 2a, defines authorization as the owner's permission and lets the owner limit it by giving the user actual notice orally or in writing, by posting a written notice next to the computer, or by a notice displayed on or announced by the computer being used. A cease-and-desist letter is therefore written notice that limits authorization, and continuing after one is access without authorization under § 609.89.

Getting past a CAPTCHA, IP block or rate limit is access the owner has refused. Section 609.89 has no security-system element, so it reaches that conduct whether or not the barrier is a computer security system under § 609.891, and no Minnesota decision applies that definition to such a barrier. A crawler that collects a site's data has the purpose of obtaining property, which includes electronic data, and no harm or loss threshold conditions the offense.

Both offenses require that the actor act intentionally, and Minnesota defines intent to include knowledge of the facts set forth after that word (§ 609.02, subdivision 9), which here include that the access is without authorization. A crawler that reads an open page with no notice of any limit lacks that knowledge, so ordinary public crawling does not meet either offense, while a defeated barrier or a cease-and-desist letter supplies it.

No Minnesota statute or decision says whether an operator that serves a page to anyone has given permission for automated access, so whether a page's being public takes it outside the offenses is open.

Whether a robots.txt file, or terms of use that a site displays or a user accepted, is a notice displayed on or announced by the computer that limits authorization is also open. No Minnesota statute or decision gives robots.txt legal weight of its own, and no reported Minnesota appellate decision applies § 609.891 or § 609.89 to scraping or public-page access.

In Minnesota, assent to a contract is judged by a party's objective conduct rather than subjective intent. A federal court applying Minnesota law held that a click on a page stating that disputes go to arbitration represents assent to the contract, including the arbitration clause (Siebert v. Amateur Athletic Union of the United States, Inc., D. Minn. 2006).

Terms accepted at signup therefore bind, and terms shown only by a link bind only where the visitor's conduct objectively shows assent, which turns on notice of them. No Minnesota decision applies either rule to a crawler.

Trespass to chattels is an intentional tort in Minnesota under the Restatement (Second) of Torts (Herrmann v. Fossum, Minn. 1978). A federal court applying Minnesota law states that liability arises where the defendant dispossesses the possessor, impairs the chattel's condition, quality or value, or deprives the possessor of its use for a substantial period (Strei v. Blaine, D. Minn. 2014, drawing on Olson v. LaBrie, Minn. Ct. App.

2013, an unpublished decision), so a claim over server load needs impairment of the server or loss of its use for a substantial period.

The Minnesota Consumer Data Privacy Act excludes publicly available information from personal data, meaning information lawfully made available from government records or widely distributed media, or that a controller has a reasonable basis to believe was lawfully made available to the general public. The exclusion carries no exception for biometric data.

The Act applies to entities that do business in Minnesota or target its residents and meet a consumer-volume or revenue threshold, and separately bars a small business, as the federal Small Business Administration defines one, from selling a consumer's sensitive data without prior consent. It gives a consumer whose data is profiled for a decision with legal or similarly significant effect the right to question the result and to be told why it resulted, and it creates no private right of action.

Copyright, text-and-data-mining and database rights add nothing to the federal position. Copyright is exclusively federal law, whether commercial mining is fair use under 17 U.S.C. § 107 is unsettled, and Minnesota law recognizes no mining opt-out.

No Minnesota statute specifically governs the data used to train an AI model. The State's enacted AI measures concern election deepfakes, sexual deepfakes, nudification tools, AI-generated child sexual abuse material and health-insurance utilization review, and their text does not reach training data, nor does the text of the bills introduced on disclosing AI interaction or on AI in official government records.

Computer misuse

Minnesota Unauthorized Computer Access, penetrating a computer security system

Minn. Stat. § 609.891official text, Office of the Revisor of Statutes (revisor.mn.gov)

In force since . Binds public and private bodies.

What this law does

Subdivision 1 provides that a person is guilty of unauthorized computer access if the person intentionally and without authorization attempts to or does penetrate a computer security system or electronic terminal, so the offense reaches an attempt as well as a completed penetration, and subdivision 4 makes a violation a misdemeanor.

This ties the offense to penetrating a computer security system rather than to access without permission as such, so a plain crawl of a public page behind no security system would not, on this section's own terms, appear to fall within it.

The grade rises to a gross misdemeanor where a violation creates a risk to public health and safety, compromises the security of data that are not public data, or gains access to personal data, and to a felony where it creates a grave risk of causing the death of a person. Further tiers apply to opening a panel or access door of an electronic terminal, including to place a device that captures access device information.

What it requires

Minnesota computer or electronic data theft, with the definition of authorization

Minn. Stat. §§ 609.87, 609.89official text, Office of the Revisor of Statutes (revisor.mn.gov)

In force since . Binds public and private bodies.

What this law does

Section 609.89, subdivision 1, makes it computer or electronic data theft to intentionally and without authorization or claim of right access, or cause to be accessed, any computer, computer system, computer network or part of one for the purpose of obtaining services or property. The same subdivision reaches intentionally and without authorization or claim of right accessing or copying computer software or electronic data and then using, altering, transferring, retaining or publishing it.

It also reaches intentionally retaining copies of computer software or electronic data beyond the individual's authority. Section 609.89 has no computer-security-system element; subdivision 1 turns on access without authorization or claim of right. Section 609.87, subdivision 6, defines property to include electronically processed or produced data and information contained in a computer or computer software in either machine or human readable form.

Subdivision 7 of the same section defines services to include computer time, data processing and storage functions. Section 609.87, subdivision 2a, defines authorization to include access with the permission of the owner of the computer, computer system, computer network, computer software or other property.

The owner may limit authorization by giving the user actual notice orally or in writing, by posting a written notice in a prominent location adjacent to the computer being used, or by using a notice displayed on or announced by the computer being used.

The penalty depends on the loss to the owner, the owner's agent or lessee: up to ten years in prison or a fine of up to $50,000, or both, for a loss over $2,500, up to five years or a fine of up to $10,000, or both, for a loss of more than $500 but not more than $2,500, and up to 90 days or a fine of up to $1,000, or both, in all other cases.

What it requires

Personal data

Minnesota Consumer Data Privacy Act (MCDPA), publicly available information exemption and profiling explanation right

Minn. Stat. §§ 325M.10-325M.14 (2024 c 121, art. 5)official text, Office of the Revisor of Statutes (revisor.mn.gov)

In force since . Binds private bodies.

What this law does

Personal data excludes deidentified data or publicly available information, defined as information lawfully made available from government records or widely distributed media, or that a controller reasonably believes was lawfully made available to the public.

The Act applies to an entity doing business in Minnesota or targeting Minnesota residents that in a calendar year controls or processes personal data of 100,000 consumers or more, or derives more than 25% of gross revenue from selling personal data and processes or controls data of 25,000 consumers or more.

Section 325M.14(g) grants an unusual right: where personal data is profiled in furtherance of a decision with legal or similarly significant effect, 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.

Section 325M.20(d) expressly states the Act establishes no private right of action for a violation of its provisions or any other law; enforcement is by the Attorney General, with civil penalties up to $7,500 per violation. Effective , except that postsecondary institutions regulated by the Office of Higher Education have until .

What it requires

Cybersecurity law4 instruments, 4 in force

Research summary (814 words)

Minnesota has no enacted statute setting security requirements a connected device or software product must meet to be placed on the market, comparable to California's or Oregon's connected-device statutes, and no bill of that kind is before the 94th Legislature (2025-2026 biennium); this is a researched absence rather than a gap in coverage.

The state's incident-reporting statute, Minn. Stat. section 16E.36 (Laws 2024, chapter 123, article 17, section 24), binds public agencies, defined to include state agencies, local governments, school districts, charter schools, intermediate districts, cooperative units, and public postsecondary institutions: the head of or decision-making body for a public agency must report a cybersecurity incident that impacts it to the commissioner of Minnesota IT Services within 72 hours of identifying the incident.

A government contractor, defined narrowly as an entity under contract with a public agency that has access to or hosts that agency's network, systems, applications, or information, has a parallel duty to report an incident to the public agency itself, not to the Bureau, within the same 72 hours, when the incident impacts that agency. The section's duties on public agencies and their contractors are filed as a row of its own with no activity flag.

Minnesota separately adopted the NAIC Insurance Data Security Model Law at Minn. Stat. sections 60A.985 to 60A.9858 (enacted 1Sp2021 chapter 4, article 3, sections 5 and 6), which requires an entity licensed, authorized, or registered by the Department of Commerce or the Department of Health under the state's insurance chapters to develop, implement, and maintain a written information security program based on a risk assessment, covering access controls, encryption, multifactor authentication, oversight of third-party service providers, and board reporting, and to notify the commissioner of a cybersecurity event.

Its program and notice duties are filed as rows of their own.

Minnesota's only general reasonable-security duty that is not sector-gated to insurance sits inside the Minnesota Consumer Data Privacy Act itself, Minn. Stat. section 325M.16, subdivision 2, paragraph (c), which requires a controller to establish, implement, and maintain reasonable administrative, technical, and physical data security practices to protect the confidentiality, integrity, and accessibility of personal data; that is the comprehensive privacy regime's own security-of-processing clause, already this jurisdiction's privacy-topic finding, and is not repeated as a row here.

A second, older and narrower security duty sits at Minn. Stat. section 325M.05, part of the 2002 Internet Privacy Act (Minn. Stat. sections 325M.01 to 325M.09), a standalone statute that shares its chapter number with the unrelated Consumer Data Privacy Act only by codification accident: it requires that an Internet service provider take reasonable steps to maintain the security and privacy of a consumer's personally identifiable information.

The Act defines an Internet service provider narrowly as a business that provides a consumer authenticated access to, or presence on, the Internet over a switched or dedicated telecommunications channel and that itself routes Internet Protocol packets on the consumer's behalf, excluding a common carrier's offering of telecommunications facilities; the duty is filed as a row of its own, flagged for a telecommunications service.

Every section of the 2002 Act, including section 325M.05, carries a sunset clause tying its expiration to the effective date of federal legislation that preempts state regulation of an Internet service provider's release of personal information; no such federal legislation has been enacted, and the Office of the Revisor of Statutes continues to publish the Act, including section 325M.05, as current law.

Minnesota's breach-notification statute, Minn. Stat. section 325E.61, is this jurisdiction's privacy-topic finding and is not restated here. Because no instrument described above binds a private actor on any activity this corpus's vocabulary reaches, there is no enforcement record to report against this topic in Minnesota.

Beginning , the head of or the decision-making body for a public agency must report a cybersecurity incident that impacts the public agency to the commissioner. A government contractor or vendor that provides goods or services to a public agency must report a cybersecurity incident to the public agency if the incident impacts the public agency.

The report must be made within 72 hours of when the public agency or government contractor reasonably identifies or believes that a cybersecurity incident has occurred. Each licensee must develop, implement, and maintain a comprehensive written information security program based on its risk assessment, with administrative, technical, and physical safeguards for nonpublic information and its information system.

By April 15 of each year, an insurer domiciled in Minnesota must certify in writing to the commissioner that it complies with section 60A.9851. A licensee must notify the commissioner of commerce or commissioner of health, whichever regulates it, without unreasonable delay and no later than five business days from a determination that a cybersecurity event has occurred when either of two criteria is met.

An Internet service provider must take reasonable steps to maintain the security and privacy of a consumer's personally identifiable information.

Sector security regimes

Minnesota Insurance Data Security Act, information security program and investigation of a cybersecurity event

Minn. Stat. sections 60A.985, 60A.9851, 60A.9852 (Minnesota Insurance Data Security Act)Text of Minnesota Statutes sections 60A.985 to 60A.9852 and 60A.9856 from the Office of the Revisor of Statutes

In force since . Binds private bodies.

What this law does

Each licensee must develop, implement, and maintain a comprehensive written information security program based on its risk assessment, with administrative, technical, and physical safeguards for nonpublic information and its information system.

A licensee is a person licensed, authorized to operate, or registered, or required to be licensed, authorized, or registered, by the Department of Commerce or the Department of Health under chapters 59A to 62M, 62Q to 62V, and 64B to 79A. Each licensee must establish a written incident response plan designed to promptly respond to and recover from a cybersecurity event that compromises nonpublic information, its information systems, or the continuing functionality of its business or operations.

A licensee must require a third-party service provider to implement appropriate administrative, technical, and physical measures to protect the information systems and nonpublic information that the provider can access or holds. By April 15 of each year, an insurer domiciled in Minnesota must certify in writing to the commissioner that it complies with section 60A.9851. If a licensee learns that a cybersecurity event has or may have occurred, it must conduct a prompt investigation.

A licensee must maintain records concerning all cybersecurity events for at least five years from the date of the event and produce them on the commissioner's demand. A licensee with fewer than 25 employees is exempt from sections 60A.9851 and 60A.9852. A licensee subject to and in compliance with Health Insurance Portability and Accountability Act (HIPAA) is considered to comply with sections 60A.9851 and 60A.9852 if it submits a written statement certifying its compliance with HIPAA.

Licensees had one year from to implement section 60A.9851, subdivisions 1 to 5 and 7 to 9, and two years to implement subdivision 6. A violation of sections 60A.985 to 60A.9856 may be penalized in accordance with section 60A.052.

What it requires

Security baseline statutes

Minnesota Internet Privacy Act, Internet service provider duty to maintain the security of consumer information

Minn. Stat. section 325M.05 (Laws 2002, chapter 395, article 1, section 5)Text of Minnesota Statutes sections 325M.01, 325M.05, 325M.07 and 325M.09 from the Office of the Revisor of Statutes

In force since . Binds private bodies.

What this law does

An Internet service provider must take reasonable steps to maintain the security and privacy of a consumer's personally identifiable information. An Internet service provider is a business or person who provides consumers authenticated access to, or presence on, the Internet by means of a switched or dedicated telecommunications channel on which the provider provides transit routing of Internet Protocol packets for and on behalf of the consumer.

The definition does not include the offering, on a common carrier basis, of telecommunications facilities or of telecommunications by means of these facilities. A consumer is a person who agrees to pay a fee to an Internet service provider for access to the Internet for personal, family, or household purposes and who does not resell access.

The provider is not liable for actions that would violate section 609.88, 609.89, or 609.891 if it does not participate in, authorize, or approve the actions. A consumer who prevails or substantially prevails in an action brought under sections 325M.01 to 325M.09 is entitled to the greater of $500 or actual damages. No class action may be brought under sections 325M.01 to 325M.09.

It is a defense that the defendant has established and implemented reasonable practices and procedures to prevent violations of sections 325M.01 to 325M.09. Sections 325M.01 to 325M.09 apply to Internet service providers in the provision of services to consumers in Minnesota. Article 1 of chapter 395 took effect and expires on the effective date of federal legislation that preempts state regulation of the release of personally identifiable information by Internet service providers.

What it requires

Vulnerability and incident reporting

Minnesota Insurance Data Security Act, notification of a cybersecurity event to the commissioner

Minn. Stat. section 60A.9853 (Minnesota Insurance Data Security Act)Text of Minnesota Statutes section 60A.9853 from the Office of the Revisor of Statutes

In force since . Binds private bodies.

What this law does

A licensee must notify the commissioner of commerce or commissioner of health, whichever regulates it, without unreasonable delay and no later than five business days from a determination that a cybersecurity event has occurred when either of two criteria is met.

The first criterion is that Minnesota is the licensee's state of domicile, for an insurer, or home state, for a producer, and the event has a reasonable likelihood of materially harming a consumer residing in Minnesota or any part of the licensee's normal operations.

The second criterion is that the licensee reasonably believes the nonpublic information of 250 or more consumers residing in Minnesota is involved and either notice is owed to a government or supervisory body or the event has a reasonable likelihood of materially harming a Minnesota consumer or part of the licensee's normal operations.

A licensee has a continuing obligation to update and supplement its notifications to the commissioner concerning material changes to previously provided information. An assuming insurer must notify its affected ceding insurers and the commissioner of its state of domicile within three business days of making the determination that a cybersecurity event has occurred.

A licensee required to report to the commissioner must also notify a Minnesota consumer whose nonpublic information was or is reasonably believed to have been acquired by an unauthorized person where there is a reasonable likelihood of material harm.

What it requires

Minnesota cybersecurity incident reporting by public agencies and government contractors

Minn. Stat. section 16E.36 (Laws 2024, chapter 123, article 17, section 24)Text of Minnesota Statutes section 16E.36 from the Office of the Revisor of Statutes

In force since . Binds public and private bodies.

What this law does

Beginning , the head of or the decision-making body for a public agency must report a cybersecurity incident that impacts the public agency to the commissioner. A government contractor or vendor that provides goods or services to a public agency must report a cybersecurity incident to the public agency if the incident impacts the public agency.

The report must be made within 72 hours of when the public agency or government contractor reasonably identifies or believes that a cybersecurity incident has occurred. The section defines a public agency to include school districts, charter schools, intermediate districts, cooperative units under section 123A.24, subdivision 2, and public postsecondary education institutions.

The commissioner must coordinate with the superintendent of the Bureau of Criminal Apprehension to promptly share reported cybersecurity incidents. The cyber incident reporting system must securely accept a cybersecurity incident notification from any individual or private entity, whether or not the entity is a public agency or government contractor.

What it requires

Age gating law1 instrument, 1 not yet in force

Research summary (190 words)

Minnesota enacted the STOP HARMS from Addictive Social Media Act as part of House File 4138, signed , which will require covered social media platforms to estimate users' ages, obtain verifiable parental consent for accounts they must treat as belonging to a child, default to the most private settings, and disable addictive interface features such as infinite scroll and autoplay for children, effective .

The Act includes a private right of action for children and parents in addition to Attorney General enforcement as a deceptive trade practice. A separate bill that would require anonymous age verification for websites with material harmful to minors (HF 1434, companion SF 2105) has not advanced past committee, so Minnesota has no adult content age verification, app store age verification, or comprehensive design code law.

A related 2025 law, Minn. Stat. 325M.335, requires a mental health warning label on social media platforms effective ; it applies to users of all ages rather than gating by age, and the state has agreed not to enforce it while NetChoice's First Amendment challenge (NetChoice v. Ellison, D. Minn. No. 0:26-cv-2405) is pending.

Social media and minors

HF 4138 (2026), STOP HARMS from Addictive Social Media Act

Minn. Stat. §§ 325M.33, 325M.40 (2026 Minn. Laws ch. 111)official session law text, Minnesota Revisor of Statutes

Not yet in force. from , in 8 months It starts to bind on .

Binds private bodies.

What this law does

Requires a covered social media platform, as the Act defines that term in subdivision 1, to estimate a new account holder's age after 25 hours of use within six months, treating the user as a child (age 15 or younger) unless it can conclude with 80 percent confidence the user is 16 or older, rising to a 90 percent confidence threshold at 50 hours of use.

Child accounts require verifiable parental consent, must default to the most private settings, and may not display addictive interface features such as infinite scroll, autoplay, push notifications, or targeted advertising.

What it requires

Where nothing was found1 area of law

These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.

Reuse law

Minnesota has no state statute creating a press-publisher neighbouring right, a platform-to-publisher bargaining code, or a state-specific text-and-data-mining exception; the federal position (17 U.S.C. §§ 107, 301, and the hiQ v. LinkedIn and hot-news case line already catalogued at the national level) governs news aggregation in the state.

Minnesota Statutes chapter 325D (Minnesota antitrust law) contains no publisher-bargaining or collective-negotiation carve-out comparable to the federal Journalism Competition and Preservation Act, and no Minnesota appellate decision has been located recognizing a state common-law hot-news misappropriation claim for time-sensitive news content of the kind some other states allow under Minnesota's general unfair-competition statute, chapter 325D. No Minnesota bill comparable to California's AB 886 or the federal JCPA has been identified in the legislature's bill-search tools.

As of .

Case law

  • No current case law for Minnesota AI law
  • No current case law for Minnesota privacy law
  • No current case law for Minnesota scraping law
  • No current case law for Minnesota cybersecurity law
  • No current case law for Minnesota communications law
  • No current case law for Minnesota content moderation law
  • No current case law for Minnesota product and AI liability law
  • No current case law for Minnesota digital accessibility law
  • No current case law for Minnesota age gating law
  • No current case law for Minnesota reuse law

Reporting clocks that run here20 instruments

The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Minnesota comes first, then the law of the bodies above it that applies here.

Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.

1 hour
Incident notificationsecurity law
4 hours
Incident notificationsecurity law
8 hours
Incident notificationsecurity law
36 hours
48 hours
Breach notificationprivacy law
4 business days
Incident notificationsecurity law
7 business days
Breach notificationprivacy law
30 days
Incident notificationsecurity law
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
60 days
Breach notificationprivacy law
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.

The law of Minnesota

48 hours

Minnesota breach notification

Minn. Stat. § 325E.61privacy law, in force since

The sentences the clocks are read from

Disclose a breach of the security of the system to an affected Minnesota resident in the most expedient time possible and without unreasonable delay. Minnesota sets no fixed numeric-day cap on notice to residents, unlike several peer states.

If you discover circumstances requiring notification of more than 500 persons at one time, also notify, within 48 hours, every nationwide consumer reporting agency of the timing, distribution, and content of the notices (Minn. Stat. 325E.61, subd. 2).

Notify the data owner immediately upon discovering a breach if you maintain, but do not own, the affected data.

3 business days5 business days

Insurance data security law: notification of a cybersecurity event to the commissioner and to consumers

Minn. Stat. § 60A.9853privacy law, in force since

The sentences the clocks are read from

If you are a licensee of the Department of Commerce or the Department of Health, notify the commissioner who regulates you without unreasonable delay and no later than five business days from a determination that a cybersecurity event has occurred, when this state is your state of domicile (insurer) or home state (producer) and the event has a reasonable likelihood of materially harming a Minnesota consumer or part of your normal operations, or when you reasonably believe the nonpublic information involved is of 250 or more Minnesota consumers and the event must be reported to another government or supervisory body or has a reasonable likelihood of that harm.

If you are required to report to the commissioner, notify each Minnesota consumer whose nonpublic information was or is reasonably believed to have been acquired by an unauthorized person where there is a reasonable likelihood of material harm, in the most expedient time possible and without unreasonable delay, and send the commissioner a copy of the notice.

If you are an assuming insurer with no direct contractual relationship with the affected consumers, notify your affected ceding insurers and the commissioner of your state of domicile within three business days of determining that a cybersecurity event has occurred.

72 hours

Minnesota cybersecurity incident reporting by public agencies and government contractors

Minn. Stat. section 16E.36 (Laws 2024, chapter 123, article 17, section 24)security law, in force since

The sentences the clocks are read from

If you are a public agency, report a cybersecurity incident that impacts you to the commissioner within 72 hours of when you reasonably identify or believe that the incident has occurred, beginning .

If you are a government contractor or vendor that provides goods or services to a public agency, report a cybersecurity incident to that public agency within 72 hours of when you reasonably identify or believe that it has occurred, if the incident impacts the agency.

3 business days5 business days

Minnesota Insurance Data Security Act, notification of a cybersecurity event to the commissioner

Minn. Stat. section 60A.9853 (Minnesota Insurance Data Security Act)security law, in force since

The sentences the clocks are read from

Notify the commissioner of commerce or commissioner of health, whichever regulates you, without unreasonable delay and no later than five business days after you determine that a cybersecurity event has occurred, when Minnesota is your state of domicile (insurer) or home state (producer) and the event has a reasonable likelihood of materially harming a Minnesota consumer or part of your normal operations, or when you reasonably believe the nonpublic information of 250 or more Minnesota consumers is involved and notice is owed to a government or supervisory body or the event has a reasonable likelihood of that harm (60A.9853, subd.

1).

If you are an assuming insurer, notify your affected ceding insurers and the commissioner of your state of domicile within three business days of determining that a cybersecurity event has occurred (60A.9853, subd. 5).

The law of the United States, which applies in Minnesota

1 hour4 hours8 hours24 hours

NRC cyber security event notifications by nuclear power plant licensees

NRC cyber security event notifications, 10 CFR 73.77security law, in force since

The sentences the clocks are read from

Notify the NRC Headquarters Operations Center via the Emergency Notification System within one hour after discovery of a cyberattack that adversely impacted safety-related or important-to-safety functions, security functions, or emergency preparedness functions (including offsite communications), or that compromised support systems and equipment resulting in adverse impacts to those functions.

Also notify within one hour after discovery of a cyberattack that adversely impacted the safety, security, and emergency preparedness functions performed by digital assets described in 10 CFR 73.77(a)(1)(ii).

Notify the NRC Headquarters Operations Center within four hours after discovery of a cyberattack that could have caused such an adverse impact, after discovery of a suspected or actual cyberattack initiated by personnel with physical or electronic access to the systems in scope, or after notifying a local, State, or other Federal agency of an event related to your cyber security program that does not otherwise require notification.

Notify the NRC Headquarters Operations Center within eight hours after receipt or collection of information regarding observed behavior, activities, or statements that may indicate intelligence gathering or pre-operational planning related to a cyberattack against the systems in scope.

Use the site corrective action program to record vulnerabilities, weaknesses, failures and deficiencies in your cyber security program, and the notifications you make, within twenty-four hours of their discovery.

24 hours72 hours

Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA)

6 U.S.C. 681-681g (CIRCIA)security law, enacted, not yet in force

The sentences the clocks are read from

Once the final rule takes effect, report a covered cyber incident to the Agency not later than 72 hours after your organization reasonably believes that the covered cyber incident has occurred.

Once the final rule takes effect, report a ransom payment to the Agency not later than 24 hours after your organization makes the payment, even where the underlying ransomware attack is not itself a covered cyber incident.

Once the final rule takes effect, promptly submit an update to a previously submitted covered cyber incident report whenever substantial new or different information becomes available or a ransom payment is later made, continuing until your organization notifies the Agency that the incident has concluded and been fully mitigated and resolved, and preserve data relevant to the incident or payment under the procedures the final rule establishes.

24 hours5 business days30 days

SEC Regulation SCI: notification of SCI events to the Commission and to members

SEC Regulation SCI SCI event notices, 17 CFR 242.1002(b) and (c)security law, in force since

The sentences the clocks are read from

Upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, begin appropriate corrective action and notify the Commission of the SCI event immediately.

Within 24 hours of that conclusion, submit a written notification to the Commission, made on a good faith, best efforts basis, that describes the SCI event and the systems affected and, to the extent available, your assessment of the market participants potentially affected, the potential impact on the market, and the steps you have taken, are taking or plan to take.

If the SCI event is resolved and the investigation closed within 30 calendar days, submit a final written notification within five business days after resolution. If not, submit an interim written notification within 30 calendar days after the event, and a final one within five business days after resolution and closure.

36 hours

Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers

12 CFR Part 53 (OCC); 12 CFR Part 225, Subpart N (Federal Reserve Board); 12 CFR Part 304, Subpart C (FDIC)security law, in force since

The sentences the clocks are read from

If your organization is a banking organization, notify your primary federal banking regulator, the OCC, the Federal Reserve Board, or the FDIC, whichever supervises it, about a notification incident, as soon as possible and no later than 36 hours after your organization determines that a notification incident has occurred.

A notification incident is the subset of computer-security incidents that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, your ability to serve customers, a business line, or an operation whose failure would threaten the financial stability of the United States, so a computer-security incident that falls short of that threshold does not by itself start this clock.

If your organization is a bank service provider, notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible after your organization determines that it has experienced a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services provided to that banking organization for a period of four hours or more.

This duty carries a standard, as soon as possible, rather than a fixed number of hours to notify by, and that disruption threshold is what engages the duty rather than a period to notify within.

72 hours30 days

Artificial Intelligence Risk Management and Security Act of 2026

S. 5576, 119th Congressfrontier-model AI law, proposed

The sentence the clocks are read from

If you are a developer or provider of a frontier AI model, or an operator of critical infrastructure that uses an AI model to manage industrial control systems or other operational technologies, report any confirmed AI safety incident or AI security incident within 30 days of confirmation, and within 72 hours if the incident poses an imminent threat to national security, critical infrastructure or public safety.

72 hours

NCUA Cyber Incident Notification Requirements for Federally Insured Credit Unions

NCUA Cyber Incident Notification Requirements, 12 CFR 748.1(c)security law, in force since

The sentences the clocks are read from

If your organization is a federally insured credit union, notify the NCUA-designated point of contact of a reportable cyber incident by email, telephone, or another method the NCUA prescribes, so that the NCUA receives the notification as soon as possible and no later than 72 hours after your organization reasonably believes it has experienced a reportable cyber incident.

Where the reportable cyber incident is a disruption of business operations or unauthorized access to sensitive data facilitated through, or caused by, a compromise of a credit union service organization, cloud service provider, or other third-party data hosting provider, or by a supply chain compromise, the NCUA must receive the notification within 72 hours of your organization being notified by the third party if that is sooner.

72 hours30 days

Regulation S-P: incident response program and customer breach notice

17 CFR 248.30(a)(3) to (a)(5)privacy law, in force since

The sentences the clocks are read from

Send the notice as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred, delaying it only for the period the United States Attorney General specifies where the Attorney General determines that notice poses a substantial risk to national security or public safety (17 CFR 248.30(a)(4)(iii)).

Maintain written policies and procedures reasonably designed to require oversight, including through due diligence and monitoring, of service providers, including that a service provider notify you as soon as possible, and no later than 72 hours, after becoming aware of a breach in security resulting in unauthorized access to a customer information system it maintains (17 CFR 248.30(a)(5)(i)).

72 hours

SEC Regulation S-P: service provider oversight and 72-hour breach notice to the covered institution

SEC Regulation S-P service provider oversight and notice, 17 CFR 248.30(a)(5)security law, in force

The sentence the clocks are read from

Make those policies and procedures reasonably designed to ensure that each service provider takes appropriate measures to protect against unauthorized access to or use of customer information, and to notify you as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system the service provider maintains.

4 business days

SEC Cybersecurity Risk Management, Governance, and Incident Disclosure (Regulation S-K Item 106; Form 8-K Item 1.05)

17 CFR 229.106; 17 CFR 249.308 (Form 8-K Item 1.05)security law, in force since

The sentences the clocks are read from

If your organization is an Securities and Exchange Commission (SEC) reporting company, determine, without unreasonable delay after you discover a cybersecurity incident, whether the incident is material, and if it is, file a Form 8-K under Item 1.05 within four business days after you make that determination.

If the information called for in Item 1.05 is not determined or is unavailable when you file, state that in the filing and file an amendment to the Form 8-K within four business days after you determine it or it becomes available.

7 business days30 days

FCC CPNI breach notification rule

47 CFR 64.2011privacy law, in force

The sentences the clocks are read from

After you reasonably determine that a breach of your customers' CPNI has occurred, electronically notify the United States Secret Service and the Federal Bureau of Investigation through the central reporting facility as soon as practicable, and in no event later than seven business days (47 CFR 64.2011(b)).

Do not notify customers or disclose the breach where the relevant investigating agency directs you in writing not to, for an initial period of up to 30 days that the agency may extend (47 CFR 64.2011(b)(3)).

60 days

FTC Health Breach Notification Rule

16 CFR Part 318privacy law, in force since

The sentences the clocks are read from

If you are a vendor of personal health records (an entity that offers or maintains an electronic record of health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual) or a PHR related entity, notify each affected individual who is a citizen or resident of the United States, in plain language and without unreasonable delay, no later than 60 calendar days after you discover a breach of security of unsecured PHR identifiable health information.

Notify prominent media outlets serving a State or jurisdiction, without unreasonable delay and in no case later than 60 calendar days after you discover the breach, when the unsecured PHR identifiable health information of 500 or more of its residents is, or is reasonably believed to have been, acquired during the breach.

If you are a third party service provider, notify the official designated in a written contract by the vendor of personal health records or PHR related entity you serve (or else a senior official of that vendor or entity), without unreasonable delay and in no case later than 60 calendar days after you discover the breach; identify each customer of that vendor or entity whose unsecured PHR identifiable health information has been, or is reasonably believed to have been, acquired during the breach; and obtain acknowledgment that the notice was received.

60 days

HIPAA Breach Notification Rule

45 CFR Part 164, Subpart D (Sections 164.400-164.414)privacy law, in force since

The sentences the clocks are read from

Notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured protected health information.

For a breach of unsecured protected health information involving more than 500 residents of a State or jurisdiction, notify prominent media outlets serving that State or jurisdiction without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

If you are a business associate, notify the covered entity of a breach of unsecured protected health information without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

promptly

CFTC system safeguards: prompt notice to Commission staff of cyber security incidents and targeted threats

CFTC system safeguards notices, 17 CFR 39.18(g), 38.1051(e) and 37.1401(e)security law, in force since

The sentences the clocks are read from

If your organization is a derivatives clearing organization, notify staff of the Division of Clearing and Risk promptly of any hardware or software malfunction, security incident, or targeted threat that materially impairs, or creates a significant likelihood of material impairment of, automated system operation, reliability, security, or capacity, and of any activation of your business continuity and disaster recovery plan.

If your organization is a designated contract market, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and significant systems malfunctions and activations of your business continuity-disaster recovery plan.

If your organization is a swap execution facility, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and material system malfunctions and activations of your business continuity-disaster recovery plan.

immediately

Coast Guard Cybersecurity in the Marine Transportation System: reportable cyber incidents

Coast Guard reportable cyber incident reporting, 33 CFR 101.620(b)(7) and 101.615security law, in force since

The sentence the clocks are read from

Evidence of sabotage, subversive activity, or an actual or threatened cyber incident involving or endangering any vessel, harbor, port, or waterfront facility must be reported immediately to the Federal Bureau of Investigation, the Cybersecurity and Infrastructure Security Agency (for any cyber incident), and the Captain of the Port, or to their respective representatives.

Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.

Law in local jurisdictions1 with a page

Each has a page of its own; the number is how many of its instruments are researched to a stage.

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

This page covers the instruments LexLint has researched to a stage. Instruments named in the law library but not yet researched are counted in the head and are not listed here. Every entry carries its own primary source on its note page. This is a research index, not legal advice.