Inori
FeaturesToolsPricing
Learn
GuidesStep-by-step tutorials and walkthroughs
GlossaryInsurance and compliance terminology
CompareSee how Inori compares to alternatives
Support
Help CenterFind answers and get support
ChangelogLatest updates and improvements
DemoSee Inori in action
Legal
PrivacyHow we handle your data
TermsTerms of service and usage
Blog
Sign InStart Free

Product

  • Features
  • Pricing
  • Tools
  • Demo

Resources

  • Help Center
  • Guides
  • Glossary
  • Compare

Company

  • About
  • Blog
  • Changelog
  • Contact

Legal

  • Privacy
  • Terms
  • DPA
  • Security

© 2026 Inori Inc.

  1. Home
  2. /Glossary
  3. /Oregon Consumer Privacy Act (OCPA)

Oregon Consumer Privacy Act (OCPA)

Oregon's comprehensive privacy law, notable for covering non-profits, requiring a list of specific third parties in access responses, and banning the sale of precise geolocation data outright as of January 2026.

Overview

The Oregon Consumer Privacy Act (OCPA), codified at Or. Rev. Stat. § 646A.570 et seq. and enacted as SB 619 (2023), became effective July 1, 2024. The OCPA is one of the most protective state privacy laws after California and extends coverage in distinctive ways: it does not exempt non-profits, it requires controllers to disclose specific named third parties in response to access requests (not just categories), it prohibits the sale of precise geolocation data outright (effective January 1, 2026), and it extends coverage to connected-vehicle data regardless of consumer-count thresholds.

Applicability: (a) 100,000+ Oregon consumers processed per year, or (b) 25,000+ consumers AND 25%+ of gross revenue from sale or licensing of personal data.

Exemptions: HIPAA entities, GLBA financial institutions, FCRA/DPPA/FERPA/COPPA-regulated data, employee/B2B. Non-profits ARE covered — an outlier choice.

Consumer Rights

  • Right to confirm and access — including a list of specific third parties the data was shared with (more rigorous than the category-level baseline)
  • Right to correct
  • Right to delete
  • Right to portability (machine-readable)
  • Right to opt out of sale, targeted advertising, and profiling
  • Right to appeal — 45-day response window

Sensitive data includes the standard categories plus transgender status (a protection unique to Oregon) and a broad biometric definition spanning facial geometry, voice patterns, iris/retina scans, and fingerprints. Opt-in consent is required.

Compliance Requirements

Controllers must publish privacy notices, honor GPC/UOOM (mandatory since January 1, 2026), perform DPIAs for high-risk processing, and execute processor contracts per § 646A.574. Connected-vehicle manufacturers and affiliates are covered regardless of consumer-count thresholds for data collected from vehicles owned or leased by Oregon residents — telemetry, location, diagnostics, and driving-behavior data all fall in scope. The prohibition on sale of precise geolocation data (as of January 2026) is a hard prohibition, not an opt-out.

Cure Period + Enforcement

The Oregon AG holds exclusive enforcement authority. Penalties reach $7,500 per violation. The original 30-day cure period expired January 1, 2026 — no automatic safe harbor remains.

How Inori Addresses This

  • Notice: src/content/legal/privacy.mdx v1.2 discloses categories of third parties (Stripe, Anthropic, Firebase); Oregon's named-party requirement is satisfied because the list is already enumerated by specific provider, not just by category.
  • GPC (mandatory): middleware.ts:respectGpc honors Sec-GPC: 1.
  • DSAR: /api/dsar returns the specific list of third parties alongside standard access responses; 30-day SLA.
  • Geolocation: Inori does not collect precise geolocation — the January 2026 sale prohibition is moot for us.
  • Connected vehicles: Out of scope — Inori does not collect vehicle data.
  • Sensitive data including transgender status: Not collected.
  • Deferred: Specific-third-party disclosure UI in the privacy settings page is planned; currently the list is delivered via the DSAR response.

Related Concepts

See CCPA/CPRA, VCDPA, Colorado Privacy Act, and CTDPA for comparative frameworks. GPC covers the mandatory UOOM signal. DSAR handles the unified request pipeline. MCDPA is a similar protective model with a lower consumer threshold.

See how Inori handles oregon consumer privacy act (ocpa)

Try our free COI checker first, or start a free trial of the full platform.

Free COI CheckerStart Free Trial

Related Terms

CCPA / CPRA (California Consumer Privacy Act / California Privacy Rights Act)

California's comprehensive consumer privacy laws giving residents the right to know, delete, correct, and opt out of the sale or sharing of their personal information. CPRA amended and expanded CCPA effective January 1, 2023.

Virginia Consumer Data Protection Act (VCDPA)

Virginia's comprehensive consumer privacy law — the second state law after CCPA — granting residents rights to access, correct, delete, and opt out of data sales. Served as the template for most subsequent state laws.

Colorado Privacy Act (CPA)

Colorado's comprehensive privacy law — the third state after California and Virginia — notable for being the first to formally approve Global Privacy Control as a Universal Opt-Out Mechanism and for pairing with the Colorado AI Act.

GPC (Global Privacy Control)

A browser-level signal (Sec-GPC: 1 HTTP header) that communicates a user's preference to opt out of the sale or sharing of their personal information. Legally recognized as a valid opt-out mechanism under CCPA/CPRA.

DSAR (Data Subject Access Request)

A formal request by an individual to a company to exercise their privacy rights — including accessing, correcting, deleting, or exporting their personal data — as provided by CCPA, CPRA, GDPR, and U.S. state privacy laws.