Wisconsin breach notification lookup
Use this Wisconsin breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Wisconsin: 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 | Wis. Stat. § 134.98 | Link the decision record to the official citation |
| Deadline | Individual notice within a reasonable time, not to exceed 45 days after acquiring knowledge of the breach, subject to law-enforcement delay and measures needed to determine scope and restore system integrity; consumer-reporting-agency notice applies for 1,000+ individuals. | Sort multi-state response work by the shortest stated clock |
| Residents | Wisconsin individuals whose personal information was, or is reasonably believed to have been, acquired by an unauthorized person in a way that materially compromises security, confidentiality, or integrity and creates a material risk of identity theft or fraud. | Identify whether affected residents receive notice |
| Regulator | The reviewed Wisconsin statute does not create a routine Attorney General filing trigger; Wisconsin business guidance is provided through the Department of Agriculture, Trade and Consumer Protection, while consumer-reporting-agency notice is triggered at 1,000 or more individuals. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify all nationwide consumer reporting agencies when one incident requires notice to 1,000 or more individuals. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | Wisconsin requires notification of all nationwide consumer reporting agencies when a single incident requires notice to 1,000 or more individuals, and DATCP publishes guidance for businesses and consumers on data breaches. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Wisconsin fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
Wis. Stat. § 134.98 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
Wisconsin requires notification of all nationwide consumer reporting agencies when a single incident requires notice to 1,000 or more individuals, and DATCP publishes guidance for businesses and consumers on data breaches. 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 Wisconsin 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 Wisconsin, 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 Wisconsin 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 Wisconsin 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 Wisconsin?
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.