If personal information your business holds is acquired by an unauthorized person, Wisconsin law requires you to notify each affected person within a reasonable time, not to exceed 45 days after you learn of it. The rule is Wis. Stat. § 134.98. The 45-day clock is short, and most of it gets used up working out what was taken, which is why the businesses that handle a breach well are the ones with logs, backups and a response plan in place before anything happens. We are a managed IT provider in West Bend, and this guide covers the law in plain terms and the technical groundwork that makes meeting it realistic.
This is general information for business owners, not legal advice. When an incident happens, your attorney decides whether notice is required in your specific facts.
TL;DR
- Wisconsin requires notice to affected individuals within a reasonable time, not more than 45 days after you learn personal information was acquired without authorization (Wis. Stat. § 134.98).
- If one incident requires notice to 1,000 or more people, you must also notify the nationwide consumer reporting agencies.
- Encrypted, redacted or unreadable data is outside the definition of personal information, so strong encryption can change your obligations.
- Wisconsin has no state-regulator reporting requirement in the statute, but a missed notice can be used as evidence of negligence.
- The 45 days are won or lost on preparation: knowing what data you hold, where it lives and what your logs can prove.
Table of Contents
- What Wisconsin's breach law requires
- Who is covered
- What counts as personal information
- What triggers the duty to notify
- What the notice must say and how to send it
- Consequences of missing the deadline
- A worked example: how 45 days disappear
- Build the technical groundwork before an incident
- Industry notes
- Perspective
- How we can help
- FAQ
- Sources
What Wisconsin's breach law requires
Section 134.98 is Wisconsin's data breach notification statute. According to the Wisconsin Department of Agriculture, Trade and Consumer Protection (DATCP), it generally applies to businesses operating in Wisconsin and maintaining personal information about Wisconsin residents. When that information is acquired without authorization, the business must notify the affected individuals within a reasonable time, not to exceed 45 days. The statute measures that time from when the entity learns of the acquisition. Reasonableness takes into account the number of notices and the communication methods available (Wis. Stat. § 134.98).
Three duties follow:
- Notify each affected individual. The notice goes by mail or by a method you have previously used to communicate with that person.
- Notify the credit reporting agencies when the scale is large. If a single incident requires notice to 1,000 or more individuals, you must tell all nationwide consumer reporting agencies, without unreasonable delay, about the timing, distribution and content of the notices.
- Tell the data owner if you only hold the data. A third party that stores data for someone else, without a contract covering the situation, must notify the owner as soon as practicable.
The 45-day window is among the shortest in the country. A Wisconsin Legislative Research Bureau policy paper counts Wisconsin among nine states with the shortest time limit, and a 2026 50-state survey lists it among ten states with a fixed 45-day numeric deadline.
Who is covered
The law reaches further than many owners expect. DATCP lists these covered entities:
- Businesses conducting business in Wisconsin and maintaining personal information
- Businesses that license personal information in the state
- Businesses that maintain depository accounts for Wisconsin residents or lend money to them
- State government bodies, cities, villages, towns and counties
Out-of-state companies are not excused. An entity that maintains or licenses personal information in Wisconsin has a parallel duty to notify each affected Wisconsin resident (Wis. Stat. § 134.98).
For our readers, that means a manufacturer holding employee and customer records, a law firm holding client files, a dental practice holding patient records and a financial firm holding account data are all squarely within scope when they hold the covered data elements.
What counts as personal information
The statute defines personal information as an individual's last name plus first name or first initial, linked to at least one of these elements, when the element is not publicly available and not encrypted, redacted or altered to be unreadable (Wis. Stat. § 134.98(1)):
- Social Security number
- Driver's license or state ID number
- Financial account number, or a security code, access code or password that permits access to an account
- DNA profile
- Unique biometric data, such as a fingerprint, voice print, retina or iris image, or another unique physical representation
Two practical points stand out. First, a name alone is not enough. A breached list of names and email addresses, with none of the elements above, does not meet the definition. Second, the definition includes biometric data. If you use fingerprint time clocks, voice authentication or face-based door access, that data belongs in your inventory. Operational controls for protecting biometric data are worth reviewing alongside your notification plan, because a biometric template cannot be reset like a password.
What triggers the duty to notify
The trigger is unauthorized acquisition of personal information. Not every security event qualifies. DATCP and the statute note exceptions:
- No material risk. No notice is required if the acquisition does not create a material risk of identity theft or fraud.
- Good-faith acquisition. No notice is required if an employee or agent acquired the data in good faith for a lawful purpose.
- Encrypted or unreadable data. Data protected this way falls outside the definition, as Mintz's Wisconsin summary also describes.
- Federally regulated entities. The statute treats entities that comply with the Gramm-Leach-Bliley Act or HIPAA as meeting its requirements (Wis. Stat. § 134.98). Dental practices and financial firms should have counsel confirm how that applies to their own situation.
The material-risk exception sounds generous, but the judgment is yours, and you need evidence behind it. Concluding "nothing was taken" requires logs showing what an intruder could and could not reach. A business with no logging cannot show that, and in practice has to assume the worst. This is the clearest example of IT decisions shaping legal outcomes.
What the notice must say and how to send it
The statute is thin on content. The notice must indicate that you know of the unauthorized acquisition of personal information about the recipient. On written request, you must identify the specific information acquired. DATCP's guidance goes further and recommends including:
- A description of the incident
- The types of information involved
- What you are doing to fix the problem
- Your contact information
- Self-protection tips for the recipient
- Contact details for the credit reporting agencies and the FTC
Delivery is by mail or a method you have previously used with the person. When you cannot determine a mailing address and have never communicated with the person, you must use substitute notice reasonably calculated to reach them. DATCP says that might include newspaper, television or radio notice (DATCP).
Law enforcement can ask you to hold notice. The statute allows a delay for any period needed to protect a criminal investigation or homeland security, and DATCP describes the same rule.
Consequences of missing the deadline
The statute states that failing to comply is not itself negligence or a breach of a duty. It can, however, be evidence of negligence or of a breach of a legal duty (Wis. Stat. § 134.98). Davis Wright Tremaine's state summary adds that the statute has no government-notification requirement and no explicit private right of action, while noting that violations may bring civil penalties.
For professionals the exposure is concrete. A State Bar of Wisconsin article explains that a late or missing notice could support an errors and omissions claim against a law firm. Beyond the statute, clients, insurers and customers judge you by how quickly and clearly you told them.
A worked example: how 45 days disappear
Here is an illustration, not a real case. A 120-person Wisconsin manufacturer finds a compromised email account. The attacker used it to reach a shared HR folder containing employee names, Social Security numbers and direct deposit account numbers for 900 current and former employees.
- Days 1 to 3: Contain the incident. Reset credentials, cut off the attacker's access, preserve logs.
- Days 3 to 15: Work out what was accessed. This is where a business without audit logging stalls. If it cannot prove which files were opened, it must assume all 900 records were acquired.
- Days 15 to 25: Counsel confirms the notice duty. The team compiles the mailing list from HR records, including former employees with old addresses.
- Days 25 to 40: Letters are drafted, approved and mailed. The incident is under 1,000 people, so the credit agency notice is not triggered. At 1,000 or more it would be.
That is a good outcome with little slack. Add a missing backup, a vendor that is slow to hand over logs or an HR file nobody knew existed, and the deadline is at risk. Each of those is an IT problem you can solve before an incident.
Build the technical groundwork before an incident
The law does not tell you how to protect data, but its structure rewards certain habits.
Know what personal information you hold
List every system holding the covered elements: HR and payroll, client matter files, patient records, customer account data, shared drives, email archives and laptops. You cannot notify about data you did not know you had, and you cannot prove a material-risk exception for it either.
Encrypt what you can
Because encrypted, redacted or unreadable data is outside the statutory definition, encryption on laptops, servers, backups and cloud storage is the most direct way to reduce what a theft or loss can trigger. The protection depends on the key staying safe, so keep keys and credentials separate from the data.
Keep logs that answer the question
The first question after an incident is what was accessed. Microsoft 365 audit logging, server and firewall logs and endpoint monitoring are what answer it. Make sure retention is long enough to cover a breach discovered weeks late. Our Microsoft 365 consulting covers the configuration side of this.
Have tested backups
Containment and recovery run in parallel. When ransomware encrypts your systems, clean, tested backups let you restore operations while the legal analysis continues. See our overview of backup and disaster recovery in Wisconsin and our ransomware response plan.
Write the response plan and name the people
A one-page plan should name who declares an incident, who calls counsel and your insurer, who preserves evidence, who drafts letters and who talks to staff and customers. Add after-hours phone numbers, since attackers often move on nights and weekends. For an example of how a vendor-side breach can reach your clients' data, see our SMB action checklist.
Check your vendors
If a vendor holds your data, the incident may start on their systems. Your contracts should require them to tell you promptly, so your 45 days do not begin long before you hear anything. The statute itself obliges a data holder to alert the data owner as soon as practicable when no contract says otherwise.
Industry notes
Manufacturers hold employee records, benefits data and sometimes customer or defense-related information. Production downtime compounds the cost, so segmentation between office and plant networks and tested restores matter.
Law firms hold client files and trust account data. Beyond the statute, professional duties to clients apply, and the exposure described by the State Bar article above makes prompt notice a risk-management issue. Our law firm cybersecurity guide goes through the controls.
Dental practices hold patient identifiers, insurance data and payment information. HIPAA and Wisconsin's statute interact, so confirm with counsel which duties apply to your practice.
Financial firms carry GLBA obligations and need documentation to show what safeguards were in place. Our financial services IT support is built around that documentation need.
Perspective
We work with Wisconsin manufacturers, law firms, dentists and financial firms, and the pattern is consistent: the legal clock is rarely the hard part. The hard part is the first two weeks, when nobody can say with confidence what was accessed.
That is why we treat IT as infrastructure, not an expense. Our managed IT services run on a standardized, fully-loaded stack at a fixed cost per user, with 24/7 monitoring, proactive support, security management, backup and disaster recovery, and compliance documentation included. When something happens, the monitoring, the logs and the backups already exist, and so does the documentation showing what safeguards you had.
A fixed per-user price also removes a bad moment from an incident. You are not wondering whether the next hour of help is billable. Emergency response is available when you need it, and the work of preparing for it is part of the service.
The 45-day deadline is short. Preparation is what makes it comfortable.
Dustin Collett
How we can help
The most useful first step is knowing where you stand. Our IT & Security Assessment reviews your environment, including where personal information lives, how it is protected and where the gaps are, so you have a documented picture before you need one. If you want a quick starting point, our IT risk score takes about a minute. If you are already in an incident, our emergency IT services are available around the clock.
When you are ready, book the IT & Security Assessment and we will show you what a prepared Wisconsin business looks like. For ongoing protection, see Managed IT Services.
FAQ
How long do I have to notify people after a data breach in Wisconsin?
You must notify within a reasonable time, not to exceed 45 days after you learn that personal information was acquired without authorization. Reasonableness considers the number of notices and the communication methods available. Law enforcement can ask you to delay if notice would compromise an investigation.
Do I have to report a breach to the state of Wisconsin?
The statute does not require you to report to a state regulator, according to Davis Wright Tremaine's summary. You must notify affected individuals and, when 1,000 or more people are involved, the nationwide consumer reporting agencies. Other laws, contracts or professional rules may add duties, so ask your attorney.
Does the law apply to an out-of-state company with Wisconsin customers?
Yes. An entity that maintains or licenses personal information in Wisconsin has a parallel duty to notify each affected Wisconsin resident. Where you are headquartered does not remove the obligation.
Is encrypted data covered?
Personal information that is encrypted, redacted or altered so it is unreadable falls outside the statutory definition. The protection holds only while the data stays unreadable, so keys and passwords must stay protected as well.
What does the notice have to include?
The statute requires that it indicate you know of the unauthorized acquisition of the person's personal information. DATCP recommends also describing the incident, the information involved, your response, your contact details and self-protection steps, plus contacts for the credit reporting agencies and the FTC.
Sources
- Wisconsin DATCP: Wisconsin's Data Breach Notification Law
- Wisconsin Legislature: Wis. Stat. 134.98(5)
- Wisconsin Legislature: Wis. Stat. 134.98(1)
- Wisconsin Legislative Research Bureau: Data Breaches: Risk, Recovery, and Regulation
- Privacy Rights Clearinghouse: Data Breach Notification Laws, 50-State Survey (2026)
- State Bar of Wisconsin: Wisconsin's Data Breach Notification Law
- Davis Wright Tremaine: Wisconsin data breach summary
- Mintz: Wisconsin
- Operational controls for biometric breach prevention
