Law / United States / Arkansas

Arkansas

19 of 21 named instruments researched to a stage, across five of the ten areas of law we track: 17 in force, 1 blocked by a court and 1 no longer in force. As of .

When each starts14 of 19 carry a date, 5 do not. Earlier is before 2014.
Before 2014: 4 instruments (4 in force) earlier 2014: 0 instruments 2015: 0 instruments ’15 2016: 0 instruments 2017: 0 instruments 2018: 0 instruments 2019: 0 instruments 2020: 0 instruments ’20 2021: 0 instruments 2022: 0 instruments 2023: 2 instruments (1 in force, 1 no longer in force) 2024: 0 instruments 2025: 6 instruments (5 in force, 1 blocked by a court) 2026: 2 instruments (2 in force) ’26 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law 4
  2. Privacy law 2
  3. Scraping law 3
  4. Cybersecurity law 5
  5. Communications law not researched
  6. Content moderation law not researched
  7. Product and AI liability law not researched
  8. Digital accessibility law not researched
  9. Age gating law 5
  10. Reuse law

Case lawPremium data

Our analysis of Arkansas law draws on 4 court rulings.

Which laws the rulings read, and each ruling, are premium data, in the Plus, Pro and Enterprise plans.

  • No current case law for Arkansas AI law
  • No current case law for Arkansas privacy law
  • No current case law for Arkansas scraping law
  • No current case law for Arkansas cybersecurity law
  • No current case law for Arkansas communications law
  • No current case law for Arkansas content moderation law
  • No current case law for Arkansas product and AI liability law
  • No current case law for Arkansas digital accessibility law
  • Age gating law: 4 court rulings
  • No current case law for Arkansas reuse law

See the plansSign in

AI law4 instruments, 4 in force

Research summary (379 words)

Arkansas has no general AI-transparency or chatbot-disclosure statute and no comprehensive AI-risk-management framework. Four narrower Acts from the 2025 Regular Session add activity-specific duties or a default ownership rule on private actors; a fifth, Act 848 (HB 1958), the Arkansas Public Entity AI Policy Act, binds only public entities' own use of AI and is not catalogued as an instrument here.

Act 159 (HB 1071) amends the Frank Broyles Publicity Rights Protection Act of 2016 to bring an AI-generated reproduction of a person's photograph, voice, or likeness within the Act's existing right of publicity. Act 827 (HB 1529) creates both a criminal offense and a civil cause of action for a nonconsensual sexual deepfake, and reaches the developer of the image-generation technology used to create it where the developer lacked reasonable safeguards against that misuse.

Act 927 (HB 1876) assigns default ownership of a generative AI tool's output: the person who supplies the input or directive owns the generated content, the person who supplies the training data owns the resulting trained model, and where an employee does either within the scope of employment at the employer's direction, the employer owns the result instead.

Act 977 (HB 1877) extends the state's child-exploitation statutes to a computer-generated image indistinguishable from a real child, with a safe harbor for good-faith AI-safety adversarial testing.

None of these four Acts states an explicit commencement date beyond the governor's signature date, so each is recorded here as in force with the commencement date confirmed absent rather than invented; other 2025 Regular Session Acts carrying no emergency clause, including Act 900 and Act 901, are recorded elsewhere as commencing .

Commentary describes an Arkansas requirement to disclose an AI-generated deepfake of a candidate in election communications, reportedly enacted in 2024 with a satire and parody exemption, but its Arkansas Code citation is not confirmed in any primary text located and it is not catalogued for that reason.

In the absence of an AI-specific bot-disclosure or transparency statute, Arkansas's general Deceptive Trade Practices Act, Ark. Code Ann. § 4-88-107, prohibits deceptive and unconscionable trade practices generally and could reach an undisclosed AI-generated misrepresentation to a consumer, but as a general consumer-protection statute rather than an AI-specific measure it is not catalogued as an instrument here.

AI prohibited practices

Act 159 of 2025 (HB 1071), AI-Generated Replicas Amendment to Publicity Rights Act

Ark. Code Ann. §§ 4-75-1103, 4-75-1110, 4-75-1112session law text, Arkansas General Assembly

In force since . Binds public and private bodies.

What this law does

Act 159 amends the Frank Broyles Publicity Rights Protection Act of 2016 so that the Act's existing definitions of "likeness" and "photograph" expressly include a reproduction generated through artificial intelligence, and adds a new definition of "voice" that reaches a simulation of an individual's voice, including an AI-generated simulation, whether or not it contains the person's actual voice.

It also narrows a safe harbor for a system or network provider, so that a provider loses that protection once it has actual knowledge that a photograph, voice, or likeness on its system violates the Act. Approved .

What it requires

Act 827 of 2025 (HB 1529), Unlawful Creation or Distribution of Deepfake Visual Material

Ark. Code Ann. §§ 5-14-139, 16-118-119session law text, Arkansas General Assembly

In force since . Binds public and private bodies.

What this law does

Act 827 creates the offense of unlawful creation or distribution of deepfake visual material: without the depicted person's consent, knowingly creating or distributing an AI-generated or AI-modified visual depiction that an ordinary person would conclude shows an identifiable person nude or engaged in sexual conduct. A first offense is a Class A misdemeanor and a second or subsequent offense is a Class D felony.

The Act separately creates a civil cause of action: a person injured by a violation may sue whoever created the deepfake or the provider or developer of the image-generation technology used to create it, and the Attorney General may separately sue a provider or developer of prompt-based image-generation technology used to create the material if that provider or developer lacked reasonable safeguards against generating it.

Ark. Code Ann. § 5-14-139(d) exempts a provider of, or an affiliate of a provider of, a telecommunication service, information service, or cable service as defined in 47 U.S.C. § 153, for content provided by another person. Approved .

What it requires

Act 977 of 2025 (HB 1877), AI-Generated Child Sexual Abuse Material Amendments

Ark. Code Ann. §§ 5-27-302, 5-27-304, 5-27-601 to 5-27-603, 5-27-609session law text, Arkansas General Assembly

In force since . Binds public and private bodies.

What this law does

Act 977 amends the Arkansas Protection of Children Against Exploitation Act of 1979 and the state's computer-crimes-against-minors chapter to add "computer generated" (produced, adapted, or modified, in whole or in part, through artificial intelligence) alongside the existing categories of prohibited child sexual abuse material, and adds "indistinguishable," a visual or print medium that an ordinary person viewing it would conclude depicts an actual child, excluding a drawing, cartoon, sculpture, or painting.

Electronic facilitation of child sexual abuse, which now reaches this computer-generated material, is a Class B felony under section 5-27-603; the felony class for the amended distributing, possessing, or viewing offense at section 5-27-602 is not stated in the text of this Act.

The Act carves out an interactive computer service for content supplied by another party, a law-enforcement investigation exemption, and a safe harbor for a provider or developer whose computer-generated material was produced through adversarial testing conducted in good faith to prevent, detect, or mitigate the risk of an AI system generating this material, so long as the testing was not for personal, exploitative, or unrelated purposes. Approved .

What it requires

AI training data

Act 927 of 2025 (HB 1876), Generative AI Ownership of Model Training and Content

Ark. Code Ann. § 18-4-101session law text, Arkansas General Assembly

In force since . Binds public and private bodies.

What this law does

Act 927 adds Ark. Code Ann. § 18-4-101, assigning default ownership of a generative artificial intelligence tool's output.

Absent a contrary agreement, the person who provides the input or directive to the tool owns the content it generates, and the person who provides the data or input used to train the tool owns the resulting trained model, provided the content or training data does not infringe an existing copyright or other intellectual property right and, for a trained model, that the training data was lawfully acquired and ownership was not otherwise transferred by contract.

Where an employee uses the tool to generate content or train a model within the scope of employment and under the employer's direction and control, the employer owns the result instead. The section grants no ownership over infringing content regardless of AI use. Approved .

What it requires

Privacy law2 instruments, 2 in force

Research summary (165 words)

Arkansas has no comprehensive personal-data privacy law. A signed, dated comprehensive Arkansas act is sometimes attributed to this state in error; those dates belong to Tennessee's Information Protection Act and are not repeated here.

Arkansas's general privacy statute is the Personal Information Protection Act (PIPA), Ark. Code Ann. section 4-110-101 et seq., a security-practices and breach-notification law that names faceprint and voiceprint as biometric data elements with no photograph- or recording-derived exclusion, but creates no capture-consent, retention, or destruction duty, and no data-subject rights.

PIPA borrows the Arkansas Deceptive Trade Practices Act's enforcement mechanism for Attorney General action; whether that Act's own private-suit provision also reaches a PIPA violation is not established and is recorded here as an open question rather than a decided finding.

The Arkansas Children and Teens' Online Privacy Protection Act (Act 952 of 2025, Ark. Code Ann. sections 4-88-1501 to 4-88-1505), in force since , separately sets duties for online services that collect personal information from children and teens.

Breach notification

Arkansas Personal Information Protection Act, breach notification and security

Ark. Code Ann. secs. 4-110-101 to 4-110-108official Arkansas General Assembly session-law text

In force. Binds public and private bodies.

What this law does

PIPA requires an individual, business, or state agency that acquires, owns, or licenses personal information of an Arkansas resident to implement and maintain reasonable security procedures, dispose of records properly, and notify affected Arkansas residents of a breach of security without unreasonable delay.

If a breach affects more than 1,000 individuals, the person or business must also notify the Attorney General, at the same time as consumer notice or within 45 days of determining a reasonable likelihood of harm, whichever is first.

Biometric data, including faceprint and voiceprint, is one of the data elements that makes information personal information for these purposes, named with no exclusion for data derived from a photograph or recording, but PIPA imposes no separate capture-consent, retention, or destruction duty on biometric data as such.

PIPA violations are enforced by the Attorney General under the Arkansas Deceptive Trade Practices Act; whether that Act's own private-suit provision, section 4-88-113, also arms a private plaintiff for a PIPA violation specifically was not confirmed from primary text and is left as an open question rather than a decided finding. The provisions this entry describes came into force on different days.

What it requires

Data subject rights

Arkansas Children and Teens' Online Privacy Protection Act (Act 952 of 2025), consent, notice, deletion and security duties for children's and teens' personal information

Ark. Code Ann. secs. 4-88-1501 to 4-88-1505 (Act 952 of 2025)official Arkansas General Assembly session-law text, Act 952 of 2025 (HB 1717)

In force since . Binds private bodies.

What this law does

Act 952 of 2025 adds Subchapter 15 to Chapter 88 of Title 4 of the Arkansas Code and names it the Arkansas Children and Teens' Online Privacy Protection Act. It takes effect on . It binds an operator of a website, online service, online application or mobile application that is directed at children or teens, or that has actual knowledge it is collecting personal information from children or teens. A child is an individual twelve years of age or younger.

A teen is an individual located in Arkansas who is thirteen years of age or older and younger than seventeen. The operator must obtain consent for the collection, use or disclosure of a teen's personal information from the teen or the teen's parent, except for purposes the Act lists. The operator must give clear and conspicuous notice of what information it collects from children or teens, the purpose of processing it, and its disclosure practices.

The parent of a child must be able to request deletion of the child's account, content or information and to refuse further collection of the child's personal information. A teen must be able at any time to delete personal information collected from the teen and to challenge its accuracy and have inaccurate information corrected. The operator may not collect a child's or teen's personal information for targeted advertising to children or teens, or let another person do so.

It may collect a child's or teen's personal information only where the collection is consistent with the context of a particular service or its relationship with the child or teen, or is required or specifically authorized by law. It may not retain that information for longer than is reasonably necessary to fulfill a transaction or provide a service the child, teen or parent requested, except as required for the safety or integrity of the service or specifically authorized by law.

The operator must establish, implement and maintain reasonable security practices to protect the personal information of children and teens. The Act does not require an operator to collect age information it is not already collecting or to implement age verification. The Attorney General has exclusive authority to enforce the Act, and it creates no private right of action.

What it requires

Scraping law3 instruments, 3 in force

Research summary (256 words)

Arkansas adds its own computer-crime chapter on top of the federal Computer Fraud and Abuse Act.

Ark. Code Ann. section 5-41-103 makes it a Class D felony to intentionally access a computer to defraud, extort, or obtain money, property, or a service by false pretense; section 5-41-104 makes intentional, unauthorized access, alteration, or disruption a misdemeanor that escalates to a Class D felony once the resulting loss or damage reaches two thousand five hundred dollars; and section 5-41-203 separately criminalizes knowingly and without authorization interfering with another person's access to a computer, or using or accessing one, with an affirmative defense for a reasonable, good-faith belief of authorization.

None of the three sections defines "without authorization" beyond ordinary usage, and no Arkansas case applying any of them to a scraping or automated-collection fact pattern was located.

A section sometimes confused with this group, section 5-41-108, is captioned "Unlawful computerized communications" but in fact criminalizes threatening or obscene electronic messages sent to harass a specific person; it has no bearing on unauthorized computer access or automated collection and is not catalogued here.

Arkansas has published no free official full-text edition of its own consolidated Code, so these sections are cited to a commercial legal-reference site's copy, current as of , which states no original enactment or amendment date; each is recorded as in force with the commencement date confirmed absent rather than invented.

No Arkansas statute assigns robots.txt any independent legal weight, and terms-of-service enforceability rests on ordinary Arkansas contract law, untested against scraping specifically.

Computer misuse

Computer fraud

Ark. Code Ann. § 5-41-103Arkansas Code, as published by FindLaw

In force since . Binds public and private bodies.

What this law does

A person commits computer fraud by intentionally accessing, or causing to be accessed, any computer, computer system, or computer network for the purpose of devising or executing a scheme to defraud or extort, or of obtaining money, property, or a service through a false or fraudulent intent, representation, or promise.

The offense does not turn on whether the access itself was authorized, only on the fraudulent or extortionate purpose behind it, so ordinary automated access to a public page for a non-fraudulent purpose falls outside this section. Computer fraud is a Class D felony.

What it requires

Computer trespass

Ark. Code Ann. § 5-41-104Arkansas Code, as published by FindLaw

In force since . Binds public and private bodies.

What this law does

A person commits computer trespass by intentionally and without authorization accessing, altering, deleting, damaging, destroying, or disrupting any computer, computer system, computer network, computer program, or data.

The offense is graded by loss or damage caused: a Class C misdemeanor for a first violation causing none, rising to a Class B misdemeanor for a repeat violation causing none or a violation causing less than five hundred dollars, a Class A misdemeanor between five hundred and two thousand five hundred dollars, and a Class D felony at two thousand five hundred dollars or more. The statute requires both intent and a lack of authorization.

What it requires

Unlawful interference with access to computers; unlawful use or access of computers

Ark. Code Ann. § 5-41-203Arkansas Code, as published by FindLaw

In force since . Binds public and private bodies.

What this law does

A person commits unlawful interference with access to computers by knowingly and without authorization interfering with, denying, or causing the denial of access to or use of a computer, system, or network to a person who has the duty and right to use it, a Class A misdemeanor.

Separately, a person commits unlawful use or access to computers by knowingly and without authorization using, accessing, attempting to access, or causing access to be gained to a computer, system, network, telecommunications device, telecommunications service, or information service, also a Class A misdemeanor, rising to a Class C felony where either violation is committed to devise or execute a scheme to defraud or illegally obtain property.

It is an affirmative defense that the person reasonably believed they were authorized and acting within the scope of that authorization, or that the person able to consent would have authorized the access; a defendant who intends to raise this defense must give the prosecuting attorney written notice at least fourteen calendar days before trial or hearing.

This section is sometimes cited under the caption "unlawful computerized communications," which is instead the name of a different, unrelated section, Ark. Code Ann. § 5-41-108, a harassment statute covering threatening or obscene electronic messages and having no bearing on unauthorized computer access.

What it requires

Cybersecurity law5 instruments, 5 in force

Research summary (422 words)

Arkansas's product-security and cyber-resilience posture rests on one enacted state statute reaching software or systems generally: the Personal Information Protection Act's reasonable-security duty, Ark. Code Ann. section 4-110-104(b), which requires a person or business, a term defined to include a state agency, that acquires, owns, or licenses personal information about an Arkansas resident to implement and maintain reasonable security procedures and practices appropriate to the nature of the information.

This duty is legally distinct from, though enacted in the same 2005 Act as, the Personal Information Protection Act's breach-notification duty at section 4-110-105, which is Arkansas's privacy row and is not repeated here.

No Arkansas statute was located setting security requirements a software product or connected device must meet before or after being placed on the market, a private-sector duty to report a vulnerability or a security incident to an authority, or a private-sector cyber-resilience regime; the public-entity reporting, policy and cyber response duties are filed as rows of their own with no activity flag.

Arkansas has not enacted the NAIC Insurance Data Security Model Act as its own insurance-licensee-scoped statute; the NAIC's own 2026 state-adoption tracker records Arkansas's citation as the general Personal Information Protection Act together with Ark. Code Ann. section 25-1-128, rather than a dedicated insurer security-program law, so no insurance-sector absence document is filed for this jurisdiction.

Ark. Code Ann. sections 25-26-301 to 25-26-306, the Arkansas Cyber Initiative Act, and section 25-1-128 bind only the state's own technology-resource policy and a voluntary economic-development cybersecurity alliance; neither imposes a duty on a private software vendor, and the public entity policy duties of section 25-1-128 are filed as a row of their own.

The reasonable-security duty is enforced only by the Attorney General under the Arkansas Deceptive Trade Practices Act, and no published enforcement record specific to a Personal Information Protection Act reasonable-security action was located. A public entity that experiences a security incident shall disclose, in writing, an initial report of the known facts of the security incident to the Legislative Auditor within five business days after learning of the security incident.

A public entity shall develop a cybersecurity policy for all technology resources of the public entity based on the standards and guidelines set by the State Cybersecurity Office. All municipalities, counties, and school districts in Arkansas shall participate in the Arkansas Self-Funded Cyber Response Program, administered by the Arkansas Cyber Response Board.

A state agency shall comply with the governance standards, policies, and procedures established by the State Cybersecurity Office under the Arkansas Cybersecurity Act of 2025.

Sector security regimes

Arkansas Cybersecurity Act of 2025, state agency compliance with State Cybersecurity Office governance standards

Arkansas Cybersecurity Act of 2025, Ark. Code Ann. section 25-4-130, Act 489 of 2025Text of Act 489 of 2025, the Arkansas Cybersecurity Act of 2025, published by the Arkansas General Assembly

In force. Binds government bodies.

What this law does

A state agency means a department, agency, division, board, or commission within the executive branch of the state government. The State Cybersecurity Office shall be responsible for directing and managing all functions related to state cybersecurity and information security for each state agency. The State Cybersecurity Office shall establish cybersecurity governance policies, procedures, and standards, including cybersecurity and data breach notification.

A state agency shall comply with the governance standards, policies, and procedures established by the State Cybersecurity Office. Cybersecurity personnel and personnel with information security job functions within each state agency shall functionally report to the State Cybersecurity Office. Arkansas Legislative Audit reports that Act 489 created the State Cybersecurity Office as part of the Department of Shared Administrative Services.

What it requires

Arkansas Self-Funded Cyber Response Program Act, mandatory participation and minimum cybersecurity criteria

Arkansas Self-Funded Cyber Response Program Act, Ark. Code Ann. sections 21-2-801 to 21-2-809, Act 846 of 2023Text of Act 846 of 2023

In force. Binds government bodies.

What this law does

All municipalities, counties, and school districts in Arkansas shall participate in the Arkansas Self-Funded Cyber Response Program. The Arkansas Cyber Response Board shall establish minimum cybersecurity criteria for participating governmental entities. A participating governmental entity shall have twelve months to become compliant with the minimum cybersecurity criteria established by the board.

Failure to comply with the minimum cybersecurity criteria may result in the board establishing lower program coverage amounts. To sustain program coverage, a participating governmental entity shall procure an audit of its books and records for each fiscal year, including an information systems audit, review, or assessment performed by Arkansas Legislative Audit.

Arkansas Legislative Audit reports that Act 846 of 2023 authorized formation of the Arkansas Cyber Response Board to oversee the Arkansas Self-Funded Cyber Response Program. The board shall promulgate rules and procedures for use of the program that generally align with a procedure under which a participating governmental entity notifies the cyber response contact designated by the board upon discovery of a cyberattack.

What it requires

Public entity cybersecurity policy and training duties (Act 504 of 2023, as amended by Act 848 of 2025)

Public entity cybersecurity policy, Ark. Code Ann. section 25-1-128(b), Act 848 of 2025Text of Act 848 of 2025 amending Arkansas Code section 25-1-128

In force. Binds government bodies.

What this law does

A public entity means an instrumentality funded in whole or in part by taxpayer funds. A public entity shall develop a cybersecurity policy for all technology resources of the public entity based on the standards and guidelines set by the State Cybersecurity Office. The cybersecurity policy duty does not apply to political subdivisions of the state. A public entity shall develop a training program for all employees concerning the technology resources policy and the cybersecurity policy.

A political subdivision of the state is not required to develop a training program under the section for a cybersecurity policy. Each state entity shall submit a cybersecurity policy for approval to the State Cybersecurity Office by October 1 of each even-numbered year. A public entity, except for a political subdivision of the state, shall create a disciplinary procedure for a violation of its cybersecurity policy in consultation with the State Cybersecurity Office.

Arkansas Legislative Audit reports that Act 504 of 2023 requires public entities to develop policies pertaining to the authorized use of technology resources and addressing cybersecurity concerns.

What it requires

Security baseline statutes

Arkansas Personal Information Protection Act, reasonable security procedures

Ark. Code Ann. section 4-110-104(b)Official Arkansas General Assembly session-law text, Act 1526 of 2005 (SB1167), sec. 4 (original enactment of Ark. Code Ann. sec. 4-110-104)

In force since . Binds public and private bodies.

What this law does

A person or business that acquires, owns, or licenses personal information about an Arkansas resident must implement and maintain reasonable security procedures and practices appropriate to the nature of the information, to protect the personal information from unauthorized access, destruction, use, modification, or disclosure.

This reasonable-security duty sits in the same Act, and the same code section, as the Act's separate duty to take all reasonable steps to destroy or arrange for the destruction of a customer's records containing personal information that is no longer to be retained, and it is legally distinct from the Act's breach-notification duty at section 4-110-105, already researched as this jurisdiction's privacy row.

"Business" is defined to include a state agency, so the duty reaches Arkansas's own state agencies as well as private persons and businesses. The reasonable-security duty has not been amended since the Act's original 2005 enactment: the only later amendment to this subchapter located, Act 1030 of 2019, added biometric data elements to the definition of personal information and separately amended the breach-notification section, and left this duty's own text untouched.

Act 1526 of 2005 itself states no day-precise commencement date and carries no emergency clause, so it took effect on the general effective date the Arkansas Attorney General set for acts of the 2005 Regular Session that carried neither, .

The Act names no dedicated regulator and no penalty amount of its own for a violation of this duty; any violation of the subchapter is punishable only by action of the Attorney General under the Arkansas Deceptive Trade Practices Act, and whether that Act's own private-suit provision also arms a private plaintiff for a violation of the reasonable-security duty specifically was not confirmed from primary text.

What it requires

Vulnerability and incident reporting

Public entity security incident report to the Legislative Auditor

Public entity security incident report, Ark. Code Ann. section 10-4-429, Act 260 of 2021Text of Arkansas Code section 10-4-429 as added by Act 260 of 2021

In force. Binds government bodies.

What this law does

A public entity means an entity of the state, a political subdivision of the state, or a school. A security incident means any compromise of the security, confidentiality, or integrity of an information system maintained by a public entity, a contractual provider of an information system that contracts with a public entity, or other computer-related services of a public entity, caused by unauthorized access, destruction, or acquisition of data.

A public entity that experiences a security incident shall disclose, in writing, an initial report of the known facts of the incident to the Legislative Auditor within five business days after learning of the incident. A public entity shall provide regular updates of the security incident to the Legislative Auditor until the investigation of the incident is closed. The Legislative Auditor shall maintain a list of all security incidents reported by a public entity.

If the Legislative Auditor believes an incident significantly compromises citizens' data, creates a significant security concern, or involves significant theft, the Legislative Auditor shall notify a list of state officials beginning with the Governor. A report, update, notification, or list created or maintained under the section is exempt from disclosure under the Freedom of Information Act of 1967. The section was amended by Act 175 of 2023, effective .

Arkansas Legislative Audit reports that 217 cybersecurity incidents were reported to it by 124 public entities from through .

What it requires

Age gating law5 instruments, 3 in force, 1 blocked by a court, 1 no longer in force

Research summary (101 words)

Arkansas requires commercial websites where more than one third of content is harmful to minors to verify users are 18 or older under a 2023 law that remains in effect. Arkansas has enacted three social media minor access laws since 2023, the original Social Media Safety Act and two 2025 acts strengthening its addictive design rules and adding civil liability for platforms.

Federal courts have blocked all three on First Amendment grounds: the 2023 Act was permanently enjoined and is on appeal to the Eighth Circuit, and the two 2025 Acts took effect in August 2025 but are now preliminarily enjoined.

Adult content age verification (AV)

Act 612 of 2023 (SB66), Protection of Minors from Distribution of Harmful Material Act

Act 612 of 2023 (SB66), codified at Ark. Code Ann. § 4-88-1101 et seq.official act text, Arkansas State Legislature

In force since . Binds private bodies.

What this law does

Makes a commercial entity liable if its website contains a substantial portion of material harmful to minors, as the applicability criteria define it, and it fails to perform reasonable age verification using a government issued ID, digital identification, or a commercially reasonable method meeting identity assurance level 2.

What it requires

Social media and minors

Act 689 of 2023 (SB396), Social Media Safety Act

Act 689 of 2023 (SB396), codified at Ark. Code Ann. § 4-88-1401 et seq.official act text, Arkansas State Legislature

No longer in force. since struck down Struck down by a court on . The page is kept as a record.

Binds private bodies.

What this law does

Would have required social media companies to use a third party vendor to perform reasonable age verification, such as a digitized ID or government issued ID, before allowing account access, and to obtain parental consent for minor accounts.

What it requires

Our analysis of this law draws on 2 court rulings.Premium data

Act 900 of 2025 (SB611), Social Media Safety Act amendments (addictive design)

Act 900 of 2025 (SB611), amending Ark. Code Ann. § 4-88-1401 et seq.official act text, Arkansas State Legislature

Blocked by a court. blocked by a court A court paused enforcement on . An injunction can be lifted, so the duty may return.

Binds private bodies.

What this law does

Amends the Social Media Safety Act to lower the covered minor age from 18 to 16, prohibit addictive design features, require default privacy settings, and disable non-essential notifications between 10 PM and 6 AM. Signed ; most provisions took effect , while the addictive design and notification duties in Section 2 carried a delayed effective date of , one year after enactment.

What it requires

Our analysis of this law draws on 1 court ruling.Premium data

Act 901 of 2025 (SB612), social media platform civil liability

Act 901 of 2025 (SB612), codified at Ark. Code Ann. §§ 4-88-1501 to 4-88-1503official act text, Arkansas State Legislature

In force since partly blocked by a court. Binds private bodies.

What this law does

Creates a private right of action against a social media platform whose design, algorithm, or feature causes a minor to suffer harm such as an eating disorder, suicide or attempted suicide, or platform addiction. Signed and effective with no separate effective date clause.

What it requires

Our analysis of this law draws on 1 court ruling.Premium data

Act 952 of 2025 (HB1717), Arkansas Children and Teens' Online Privacy Protection Act

Act 952 of 2025 (HB1717), adding a subchapter to Ark. Code Ann. Title 4, Chapter 88official act text, Arkansas State Legislature

In force since . Binds private bodies.

What this law does

A child is an individual twelve years of age or younger in Arkansas. A teen is an individual located in Arkansas who is thirteen years of age or older and younger than seventeen.

The duties below apply to an operator of a website, online service, online application or mobile application that has actual knowledge that it is collecting personal information from children or teens. The operator must obtain consent for the collection, use or disclosure of a teen's personal information from the teen or the teen's parent, except for purposes the Act lists.

The operator must provide clear and conspicuous notice of what information it collects from children or teens, the purpose of processing it, and its disclosure practices.

The operator must give the parent of a child the opportunity to request deletion of the child's account, content or information and to refuse further collection of the child's personal information, and to challenge and correct inaccurate information. The operator must give a teen the opportunity at any time to delete personal information collected from the teen, and to challenge the accuracy of that information and have inaccurate information corrected.

The operator must establish, implement and maintain reasonable security practices to protect the confidentiality, integrity and accessibility of the personal information of children and teens.

It is also unlawful for an operator directed at children or teens, or one with actual knowledge that it collects their personal information, to collect that information for targeted advertising to children or teens, to collect it outside the context of a service or the child's or teen's relationship with the operator unless law requires or authorizes it, or to retain it longer than is reasonably necessary to fulfill a transaction or provide a requested service, except as required for the safety or integrity of the service or specifically authorized by law.

The Act does not require an operator to affirmatively collect age information it is not already collecting in the normal course of business, or to implement age-gating or age verification functionality.

The Attorney General has exclusive authority to enforce the Act, and the Act creates no private right of action. A violation of the teen consent duty or of the duties owed to the parent of a child is treated as an unfair or deceptive act or practice under the Deceptive Trade Practices Act.

The Act was approved on . The Act is effective on and after .

What it requires

Where nothing was found1 area of law

These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.

Reuse law

Arkansas has no press-publisher neighbouring right, no compelled platform-to-publisher bargaining code, and no text-and-data-mining opt-out statute. Title 4 of the Arkansas Code (Business and Commercial Law) runs from the Uniform Commercial Code through corporations, partnerships, contracts, business practices, and consumer protection, with no chapter addressing news publishing, copyright, or a neighbouring right in journalism.

No Arkansas bill comparable to California's journalism usage fee proposal or a mandatory bargaining code was located. An aggregator's reproduction of Arkansas news headlines or snippets is governed by federal copyright law and its fair use doctrine, and by Arkansas's own common-law misappropriation doctrine for any residual, non-copyrightable factual reporting, neither of which is Arkansas-specific.

As of .

Reporting clocks that run here18 instruments

The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Arkansas comes first, then the law of the bodies above it that applies here.

Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.

1 hour
Incident notificationsecurity law
4 hours
Incident notificationsecurity law
8 hours
Incident notificationsecurity law
36 hours
72 hours
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
4 business days
Incident notificationsecurity law
5 business days
Incident notificationsecurity law
7 business days
Breach notificationprivacy law
30 days
Incident notificationsecurity law
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
45 days
Breach notificationprivacy law
60 days
Breach notificationprivacy law
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.

The law of Arkansas

5 business days

Public entity security incident report to the Legislative Auditor

Public entity security incident report, Ark. Code Ann. section 10-4-429, Act 260 of 2021security law, in force

The sentence the clocks are read from

When you experience a security incident (any compromise of the security, confidentiality, or integrity of an information system you or a contractual provider maintain, or of your other computer-related services, caused by unauthorized access, destruction, or acquisition of data), give the Legislative Auditor a written initial report of the known facts within five business days after learning of it.

The law of the United States, which applies in Arkansas

1 hour4 hours8 hours24 hours

NRC cyber security event notifications by nuclear power plant licensees

NRC cyber security event notifications, 10 CFR 73.77security law, in force since

The sentences the clocks are read from

Notify the NRC Headquarters Operations Center via the Emergency Notification System within one hour after discovery of a cyberattack that adversely impacted safety-related or important-to-safety functions, security functions, or emergency preparedness functions (including offsite communications), or that compromised support systems and equipment resulting in adverse impacts to those functions.

Also notify within one hour after discovery of a cyberattack that adversely impacted the safety, security, and emergency preparedness functions performed by digital assets described in 10 CFR 73.77(a)(1)(ii).

Notify the NRC Headquarters Operations Center within four hours after discovery of a cyberattack that could have caused such an adverse impact, after discovery of a suspected or actual cyberattack initiated by personnel with physical or electronic access to the systems in scope, or after notifying a local, State, or other Federal agency of an event related to your cyber security program that does not otherwise require notification.

Notify the NRC Headquarters Operations Center within eight hours after receipt or collection of information regarding observed behavior, activities, or statements that may indicate intelligence gathering or pre-operational planning related to a cyberattack against the systems in scope.

Use the site corrective action program to record vulnerabilities, weaknesses, failures and deficiencies in your cyber security program, and the notifications you make, within twenty-four hours of their discovery.

24 hours72 hours

Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA)

6 U.S.C. 681-681g (CIRCIA)security law, enacted, not yet in force

The sentences the clocks are read from

Once the final rule takes effect, report a covered cyber incident to the Agency not later than 72 hours after your organization reasonably believes that the covered cyber incident has occurred.

Once the final rule takes effect, report a ransom payment to the Agency not later than 24 hours after your organization makes the payment, even where the underlying ransomware attack is not itself a covered cyber incident.

Once the final rule takes effect, promptly submit an update to a previously submitted covered cyber incident report whenever substantial new or different information becomes available or a ransom payment is later made, continuing until your organization notifies the Agency that the incident has concluded and been fully mitigated and resolved, and preserve data relevant to the incident or payment under the procedures the final rule establishes.

24 hours5 business days30 days

SEC Regulation SCI: notification of SCI events to the Commission and to members

SEC Regulation SCI SCI event notices, 17 CFR 242.1002(b) and (c)security law, in force since

The sentences the clocks are read from

Upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, begin appropriate corrective action and notify the Commission of the SCI event immediately.

Within 24 hours of that conclusion, submit a written notification to the Commission, made on a good faith, best efforts basis, that describes the SCI event and the systems affected and, to the extent available, your assessment of the market participants potentially affected, the potential impact on the market, and the steps you have taken, are taking or plan to take.

If the SCI event is resolved and the investigation closed within 30 calendar days, submit a final written notification within five business days after resolution. If not, submit an interim written notification within 30 calendar days after the event, and a final one within five business days after resolution and closure.

36 hours

Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers

12 CFR Part 53 (OCC); 12 CFR Part 225, Subpart N (Federal Reserve Board); 12 CFR Part 304, Subpart C (FDIC)security law, in force since

The sentences the clocks are read from

If your organization is a banking organization, notify your primary federal banking regulator, the OCC, the Federal Reserve Board, or the FDIC, whichever supervises it, about a notification incident, as soon as possible and no later than 36 hours after your organization determines that a notification incident has occurred.

A notification incident is the subset of computer-security incidents that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, your ability to serve customers, a business line, or an operation whose failure would threaten the financial stability of the United States, so a computer-security incident that falls short of that threshold does not by itself start this clock.

If your organization is a bank service provider, notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible after your organization determines that it has experienced a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services provided to that banking organization for a period of four hours or more.

This duty carries a standard, as soon as possible, rather than a fixed number of hours to notify by, and that disruption threshold is what engages the duty rather than a period to notify within.

72 hours30 days

Artificial Intelligence Risk Management and Security Act of 2026

S. 5576, 119th Congressfrontier-model AI law, proposed

The sentence the clocks are read from

If you are a developer or provider of a frontier AI model, or an operator of critical infrastructure that uses an AI model to manage industrial control systems or other operational technologies, report any confirmed AI safety incident or AI security incident within 30 days of confirmation, and within 72 hours if the incident poses an imminent threat to national security, critical infrastructure or public safety.

72 hours

NCUA Cyber Incident Notification Requirements for Federally Insured Credit Unions

NCUA Cyber Incident Notification Requirements, 12 CFR 748.1(c)security law, in force since

The sentences the clocks are read from

If your organization is a federally insured credit union, notify the NCUA-designated point of contact of a reportable cyber incident by email, telephone, or another method the NCUA prescribes, so that the NCUA receives the notification as soon as possible and no later than 72 hours after your organization reasonably believes it has experienced a reportable cyber incident.

Where the reportable cyber incident is a disruption of business operations or unauthorized access to sensitive data facilitated through, or caused by, a compromise of a credit union service organization, cloud service provider, or other third-party data hosting provider, or by a supply chain compromise, the NCUA must receive the notification within 72 hours of your organization being notified by the third party if that is sooner.

72 hours30 days

Regulation S-P: incident response program and customer breach notice

17 CFR 248.30(a)(3) to (a)(5)privacy law, in force since

The sentences the clocks are read from

Send the notice as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred, delaying it only for the period the United States Attorney General specifies where the Attorney General determines that notice poses a substantial risk to national security or public safety (17 CFR 248.30(a)(4)(iii)).

Maintain written policies and procedures reasonably designed to require oversight, including through due diligence and monitoring, of service providers, including that a service provider notify you as soon as possible, and no later than 72 hours, after becoming aware of a breach in security resulting in unauthorized access to a customer information system it maintains (17 CFR 248.30(a)(5)(i)).

72 hours

SEC Regulation S-P: service provider oversight and 72-hour breach notice to the covered institution

SEC Regulation S-P service provider oversight and notice, 17 CFR 248.30(a)(5)security law, in force

The sentence the clocks are read from

Make those policies and procedures reasonably designed to ensure that each service provider takes appropriate measures to protect against unauthorized access to or use of customer information, and to notify you as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system the service provider maintains.

4 business days

SEC Cybersecurity Risk Management, Governance, and Incident Disclosure (Regulation S-K Item 106; Form 8-K Item 1.05)

17 CFR 229.106; 17 CFR 249.308 (Form 8-K Item 1.05)security law, in force since

The sentences the clocks are read from

If your organization is an Securities and Exchange Commission (SEC) reporting company, determine, without unreasonable delay after you discover a cybersecurity incident, whether the incident is material, and if it is, file a Form 8-K under Item 1.05 within four business days after you make that determination.

If the information called for in Item 1.05 is not determined or is unavailable when you file, state that in the filing and file an amendment to the Form 8-K within four business days after you determine it or it becomes available.

7 business days30 days

FCC CPNI breach notification rule

47 CFR 64.2011privacy law, in force

The sentences the clocks are read from

After you reasonably determine that a breach of your customers' CPNI has occurred, electronically notify the United States Secret Service and the Federal Bureau of Investigation through the central reporting facility as soon as practicable, and in no event later than seven business days (47 CFR 64.2011(b)).

Do not notify customers or disclose the breach where the relevant investigating agency directs you in writing not to, for an initial period of up to 30 days that the agency may extend (47 CFR 64.2011(b)(3)).

60 days

FTC Health Breach Notification Rule

16 CFR Part 318privacy law, in force since

The sentences the clocks are read from

If you are a vendor of personal health records (an entity that offers or maintains an electronic record of health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual) or a PHR related entity, notify each affected individual who is a citizen or resident of the United States, in plain language and without unreasonable delay, no later than 60 calendar days after you discover a breach of security of unsecured PHR identifiable health information.

Notify prominent media outlets serving a State or jurisdiction, without unreasonable delay and in no case later than 60 calendar days after you discover the breach, when the unsecured PHR identifiable health information of 500 or more of its residents is, or is reasonably believed to have been, acquired during the breach.

If you are a third party service provider, notify the official designated in a written contract by the vendor of personal health records or PHR related entity you serve (or else a senior official of that vendor or entity), without unreasonable delay and in no case later than 60 calendar days after you discover the breach; identify each customer of that vendor or entity whose unsecured PHR identifiable health information has been, or is reasonably believed to have been, acquired during the breach; and obtain acknowledgment that the notice was received.

60 days

HIPAA Breach Notification Rule

45 CFR Part 164, Subpart D (Sections 164.400-164.414)privacy law, in force since

The sentences the clocks are read from

Notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured protected health information.

For a breach of unsecured protected health information involving more than 500 residents of a State or jurisdiction, notify prominent media outlets serving that State or jurisdiction without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

If you are a business associate, notify the covered entity of a breach of unsecured protected health information without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

promptly

CFTC system safeguards: prompt notice to Commission staff of cyber security incidents and targeted threats

CFTC system safeguards notices, 17 CFR 39.18(g), 38.1051(e) and 37.1401(e)security law, in force since

The sentences the clocks are read from

If your organization is a derivatives clearing organization, notify staff of the Division of Clearing and Risk promptly of any hardware or software malfunction, security incident, or targeted threat that materially impairs, or creates a significant likelihood of material impairment of, automated system operation, reliability, security, or capacity, and of any activation of your business continuity and disaster recovery plan.

If your organization is a designated contract market, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and significant systems malfunctions and activations of your business continuity-disaster recovery plan.

If your organization is a swap execution facility, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and material system malfunctions and activations of your business continuity-disaster recovery plan.

immediately

Coast Guard Cybersecurity in the Marine Transportation System: reportable cyber incidents

Coast Guard reportable cyber incident reporting, 33 CFR 101.620(b)(7) and 101.615security law, in force since

The sentence the clocks are read from

Evidence of sabotage, subversive activity, or an actual or threatened cyber incident involving or endangering any vessel, harbor, port, or waterfront facility must be reported immediately to the Federal Bureau of Investigation, the Cybersecurity and Infrastructure Security Agency (for any cyber incident), and the Captain of the Port, or to their respective representatives.

Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

This page covers the instruments LexLint has researched to a stage. Instruments named in the law library but not yet researched are counted in the head and are not listed here. Every entry carries its own primary source on its note page. This is a research index, not legal advice.