Minnesota breach notification lookup
Use this Minnesota breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Minnesota: statute citation, stated notification deadline, residents or regulators who may need notice, consumer-reporting-agency threshold, consumer-notice trigger, official source links, and the last verified date.
Last verified 2026-08-13. Not legal advice.
| Field | Verified value | Use in the incident file |
|---|---|---|
| Statute | Minn. Stat. § 325E.61 | Link the decision record to the official citation |
| Deadline | Resident notice in the most expedient time possible and without unreasonable delay, consistent with law-enforcement delay and scope/restoration needs; nationwide consumer-reporting-agency notice within 48 hours for more than 500 persons at one time. | Sort multi-state response work by the shortest stated clock |
| Residents | Minnesota residents whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorized person after discovery or notification of a security breach. | Identify whether affected residents receive notice |
| Regulator | The reviewed Minnesota breach-notification statute does not create a routine Attorney General filing trigger; the Minnesota Attorney General publishes consumer guidance and may enforce Minnesota consumer-protection laws where appropriate. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify all nationwide consumer reporting agencies within 48 hours after discovering the breach when notice is required for more than 500 persons at one time. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | Minnesota requires a business that must notify more than 500 persons at one time to notify all consumer reporting agencies that compile and maintain files on consumers on a nationwide basis within 48 hours of the discovery of the breach. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Minnesota fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
Minn. Stat. § 325E.61 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
Minnesota requires a business that must notify more than 500 persons at one time to notify all consumer reporting agencies that compile and maintain files on consumers on a nationwide basis within 48 hours of the discovery of the breach. The consumer trigger matters because the clock usually starts only after a legally meaningful incident analysis, not merely because an IT alert appeared.
The last verified date for this Minnesota lookup is 2026-08-13. Use that date as a prompt to refresh counsel review before making a live notification decision.
How to use it during an incident
Start with containment and evidence preservation, then identify affected resident states and compare the shortest stated deadline first.
A practical incident file should record discovery time, encryption status, systems involved, affected consumer count, vendor involvement, and the person responsible for counsel review.
For Minnesota, the WISP should say where the notification decision log lives, who contacts counsel, who checks the regulator portal, and who approves any consumer notice before it is sent.
This lookup pairs with the Incident Response Plan because the plan owns the workflow: intake, escalation, containment, preservation, notice analysis, communications, and final review.
How it fits the WISP
A WISP should not guess at state-law outcomes; it should make the breach-review path fast, documented, and source-linked.
Pair this lookup with the Minnesota WISP requirements page so the firm's written program names the state-aware incident path before an event happens.
Policywright keeps the breach clock separate from the policy packet: the lookup tells you what to review, while the generated packet assigns owners, evidence records, remediation steps, and review cadence.
Not legal advice. A qualified lawyer should confirm whether the incident facts meet a statutory definition, whether substitute notice or regulator notice applies, and whether another state or federal rule changes the timeline.
FAQ
Is this Minnesota lookup legal advice?
No. It is a source-linked lookup for incident planning and should be reviewed with qualified counsel before relying on it in a live notification decision.
What if affected residents live outside Minnesota?
Use the multi-state lookup page and include every state where affected residents may live. The comparison table sorts selected states by the shortest stated deadline first.
Does this replace the FTC Safeguards Rule notice analysis?
No. State notice review is separate from the federal Safeguards Rule and 16 CFR 314.4(j) analysis. A serious incident file should preserve both review tracks.