Indiana Data Breach Notification Law: What Businesses Must Do
Indiana law requires a business that discovers a breach of personal information to notify affected Indiana residents without unreasonable delay, and no later than 45 days after discovery. If the breach could lead to identity theft, deception or fraud, the business must also tell the Indiana Attorney General. If more than 1,000 residents are notified, it must tell the nationwide consumer reporting agencies too. The rules sit in Indiana Code Article 24-4.9. This guide walks through them in the order you will need them: what counts, who is covered, the clock, the notice itself, exemptions and penalties.
TL;DR
- The 45-day limit is a ceiling, not a target. Notice must go out without unreasonable delay, and within 45 days of discovery, with narrow reasons for a longer delay.
- Covered data is a Social Security number, or a name plus a driver’s license, state ID, card or financial account number with its access code, or adult website age-verification data, when unencrypted.
- Notice goes to affected residents and the Attorney General. Consumer reporting agencies are added above 1,000 residents.
- Penalties reach $150,000 per deceptive act, and separate safeguard duties carry their own penalty.
- The cheapest protection is preparation: encryption, backups, monitoring and a written response plan.
Table of Contents
- What counts as a breach under Indiana law
- Who must comply
- When notification is required
- The 45-day clock
- What the notice must look like
- Telling the Attorney General and credit bureaus
- Exemptions: HIPAA, federal rules and financial institutions
- Penalties and the duty to protect data
- A response timeline you can adopt
- Perspective
- How to prepare before an incident
- Where Curetopia Networks fits
- FAQ
- Sources
What counts as a breach under Indiana law
Indiana defines a “breach of the security of data” as unauthorized acquisition of computerized data that compromises the security, confidentiality or integrity of personal information. The definition also reaches data that has been moved to another medium, such as paper or microfilm. The state’s own cybersecurity guidance points out that this means records printed from a database and not properly disposed of can fall under the statute.

The word that matters is acquisition. A ransomware crew that copies your files has acquired data. A stolen laptop with an unencrypted customer spreadsheet is a breach. A misdirected email to the wrong recipient can be one as well, depending on what the message held and who now has it.
What “personal information” means
The statute does not cover every piece of customer data. Personal information is:
- A Social Security number that is not encrypted or redacted.
- A first and last name (or first initial and last name) combined with at least one unencrypted, unredacted element: a driver’s license number, a state identification card number, a credit card number, or a financial account or debit card number together with the security code, password or access code that would open the account.
- Information collected by an adult-oriented website operator under IC 24-4-23.
The third item is a recent addition, and it is why law firm alerts have been flagging Indiana’s amendment tied to age-verification data. Information lawfully obtained from public records, or from government records made available to the general public, is excluded.
Notice what is absent: email addresses and passwords alone, medical records outside the HIPAA framework, and dates of birth by themselves. Those can still cause real harm and may trigger other duties, such as contract terms or federal rules, but they are not the Indiana statute’s trigger on their own.
Who must comply
The law speaks to a “data base owner,” meaning a person that owns or licenses computerized data that includes personal information. “Person” is broad: it covers individuals, corporations, partnerships, associations, trusts, and nonprofit corporations or organizations. A ten-person accounting practice, a manufacturer with employee records and a nonprofit with donor data are all in scope.
Two definitions decide whether a given person is protected:
- An Indiana resident is someone whose principal mailing address, as reflected in the data base owner’s records, is in Indiana.
- Doing business in Indiana means owning or using an Indiana resident’s personal information for commercial purposes.
You do not need an Indiana office. If you hold personal information about Indiana residents, the law follows the data.
Vendors and service providers
If you hold data you do not own, such as a payroll processor or an IT provider with access to client files, a separate duty applies. A person that maintains computerized data but is not the owner must notify the data base owner when it discovers that personal information was or may have been acquired by an unauthorized person. That is why your vendor contracts should name who tells whom, and how fast.
When notification is required
Notice is not triggered by every incident. After discovering or being notified of a breach, the data base owner must disclose it to an Indiana resident whose unencrypted personal information was or may have been acquired by an unauthorized person. The same applies to encrypted information if the encryption key was also accessible. The duty applies if the owner knows, should know or should have known that the breach has resulted in or could result in identity deception, identity theft or fraud affecting that resident.
Two practical points follow:
- Encryption matters twice. Properly encrypted data without a compromised key generally falls outside the notice duty, and encrypted data is not even “personal information” in the first place.
- “May have been acquired” is a low bar. If your logs cannot show what the intruder touched, you may not be able to prove the data was safe. Good logging and monitoring are what let you narrow the scope of notice.
The 45-day clock
Since the 2022 amendment (P.L.171-2022, effective July 1, 2022), notice must be made without unreasonable delay, but not more than 45 days after discovery of the breach. Before that change the statute said only “without unreasonable delay,” which left the outer limit open.
A delay is considered reasonable only when it is:
- necessary to restore the integrity of the computer system;
- necessary to discover the scope of the breach; or
- in response to a request from the Attorney General or a law enforcement agency to delay because disclosure would impede a criminal or civil investigation or jeopardize national security.
Once the reason for delay ends, disclosure must follow as soon as possible. Practitioners reading the statute, including Mintz in its state summary, describe the same structure: a 45-day outer limit with those three recognized reasons for longer delay.
In practice, 45 days disappears fast. A forensic investigation, a list of affected addresses, legal review and a mail house all take time. The organizations that meet the deadline calmly are the ones that decided who does what before an incident happened.
What the notice must look like
The statute is more specific about delivery than about content. A data base owner must use one of these methods:
- Telephone
- Fax
- Email, if you have the resident’s email address
For very large events there is a substitute path. If you must notify more than 500,000 Indiana residents, or the cost will exceed $250,000, you may instead post a conspicuous notice on your website (if you have one) and notify major news media in the geographic area where the affected residents live. Most small and midsize organizations will never reach those thresholds, so plan for direct notice.
Even though the text does not prescribe wording, a useful notice normally says what happened, what kind of information was involved, what you are doing about it, and what the person can do next, such as placing a fraud alert or credit freeze. If you want a plain-language example of how a company-facing breach explanation reads, this page on steps after a data leak shows how affected customers can be told what was exposed and what to do next.
Telling the Attorney General and credit bureaus
If you notify residents, you must also disclose the breach to the Attorney General. The Attorney General’s office publishes a business FAQ and notification form for this purpose. A determination that there is no likelihood of harm, in which case no resident notice is required, does not require that filing, according to Mintz.
If you must notify more than 1,000 consumers, you must also give each nationwide consumer reporting agency the information it needs to help prevent fraud, including the affected residents’ personal information. The same Attorney General page lists mailing and email contacts for Equifax, Experian and TransUnion.
Exemptions: HIPAA, federal rules and financial institutions
Indiana does not stack its rules on top of every federal regime. A data base owner that keeps its own disclosure procedures as part of a privacy, security or compliance plan under certain federal laws is not required to disclose under this chapter, provided the plan requires notice to Indiana residents without unreasonable delay and the owner follows it. The listed laws include the USA PATRIOT Act, Executive Order 13224, the Driver’s Privacy Protection Act, the Fair Credit Reporting Act, the Financial Modernization Act of 1999 and HIPAA.
Financial institutions that comply with the specified federal interagency guidance are likewise not required to disclose under the chapter.
That does not mean “no notification.” A medical or dental practice following HIPAA, for example, is held to the federal timeline instead, which one compliance firm describes as no later than 60 calendar days under 45 C.F.R. 164.404(b). If your organization sits under a federal framework, ask your attorney which clock governs before an incident, not during one.
Penalties and the duty to protect data
Enforcement belongs to the Attorney General. For failures to follow the notification chapter, the AG may seek an injunction, a civil penalty of up to $150,000 per deceptive act, and reasonable costs of investigation and of maintaining the action. The Attorney General’s own pages say the same: failure to comply can lead to a lawsuit and civil penalties.
There is a second duty that gets less attention. A data base owner must implement and maintain reasonable procedures, including appropriate corrective action, to protect personal information of Indiana residents from unlawful use or disclosure. A person that knowingly or intentionally fails to comply with that section commits a deceptive act that only the Attorney General can pursue, with a civil penalty of up to $5,000 per deceptive act.
The law does not list specific controls, so “reasonable” is measured against what a prudent organization of your size and type would do. Documented, consistently applied security practices are your best evidence.
A response timeline you can adopt
Use the 45 days as a working schedule, and treat the early days as the most valuable.
| Window | What happens |
|---|---|
| Day 0 to 2 | Contain the incident: isolate affected systems, reset credentials, preserve logs. Bring in your IT provider and legal counsel. |
| Day 2 to 14 | Establish scope: which systems, which records, which residents. Determine whether the data was encrypted and whether keys were exposed. |
| Day 14 to 30 | Decide whether the breach meets the notice trigger. Prepare the letter, the Attorney General filing and, if over 1,000 residents, the consumer reporting agency disclosure. |
| Day 30 to 45 | Send notice, file with the Attorney General, and document every decision and reason for any delay. |
These are planning intervals, not statutory milestones. The only statutory number is the 45-day outer limit. If law enforcement asks you to hold off, get the request in writing and record the date.
Perspective
Most breach-notification trouble we see does not start with the breach. It starts with the fact that nobody could say, quickly, what data the business held, where it lived and who could reach it. The 45-day clock only works for you if those answers already exist.
We manage IT as one integrated environment rather than a pile of separate fixes, and that is what makes a breach manageable. When endpoints, email, network, backups and user access are run together, with clear accountability, scoping an incident becomes a matter of reading the logs and records you already have. When they are scattered across vendors and ad-hoc repairs, the same scoping takes weeks.
Our approach is designed to diagnose root causes rather than patch symptoms. For a business in Indiana, that means the reasonable safeguards the statute expects are built into daily operations: encryption on laptops and cloud storage, tested backups, multi-factor sign-in and a written response plan with names next to each task. A technology roadmap from a virtual CIO helps leadership see where regulated data sits before an incident forces the question.
If you take one step this quarter, make it an inventory of where Social Security numbers, financial account numbers and driver’s license numbers live in your organization. Everything in the statute starts from that list.
Cameron
How to prepare before an incident
The statute rewards organizations that can answer questions fast. These are the preparations that pay off most:
- Map your regulated data. List where the personal information defined in the statute is stored: file shares, line-of-business apps, email attachments, cloud drives, paper files and old backups.
- Encrypt by default. Laptops, phones, removable media and cloud storage. Encrypted data without an exposed key falls outside the notice trigger.
- Control access. Multi-factor authentication, least-privilege permissions and prompt removal of departed users shrink both the likelihood and the scope of a breach.
- Keep tested backups. Recovery that works lets you restore system integrity quickly, one of the recognized reasons the law treats as necessary. Our backup and disaster recovery service is built around that outcome.
- Log and monitor. You can only narrow the list of affected residents if you can show what was and was not accessed.
- Write the plan. Name the incident lead, legal counsel, forensic contact, communications owner and insurance carrier. Put the Attorney General’s form and credit bureau contacts in the plan.
- Check vendor contracts. Require vendors who hold your data to notify you promptly if they discover unauthorized acquisition, mirroring the statute’s own vendor duty.
- Dispose of paper properly. Shred printouts that contain covered data, since the statute reaches paper copies of database records.
Industries with extra exposure benefit from tailored checklists. Accounting practices, for example, hold exactly the identifiers the statute names, and our CPA firm IT security checklist covers the controls that matter for that kind of data. Remote and hybrid teams widen the surface further, and our guide to secure remote work covers the practical side.
Where Curetopia Networks fits
If you are reading this because you have to meet the law, or because you want to be ready when it matters, the work is ongoing management, not a one-time project. We provide managed IT and security for organizations across Indianapolis and Central Indiana, treating networks, cloud services, backups and user access as one environment with clear accountability.

Our cybersecurity services cover the safeguards that give you a defensible position under Indiana’s reasonable-procedures duty, and our managed IT services keep those safeguards running day to day. If you already have an internal IT person, co-managed IT adds our team alongside yours. To see where you stand today, start with a free IT assessment.
FAQ
Does Indiana’s breach law apply to small businesses and nonprofits?
Yes. The statute defines a covered “person” to include individuals, corporations, partnerships and nonprofit corporations or organizations. There is no size threshold. If you own or license computerized data containing Indiana residents’ personal information, the law applies to you.
Is there a fixed deadline for notifying Indiana residents?
Yes. Notice must be made without unreasonable delay and no more than 45 days after you discover the breach. A longer delay is allowed only to restore system integrity, determine the scope of the breach, or at the request of the Attorney General or law enforcement, as laid out in the 2022 amendment.
Do I have to notify the Attorney General?
If you notify Indiana residents under the statute, you must also notify the Attorney General. The office provides a designated notification form for businesses to use.
What is the penalty for not following the law?
The Attorney General can seek an injunction and a civil penalty of up to $150,000 per deceptive act, plus investigation costs. Failing to maintain reasonable data protection procedures carries a separate penalty of up to $5,000 per deceptive act when done knowingly or intentionally.
Does the law change if I follow HIPAA?
A data base owner whose HIPAA compliance plan includes breach procedures is not required to make a disclosure under the Indiana chapter, if the plan requires notice to Indiana residents without unreasonable delay and the owner follows it. Confirm the details of your situation with your healthcare compliance counsel.
Sources
- Indiana Code 2026, Chapter 2: definitions
- Indiana Code 2025, Article 24-4.9
- IC 24-4.9-3-1: Disclosure of breach
- IC 24-4.9-3-3.5: Duties of a data base owner
- IC 24-4.9-3-4: Method of disclosure and exceptions
- IC 24-4.9-4-2: Action by Attorney General
- Indiana Cybersecurity Hub: reasonable security controls
- Indiana Attorney General: business FAQ and notification form
- Indiana Attorney General: consumer FAQ
- Workplace Privacy Report: Indiana tightens its notification deadline
- Mintz: Indiana breach notification summary
- GuardWell Compliance: Indiana healthcare compliance guide
