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.