01
Choice state
Record the visitor preference sent for the test.
ALABAMA / HB 351 (2026), ENROLLED
FUTURE EFFECTIVE
Alabama enacted the Personal Data Protection Act in 2026, with an effective date of May 1, 2027. As of September 2026, the act is not yet in force. A scan today can establish a technical baseline; it cannot identify a present APDPA violation. Alabama Legislature: enrolled HB 351
The enrolled act covers Alabama-facing persons that process more than 25,000 consumers’ data, excluding payment-only data, or derive more than 25% of gross revenue from personal-data sales regardless of consumer count. That second route is easy to miss when copying another state’s threshold. Alabama Legislature: enrolled HB 351
The APDPA is Alabama’s enacted consumer privacy measure scheduled to apply May 1, 2027. It provides eligible residents data rights and addresses targeted advertising, sale, notices, opt-out requests, security and Attorney General enforcement. Alabama Legislature: enrolled HB 351
Unlike many state formulas, Alabama’s alternative sale-revenue trigger does not require a second minimum number of consumers. Its enacted website opt-out provision specifically calls for a clear and conspicuous link to a direct opt-out page or current contact information for submitting the request. Alabama Legislature: enrolled HB 351
| Field | Alabama rule |
|---|---|
| Status | Enacted; not in force as of September 28, 2026 |
| Effective date | May 1, 2027 |
| Volume route | More than 25,000 consumers, excluding payment-only data |
| Sale-revenue route | More than 25% of gross revenue from sales, regardless of consumer count |
| Opt-out access | Clear website link to a direct opt-out page or up-to-date contact information |
| Signals | The enrolled text addresses opt-out preference-signal conflicts; review exact conditions |
| Enforcement after effective date | Attorney General notice; 45-day cure; up to $15,000 per uncured violation |
| Scan status | Technical preparation; no present APDPA enforcement conclusion |
01 / FUTURE APPLICABILITY
Section 3 of enrolled HB 351 addresses persons doing business in Alabama or producing products or services targeted to residents that either control or process personal data of more than 25,000 consumers, excluding data handled solely to complete payment transactions, or derive more than 25% of gross revenue from personal-data sales. The sale-revenue route says regardless of the number of consumers. Alabama Legislature: enrolled HB 351
Section 4 includes detailed entity and information exclusions, including specified small businesses that do not sell data and certain smaller nonprofits that do not sell data. The coverage result depends on business model, employee and sale facts as well as data flows; a site scan cannot resolve the exemption analysis. Alabama Legislature: enrolled HB 351
02 / FUTURE RIGHTS
The enrolled act gives eligible Alabama consumers rights to access, correct, delete and obtain eligible data and to opt out of certain uses including targeted advertising and sale. The request provisions describe a 45-day initial response, an available extension under stated conditions and limits on how an opt-out may be denied. Alabama Legislature: enrolled HB 351
A covered controller will need a notice, intake method and vendor process that carry the customer’s decision beyond the website interface. For data obtained from sources other than the consumer, the enrolled deletion section identifies specific ways to comply; legal counsel should evaluate those options instead of treating every request as an identical database operation. Alabama Legislature: enrolled HB 351
Document both applicability routes and exclusions.
Build intake for access, correction, deletion and opt-out.
Identify recipients of sale or targeted-advertising data.
Test whether downstream systems honor the choice.
03 / WEBSITE TRACKING
Section 6(b) of the enrolled bill requires a clear and conspicuous link on the controller’s website to a page enabling direct opt-out of targeted advertising or sale, or up-to-date contact information to submit the opt-out request. Product teams should choose a usable path and make it discoverable before the effective date. Alabama Legislature: enrolled HB 351
Engineering should compare advertising pixels, storage, conversion APIs and server events before and after the submitted choice. Counsel must classify whether a vendor transfer meets the act’s sale or targeted-advertising definitions; the presence of a tag alone is not a legal conclusion. Alabama Legislature: enrolled HB 351
04 / PREFERENCE SIGNALS
The enrolled § 6(c) discusses an opt-out preference signal sent in accordance with the section and a conflict with a controller-specific privacy setting or voluntary loyalty program. In that case the controller must comply with the signal but may notify the consumer and offer confirmation of the other setting or program. The text should be read with § 6(b)’s direct-request route and any later implementation guidance. Alabama Legislature: enrolled HB 351
Test the direct website link or contact path and a signal scenario separately, preserving the exact preference state and downstream response. A scanner cannot decide whether a particular implementation satisfies every statutory condition, and no current APDPA obligation may be described as violated before May 2027. Alabama Legislature: enrolled HB 351
05 / DATES AND ENFORCEMENT
Section 12 makes the enacted APDPA effective May 1, 2027. Under § 11, the Attorney General issues a violation notice before an action; if the controller fails to correct it within 45 days, the Attorney General may seek an injunction and a court may assess a civil penalty of up to $15,000 per violation after the stated findings. Alabama Legislature: enrolled HB 351
Curing within the notice period also requires an express written statement that the alleged violation is corrected and will not recur. These are future statutory enforcement procedures, not a present 2026 finding or a substitute for preparing the controls before the law starts. Alabama Legislature: enrolled HB 351
06 / PREPARATION
Legal and finance teams should establish whether the organization exceeds the consumer threshold or the independent sale-revenue route, then check entity exceptions and the meaning of each vendor arrangement. Review privacy notices, rights intake and the direct opt-out page against the enrolled act. Alabama Legislature: enrolled HB 351
Run a baseline website scan for rejected consent and GPC, submit the direct opt-out in a separate test, and inventory client and server traffic. Repair controls according to counsel’s classification, keep a dated record and retest before May 1, 2027. Consider other currently applicable laws separately. Alabama Legislature: enrolled HB 351
Assess consumer count and sale-revenue triggers independently.
Review exclusions, particularly the conditional small-entity rules.
Publish a clear direct opt-out or contact route when required.
Check resulting browser and server-side behavior.
TECHNICAL VERIFICATION
Use separate browser sessions to compare the site’s initial behavior, its response to a direct opt-out, and its response to Global Privacy Control where relevant to your review. Record the page URL, test time, browser settings and exact choice made so the result can be reproduced.
Inspect cookies and network requests before and after each choice. Record which requests continue, their destinations and the controls involved. Browser evidence can help diagnose an implementation; it cannot establish statutory applicability, the legal purpose of every transfer or organization-wide compliance.
01
Record the visitor preference sent for the test.
02
List scripts, cookies, platforms like Google Ads and Meta and timing after the choice.
03
Give counsel the recipient, purpose and contractual facts.
04
Compare behavior after approved controls are changed.
INDEPENDENT LEGAL COUNSEL
Legal interpretation, applicability, exemptions, privacy notices, vendor contracts, rights-request procedures, sensitive-data obligations, and organizational governance should be handled by qualified privacy counsel.
FAQ
The enacted HB 351 sets May 1, 2027 as the effective date. As of September 28, 2026, it is not yet in force. Alabama Legislature: enrolled HB 351
One coverage route concerns more than 25,000 consumers’ personal data, excluding data used only to complete payment transactions, for persons doing business in Alabama or targeting residents. Alabama Legislature: enrolled HB 351
Yes. The alternative route is more than 25% of gross revenue from personal-data sales regardless of consumer count, subject to exemptions and the act’s other conditions. Alabama Legislature: enrolled HB 351
No. Section 4 lists conditional exclusions for some smaller businesses and nonprofits that do not sell personal data, among other exemptions. The exact entity and sale facts require review. Alabama Legislature: enrolled HB 351
The enrolled § 6(b) calls for a clear and conspicuous website link to a direct opt-out page for targeted advertising or sale, or current contact information through which a consumer can submit the request. Alabama Legislature: enrolled HB 351
The enacted § 6(c) says a controller must comply with an opt-out preference signal sent in accordance with that section when it conflicts with an existing setting or loyalty choice, though it may notify the consumer and offer a choice to confirm the other setting. Alabama Legislature: enrolled HB 351
The Alabama Attorney General provides notice and a 45-day opportunity to correct; under the enacted conditions a court may assess up to $15,000 for an uncured violation. Alabama Legislature: enrolled HB 351
No. The act is future-effective. A scan in September 2026 records technical behavior for preparation, not a present legal violation.
PRIMARY SOURCES
This page relies on the Alabama Legislature’s final enrolled HB 351, particularly §§ 3–6 and 11–12. Its provisions are described prospectively, and the independent revenue route is kept distinct from the consumer-count threshold.
Prepared by Etalon Editorial Team. Last reviewed September 28, 2026. Material corrections may be sent to contact@etalondata.com.
SCOPE AND RESPONSIBILITY
Etalon is not a law firm and does not provide legal advice. A passing scan or certificate does not guarantee that an organization satisfies every legal obligation.
Technical testing records observable website behavior. Your legal and privacy team remains responsible for coverage, exclusions, classifications, notices, requests, sensitive data, children, contracts, assessments and governance. The APDPA is enacted but its obligations are not yet in force; a present scan cannot establish a violation of this future-effective law.
OPTIONAL SUPPORTING TOOL
Etalon Spectra compares network requests and cookies across isolated consent states to identify tracking that continues after a visitor opts out.
It can support the evidence-gathering process described in this guide. Findings describe tested website behavior and do not determine whether an organization complies with the law.