---
jurisdiction: "Maine"
slug: maine
countryCode: US
snapshotAsOf: "2026-06-12"
lastReviewed: "2026-06-11"
canonicalUrl: https://openagreements.org/legal/privacy/maine
license: CC BY 4.0
stale: false
---

> [!IMPORTANT]
> **Informational only — not legal advice.** This is a snapshot of an OpenAgreements practice note,
> provided for general information. It is not legal advice, does not create an attorney-client
> relationship, and is not a substitute for a licensed attorney in the relevant jurisdiction.
> Laws change; verify against the canonical version before relying on it.
>
> **Canonical:** https://openagreements.org/legal/privacy/maine · **Snapshot as of:** 2026-06-12 · License: CC BY 4.0 · © UseJunior

# Maine Consumer Privacy Law[^about]

Maine has no comprehensive consumer-privacy statute — LD 1822 was placed in the Legislative Files (DEAD) on April 13, 2026 after the chambers insisted on opposing enactment positions — but it has the nation's strictest ISP privacy law (35-A M.R.S. § 9301, opt-in consent) plus a 30-day breach-notice clock under the Notice of Risk to Personal Data Act.


## At a glance

| Question | Maine |
| --- | --- |
| **Summary** | Maine has no comprehensive consumer-privacy law — the Maine Online Data Privacy Act (LD 1822) was placed in the Legislative Files (DEAD) on April 13, 2026 after the chambers insisted on opposing enactment positions — but it does have the nation's strictest ISP privacy statute, which since July 1, 2020 has required broadband providers serving Maine customers to get opt-in consent before using, disclosing, or selling customer personal information. Every other business builds to the Notice of Risk to Personal Data Act's 30-day breach-notice clock, the Maine Unfair Trade Practices Act, and the federal overlay. |
| **Main law** | 35-A M.R.S. § 9301 (broadband ISP opt-in privacy law, eff. July 1, 2020) plus the Notice of Risk to Personal Data Act, 10 M.R.S. §§ 1346–1350-B — Maine has no comprehensive consumer-privacy statute |
| **Privacy policy required?** | No general mandate — broadband providers must post a clear notice of customers' opt-in rights at the point of sale and on their website; for everyone else, policy contents are driven by FTC Act § 5 and the GLBA, HIPAA, and COPPA overlay |
| **Who does it cover?** | The ISP law reaches only broadband providers serving customers physically located and billed in Maine; the breach act reaches any person maintaining computerized personal information of Maine residents — including state agencies, municipalities, and universities — with no revenue or volume threshold |
| **Can consumers sue?** | None under the breach act (regulator/AG-enforced) and none stated in the ISP law; Maine UTPA § 213 gives consumer purchasers a restitution-oriented action for loss of money or property from unfair or deceptive practices |
| **Who enforces it?** | Maine Attorney General; Department of Professional and Financial Regulation regulators for licensed entities (Bureau of Insurance superintendent for insurance licensees) |

## Which privacy laws apply to your business in Maine? {#which-privacy-laws-apply}

**Short answer.** Maine regulates privacy by sector, not across the board — there is no comprehensive consumer-privacy law. The state's headline statute is the broadband privacy law, 35-A M.R.S. § 9301, the strictest ISP privacy rule in the country: a broadband provider may not use, disclose, sell, or permit access to customer personal information without the customer's opt-in consent [^isp-ban], but it applies only to providers serving customers that are physically located and billed for service in Maine [^isp-scope]. For every other business, the operative state statute is the Notice of Risk to Personal Data Act, Maine's breach-notification law, which reaches essentially any person or entity — including government agencies and universities — that maintains computerized personal information [^breach-person].

Maine came within a few votes of joining the comprehensive-statute states. LD 1822, the Maine Online Data Privacy Act, would have enacted a new 10 M.R.S. chapter 1057 — a strict data-minimization regime modeled on Maryland's law, enforced exclusively by the Attorney General — but it died between the chambers: on April 9, 2026 the House defeated the motion to recede and concur in enactment by a vote of 70 to 79 (Roll Call 800), the Senate insisted on its position on April 13, 2026, and the bill was placed in the Legislative Files, ending it for the session. It is dead, not pending. Given how close the margin was, a re-pass attempt in the next Legislature is plausible, so the comprehensive-bill question is a watch item — but as of this writing nothing is pending, and none of the duties the bill would have created are law.

The practical consequence: Maine residents have no general state-law rights to access, delete, or correct their personal data, no right to opt out of its sale by ordinary businesses, and no Maine law recognizes universal opt-out preference signals. What exists instead is a scoped framework. The broadband law governs ISPs. The breach act governs incident response for everyone. Two sectoral statutes add duties for specific industries: the Maine Insurance Data Security Act requires insurance licensees to maintain a comprehensive written information security program [^insurance-infosec], and the Student Information Privacy Act bars K-12 ed-tech operators from using student data for targeted advertising, profiling, or sale without parental or eligible-student consent [^student-privacy]. The Maine Unfair Trade Practices Act supplies the general deception backstop, and the federal overlay — FTC Act § 5, GLBA for financial institutions, HIPAA for covered health entities, COPPA for child-directed services — carries the rest of a Maine-facing privacy program.

## Does Maine's broadband privacy law require opt-in consent? {#broadband-opt-in-consent}

**Short answer.** Yes — if you are a broadband provider serving Maine customers. Since July 1, 2020, a provider may use, disclose, sell, or permit access to a customer's personal information only if the customer gives express, affirmative consent, which the customer may revoke at any time [^optin-consent]. The statute also bans pay-for-privacy: a provider may not refuse to serve a customer who withholds consent [^no-penalty], and may not charge a penalty or offer a discount based on the consent decision [^no-penalty]. This opt-in default is unusually strict for broadband privacy, and the FCC rules Congress repealed in 2017 were the model this statute revived at the state level.

The scope is precise and narrow. The law covers *broadband Internet access service* — mass-market retail Internet service — and the duty runs only to providers operating in Maine when serving customers physically located and billed in the state. It does not apply to websites, apps, advertisers, or any ordinary business. *Customer personal information* is defined expansively: identifying information such as name, billing information, and Social Security number, plus usage data including web browsing history, application usage history, precise geolocation, financial and health information, device identifiers, and the content of communications.

Three softer edges sit alongside the opt-in core. First, information that is *not* customer personal information runs on opt-out — a provider may use it unless the customer gives written notice withholding permission [^noncpi-optout]. Second, the statute carves out operational uses: a provider may collect, retain, use, disclose, sell and permit access to customer personal information without customer approval [^exceptions] for purposes such as providing the service itself, marketing the provider's own communications-related services, billing and collection, complying with court orders, fraud protection, and emergency-services geolocation. Third, providers owe a freestanding security duty — reasonable measures to protect customer personal information from unauthorized use, disclosure, or access, scaled to the provider's size, activities, and data sensitivity [^security-duty].

How the law is enforced is a genuine open question. Section 9301 prescribes duties but states no penalty, no express enforcement mechanism, and no private right of action, and no Maine enforcement action or merits decision applying it to a provider appears in the public record. Plausible routes — an Unfair Trade Practices Act theory, Public Utilities Commission authority, or an implied action — remain untested. A federal First Amendment challenge by national ISP trade associations (*ACA Connects v. Frey*, D. Me.) would have tested the statute's validity; after the district court denied plaintiffs' motion for judgment on the pleadings, plaintiffs voluntarily dismissed the case on September 2, 2022 before final merits judgment. The statute remains intact and unenjoined, but its constitutionality was never finally adjudicated, and its enforcement machinery has never been exercised.

## Does Maine require your business to post a privacy policy? {#privacy-policy-required}

**Short answer.** For most businesses, no — no Maine statute of general application requires a consumer privacy policy or fixes its contents. The one Maine-specific posting duty falls on broadband providers, which must give every customer a clear, conspicuous, and nondeceptive notice — at the point of sale and on the provider's public website — of the provider's obligations and the customer's rights under the opt-in law [^isp-notice]. For everyone else, FTC Act § 5 supplies the general federal unfair-or-deceptive-practices hook, so whatever you publish has to match what you do [^ftc5-deceptive].

The contents of a Maine-facing privacy policy are therefore overlay-driven. A financial institution may not share nonpublic personal information with nonaffiliated third parties without first delivering the GLBA privacy notice [^glba-notice]. A HIPAA covered entity must give individuals a notice of privacy practices describing the uses and disclosures of their protected health information, their rights, and the entity's duties [^hipaa-notice]. A service directed to children under 13 owes COPPA's online notice and verifiable parental consent. Outside those verticals, follow best practice — describe the categories of data collected, the purposes, the third parties you share with, and how users exercise any choices you offer — and then honor it, because the enforceable obligation is consistency between the statement and the conduct. Maine's Unfair Trade Practices Act tracks FTC Act § 5 by design, so a deceptive policy is exposed under state law on the same theory. Had LD 1822 passed, Maine would have imposed a statutory notice with fixed contents on covered businesses; with the bill dead, no such state checklist exists.

## What must your contracts with vendors say under Maine law? {#vendor-contracts}

**Short answer.** There is no Maine omnibus data-processing-agreement requirement — no statute of general application prescribes controller-to-processor terms, audit rights, deletion clauses, or subprocessor flow-downs. The vendor duties that do exist are sectoral. An insurance licensee must require each third-party service provider to implement appropriate administrative, technical, and physical safeguards for the nonpublic information the provider holds [^insurance-vendor]. No later than January 1, 2027, an insurance licensee must also require third-party service providers to notify it of certain materially harmful cybersecurity events affecting nonpublic information obtained from the licensee [^insurance-vendor-notice]. A K-12 ed-tech operator disclosing student data to a service provider must contractually prohibit the provider from using the data for any purpose other than the contracted service [^student-vendor].

The federal overlay supplies the rest. The GLBA Safeguards Rule requires financial institutions to oversee service providers by contract and to require them to implement and maintain appropriate safeguards [^glba-safeguards]; HIPAA requires a written business-associate agreement with mandatory data-protection, breach-reporting, and subcontractor flow-down terms before protected health information is shared [^hipaa-baa]. Outside those regimes, carrying the same protections forward — processing limited to documented instructions, confidentiality, reasonable security, breach notification back to your business, and return or deletion at the end of the engagement — is best practice rather than a Maine mandate.

One Maine statute does reach every vendor relationship at the moment of failure: under the breach act, a third party that maintains computerized personal information on another person's behalf must notify that person immediately after discovering a breach in which the personal information was, or is reasonably believed to have been, acquired by an unauthorized person [^breach-thirdparty]. Writing that statutory duty into the contract — with a defined notice window and cooperation obligations — converts a bare legal floor into an enforceable workflow, and it matters because the notification clocks discussed in the next section start running against the data owner.

## When must you notify people of a data breach in Maine? {#breach-notification}

**Short answer.** Within 30 days of becoming aware of the breach and identifying its scope, if notice is required at all [^breach-30-day]. The trigger is two-tiered. An ordinary business must investigate promptly and notify affected Maine residents if misuse of their personal information has occurred or is reasonably possible [^breach-general-trigger]. An *information broker* — a business that compiles personal information about individuals to furnish to third parties — faces a stricter, acquisition-based trigger: it must notify residents whose personal information has been, or is reasonably believed to have been, acquired by an unauthorized person, with no misuse-likelihood screen [^breach-broker-trigger]. Whenever resident notice is required, you must also notify the appropriate state regulator — the Department of Professional and Financial Regulation for entities it licenses, otherwise the Attorney General [^breach-regulator-notice].

The Notice of Risk to Personal Data Act defines a *security breach* as the unauthorized acquisition, release, or use of computerized data containing personal information that compromises its security, confidentiality, or integrity, with a good-faith-employee carve-out [^breach-definition]. *Personal information* is the familiar name-plus-data-element formula — name combined with an unencrypted or unredacted Social Security number, driver's license or state ID number, account or card number usable without additional credentials, or passwords and access codes — plus a catchall for data elements that alone would let someone assume the resident's identity [^breach-personal-info]. Encryption and redaction take data outside the definition, which makes them the practical safe harbor [^breach-personal-info].

Two more clocks sit alongside the resident notice. If a single breach requires notifying more than 1,000 persons at once, you must also tell the nationwide consumer reporting agencies without unreasonable delay [^breach-cra-notice]. And if you are an insurance licensee, the Maine Insurance Data Security Act — in force since January 1, 2022 — adds a much faster regulator clock: notice to the Bureau of Insurance superintendent as promptly as possible and no later than 3 business days after determining a cybersecurity event occurred, where Maine is the carrier's domicile or producer's home state, or where the event involves 250 or more Maine consumers and either is otherwise reportable to a government, self-regulatory, or supervisory body or is reasonably likely to materially harm a Maine consumer or a material part of operations [^insurance-3day]. Notification may be delayed for law enforcement, but once an investigation no longer requires delay, the statute allows no more than 7 business days after law enforcement clears it. A person that complies with at-least-as-protective federal or state notification procedures is deemed compliant with the Maine resident-notice section, which may be relevant for entities subject to those federal or state procedures [^breach-deemed-compliance].

## Can a consumer sue your business in Maine over privacy? {#consumer-lawsuit}

**Short answer.** Not under the breach act, and not expressly under the broadband privacy law. The Notice of Risk to Personal Data Act is enforced publicly: the Department of Professional and Financial Regulation enforces it against the entities it licenses, and the Attorney General enforces it against everyone else [^breach-enforcement]. A violation is a civil violation punishable by a fine of not more than $500 per violation, up to a maximum of $2,500 for each day the person is in violation [^breach-penalties], plus equitable relief and injunctions. The route a Maine consumer does have is the Unfair Trade Practices Act: a person who buys goods or services for personal, family, or household purposes and suffers a loss of money or property from an unfair or deceptive practice may sue for actual damages, restitution, and equitable relief [^utpa-pra].

The UTPA's private remedy is real but restitution-oriented and narrower than the data-rights actions in comprehensive-statute states. Standing is limited to consumer purchasers; the plaintiff must show a loss of money or property — a contested hurdle in pure data-exposure cases where no fraud or out-of-pocket loss has occurred; and at least 30 days before filing a damages action, the claimant must mail or deliver a written demand for relief describing the practice and the injuries [^utpa-demand]. The statute's draw for plaintiffs is mandatory fee-shifting: a petitioner who establishes a violation recovers reasonable attorney's fees and costs irrespective of the amount in controversy [^utpa-fees].

Public enforcement carries the heavier artillery. The substantive prohibition is broad — unfair methods of competition and unfair or deceptive acts or practices in trade or commerce are unlawful and construed in line with FTC interpretations [^utpa-207] — and the Attorney General can seek injunctions and restitution [^utpa-ag-remedies], plus a civil penalty of up to $10,000 for each intentional violation [^utpa-ag-penalty]. How any of this maps onto the broadband privacy law remains the open question flagged above: § 9301 prescribes duties without its own penalty or enforcement provision, so whether a violation would be pursued as an unfair trade practice, through utility regulation, or otherwise is untested. A business subject to it should assume the AG would find a route rather than treat the silence as a free pass — but a consumer plaintiff invoking § 9301 directly would be in uncharted territory.

[^about]: By Steven Obiajulu, J.D. Published by [openagreements.org](https://openagreements.org) · Maintained by [UseJunior](https://usejunior.com). Last reviewed 2026-06-11. License: CC BY 4.0. Steven Obiajulu, J.D. is admitted in New York, not Maine. This article synthesizes Maine primary law and is not legal advice from a Maine-admitted attorney. This article is for informational purposes only and does not create an attorney-client relationship.

[^isp-ban]: **35-A M.R.S. § 9301** — "A provider may not use, disclose, sell or permit access to customer personal information" *35-A M.R.S. § 9301(2).* <https://legislature.maine.gov/statutes/35-A/title35-Asec9301-3.html>

[^isp-scope]: **35-A M.R.S. § 9301** — "The requirements of this section apply to providers operating within the State when providing broadband Internet access service to customers that are physically located and billed for service received in the State." *35-A M.R.S. § 9301(7).* <https://legislature.maine.gov/statutes/35-A/title35-Asec9301-3.html>

[^breach-person]: **10 M.R.S. § 1347** — "‘Person’ means an individual, partnership, corporation, limited liability company, trust, estate, cooperative, association or other entity, including agencies of State Government, municipalities, school administrative units, the University of Maine System, the Maine Community College System, Maine Maritime Academy and private colleges and universities." *10 M.R.S. § 1347(5).* <https://legislature.maine.gov/statutes/10/title10sec1347.html>

[^insurance-infosec]: **24-A M.R.S. § 2264** — "a licensee shall develop, implement and maintain a comprehensive, written information security program based on the licensee's risk assessment and containing administrative, technical and physical safeguards for the protection of nonpublic information and the licensee's information systems" *24-A M.R.S. § 2264(1).* <https://legislature.maine.gov/statutes/24-A/title24-Asec2264.html>

[^student-privacy]: **20-A M.R.S. § 953** — "An operator may not knowingly engage in any of the following activities with respect to the operator's website, service or application without explicit written or electronic consent from a student's parent or an eligible student: A. Use student data to engage in targeted advertising on the operator's website, service or application or targeted advertising on any other website, service or application when the targeting of the advertising is based upon any student data and state-assigned student identifiers or other persistent unique identifiers that the operator has acquired because of the use of the operator's website, service or application; ... B. Use student data, including state-assigned student identifiers or other persistent unique identifiers, created or gathered by the operator to amass a profile of a student except for kindergarten to grade 12 school purposes. For purposes of this paragraph, ‘amass a profile’ does not include collection and retention of account information that remains under the control of a student, parent or school administrative unit; ... C. Sell student data." *20-A M.R.S. § 953(1)(A)-(C).* <https://legislature.maine.gov/statutes/20-A/title20-Asec953.html>

[^optin-consent]: **35-A M.R.S. § 9301** — "A provider may use, disclose, sell or permit access to a customer's customer personal information if the customer gives the provider express, affirmative consent to such use, disclosure, sale or access. A customer may revoke the customer's consent under this paragraph at any time." *35-A M.R.S. § 9301(3)(A).* <https://legislature.maine.gov/statutes/35-A/title35-Asec9301-3.html>

[^no-penalty]: **35-A M.R.S. § 9301** — "Charge a customer a penalty or offer a customer a discount based on the customer's decision to provide or not provide consent under paragraph A" *35-A M.R.S. § 9301(3)(B)(2).* <https://legislature.maine.gov/statutes/35-A/title35-Asec9301-3.html>

[^noncpi-optout]: **35-A M.R.S. § 9301** — "A provider may use, disclose, sell or permit access to information the provider collects pertaining to a customer that is not customer personal information, except upon written notice from the customer notifying the provider that the customer does not permit the provider to use, disclose, sell or permit access to that information." *35-A M.R.S. § 9301(3)(C).* <https://legislature.maine.gov/statutes/35-A/title35-Asec9301-3.html>

[^exceptions]: **35-A M.R.S. § 9301** — "a provider may collect, retain, use, disclose, sell and permit access to customer personal information without customer approval" *35-A M.R.S. § 9301(4).* <https://legislature.maine.gov/statutes/35-A/title35-Asec9301-3.html>

[^security-duty]: **35-A M.R.S. § 9301** — "A provider shall take reasonable measures to protect customer personal information from unauthorized use, disclosure or access." *35-A M.R.S. § 9301(5).* <https://legislature.maine.gov/statutes/35-A/title35-Asec9301-3.html>

[^isp-notice]: **35-A M.R.S. § 9301** — "A provider shall provide to each of the provider's customers a clear, conspicuous and nondeceptive notice at the point of sale and on the provider's publicly accessible website of the provider's obligations and a customer's rights under this section." *35-A M.R.S. § 9301(6).* <https://legislature.maine.gov/statutes/35-A/title35-Asec9301-3.html>

[^ftc5-deceptive]: **FTC Act § 5** — "Unfair methods of competition in or affecting commerce, and unfair or deceptive acts or practices in or affecting commerce, are hereby declared unlawful." *15 U.S.C. § 45(a)(1).* <https://www.law.cornell.edu/uscode/text/15/45#:~:text=Unfair%20methods%20of%20competition%20in,commerce%2C%20are%20hereby%20declared%20unlawful.>

[^glba-notice]: **GLBA Privacy Notice** — "a financial institution may not, directly or through any affiliate, disclose to a nonaffiliated third party any nonpublic personal information, unless such financial institution provides or has provided to the consumer a notice that complies with section 6803 of this title" *15 U.S.C. § 6802(a).* <https://www.law.cornell.edu/uscode/text/15/6802#:~:text=a%20financial%20institution%20may%20not%2C,section%206803%20of%20this%20title>

[^hipaa-notice]: **HIPAA Notice of Privacy Practices** — "an individual has a right to adequate notice of the uses and disclosures of protected health information that may be made by the covered entity, and of the individual's rights and the covered entity's legal duties with respect to protected health information" *45 C.F.R. § 164.520.* <https://www.law.cornell.edu/cfr/text/45/164.520#:~:text=an%20individual%20has%20a%20right,respect%20to%20protected%20health%20information>

[^insurance-vendor]: **24-A M.R.S. § 2264** — "Require each 3rd-party service provider to implement appropriate administrative, technical and physical safeguards to protect and secure the information systems and nonpublic information that are accessible to or held by the 3rd-party service provider" *24-A M.R.S. § 2264(6)(B).* <https://legislature.maine.gov/statutes/24-A/title24-Asec2264.html>

[^insurance-vendor-notice]: **24-A M.R.S. § 2264** — "No later than January 1, 2027, require each 3rd-party service provider to notify the licensee when the 3rd-party service provider becomes aware of any cybersecurity event affecting nonpublic information obtained from the licensee that has occurred in an information system maintained by the 3rd-party service provider or by an ancillary service provider if the cybersecurity event has a reasonable likelihood of materially harming any consumer or any material part of the normal operations of the licensee." *24-A M.R.S. § 2264(6)(C).* <https://legislature.maine.gov/statutes/24-A/title24-Asec2264.html>

[^student-vendor]: **20-A M.R.S. § 953** — "Prohibits the service provider from using any student data for any purpose other than providing the contracted service to, or on behalf of, the operator" *20-A M.R.S. § 953(1)(D)(6)(a).* <https://legislature.maine.gov/statutes/20-A/title20-Asec953.html>

[^glba-safeguards]: **GLBA Safeguards Rule** — "Oversee service providers, by: (1) Taking reasonable steps to select and retain service providers that are capable of maintaining appropriate safeguards for the customer information at issue; (2) Requiring your service providers by contract to implement and maintain such safeguards; and (3) Periodically assessing your service providers based on the risk they present and the continued adequacy of their safeguards." *16 C.F.R. § 314.4(f).* <https://www.law.cornell.edu/cfr/text/16/314.4#:~:text=Oversee%20service%20providers%2C%20by%3A%20(1),continued%20adequacy%20of%20their%20safeguards.>

[^hipaa-baa]: **HIPAA Business Associate Contracts** — "A contract between the covered entity and a business associate must: (i) Establish the permitted and required uses and disclosures of protected health information by the business associate. The contract may not authorize the business associate to use or further disclose the information in a manner that would violate the requirements of this subpart, if done by the covered entity, except that: (A) The contract may permit the business associate to use and disclose protected health information for the proper management and administration of the business associate, as provided in paragraph (e)(4) of this section; and (B) The contract may permit the business associate to provide data aggregation services relating to the health care operations of the covered entity. (ii) Provide that the business associate will: (A) Not use or further disclose the information other than as permitted or required by the contract or as required by law; (B) Use appropriate safeguards and comply, where applicable, with subpart C of this part with respect to electronic protected health information, to prevent use or disclosure of the information other than as provided for by its contract; (C) Report to the covered entity any use or disclosure of the information not provided for by its contract of which it becomes aware, including breaches of unsecured protected health information as required by § 164.410; (D) In accordance with § 164.502(e)(1)(ii), ensure that any subcontractors that create, receive, maintain, or transmit protected health information on behalf of the business associate agree to the same restrictions and conditions that apply to the business associate with respect to such information" *45 C.F.R. § 164.504(e)(2).* <https://www.law.cornell.edu/cfr/text/45/164.504#:~:text=A%20contract%20between%20the%20covered,with%20respect%20to%20such%20information>

[^breach-thirdparty]: **10 M.R.S. § 1348** — "A 3rd-party entity that maintains, on behalf of a person, computerized data that includes personal information that the 3rd-party entity does not own shall notify the person maintaining personal information of a breach of the security of the system immediately following discovery if the personal information was, or is reasonably believed to have been, acquired by an unauthorized person." *10 M.R.S. § 1348(2).* <https://legislature.maine.gov/statutes/10/title10sec1348.html>

[^breach-30-day]: **10 M.R.S. § 1348** — "If there is no delay of notification due to law enforcement investigation pursuant to subsection 3, the notices must be made no more than 30 days after the person identified in paragraph A or B becomes aware of a breach of security and identifies its scope." *10 M.R.S. § 1348(1).* <https://legislature.maine.gov/statutes/10/title10sec1348.html>

[^breach-general-trigger]: **10 M.R.S. § 1348** — "If any other person who maintains computerized data that includes personal information becomes aware of a breach of the security of the system, the person shall conduct in good faith a reasonable and prompt investigation to determine the likelihood that personal information has been or will be misused and shall give notice of a breach of the security of the system following discovery or notification of the security breach to a resident of this State if misuse of the personal information has occurred or if it is reasonably possible that misuse will occur." *10 M.R.S. § 1348(1)(B).* <https://legislature.maine.gov/statutes/10/title10sec1348.html>

[^breach-broker-trigger]: **10 M.R.S. § 1348** — "If an information broker that maintains computerized data that includes personal information becomes aware of a breach of the security of the system, the information broker shall conduct in good faith a reasonable and prompt investigation to determine the likelihood that personal information has been or will be misused and shall give notice of a breach of the security of the system following discovery or notification of the security breach to a resident of this State whose personal information has been, or is reasonably believed to have been, acquired by an unauthorized person." *10 M.R.S. § 1348(1)(A).* <https://legislature.maine.gov/statutes/10/title10sec1348.html>

[^breach-regulator-notice]: **10 M.R.S. § 1348** — "When notice of a breach of the security of the system is required under subsection 1, the person shall notify the appropriate state regulators within the Department of Professional and Financial Regulation, or if the person is not regulated by the department, the Attorney General." *10 M.R.S. § 1348(5).* <https://legislature.maine.gov/statutes/10/title10sec1348.html>

[^breach-definition]: **10 M.R.S. § 1347** — "‘Breach of the security of the system’ or ‘security breach’ means unauthorized acquisition, release or use of an individual's computerized data that includes personal information that compromises the security, confidentiality or integrity of personal information of the individual maintained by a person." *10 M.R.S. § 1347(1).* <https://legislature.maine.gov/statutes/10/title10sec1347.html>

[^breach-personal-info]: **10 M.R.S. § 1347** — "‘Personal information’ means an individual's first name, or first initial, and last name in combination with any one or more of the following data elements, when either the name or the data elements are not encrypted or redacted: A. Social security number; ... B. Driver's license number or state identification card number; ... C. Account number, credit card number or debit card number, if circumstances exist wherein such a number could be used without additional identifying information, access codes or passwords; ... D. Account passwords or personal identification numbers or other access codes; or ... E. Any of the data elements contained in paragraphs A to D when not in connection with the individual's first name, or first initial, and last name, if the information if compromised would be sufficient to permit a person to fraudulently assume or attempt to assume the identity of the person whose information was compromised." *10 M.R.S. § 1347(6).* <https://legislature.maine.gov/statutes/10/title10sec1347.html>

[^breach-cra-notice]: **10 M.R.S. § 1348** — "If a person discovers a breach of the security of the system that requires notification to more than 1,000 persons at a single time, the person shall also notify, without unreasonable delay, consumer reporting agencies that compile and maintain files on consumers on a nationwide basis, as defined in 15 United States Code, Section 1681a(p)." *10 M.R.S. § 1348(4).* <https://legislature.maine.gov/statutes/10/title10sec1348.html>

[^insurance-3day]: **24-A M.R.S. § 2266** — "Notwithstanding Title 10, chapter 210‑B, a licensee shall notify the superintendent as promptly as possible but in no event later than 3 business days from a determination that a cybersecurity event has occurred if: A. This State is the licensee's state of domicile, in the case of an insurance carrier, or this State is the licensee's home state, as that term is defined in section 1420‑A, subsection 2, in the case of an insurance producer; or ... B. The licensee reasonably believes that the nonpublic information involved concerns 250 or more consumers residing in this State and that the cybersecurity event is either of the following ... (1) A cybersecurity event affecting the licensee of which notice is required to be provided to any government body, self-regulatory organization or other supervisory body pursuant to any state or federal law; or (2) A cybersecurity event that has a reasonable likelihood of materially harming: (a) Any consumer residing in this State; or (b) Any material part of the normal operation of the licensee." *24-A M.R.S. § 2266(1).* <https://legislature.maine.gov/statutes/24-A/title24-Asec2266.html>

[^breach-deemed-compliance]: **10 M.R.S. § 1349** — "A person that complies with the security breach notification requirements of rules, regulations, procedures or guidelines established pursuant to federal law or the law of this State is deemed to be in compliance with the requirements of section 1348 as long as the law, rules, regulations or guidelines provide for notification procedures at least as protective as the notification requirements of section 1348." *10 M.R.S. § 1349(4).* <https://legislature.maine.gov/statutes/10/title10sec1349.html>

[^breach-enforcement]: **10 M.R.S. § 1349** — "The appropriate state regulators within the Department of Professional and Financial Regulation shall enforce this chapter for any person that is licensed or regulated by those regulators. The Attorney General shall enforce this chapter for all other persons." *10 M.R.S. § 1349(1).* <https://legislature.maine.gov/statutes/10/title10sec1349.html>

[^breach-penalties]: **10 M.R.S. § 1349** — "A person that violates this chapter commits a civil violation and is subject to one or more of the following: A. A fine of not more than $500 per violation, up to a maximum of $2,500 for each day the person is in violation of this chapter, except that this paragraph does not apply to State Government, municipalities, school administrative units, the University of Maine System, the Maine Community College System or Maine Maritime Academy; ... B. Equitable relief; or ... C. Enjoinment from further violations of this chapter." *10 M.R.S. § 1349(2).* <https://legislature.maine.gov/statutes/10/title10sec1349.html>

[^utpa-pra]: **5 M.R.S. § 213** — "Any person who purchases or leases goods, services or property, real or personal, primarily for personal, family or household purposes and thereby suffers any loss of money or property, real or personal, as a result of the use or employment by another person of a method, act or practice declared unlawful by section 207 or by any rule or regulation issued under section 207, subsection 2 may bring an action either in the Superior Court or District Court for actual damages, restitution and for such other equitable relief, including an injunction, as the court determines to be necessary and proper." *5 M.R.S. § 213(1).* <https://legislature.maine.gov/statutes/5/title5sec213.html>

[^utpa-demand]: **5 M.R.S. § 213** — "At least 30 days prior to the filing of an action for damages, a written demand for relief, identifying the claimant and reasonably describing the unfair and deceptive act or practice relied upon and the injuries suffered, must be mailed or delivered to any prospective respondent at the respondent's last known address." *5 M.R.S. § 213(1-A).* <https://legislature.maine.gov/statutes/5/title5sec213.html>

[^utpa-fees]: **5 M.R.S. § 213** — "If the court finds, in any action commenced under this section that there has been a violation of section 207, the petitioner shall, in addition to other relief provided for by this section and irrespective of the amount in controversy, be awarded reasonable attorney's fees and costs incurred in connection with said action." *5 M.R.S. § 213(2).* <https://legislature.maine.gov/statutes/5/title5sec213.html>

[^utpa-207]: **5 M.R.S. § 207** — "Unfair methods of competition and unfair or deceptive acts or practices in the conduct of any trade or commerce are declared unlawful ... It is the intent of the Legislature that in construing this section the courts will be guided by the interpretations given by the Federal Trade Commission and the Federal Courts to Section 45(a)(1) of the Federal Trade Commission Act (15 United States Code 45(a)(1)), as from time to time amended." *5 M.R.S. § 207, § 207(1).* <https://legislature.maine.gov/statutes/5/title5sec207.html>

[^utpa-ag-remedies]: **5 M.R.S. § 209** — "Whenever the Attorney General has reason to believe that a person is using or is about to use any method, act or practice declared by section 207 to be unlawful, and that proceedings would be in the public interest, the Attorney General may bring an action in the name of the State against the person to restrain by temporary or permanent injunction the use of the method, act or practice and the court may make such other orders or judgments as may be necessary to restore to any person who has suffered any ascertainable loss by reason of the use or employment of the unlawful method, act or practice, any moneys or property, real or personal, that may have been acquired by means of the method, act or practice." *5 M.R.S. § 209.* <https://legislature.maine.gov/statutes/5/title5sec209.html>

[^utpa-ag-penalty]: **5 M.R.S. § 209** — "Each intentional violation of section 207 in which the Attorney General establishes that the conduct giving rise to the violation is either unfair or deceptive is a violation for which a civil penalty of not more than $10,000 shall be adjudged." *5 M.R.S. § 209.* <https://legislature.maine.gov/statutes/5/title5sec209.html>
