United States law applies in IndianaIndiana is a state of the United States, whose 134 researched instruments are listed on the United States page, not here. The law of Indiana, described on this page below, applies here too.
29 of 30 named instruments researched to a stage, across five of the ten areas of law we track: 28 in force and 1 not yet in force. As of .
When each starts21 of 29 carry a date, 8 do not. Earlier is before 2015.
in forcenot yet in forceblocked by a courtproposedno longer in force
Indiana has no general statute requiring disclosure or labeling of AI-generated content outside the election context, and no chatbot-disclosure statute has been enacted; a 2025 health-care AI bill covering similar ground to the enacted downcoding law did not pass.
Indiana instead reaches AI through targeted amendments to existing criminal and civil statutes: House Enrolled Act 1133 of 2024 (Public Law 81-2024) added a disclaimer duty for campaign communications containing fabricated or AI-generated media of a candidate, and House Enrolled Act 1047 of 2024 (Public Law 79-2024) extended the criminal offense of distributing an intimate image, and the parallel civil action for disclosing nonconsensual pornography, to images created or altered by artificial intelligence.
Separately, Indiana's child-exploitation and child-pornography statute already reaches an obscene, computer-generated image of a fictional child, without requiring that the depicted child actually exist.
House Enrolled Act 1271 of 2026 (Public Law 88-2026) bars a health insurer from using an automated tool, including artificial intelligence, as the sole basis for downcoding a medical-necessity claim without human review, and requires disclosure when artificial intelligence is used to make an adverse prior-authorization determination or to downcode a claim.
Indiana Code Article 4-13.1 creates an AI task force and requires state agencies to inventory their own AI systems; that duty runs to state government's own use of AI and is not catalogued here as an instrument.
Indiana's child-exploitation statute defines "image" to include a computer-generated image, and separately reaches simulated sexual conduct involving a representation that appears to be a child under eighteen, where the representation is obscene, without requiring that the child depicted actually exist.
Producing, disseminating, or possessing with intent to disseminate such an image is child exploitation, a Level 5 felony (a Level 4 felony on aggravating circumstances such as the depicted conduct including force or a victim under twelve), and knowingly possessing or accessing such an image is possession of child pornography, a Level 6 felony (a Level 5 felony on the same aggravating circumstances).
This reaches an AI-generated depiction of a fictional child in an obscene sexual context on the same terms as any other computer-generated image. Both the computer-generated-image definition and the simulated-conduct language quoted here were added by House Enrolled Act 1363 (P.L.172-2022), effective .
House Enrolled Act 1047 amended the definition of "intimate image" that runs through both Indiana's criminal distribution-of-an-intimate-image statute and its civil nonconsensual-pornography-disclosure statute to include a photograph, digital image, or video of a person that was created or modified by a computer software program, artificial intelligence, application, or other digital editing tool, so that an AI-generated or AI-altered depiction of a real, identifiable person in an intimate context is treated the same as an authentic one.
Distributing such an image without the depicted person's consent, when the distributor knows or reasonably should know the person does not consent, is a Class A misdemeanor, elevated to a Level 6 felony on a prior unrelated conviction.
A depicted individual who is identifiable and suffered harm may separately bring a civil action for disclosing nonconsensual pornography, recovering the greater of actual and emotional-distress damages or statutory damages up to $10,000 per defendant, plus any of the defendant's monetary gain, punitive damages, attorney's fees, and injunctive relief. Both amendments took effect under the act's own effective-date clause.
A new Indiana Code chapter on downcoding of health benefits claims bars a health insurer, HMO, or dental preferred-provider plan from using an automated process, system, or tool, including artificial intelligence, as the sole basis to downcode a claim based on medical necessity, without a covered individual's medical record first being reviewed by an insurer employee or contractor; it likewise bars a provider from submitting a claim through such an automated tool without human review.
The insurer must disclose, in an easily accessible and readable manner, whenever artificial intelligence is used to make an adverse determination on a prior authorization request or to downcode a claim. The chapter does not apply to the Medicaid program or a Medicaid managed care organization. Enacted as House Enrolled Act 1271, it took effect under the act's own effective-date clause.
Ind. Code § 3-9-8official enrolled act text, Indiana General Assembly
In force since .Binds public and private bodies.
What this law does
If a campaign communication includes fabricated media, meaning audio, video, or an image that has been altered or artificially generated to convey a materially inaccurate depiction of a candidate that a reasonable person would not recognize as altered, the person who paid for the communication must include a disclaimer stating that elements of the media have been digitally altered or artificially generated.
The disclaimer requirements vary by medium: a printed or video disclaimer must be displayed continuously, and an audio disclaimer must be read at the start, the end, and every two minutes for a communication longer than two minutes.
A candidate depicted in noncompliant fabricated media may bring a civil action against the person who paid for or sponsored the communication, and against a disseminator who knowingly, intentionally, or recklessly removed the disclaimer, for actual damages, injunctive relief, and attorney's fees, on a clear-and-convincing-evidence standard.
The enrolled act declared an emergency and took effect upon passage; the Indiana General Assembly's own bill-actions record shows the Governor signed it .
The Indiana Consumer Data Protection Act (INCDPA), Ind. Code Art. 24-15 (codified caption "Consumer Data Protection," the popular INCDPA name is not itself codified text), is Indiana's comprehensive consumer-privacy regime, enacted as P.L.94-2023 (Senate Bill 5, 2023 Regular Session) and effective across every section of the article.
Genetic or biometric data processed to uniquely identify a specific individual is one of INCDPA's enumerated sensitive-data categories, but the Act's biometric data definition carries a blanket, unconditional exclusion for a photograph, or for a video or audio recording, or any data generated from either, with no clawback for data generated to identify someone, so a faceprint or voiceprint extracted from a recording falls outside biometric data, and therefore outside sensitive data, regardless of purpose.
Florida's FDBR shares this unconditional structure in the same batch, while Maryland's, Minnesota's, and New Jersey's biometric definitions each claw the data back. A separate, older statute, the Disclosure of Security Breach Act (Ind. Code Art. 24-4.9), governs breach notification and is enforced, like INCDPA, exclusively by the Indiana Attorney General, and a violation of either statute is not privately actionable.
INCDPA's 30-day cure right before an Attorney General enforcement action is mandatory, not discretionary, and carries no sunset date anywhere in the article, unlike several peer states' time-limited cure rights.
Chapter 24 of article 4 of title 24 of the Indiana Code bars a consumer genetic testing provider from taking listed actions with an individual's biological material or genetic data unless the provider has solicited and received the individual's freely given, specific, informed and unambiguous consent.
Section 21(c) of IC 27-2-27 requires an insurance licensee to notify the insurance commissioner as promptly as possible but not later than three business days after a determination that a cybersecurity event involving nonpublic information in the licensee's possession has occurred, if a listed condition applies.
Section 2 of IC 22-9-14 bars a person from discriminating against an individual on the basis of the individual's use of consumer genetic testing services or the results of genetic testing performed by a consumer genetic testing provider. Section 5 of IC 27-8-26 bars an insurer processing an application for health care services coverage from requiring an individual to submit to genetic screening or testing and from considering information obtained from it adversely.
Section 1(c) of IC 16-39-1 requires a provider, on written request and reasonable notice, to supply to a patient the health records possessed by the provider concerning the patient. Section 2(d) of IC 16-39-5 bars an insurance company other than a life insurance company from obtaining the results of any genetic screening or testing without a separate written consent by an individual.
Section 3(d) of IC 16-39-5 requires a provider using a health record for a legitimate business purpose without specific written authorization to protect the confidentiality of the record at all times.
A data base owner must disclose a breach of the security of a system to an affected Indiana resident if the owner knows, should know, or should have known that the unauthorized acquisition has resulted in or could result in identity deception, identity theft, or fraud affecting that resident, without unreasonable delay and no later than 45 days after discovering the breach.
A data base owner disclosing to more than 1,000 consumers must also notify nationwide consumer reporting agencies, and any disclosure at all triggers a required notice to the Indiana Attorney General.
Failing to make a required disclosure is a deceptive act actionable only by the Attorney General, with a civil penalty of up to $150,000 per deceptive act, and a separate, narrower duty to implement reasonable safeguards and dispose of records properly carries its own $5,000-per-act penalty, also enforced only by the Attorney General. This is a separate, pre-existing statute from INCDPA. The cited sections were added by P.L.125-2006, Securities and Exchange Commission (SEC).6, and have since been amended piecemeal: Ind.
Code sections 24-4.9-3-1 and 24-4.9-4-1 by P.L.137-2009, and section 24-4.9-3-3 by P.L.171-2022; section 24-4.9-4-2 has not been amended since 2006. The provisions this entry describes came into force on different days.
Ind. Code § 27-2-27-21Official text of Indiana Code chapter 27-2-27 (2026 Code), Indiana General Assembly (iga.in.gov)
In force since .Binds private bodies.
What this law does
Section 21(c) of IC 27-2-27 requires a licensee to notify the commissioner as promptly as possible but not later than three business days after a determination that a cybersecurity event involving nonpublic information in the licensee's possession has occurred, if either of two listed conditions applies.
Section 21(c)(1) reaches an insurer domiciled in Indiana, or a producer whose home state is Indiana, when the event has a reasonable likelihood of materially harming a consumer residing in Indiana or any material part of the licensee's normal operations.
Section 21(c)(2) reaches a licensee that reasonably believes the nonpublic information of at least 250 consumers residing in Indiana was affected, where notice of the event is required by another state, federal or local law or the event has a reasonable likelihood of materially harming a consumer residing in Indiana or a material part of the licensee's normal operations.
Section 21(d) requires a licensee, after learning that a cybersecurity event has or may have occurred, to provide as much as possible of the thirteen listed items of information in electronic form, as directed by the commissioner. Section 21(e) gives the licensee a continuing obligation to update and supplement initial and subsequent notifications to the commissioner regarding material changes to previously provided information.
Section 21(f) requires a licensee to comply with IC 24-4.9 and to provide the commissioner a copy of the consumer notice if the licensee is required to notify the commissioner under subsection (c). In IC 27-2-27, a licensee is a person that is licensed, authorized to operate or registered, or required to be, under title 27 of the Indiana Code and the rules adopted under it.
Section 26(b) of IC 27-2-27 treats a licensee that is subject to Health Insurance Portability and Accountability Act (HIPAA) and maintains an information security program under it as meeting the chapter, except for the notice requirements in section 21. Section 27 of IC 27-2-27 lets the insurance commissioner, after notice and hearing, suspend or revoke the license, certificate of authority or registration of a licensee that violates the chapter.
Section 29 of IC 27-2-27 provides that the chapter does not create a private right of action against any person. Section 1 of IC 27-2-27 provides that the chapter applies after . P.L.130-2020 added the chapter to the Indiana Code.
INCDPA governs private-sector processing of Indiana residents' personal data. It applies to a person conducting business in Indiana, or producing a product or service targeted to Indiana residents, that during a calendar year controls or processes the personal data of at least 100,000 Indiana consumers, or of at least 25,000 Indiana consumers while deriving more than 50 percent of gross revenue from selling personal data.
A controller must limit collection to what is adequate, relevant, and reasonably necessary for the purposes disclosed to the consumer, and may not process personal data for an incompatible purpose without the consumer's consent. Article 15 also preempts local law: no city, county, or other local government may regulate a controller's or processor's processing of personal data.
INCDPA requires a controller to conduct and document a data protection impact assessment of each of these processing activities involving personal data: targeted advertising, the sale of personal data, profiling that presents a reasonably foreseeable risk of unfair or deceptive treatment, injury, an offensive intrusion or other substantial injury to consumers, the processing of sensitive data, and any processing that presents a heightened risk of harm to consumers.
Each assessment must identify and weigh the benefits of the processing to the controller, the consumer, other stakeholders and the public against the potential risks to the rights of the consumer, as mitigated by safeguards.
The Attorney General may request, pursuant to a civil investigative demand, that a controller disclose any such assessment relevant to an investigation, and the controller must make it available to the Attorney General, who may evaluate it for compliance with the controller responsibilities in chapter 4. Assessments are confidential and exempt from public inspection and copying, and disclosing one to the Attorney General does not waive attorney-client privilege or work product protection. The requirements apply to processing activities created or generated after .
INCDPA gives an Indiana consumer the right to confirm and access their personal data, correct inaccuracies, delete data, obtain a portable copy, and opt out of targeted advertising, the sale of personal data, and profiling that produces a legal or similarly significant effect, exercisable against the controller.
A controller must respond without undue delay and no later than 45 days after receipt, with one additional 45-day extension available when reasonably necessary, and must inform the consumer of a decline and the means to appeal it on the same 45-day timeline. This is the ordinary 45-plus-45 response model used across most states, not the shortened timeline Florida uses.
Section 1 of IC 16-39-1 applies to all health records except mental health records, which IC 16-39-2, IC 16-39-3 and IC 16-39-4 govern. Article 39 of title 16 does not apply to records regarding communicable diseases, which IC 16-41-8-1 governs, or to alcohol and other drug abuse patient records, which 42 CFR Part 2 governs.
Section 1(c) of IC 16-39-1 requires a provider, on written request and reasonable notice, to supply to a patient the health records possessed by the provider concerning the patient. Section 1(d) of IC 16-39-1 requires a provider, on a patient's written request and reasonable notice, to furnish the patient or the patient's designee a copy of the patient's health record used in assessing the patient's health condition.
Section 1(e) of IC 16-39-1 requires a provider to provide the requested health records within 30 days after the written request, unless within the first 30 days it seeks an extension of not more than 30 days and informs the patient in writing of the reasons and the date. Section 1(f) of IC 16-39-1 lets the state department impose a fine against a provider not to exceed $5,000 for not complying with the section.
Section 2 of IC 16-39-1 requires a provider, on a patient's written request and reasonable notice, to provide the patient or the patient's designee access to, or a copy of, the patient's x-ray image at no cost.
Section 4 of IC 16-39-1 requires a patient's written consent for release of the patient's health record to include the name of the person requested to release the record, the recipient, the purpose, a description of the information, the signature and date, a statement that the consent can be revoked, and the date or event on which it expires.
Section 5 of IC 16-39-1 lets a provider who is a health care professional withhold requested information from the patient if the provider reasonably determines it is detrimental to the patient's physical or mental health or likely to cause the patient to harm the patient or another. Section 339 of IC 16-18-2 defines the state department as the department established by IC 16-19-1-1.
Section 1 of IC 16-19-1 establishes the Indiana department of health, which may officially be known as the Indiana department of health or the state department of health. The provisions this entry describes came into force on different days.
The Indiana Attorney General has exclusive authority to enforce INCDPA, with a civil penalty of up to $7,500 per violation plus recoverable investigation expenses. Before suing, the Attorney General must give a controller or processor 30 days' written notice identifying the specific provisions violated; if the violation is cured within that period and the controller or processor provides a written attestation of the cure, the Attorney General may not initiate an action.
This cure right is mandatory, not discretionary, and carries no sunset date anywhere in Article 15, unlike Maryland's, New Jersey's, and Minnesota's time-limited or discretionary cure provisions. The chapter creates no private right of action.
In chapter 24 of article 4 of title 24 of the Indiana Code, consumer genetic testing means a service in which a person provides an individual with a means of submitting a sample of the individual's biological material directly to the person, performs or causes to be performed genetic testing on it, and returns the results directly to the individual.
The chapter excludes genetic testing of a health care provider's patient that is requested by the provider for diagnosis, treatment or prevention and is subject to Health Insurance Portability and Accountability Act (HIPAA), testing required by a court order, testing for a law enforcement investigation, testing at the request of a coroner or medical examiner, and research subject to the federal human subject protection rules.
A consumer genetic testing provider is a person that, in the ordinary course of business, offers consumer genetic testing or collects, uses or analyzes genetic data that results from a consumer genetic testing product or service and is provided by a consumer, in exchange for consideration. Section 8 of the chapter bars a provider from performing genetic testing on an individual's biological material unless it has given the individual a written disclosure of its privacy policy.
Section 9 of the chapter bars a provider from testing beyond what the individual requested, using the biological material for another purpose, giving a third party access, retaining the material or identifiable data for more than 30 days, or marketing based on the results unless the provider has received the individual's freely given, specific, informed and unambiguous consent.
Section 9(c) of the chapter provides that consent is not freely given, specific, informed and unambiguous if it is provided by the individual's inaction, by acceptance of general or broad terms of service, by closing, muting, pausing or hovering over content, or through an interface designed to subvert user choice.
Section 10(a) of the chapter requires a provider to implement commercially reasonable security measures to protect the biological material and the resulting data from unauthorized access, destruction, use, modification or disclosure. Section 10(a) of the chapter requires a provider to comply with a revocation of consent not later than 30 days after the individual communicates it, including by destroying the biological material and the resulting data.
Section 10(b) of the chapter bars a provider from providing data, other than deidentified data, resulting from genetic testing to an insurer, to a person that provides information to insurers for underwriting or rating of risks, or to a person that employs the individual, regardless of the individual's consent to third-party access.
Section 11 of the chapter gives the attorney general exclusive authority to enforce the chapter, by an action for an injunction and a civil penalty not to exceed $7,500 for each violation. Section 11(d) of the chapter requires the attorney general to give a provider 30 days written notice of the alleged violation before bringing an action, and bars the action if the provider cures the violation and gives an express written statement within that period.
Section 11(f) of the chapter provides that nothing in the section may be construed as providing the basis for a private right of action for violations of the chapter or any other law. Public Law 233 of 2025 added the chapter to the Indiana Code. House Bill 1521 of the 2025 session became Public Law 233, and the Governor signed it on .
Section 2 of IC 22-9-14 bars a person from discriminating against an individual on the basis of the individual's solicitation and use of consumer genetic testing services or on the basis of the results of genetic testing performed by a consumer genetic testing provider.
Section 2 of IC 22-9-14 lists denying the individual access to the person's goods or services, charging the individual a different rate for them, and suggesting that the individual will be subject to either measure as forms of the discrimination it bars. Section 1 of IC 22-9-14 applies the definitions in IC 24-4-24 throughout the chapter. Public Law 233 of 2025 added the chapter to the Indiana Code.
Subsection (d) of section 2 of IC 16-39-5 bars an insurance company other than a life insurance company from obtaining the results of any genetic screening or testing without a separate written consent by an individual at the time of application for insurance or at any other time.
Subsection (d) of section 2 of IC 16-39-5 requires the consent form to indicate in at least 10 point boldface type that the individual need not consent to releasing the results of any genetic testing or screening, and to be approved by the commissioner before use.
Subsection (e) of section 2 of IC 16-39-5 provides that an insurance company other than a life insurance company is not liable if it inadvertently receives the results of genetic testing or screening without the separate written consent, but may not use the results in violation of IC 27-8-26. No day on which the provisions this entry describes came into force has been located.
Section 1 of IC 27-8-26 applies the chapter to accident and sickness insurance policies issued, delivered or renewed in Indiana, health maintenance organization contracts, health care plans of a state or local governmental entity that cover services on a self-insurance basis, and self-funded employee welfare benefit plans.
Section 1 of IC 27-8-26 excludes accident-only, credit and disability income insurance, coverage issued as a supplement to liability insurance, worker's compensation, automobile medical payment insurance and life insurance.
Section 5 of IC 27-8-26 bars an insurer processing an application for health care services coverage, or determining insurability, from requiring genetic screening or testing, considering information from it adversely, inquiring into its results, or deciding adversely on entries about its results. Section 6 of IC 27-8-26 bars an insurer from asking an applicant for the results of genetic screening or testing, or questions designed to ascertain the results.
Section 7 of IC 27-8-26 bars an insurer from canceling, refusing to issue, refusing to renew or refusing to enter into a contract for health care services coverage based on the results of genetic screening or testing. Section 8 of IC 27-8-26 bars an insurer from delivering, issuing, renewing or executing a contract for health care services coverage in Indiana that limits benefits or establishes premiums based on the results of genetic screening or testing.
Section 9 of IC 27-8-26 lets an insurer consider the results of genetic screening or testing if the applicant or the individual seeking renewal voluntarily submits them and they are favorable. Section 10 of IC 27-8-26 requires the commissioner to enforce the chapter. Section 11 of IC 27-8-26 makes a violation of the chapter an unfair and deceptive act or practice in the business of insurance under IC 27-4-1-4.
Section 0.1 of IC 27-8-26 provides that the chapter applies to all applications and policies for accident and sickness insurance delivered, issued for delivery, renewed or executed after . Section 6 of IC 27-4-1 lets the commissioner, after a hearing, order a civil penalty of not more than $25,000 for each act or violation of the chapter, or of not more than $50,000 if the person knew or reasonably should have known of the violation.
Ind. Code § 16-39-5-3Official text of the Indiana Code (2026 Code), Indiana General Assembly (iga.in.gov)
In force.Binds public and private bodies.
What this law does
Section 3(c) of IC 16-39-5 provides that the original health record of the patient is the property of the provider and may be used by the provider without specific written authorization for legitimate business purposes, including claims, collection of accounts, litigation defense, quality assurance, peer review, and scientific, statistical and educational purposes.
Section 3(d) of IC 16-39-5 requires a provider to protect the confidentiality of the health record at all times in a use under subsection (c), and permits disclosure of the patient's identity only when disclosure is essential to the provider's business use or to quality assurance and peer review.
Section 3(e) of IC 16-39-5 lets a provider or the Indiana archives and records administration disclose a health record to another provider or to a nonprofit research organization for a scientific, statistical or educational project, and requires each party that receives information to protect the confidentiality of the record and not to disclose the patient's identity except as the article allows.
Section 3(f) of IC 16-39-5 lets a provider disclose a health record to an Indiana hospital trade association for a data aggregation project, and permits disclosure of a patient's identity to the association only when the disclosure is essential to the project. Section 3(j) of IC 16-39-5 makes a person who recklessly violates or fails to comply with subsections (e) through (h) guilty of a Class C infraction, with each day a violation continues a separate offense. The provisions this entry describes came into force on different days.
INCDPA classifies racial or ethnic origin, religious belief, a health diagnosis made by a health care provider, sexual orientation, citizenship or immigration status, genetic or biometric data processed to uniquely identify a specific individual, a known child's data, and precise geolocation data as sensitive data requiring the consumer's consent before processing, except that a known child's sensitive data may instead be processed under COPPA's consent framework.
'Biometric data' means data from automatic measurement of an individual's biological characteristics used to identify them, such as a fingerprint, voiceprint, or retina or iris image, but the definition carries a blanket, unconditional exclusion for a physical or digital photograph, a video or audio recording, or any data generated from either, with no clawback for data generated to identify someone.
A faceprint or voiceprint extracted from a recording therefore falls outside both biometric data and sensitive data under Indiana law, regardless of the purpose for which it was extracted; only a biometric identifier captured directly, such as from a live scanner, triggers this consent duty.
Indiana's computer trespass statute, Ind. Code § 35-43-2-3(b), makes it a Class A misdemeanor to knowingly or intentionally access a computer system or network without the consent of its owner or the owner's licensee. The statute does not define consent, has no security-measure or harm element, and defines access to include retrieving data from a computer system, so the offense turns on what the owner consented to.
Subsections (c) and (d) of the same section separately punish using, selling or distributing a hoarding program, software designed to bypass a security measure that limits how much merchandise one person may purchase online; they concern software built to defeat purchase limits, not a page crawler. A separate offense, Ind. Code § 35-43-1-8, makes it a Level 6 felony to knowingly or intentionally and without authorization disrupt or deny computer system services to an authorized user.
The statute has no exception for a page the owner serves openly, and no Indiana appellate decision applies the consent element to a crawler or to an open page, so whether serving a page openly is itself consent to an ordinary request for it is open, as is whether a robots.txt directive withdraws consent.
An owner's express refusal is different: a CAPTCHA, block or rate limit that keeps a visitor out is the owner refusing consent, so knowing access past it is access without consent, with no further element in the offense. A written demand to stop states the same refusal, but the page stays open to everyone, and no Indiana statute or decision says whether a letter alone withdraws consent to it; no Indiana decision has applied either to a crawler.
House Enrolled Act 1360 (2026), effective , makes no crawler's conduct unlawful: it amends the Access to Public Records Act to define data scraping as use of an automated system to extract data from websites and other Internet accessible sources, and it lets a public agency run a CAPTCHA-gated records portal, decline a records request it suspects is data scraping, and delay or surcharge requests from automated systems.
On contract, Indiana courts require reasonable notice and manifested assent, and the Court of Appeals enforces terms a user accepts by clicking (Adsit Co. v. Gustin; Jallali v. National Board of Osteopathic Medical Examiners), so crawling in breach of accepted terms risks a contract claim; no Indiana appellate decision applies the notice test to terms shown only through a link.
Trespass to chattels in Indiana requires dispossession, impairment of the chattel's condition, quality or value, loss of its use for a substantial time, or harm to another legally protected interest (Coleman v. Vukovich), and no Indiana appellate decision applies it to server load from crawling.
Copyright and text-and-data-mining law are federal: fair use governs, whether commercial mining is fair use is unsettled, and neither Indiana law nor the Copyright Act provides a mining opt-out; Indiana has no database right and no state mining exception. No Indiana statute specifically governs the use of data to train an AI model; the state's AI measures reach election media, intimate images and insurance claim decisions. No Indiana statute or appellate decision gives robots.txt legal effect.
Indiana's consumer data protection act, Ind. Code art. 24-15, excludes publicly available information from personal data and is enforced only by the Attorney General.
Section 35-43-2-3(b) provides that a person who knowingly or intentionally accesses a computer system, computer network, or any part of either without the consent of the owner or the owner's licensee commits computer trespass, a Class A misdemeanor. This is phrased as lack of the owner's consent, with no separate exceeds-authority prong. The same article separately punishes, at section 35-43-1-8, knowing and intentional unauthorized disruption or denial of computer system services.
House Enrolled Act 1360 adds new IC 5-14-3-2(d), defining data scraping to mean use of an automated system to extract data from websites and other Internet accessible sources. New IC 5-14-3-3.3 authorizes, but does not require, a public agency to build a records-request portal using a CAPTCHA or an equivalent mechanism for ensuring that a requestor is a human, to require verification of a requestor's physical address, and to have the portal indicate whether the requestor is an Indiana resident.
New IC 5-14-3-8.1 lets an agency give priority to Indiana residents and to civic, journalistic, academic, or personal-use requests, while delaying or surcharging requests identified as originating from out-of-state entities or automated systems. New IC 5-14-3-11 requires an agency to report suspected automated, phishing, or data-scraping requests to the state Public Access Counselor through a standardized mechanism. The enrolled act carries a effective date on every section.
IC 24-15-2-19(b) defines personal data to exclude de-identified data, aggregate data, or publicly available information.
IC 24-15-2-26 defines publicly available information as information that is lawfully made available through federal, state, or local government records, or that a business has a reasonable basis to believe is lawfully made available to the general public through widely distributed media, by the consumer to whom the information pertains, or by a person to whom the consumer has disclosed it, unless the consumer has restricted the information to a specific audience.
The exclusion removes information lawfully made available through government records or widely distributed media from the definition of personal data itself, rather than exempting it by a separate carve-out.
IC 24-15-1-1(a) applies the Act to a person conducting business in Indiana or targeting Indiana residents that, during a calendar year, controls or processes personal data of at least 100,000 Indiana consumers, or of at least 25,000 Indiana consumers while deriving more than half of its gross revenue from selling personal data. Enforcement is Attorney-General-only; there is no private right of action.
Indiana's private-sector security-topic presence is a disposal duty for persons holding customer information (IC 24-4-14) and a standalone duty sitting inside its breach-notification statute: Ind.
Code sec. 24-4.9-3-3.5, added to the Disclosure of Security Breach Act by P.L.137-2009 and amended by P.L.76-2017, requires a 'data base owner' (a person that owns or licenses computerized data including personal information of an Indiana resident) to implement and maintain reasonable procedures to protect and safeguard that personal information from unlawful use or disclosure, and to dispose of records containing it only by shredding, incinerating, mutilating, erasing, or otherwise rendering it illegible.
A data base owner already following its own compliance plan under a named federal privacy or security regime (the USA PATRIOT Act, Executive Order 13224, the Driver's Privacy Protection Act, the Fair Credit Reporting Act, the Gramm-Leach-Bliley Act, or Health Insurance Portability and Accountability Act (HIPAA)) is exempt from this duty, except that a current or former health care provider that claimed the HIPAA-based exemption remains bound for personal information, including health records, if its own compliance plan does not require, or is not implemented to provide, that protection once the provider stops being a HIPAA covered entity.
Indiana's codified history notes for this section carry only a public-law-and-year citation with no day-precise commencement date, so no effective date is recorded here, the same source-quality gap this jurisdiction's privacy-topic row records for the surrounding breach-notification sections. The duty sits structurally the same way New York's SHIELD Act splits across two topics: the Disclosure of Security Breach Act's title and its notification sections (Ind.
Code secs. 24-4.9-3-1 through 24-4.9-3-4, 24-4.9-4-1, 24-4.9-4-2) are already this jurisdiction's privacy-topic row, a breach-notification duty about personal data, while section 3-3.5's safeguards and disposal duty is a standalone security-programme provision inside that same article, so it is filed here instead. The Indiana Consumer Data Protection Act's own security clause, Ind.
Code sec. 24-15-4-1(3), requiring a controller to establish, implement, and maintain reasonable administrative, technical, and physical data security practices appropriate to the volume and nature of the personal data at issue, is likewise not repeated here: it is one subsection of INCDPA's own controller-duties chapter, the same shape as the General Data Protection Regulation's Article 32 and the Texas Data Privacy and Security Act's section 541.101(a)(2), and it is already researched as part of this jurisdiction's privacy-topic INCDPA row.
No enacted Indiana statute was located that sets security requirements a connected device or software product must meet before or after it reaches the market, comparable to California's, Oregon's, or Connecticut's connected-device statutes or the Cyber Resilience Act; a targeted search for an Indiana connected-device or IoT security law returned no citable statutory text on the Indiana General Assembly's or Justia's own Indiana Code pages, only unsourced secondary summaries that are not relied on for this finding, so it is treated as a researched absence rather than a gap in coverage.
Outside the water and wastewater systems' report under IC 13-18-16.5, Indiana has no general private-sector duty to report an exploited vulnerability or a security incident to an authority or to users; IC 4-13.1-2-9 requires state agencies and political subdivisions to report a cybersecurity incident to the Indiana Office of Technology within two business days, and 2025's Senate Enrolled Act 472, effective , requires a public entity's own technology-resources and cybersecurity policies, each filed as a row of its own with no activity flag.
Indiana's Insurance Data Security Law, Ind.
Code sec. 27-2-27 (P.L.130-2020, applicable after ), requires a 'licensee,' any person licensed, authorized to operate, or registered, or required to be, under Indiana's insurance title, to develop, implement, and maintain a comprehensive written information security program and to notify the insurance commissioner of a cybersecurity event, with an exemption for a licensee under 50 employees, under $5,000,000 in gross annual revenue, or under $10,000,000 in year-end total assets, no private right of action, and an affirmative tort defense for a compliant licensee; its program duty is filed as a row of its own, flagged for an insurer, and the notice to the commissioner is this jurisdiction's privacy-topic row.
Section 3.5 is enforced solely by the Indiana Attorney General as a deceptive act, with a civil penalty of up to $5,000 per deceptive act (a related series of acts or omissions counts as one), and it creates no private right of action, distinct from the $150,000-per-act penalty that governs a failure of the article's own breach-notification duty. Indiana's Insurance Data Security Law requires an insurance licensee to maintain a comprehensive, written information security program.
A state agency or political subdivision must report any cybersecurity incident to the Office of Technology not later than two business days after discovery. A public entity must adopt a cybersecurity policy by . A public water or wastewater entity within the chapter must report a cybersecurity incident to the Office of Technology within 24 hours if it impacts operations.
An entity that is not a public entity and connects to the technology infrastructure of the state after must have completed a cybersecurity assessment within the two year period before the connection. A state educational institution must submit a summary analysis report of cyber security incidents to the Office of Technology on a quarterly basis.
A licensee must develop, implement, and maintain a comprehensive, written information security program that is based on its risk assessment and contains administrative, technical, and physical safeguards for nonpublic information and its information systems. A licensee's risk assessment must include implementing information safeguards for the threats it identifies and assessing the effectiveness of their key controls, systems, and procedures at least one time each year.
A licensee must establish a written incident response plan designed to promptly respond to, and recover from, any cybersecurity event. Each insurer domiciled in Indiana must submit to the commissioner, not later than April 15 each year, a written statement certifying that it is in compliance with sections 16 through 20 of the chapter.
A licensee is exempt from sections 16 through 20 if it has fewer than fifty employees, less than five million dollars in gross annual revenue, or less than ten million dollars in year-end total assets. If a licensee violates the chapter, the insurance commissioner may, after notice and hearing, suspend or revoke the license, certificate of authority, or registration of the licensee. The chapter does not create a private right of action against any person. The chapter applies after .
A public entity means a political subdivision, state agency, school corporation, or state educational institution. Not later than , each public entity must adopt a policy governing use of technology resources by its employees, a cybersecurity policy, and a training program that is mandatory for its employees. Not later than December 31 of each odd-numbered year, a public entity must submit its cybersecurity policy to the Office of Technology.
A public entity that engages a third party to assess its cybersecurity policy must provide the results of the assessment to the Office of Technology. A public entity that connects to the technology infrastructure of the state after must have completed a cybersecurity assessment within the three year period before the connection. The provisions this entry describes came into force on different days.
The chapter applies to a community water system with a population of five hundred or more, a publicly owned treatment works, or a Class III or Class IV semipublic facility that uses a computerized system to monitor and control its processes from a central location. An entity must conduct a cybersecurity vulnerability assessment at least once per calendar year.
Beginning in 2026, not later than December 31 of each even-numbered year, an entity must submit a certification to the department via a secured portal. Before September 1 of each year, an entity must give the Office of Technology the name and contact information of its primary reporter of a cybersecurity incident. An assessment must use an assessment tool or framework approved by the department and the Office of Technology.
Ind. Code sec. 24-4.9-3-3.5Official statute text, Indiana Code Article 4.9, Disclosure of Security Breach Act
In force.Binds private bodies.
What this law does
A data base owner, a person that owns or licenses computerized data including personal information of an Indiana resident, must implement and maintain reasonable procedures, including taking any appropriate corrective action, to protect and safeguard that personal information from unlawful use or disclosure.
A data base owner must also not dispose of or abandon records or documents containing unencrypted and unredacted personal information of Indiana residents without shredding, incinerating, mutilating, erasing, or otherwise rendering it illegible or unusable. A data base owner that maintains its own data security procedures under a listed federal privacy or security regime, and complies with that regime's own reasonable-procedures requirement, is exempt.
A current or former health care provider that claimed the Health Insurance Portability and Accountability Act (HIPAA)-based exemption remains bound for personal information, including health records, if its own compliance plan does not require, or is not implemented to provide, that protection once the provider stops being a HIPAA covered entity.
A knowing or intentional failure to comply is a deceptive act, actionable only by the Indiana Attorney General, and a related series of acts or omissions in violation of this section constitutes one deceptive act. No day on which the provisions this entry describes came into force has been located.
A person who disposes of the unencrypted, unredacted personal information of a customer without shredding, incinerating, mutilating, erasing, or otherwise rendering the information illegible or unusable commits a Class C infraction. The offense is a Class A infraction if the person disposes of the unencrypted, unredacted personal information of more than one hundred customers or has a prior unrelated judgment for a violation of the section.
To dispose of personal information means to discard or abandon the personal information of a customer in an area accessible to the public. A customer is a person who has received, or contracted for, the provision of goods or services from another person holding the person's personal information, or who provides personal information to another person in connection with a transaction with a nonprofit corporation or charitable organization.
A person is an individual, a partnership, a corporation, a limited liability company, or another organization. Personal information has the meaning set forth in IC 24-4.9-2-10 and includes information stored in a digital format. That definition covers a Social Security number that is not encrypted or redacted, and an individual's name together with a driver's license number, state identification card number or credit card number that is not encrypted or redacted.
Personal information is redacted if it has been altered or truncated so that not more than five digits of a Social Security number are accessible. The chapter does not apply to the executive, judicial, or legislative department of state government or any political subdivision.
It also does not apply to a person that maintains and complies with a disposal program under the USA Patriot Act, Executive Order 13224, the Driver's Privacy Protection Act, the Fair Credit Reporting Act, the Financial Modernization Act of 1999 or the Health Insurance Portability and Accountability Act, if applicable.
A person in the business of waste collection is outside the chapter except to the extent the person holds a customer's personal information directly in connection with the business of waste collection. No day on which the provisions this entry describes came into force has been located: the codified text carries only a public-law-and-year citation, P.L.125-2006, with no day.
Ind. Code sec. 13-18-16.5-1(b)(4)Official text of Indiana Code chapter 13-18-16.5, Public Water and Wastewater Cybersecurity, on the Indiana General Assembly site
In force since .Binds public and private bodies.
What this law does
The chapter applies to a community water system with a population of five hundred or more, a publicly owned treatment works, or a Class III or Class IV semipublic facility that uses a computerized system to monitor and control its processes from a central location. When an actual or reasonably suspected cybersecurity breach occurs, an entity must report the incident to the Office of Technology not later than twenty-four hours after discovery if the incident impacts the operations of the entity.
If the incident does not impact the operations of the entity, the report is due not later than two business days after discovery.
Ind. Code sec. 4-13.1-2-9Official text of Indiana Code chapter 4-13.1-2, Office of Technology, on the Indiana General Assembly site
In force since .Binds government bodies.
What this law does
A state agency other than a state educational institution, and a political subdivision, must report any cybersecurity incident to the Office of Technology without unreasonable delay and not later than two business days after discovery. The reporting duty excludes a department of public utilities established under section 8-1-11.1 of the Indiana Code and an entity subject to the water and wastewater cybersecurity chapter.
Each such entity must give the Office of Technology the name and contact information of its primary reporter of a cybersecurity incident before September 1 of each year. Nothing in the section requires reporting that conflicts with federal privacy laws or is prohibited due to an ongoing law enforcement investigation.
Age gating law2 instruments, 1 in force, 1 not yet in force
Research summary (112 words)
Indiana's SB 17 (2024) requires age verification on adult oriented websites and has been in effect since 2024; after the U.S. Supreme Court upheld a materially identical Texas law in June 2025, the Seventh Circuit remanded Indiana's case with instructions to rule for the state.
A 2026 law (HEA 1408) separately requires a covered social media provider to use commercially reasonable means, such as a neutral age screen, to determine an account requester's age and state of residence, and to obtain verifiable parental consent before creating an account for an Indiana resident under 16, taking effect . Indiana has not enacted an app store age verification or design code law.
Ind. Code ch. 24-4-23official Indiana Code text and Indiana General Assembly bill record
In force since .Binds private bodies.
What this law does
Requires an adult oriented website, as the chapter defines that term, to use a reasonable age verification method before granting access, and bars retention of a user's identifying information after verification. The Attorney General or a harmed parent may sue for injunctive relief and damages.
Not yet in force.from ,in 2 months It starts to bind on .
Binds private bodies.
What this law does
The act adds Indiana Code article 24-16 and binds a social media provider, defined as an online forum, website, or application that functions primarily to let registered users upload or access content, uses algorithms to select content for users, has an addictive feature such as continuously loading content or autoplay video, has a user base in which ten percent or more of the daily active users under 16 spend an average of two hours per day or longer on it, and is owned or operated by a person that generated at least one billion dollars in gross revenues worldwide in one or more of the three preceding years.
A provider that receives an account request from an Indiana resident must use commercially reasonable means, such as a neutral age screen, to determine the individual's age and state of residence, and may create the account of an individual under 16 only with verifiable parental consent from a parent or legal guardian.
The provider must configure the account of a registered user it knows or has reason to know is an Indiana resident under 16 so that the account cannot receive direct communications except from a linked account, cannot appear in search results except to a person holding a linked account, and cannot be shown content, recommendations, or advertising based on the adolescent's patterns of use, or the addictive features, and the adolescent may not change or bypass that configuration.
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
Indiana has no press-publisher neighbouring right, mandatory platform-to-publisher bargaining code, or hot-news misappropriation statute, and no bill creating one is pending before the General Assembly.
Indiana Code Title 24 (Trade Regulation), which carries the state's antitrust, trademark, consumer-sales, and consumer-data-protection provisions, contains no article addressing reproduction of news content, compelled payment to news publishers, or a machine-readable text-and-data-mining reservation. No Indiana appellate decision recognizing a common-law hot-news misappropriation claim, on the model of International News Service v. Associated Press, has been located.
A news aggregator operating in Indiana is governed by the same federal copyright fair-use framework, and the absence of any state-law press-publisher right or bargaining charge, that applies nationally.
As of .
Case law
No current case law for Indiana AI law
No current case law for Indiana privacy law
No current case law for Indiana scraping law
No current case law for Indiana cybersecurity law
No current case law for Indiana communications law
No current case law for Indiana content moderation law
No current case law for Indiana product and AI liability law
No current case law for Indiana digital accessibility law
No current case law for Indiana age gating law
No current case law for Indiana reuse law
Reporting clocks that run here20 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 Indiana 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.
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.
When an actual or reasonably suspected cybersecurity breach occurs, report the cybersecurity incident to the Office of Technology not later than 24 hours after discovery if it impacts the operations of the entity, or not later than two business days after discovery if it does not, in a format prescribed by the chief information officer of the Office of Technology.
Report any cybersecurity incident to the Office of Technology, using your best professional judgment, without unreasonable delay and not later than two business days after discovery, in a format prescribed by the chief information officer.
As an insurance licensee, notify the insurance commissioner as promptly as possible, and not later than three business days after you determine that a cybersecurity event involving nonpublic information in your possession has occurred, if Indiana is your state of domicile as an insurer or your home state as a producer and the event has a reasonable likelihood of materially harming a consumer residing in Indiana or a material part of your normal operations (Ind. Code 27-2-27-21(c)(1)).
Notify the commissioner within the same three business days if you reasonably believe the nonpublic information of at least 250 consumers residing in Indiana was affected and either another state, federal or local law requires notice of the event or the event has a reasonable likelihood of materially harming a consumer residing in Indiana or a material part of your normal operations (27-2-27-21(c)(2)).
Disclose a breach to affected Indiana residents without unreasonable delay and no later than 45 days after discovering the breach, if you know, should know, or should have known that the unauthorized acquisition has resulted in or could result in identity deception, identity theft, or fraud affecting them.
Make every disclosure or notification the statute requires, including notice to the Indiana Attorney General, notice to each nationwide consumer reporting agency, and a data holder's notice to the data base owner, without unreasonable delay and no later than 45 days after discovering the breach.
The law of the United States, which applies in Indiana
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.
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.
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.
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.
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.
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.
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)).
Rapidly report a cyber incident to the Department of Defense within 72 hours of discovering it, at the Department's DIBNet portal (dibnet.dod.mil), using a DoD-approved medium assurance certificate that you must obtain before you need to file a report.
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.
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.
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)).
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.
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.
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.
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.
AIDrafted 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.