Maine breach notification lookup
Use this Maine breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Maine: 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 | 10 M.R.S. §§ 1348 and 1349 | Link the decision record to the official citation |
| Deadline | Resident notice as expediently as possible and without unreasonable delay, and if there is no law-enforcement delay, no more than 30 days after becoming aware of the breach and identifying its scope; third-party maintainers notify the data owner immediately; law-enforcement delay may last no longer than seven business days after law enforcement determines notice will not compromise the investigation. | Sort multi-state response work by the shortest stated clock |
| Residents | Maine residents whose personal information has been, or is reasonably believed to have been, acquired by an unauthorized person after the required investigation, including the separate standard for non-broker persons when misuse has occurred or is reasonably possible. | Identify whether affected residents receive notice |
| Regulator | Notify the appropriate Maine Department of Professional and Financial Regulation regulator if regulated by that department; otherwise notify the Maine Attorney General through the Report a Data Breach service when notice under 10 M.R.S. § 1348 is required. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify nationwide consumer reporting agencies without unreasonable delay when a breach requires notice to more than 1,000 persons at a single time, including the date of the breach, estimated affected-person count if known, and actual or anticipated resident-notice date. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | Maine requires regulator notice when resident notice is required: entities regulated by Maine’s Department of Professional and Financial Regulation notify the appropriate department regulator, and other entities notify the Attorney General through the security breach reporting service. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Maine fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
10 M.R.S. §§ 1348 and 1349 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
Maine requires regulator notice when resident notice is required: entities regulated by Maine’s Department of Professional and Financial Regulation notify the appropriate department regulator, and other entities notify the Attorney General through the security breach reporting service. 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 Maine 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 Maine, 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 Maine 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 Maine 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 Maine?
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.