Law / United States / Oregon

Oregon

Oregon has 1 local jurisdiction That local jurisdiction has law of its own, on a page of its own, listed below.

34 of 35 named instruments researched to a stage, across six of the ten areas of law we track: 33 in force and 1 not yet in force. As of .

When each starts21 of 34 carry a date, 13 do not. Earlier is before 2015.
Before 2015: 3 instruments (3 in force) earlier 2015: 0 instruments 2016: 2 instruments (2 in force) 2017: 1 instrument (1 in force) 2018: 0 instruments 2019: 0 instruments 2020: 1 instrument (1 in force) ’20 2021: 0 instruments 2022: 0 instruments 2023: 0 instruments 2024: 8 instruments (8 in force) 2025: 0 instruments ’25 2026: 5 instruments (5 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 15
  3. Scraping law 2
  4. Cybersecurity law 5
  5. Communications law 7
  6. Content moderation law not researched
  7. Product and AI liability law not researched
  8. Digital accessibility law not researched
  9. Age gating law 1
  10. Reuse law

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

Research summary (289 words)

Oregon adds four sector-specific AI disclosure and prohibition duties on top of the federal baseline, and has no general-purpose AI risk-management statute. A 2024 election-law amendment requires a disclosure whenever a campaign communication uses synthetic media to create a realistic but false depiction of a candidate (ORS 260.268, created by SB 1571).

A 2025 amendment extends the state's nonconsensual intimate-image crime to a digitally created, manipulated or altered depiction that is reasonably realistic, reaching an AI-generated or deepfake image on the same terms as an authentic one (ORS 163.472, amended by HB 2299). A separate 2025 act bars any nonhuman entity, including an agent powered by artificial intelligence, from using a protected nursing title (ORS 678.027, created by HB 2748).

A 2026 act requires an operator of an AI companion chatbot to disclose that a user is interacting with artificially generated output, run a suicide and self-harm detection protocol, and observe additional safeguards where a user is a minor, backed by a private right of action (Or. Laws 2026, ch. 85, SB 1546).

The Oregon Department of Justice issued guidance in December 2024 stating that the state's existing unlawful-trade-practices, consumer-privacy, breach-notification and civil-rights statutes already reach AI conduct, but that is guidance rather than a binding duty and is not catalogued as an instrument here.

A bill that would create a permanent Commission on Artificial Intelligence and a Chief Artificial Intelligence Officer within the Department of Justice (HB 3592) reaches only the state's own use of AI and is likewise not catalogued. No Oregon statute or reported decision was found addressing an AI-generated depiction of child sexual abuse beyond the federal baseline; ORS 163.684 to 163.689 (encouraging child sexual abuse) carry no 2025 or 2026 amendment on the point.

AI prohibited practices

Unlawful dissemination of an intimate image extended to AI-generated depictions (HB 2299)

ORS 163.472 (amended by 2025 Or. Laws ch. 116 (HB 2299))Oregon State Legislature, current Oregon Revised Statutes chapter 163

In force since . Binds public and private bodies.

What this law does

Oregon's crime of unlawfully disseminating an intimate image, previously limited to a photograph, film or other visual reproduction, now also reaches a digitally created, manipulated or altered depiction that is reasonably realistic, so a deepfake or AI-generated nude or sexual image of a real, identifiable person falls within the same crime as an authentic one.

The person must have caused the disclosure with intent to harass, humiliate or injure someone who did not consent, and a reasonable person must be harassed, humiliated or injured by it. A first offense is a Class A misdemeanor; a second or later offense is a Class C felony.

Law enforcement activity, legitimate medical, scientific or educational activity, legal proceedings, reporting to law enforcement, and images the depicted person voluntarily displayed publicly or that were created commercially with consent are excluded.

What it requires

AI sector rules

Use of nursing titles by a nonhuman entity (HB 2748)

ORS 678.027Oregon State Legislature, current Oregon Revised Statutes chapter 678

In force since . Binds public and private bodies.

What this law does

A nonhuman entity, including but not limited to an agent powered by artificial intelligence, may not use the title or abbreviation of Advanced Practice Registered Nurse, certified registered nurse anesthetist, clinical nurse specialist, licensed practical nurse, registered nurse, nurse practitioner, certified medication aide or certified nursing assistant.

The chapter carrying this section exempts only the employment of nurses in institutions or agencies of the federal government; a state or local government entity is otherwise bound the same as a private one, so an AI system interacting with patients in a state, local or private health care setting may not present itself under any of these titles.

What it requires

AI transparency

AI Companion Chatbot Safety Act (SB 1546)

Or. Senate Bill 1546, 2026 Regular SessionOregon Legislative Information System, enrolled Senate Bill 1546 (2026 Regular Session)

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

Binds private bodies.

What this law does

An operator of an artificial intelligence companion or companion platform, software designed to simulate a sustained human-like platonic, intimate or romantic relationship by retaining information across sessions, asking unprompted emotional questions and sustaining personal dialogue, must give users a clear and conspicuous notice that they are interacting with artificially generated output whenever a reasonable person could otherwise believe they were talking to a natural person.

An operator must maintain an evidence-based protocol for detecting suicidal or self-harm ideation that refers a user to the 988 crisis lifeline, or to a youth-specific lifeline where the operator identifies the user as under 25, and must publish its protocol and an annual incident report.

Where an operator knows or has reason to believe a user is a minor, it must prevent the companion from claiming to be sentient or human, simulating emotional dependence or romantic interest, role-playing a romantic relationship with a minor, or producing sexually explicit content, and must add periodic reminders that the output is artificially generated.

An individual who suffers an ascertainable loss because of a violation may sue for the greater of actual or statutory damages of $1,000 per violation, plus an injunction and, if they prevail, attorney fees. Customer-service, productivity, video-game and voice-assistant software are excluded, as are stand-alone voice-command devices. Passed by the Legislative Assembly in the 2026 regular session and assigned chapter 85. The chaptered law gives its effective date as .

What it requires

Campaign communication disclosure of synthetic media (SB 1571)

ORS 260.268 (created by 2024 Or. Laws ch. 62 (SB 1571))Oregon State Legislature, current Oregon Revised Statutes chapter 260

In force since . Binds public and private bodies.

What this law does

A campaign communication that includes synthetic media, an image, audio or video recording of a candidate's appearance, speech or conduct intentionally manipulated with artificial intelligence or similar digital technology to create a realistic but false depiction, must include a disclosure that the recording has been manipulated.

The Secretary of State, and in specified cases the Attorney General, may sue to enjoin a violation, and a court may impose a civil penalty of up to $10,000, which the statute makes the exclusive remedy. Interactive computer services, bona fide news coverage, paid broadcasters, periodicals that carry a corrective statement, and satire or parody are excluded.

What it requires

Privacy law15 instruments, 15 in force

Research summary (720 words)

The Oregon Consumer Privacy Act (OCPA), ORS 646A.570 to 646A.589, is Oregon's comprehensive consumer-privacy regime, enacted as S.B. 619 (2023), effective for most controllers. Organizations described in section 501(c)(3) of the Internal Revenue Code were exempt from it until . Every citation here rests on the official Oregon State Legislature site (oregonlegislature.gov) rather than on a private republisher.

'Oregon Consumer Privacy Act' is the popular name for S.B. 619; the codified sections carry no short-title or caption naming the Act, so the regime is named here in prose rather than quoted from a short title that does not exist. House Bill 2008 added a ban on selling precise geolocation data.

House Bill 2008 barred a controller from processing a consumer's personal data for targeted advertising or for profiling toward decisions with legal or similar effects, and from selling a consumer's personal data, if the controller knows or willfully disregards that the consumer is under 16 years of age. House Bill 2008 took effect on .

House Bill 3875 made the Act apply to a motor vehicle manufacturer and its affiliates that control or process personal data obtained from a consumer's use of a motor vehicle or a component of one, whatever the consumer-count thresholds. House Bill 3875 took effect on . Genetic or biometric data is one of OCPA's enumerated sensitive-data categories, unqualified by an identification-purpose clause.

Oregon's biometric-data definition also carries the most explicit clawback in this batch: it separately and by name brings facial mapping or facial geometry back into 'biometric data' whenever generated or used to identify a specific consumer, in addition to the general photo, audio, or video-derived-data clawback. A separate chapter, ORS 646A.604, governs breach notification, requiring notice to the Attorney General only once the number of affected consumers exceeds 250.

The Attorney General has exclusive enforcement authority under the Oregon Consumer Privacy Act, and the Act has no private right of action. Until the Attorney General had to notify a controller of a violation that the Attorney General determined the controller could cure, and the controller had 30 days to cure it before the Attorney General could sue. Since the Attorney General is no longer required to give controllers notice and an opportunity to cure.

The notice duty that section 5 of chapter 417, Oregon Laws 2025, kept for certain noncommercial educational broadcast stations was repealed on . Oregon's data broker law, ORS 646A.593, bars a data broker from collecting, selling or licensing brokered personal data within the state unless it first registers with the Department of Consumer and Business Services.

ORS 192.535 bars a person from obtaining genetic information from an individual, or from an individual's DNA sample, without first obtaining the informed consent of the individual or the individual's representative, subject to listed exceptions. ORS 746.135 bars a person from using genetic information to reject, deny, limit, cancel, refuse to renew, increase the rates of or otherwise affect any policy for hospital or medical expenses.

The purpose of ORS 746.600 to 746.690 is to establish standards for the collection, use and disclosure of personal information gathered in connection with insurance transactions by insurers, insurance producers or insurance-support organizations. ORS 646A.620(1) bars a person from printing a consumer's Social Security number on a card required to access products or services and from publicly posting or displaying it unless it is redacted, among other prohibitions.

ORS 336.184 bars an operator of a website, service or application used primarily for kindergarten through grade 12 school purposes from selling a student's information and from engaging in targeted advertising, among other prohibitions. ORS 192.553 states the policy of the State of Oregon that an individual has the right to have protected health information safeguarded from unlawful use or disclosure and the right to access and review it.

ORS 659A.303 makes it an unlawful employment practice for an employer to seek to obtain, obtain or use genetic information of an employee or prospective employee, or of a blood relative of either, to discriminate against or restrict a right or benefit. ORS 659A.300 makes it an unlawful employment practice for an employer to subject an employee or prospective employee to a genetic test, among other listed tests, except as the section provides.

Breach notification

Notice of breach of security

ORS 646A.604official Oregon statute text, ORS 646A.604, Oregon Consumer Identity Theft Protection Act

In force. Binds public and private bodies.

What this law does

A covered entity subject to a breach of security, or that receives notice of one from a vendor, must give notice of the breach to each affected Oregon consumer, and must also notify the Attorney General once the number of Oregon consumers notified exceeds 250. The sections this entry groups came into force on different days.

What it requires

Comprehensive regime

Oregon Consumer Privacy Act (OCPA), general applicability and controller duties

ORS 646A.570, 646A.578official Oregon statute text, ORS 646A.570 to 646A.589, Oregon Revised Statutes

In force since . Binds private bodies.

What this law does

OCPA governs private-sector processing of Oregon consumers' personal data. Enacted as S.B. 619 (2023 Regular Session), Or. Laws 2023, ch. 369, effective for most controllers. Organizations described in section 501(c)(3) of the Internal Revenue Code were exempt from it until . Two 2025 amendments are already reflected in the current codified text. House Bill 2008 added a ban on selling precise geolocation data.

House Bill 2008 barred a controller from processing a consumer's personal data for targeted advertising or for profiling toward decisions with legal or similar effects, and from selling a consumer's personal data, if the controller knows or willfully disregards that the consumer is under 16 years of age. House Bill 2008 took effect on .

House Bill 3875 made the Act apply to a motor vehicle manufacturer and its affiliates that control or process personal data obtained from a consumer's use of a motor vehicle or a component of one, whatever the consumer-count thresholds. House Bill 3875 took effect on .

What it requires

Oregon Consumer Privacy Act, data protection assessments

ORS 646A.586official Oregon statute text, ORS 646A.570 to 646A.589, Oregon Revised Statutes

In force since . Binds private bodies.

What this law does

A controller must conduct and document a data protection assessment for each processing activity that presents a heightened risk of harm to a consumer, which includes targeted advertising, processing sensitive data, selling personal data and some profiling. The Attorney General may require a controller to provide any data protection assessment that is relevant to an investigation the Attorney General conducts under ORS 646A.589.

A controller must retain all of its data protection assessments for at least five years. A data protection assessment is confidential and is not subject to disclosure under Oregon's public records law. The assessment requirements apply only to processing activities that occur on and after , and are not retroactive.

What it requires

Data brokers

Oregon data broker registration with the Department of Consumer and Business Services

ORS 646A.593Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force since . Binds private bodies.

What this law does

A data broker is a business entity or part of a business entity that collects and sells or licenses brokered personal data to another person. Brokered personal data is computerized data about a resident individual that is categorized or organized for sale or licensing, including the individual's name, address, date or place of birth, biometric information and Social Security number.

A data broker may not collect, sell or license brokered personal data within Oregon unless it first registers with the Department of Consumer and Business Services. A data broker need not register if its collection, sale or licensing involves only a listed category, including publicly available information related to a resident individual's business or profession and information lawfully available from government records.

The definition of data broker excludes a business entity that collects information about a resident individual who is or was its customer, subscriber or user, its employee or agent or in a contractual relationship with it, its investor or donor, or in another relationship with it of a similar nature. The definition also excludes a business entity that performs services for, acts on behalf of or acts as an agent of a business entity that holds such a relationship with the individual.

The definition also excludes a consumer reporting agency, a person that furnishes information to one and a user of a consumer report, each to the extent the federal Fair Credit Reporting Act regulates its activities, and a financial institution, an affiliate or a nonaffiliated third party, each to the extent Title V of the Gramm-Leach-Bliley Act regulates its activities.

To register, a data broker submits its name, street address, telephone number, primary website and email address, pays a fee the department sets by rule, and declares whether and how a resident individual may opt out of its collection, sale or licensing. A registration is valid until December 31 of the year in which the department approves it. The department makes the information that business entities submit for registration publicly available on or by means of its website.

The department may impose a civil penalty of up to $500 for each violation, or $500 for each day of a continuing violation, and the total imposed on a data broker may not exceed $10,000 in a calendar year. Section 1 of House Bill 2052 of 2023 became operative on .

What it requires

Data subject rights

Oregon Consumer Privacy Act, consumer rights

ORS 646A.574, 646A.576, 646A.578official Oregon statute text, ORS 646A.570 to 646A.589, Oregon Revised Statutes

In force since . Binds private bodies.

What this law does

OCPA gives an Oregon consumer the right to confirm processing, obtain a categories disclosure, receive a portable copy, correct, delete, and opt out of targeted advertising, sale, and profiling for decisions with legal or similarly significant effects.

A controller must respond without undue delay and no later than 45 days after receipt, with one 45-day extension available; an appeal of a refusal must be decided within 45 days; and consent revocation must be honored no later than 15 days after receipt.

What it requires

Oregon insurance information practices: notice, access and correction, adverse underwriting decisions and disclosure limits

ORS 746.600 to 746.690Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force. Binds private bodies.

What this law does

The purpose of ORS 746.600 to 746.690 is to establish standards for the collection, use and disclosure of personal information gathered in connection with insurance transactions by insurers, insurance producers or insurance-support organizations.

The obligations of ORS 746.600 to 746.690 apply to insurers, insurance producers and insurance-support organizations that, for life or health insurance, collect, receive or maintain personal information about Oregon residents or engage in insurance transactions with Oregon residents, and, for other kinds of insurance, collect, receive or maintain personal information in connection with, or engage in, insurance transactions involving policies or certificates delivered, issued for delivery or renewed in Oregon, except as ORS 746.606 to 746.609 provide.

An insurance transaction is a transaction that involves insurance primarily for personal, family or household needs rather than business or professional needs and that entails the determination of an individual's eligibility for coverage, benefit or payment or the servicing of an insurance application, policy or certificate.

A licensee must provide a clear and conspicuous notice of personal information practices to a consumer who becomes a customer, not later than the date the licensee establishes a continuing relationship under which it provides insurance products or services used primarily for personal, family or household purposes. A licensee must give a customer a clear and conspicuous notice that accurately reflects its privacy policies and practices not less than annually during the relationship.

The privacy notice must be in writing and clear and conspicuous, and it must include the categories of personal information the licensee collects. An insurer, insurance producer or insurance-support organization may not use or authorize the use of pretext interviews to obtain personal information in connection with an insurance transaction.

A licensee or insurance-support organization may not use a disclosure authorization form unless it is clear and conspicuous and states the identity of the individual, the categories of information, the parties to whom it is disclosed and why, the individual's signature and date, how long it is valid, that the individual may revoke it and how.

An insurer, insurance producer or insurance-support organization must, within 30 business days of a written request for access to reasonably locatable recorded personal information, inform the individual of its nature and substance, let the individual see and copy it, disclose to whom it has been disclosed, and summarize the correction procedures.

Within 30 business days of a written request to correct, amend or delete recorded personal information, an insurer, insurance producer or insurance-support organization must either do so or notify the individual of its refusal, the reasons and the right to file a statement.

After an adverse underwriting decision, the insurer or insurance producer responsible must either give the consumer the specific reasons in writing or advise that the reasons are available on written request, and give a summary of the consumer's rights under ORS 746.650, 746.640 and 746.645.

A licensee or insurance-support organization may not disclose personal or privileged information about an individual collected or received in connection with an insurance transaction unless the disclosure meets one of the conditions ORS 746.665(1) lists. ORS 746.607 and 746.608 establish standards for health insurers that are subject to the information privacy provisions of both the federal Health Insurance Portability and Accountability Act and the federal Gramm-Leach-Bliley Act.

ORS 746.620, 746.630, 746.640, 746.645 and 746.665 do not apply to health insurers. A health insurer may use or disclose personal information of an individual in a manner consistent with an authorization from the individual or a personal representative.

The Director of the Department of Consumer and Business Services may examine and investigate the affairs of any insurer or insurance producer transacting insurance in Oregon, and of an insurance-support organization acting on behalf of one, to determine whether it has engaged in conduct in violation of ORS 746.600 to 746.690. A person whose rights under ORS 746.607(7), 746.640, 746.645 or 746.650 are violated may apply to a court for appropriate equitable relief.

A licensee or insurance-support organization that discloses information in violation of ORS 746.665, or a health insurer that uses or discloses information in violation of ORS 746.607(1) or (2), is liable for the actual damages the individual sustains. Except as ORS 746.680 provides, no remedy or recovery is available to individuals, in law or in equity, for a violation of any provision of ORS 746.600 to 746.690.

No person may knowingly and willfully obtain information about an individual from an insurer, insurance producer or insurance-support organization under false pretenses. The history note of ORS 746.610 lists section 3 of chapter 649, Oregon Laws 1981, and later amendments through chapter 364, Oregon Laws 2003. ORS chapters 731, 732, 733, 734, 735, 737, 742, 743, 743A, 743B, 744, 746, 748 and 750 may be cited as the Insurance Code.

A person that violates any provision of the Insurance Code is subject to a civil penalty the Director of the Department of Consumer and Business Services determines that does not exceed $10,000 for each offense. A violation of any provision of the Insurance Code for which no greater penalty is provided is a Class A misdemeanor. The sections this entry groups came into force on different days.

What it requires

Enforcement supervision

Oregon Consumer Privacy Act, Attorney General enforcement

ORS 646A.589official Oregon statute text, ORS 646A.570 to 646A.589, Oregon Revised Statutes

In force since . Binds private bodies.

What this law does

The Oregon Attorney General has exclusive authority to enforce OCPA; no other Oregon law creates a private right of action for a violation. Civil penalties run up to $7,500 per violation, and the statute of limitations is five years from the last violative act. Until the Attorney General had to notify a controller of a violation that the Attorney General determined the controller could cure, and the controller had 30 days to cure it before the Attorney General could sue.

Since the Attorney General is no longer required to give controllers notice and an opportunity to cure. The notice duty that section 5 of chapter 417, Oregon Laws 2025, kept for certain noncommercial educational broadcast stations was repealed on .

What it requires

Sensitive categories

Oregon Consumer Privacy Act, sensitive data categories and biometric data definition

ORS 646A.570(3), (18)official Oregon statute text, ORS 646A.570 to 646A.589, Oregon Revised Statutes

In force since . Binds private bodies.

What this law does

OCPA defines sensitive data as personal data that reveals a consumer's racial or ethnic background, national origin, religious beliefs, mental or physical condition or diagnosis, sexual orientation, status as transgender or nonbinary, status as a victim of crime or citizenship or immigration status; is a child's personal data; accurately identifies within a radius of 1,750 feet a consumer's present or past location, or the present or past location of a device that links or is linkable to a consumer; or is genetic or biometric data, which it lists independently and does not qualify with a for-the-purpose-of-uniquely-identifying clause the way several peer states phrase it.

'Biometric data' means data from automatic measurement of biological characteristics used to identify a consumer, and Oregon's clawback is the most explicit of any state in this batch: it separately and by name brings facial mapping or facial geometry back into biometric data whenever generated or used to identify a specific consumer, in addition to the general photo, audio, or video-derived-data clawback.

What it requires

Oregon Student Information Protection Act

ORS 336.184Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force since . Binds private bodies.

What this law does

ORS 336.184 may be cited as the Oregon Student Information Protection Act. An operator is the operator of an Internet website, online service, online application or mobile application with actual knowledge that it is used primarily for kindergarten through grade 12 school purposes and was designed and marketed for those purposes, to the extent it is operating in that capacity.

Covered information is personally identifiable information or materials that regard a student in Oregon and that the student or a parent provides to an operator, that a school employee or agent provides for kindergarten through grade 12 purposes, or that an operator gathers and that identify the student or are linked to information that does.

An operator may not knowingly engage in targeted advertising, target advertising on another site based on information acquired through the school use, amass a profile about a student except in furtherance of kindergarten through grade 12 school purposes, sell a student's information, or disclose covered information except as ORS 336.184(3)(a)(E) allows.

An operator must implement and maintain reasonable security procedures and practices appropriate to the nature of the covered information and must delete a student's covered information within a reasonable time if the school or school district requests deletion of data under its control. ORS 336.184 does not apply to general audience Internet websites, online services, online applications or mobile applications, even if login credentials created for an operator's site may be used to access them.

A violation of ORS 336.184 is an unlawful practice under ORS 646.607. The history note of ORS 336.184 lists section 2 of chapter 528, Oregon Laws 2015. Section 5 of Enrolled Senate Bill 187 (2015) provides that the Act takes effect . Section 4 of Enrolled Senate Bill 187 (2015) provides that the new operator section first applies to data created, provided or gathered on or after the effective date of the Act.

A court that finds a person willfully used a practice declared unlawful by ORS 646.607 may, on the prosecuting attorney's petition, set a civil penalty not exceeding $25,000 per violation. A prosecuting attorney who has probable cause to believe that a person is engaging in an unlawful trade practice may bring suit in the name of the State of Oregon to restrain the practice.

What it requires

Oregon employer prohibition on genetic tests of employees and applicants

ORS 659A.300(1), (5)Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force. Binds public and private bodies.

What this law does

Except as ORS 659A.300 provides, it is an unlawful employment practice for any employer to subject, directly or indirectly, any employee or prospective employee to a genetic test, among other listed tests. For ORS 659A.300, genetic test has the meaning given in ORS 192.531.

ORS 659A.300(1) does not prohibit a genetic test if the individual or the individual's representative grants informed consent in the manner ORS 192.535 provides and the test is administered solely to determine a bona fide occupational qualification. A person claiming to be aggrieved by an unlawful practice that ORS 659A.885(2) specifies, which includes a violation of ORS 659A.300, may file a civil action in circuit court, and the court may order injunctive and other equitable relief.

After a hearing the commissioner issues an appropriate cease and desist order against a respondent found to have engaged in an unlawful practice, and the order may require the respondent to pay an award of actual damages suffered by the complainant. No record stating the day on which the section came into force has been located.

What it requires

Oregon employer prohibition on obtaining, seeking or using genetic information of employees and applicants

ORS 659A.303Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force. Binds public and private bodies.

What this law does

It is an unlawful employment practice for an employer to seek to obtain, to obtain or to use genetic information of an employee or a prospective employee, or of a blood relative of either, to distinguish between or discriminate against or restrict any right or benefit otherwise due or available to an employee or a prospective employee. For ORS 659A.303, blood relative, genetic information and obtain genetic information have the meanings given in ORS 192.531.

An employer is any person who in Oregon, directly or through an agent, engages or uses the personal service of one or more employees, reserving the right to control the means by which the service is performed. A person includes a public body as defined in ORS 30.260. The history note of ORS 659A.303 lists former ORS 659.036 and section 4 of chapter 210, Oregon Laws 2011.

A person claiming to be aggrieved by an unlawful practice may file with the Commissioner of the Bureau of Labor and Industries a verified written complaint. After a hearing the commissioner issues an appropriate cease and desist order against a respondent found to have engaged in an unlawful practice, and the order may require the respondent to pay an award of actual damages suffered by the complainant. No record stating the day on which the section came into force has been located.

What it requires

Oregon genetic privacy statutes: consent, retention, destruction, access and disclosure limits for genetic information and DNA samples

ORS 192.531 to 192.549Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force. Binds public and private bodies.

What this law does

ORS 192.535 bars a person from obtaining genetic information from an individual, or from an individual's DNA sample, without first obtaining the informed consent of the individual or the individual's representative, unless an exception applies. Genetic information is information about an individual or the individual's blood relatives obtained from a genetic test. To obtain genetic information is to perform or get the results of a genetic test.

ORS 192.537 requires any person authorized by law or by an individual to obtain, retain or use an individual's genetic information or DNA sample to maintain its confidentiality and to protect it from unauthorized disclosure or misuse. ORS 192.537 bars a person from retaining another individual's genetic information or DNA sample without first obtaining authorization from the individual or the individual's representative, unless an exception applies.

ORS 192.537 requires the DNA sample of an individual from which genetic information has been obtained to be destroyed promptly on the specific request of the individual or the individual's representative, unless an exception applies. ORS 192.537 lets an individual or the individual's representative, promptly on request, inspect, request correction of and obtain genetic information from the records of the individual.

ORS 192.539 bars a person from disclosing, or being compelled by subpoena or any other means to disclose, the identity of an individual on whom a genetic test has been performed, or genetic information about the individual in a manner that permits identification, unless an exception applies.

A health care provider that is a covered entity and obtains an individual's biological specimen or clinical individually identifiable health information must notify the individual that it may be disclosed or retained by the provider for anonymous research or coded research. The history note of ORS 192.531 lists former ORS 659.700, section 1 of chapter 333, Oregon Laws 2003, section 1 of chapter 678, Oregon Laws 2005, and section 6 of chapter 800, Oregon Laws 2007.

ORS 192.531 defines the genetic privacy statutes as ORS 192.531 to 192.549, 659A.303 and 746.135 and the provisions of ORS 659A.300 relating to genetic testing. An individual or the individual's blood relative, representative or estate may bring a civil action against any person who violates ORS 192.535, 192.537, 192.539 or 192.547.

For a violation of ORS 192.535 or 192.539 the court awards the greater of actual damages or an amount from $1,000 for an inadvertent violation to $250,000 for a knowing violation committed with intent to sell, transfer or use for commercial advantage, personal gain or malicious harm.

For a violation of ORS 192.537 or 192.547 the court awards the greater of actual damages or an amount from $100 for an inadvertent violation to $25,000 for a knowing violation committed with intent to sell, transfer or use for commercial advantage, personal gain or malicious harm. Unlawfully obtaining, retaining or disclosing genetic information in violation of ORS 192.531 to 192.549 is a Class A misdemeanor.

The Attorney General or a district attorney may bring an action against a person who violates ORS 192.535, 192.537, 192.539 or 192.547, and the court awards the costs of the investigation.

What it requires

Oregon insurer limits on genetic tests and genetic information

ORS 746.135Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force. Binds public and private bodies.

What this law does

If a person asks an applicant for insurance to take a genetic test in connection with an application, the use of the test must be revealed to the applicant and the person must obtain the applicant's specific authorization on a form the Director of the Department of Consumer and Business Services adopts by rule. A person may not use favorable genetic information to induce the purchase of insurance.

A person may not use genetic information to reject, deny, limit, cancel, refuse to renew, increase the rates of, affect the terms and conditions of or otherwise affect any policy for hospital or medical expenses. A person may not use genetic information about a blood relative to reject, deny, limit, cancel, refuse to renew, increase the rates of, affect the terms and conditions of or otherwise affect any policy of insurance.

The history note of ORS 746.135 lists section 8 of chapter 680, Oregon Laws 1995, and section 17 of chapter 588, Oregon Laws 2001. ORS chapters 731, 732, 733, 734, 735, 737, 742, 743, 743A, 743B, 744, 746, 748 and 750 may be cited as the Insurance Code. A person that violates any provision of the Insurance Code is subject to a civil penalty the Director of the Department of Consumer and Business Services determines that does not exceed $10,000 for each offense.

The civil penalty for individual insurance producers, adjusters or insurance consultants may not exceed $1,000 for each offense, and each violation is a separate offense. A violation of any provision of the Insurance Code for which no greater penalty is provided is a Class A misdemeanor. No record stating the day on which the section came into force has been located.

What it requires

Oregon prohibition on printing, displaying or posting Social Security numbers

ORS 646A.620(1)(a) to (c)Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force since . Binds public and private bodies.

What this law does

ORS 646A.620(1) bars a person, except as otherwise specifically provided by law, from printing a consumer's Social Security number on unrequested mail or on documentation of a requested transaction or service unless it is redacted, from printing it on a card required to access products or services, and from publicly posting or displaying it unless it is redacted.

ORS 646A.620 does not prevent the collection, use or release of a Social Security number as required by state or federal law or court rule, or its use or printing for internal verification or administrative purposes or to enforce a judgment or court order. The history note of ORS 646A.620 lists section 11 of chapter 759, Oregon Laws 2007, and section 1 of chapter 254, Oregon Laws 2017.

Chapter 254, Oregon Laws 2017 (Senate Bill 769), relates to disposing of material that displays Social Security numbers and amends ORS 646A.620. A person who violates or who procures, aids or abets in the violation of ORS 646A.600 to 646A.628 is subject to a penalty of not more than $1,000 for every violation, and the maximum penalty for any occurrence does not exceed $500,000.

If the Director of the Department of Consumer and Business Services has reason to believe that a person is violating ORS 646A.600 to 646A.628, the director may issue a cease and desist order or require the person to pay compensation to injured consumers. ORS 646.607 lists a violation of a provision of ORS 646A.600 to 646A.628 among the unlawful trade practices.

A prosecuting attorney who has probable cause to believe that a person is engaging in an unlawful trade practice may bring suit in the name of the State of Oregon to restrain the practice. A court that finds a person willfully used a practice declared unlawful by ORS 646.607 may, on the prosecuting attorney's petition, set a civil penalty not exceeding $25,000 per violation.

What it requires

Oregon protected health information statutes: authorization, use and disclosure by health care providers and state health plans

ORS 192.553 to 192.581Official Oregon Revised Statutes text, Oregon State Legislature (oregonlegislature.gov)

In force. Binds public and private bodies.

What this law does

ORS 192.553 states the policy of the State of Oregon that an individual has the right to have protected health information safeguarded from unlawful use or disclosure and the right to access and review it. A covered entity is a state health plan, a health insurer, a health care provider that transmits health information in electronic form in connection with a transaction covered by ORS 192.553 to 192.581, or a health care clearinghouse.

Protected health information is individually identifiable health information that is maintained or transmitted in any form of electronic or other medium by a covered entity. Protected health information does not include individually identifiable health information in education records covered by the federal Family Educational Rights and Privacy Act or in employment records held by a covered entity in its role as employer.

A health care provider or state health plan may use or disclose protected health information consistent with an authorization, and without one for its own treatment, payment or health care operations or as otherwise permitted or required by state or federal law or by order of the court.

An authorization is a document written in plain language that contains the description of the information, the persons authorized to disclose and receive it, each purpose, an expiration date or event, the signature and date, the authority of any personal representative, and statements on revocation, conditioning of treatment and redisclosure.

A health care provider or state health plan that receives an authorization to disclose protected health information may charge no more than $30 for copying 10 or fewer pages, no more than 50 cents per page for pages 11 through 50 and no more than 25 cents for each additional page. Any disclosure of protected health information under ORS 192.567 must be limited to the minimum necessary to accomplish the purpose of the disclosure.

A covered entity must, on request of an individual appealing the denial of Social Security disability benefits, provide one copy of the individual's health information free of charge. A health care provider that participates in a coordinated care organization must disclose protected health information to the other participating providers for treatment and to the organization for health care operations and payment.

Nothing in ORS 192.556 or 192.558 may be construed to create a new private right of action against a health care provider or a state health plan. A health care facility, meaning a hospital or a federally qualified health center, may not disclose for the purpose of law enforcement information concerning a person's citizenship or immigration status or country of birth unless state or federal law or a court order requires the disclosure. That bar took effect on . The sections this entry groups came into force on different days.

What it requires

Scraping law2 instruments, 2 in force

Research summary (1,306 words)

Oregon's computer-crime statute, ORS 164.377, makes it a Class A misdemeanor to knowingly and without authorization use, access or attempt to access a computer, computer system or computer network, or the software, programs, documentation or data in one (subsections (4) and (5)(a)).

Its definitions say what access is (to instruct, communicate with, store data in, retrieve data from or otherwise make use of any resource of a computer, computer system or computer network) and never define authorization, and subsection (4) carries no security-measure, purpose or harm element.

Two neighboring offenses are felonies: subsection (2) punishes knowingly accessing or using a computer for the purpose of defrauding, obtaining money, property or services by false pretenses, or committing theft, and subsection (3) punishes knowingly altering, damaging or destroying a computer or its data without authorization.

The Oregon Supreme Court construed "without authorization" in State v. Nascimento, 360 Or 28, 379 P3d 484 (2016). A store clerk who was trained and permitted to run a lottery terminal used it to print tickets for herself without paying, and the state argued that any use for a purpose the owner's policies forbid is without authorization. The court rejected that reading.

Authorization is permission given by or as if by some recognized or proper authority, the text divides those who are authorized to use a computer from those who are not, and a person who is authorized to use a computer does not act without authorization by using it for a purpose the owner's personnel or computer-use policies prohibit; that use may draw private discipline or proceedings under other provisions, but it does not violate subsection (4).

The court added that authorization may be restricted by a password or other authentication or security procedures, that an owner may restrict the scope of access it authorizes, and that the 1985 legislative history aimed the provision at hackers and others with no authority to use the computer.

The reasoning rests on a text that divides authorized from unauthorized users and does not look to the purpose of the use, so it is not confined to employers, but the case involved an employee and no Oregon decision applies it to a visitor bound by website terms.

The Court of Appeals had earlier said, in rejecting a vagueness challenge to subsection (3) on facts of password cracking and installing programs that opened a company's computers to outside access, that doing something to a computer against the owner's policy without asking for an exception is without authorization (State v. Schwartz, 173 Or App 301, 21 P3d 1128 (2001)).

Subsection (4) punishes only a person who acts knowingly. ORS 161.085(8) defines knowingly, for a circumstance described by an offense, as acting with an awareness that the circumstance exists, and ORS 161.115(1) applies a prescribed mental state to each material element that necessarily requires one, so the mental state reaches the circumstance that the access is without authorization.

A crawler that reads a page open to everyone, with no login and no notice that the owner withholds permission, lacks that awareness, and subsection (2) reaches a person only when the purpose is to defraud, to obtain money, property or services by false pretenses, or to commit theft.

No Oregon statute or decision says whether an operator that serves a page to anyone has thereby given the permission the Supreme Court describes, so whether an open page is outside the statute altogether is open, and a notice that permission is withheld can supply the awareness.

The legislative history the court quoted has a district attorney testifying in 1985 that a caller to a bulletin board sees the menu, which is not what the bill addressed, and that it addressed a computer system the caller is not authorized to dial, but that testimony is not a holding on open web pages.

No Oregon statute or decision says whether a robots.txt directive, or a cease-and-desist letter to a person who can still reach the page, supplies the awareness, and the statute has no notice or revocation clause. Getting past a CAPTCHA, IP block or rate limit is different: subsection (4) needs only knowing access without authorization, and a barrier is the operator refusing permission, so a person who defeats one knows the access is unauthorized.

Oregon has no statute or reported decision written for scraping terms. Its Uniform Electronic Transactions Act provides that a contract may be formed between an electronic agent and an individual through an interaction in which the individual performs actions the individual is free to refuse and knows or has reason to know will cause the agent to complete the transaction or performance (ORS 84.040(2)).

A contract can therefore form when a crawler's operator clicks to accept, and a visitor who only browses is bound only where the visitor knew or had reason to know that browsing would complete the transaction, so notice is the question; the terms themselves are determined by Oregon's substantive contract law (ORS 84.040(3)).

Oregon's Unlawful Trade Practices Act, ORS 646.605 et seq., governs unfair and deceptive trade practices, and no reported Oregon decision applies it or a misappropriation doctrine to scraping.

Oregon recognizes trespass to chattels. Its courts call the tort the little brother of conversion and treat its elements as conversion's, differing in the extent of the interference and the remedy (Scott v. Jackson County, 244 Or App 484 (2011)); its gist is the disturbance of the plaintiff's possession, and a temporary disturbance for which only emotional damage is claimed is not actionable (Morrow v. First Interstate Bank of Oregon, 118 Or App 164 (1993)).

The Supreme Court upheld punitive damages for trespass to chattels where protesters chained themselves to a logging company's equipment and rendered it inoperable (Huffman and Wright Logging Co. v. Wade, 317 Or 445 (1993)). No Oregon decision applies the tort to server load or crawling or adopts the Restatement's impairment test, so a claim over crawling rests on an actual disturbance of the operator's possession, which no decision has measured against server load.

The Oregon Consumer Privacy Act, ORS 646A.570 to 646A.589, treats a consumer's precise location, accurate within a radius of 1,750 feet, and genetic or biometric data as sensitive data, and a controller may not process sensitive data without first obtaining the consumer's consent.

Its exclusion for public information is narrower than a blanket one: personal data does not include data lawfully available through government records or widely distributed media, or that a controller reasonably has understood to have been lawfully made available to the public by the consumer.

House Bill 2008 (Oregon Laws 2025, chapter 251) amended ORS 646A.578(2) to bar a controller from selling personal data that accurately identifies, within a radius of 1,750 feet, a consumer's present or past location, and the text carries no consent exception; it also bars selling the personal data of a consumer the controller knows, or willfully disregards, is under 16.

The public-information exclusion reaches only those two showings, so scraped sensitive data that meets neither stays inside the Act, which the privacy topic covers.

Copyright and text-and-data-mining are governed by federal law alone, including the unsettled question whether commercial mining is fair use, and Oregon adds no mining exception, opt-out or database right. No Oregon statute governs AI training data as its subject: the state's artificial intelligence enactments address election deepfakes, intimate images, nursing titles and companion chatbots, and the companion-chatbot act mentions training data only in a bar on misrepresenting it.

The Oregon Department of Justice's December 2024 guidance, which is not binding, reads the Oregon Consumer Privacy Act to require a developer that uses personal data to train AI systems to disclose this in its privacy notice, and to obtain consent before using sensitive data to develop or train a model. No Oregon statute or reported decision gives robots.txt legal weight of its own.

Computer misuse

Oregon Computer Crime, without-authorization access and alteration

Or. Rev. Stat. § 164.377official text, Oregon State Legislature (oregonlegislature.gov)

In force. Binds public and private bodies.

What this law does

Subsection (4) makes it a Class A misdemeanor to knowingly and without authorization use, access or attempt to access any computer, computer system, computer network, or any computer software, program, documentation or data contained in one.

Subsection (3) makes it a Class C felony to knowingly and without authorization alter, damage or destroy a computer, computer system, computer network, or its software, program, documentation or data, and subsection (2) makes it a Class C felony to knowingly access, attempt to access or use a computer, computer system or computer network for the purpose of devising or executing a scheme to defraud, obtaining money, property or services by false or fraudulent pretenses, representations or promises, or committing theft, including theft of proprietary information or of an intimate image.

Subsection (1) defines to access as to instruct, communicate with, store data in, retrieve data from or otherwise make use of any resources of a computer, computer system or computer network, and it does not define authorization.

Any violation of the section relating to a computer, network, program, software, system or data owned or operated by the Oregon State Lottery, or by another person or entity under contract to or at the direction of the Oregon State Lottery Commission, is a Class C felony.

What it requires

Personal data

Oregon Consumer Privacy Act (OCPA), sensitive-data consent and geolocation

Or. Rev. Stat. §§ 646A.570 to 646A.589official text, Oregon State Legislature (oregonlegislature.gov)

In force since . Binds private bodies.

What this law does

OCPA applies to a person conducting business in Oregon, or providing products or services to Oregon residents, that during a calendar year controls or processes the personal data of 100,000 or more consumers, other than data processed solely to complete a payment transaction, or of 25,000 or more consumers while deriving 25 percent or more of gross revenue from selling personal data, with no separate dollar-revenue threshold of its own.

Sensitive data is defined to include a consumer's precise present or past location, accurate within a 1,750-foot radius, and genetic or biometric data, and a controller may not process sensitive data about a consumer without first obtaining the consumer's consent.

OCPA's own 'personal data' definition does carry a publicly-available-information exemption, and 'sensitive data' is itself defined as a subset of personal data, so the same exemption applies upstream to it: personal data does not include data that is lawfully available through federal, state, or local government records or through widely distributed media, or that a controller reasonably has understood to have been lawfully made available to the public by the consumer (ORS 646A.570(13)(b)).

This is narrower than a blanket public-availability exemption, since it does not cover data merely observable online that a scraper, rather than the consumer or a distributed-media outlet, is the one making public; scraped sensitive or personal data of unclear provenance should still be treated as covered unless one of those two specific showings applies.

Oregon amended OCPA in 2025 (HB 2008, Oregon Laws 2025, chapter 251, ORS 646A.578(2)(d)) to bar a controller from selling personal data that accurately identifies, within a radius of 1,750 feet, a consumer's present or past location, and the text carries no consent exception; it also bars selling the personal data of a consumer the controller knows, or willfully disregards, is under 16.

Enforcement is by the Attorney General only, with a civil penalty of up to $7,500 per violation; before bringing an action the Attorney General must give a controller 30 days to cure a violation that can be cured, a duty that Oregon Laws 2025, chapter 417, section 5, applies to every controller until and after that only to certain noncommercial educational broadcast stations, and that section 6 repeals on . OCPA carries no private right of action.

What it requires

Cybersecurity law5 instruments, 5 in force

Research summary (590 words)

Oregon binds a private-sector manufacturer of an Internet-connected consumer device to a market-entry security duty at ORS 646A.813 (2019 c.193, House Bill 2395-A), which requires a manufacturer that sells or offers to sell a connected device, a physical object connected directly or indirectly to the Internet and used primarily for personal, family or household purposes, in the state to equip it with reasonable security features: a unique preprogrammed authentication credential or a requirement that the user set new credentials before first use, or compliance with an applicable federal security requirement.

The section reaches only the manufacturer of the physical device itself, expressly disclaiming any duty over software, firmware or peripheral devices that another manufacturer makes and a consumer later adds, so it does not by itself reach a developer who ships only an app or other software with no connected device of its own, and it exempts a device already regulated under Health Insurance Portability and Accountability Act (HIPAA) or under the Food and Drug Administration's medical-device rules.

A violation is declared an unlawful trade practice under ORS 646.607, enforceable by the Attorney General or a district attorney by injunction under ORS 646.632 and by a civil penalty of up to $25,000 per willful violation under ORS 646.642(3); Oregon's general private right of action for unlawful trade practices, ORS 646.638, reaches only a practice declared unlawful under the separate ORS 646.608, so the connected-device duty carries no private remedy of its own.

Separately, the Oregon Consumer Information Protection Act's safeguards provision, ORS 646A.622 (originally 2007 c.759, most recently amended 2019 c.180), requires a covered entity, a person who owns, licenses, maintains, stores, manages, collects, processes, acquires or otherwise possesses an Oregon consumer's personal information in the course of business, vocation, occupation or volunteer activity, including a public body, and a vendor that holds that information on a covered entity's behalf, to develop, implement and maintain reasonable administrative, technical and physical safeguards; a covered entity or vendor complies either by already being regulated under Gramm-Leach-Bliley Act Title V, HIPAA and HITECH, or another law providing greater protection, or by running an information security program with the administrative, technical and physical elements the statute lists, and a small business may scale its program to its own size and the sensitivity of the information it holds.

The Director of the Department of Consumer and Business Services enforces the safeguards duty by investigation, subpoena and a cease-and-desist or consumer-compensation order, with a civil penalty of up to $1,000 per violation capped at $500,000 for any one occurrence; the sections name no private right of action of their own.

No Oregon statute requiring a private business to report an exploited vulnerability or a security incident to an authority, a computer security incident response team (CSIRT) or users was located in the sources checked; a state agency's notice to the Legislative Fiscal Office under ORS 276A.306 is filed as a row of its own with no activity flag.

Oregon's insurer safeguards rules, OAR 836-081-0101 to 836-081-0126, require an insurance licensee to keep an information security program, and the state agency security duties of ORS 276A.323 are filed as a row of their own. Oregon's breach-of-security notice duty, ORS 646A.604, is part of the same Oregon Consumer Information Protection Act as the safeguards provision above but is already this jurisdiction's privacy row and is not repeated here.

ORS 276A.306(2) requires each state agency to promptly notify the Legislative Fiscal Office of an information security incident. ORS 276A.323(2) requires all state agencies to conduct and document the completion of annual information technology security awareness training for all agency employees.

Product security requirements

Security requirements for Internet-connected devices

ORS 646A.813 (added by 2019 c.193 (H.B. 2395-A) sec. 1; amending ORS 646.607)Official statute text, Oregon Revised Statutes, ORS chapter 646A

In force since . Binds private bodies.

What this law does

A manufacturer, a person that makes a connected device and sells or offers to sell it in Oregon, must equip the device with reasonable security features: a preprogrammed authentication credential unique to each unit, or a requirement that the user generate new credentials before first use, or compliance with an applicable federal security requirement for connected devices.

A connected device is limited, under the section's own definition, to a physical object used primarily for personal, family or household purposes that connects to the Internet or is assigned an address for a short-range wireless connection.

The section expressly imposes no duty on the manufacturer for software, firmware or peripheral devices that another manufacturer makes and a consumer later installs or adds, so it does not by itself reach a developer who ships only software or an app with no connected device of its own. It also exempts a device already regulated as to the relevant activity under Health Insurance Portability and Accountability Act (HIPAA), or already subject to Food and Drug Administration medical-device requirements.

It imposes no verification duty on an app store or marketplace. A violation is declared an unlawful trade practice under ORS 646.607, enforceable only by the Attorney General or a district attorney by injunction and a civil penalty of up to $25,000 per willful violation. Oregon's general private right of action for unlawful trade practices, ORS 646.638, reaches only a practice declared unlawful under the separate ORS 646.608, so a violation of this section carries no private remedy of its own. The enacting 2019 Act, chapter 193, carries its own printed effective date of .

What it requires

Sector security regimes

Insurance licensee safeguards for customer information, information security program rules

OAR 836-081-0101 to 836-081-0126Text of Oregon Administrative Rules chapter 836, division 81, published by the Oregon Secretary of State

In force since . Binds private bodies.

What this law does

Rule 836-081-0101(3) requires each licensee to establish and implement an information security program, including appropriate policies and systems. The rules establish standards for developing and implementing administrative, technical and physical safeguards to protect the security, confidentiality and integrity of customer information, pursuant to Sections 501, 505(b), and 507 of the Gramm-Leach-Bliley Act.

The safeguards apply to nonpublic personal information, including financial information and health information.

Rule 836-081-0116 requires a licensee's information security program to be designed to ensure the security and confidentiality of customer information, to protect against any anticipated threats or hazards to the security or integrity of the information, and to protect against unauthorized access to or use of the information that could result in substantial harm or inconvenience to any customer.

Customer information means personal information as defined in ORS 746.600 about a customer, whether in paper, electronic or other form, that is maintained by or on behalf of the licensee. A licensee is a licensee as defined in ORS 746.600, except that the term does not include a purchasing group or an unauthorized insurer in regard to surplus lines business conducted pursuant to ORS 735.400 to 735.495.

The rules are adopted by the Director of the Department of Consumer and Business Services under the authority of ORS 731.244 to implement ORS 746.240 and ORS 746.670, and do not name ORS 646A.622 as a statute they implement. ORS 646A.622(2)(b) treats a covered entity or vendor as complying with the safeguards duty in ORS 646A.622(1) if it complies with regulations promulgated under Title V of the Gramm-Leach-Bliley Act, where its personal information is also subject to that Act.

ORS 646A.622(2)(a) likewise treats a covered entity or vendor as complying if it complies with a state or federal law that provides greater protection to personal information than the section provides. Rule 836-081-0116 took effect on .

What it requires

State agencies, cooperation with the state information security program, training and metrics

ORS 276A.323(2)Text of ORS 276A.323 in Oregon Revised Statutes chapter 276A, published by the Oregon Legislative Counsel

In force since . Binds government bodies.

What this law does

All state agencies must cooperate with the office of Enterprise Information Services in the implementation of a continuing statewide agency-by-agency risk-based information technology security assessment and remediation program. All state agencies must cooperate in the development of, and follow, the plans, rules, policies and standards adopted by the State Chief Information Officer with regard to the unification of agency information technology security functions in the state.

All state agencies must conduct and document the completion of annual information technology security awareness training for all agency employees. All state agencies must report security metrics using methodologies developed by the office of Enterprise Information Services. All state agencies must participate in activities the office of Enterprise Information Services coordinates to better understand and address security incidents and critical cybersecurity threats to the state.

A state agency in this section is an agency, as defined in ORS 183.310, in the executive department, and the executive department excludes the Secretary of State, the State Treasurer, the Attorney General, the Oregon State Lottery and the public universities listed in ORS 352.002.

What it requires

Security baseline statutes

Oregon Consumer Information Protection Act, requirement to develop safeguards for personal information

ORS 646A.622 (2007 c.759 sec. 12; amended 2015 c.357 sec. 3; 2018 c.10 sec. 6; 2019 c.180 sec. 4)Official statute text, Oregon Revised Statutes, ORS chapter 646A

In force since . Binds public and private bodies.

What this law does

A covered entity and a vendor must develop, implement and maintain reasonable administrative, technical and physical safeguards to protect the security, confidentiality and integrity of personal information, including safeguards for its disposal.

A covered entity is any person, defined to include a public body, that owns, licenses, maintains, stores, manages, collects, processes, acquires or otherwise possesses personal information in the course of the person's business, vocation, occupation or volunteer activities. A vendor is a person a covered entity contracts with to maintain, store, manage, process or otherwise access personal information on the covered entity's behalf.

A covered entity or vendor complies either by already being subject to and complying with Gramm-Leach-Bliley Act Title V regulations, Health Insurance Portability and Accountability Act (HIPAA) and HITECH regulations, or another state or federal law providing greater protection, or by implementing an information security program with the administrative safeguards (a designated coordinator, periodic risk assessment, employee training, vetted service-provider contracts), technical safeguards (network and software risk assessment, security patch management, attack detection and testing) and physical safeguards (collection and disposal risk assessment, intrusion monitoring, and secure destruction of records) the statute lists.

A small business may instead scale its program to its own size, complexity and the sensitivity of the personal information it collects. The Director of the Department of Consumer and Business Services enforces the duty by investigation, subpoena, and a cease-and-desist order or, only where enforcement by private civil action would be impractical, an order that the violator compensate injured consumers, with a civil penalty of up to $1,000 per violation and up to $500,000 for any one occurrence.

The sections name no private right of action of their own. The safeguards duty was enacted as section 12 of the 2007 Act, chapter 759, whose own text set that section operative on ; it has since been amended three times, most recently in 2019.

What it requires

Vulnerability and incident reporting

State agencies, notice to the Legislative Fiscal Office of an information security incident

ORS 276A.306(2) and (3)Text of ORS 276A.306 in Oregon Revised Statutes chapter 276A, published by the Oregon Legislative Counsel

In force since . Binds government bodies.

What this law does

A state agency must promptly notify the Legislative Fiscal Office of an information security incident and describe the actions the agency has taken or must reasonably take to prevent, mitigate or recover from damage to, unauthorized access to, unauthorized modifications or deletions of or other impairments of the integrity of its information system or information resources.

An information security incident is an incident that creates a risk of harm to a state agency or its operations and in which sensitive, protected or confidential information is accessed or used without the agency's authorization, a failure of compliance with its security or acceptable use policies results in unauthorized access, or its information system or information resources, or a third party information service to which it subscribes, become unavailable in a reliable and timely manner to authorized individuals or organizations, or are modified or deleted in circumstances the agency does not intend, plan or initiate.

Each state agency must periodically conduct or contract for an information security assessment of its information system and information resources and must notify the Legislative Fiscal Office of the assessment after it receives the results.

A state agency is an officer, board, commission, department, agency or institute of state government as defined in ORS 174.111, other than the public universities listed in ORS 352.002 and the Oregon State Lottery and the entities with which the Lottery has a contract or agreement with respect to its gaming systems or networks.

The Legislative Fiscal Office may use the notifications it receives solely to support the Joint Legislative Committee on Information Management and Technology, the Joint Committee on Ways and Means and the Joint Legislative Audit Committee.

What it requires

Communications law7 instruments, 7 in force

Research summary (405 words)

Oregon requires the consent of at least one participant before a person who is not a participant may obtain the contents of a telecommunication or radio communication, but a device may not obtain any part of an in-person or video-conferencing conversation unless every participant is specifically informed, with exceptions for a felony endangering life, an open recording of an on-duty officer, public or semipublic meetings and classes recorded openly, and private meetings where all others knew or should have known of the recording; a violation is a Class A misdemeanor, and the civil damages action at ORS 133.739 is written for violations of the court-order interception and law-enforcement disclosure sections.

A telephonic seller making certain pitches (a business opportunity, free gifts or prizes, precious metals or stones, or an oil, gas or mineral interest) must register with the Department of Justice and make point-of-sale disclosures; a separate statute, amended effective , bars calling or texting a person again after they ask not to be contacted, limits solicitation calls and texts to 8 a.m. to 8 p.m. and three in 24 hours unless the caller has an established business relationship, and bars misrepresenting the caller's identity or purpose; a third bars telephone solicitation of a number on the do-not-call registry.

Those three, the automatic dialing device statute's misrepresentation and caller-ID rules, and the fax opt-out rule are unlawful trade practices, which lets a person who suffers an ascertainable loss from a willful violation sue for actual damages or $200, whichever is greater; the dialing device's usage limits (an opt-out tone, excluded numbers, calling hours and a frequency cap) are enforced by the Attorney General with a civil penalty of up to $5,000 a violation.

Oregon's pen register and trap and trace statute binds any person, with exceptions for a provider's own service and for court orders. Oregon's Consumer Privacy Act gives a consumer the right to opt out of a controller's processing of personal data for targeted advertising, sale or profiling, a privacy-law right covered with the state's privacy law.

ORS 163.715 makes it a Class A misdemeanor to knowingly affix a global positioning system device to a motor vehicle without the consent of the owner of the motor vehicle. The offense does not apply to a police officer who affixes the device under a warrant or court order, or to a person who affixes it to a vehicle operated by a motor carrier.

Commercial messages

Oregon Unsolicited Facsimile Machine Transmissions Statute

ORS 646A.360Official statute text, Oregon Revised Statutes, Other Mailings or Deliveries chapter

In force. Binds public and private bodies.

What this law does

If a person receives unsolicited and unwanted advertising material for the sale of real estate, goods or services on a facsimile machine, that person may give the sender written notice to stop, and once given, the sender may not fax unsolicited advertising material to that person for one calendar year.

A violation is an unlawful trade practice, letting a person who suffers an ascertainable loss from a willful violation sue under ORS 646.638 for actual damages or $200, whichever is greater, plus attorney fees, in addition to the Attorney General's own enforcement powers. The codified text names no enacting act, and no day on which the section came into force has been located.

What it requires

Device storage and tracking consent

Oregon Pen Register and Trap and Trace Device Statute

ORS 165.657-165.673Official statute text, Oregon Revised Statutes, Interception of Wire, Electronic or Oral Communication chapter

In force. Binds public and private bodies.

What this law does

No person may install or use a pen register or trap and trace device except as the listed court-order and interception statutes and ORS 165.657 to 165.673 allow.

A pen register is a device that records or decodes impulses identifying the numbers dialed or otherwise transmitted on the telephone line it is attached to, but not a device a provider, or a customer of a provider, uses for billing or recording incident to billing, or for cost accounting or similar purposes in the ordinary course of its business. A trap and trace device is a device that captures the originating number of an incoming communication.

A provider of wire or electronic communication service may use such a device in operating, maintaining, testing or protecting its service, its rights or property or its users, to record that a communication was initiated or completed to protect against fraudulent, unlawful or abusive use, or where the consent of the user of that service has been obtained; all three are provider exceptions.

The sections state no penalty, and ORS 161.555(3) provides that an offense defined by statute without a stated classification or penalty is a Class A misdemeanor. The general misdemeanor sentencing statutes cap a Class A misdemeanor at 364 days' imprisonment. They separately cap its fine at $6,250. The sections name no private civil action, and ORS 165.669(4) bars an action against a provider that assists under a court order. No day on which these sections came into force has been located.

What it requires

Interception and recording consent

Oregon Obtaining and Interception of Communications Statute

ORS 165.535, 165.540, 165.543, 165.545Official statute text, Oregon Revised Statutes, Crimes Involving Communications

In force. Binds public and private bodies.

What this law does

Oregon bars a person from obtaining or attempting to obtain the whole or part of a telecommunication or radio communication to which the person is not a participant unless at least one participant has consented, so a participant to a phone call may record it under this clause without telling the other participants, while a stranger to the call needs only one participant's consent.

A separate clause bars obtaining any part of a conversation unless all participants are specifically informed that their conversation is being obtained, a duty that binds a participant to an in-person or video-conferencing conversation as much as a stranger to it. A conversation for this purpose is an oral communication that is not a telecommunication or radio communication, and it includes a communication occurring through a video conferencing program.

One exception to the conversation rule reaches a person recording during a felony that endangers human life. Another reaches a public or semipublic meeting such as a hearing, trial, press conference or class if recorded with an unconcealed device or through a video conferencing program. A third reaches a private meeting or conference if all others involved knew or reasonably should have known that the recording was being made.

Separate exceptions cover an open recording of an on-duty law enforcement officer made from a place the recorder may lawfully be, an officer's own body-worn or vehicle camera, and certain custodial interview recordings.

A person who, intending to capture alleged unlawful activity, records a video-conferencing conversation as a participant or with one participant's consent is also exempt from the notice rule if the person is coordinating with law enforcement, an attorney or an enforcement or regulatory body, or reasonably believes the recording may be used as evidence.

Subscribers and their family members recording in their own homes, and a telecommunication or radio company's own employees acting to construct, maintain or operate its service, are also exempt from the participant-consent and specific-notice provisions. It is also barred to obtain a conversation or communication from another person while knowing or having good reason to believe it was first obtained in a prohibited way, or to use or divulge one obtained by prohibited means.

Neither of those two bars reaches a person who took no part in first obtaining the conversation or communication where it concerns a matter of public concern. A related section separately makes it a Class A misdemeanor for a person who is not a party to a wire or oral communication to willfully intercept it, or procure its interception, where none of the parties has consented. A willful violation of these sections is a Class A misdemeanor.

The general misdemeanor sentencing statutes cap a Class A misdemeanor at 364 days' imprisonment. They separately cap its fine at $6,250. The civil damages action at ORS 133.739 reaches a communication intercepted, disclosed or used in violation of ORS 133.724 or 133.737, the court-order interception and law-enforcement disclosure sections. ORS 133.739(3) nonetheless preserves whatever other private civil remedy for invasion of privacy the common law otherwise gives. The sections this entry groups came into force on different days.

What it requires

Telephone contact

Oregon Automatic Dialing and Announcing Device Statute (as amended by 2025 Or. Laws ch. 580, effective January 1, 2026)

ORS 646A.370-646A.376Official statute text

In force since . Binds public and private bodies.

What this law does

House Bill 3865 (Oregon Laws 2025, chapter 580) amended this statute, effective .

As amended, a caller may not use an automatic dialing and announcing device, a device that selects and dials numbers and disseminates a prerecorded or synthesized voice or text message, to call a subscriber by telephone unless the device disconnects within 10 seconds after the subscriber ends the call and, within the first 10 seconds, offers a one-touch or one-digit method for the subscriber to opt out of future calls; the opt-out duty does not reach a collection agency, debt buyer or debt collector, a public safety or law enforcement representative, or a caller with an established business relationship with the subscriber.

The device may not dial a number for a fire, law enforcement or other emergency agency, a hospital, health care facility, physician's office, poison control center, or suicide-prevention or domestic-violence counseling service, or a subscriber who used the opt-out (unless the caller is a collection agency, debt buyer or debt collector, a public safety or law enforcement representative, or has an established business relationship), and, when dialing randomly or sequentially, a subscriber on an official government do-not-call list (unless the caller has an established business relationship, is a debt buyer or subject to the Fair Debt Collection Practices Act, is a public safety or law enforcement representative, or is a school district or school calling its employees, students or their families).

It may be used to call a subscriber only between 8 a.m. and 8 p.m. and no more than three times in 24 hours, with the same exceptions as the government-list rule plus a caller responding directly to the subscriber's own message, and a caller may rely on a mobile number's area code to decide whether the subscriber is in Oregon.

A caller using such a device may not misrepresent or falsify, in speaking with the subscriber, in the prerecorded or synthesized message or in any text message, the caller's own or a represented person's identity, the caller's telephone number, the caller's location, or the purpose of the call.

Separately, a caller, a term that section does not limit to a user of such a device, may not intentionally alter, misrepresent or falsify the information a caller identification service would ordinarily provide.

A person who knowingly, or while consciously avoiding knowledge, provides substantial assistance for a misrepresentation or caller-ID violation, including carrying or facilitating the calls, is liable to the same extent as the caller, except a common carrier or a network operator on whose network the call merely terminates.

A violation of the misrepresentation and caller-ID duties is an unlawful trade practice, letting a person who suffers an ascertainable loss from a willful violation sue under ORS 646.638 for actual damages or $200, whichever is greater, plus attorney fees.

A violation of the usage limits is an unlawful trade practice subject to Attorney General investigation and enforcement with a civil penalty of up to $5,000 for each violation, and ORS 646.608, whose list the private action under ORS 646.638 depends on, names ORS 646A.374 but not ORS 646A.372.

What it requires

Oregon Registration of Telephonic Sellers

ORS 646.551-646.559Official statute text, Oregon Revised Statutes, Telephone Solicitation chapter

In force. Binds private bodies.

What this law does

A telephonic seller is defined narrowly to reach a person who causes a telephone solicitation of a business opportunity, or who solicits by phone while representing that a buyer will receive additional units without further cost or a prize or gift for buying or paying, that an unusual event or price increase justifies a below-market price, that the seller, manufacturer or supplier is other than the real one, or who is selling gold, silver or another precious metal, a precious stone, or an interest in oil, gas or a mineral field, well or exploration site.

Such a seller must register with the Department of Justice at least 10 days before conducting business in Oregon, whether calling from inside or into the state, and pay a $400 annual fee; individual employees need not register separately.

The definition excludes, among others, a securities seller, a person licensed in real estate, construction contracting or insurance acting within that license, a franchise seller governed by Oregon's franchise law, a newspaper, magazine or negative-option subscription seller, a person soliciting prior purchasers of the business it calls for (unless selling a business opportunity), a person who completes the sale only at a later face-to-face meeting, a supervised financial institution or its affiliate, a funeral, cable or regulated-utility seller, an issuer registered under section 12 of the Securities Exchange Act of 1934 or its subsidiary, and a registered charity.

When a telephonic seller represents free items, offers metals, stones or minerals or an oil, gas or mineral interest, or offers office equipment or supplies below usual prices, it must, at the time of the solicitation and before any sale, give the street address it is calling from and its principal address and the further information the section lists for that kind of offer.

A violation of the registration or disclosure duty is an unlawful trade practice, letting a person who suffers an ascertainable loss from a willful violation sue under ORS 646.638 for actual damages or $200, whichever is greater, plus attorney fees, in addition to the Attorney General's own enforcement powers. The sections this entry groups came into force on different days.

What it requires

Oregon Telephone Solicitation Do Not Call List

ORS 646.567-646.578Official statute text, Oregon Revised Statutes, Telephone Solicitation chapter

In force. Binds public and private bodies.

What this law does

A person may not engage in the telephone solicitation of a party at a telephone number on the current list published by the administrator of Oregon's telephone solicitation program or on the federal do-not-call registry designated as part of it.

A telephone solicitation for this purpose is a solicitation by telephone to encourage a party to purchase real estate, goods or services or to make a donation, and excludes a call responding to the called party's request or inquiry, a charitable organization's, public agency's or volunteers' call to members or donors, a call limited to polling or soliciting opinions or votes, and a business-to-business contact.

Unlike ORS 646.561, which chapter 580 of the 2025 Oregon Laws extended to text messages, this definition does not mention text messages. For the registry ban, a telephone solicitation also does not include soliciting a prospective purchaser who has previously purchased from the caller, the business it calls for, or a financial-institution predecessor of that business.

A person who knows or consciously avoids knowing that another is violating the registry ban and nonetheless provides substantial assistance, including carrying or facilitating the calls, is liable to the same extent as the caller, except a common carrier or a network operator on whose network the call merely terminates.

A violation is an unlawful trade practice, letting a person who suffers an ascertainable loss from a willful violation sue under ORS 646.638 for actual damages or $200, whichever is greater, plus attorney fees, in addition to the Attorney General's own enforcement powers. The sections this entry groups came into force on different days.

What it requires

Oregon Unlawful Telephone Solicitations Act (as amended by 2025 Or. Laws ch. 580, effective January 1, 2026)

ORS 646.561, 646.563Official statute text, Oregon Revised Statutes, Unlawful Telephone Solicitations, as amended by House Bill 3865 (2025 Or. Laws ch. 580)

In force since . Binds public and private bodies.

What this law does

House Bill 3865 (Oregon Laws 2025, chapter 580) amended this section, effective . As amended, Oregon bars a person from making a subsequent telephone solicitation, by call or text message, of a party who has stated during a telephone solicitation a desire not to be called or texted again.

It also bars initiating a telephone solicitation outside the hours of 8 a.m. to 8 p.m., or more than three separate times to a party within 24 hours, unless the person has an established business relationship with the party. An established business relationship for this purpose means a transaction within the preceding 18 months. And it bars misrepresenting or falsifying the caller's own identity or the identity of the person on whose behalf the call is made, or the purpose of the solicitation.

A telephone solicitation for this purpose is a call or text message encouraging a party to purchase real estate, goods or services or to make a donation, and it excludes a charitable organization or public agency contacting its own members or donors, a call or text limited to polling or soliciting opinions or votes, a business-to-business contact, and a call or text that responds directly to a message the party sent.

A party is a telephone customer of a telecommunications company, and a person may rely on a mobile number's area code to decide whether the party is in Oregon. A violation is an unlawful trade practice, letting a person who suffers an ascertainable loss from a willful violation sue under ORS 646.638 for actual damages or $200, whichever is greater, plus attorney fees, in addition to the Attorney General's own enforcement powers.

What it requires

Age gating law1 instrument, 1 in force

Research summary (135 words)

Oregon has no adult content age verification law. A bill that would have required age verification for websites where a substantial share of content is sexual material harmful to minors (HB 2032) died when the 2025 session adjourned on , and an app store age verification bill (HB 3696) died in House committee at the same adjournment; the short 2026 session, which adjourned , enacted nothing in the four tracked families.

Oregon has no social media specific minor access law. Its age gating protection instead runs through its comprehensive privacy law: a 2025 amendment to the Oregon Consumer Privacy Act (HB 2008) bars selling the personal data of, serving targeted advertising to, or profiling a consumer the controller knows or willfully disregards is under 16, in effect since .

Age-appropriate design code

HB 2008, Oregon Consumer Privacy Act minors and geolocation amendments

Or. Rev. Stat. section 646A.578 (2025 Or. Laws ch. 251)official Oregon Legislative Information System enrolled bill and session law chapter

In force since . Binds private bodies.

What this law does

Bars a controller that has actual knowledge that, or willfully disregards whether, a consumer is under 16 from selling that consumer's personal data, using it for targeted advertising, or profiling in furtherance of decisions with legal or similarly significant effects, with no consent exception, and separately bars selling personal data that identifies a consumer's location within a 1,750 foot radius. Signed by Governor Kotek on .

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

Oregon has no enacted statute creating a press-publisher neighbouring right or a mandatory platform-to-publisher bargaining code, and no reported Oregon court decision addresses hot-news misappropriation, snippet reproduction, linking or framing, or a text-and-data-mining opt-out; the state's position on all of these rests entirely on the federal baseline covered in the national document.

Oregon Revised Statutes chapter 646A (unlawful trade practices) and chapter 164 (computer crime) were checked and contain no aggregation-specific provision.

As of .

Case law

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

Reporting clocks that run here18 instruments

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

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

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

The law of Oregon

10 days45 days

Notice of breach of security

ORS 646A.604privacy law, in force

The sentences the clocks are read from

Notify each affected Oregon consumer of a breach of security, including one you learn of through a vendor, in the most expeditious manner possible and not later than 45 days after discovering or receiving notification of the breach, and notify the Oregon Attorney General as well once more than 250 Oregon consumers are notified (ORS 646A.604(1), (3)).

If you are a vendor that discovers a breach of security or has reason to believe one has occurred, notify each covered entity you have a contract with as soon as is practicable and not later than 10 days after discovering the breach or having reason to believe it occurred, and if you contract with another vendor that serves a covered entity, notify that vendor the same way (ORS 646A.604(2)).

promptly

State agencies, notice to the Legislative Fiscal Office of an information security incident

ORS 276A.306(2) and (3)security law, in force since

The sentence the clocks are read from

Promptly notify the Legislative Fiscal Office of an information security incident and describe the actions the agency has taken or must reasonably take to prevent, mitigate or recover from damage to, unauthorized access to, unauthorized modifications or deletions of or other impairments of the integrity of the agency's information system or information resources.

The law of the United States, which applies in Oregon

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.

Law in local jurisdictions1 with a page

Each has a page of its own; the number is how many of its instruments are researched to a stage.

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.