Security Breach Notification Act; prohibiting class action liability for private entity for cybersecurity event; providing exceptions. Effective date.
SB 1716 amends Oklahoma's Security Breach Notification Act to limit class action lawsuits against private entities following cybersecurity breaches. It prohibits class action liability unless a breach results from the entity's "willful and wanton conduct or gross negligence." The bill also clarifies that private entities using reasonable safeguards and providing required breach notices cannot be held liable for civil penalties, while those failing to use reasonable safeguards face reduced penalties ($75,000) but not class actions. This directly affects businesses and organizations handling personal data in Oklahoma, shifting enforcement exclusively to the Attorney General or district attorneys for most cases.
Bill status
passed
3 of 5 stages cleared
Introduction
Feb 2026
Committee Review
Apr 2026
Senate Passage
Mar 2026
House Passage
Governor
Introduced Feb 2, 2026
Last action Apr 6, 2026
Maddy AI version diff · 3 comparisons
What changed between versions
Proposed Policy Committee Substitute 1
→
Floor (Senate)
·
3 edits
MINOR
The bill was completely rewritten to replace a committee substitute version with the final Senate Floor version. The new text updates the legal citations to reflect the bill's progression through the legislative process and reorganizes the structure to align with the final enacted format.
Scope change
The bill's substantive scope regarding security breach notification requirements, liability exemptions, and definitions remains unchanged from the committee version; only the formatting and legal citations were modified.
TECHNICAL
The entire text of the bill was replaced to update the header information, including the bill title, sponsor names, and session details, to match the final Senate Floor version.
Legal citations and section references were updated to reflect the bill's status as an amendment to 24 O.S. 2021, Section 165, rather than referencing a previous Senate Bill number.
The document structure was reorganized to remove committee-specific labels (like 'Proposed Policy Committee Substitute') and replace them with standard Senate Floor formatting.
Floor votes · Senate Mar 16, 2026
How they voted
47–0
Passed · 3 other
Total votes 50
Mar 16, 2026
D
Democratic9
77% Yea
R
Republican41
97% Yea
Vote distribution
All Yea
All Nay
Mixed
No data
Full legislative history
Actions timeline
Total actions
16
Key actions
4
Committee
4
Amendments
1
Apr 6, 2026
Lower · Passed
Policy recommendation to the Judiciary and Public Safety Oversight committee; Do Pass, amended by committee substitute Civil Judiciary
lower
Mar 30, 2026
Committee
Referred to Civil Judiciary
lower
Mar 17, 2026
Introduced
First Reading
lower
Mar 17, 2026
Upper · Passed
Engrossed to House
upper
Mar 16, 2026
Committee
Referred for engrossment
upper
Mar 16, 2026
Upper · Passed
Measure passed: Ayes: 45 Nays: 1
upper
Mar 16, 2026
Introduced
General Order, Amended
upper
Feb 19, 2026
Upper · Passed
Reported Do Pass as amended Technology and Telecommunications committee; CR filed
upper
Feb 2, 2026
Introduced
First Reading
upper
2 primary · 0 co-sponsors
Sponsors
Ask Maddy
·
AI policy assistant
Ask Maddy about SB 1716
Scope: OK
Hi! I can help you understand SB 1716. What would you like to know?
Try one of these
i
Maddy answers using official bill text and legislative records. Always verify before sharing.
Sources cited inline