Arkansas

Plain:Verify the age of every account holder using a reasonable method (originally requiring a third-party age-verification vendor) before allowing use of the platform.

Engineering:Age-verify all users at account creation via an approved method to identify minors under 18. Provision permanently enjoined, not operative.

Statute’s own ages: Blocked minors under 18 from accounts without parental consent ('minor' = under 18).

Plain:Obtain a parent's or guardian's consent before a minor under 18 could create an account on a covered platform.

Engineering:Gate minor account creation on verified parental consent. Provision permanently enjoined, not operative.

Statute’s own ages: Applied to minors under 18.

Plain:Use a reasonable method to verify that account holders are at least 16, and implement technological measures to prevent circumvention of that age verification.

Engineering:Age-verify users at account creation to confirm they are 16 or older, and add anti-circumvention controls; identify accounts belonging to minors under 16 for the Act's protective duties.

Statute’s own ages: Covered minor = under 16 (Act 900 lowered the threshold from Act 689's under-18).

Plain:Do not use design practices that evoke addiction or compulsive behavior in minor users, including notifications, recommended content, an artificial sense of accomplishment, or engagement with online bots that appear human.

Engineering:For minor accounts, remove or disable engagement-maximizing mechanics the statute frames as addictive/compulsive: push-notification loops, algorithmic recommended content, streak/achievement gamification, and interactions with human-appearing bots. Enjoined 2026-04-20 as unconstitutionally vague, not operative.

Statute’s own ages: Applies to minor users (under 16).

Plain:Do not send non-safety notifications to minor users between 10 p.m. and 6 a.m. Central Standard Time, unless a parent or guardian modifies the setting.

Engineering:Gate push notifications for minor accounts by local time: suppress all non-safety/non-privacy pushes 22:00–06:00 CST by default, with a parent-controlled override. Enjoined 2026-04-20, not operative.

Statute’s own ages: Applies to minor users (under 16).

Plain:Default minor accounts to the most protective privacy and safety settings the platform offers.

Engineering:Ship maximum-protection privacy/safety defaults (restricted visibility, contactability, and data exposure) for accounts identified as minors under 16. Enjoined 2026-04-20, not operative.

Statute’s own ages: Applies to minor users (under 16).

Plain:Provide an easily accessible online dashboard that lets a parent or guardian monitor a minor's usage patterns and restrict the minor's access to the platform.

Engineering:Expose a parent-facing dashboard for minor accounts surfacing usage metrics and offering access controls (time/usage restriction). Enjoined 2026-04-20, not operative.

Statute’s own ages: Applies to minor users (under 16).

Plain:Conduct quarterly audits to identify design features that foster compulsive or addictive behavior in minor users.

Engineering:Run recurring (quarterly) internal audits of product surfaces for minor accounts to detect features implicating the addictive/compulsive-design prohibition, and document findings.

Statute’s own ages: Applies to platform duties toward minor users (under 16).