# Alabama Consumer Privacy Law[^about] Alabama's Personal Data Protection Act (Act No. 2026-552) takes effect May 1, 2027, reaching businesses that handle data on more than 25,000 consumers; until then the 2018 breach-notification act, the ADTPA, and federal law govern. ## Which privacy laws apply to your business in Alabama? {#which-privacy-laws-apply} **Short answer.** Two regimes, on a timeline. Alabama has enacted a comprehensive consumer-privacy statute — the Alabama Personal Data Protection Act [^apdpa-short-title] — but it does not take effect until May 1, 2027 [^apdpa-effective-date]. Until that date, the state laws that govern data handling day to day are the Alabama Data Breach Notification Act of 2018 [^breach-act-title] and the Alabama Deceptive Trade Practices Act, supplemented by the federal overlay. The APDPA is currently citable as the session law, Ala. Act No. 2026-552. Two structural points shape everything below. First, the enrolled act text staged here does not include an express rulemaking provision, so its interpretive gaps are likely to be filled by amendment, enforcement positions, or litigation. Second, the APDPA layers on top of — it does not replace — the breach-notification act, which has been in force since 2018 and continues to supply Alabama's data-security and incident-response duties. For the period before May 1, 2027, an Alabama-facing privacy program looks like a no-comprehensive-statute state: the breach act sets the security and notification duties, the Deceptive Trade Practices Act reaches false or misleading privacy statements, and the rest rides federal law — FTC Act § 5 for deceptive or unfair practices generally, the Gramm-Leach-Bliley Act for financial institutions, HIPAA for covered health entities, and COPPA for services directed to children under 13. A program built to that overlay now upgrades, rather than restarts, when the APDPA arrives. ## Will Alabama's new privacy law apply to your business? {#does-apdpa-apply} **Short answer.** Starting May 1, 2027 — only if you clear an unusual two-part gate. The APDPA applies to persons that conduct business in Alabama or target products or services to its residents and that either control or process the personal data of more than 25,000 consumers (excluding data processed solely to complete a payment transaction) or derive more than 25 percent of gross revenue from the sale of personal data [^apdpa-thresholds]. But an entity-level exemption then removes any business with fewer than 500 employees — and any nonprofit with fewer than 100 — provided it does not engage in the sale of personal data [^apdpa-small-business]. The 25,000-consumer trigger is unusually low, and the revenue prong has no dollar floor — more than a quarter of gross revenue from data sales is enough regardless of how few consumers are involved. What pulls in the opposite direction is the unusual employee-count exemption: a company holding data on many Alabamians is still exempt if it has fewer than 500 employees and does not sell personal data. Note the condition — any sale of personal data, as the act defines it, forfeits the exemption entirely; there is no de minimis allowance. The definition of sale is narrower than ordinary disclosure because it excludes disclosures to processors, consumer-directed disclosures, affiliate transfers, M&A transfers, analytics services, and marketing services provided solely to the controller [^apdpa-sale-def]. Coverage is also narrowed by the act's definitions and exemption lists. A consumer is an Alabama resident acting outside a commercial or employment context, so employee and business-to-business data are off the table [^apdpa-consumer-def]. The familiar regulated-entity carve-outs also appear: financial institutions and data governed by the Gramm-Leach-Bliley Act and HIPAA covered entities and business associates are exempt at the entity level [^apdpa-regulated-exemptions], alongside government bodies, higher-education institutions, and data already regulated by FCRA, FERPA, the Driver's Privacy Protection Act, and similar federal regimes. ## What must your Alabama privacy policy contain? {#privacy-policy-contents} **Short answer.** From May 1, 2027, the APDPA prescribes the contents directly: a covered controller must provide a reasonably accurate, clear, and meaningful privacy notice listing the categories of personal data processed, the purpose for processing, the categories of data shared with third parties, the categories of those third parties, an active email address or other contact mechanism, and how consumers may exercise their rights — including a link or contact information for the opt-out method [^apdpa-notice-contents]. Outside sector-specific Alabama privacy statutes, no generally applicable Alabama consumer-privacy statute fixes privacy-policy contents today, but a policy that misstates your practices is a deceptive practice under FTC Act § 5 [^fed-ftc5-deceptive] and is reachable under the ADTPA's catch-all prohibition [^adtpa-catchall]. For a template policy aimed at the APDPA, treat the six-item list as a checklist that must appear on the face of the document. Three further notice-adjacent duties travel with it. If you sell personal data to third parties or process it for targeted advertising, you must clearly and conspicuously disclose that processing and how a consumer can opt out of it [^apdpa-sale-disclosure]. The notice must also establish and describe one or more secure and reliable means for consumers to submit rights requests, suited to how consumers normally interact with you [^apdpa-request-methods]. And the website itself must carry a clear and conspicuous link to a page where a consumer can directly opt out of targeted advertising or sale — or up-to-date contact information for submitting the opt-out request [^apdpa-optout-link]. Compared with other states' notice lists, Alabama's is lean: there is no required retention-period disclosure, no required description of an appeal process (the act creates none), and no fixed sale-of-sensitive-data notice sentence. Until the act takes effect, the operative drafting rule is the consistency rule — under FTC Act § 5 and the ADTPA, the enforceable obligation is that the published policy match actual practice — so a policy built now to the six-item APDPA list both satisfies today's truthfulness standard and is aligned with the APDPA notice list when the act arrives. ## What must your contracts with data vendors say? {#vendor-contracts} **Short answer.** From May 1, 2027, a written contract between the controller and each processor must govern the processor's data processing obligations — the APDPA makes a data processing agreement a statutory requirement [^apdpa-dpa-required]. Today, the breach act already pushes in the same direction: a covered entity's reasonable security measures include retaining service providers that are contractually required to maintain appropriate safeguards for sensitive personally identifying information [^breach-vendor-safeguards]. The APDPA contract must be binding and clearly set out the processing instructions, the nature and purpose of processing, the type of data, the duration, and both parties' rights and obligations. It must also commit the processor to a duty of confidentiality, to delete or return all personal data at the controller's direction at the end of the engagement, to make available the information needed to demonstrate compliance on the controller's reasonable request, and to bind any subcontractor to the same processor obligations [^apdpa-dpa-terms]. Many multi-state DPA templates can be adapted to these elements after checking the Alabama-specific list. One genuine departure deserves emphasis: the staged APDPA text contains no express data-protection-assessment requirement. Nothing in the staged text requires a documented risk assessment before targeted advertising, selling data, processing sensitive data, or profiling. The processor contract, not an assessment file, is the act's named compliance artifact. Where a federal regime applies, it adds its own contracting layer regardless of state law: the GLBA Safeguards Rule requires financial institutions to bind service providers by contract to implement and maintain safeguards [^fed-glba-safeguards], and HIPAA requires a business-associate agreement before protected health information is shared [^fed-hipaa-baa]. ## What rights will Alabama consumers have, and how fast must you respond? {#consumer-rights} **Short answer.** From May 1, 2027, an Alabama consumer can require a covered controller to confirm and access processing of their personal data, correct inaccuracies, delete their data, obtain a portable copy, and opt out of targeted advertising, the sale of their data, and profiling in furtherance of solely automated significant decisions [^apdpa-rights]. The controller must respond within 45 days of receiving the request and may take one 45-day extension when reasonably necessary, with notice and the reason given inside the initial window [^apdpa-response-clock]. Responses are free of charge once per consumer in any 12-month period; for manifestly unfounded, excessive, technically infeasible, or repetitive requests the controller may charge a reasonable fee or decline to act, and bears the burden of demonstrating that character on inquiry by an enforcement authority [^apdpa-request-fees]. The access and portability rights each carry a trade-secret carve-out, and parents, guardians, and conservators may exercise rights on a known child's or protected consumer's behalf [^apdpa-representative-rights]. The rights themselves cannot be contracted away: any contract provision that purports to waive or limit a consumer's rights under the act is void and unenforceable as contrary to public policy [^apdpa-anti-waiver]. Two things the act does not contain are worth stating plainly. The APDPA requires a controller that declines a request to give the consumer its justification within 45 days, but the staged text does not include an appeal mechanism or require the privacy notice to describe one [^apdpa-refusal-response]. And because the enrolled act text staged here does not include an express rulemaking provision, there is no regulator who can add one by rule. The profiling opt-out is also narrower than it may first appear: it reaches only solely automated processing, and only for a closed list of significant decisions such as credit, housing, insurance, education, criminal justice, employment opportunity, health care, and basic necessities [^apdpa-significant-decision]. > [!NOTE] > **Practice note.** > > Open statutory question — universal opt-out preference signals. The act's only treatment of browser- or device-level opt-out signals is a conflict rule: when a consumer's opt-out decision sent through an opt-out preference signal conflicts with an existing controller-specific setting or loyalty-program participation, the controller shall comply with the signal [^apdpa-optout-signal]. One reading takes that command as presupposing a duty to process such signals; the other observes that no provision affirmatively requires controllers to recognize universal signals, the act specifies no technical standard or phase-in, and no agency has rulemaking power to supply one. The text supports both readings, and commentary on the act splits the same way. Until the Attorney General or a court resolves it, a conservative posture treats widely adopted signals as valid opt-outs of targeted advertising and sale. ## Will you need consent to use sensitive data? {#sensitive-data-consent} **Short answer.** Yes. From May 1, 2027, a covered controller may not process a consumer's sensitive data without that consumer's consent — and for a known child, processing must comply with the federal Children's Online Privacy Protection Act [^apdpa-sensitive-optin]. Sensitive data covers data revealing racial or ethnic origin, religious beliefs, health conditions or diagnoses, sex life, sexual orientation, or citizenship or immigration status; genetic or biometric data processed to uniquely identify a person; personal data collected from a known child; and precise geolocation data [^apdpa-sensitive-def]. The consent bar is deliberately high: consent means a clear affirmative act signifying a freely given, specific, informed, and unambiguous agreement, and it expressly excludes acceptance of broad terms of use, hovering, muting, or pausing content, and agreements obtained through dark patterns [^apdpa-consent-def]. Consent must also be revocable through a mechanism at least as easy as the one used to give it [^apdpa-consent-revocation]. Teenagers get a separate protection: a controller with actual knowledge that a consumer is at least 13 but younger than 16 may not process that consumer's personal data for targeted advertising or sell it without consent [^apdpa-teen-rule]. Controllers that comply with COPPA's verifiable parental-consent requirements are deemed compliant with the act's parental-consent obligations, so an existing COPPA program carries over [^apdpa-coppa-safe-harbor]. ## When must you notify people of a data breach in Alabama? {#breach-notification} **Short answer.** This duty is in force now, and it survives the APDPA. A covered entity that determines that sensitive personally identifying information has been acquired (or is reasonably believed to have been acquired) by an unauthorized person, and is reasonably likely to cause substantial harm, must notify each affected individual [^breach-notice-trigger]. The notice must go out as expeditiously as possible and, in any event, within 45 days of the entity's determination or of notice from a third-party agent [^breach-45-days]. If more than 1,000 individuals must be notified, the entity must also give written notice to the Attorney General [^breach-ag-notice]. The breach act also imposes Alabama's standing security duty: every covered entity and third-party agent must implement and maintain reasonable security measures to protect sensitive personally identifying information [^breach-security-duty] — including designating a security coordinator, identifying risks, adopting safeguards, and keeping management informed. Vendors are on their own clock: a third-party agent that experiences a breach in a system it maintains must notify the covered entity as expeditiously as possible and no later than 10 days after determining the breach occurred [^breach-vendor-clock]. And when more than 1,000 individuals are notified at one time, the entity must also notify the nationwide consumer reporting agencies [^breach-cra-notice]. Some operating details matter for the incident-response plan. Sensitive personally identifying information is a name combined with elements like a non-truncated Social Security number, government ID number, financial account number with its access code, medical or health-insurance information, or online-account credentials — and properly encrypted or truncated data is excluded unless the key was also compromised [^breach-spii-def]. The individual notice must include at minimum the breach date or date range, a description of the information involved, the remediation actions taken, steps the individual can take against identity theft, and contact information [^breach-notice-contents]. Substitute notice (website posting plus media) is allowed when direct notice would cost over $500,000, contact information is lacking, or more than 100,000 people are affected [^breach-substitute-notice]. If you determine notice is not required, document that determination and keep it for at least five years [^breach-no-notice-record]. ## Can a consumer sue your business under Alabama privacy law? {#consumer-lawsuit} **Short answer.** The APDPA contains no express private right of action; its enforcement section authorizes Attorney General enforcement after notice and cure. Only if the controller fails to correct the violation within 45 days may the Attorney General sue for an injunction, with a civil penalty of up to $15,000 per violation [^apdpa-enforcement]. The breach act is clearer: it routes its violations into the Deceptive Trade Practices Act with the Attorney General holding exclusive authority to seek civil penalties [^breach-adtpa-routing], and it states expressly that a violation does not establish a private cause of action [^breach-no-pra]. The APDPA's cure right is unusually strong: it never sunsets, and after a controller corrects the noticed violation within the 45-day window and gives the Attorney General an express written statement that the violations are corrected and will not recur, no APDPA enforcement action may be initiated against the controller under Section 11 [^apdpa-enforcement]. That makes Alabama exposure regulatory and, in the first instance, correctable. Note also that the notice-and-cure text speaks only of controllers; how it applies to processors is an open question the act does not address. The breach act has real penalty teeth despite the no-private-action rule: knowing violations of its notice provisions draw ADTPA penalties capped at $500,000 per breach [^breach-500k-cap], and a separate provision adds up to $5,000 per day for each consecutive day an entity fails to take reasonable action to comply with the notice duties [^breach-per-day]. The ADTPA itself does carry a limited private remedy — a consumer who suffers monetary damage from an unlawful trade practice may recover actual damages or $100, whichever is greater, with discretionary trebling [^adtpa-private-remedy] — but it is individual-only: the statute bars class actions as a substantive limitation [^adtpa-class-bar], and it requires a 15-day pre-suit demand [^adtpa-demand]. Expect that narrow route to stay closed for APDPA claims as well: where the Legislature wants ADTPA treatment it cross-references the ADTPA expressly, as the breach act does, and the APDPA contains no such cross-reference — it gives the enforcement role to the Attorney General instead. [^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 Alabama. This article synthesizes Alabama primary law and is not legal advice from a Alabama-admitted attorney. This article is for informational purposes only and does not create an attorney-client relationship. [^apdpa-short-title]: **Ala. Act No. 2026-552, § 1 (APDPA short title)** — "Section 1. This act shall be known as the Alabama Personal Data Protection Act." *Ala. Act No. 2026-552, § 1.* [^apdpa-effective-date]: **Ala. Act No. 2026-552, § 12 (effective date)** — "Section 12. This act shall become effective on May 1, 2027." *Ala. Act No. 2026-552, § 12.* [^breach-act-title]: **Ala. Code § 8-38-1 (Data Breach Notification Act short title)** — "This chapter may be cited and shall be known as the Alabama Data Breach Notification Act of 2018." *Ala. Code § 8-38-1.* [^apdpa-thresholds]: **Ala. Act No. 2026-552, § 3 (applicability thresholds)** — "Section 3. The provisions of this act apply to persons that conduct business in this state or persons that produce products or services that are targeted to residents of this state and that meet either of the following qualifications: (1) Control or process the personal data of more than 25,000 consumers, excluding personal data controlled or processed solely for the purpose of completing a payment transaction. (2) Derive more than 25 percent of gross revenue from the sale of personal data, regardless of the number of consumers whose data the person controls or processes." *Ala. Act No. 2026-552, § 3.* [^apdpa-small-business]: **Ala. Act No. 2026-552, § 4(a)(7)-(8) (employee-count exemptions)** — "A business, including an organization cooperatively organized under Chapter 6 of Title 37, Code of Alabama 1975, or an entity that is an instrumentality of a municipal corporation, with fewer than 500 employees, provided the business does not engage in the sale of personal data. (8) A nonprofit entity, as defined in Section 10A-1-1.03, Code of Alabama 1975, with less than 100 employees, provided the entity does not engage in the sale of personal data." *Ala. Act No. 2026-552, § 4(a)(7)-(8).* [^apdpa-sale-def]: **Ala. Act No. 2026-552, § 2(20) (sale of personal data definition)** — "(20) SALE OF PERSONAL DATA. The exchange of personal data for monetary consideration by a controller to a third party, or for other valuable consideration by a controller to a third party where the controller receives a material benefit and the third party is not restricted in its subsequent uses of the personal data. The term does not include any of the following: a. The disclosure of personal data to a processor that processes the personal data on behalf of the controller. b. The disclosure of personal data to a third party for the purposes of providing a product or service requested by the consumer. c. The disclosure or transfer of personal data to an affiliate of the controller. d. The disclosure of personal data in which the consumer directs the controller to disclose the personal data or intentionally uses the controller to interact with a third party. e. The disclosure of personal data that the consumer intentionally made available to the public via a channel of mass media and did not restrict to a specific audience. f. The disclosure or transfer of personal data to a third party as an asset that is part of a merger, acquisition, bankruptcy, or other transaction, or a proposed merger, acquisition, bankruptcy, or other transaction in which the third party assumes control of all or part of the controller's assets. g. The disclosure or transfer of personal data to a third party for the purposes of providing analytics services. h. The disclosure or transfer of personal data to a third party for the purposes of providing marketing services solely to the controller." *Ala. Act No. 2026-552, § 2(20).* [^apdpa-consumer-def]: **Ala. Act No. 2026-552, § 2(6) (consumer definition)** — "CONSUMER. An individual who is a resident of this state. The term does not include an individual acting in a commercial or employment context or as an employee, owner, director, officer, or contractor of a company, partnership, sole proprietorship, nonprofit, or government agency whose communications or transactions with the controller occur solely within the context of that individual's role with the company, partnership, sole proprietorship, nonprofit, or government agency." *Ala. Act No. 2026-552, § 2(6).* [^apdpa-regulated-exemptions]: **Ala. Act No. 2026-552, § 4(a)(5)-(6) (GLBA and HIPAA exemptions)** — "A financial institution or an affiliate of a financial institution governed by, or personal data collected, processed, sold, or disclosed in accordance with Title V of the Gramm-Leach-Bliley Act, 15 U.S.C. § 6801 et. seq. (6) A covered entity or business associate as defined in the privacy regulations of 45 C.F.R. § 160.103." *Ala. Act No. 2026-552, § 4(a)(5)-(6).* [^apdpa-notice-contents]: **Ala. Act No. 2026-552, § 7(d) (privacy-notice contents)** — "A controller shall provide consumers with a reasonably accurate, clear, and meaningful privacy notice that includes all of the following: (1) The categories of personal data processed by the controller. (2) The purpose for processing personal data. (3) The categories of personal data that the controller shares with third parties, if any. (4) The categories of third parties, if any, with which the controller shares personal data. (5) An active email address or other mechanism that the consumer may use to contact the controller. (6) How consumers may exercise their consumer rights, including a link or contact information for availing themselves of the opt-out method provided in Section 6." *Ala. Act No. 2026-552, § 7(d).* [^fed-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).* [^adtpa-catchall]: **Ala. Code § 8-19-5(27) (ADTPA catch-all)** — "Engaging in any other unconscionable, false, misleading, or deceptive act or practice in the conduct of trade or commerce." *Ala. Code § 8-19-5(27).* [^apdpa-sale-disclosure]: **Ala. Act No. 2026-552, § 7(c) (sale and targeted-advertising disclosure)** — "If a controller sells personal data to third parties or processes personal data for targeted advertising, the controller shall clearly and conspicuously disclose the processing, as well as the way a consumer may exercise the right to opt out of the processing." *Ala. Act No. 2026-552, § 7(c).* [^apdpa-request-methods]: **Ala. Act No. 2026-552, § 7(e)(1) (request methods described in the notice)** — "A controller shall establish and describe in a privacy notice one or more secure and reliable means for consumers to submit a request to exercise their consumer rights, as established under Section 5, pursuant to this act considering the ways in which consumers normally interact with the controller, the need for secure and reliable communication of consumer requests, and the ability of the controller to authenticate the identity of the consumer or authorized agent making the request." *Ala. Act No. 2026-552, § 7(e)(1).* [^apdpa-optout-link]: **Ala. Act No. 2026-552, § 6(b) (website opt-out link)** — "A controller must allow a consumer to opt-out by providing a clear and conspicuous link on the controller's Internet website to an Internet web page that enables a consumer directly to opt out of any processing of the consumer's personal data for the purposes of targeted advertising or sale of the consumer's personal data, or provides up-to-date contact information for a consumer to submit the opt-out request." *Ala. Act No. 2026-552, § 6(b).* [^apdpa-dpa-required]: **Ala. Act No. 2026-552, § 8(b)(1) (processor contract required)** — "A contract between a controller and a processor shall govern the processor's data processing obligations with respect to processing performed on behalf of the controller." *Ala. Act No. 2026-552, § 8(b)(1).* [^breach-vendor-safeguards]: **Ala. Code § 8-38-3(b)(4) (service providers contractually bound)** — "Retention of service providers, if any, that are contractually required to maintain appropriate safeguards for sensitive personally identifying information." *Ala. Code § 8-38-3(b)(4).* [^apdpa-dpa-terms]: **Ala. Act No. 2026-552, § 8(b)(2)-(3) (required processor contract terms)** — "(2) The contract shall: a. Be binding; b. Clearly set forth instructions for processing data; c. Clearly set forth the nature and purpose of the processing; d. Clearly set forth the type of data subject to processing; e. Clearly set forth the duration of processing; and f. Clearly set forth the rights and obligations of both parties. (3) The contract, taking into account the nature of the processing, the relationship between the parties, and other factors, shall also require the processor to: a. Ensure that each processor of personal data is subject to a duty of confidentiality with respect to the personal data; b. Delete or return all personal data to the controller as requested at the end of the provision of services at the controller's direction, unless retention of the personal data is required or permitted by law or the contract; c. Make available to the controller all information in the processor's possession necessary to demonstrate the processor's compliance with the obligations of this act upon the reasonable request of the controller; and d. Obligate any subcontractor processing personal data to meet the obligations of the processor with respect to the personal data." *Ala. Act No. 2026-552, § 8(b)(2)-(3).* [^fed-glba-safeguards]: **GLBA Safeguards Rule** — "Requiring your service providers by contract to implement and maintain such safeguards" *16 C.F.R. § 314.4(f)(2).* [^fed-hipaa-baa]: **HIPAA Business Associate Contracts** — "A contract between the covered entity and a business associate must" *45 C.F.R. § 164.504(e)(2).* [^apdpa-rights]: **Ala. Act No. 2026-552, § 5(a) (consumer rights)** — "A controller shall comply with an authenticated request to do any of the following: (1) Confirm whether a controller, or a processor or third party acting on a controller's behalf, is processing the consumer's personal data and accessing any of the consumer's personal data under the control of the controller, unless confirmation or access would require the controller to reveal a trade secret. (2) Correct inaccuracies in the consumer's personal data, considering the nature of the personal data and the purposes of the processing of the consumer's personal data. (3) Direct a controller to delete the consumer's personal data. (4) Obtain a copy of the consumer's personal data previously provided by the consumer to a controller in a portable and, to the extent technically feasible, readily usable format that allows the consumer to transmit the personal data to another controller without hindrance when the processing is carried out by automated means, unless the provision of the data would require the controller to reveal a trade secret. (5) Opt out of the processing of the consumer's personal data for any of the following purposes: a. Targeted advertising. b. The sale of the consumer's personal data. c. Profiling in furtherance of solely automated significant decisions concerning the consumer." *Ala. Act No. 2026-552, § 5(a).* [^apdpa-response-clock]: **Ala. Act No. 2026-552, § 5(d)(1) (45-day response; one extension)** — "A controller shall respond to a consumer's request within 45 days of receipt of the request. b. A controller may extend the response period by 45 additional days, when reasonably necessary considering the complexity and number of the consumer's requests, by notifying the consumer of the extension and the reason for the extension within the initial 45-day response period." *Ala. Act No. 2026-552, § 5(d)(1).* [^apdpa-request-fees]: **Ala. Act No. 2026-552, § 5(d)(3) (free responses; fee for abusive requests)** — "Information provided in response to a consumer request must be provided by a controller, free of charge, once for each consumer during any 12-month period. If a consumer's requests are manifestly unfounded, excessive, technically infeasible, or repetitive, the controller may charge the consumer a reasonable fee to cover the administrative costs of complying with a request or decline to act on a request. Upon inquiry by an enforcement authority, the controller bears the burden of demonstrating the manifestly unfounded, excessive, technically infeasible, or repetitive nature of a request." *Ala. Act No. 2026-552, § 5(d)(3).* [^apdpa-representative-rights]: **Ala. Act No. 2026-552, § 5(c) (representative exercise of rights)** — "(c)(1) A parent or legal guardian of a known child may exercise the consumer's rights on behalf of the known child regarding the processing of personal data. (2) A guardian or conservator of a consumer may exercise the consumer's rights on behalf of the consumer regarding the processing of personal data." *Ala. Act No. 2026-552, § 5(c).* [^apdpa-anti-waiver]: **Ala. Act No. 2026-552, § 7(f) (anti-waiver)** — "Any provision of a contract or agreement of any kind that purports to waive or limit in any way a consumer's consumer rights as established under this act shall be deemed contrary to public policy and shall be void and unenforceable." *Ala. Act No. 2026-552, § 7(f).* [^apdpa-refusal-response]: **Ala. Act No. 2026-552, § 5(d)(2) (refusal response)** — "If a controller declines to act regarding a consumer's request, the controller shall inform the consumer of the justification for declining to act within 45 days of receipt of the request." *Ala. Act No. 2026-552, § 5(d)(2).* [^apdpa-significant-decision]: **Ala. Act No. 2026-552, § 2(22) (significant decision definition)** — "(22) SIGNIFICANT DECISION. A decision made by a controller that results in the provision or denial by the controller of credit or lending services, housing, insurance, education enrollment or opportunity, criminal justice, employment opportunity, health care service, or access to basic necessities such as food or water." *Ala. Act No. 2026-552, § 2(22).* [^apdpa-optout-signal]: **Ala. Act No. 2026-552, § 6(c)(1) (opt-out preference signal conflict rule)** — "If a consumer's decision to opt out of any processing of the consumer's personal data for the purposes of targeted advertising, or any sale of personal data, through an opt-out preference signal sent in accordance with this section conflicts with the consumer's existing controller-specific privacy setting or voluntary participation in a controller's bona fide loyalty, rewards, premium features, discounts, or club card program, the controller shall comply with the consumer's opt-out preference signal but may notify the consumer of the conflict and provide the choice to confirm controller-specific privacy settings or participation in such a program." *Ala. Act No. 2026-552, § 6(c)(1).* [^apdpa-sensitive-optin]: **Ala. Act No. 2026-552, § 7(b)(1)-(2) (sensitive-data consent)** — "(b) A controller may not do any of the following: (1) Except as provided in this act, process personal data for purposes that are not reasonably necessary to or compatible with the disclosed purposes for which the personal data is processed as disclosed by the controller. (2) Process sensitive data concerning a consumer other than a known child without obtaining that consumer's consent or, in the case of the processing of personal data concerning a known child, without processing the data in accordance with the federal Children's Online Privacy Protection Act of 1998, 15 U.S.C. § 6501 et seq." *Ala. Act No. 2026-552, § 7(b)(1)-(2).* [^apdpa-sensitive-def]: **Ala. Act No. 2026-552, § 2(21) (sensitive-data definition)** — "SENSITIVE DATA. Personal data that includes any of the following: a. Data revealing racial or ethnic origin, religious beliefs, a mental or physical health condition or diagnosis, information about an individual's sex life, sexual orientation, or citizenship or immigration status. b. The processing of genetic or biometric data for the purpose of uniquely identifying an individual. c. Personal data collected from a known child. d. Precise geolocation data." *Ala. Act No. 2026-552, § 2(21).* [^apdpa-consent-def]: **Ala. Act No. 2026-552, § 2(5) (consent definition)** — "CONSENT. A clear affirmative act signifying a consumer's freely given, specific, informed, and unambiguous agreement to allow the processing of personal data relating to the consumer, including, but not limited to, a written statement or a statement by electronic means. The term does not include any of the following: a. Acceptance of a general or broad term of use or similar document that contains descriptions of personal data processing along with other unrelated information. b. Hovering over, muting, or pausing a given piece of content. c. An agreement obtained using dark patterns." *Ala. Act No. 2026-552, § 2(5).* [^apdpa-consent-revocation]: **Ala. Act No. 2026-552, § 7(a)(3) (consent revocation)** — "(3) Provide an effective mechanism for a consumer to revoke the consumer's consent under this act that is at least as easy as the mechanism by which the consumer provided the consumer's consent and, on revocation of the consent, cease to further process the personal data as soon as practicable, but no later than 45 days after complying with the consumer's opt-out request consistent with this act." *Ala. Act No. 2026-552, § 7(a)(3).* [^apdpa-teen-rule]: **Ala. Act No. 2026-552, § 7(b)(4) (13-to-15-year-olds)** — "(b) A controller may not do any of the following: (1) Except as provided in this act, process personal data for purposes that are not reasonably necessary to or compatible with the disclosed purposes for which the personal data is processed as disclosed by the controller. (2) Process sensitive data concerning a consumer other than a known child without obtaining that consumer's consent or, in the case of the processing of personal data concerning a known child, without processing the data in accordance with the federal Children's Online Privacy Protection Act of 1998, 15 U.S.C. § 6501 et seq. (3) Process personal data in violation of the laws of this state or federal laws that prohibit unlawful discrimination against consumers. (4) Process the personal data of a consumer for the purposes of targeted advertising or sell a consumer's personal data without the consumer's consent under circumstances in which a controller has actual knowledge that the consumer is at least 13 years of age but younger than 16 years of age." *Ala. Act No. 2026-552, § 7(b)(4).* [^apdpa-coppa-safe-harbor]: **Ala. Act No. 2026-552, § 4(c) (COPPA parental-consent compliance)** — "(c) Controllers and processors that comply with the verifiable parental consent requirements of the federal Children's Online Privacy Protection Act of 1998 are compliant with any obligation to obtain parental consent pursuant to this act." *Ala. Act No. 2026-552, § 4(c).* [^breach-notice-trigger]: **Ala. Code § 8-38-5(a) (individual-notice trigger)** — "A covered entity that is not a third-party agent that determines under Section 8-38-4 that, as a result of a breach of security, sensitive personally identifying information has been acquired or is reasonably believed to have been acquired by an unauthorized person, and is reasonably likely to cause substantial harm to the individuals to whom the information relates, shall give notice of the breach to each individual." *Ala. Code § 8-38-5(a).* [^breach-45-days]: **Ala. Code § 8-38-5(b) (45-day individual-notice clock)** — "(b) Notice to individuals under subsection (a) shall be made as expeditiously as possible and without unreasonable delay, taking into account the time necessary to allow the covered entity to conduct an investigation in accordance with Section 8-38-4. Except as provided in subsection (c), the covered entity shall provide notice within 45 days of the covered entity's receipt of notice from a third-party agent that a breach has occurred or upon the covered entity's determination that a breach has occurred and is reasonably likely to cause substantial harm to the individuals to whom the information relates." *Ala. Code § 8-38-5(b).* [^breach-ag-notice]: **Ala. Code § 8-38-6(a) (Attorney General notice over 1,000)** — "If the number of individuals a covered entity is required to notify under Section 8-38-5 exceeds 1,000, the entity shall provide written notice of the breach to the Attorney General as expeditiously as possible and without unreasonable delay." *Ala. Code § 8-38-6(a).* [^breach-security-duty]: **Ala. Code § 8-38-3(a)-(b) (reasonable security measures)** — "(a) Each covered entity and third-party agent shall implement and maintain reasonable security measures to protect sensitive personally identifying information against a breach of security. (b) Reasonable security measures means security measures practicable for the covered entity subject to subsection (c), to implement and maintain, including consideration of all of the following: (1) Designation of an employee or employees to coordinate the covered entity's security measures to protect against a breach of security. An owner or manager may designate himself or herself. (2) Identification of internal and external risks of a breach of security. (3) Adoption of appropriate information safeguards to address identified risks of a breach of security and assess the effectiveness of such safeguards. (4) Retention of service providers, if any, that are contractually required to maintain appropriate safeguards for sensitive personally identifying information. (5) Evaluation and adjustment of security measures to account for changes in circumstances affecting the security of sensitive personally identifying information. (6) Keeping the management of the covered entity, including its board of directors, if any, appropriately informed of the overall status of its security measures; provided, however, that the management of a government entity subject to this subdivision may be appropriately informed of the status of its security measures through a properly convened executive session under the Open Meetings Act pursuant to Section 36-25A-7." *Ala. Code § 8-38-3(a)-(b).* [^breach-vendor-clock]: **Ala. Code § 8-38-8 (third-party agent 10-day notice)** — "In the event a third-party agent has experienced a breach of security in the system maintained by the agent, the agent shall notify the covered entity of the breach of security as expeditiously as possible and without unreasonable delay, but no later than 10 days following the determination of the breach of security or reason to believe the breach occurred." *Ala. Code § 8-38-8.* [^breach-cra-notice]: **Ala. Code § 8-38-7 (consumer reporting agency notice)** — "If a covered entity discovers circumstances requiring notice under Section 8-38-5 of more than 1,000 individuals at a single time, the entity shall also notify, without unreasonable delay, all consumer reporting agencies that compile and maintain files on consumers on a nationwide basis, as defined in the Fair Credit Reporting Act, 15 U.S.C. §1681a, of the timing, distribution, and content of the notices." *Ala. Code § 8-38-7.* [^breach-spii-def]: **Ala. Code § 8-38-2(6) (sensitive personally identifying information)** — "(6) SENSITIVE PERSONALLY IDENTIFYING INFORMATION. a. Except as provided in paragraph b., an Alabama resident's first name or first initial and last name in combination with one or more of the following with respect to the same Alabama resident: 1. A non-truncated Social Security number or tax identification number. 2. A non-truncated driver's license number, state-issued identification card number, passport number, military identification number, or other unique identification number issued on a government document used to verify the identity of a specific individual. 3. A financial account number, including a bank account number, credit card number, or debit card number, in combination with any security code, access code, password, expiration date, or PIN, that is necessary to access the financial account or to conduct a transaction that will credit or debit the financial account. 4. Any information regarding an individual's medical history, mental or physical condition, or medical treatment or diagnosis by a health care professional. 5. An individual's health insurance policy number or subscriber identification number and any unique identifier used by a health insurer to identify the individual. 6. A user name or email address, in combination with a password or security question and answer that would permit access to an online account affiliated with the covered entity that is reasonably likely to contain or is used to obtain sensitive personally identifying information. b. The term does not include either of the following: 1. Information about an individual which has been lawfully made public by a federal, state, or local government record or a widely distributed media. 2. Information that is truncated, encrypted, secured, or modified by any other method or technology that removes elements that personally identify an individual or that otherwise renders the information unusable, including encryption of the data, document, or device containing the sensitive personally identifying information, unless the covered entity knows or has reason to know that the encryption key or security credential that could render the personally identifying information readable or useable has been breached together with the information." *Ala. Code § 8-38-2(6).* [^breach-notice-contents]: **Ala. Code § 8-38-5(d) (individual-notice contents)** — "(d) Except as provided by subsection (e), notice to an affected individual under this section shall be given in writing, sent to the mailing address of the individual in the records of the covered entity, or by email notice sent to the email address of the individual in the records of the covered entity. The notice shall include, at a minimum, all of the following: (1) The date, estimated date, or estimated date range of the breach. (2) A description of the sensitive personally identifying information that was acquired by an unauthorized person as part of the breach. (3) A general description of the actions taken by a covered entity to restore the security and confidentiality of the personal information involved in the breach. (4) A general description of steps an affected individual can take to protect himself or herself from identity theft. (5) Information that the individual can use to contact the covered entity to inquire about the breach." *Ala. Code § 8-38-5(d).* [^breach-substitute-notice]: **Ala. Code § 8-38-5(e) (substitute notice)** — "(e)(1) A covered entity required to provide notice to any individual under this section may provide substitute notice in lieu of direct notice, if direct notice is not feasible due to any of the following: a. Excessive cost. The term includes either of the following: 1. Excessive cost to the covered entity relative to the resources of the covered entity. 2. The cost to the covered entity exceeds five hundred thousand dollars ($500,000). b. Lack of sufficient contact information for the individual required to be notified. c. The affected individuals exceed 100,000 persons. (2) a. Substitute notice shall include both of the following: 1. A conspicuous notice on the Internet website of the covered entity, if the covered entity maintains a website, for a period of 30 days. 2. Notice in print and in broadcast media, including major media in urban and rural areas where the affected individuals reside. b. An alternative form of substitute notice may be used with the approval of the Attorney General." *Ala. Code § 8-38-5(e).* [^breach-no-notice-record]: **Ala. Code § 8-38-5(f) (no-notice documentation)** — "(f) If a covered entity determines that notice is not required under this section, the entity shall document the determination in writing and maintain records concerning the determination for no less than five years." *Ala. Code § 8-38-5(f).* [^apdpa-enforcement]: **Ala. Act No. 2026-552, § 11 (AG enforcement; 45-day cure; $15,000 penalty)** — "Section 11. (a) The Attorney General may enforce violations of this act. (b)(1) The Attorney General, prior to initiating any action for a violation of any provision of this act, shall issue a notice of violation to the controller. (2) If the controller fails to correct the violation within 45 days after receipt of the notice of violation, the Attorney General may bring an action for an injunction pursuant to this section. Upon a finding that the controller has violated this act and failed to correct the violation as required by this section, the court may assess a civil penalty of not more than fifteen thousand dollars ($15,000) per violation. (3) If within the 45-day period the controller corrects the noticed violation and provides the Attorney General an express written statement that the alleged violations have been corrected and that no such further violations will occur, no action may be initiated against the controller." *Ala. Act No. 2026-552, § 11.* [^breach-adtpa-routing]: **Ala. Code § 8-38-9(a) (breach violations routed to the ADTPA)** — "A violation of the notification provisions of this chapter is an unlawful trade practice under the Alabama Deceptive Trade Practices Act, Chapter 19 of this title, but does not constitute a criminal offense under Section 8-19-12. The Attorney General shall have the exclusive authority to bring an action for civil penalties under this chapter." *Ala. Code § 8-38-9(a).* [^breach-no-pra]: **Ala. Code § 8-38-9(a)(1) (no private cause of action)** — "A violation of this chapter does not establish a private cause of action under Section 8-19-10. Nothing in this chapter may otherwise be construed to affect any right a person may have at common law, by statute, or otherwise." *Ala. Code § 8-38-9(a)(1).* [^breach-500k-cap]: **Ala. Code § 8-38-9(a)(2) (knowing violations; $500,000 per breach)** — "Any covered entity or third-party agent who is knowingly engaging in or has knowingly engaged in a violation of the notification provisions of this chapter is subject to the penalty provisions set out in Section 8-19-11. For the purposes of this chapter, knowingly shall mean willfully or with reckless disregard in failing to comply with the notice requirements of Sections 8-38-5 and 8-38-6. Civil penalties assessed under Section 8-19-11, shall not exceed five hundred thousand dollars ($500,000) per breach." *Ala. Code § 8-38-9(a)(2).* [^breach-per-day]: **Ala. Code § 8-38-9(b)(1) ($5,000-per-day penalty)** — "Notwithstanding any remedy available under subdivision (2) of subsection (a), a covered entity that violates the notification provisions of this chapter shall be liable for a civil penalty of not more than five thousand dollars ($5,000) per day for each consecutive day that the covered entity fails to take reasonable action to comply with the notice provisions of this chapter." *Ala. Code § 8-38-9(b)(1).* [^adtpa-private-remedy]: **Ala. Code § 8-19-10(a) (ADTPA limited private remedy)** — "Any person who commits one or more of the acts or practices declared unlawful under this chapter and thereby causes monetary damage to a consumer, and any person who commits one or more of the acts or practices declared unlawful in subdivisions (19) and (20) of Section 8-19-5 and thereby causes monetary damage to another person, shall be liable to each consumer or other person for: (1) Any actual damages sustained by such consumer or person, or the sum of $100, whichever is greater; or (2) Up to three times any actual damages, in the court's discretion." *Ala. Code § 8-19-10(a).* [^adtpa-class-bar]: **Ala. Code § 8-19-10(f) (statutory class-action bar)** — "A consumer or other person bringing an action under this chapter may not bring an action on behalf of a class. The limitation in this subsection is a substantive limitation and allowing a consumer or other person to bring a class action or other representative action for a violation of this chapter would abridge, enlarge, or modify the substantive rights created by this chapter." *Ala. Code § 8-19-10(f).* [^adtpa-demand]: **Ala. Code § 8-19-10(e) (15-day pre-suit demand)** — "(e) At least 15 days prior to the filing of any action under this section, a written demand for relief, identifying the claimant and reasonably describing the unfair or deceptive act or practice relied upon and the injury suffered, shall be communicated to any prospective respondent by placing in the United States mail or otherwise." *Ala. Code § 8-19-10(e).*