Law / United States / Idaho

Idaho

13 of 16 named instruments researched to a stage, across five of the ten areas of law we track: 12 in force and 1 not yet in force. As of .

When each starts10 of 13 carry a date, 3 do not. Earlier is before 2015.
Before 2015: 3 instruments (3 in force) earlier 2015: 0 instruments 2016: 0 instruments 2017: 0 instruments 2018: 0 instruments 2019: 0 instruments 2020: 0 instruments ’20 2021: 0 instruments 2022: 0 instruments 2023: 0 instruments 2024: 3 instruments (3 in force) 2025: 1 instrument (1 in force) ’25 2026: 2 instruments (2 in force) 2027: 1 instrument (1 not yet in force) ’27 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law 4
  2. Privacy law 5
  3. Scraping law 1
  4. Cybersecurity law 1
  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 2
  10. Reuse law

AI law4 instruments, 3 in force, 1 not yet in force

Research summary (606 words)

Idaho's AI-transparency law runs on two enacted disclosure duties.

Idaho Code section 67-6628A, the Freedom From AI-Rigged (FAIR) Elections Act, arms a candidate with an injunction and a damages action against a person who deceptively depicts that candidate through AI-generated synthetic media in an electioneering communication, subject to an affirmative defense where the communication itself carries a stated manipulation disclosure; it was enacted as House Bill 664 in 2024 after an earlier version of the same policy, House Bill 426, stalled in the House State Affairs Committee, and took effect on the Governor's signature, .

A broader duty, the Conversational AI Safety Act, requires any operator of a public-facing conversational AI service to disclose its non-human status where a reasonable person could otherwise be misled, adds a persistent-disclosure duty and safety measures for minor account holders, and is enforced exclusively by the Attorney General with no private right of action; enacted in 2026 as Senate Bill 1297 (Session Law Chapter 249), the bill's own text and the Legislature's bill-status page number the new chapter Idaho Code sections 48-2101 to 48-2105, but Title 48 Chapter 21 had already been claimed the same session by the Stop Harms from Addictive Social Media Act, so the live Idaho Statutes site instead carries this Act as Chapter 21 [22] and numbers its sections 48-2201 to 48-2205, which is the citation used here.

It does not take effect until , and a narrower 2025 predecessor confined to chatbot disclosure, House Bill 127, died in committee. Until the Conversational AI Safety Act takes effect, the Idaho Consumer Protection Act's general prohibition on any act or practice that is misleading, false, or deceptive to the consumer, Idaho Code section 48-603(17), is the only state-law backstop against an undisclosed chatbot's non-human status, and no Idaho court has applied it to that fact pattern.

Idaho also enacted the Generative Artificial Intelligence in Education Act in 2026 as Senate Bill 1227 (Session Law Chapter 71), Idaho Code sections 33-7001 to 33-7008, directing the State Department of Education, the State Board of Education, and local school districts and public charter schools to adopt generative-AI governance frameworks, policies, and standards for K-12 schools; most of that framework runs to those government bodies and is not catalogued as an instrument here, but section 33-7007 reaches outward and requires a vendor whose product is procured by a district or charter school to disclose whether the product uses machine learning, predictive analytics, or generative AI and to provide assurances on data protection, algorithmic transparency, and responsible use, a duty catalogued below; the chapter attaches no penalty, private right of action, or enforcement body to that disclosure duty, and it took effect .

Two further research candidates, a 2026 Artificial Intelligence Definition Act reported as House Bill 1723 and a 2026 AI Deepfake / Right of Publicity Act reported as Senate Bill 2076, do not appear under either number, or under any title matching either description, in the Idaho Legislature's own 2026 session bill index, and neither is catalogued or otherwise relied on here.

Idaho Code section 18-6606, in the Sex Crimes chapter, separately makes it a crime for any person to knowingly disclose explicit synthetic media depicting an identifiable person without consent and causing substantial emotional distress, with intent to harass or degrade that person, or to extort money by threatening disclosure, a misdemeanor rising to a felony where the depicted person is a minor or the violator has a qualifying prior conviction; added in 2024 and amended in 2026, it is catalogued below as a prohibited-practices instrument rather than treated as an aggregation exclusion.

AI prohibited practices

Disclosing explicit synthetic media

Idaho Code section 18-6606official Idaho Statutes text, Idaho State Legislature website

In force since . Binds public and private bodies.

What this law does

A person is guilty of disclosing explicit synthetic media (any image or video created or altered using technical means, such as artificial intelligence, to realistically misrepresent an identifiable individual as engaging in conduct in which the individual did not engage) when the person knowingly discloses it either knowing or having reason to know the identifiable person did not consent and that disclosure would cause substantial emotional distress, or with intent to annoy, terrify, threaten, intimidate, harass, offend, humiliate, or degrade the identifiable person, or possesses and threatens to disclose it to obtain money or other valuable consideration.

A base violation is a misdemeanor; it becomes a felony, punishable by up to ten years' imprisonment, a fine of up to $25,000, or both, where the identifiable person is under eighteen or the person was previously found guilty of a violation of this section or a similar statute elsewhere within the past five years.

Exceptions to the lack-of-consent-and-emotional-distress theory of liability under subsection (1)(a) cover disclosure for a lawful criminal investigation or prosecution, reporting unlawful conduct, a matter of genuine public interest (a public figure's mere presence does not by itself qualify), legitimate scientific research or education, or disclosure made in the normal course of civil legal proceedings or under a nondissemination court order; none of them reaches the harassment-intent theory in subsection (1)(b) or the extortion theory in subsection (1)(c).

An interactive computer service, information service, or telecommunication service is not liable for content provided by another person unless it intentionally aids or abets the disclosure. The section was added by 2024 Idaho Session Laws chapter 105 (House Bill 575) and later amended by 2026 Idaho Session Laws chapter 121 (House Bill 727), which revised only the penalty provision; the Idaho Legislature's own bill status record for House Bill 575 states an effective date of .

What it requires

AI transparency

Conversational AI Safety Act

Idaho Code sections 48-2201 to 48-2205official Idaho Statutes text, Idaho State Legislature website

Not yet in force. from , in 8 months It starts to bind on .

Binds public and private bodies.

What this law does

An operator, a person who makes a conversational AI service (an artificial intelligence application, web interface, or program accessible to the general public that primarily simulates human conversation through text, visual, or aural communication, with exceptions for developer or research tools, features that are not themselves a conversational AI service, business-internal or business-to-business tools, voice assistants for consumer electronics, and enterprise-only platforms) available to the public, must clearly and conspicuously disclose that the service is artificial intelligence if a reasonable person could otherwise be misled into believing they are interacting with a human.

An operator must adopt a protocol for responding to user prompts about suicidal ideation, including referring users to crisis services, and may not cause the service to represent that it provides professional mental or behavioral health care.

For a minor account holder, an operator must give a persistent visible disclaimer, or disclose at the start of each session and at least every three hours, must not use unpredictable reward mechanics to increase engagement, must take reasonable measures against sexually explicit content and against statements suggesting the AI is sentient, human, romantically or sexually interested, or emotionally dependent, and must offer account and privacy management tools to minors and to the parents or guardians of those under thirteen.

A violation is subject to an injunction and a civil penalty of $1,000 per violation up to $500,000 per operator, or actual damages, whichever is greater, sought exclusively by the Attorney General; the Act creates no private right of action and does not make an AI model's developer liable for a third-party operator's violation. Enacted in 2026 as Senate Bill 1297 (Session Law Chapter 249), signed , and effective .

Title 48 Chapter 21 had already been claimed the same session by the Stop Harms from Addictive Social Media Act, so the live Idaho Statutes site carries this Act as Chapter 21 [22] and numbers its own sections 48-2201 to 48-2205, superseding the 48-2101 to 48-2105 numbering in the enacting bill's own text. A narrower 2025 predecessor limited to chatbot disclosure, House Bill 127, died in the House Business Committee.

What it requires

FAIR Elections Act, disclosure duty for synthetic media in electioneering communications

Idaho Code section 67-6628Aofficial Idaho Statutes text, Idaho State Legislature website

In force since . Binds public and private bodies.

What this law does

A candidate whose action or speech is deceptively represented through synthetic media (an audio or video recording created using generative adversarial network techniques or other digital technology to depict a real event, action, or speech that did not occur, giving a fundamentally different impression than the unaltered original) in an electioneering communication may seek injunctive relief prohibiting publication and may sue the information content provider that created or developed the content for general and special damages, plus attorney's fees and costs.

It is an affirmative defense that the communication carries a stated disclosure that it has been manipulated, displayed for a video's full duration in an easily readable size, or spoken at the start, end, and every two minutes of audio over two minutes long; the plaintiff bears the burden of proving the use of synthetic media by clear and convincing evidence.

A distributing medium, rather than the information content provider, is liable only if it strips the required disclosure or itself alters the content into synthetic media. Enacted as House Bill 664 (2024 Regular Session), signed by the Governor and effective (Session Law Chapter 172). An earlier version of the same policy, House Bill 426, was returned to the House State Affairs Committee on , and did not advance under its own number.

What it requires

Generative Artificial Intelligence in Education Act, vendor disclosure duty

Idaho Code section 33-7007official Idaho Statutes text, Idaho State Legislature website

In force since . Binds private bodies.

What this law does

Idaho Code section 33-7007, part of the Generative Artificial Intelligence in Education Act (Idaho Code sections 33-7001 to 33-7008, enacted in 2026 as Senate Bill 1227, Session Law Chapter 71), requires that generative AI-related software, applications, and tools procured by local school districts and public charter schools comply with state and federal data privacy laws, including the Family Educational Rights and Privacy Act, the Children's Internet Protection Act, and the Children's Online Privacy Protection Act.

A vendor of such a product must disclose whether it utilizes machine learning, predictive analytics, or generative AI, and must provide assurances regarding data protection, algorithmic transparency, and responsible use. Senate Bill 1227 was signed by the Governor on , as Session Law Chapter 71, and took effect .

What it requires

Privacy law5 instruments, 5 in force

Research summary (213 words)

Idaho has no comprehensive consumer personal-data statute; two attempts at an Insurance Data Security Act (H0117, 2025, and H0147, 2021) both failed and no such chapter exists in Title 41.

Idaho residents' personal-data protection is sectoral: a long-standing Identity Theft Act (Idaho Code secs. 28-51-104 to 28-51-107) requires breach notice to affected residents and, for government agencies, a 24-hour notice to the Attorney General, but its personal information definition has no biometric, genetic, or health element and no fixed numeric notice deadline.

The Genetic Testing Privacy Act (Idaho Code sec. 39-8302) bars an employer of five or more persons, including government, from requiring, requesting, or accessing an individual's genetic information as a condition of employment.

The Student Data Accessibility, Transparency and Accountability Act (SDATAA, Idaho Code sec. 33-133) bars a K-12 student's biometric information from a school's permanent educational record and, with civil penalties of up to $50,000 per violation, enforced by the State Board of Education and the State Department of Education, with separate Attorney General assisted enforcement of a school's policy duty; the Act mentions a court action initiated by an injured party but grants no cause of action of its own. The general breach statute's enforcement runs to the entity's primary regulator with a civil penalty of up to $25,000.

Breach notification

Identity Theft Act, breach of security disclosure duty

Idaho Code § 28-51-105official Idaho statute text, Idaho Code Title 28, Chapter 51, Idaho Legislature

In force. Binds public and private bodies.

What this law does

An agency, individual, or commercial entity that owns or licenses computerized data including personal information must give notice as soon as possible, and in the most expedient time possible without unreasonable delay, to each affected Idaho resident following a breach of system security. A government agency must additionally notify the Idaho Attorney General within 24 hours of discovery; this duty does not extend to a private commercial entity.

Any governmental employee who intentionally discloses personal information not subject to disclosure otherwise allowed by law is guilty of a misdemeanor, punishable by up to a $2,000 fine, up to one year in county jail, or both.

Personal information is a resident's name combined with a Social Security number, a driver's license or Idaho identification card number, or a financial account or card number with an access code, and does not include publicly available information lawfully made available to the general public from government records or widely distributed media; it carries no biometric, genetic, or health element, so a breach exposing only biometric data does not trigger this duty.

The statute, added in 2006 and amended in 2014, sets no fixed numeric notice deadline and no consumer reporting agency threshold. The provisions this entry describes came into force on different days.

What it requires

Enforcement supervision

Genetic Testing Privacy Act, enforcement

Idaho Code § 39-8304official Idaho statute text, Idaho Code Title 39, Chapter 83, Idaho Legislature

In force since . Binds public and private bodies.

What this law does

The Idaho Attorney General has exclusive enforcement authority over the Genetic Testing Privacy Act.

Whenever the Attorney General has reason to believe an employer is violating, has violated, or is about to violate the chapter, the Attorney General may bring an action in the state's name for a declaratory judgment, an injunction, recovery of actual damages or restitution on behalf of the state and its agencies, and a civil penalty of up to $25,000 per violation, deposited to the state general fund. These remedies are in addition to any other available remedy at law or equity.

The chapter creates no private right of action for a genetic-information violation, unlike SDATAA's express injured-party route for student data.

What it requires

Identity Theft Act, breach notification enforcement and penalties

Idaho Code § 28-51-107official Idaho statute text, Idaho Code Title 28, Chapter 51, Idaho Legislature

In force since . Binds public and private bodies.

What this law does

An affected entity's own primary regulator, not a private plaintiff, enforces the notice duty: the primary regulator may bring a civil action to compel compliance and enjoin further violations, and an agency, individual, or commercial entity that intentionally fails to give notice is subject to a fine of up to $25,000 per breach. The chapter creates no private right of action.

What it requires

Student Data Accessibility, Transparency and Accountability Act (SDATAA)

Idaho Code § 33-133official Idaho statute text, Idaho Code sec. 33-133, Idaho Legislature

In force since . Binds public and private bodies.

What this law does

SDATAA binds the State Board of Education, school districts, public charter schools, and their private vendors on the collection, use, and disclosure of K-12 student data.

A student's permanent educational record may not include, among other exclusions, the student's biometric information, Social Security number, or data collected through statewide-assessment affective computing such as facial-expression, EEG, or eye-tracking analysis (with a carve-out for special needs and exceptional students).

A person found, in a civil enforcement action by the State Board or the Department of Education or in a court action initiated by an injured party, to have violated the Act is liable for a civil penalty of up to $50,000 per violation, and all civil penalties collected are paid into the state general fund; the Act refers to a court action initiated by an injured party but grants no cause of action of its own; a district or charter school that fails to adopt, implement, and post its student-data policy faces a separate $50,000 civil penalty enforced by the State Board with Attorney General assistance.

Unless otherwise prohibited by law or court order, a school district must provide a parent or guardian with copies of all of their child's educational records upon request, so long as the child has not yet turned eighteen.

What it requires

Sensitive categories

Genetic Testing Privacy Act, restrictions on employers

Idaho Code § 39-8303official Idaho statute text, Idaho Code Title 39, Chapter 83, Idaho Legislature

In force. Binds public and private bodies.

What this law does

Idaho's Genetic Testing Privacy Act (Idaho Code Title 39, Chapter 83) is an employment-context genetic-privacy statute rather than a general-audience personal-data regime.

Section 39-8303 bars an "employer", defined at sec. 39-8302(4) to include any entity employing five or more persons and expressly including government, from accessing or considering an individual's private genetic information, requesting or requiring consent to release it, requesting or requiring a genetic test of an individual or blood relative, or inquiring whether either has taken or refused one, in connection with a hiring, promotion, retention, or other related employment decision.

Narrow exceptions allow a court-ordered compelled disclosure in limited circumstances and forensic or human-remains DNA analysis by an employer that conducts it. The Act creates no controller or processor duties and no consumer-facing right against a business generally. The provisions this entry describes came into force on different days.

What it requires

Scraping law1 instrument, 1 in force

Research summary (182 words)

Idaho's computer crime statute, Idaho Code section 18-2202, departs from a pure malicious-intent test: subsection (3) makes it a misdemeanor to knowingly and without authorization use, access, or attempt to access any computer, computer system, or network, or the software, program, documentation, or data it contains, with no additional intent to defraud, damage, or disrupt required, while subsections (1) and (2), which do require an added mental state such as intent to defraud or knowing alteration or destruction, are felonies.

Neither this section nor its companion definitions section, Idaho Code section 18-2201, defines authorization or exempts access to a publicly available page, and no reported Idaho case has applied either section to an automated web-scraping or bulk-data-collection fact pattern. Idaho has no comprehensive consumer privacy statute reaching scraped public personal data; that ground is covered under the privacy topic and not restated here.

Terms-of-service enforceability, copyright and text-and-data-mining exceptions, database rights, unfair competition, and the legal weight of robots.txt raise only the federal and common-law questions the national document already covers, and Idaho has enacted no state-specific statute on any of them.

Computer misuse

Computer crime (unauthorized access, use, or alteration)

Idaho Code section 18-2202official Idaho Statutes text, Idaho State Legislature website

In force. Binds public and private bodies.

What this law does

Subsections (1) and (2) make it computer crime, a felony, to knowingly access, attempt to access, or use a computer, computer system, or network with intent to defraud, to obtain money, property, or services by false pretenses, or to commit theft, or to knowingly and without authorization alter, damage, or destroy a computer, system, network, or the software, program, documentation, or data it contains.

Subsection (3) separately makes it a misdemeanor for any person to knowingly and without authorization use, access, or attempt to access a computer, computer system, or network, or the software, program, documentation, or data contained in it, with no further intent element beyond knowledge and lack of authorization.

Neither this section nor its companion definitions section, Idaho Code section 18-2201, which defines only technical terms such as access, computer, and computer network, states what counts as authorization or exempts ordinary access to a publicly available page. Idaho Code section 18-2202 was added by 1984 Idaho Session Laws chapter 68, section 1, whose enacted text carries no effective-date clause and declares no emergency.

A law with neither takes effect on July 1 of the year of the regular session or sixty days after the session ends, whichever is later, under Idaho Code section 67-510, and no source states the resulting day for this act.

What it requires

Cybersecurity law1 instrument, 1 in force

Research summary (653 words)

Idaho has no product-security, vulnerability-and-incident-reporting, sector cyber-resilience, or general reasonable-security-program statute that falls inside this topic's four registered law families. Idaho Code Title 28, Chapter 51, captioned Identity Theft, is the state's only enacted general-application information-security statute, and its substantive duties are either this jurisdiction's own privacy-topic row or too narrow to describe a system's security posture.

Section 28-51-105 sets the duty to disclose a breach of the security of the system to affected Idaho residents, and Section 28-51-107 sets that duty's enforcement; both are already researched as this jurisdiction's privacy-topic instruments and are not repeated here.

Section 28-51-106 is a compliance safe harbor keyed entirely to Section 28-51-105's own notice timing: an agency, individual, or commercial entity that maintains its own notice procedures consistent with that timing, or that follows the breach procedures of its primary state or federal regulator, is deemed to comply with the notice duty. It creates no independent duty to secure a system before a breach occurs, so it is not a security-program instrument in its own right.

Section 28-51-103 requires a merchant accepting a payment card to print no more than the last five digits of the account number, or the card's expiration date, on a paper receipt; it is a narrow point-of-sale truncation rule rather than a security-management, product-security, or incident-reporting duty on a software product or service, and no activity in the LexLint vocabulary reaches a receipt printer, so it is recorded here rather than filed as an instrument.

Idaho has twice failed to enact a NAIC-model Insurance Data Security Act that would have imposed the kind of written information-security-program duty this topic files in other jurisdictions that adopted that model. House Bill 147 (2021) reached the House floor and failed on the Rules-Suspended, read-in-full third-reading vote, 31 ayes to 37 nays with 2 absent or excused, on .

House Bill 117 (2025) was reported out of the House Business Committee with a do-pass recommendation and held on the third-reading calendar for six legislative days, then was instead returned to the Business Committee on , with no further recorded action before that session closed. No bill of that title, or any bill matching the terms cybersecurity, data security, or insurance data security, appears in the 2026 regular session's legislation index.

Because neither attempt was enacted, Idaho currently carries no insurance-sector security-program law at all, not even one bound to a role (an insurance licensee) that this profile's activity vocabulary cannot express; the deferral this profile calls for in other jurisdictions with an enacted, licensee-only regime does not arise here, since there is no enacted regime to defer.

No Idaho statute was found setting security requirements a connected device or software product must meet before or after being placed on the market, comparable to California's, Oregon's, or Connecticut's connected-device statutes or the EU's Cyber Resilience Act, and no sector cyber-resilience regime binding a critical, essential, or financial entity as it reaches a digital service (a DORA or New York DFS Part 500 analogue) was found.

Idaho Code Section 67-827 places cybersecurity policy for the state's own information technology under the Office of Information Technology Services; it is a state-agency governance statute binding Idaho's own agencies, not a private-sector vendor, and the agency cybersecurity duties of sections 67-827A and 67-2363 are filed as a row of their own with no activity flag.

Idaho's computer-crime and wiretap statutes, unauthorized computer access under Idaho Code Section 18-2202 and communications interception under Idaho Code Title 18, Chapter 67 (Communications Security), each bind a person who accesses a system or intercepts a communication without authorization, an offense committed against a system rather than a duty on its operator or manufacturer, and stay with the scraping topic's computer-misuse family rather than being restated here.

Idaho's office of information technology services must require all state agencies to implement and use multifactor identification to access information technology devices or services.

Sector security regimes

State agency cybersecurity direction and multifactor identification

State Agency Cybersecurity and Multifactor Identification, Idaho Code ss. 67-827A and 67-2363Text of Idaho Code sections 67-827A, 67-831 and 67-2363, as published by the Idaho Legislature

In force since . Binds government bodies.

What this law does

The office of information technology services is directed to ensure that all state agencies implement and maintain cybersecurity best practices. The office must require all state agencies to implement and use multifactor identification to access information technology devices or services, including local and remote network access to any email accounts, cloud storage accounts, web applications, networks, databases, or servers.

The office is authorized and directed to direct state agencies and officials on penetration tests and vulnerability scans of state technology systems in order to identify steps to mitigate identified risks. State agencies means all state agencies or departments, boards, commissions, councils, and institutions of higher education, but not the elected constitutional officers and their staffs, the legislature and its staffs, or the judiciary.

Multifactor identification means using two or more different types of identification credentials to achieve authentication. The legislative branch and its staff, the judicial branch and its staff, and the elected constitutional officers and their staffs shall implement the use of multifactor identification. House Bill 35 of 2025 became Session Law Chapter 6 and took effect on .

What it requires

Age gating law2 instruments, 2 in force

Research summary (87 words)

Idaho requires age verification on websites publishing material harmful to minors under a 2024 law (HB 498), in effect since July 2024 and apparently unchallenged in court, which led several major adult sites to exit the state rather than comply. A 2026 law (HB 542) separately requires large social media platforms to estimate user age and obtain parental consent for accounts held by Idahoans age 16 or younger, and took effect . Idaho has not enacted an app store age verification or design code law.

Adult content age verification (AV)

HB 498 (2024), age verification for material harmful to minors

Idaho Code Secs. 6-3801 to 6-3809official codified chapter text, Idaho Statutes title 6 chapter 38, Idaho Legislature

In force since . Binds private bodies.

What this law does

Requires a publisher of a website whose share of material harmful to minors meets the applicability criteria to perform reasonable age verification, via a digitized identification card or a commercial age verification system using government issued identification or transactional data, and prevent minors from accessing the material. Creates a private right of action with statutory damages of at least $10,000. Enacted as 2024 Idaho Session Laws chapter 113.

What it requires

Social media and minors

HB 542 (2026), Stop Harms from Addictive Social Media Act

Idaho Code tit. 48, ch. 21 (2026 Idaho Sess. Laws ch. 268)official Idaho Legislature bill history and enrolled act

In force since . Binds private bodies.

What this law does

Requires large social media platforms, those with at least $1 billion in worldwide advertising revenue, to use reasonable age estimation for Idaho account holders and obtain verifiable parental consent before a child, defined as an Idaho resident 16 years of age or younger, may hold an account, and bars addictive interface features and certain advertising directed at children. A platform may treat an account holder as an adult only with at least 80 percent confidence the user is older than 16. Creates a private right of action. Signed , as 2026 Idaho Session Laws chapter 268.

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

Idaho has no press-publisher neighbouring right and no mandatory platform-to-publisher bargaining code; no Idaho statute or introduced bill addressing either has been located. No reported Idaho appellate decision recognizes hot-news misappropriation or otherwise addresses whether a hyperlink, or a framed or inline display, is a communication to the public.

Copyright over news content published in Idaho, including the copyrightability of headlines and snippets, the availability of a fair-use defense, and any text-and-data-mining exception, arises solely under the federal Copyright Act, already covered in the national document; Idaho has enacted no state intellectual-property statute reaching news aggregation and no machine-readable text-and-data-mining opt-out of its own.

As of .

Case law

  • No current case law for Idaho AI law
  • No current case law for Idaho privacy law
  • No current case law for Idaho scraping law
  • No current case law for Idaho cybersecurity law
  • No current case law for Idaho communications law
  • No current case law for Idaho content moderation law
  • No current case law for Idaho product and AI liability law
  • No current case law for Idaho digital accessibility law
  • No current case law for Idaho age gating law
  • No current case law for Idaho reuse law

Reporting clocks that run here17 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 Idaho 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
24 hours
Breach notificationprivacy 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
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 Idaho

24 hours

Identity Theft Act, breach of security disclosure duty

Idaho Code § 28-51-105privacy law, in force

The sentences the clocks are read from

Give notice to each affected Idaho resident as soon as possible, and in the most expedient time possible without unreasonable delay, after discovering a breach of system security involving personal information.

If you are a government agency, also notify the Idaho Attorney General within 24 hours of discovering the breach; this duty does not extend to a private commercial entity.

The law of the United States, which applies in Idaho

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.