Start hereOpen the incident file and lock the timeline
~39 days leftOpen step
Guide library
Regulation North America

Alabama Data Breach Notification Act

Alabama data breach response: investigation, 45-day notices and evidence

A practical incident-response guide for deciding whether Alabama law applies, running the investigation, and preparing notices that the right people can approve and send.

Issuing authority
Alabama Attorney General and the Alabama Data Breach Notification Act of 2018
Timing
Use the shortest applicable deadline across every affected state and sector. Alabama’s outside limit for required resident and Attorney General notices is 45 days from the organization’s receipt of a third-party-agent breach notice, or from its own determination that a breach occurred and is reasonably likely to cause substantial harm. The law also requires notice as quickly as possible without unreasonable delay. A service provider must alert its covered entity as quickly as possible and no later than 10 days after its determination or reason to believe a breach occurred.
Reviewed
Inside this guide
5 steps · 5 templates

Who it applies to

For covered organizations and service providers that handle electronic sensitive personally identifying information about Alabama residents. The Act focuses on unauthorized acquisition and likely substantial harm. Federal or state sector rules can change the route, and qualifying regulated entities must still meet the Act’s conditions for the exemption.

What you’ll produce

A dated incident file with the trigger decision, resident and data counts, evidence of the investigation, approved notice text, delivery records and a decision on parallel state and federal duties.

Do not treat 45 days as a waiting period. The $500,000 per-breach ceiling applies to knowing notification violations, defined as willful or reckless failures. A separate penalty can reach $5,000 per day for each consecutive day an organization fails to take reasonable action to comply. The Attorney General brings civil-penalty actions. The Act does not create a private cause of action under the Alabama Deceptive Trade Practices Act, while preserving other rights people may have. In Meyer v. Jefferson-Blount-St. Clair Mental Health Authority, an Alabama court-authorized settlement site describes a proposed resolution of claims alleging negligence after a November 2025 cyberattack. The Authority denies the allegations. This is a litigation example, not a court finding or a ruling on the Act.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Alabama Data Breach Notification Act kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Open the incident file and lock the timeline · Incident commander + Security operations + Legal [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Who starts the Alabama clock when a service provider finds an incident, and where is the first notice timestamp preserved?
  • Can Security produce an Alabama resident count without mixing people whose data was encrypted and unusable with people whose credentials may also have been exposed?

Worked scenario

A payroll vendor tells a mid-sized employer that a misconfigured export may have exposed names and account credentials for 1,140 Alabama residents. The incident lead preserves the vendor’s notice and the employer’s receipt time, confirms whether the credentials open financial accounts, asks the vendor for access logs and a person-level file, and opens parallel reviews for other states and sector laws. If Alabama resident notices are required for more than 1,000 people, the team prepares the Attorney General packet and consumer-reporting-agency notice alongside the individual communications.

What to read next

  • EU GDPR

    Compare the separate EU breach-notification clock if EU residents or operations are involved.

DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • Immediately; no later than 10 days after its determination or reason to believe an incident occurred

    Service provider tells the covered entity

    Alabama §8-38-8 sets the outer limit for a third-party agent. Contractual notice windows may be shorter, so use the shorter commitment.

    Official reference (opens in a new tab)
  • As expeditiously as possible; within 45 days at the latest

    Notify affected residents when the statutory trigger is met

    Clock begins on receipt of a third-party-agent notice or the covered entity’s qualifying determination. Check the current official text and other applicable laws.

    Official reference (opens in a new tab)
  • When more than 1,000 people require notice

    Send the Attorney General notice and notify nationwide consumer reporting agencies

    Alabama §8-38-6 requires Attorney General notice within the applicable 45-day period. Section 8-38-7 requires consumer-reporting-agency notice without unreasonable delay when more than 1,000 people are discovered at a single time.

    Official reference (opens in a new tab)
  • At least five years after a no-notice decision

    Retain the written determination and supporting records

    Record why notice was not required and preserve the evidence supporting that decision under §8-38-5(e)(2).

    Official reference (opens in a new tab)
The whole journeyabout 39 days across 5 steps
  1. 01Open the incident file and lock the timeline, Incident commander + Security operations + Legal, about 1 days
  2. 02Find the data, people and likely harm, Forensics + Privacy + system owners + service provider, about 7 days
  3. 03Set the legal route and recipient matrix, Privacy counsel + Compliance + incident commander, about 3 days
  4. 04Prepare and send notices through separate review paths, Privacy + Communications + Legal + customer support, about 14 days
  5. 05Reconcile delivery, preserve the record and close gaps, Privacy operations + Customer support + Internal audit, about 14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 5 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Open the incident file and lock the timelineIncident commander + Security operations + LegalImmediately when a breach may have occurredSet a start dateAlabama incident chronology and evidence logOpen
Find the data, people and likely harmForensics + Privacy + system owners + service providerStart promptly; update the working count as evidence improvesSet a start dateAlabama resident and risk assessmentOpen
Set the legal route and recipient matrixPrivacy counsel + Compliance + incident commanderAs soon as facts support an initial decision; revisit when counts or scope changeSet a start dateAlabama legal route and exemption matrixOpen
Prepare and send notices through separate review pathsPrivacy + Communications + Legal + customer supportAs expeditiously as possible; no later than the applicable 45-day limitSet a start dateAlabama notice packet and approvalsOpen
Reconcile delivery, preserve the record and close gapsPrivacy operations + Customer support + Internal auditDuring delivery and after the last required noticeSet a start dateAlabama delivery and corrective-action registerOpen
0 of 5 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Open the incident file and lock the timeline

    Who Incident commander + Security operations + Legal When Immediately when a breach may have occurred

    Create one restricted case record. Preserve the first alert, vendor notice, email headers, affected systems and decision log. Record separately when the supplier suspected the event, when it made its determination, when your organization received notice and when your own investigation made a harm determination. Name one person to maintain the authoritative clock and one executive to approve urgent containment.

    What to produce

    Alabama incident chronology and evidence logRestricted incident log

    Gather first

    • First alert
    • Vendor or employee report
    • Security tickets
    • System and identity logs
    • Alabama Act §8-38-4 investigation duties

    How to prepare it

    1. Open a restricted case folder and assign an incident commander, evidence custodian and clock owner. Preserve original alerts, message headers, logs and vendor notices. Store working copies separately and record where each original came from.
    2. Record, in UTC and local time with the time zone named, when the agent first suspected the event, when it determined or had reason to believe a breach occurred, when your organization received its notice, when your organization made its own determination and when containment occurred. Do not merge these into one discovery date.
    3. For each event, enter the source, custodian, collection time, integrity check or case reference, and the question the evidence answers. Keep investigative notes factual. Mark estimates as estimates and preserve later corrections as new entries.
    4. Route privilege-sensitive legal analysis to counsel’s approved location. Keep operational facts available to the incident team and record who approved access to restricted personal data.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional vendor notice
    Example only. A payroll processor reports at 14:20 Central on 6 May that it found an exposed export at 09:10 that morning. The customer records receipt at 14:27 Central and starts its own chronology from the original message headers.
    Clock owner
    Fictional incident commander assigns Privacy Operations to maintain the authoritative clock. Security preserves the vendor alert, cloud audit logs and containment ticket without overwriting the originals.
    Evidence reference
    IR-AL-2026-014 / E-001. Source: vendor incident notice. Received: 2026-05-06 19:27 UTC. Custodian: Security response lead. Integrity and storage location: recorded in the restricted evidence index.
    Open question
    Did the recipient download or copy the export? Assigned to forensics. Due before the next harm assessment review. The question remains open until evidence supports a conclusion.

    Check before handing it over

    A second incident lead can reconstruct every legally relevant timestamp, see which facts are confirmed or estimated, and locate unaltered evidence without exposing the records to a broad project team.

    Give the dated timeline and evidence index to Privacy and Legal. Escalate a newly discovered trigger timestamp immediately.

  2. 02

    Find the data, people and likely harm

    Who Forensics + Privacy + system owners + service provider When Start promptly; update the working count as evidence improves

    Investigate in good faith and promptly. Establish the nature and scope, identify Alabama residents and the data tied to each person, and assess whether it was acquired or is reasonably believed acquired by an unauthorized person and is reasonably likely to cause substantial harm. Check the Act’s exact combinations: name plus a non-truncated Social Security or tax number, government ID, financial account access credential, medical information, health-insurance identifier, or qualifying account login credentials. Record evidence of copying, misuse, public posting, lost devices and whether encryption keys or credentials were also exposed. Restore system security and preserve the proof used for each conclusion.

    What to produce

    Alabama resident and risk assessmentRestricted spreadsheet and decision memo

    Gather first

    • System and data inventory
    • Affected-file query
    • Residence evidence
    • Encryption and key status
    • Access, download and misuse evidence
    • Alabama Act §§8-38-2 and 8-38-4

    How to prepare it

    1. Have the system owner produce a read-only count from the affected source. Deduplicate people, not rows. Keep Alabama residents separate from other states, and keep direct identifiers out of executive summaries.
    2. Map the exposed fields to the statutory combinations. Record whether name or first initial plus last name appears with a covered identifier. For account credentials, verify whether they permit access to an account reasonably likely to contain or obtain sensitive information.
    3. For each data set, document whether it was acquired or is reasonably believed acquired by an unauthorized person and why the evidence supports that view. Consider copying, possession, public posting, use, fraud reports and identity theft reports.
    4. Record encryption status and key or security credential status together. A label such as encrypted is not enough if the key or credential may have been exposed. Assess substantial harm for the relevant people and record the evidence and reviewer.
    5. Have Legal approve the final trigger and notice decision. Keep unknowns visible, assign owners and revisit the decision when the person count, data fields or access evidence changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional affected population
    Training example only. A query identifies 1,140 distinct Alabama resident accounts in a payroll export. The count is a working total, not a real incident or a legal conclusion.
    Fictional field mapping
    Name plus bank-account number and access code appears in the sample. Privacy records the source columns, masking applied in the workbook and how the system owner validated the query.
    Fictional acquisition evidence
    Cloud audit records show an external download from an unrecognized session. The team records the session ID and time range, then asks forensics to verify whether the transferred file contained the mapped rows.
    Fictional harm and key review
    The relevant account credential was in the export. Security confirms that the credential was not encrypted separately; Legal records the likely-harm analysis and the current gaps before the final decision.

    Check before handing it over

    Every resident count can be reproduced from a named source, and every notice or no-notice conclusion has a documented field mapping, acquisition analysis, harm rationale and reviewer.

    Send Legal the resident-count methodology and evidence-backed decision memo. Limit access to row-level personal information.

  3. 03

    Set the legal route and recipient matrix

    Who Privacy counsel + Compliance + incident commander When As soon as facts support an initial decision; revisit when counts or scope change

    For each affected state, list its trigger, clock, regulator, notice content and delivery method. Separately check HIPAA, GLBA, FTC health-breach rules, federal agency contracts and any other applicable sector requirement. If relying on Alabama’s federal or state exemption, document the applicable rule and confirm that the organization maintains its procedures, gives the required individual notice and timely sends a copy to the Alabama Attorney General when more than 1,000 people are notified. Keep a signed written no-notice determination and its supporting record for at least five years.

    What to produce

    Alabama legal route and exemption matrixLegal decision matrix

    Gather first

    • Resident counts by state
    • Data category map
    • Service and sector inventory
    • Federal and state notification rules
    • Contracts
    • Alabama Act §§8-38-5 to 8-38-12

    How to prepare it

    1. Create one row per jurisdiction and affected population. Record the law or rule, trigger, clock-start event, outside deadline, required recipients, content, channel, threshold and the owner responsible for counsel’s sign-off.
    2. Check federal and state sector requirements separately. An Alabama exemption is not automatic: identify the rule that governs, the procedures maintained under it, the individual notices it requires and whether a copy must still go to the Alabama Attorney General for more than 1,000 individuals.
    3. Record the Alabama population that requires notice. More than 1,000 also triggers Attorney General reporting and, when discovered at a single time, notice to nationwide consumer reporting agencies. Treat those as separate rows and assign separate senders.
    4. Compare contract, cyber-insurance and customer obligations. Keep their deadlines visible even when they are shorter than the statute. Do not use an insurance notice as a substitute for a regulator notice.
    5. Have privacy counsel approve the route and the clock for each population. Preserve the source text, calculation, assumptions and the next review date.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional Alabama row
    Training example only. Trigger: covered entity determination of a breach reasonably likely to cause substantial harm. Recipients: affected residents. Outside limit: 45 days, with notice as expeditiously as possible and without unreasonable delay. Owner: Privacy counsel.
    Fictional regulator row
    Training example only. Alabama residents requiring notice: 1,140. Attorney General notice: required because the count exceeds 1,000. Consumer reporting agencies: separate review because more than 1,000 people were discovered at one time.
    Exemption question
    Name the specific federal or state notification regime and test every statutory condition. Leave the row open until counsel confirms that required procedures and resident notices are maintained and an Attorney General copy will be sent when required.
    Parallel obligations
    Add other affected states, HIPAA or GLBA rules, FTC Health Breach Notification Rule coverage, customer contracts and any federal contract incident clause only after the responsible specialist verifies applicability.

    Check before handing it over

    A reviewer can see all clocks and recipients at a glance and can trace any claimed exemption to each condition, responsible owner and supporting source.

    Send the signed jurisdiction matrix to the incident commander and Communications. Reopen it when population, data type or sector coverage changes.

  4. 04

    Prepare and send notices through separate review paths

    Who Privacy + Communications + Legal + customer support When As expeditiously as possible; no later than the applicable 45-day limit

    Draft the resident notice with the date or estimated range, a clear description of the sensitive information acquired, steps taken to restore security, practical identity-theft protections and a working contact route. Have Legal verify each factual claim and the contact address before release. If more than 1,000 Alabama residents must be notified, file the Attorney General notice with the event synopsis, approximate Alabama count, free services and instructions, and a named contact. If circumstances require notice to more than 1,000 people at one time, notify nationwide consumer reporting agencies without unreasonable delay about notice timing, distribution and content. Direct notice is by letter or email to the address in the organization’s records. Use substitute notice only when a statutory condition is met, and include a 30-day website notice plus print and broadcast media in the affected urban and rural areas unless the Attorney General approves another form.

    What to produce

    Alabama notice packet and approvalsNotice drafting pack

    Gather first

    • Approved resident and data-element counts
    • Timeline and containment facts
    • Contact details
    • Free services and enrollment instructions
    • Alabama Act §§8-38-5 to 8-38-7
    • Current Attorney General form

    How to prepare it

    1. Draft one plain-language resident notice from confirmed facts. Include the date or estimated date range, the sensitive information acquired, actions taken to restore security and confidentiality, steps people can take to protect themselves and a contact route that is staffed.
    2. Prepare the Attorney General submission separately. Include an event synopsis, approximate number of affected Alabama individuals, free services and how to use them, and the name, address, telephone and email of the contact person. Mark confidential material according to current instructions.
    3. If the count is above 1,000, prepare the consumer-reporting-agency communication on timing, distribution and content. Confirm the exact recipient list and transmission method with Legal.
    4. If direct notice is not feasible, record the precise statutory ground. For substitute notice, plan a conspicuous 30-day website notice and print and broadcast media in affected urban and rural areas. Obtain Attorney General approval before using an alternative form.
    5. Use a fact checker independent of the drafter. Legal approves legal content, Security confirms mitigation statements, Privacy confirms data fields and counts, Communications checks readability, and Support verifies contact instructions before release.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional resident notice opening
    Training example only: “On May 6, 2026, we learned that an unauthorized person may have downloaded a payroll file between May 5 and May 6. The file contained your name and bank-account access details. We disabled the link and began an independent investigation.” Replace every date, fact and data type with approved incident facts before use.
    Required content check
    Date or estimated range | Information acquired | General security-restoration actions | Identity-theft protection steps | Working inquiry contact. Legal checks every item against §8-38-5(d).
    Fictional Attorney General fields
    Training example only. Approximate Alabama residents: 1,140. Free service: none approved yet, so the draft is incomplete. Contact person, mailing address, telephone and monitored email: pending Privacy and Communications approval.
    Release approvals
    Privacy validates the person file and data description. Security validates the containment language. Legal signs the statutory content and recipient list. Communications tests readability. The release owner records version, approval time and send window.

    Check before handing it over

    The signed notice pack contains only substantiated claims, meets the required content checklist and has a distinct approval record for residents, the Attorney General and consumer reporting agencies.

    Give the approved release package to the named notice vendor and retain the exact version and delivery schedule.

  5. 05

    Reconcile delivery, preserve the record and close gaps

    Who Privacy operations + Customer support + Internal audit When During delivery and after the last required notice

    Reconcile the final notice population against the approved resident file. Preserve returned mail, email failures, website capture, call-center scripts, provider handoffs, regulator acknowledgments and supplements. Track later discoveries as a new decision, not an informal spreadsheet edit. Keep the investigation and the five-year retention record together. Assign corrective work to named owners with dates, then brief management on the systemic risks and the safeguards changed.

    What to produce

    Alabama delivery and corrective-action registerDelivery and action tracker

    Gather first

    • Approved notice version
    • Final recipient file
    • Mail and email results
    • Regulator receipts
    • Call-center and service records
    • Investigation closeout

    How to prepare it

    1. Freeze a dated copy of the final recipient population. Record the data extract, deduplication method, Alabama-residency rule and approvals. Keep restricted person-level data outside the broad corrective-action tracker.
    2. For each channel, log the approved notice version, planned and actual send dates, count attempted, count delivered, returned mail, email failures and the owner for follow-up. Preserve sample proofs and provider reconciliation reports.
    3. Log regulator and consumer-reporting-agency submissions separately. Record submission time, receipt or confirmation, confidentiality marking, supplements and the next owner action.
    4. Turn each root cause into a measurable fix with a named accountable executive, implementation owner, due date, validation evidence and retest date. Prioritize recurring or systemic failures and report them to management.
    5. Close only when the final population reconciles, required notices and supplements are evidenced, exceptions have owners, evidence is retained and open remediation has accepted owners and dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional delivery row
    Training example only. Version AL-NOTICE-v3 approved 12 May 2026. Mail file: 1,140 unique Alabama residents. Vendor accepted 1,138 records; two address exceptions assigned to Privacy Operations. Do not treat vendor acceptance as successful delivery.
    Fictional regulator receipt
    Training example only. Alabama Attorney General web-form confirmation saved as IR-AL-2026-014/REG-01. Submission time, filer, confirmation number and confidential attachment list recorded in the restricted evidence index.
    Fictional remediation
    Root cause: public export link lacked an expiry. Owner: payroll platform VP. Fix: disable anonymous exports, add short-lived authenticated links and alert on bulk download. Evidence: approved configuration, negative access test and a 30-day monitoring review.
    Executive closeout
    Summarize confirmed scope, notice count, unresolved uncertainty, service impact, regulator exchanges and corrective actions. Label estimates, route privilege-sensitive advice to counsel and avoid including personal rows in the board copy.

    Check before handing it over

    A replacement owner can prove what was sent, to whom, which records failed, how the regulator was contacted and whether each agreed control change actually worked.

    Give owners their assigned corrective actions and schedule the retest. Keep the incident evidence in its approved retention location.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes