Compliance

Massachusetts Data Breach Notification Law: Who to Notify, What to Say and When

The Massachusetts data breach notification law explained: who must notify, what goes to the AG, OCABR and residents, credit monitoring and the first 72 hours.

By Boston IT Services Group · Published November 14, 2026 · Updated November 14, 2026 · 9 min read

In short

The Massachusetts data breach notification law, M.G.L. Chapter 93H, requires a business that owns or licenses a Massachusetts resident's personal information to notify the Attorney General, the Office of Consumer Affairs and Business Regulation and the affected residents as soon as practicable and without unreasonable delay after it knows or has reason to know of a breach. Since 2019 the law also requires 18 months of free credit monitoring when Social Security numbers are involved. This guide explains who must notify, what each notice must contain, and what to do in the first 72 hours. It is general information, not legal advice.

The Massachusetts data breach notification law, Chapter 93H of the General Laws, requires any business that owns or licenses a Massachusetts resident's personal information to notify three parties after a breach: the Attorney General, the Office of Consumer Affairs and Business Regulation (OCABR), and the affected residents. Notice is due "as soon as practicable and without unreasonable delay," not on a fixed day count. Amendments that took effect April 10, 2019 added more detail to the government notice and required free credit monitoring when Social Security numbers are exposed.

What follows covers who has to notify, what each notice must say, how the 2019 changes work, and a practical plan for the first 72 hours. It is general information, not legal advice; when an incident happens, call your attorney early.

What triggers the Massachusetts data breach notification law

Section 3 of Chapter 93H is triggered when a person or agency knows or has reason to know of either:

  1. a breach of security, or
  2. that a resident's personal information was acquired or used by an unauthorized person or used for an unauthorized purpose.

The definitions sit in section 1. A breach of security is the unauthorized acquisition or use of unencrypted data, or of encrypted data plus the confidential process or key that can compromise it, that "creates a substantial risk of identity theft or fraud" against a resident. A good-faith but unauthorized acquisition by an employee or agent for lawful purposes is not a breach unless the information is then misused or further disclosed.

Personal information has the same meaning as in 201 CMR 17.00: a resident's first name and last name, or first initial and last name, combined with a Social Security number, a driver's license or state ID number, or a financial account or credit or debit card number that would permit access to the account. Publicly available information is excluded.

Two practical consequences follow. First, "reason to know" means you cannot wait for absolute certainty. Second, encryption matters. The statute defines encrypted as a 128-bit or higher algorithmic process, so a stolen laptop with full-disk encryption turned on, and the key not compromised, is a different conversation from a stolen laptop with nothing protecting it. Have your attorney make that call, not your IT provider.

Who must notify: owners versus storers

The law splits responsibility based on your relationship to the data.

Your role Who you notify Your obligations
You own or license the data (it is your clients' or employees' information) Attorney General, OCABR, affected residents, and any consumer reporting agencies or state agencies OCABR identifies Full notice obligations, sample notice to regulators, credit monitoring if SSNs are involved
You maintain or store data for someone else (for example, a cloud host or IT vendor) The owner or licensor of the data Notify as soon as practicable and cooperate, including the date or approximate date of the incident, its nature, and steps taken or planned

If you use an MSP, a cloud document system or a payroll processor, they are usually in the second row and you are in the first. Their notice to you starts your clock. That is one reason your vendor contracts should say how fast they will tell you about an incident.

Massachusetts breach notification requirements for the AG and OCABR

After the amendments in Chapter 444 of the Acts of 2018, the notice to the Attorney General and OCABR must include, at a minimum:

  • the nature of the breach or unauthorized acquisition or use
  • the number of Massachusetts residents affected at the time of notification
  • the name and address of the person or agency that experienced the breach
  • the name and title of the person reporting it, and their relationship to the business that experienced it
  • the type of person or agency reporting
  • the person responsible for the breach, if known
  • the type of personal information compromised (Social Security number, driver's license number, financial account number, card number or other data)
  • whether the business maintains a written information security program
  • the steps taken or planned in response, including updating the written information security program

The Attorney General's breach reporting page also asks whether a report has been made to law enforcement and whether law enforcement is investigating, and, where applicable, the certification of credit monitoring services under section 3A. You must also send both offices a sample copy of the notice you sent to residents.

After receiving your notice, OCABR identifies any relevant consumer reporting agencies or state agencies and sends you their names. You then notify those as well, again as soon as practicable and without unreasonable delay.

Where to report a data breach in Massachusetts

The Attorney General's Office accepts notices through an online portal linked from its reporting page, which says online submission is preferred but not required; you can mail the notice instead. OCABR has its own data breach notification submission form. OCABR's guidance page says it accepts notification by mail, email or its online portal. File with both offices; one filing does not cover the other.

Expect your consumer notice to become public. Under section 3(c), OCABR posts copies of sample consumer notices on its website, within one business day of receipt as practicable. OCABR reminds filers to make sure the sample does not contain any resident's personal information.

What the notice to residents must say, and must not say

The resident notice has an unusual rule. It must include:

  • the resident's right to obtain a police report
  • how to request a security freeze and the information needed to request one
  • that there is no charge for a security freeze
  • any mitigation services provided, such as credit monitoring
  • the name of the parent or affiliated corporation, if the business that had the breach is owned by another company

It must not include the nature of the breach or the number of Massachusetts residents affected. Plenty of generic breach letter templates open with a detailed account of what happened, which runs straight into this rule. If someone hands you a template, check that it has a Massachusetts version.

Notice cannot be delayed because you do not yet know the total number of affected residents. Section 3 says that in that case, and whenever information needs updating or correcting, you provide additional notice as you learn more. OCABR's guidance describes sending notices on a rolling basis.

Under section 1, notice can be written, electronic (if consistent with federal and state e-signature law), or substitute notice. Substitute notice is only available if written notice would cost more than $250,000, the affected class exceeds 500,000 residents, or you lack enough contact information; it includes email notice where you have addresses and a clear and conspicuous posting on your website, among other steps.

The 2019 changes: Massachusetts credit monitoring requirement

The OCABR FAQ explains that Chapter 444 was signed January 10, 2019 and took effect 90 days later on April 10, 2019. The biggest change for businesses was new section 3A:

  • If a breach includes a Social Security number, you must contract with a third party to offer each affected resident credit monitoring at no cost for not less than 18 months.
  • If the business that suffered the breach is a consumer reporting agency, the minimum is 42 months.
  • You must give residents all the information they need to enroll and explain how to place a security freeze.
  • You cannot require residents to waive their private right of action as a condition of the credit monitoring offer.
  • You must file a report with the Attorney General and OCABR certifying that your credit monitoring complies with section 3A. OCABR says this can go in with the breach notification.

If no Social Security number was involved, OCABR's FAQ says there is no requirement to offer credit monitoring, though some businesses choose to.

Law enforcement delays and federal rules

Section 4 allows notice to be delayed if a law enforcement agency determines that notice may impede a criminal investigation, has notified the Attorney General in writing, and informs you of that determination. Once law enforcement says notice no longer poses that risk, you notify as soon as practicable and without unreasonable delay. You must also cooperate with the investigation.

Section 5 matters for regulated firms. A business that maintains breach response procedures under federal law is deemed compliant with Chapter 93H if it notifies affected residents under those procedures and also notifies the Attorney General and OCABR as soon as practicable and without unreasonable delay. A medical practice following HIPAA, for example, notifies individuals under 45 CFR 164.404, which requires notice without unreasonable delay and no later than 60 calendar days after discovery, and still files with the two Massachusetts offices. Our guide to HIPAA IT requirements covers the federal side.

What to do in the first 72 hours

The law does not mention 72 hours. We use it as a working window because the decisions made in the first three days shape everything after, including what your attorney can tell regulators. This is the order we would follow for a small or midsize firm.

Hours 0 to 24: contain and preserve

  1. Call your attorney. If you have cyber insurance, call the carrier's claims line too, and read the policy's notice and vendor terms before you hire a forensic firm or anyone else.
  2. Contain without destroying evidence. Disable compromised accounts, reset passwords, revoke active sessions and isolate affected machines from the network. Do not wipe or rebuild anything yet.
  3. Preserve logs. Export Microsoft 365 or Google Workspace audit logs, firewall logs and EDR alerts before their retention windows roll over.
  4. Start a written timeline: who noticed what, when, and what was done. Section 3 measures your duty from when you knew or had reason to know.

Hours 24 to 48: scope the data

  1. Work out which systems and mailboxes the attacker reached, and for how long.
  2. Identify what personal information was in them. For email compromises this usually means searching mailboxes for Social Security numbers, account numbers and scanned IDs.
  3. Determine which affected people are Massachusetts residents, and whether any Social Security numbers are involved (which triggers the credit monitoring requirement).
  4. Check whether the data was encrypted and whether keys or credentials were also exposed.

Hours 48 to 72: prepare notices and recover

  1. With counsel, decide whether notice is required and draft the Massachusetts-specific resident notice and the regulator filing.
  2. Line up a credit monitoring vendor if SSNs are involved.
  3. Gather what the AG form asks for, including whether you have a WISP and what you are changing in it.
  4. Restore affected systems from clean, known-good backups once forensics allows. A tested backup and disaster recovery plan is what makes this step hours instead of weeks.

Then come the post-incident review and WISP updates that 201 CMR 17.00 requires.

How to be ready before anything happens

Most of the pain in a breach response comes from not knowing where personal information lives and not having the logs to prove what happened. If you fix those two things in advance, the 72 hours above get much easier. Concretely: know where your sensitive data is, turn on and retain audit logging, enforce MFA, encrypt laptops, keep an incident contact sheet (attorney, insurer, IT provider) somewhere outside your email, and rehearse the plan once a year.

Our cybersecurity services for Boston businesses cover monitoring, logging and incident response preparation, and our IT consulting team can help you write and test the plan. If you have never run a tabletop exercise, schedule one this quarter with your attorney in the room.

Frequently asked questions

How long do you have to report a data breach in Massachusetts?

Chapter 93H does not set a fixed number of days. It requires notice as soon as practicable and without unreasonable delay after you know or have reason to know of a breach of security, or that a resident's personal information was acquired or used by an unauthorized person or for an unauthorized purpose. Notice cannot be delayed just because you have not yet counted everyone affected. A law enforcement agency can request a delay.

Who do you notify after a data breach in Massachusetts?

A business that owns or licenses the data must notify the Attorney General's Office, the Office of Consumer Affairs and Business Regulation, and each affected Massachusetts resident. OCABR may also identify consumer reporting agencies or state agencies to notify. A business that only maintains or stores data for someone else notifies the owner or licensor instead and must cooperate with them.

Is credit monitoring required after a breach in Massachusetts?

Only when the breach includes a Social Security number. Section 3A of Chapter 93H requires offering affected residents at least 18 months of credit monitoring at no cost, through a third-party provider. A consumer reporting agency that suffers the breach must offer at least 42 months. You cannot require residents to waive their right to sue as a condition of the offer.

What should not be included in the notice to Massachusetts residents?

Unusually, the resident notice must not describe the nature of the breach or the number of Massachusetts residents affected. Those details go to the Attorney General and OCABR instead. The resident notice must explain the right to obtain a police report, how to request a free security freeze and what information is needed, and any mitigation services such as credit monitoring.

Does the Massachusetts law apply if the data was encrypted?

The statute defines a breach of security as unauthorized acquisition or use of unencrypted data, or of encrypted data together with the key or process that can decrypt it. Encrypted means a 128-bit or higher algorithmic process. Strong, properly managed encryption on a stolen laptop can therefore change the analysis. Confirm with counsel before deciding no notice is needed.

Sources and references

  1. Massachusetts General Laws c. 93H, section 3 (duty to report known security breach)
  2. Massachusetts General Laws c. 93H, section 3A (credit monitoring)
  3. Massachusetts General Laws c. 93H, section 4 (law enforcement delay)
  4. Massachusetts General Laws c. 93H, section 5 (compliance with federal procedures)
  5. Massachusetts General Laws c. 93H, section 1 (definitions)
  6. Chapter 444 of the Acts of 2018
  7. Mass.gov (OCABR): Requirements for Data Breach Notifications
  8. Mass.gov (Attorney General): Reporting data breaches to the Attorney General's Office
  9. Mass.gov (OCABR): Data breach notification submission form
  10. eCFR: 45 CFR 164.404, notification to individuals (HIPAA)

Talk to a Boston IT engineer

Tell us what is slowing your team down. We will review your current setup and send back a plain-English plan with priorities, at no cost.