13 US state privacy law skills: CCPA/CPRA, VCDPA, CPA, CTDPA, TDPSA, multi-state compliance, universal opt-out

version
1.0.0
GitHub stars
340

Install

/plugin install us-state-privacy-skills@privacy-data-protection-skills

Run it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.

Contents

Discovered from source

Skills 13

California Consumer Rights Workflow

Overview

The CCPA/CPRA grants California consumers six categories of privacy rights enforceable against businesses that meet the applicability thresholds under Cal. Civ. Code §1798.140(d). These rights are modeled after but distinct from GDPR data subject rights, with California-specific verification requirements, response timelines, and scope limitations.

The California Privacy Protection Agency (CPPA) regulations (11 CCR §7001-7102) provide detailed implementation requirements for consumer request handling, including verification standards, response formats, and authorized agent procedures.

Consumer Rights Matrix

RightStatuteVerification LevelResponse TimeExtensionFrequency Limit
Right to Know (categories)§1798.1102 data points45 days+45 days2 per 12 months
Right to Know (specific pieces)§1798.1103 data points + declaration45 days+45 days2 per 12 months
Right to Delete§1798.1052 data points45 days+45 daysNo limit stated
Right to Correct§1798.1062 data points45 days+45 daysNo limit stated
Right to Opt-Out of Sale/Sharing§1798.120Reasonable belief15 business daysNoneAnytime
Right to Limit Sensitive PI§1798.121Reasonable belief15 business daysNoneAnytime

Right to Know (§1798.100, §1798.110, §1798.115)

Categories Disclosure

Upon verified request, the business must disclose for the 12-month period preceding the request:

  1. Categories of personal information collected
  2. Categories of sources from which PI was collected
  3. Business or commercial purpose for collecting, selling, or sharing PI
  4. Categories of third parties to whom PI was disclosed
  5. Categories of PI sold and, for each category, the categories of third parties to whom it was sold
  6. Categories of PI disclosed for a business purpose and, for each category, the categories of recipients

Specific Pieces Disclosure

Requires heightened verification (three data points plus a signed declaration under penalty of perjury). The business must provide the specific pieces of PI it has collected about the consumer in a portable, readily usable format (structured, commonly used, machine-readable).

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. provides a Know My Data portal that generates two report formats:

  • PDF report: Human-readable summary with categories, sources, purposes, and recipients listed in plain language
  • JSON export: Machine-readable structured data including all specific pieces of PI, organized by category with collection timestamps

The system enforces the 12-month lookback period automatically. Consumers may request data beyond 12 months, which Liberty Commerce Inc. provides where reasonably feasible per §1798.130(a)(2).

Right to Delete (§1798.105)

Processing Steps

  1. Receive request through designated channels (web portal, email, toll-free number)
  2. Verify identity — match at least two data points (name + email, email + account number, etc.)
  3. Confirm intent — for requests submitted by means other than the designated portal, confirm the consumer's intent to delete
  4. Identify applicable exceptions (§1798.105(d)):
    • Complete the transaction for which the PI was collected
    • Detect security incidents; protect against malicious, deceptive, fraudulent, or illegal activity
    • Debug to identify and repair functionality errors
    • Exercise free speech or ensure another consumer's right to exercise free speech
    • Comply with the California Electronic Communications Privacy Act (Cal. Penal Code §1546)
    • Engage in public or peer-reviewed scientific, historical, or statistical research in the public interest
    • Enable solely internal uses reasonably aligned with consumer expectations based on the consumer's relationship
    • Comply with a legal obligation (e.g., tax record retention per 26 U.S.C. §6001)
    • Otherwise use the PI internally in a lawful manner compatible with the context of collection
  5. Execute deletion — delete PI from active systems and direct service providers and contractors to delete
  6. Handle deferred deletion — for PI in backup/archival systems, mark for deletion at next scheduled maintenance cycle
  7. Notify consumer — confirm deletion or explain partial denial with specific exception cited

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. executes a cascading deletion workflow:

  • Active database records: Deleted within 10 business days
  • Service provider systems (PaySecure Corp., SwiftShip Logistics): Deletion request forwarded with 30-day compliance deadline
  • Backup systems: Marked for deletion at next 90-day rotation
  • Retained data: Tax records (7 years per IRS requirements), fraud investigation records (duration of investigation plus 3 years)

Right to Correct (§1798.106)

Added by CPRA, effective January 1, 2023. Consumers may request that a business correct inaccurate personal information, taking into account the nature of the PI and the purposes of processing.

Business Obligations

The business must use commercially reasonable efforts to correct the PI. If the business contests the correction, it must:

  • Notify the consumer of the decision
  • Provide instructions for the consumer to submit documentation supporting the correction
  • Consider the documentation and correct the PI if warranted
  • If maintaining its decision, allow the consumer to submit a written addendum to the record

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. allows self-service correction for profile fields (name, address, email, phone number). For non-self-service data (transaction records, loyalty tier, inferred preferences), consumers submit correction requests through the privacy portal with supporting documentation. The privacy team reviews within 15 business days and either corrects or responds with reasoning.

Right to Opt-Out of Sale and Sharing (§1798.120)

Two Distinct Operations (Post-CPRA)

  1. Sale (§1798.140(ad)): Disclosure of PI to a third party for monetary or other valuable consideration
  2. Sharing (§1798.140(ah)): Disclosure of PI to a third party for cross-context behavioral advertising, regardless of monetary exchange

Both must be subject to the opt-out right. The business must provide a "Do Not Sell or Share My Personal Information" link on its homepage.

Opt-Out Signal Requirements (CPPA Regulations §7025)

  • Businesses must process opt-out preference signals (including GPC) as valid opt-out requests
  • No identity verification required — the signal itself constitutes a valid request
  • Must apply opt-out within 15 business days of receiving the signal
  • Must not display a pop-up or interstitial asking the consumer to validate the signal
  • Must not require the consumer to provide additional information to process the signal
  • If the consumer is not identifiable, apply the opt-out to the browser/device

Minor-Specific Requirements (§1798.120(c))

  • Children under 13: Business must not sell or share PI without affirmative authorization from parent or guardian
  • Children 13-15: Business must not sell or share PI without the child's affirmative authorization (opt-in)
  • No re-solicitation for at least 12 months after a minor's parent/guardian or the minor themselves opts out

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. processes opt-out requests through three channels:

  1. Homepage link: "Do Not Sell or Share My Personal Information" in page footer
  2. GPC signal: Automatic detection and honoring of Sec-GPC: 1 header
  3. Privacy portal: Authenticated opt-out with account-level persistence

Upon opt-out, the system:

  • Suppresses third-party advertising pixels (AdReach Network, TargetAds)
  • Disables cross-context behavioral advertising data transmission
  • Maintains first-party analytics (not a sale/sharing when processed under service provider agreement)
  • Updates consent management platform state within 15 minutes

Right to Limit Use of Sensitive PI (§1798.121)

Permitted Uses After Limitation

When a consumer exercises this right, the business may only use or disclose sensitive PI for:

  1. Performing services or providing goods reasonably expected by the consumer
  2. Preventing, detecting, and investigating security incidents
  3. Resisting malicious, deceptive, fraudulent, or illegal actions
  4. Ensuring the physical safety of natural persons
  5. Short-term, transient use (including non-personalized advertising)
  6. Performing services on behalf of the business (verification, maintenance, customer service)
  7. Verifying or maintaining the quality or safety of a service or device
  8. Upgrading, enhancing, or improving services

Liberty Commerce Inc. Sensitive PI Categories Processed:

  • Precise geolocation (store finder, delivery tracking)
  • Payment card details (transaction processing)
  • Racial/ethnic origin (optional diversity survey — discontinued upon any limitation request)
  • Account credentials (authentication)

Identity Verification Framework (CPPA Regulations §7060-7062)

Verification Methods

MethodData PointsApplicable To
Knowledge-basedAccount email + last 4 SSNKnow, Delete, Correct
Account verificationAuthenticated sessionKnow, Delete, Correct
Document-basedGovernment ID scanKnow (specific), high-value requests
DeclarationSigned under penalty of perjuryKnow (specific pieces) — required
Agent authorizationSigned permission or POAAll rights via authorized agent

Authorized Agent Handling (§1798.130(a)(1), CPPA Regs §7063)

When a request is submitted by an authorized agent:

  1. Verify the agent's authorization: signed written permission from the consumer or valid power of attorney under Cal. Prob. Code §§4000-4465
  2. If signed written permission (not POA): may also verify the consumer's identity directly
  3. If POA: no additional consumer verification required
  4. Deny request if authorization cannot be verified

Response Delivery Standards

Format Requirements

  • Categories disclosure: May be in any readily understandable format
  • Specific pieces: Must be in a portable, readily usable format that allows the consumer to transmit the information to another entity without hindrance (machine-readable: JSON, CSV, or XML)
  • Deletion confirmation: Written confirmation specifying what was deleted and what was retained (with legal basis)
  • Opt-out: Confirmation of opt-out status; must be effective within 15 business days

Delivery Method

  • Deliver via the same channel through which the request was received (or more secure alternative)
  • For specific pieces of PI: use a secure, password-protected delivery mechanism
  • Do not deliver sensitive PI (SSN, financial account numbers) in response to a right-to-know request — confirm existence only

Key Regulatory References

  • Cal. Civ. Code §1798.100-199 (CCPA/CPRA)
  • CPPA Regulations 11 CCR §7001-7102
  • CPPA Regulations §7025 — Opt-out preference signals
  • CPPA Regulations §7060-7063 — Consumer request verification
  • CPPA Enforcement Advisory No. 2024-01 — Dark patterns
  • AG Opinion No. 21-303 — Authorized agent verification standards

CCPA/CPRA Compliance

Overview

The California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), establishes comprehensive consumer privacy rights under California Civil Code §1798.100-199. The CPRA, approved by voters on November 3, 2020 (Proposition 24), substantially amended the CCPA effective January 1, 2023, with a lookback period to January 1, 2022. The California Privacy Protection Agency (CPPA) was established as the first dedicated state privacy enforcement agency in the United States.

The CPRA replaced the California Attorney General as the primary enforcement body with the CPPA, added the category of sensitive personal information, created new consumer rights (correction and limit use of sensitive PI), expanded the definition of "sharing" for cross-context behavioral advertising, and introduced requirements for data processing agreements.

Applicability (§1798.140(d))

A business is subject to CCPA/CPRA if it:

  1. Has annual gross revenues exceeding $25,000,000 in the preceding calendar year (adjusted by the CPPA for inflation starting January 1, 2024)
  2. Annually buys, sells, or shares the personal information of 100,000 or more consumers or households (CPRA increased from 50,000)
  3. Derives 50% or more of its annual revenues from selling or sharing consumers' personal information

Liberty Commerce Inc. Assessment: Liberty Commerce Inc., with annual revenues of $48 million and processing personal information of approximately 320,000 California consumers through its e-commerce platform, meets threshold (1) and threshold (2). Liberty Commerce Inc. is classified as a "business" under §1798.140(d).

Key Definitions

Personal Information (§1798.140(v))

Information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household. Categories include:

CategoryExamples
IdentifiersReal name, alias, postal address, unique personal identifier, online identifier, IP address, email, account name, SSN, driver's license, passport number
Commercial InformationRecords of personal property, products or services purchased, obtaining, or considered
Biometric InformationPhysiological, biological, or behavioral characteristics used to establish individual identity (fingerprint, face, voice, iris, keystroke patterns)
Internet/Network ActivityBrowsing history, search history, information regarding interaction with website, application, or advertisement
Geolocation DataPhysical location or movements
Sensory DataAudio, electronic, visual, thermal, olfactory, or similar information
Professional/EmploymentCurrent or past job-related information
Education InformationNon-publicly available education records per FERPA (20 U.S.C. §1232g)
InferencesProfiles reflecting preferences, characteristics, psychological trends, predispositions, behavior, attitudes, intelligence, abilities, aptitudes
Sensitive PI (CPRA)SSN/driver's license/passport, account log-in with password, precise geolocation, racial/ethnic origin, religious/philosophical beliefs, union membership, contents of mail/email/text, genetic data, biometric data for identification, health information, sex life/sexual orientation data

Sale (§1798.140(ad))

Selling, renting, releasing, disclosing, disseminating, making available, transferring, or otherwise communicating orally, in writing, or by electronic or other means, a consumer's personal information by the business to a third party for monetary or other valuable consideration.

Sharing (§1798.140(ah)) — Added by CPRA

Sharing, renting, releasing, disclosing, disseminating, making available, transferring, or otherwise communicating a consumer's personal information by the business to a third party for cross-context behavioral advertising, whether or not for monetary or other valuable consideration, including situations where no money is exchanged.

Service Provider vs. Contractor (§1798.140(ag), §1798.140(j))

AspectService ProviderContractor
DefinitionProcesses PI on behalf of business per written contractProcesses PI made available by business per written contract
Contract RequirementsWritten agreement prohibiting selling/sharing, limiting use to specified purposesWritten agreement with same prohibitions plus certification of understanding, grant of compliance audit rights
SubcontractingMay engage subcontractors with written contractMay engage subcontractors with written contract and business notification
Compliance AuditsNot expressly required in statuteBusiness has right to audit contractor compliance

Consumer Rights

1. Right to Know (§1798.100, §1798.110, §1798.115)

Consumers may request that a business disclose:

  • Categories of PI collected
  • Categories of sources
  • Business or commercial purpose for collecting, selling, or sharing
  • Categories of third parties to whom PI is disclosed
  • Specific pieces of PI collected about the consumer

Lookback period: 12 months preceding the request (business may voluntarily go beyond).

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. provides a "Know My Data" portal at privacy.libertycommerce.com/know where verified consumers can request all five categories of disclosure. The system generates a structured report in machine-readable format (JSON) and human-readable format (PDF) within 10 business days.

2. Right to Delete (§1798.105)

Consumers may request deletion of personal information collected from them. Upon receiving a verified request, the business must delete the PI and direct service providers and contractors to delete the consumer's PI.

Exceptions (§1798.105(d)): Transaction completion, security, error repair, free speech (Cal. Civ. Code §1798.105(d)(4)), internal uses reasonably aligned with consumer expectations, compliance with legal obligation, internal uses compatible with the context of collection.

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. processes deletion requests through a cascading deletion workflow that propagates to all service providers (payment processor, shipping partner, analytics provider) within 45 calendar days. Retained data for legal compliance (tax records per 26 U.S.C. §6001) is documented with the specific legal basis.

3. Right to Correct (§1798.106) — Added by CPRA

Consumers may request correction of inaccurate personal information. The business must use commercially reasonable efforts to correct the information.

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. allows consumers to self-correct profile data (name, address, email, phone) directly in their account. For data in backend systems (purchase history corrections, loyalty points), verified requests are processed through the privacy team with documentation of the correction.

4. Right to Opt-Out of Sale/Sharing (§1798.120)

Consumers have the right to direct a business that sells or shares their personal information to stop selling or sharing that information. The business must respect this direction.

Key requirements:

  • "Do Not Sell or Share My Personal Information" link on homepage
  • Must honor Global Privacy Control (GPC) signals as valid opt-out requests (CPPA Regulations §7025)
  • No re-solicitation for 12 months after opt-out
  • Must not discriminate against consumers who opt out (§1798.125)

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. displays a persistent "Do Not Sell or Share My Personal Information" link in the footer of every page. The system detects GPC signals via the Sec-GPC: 1 HTTP header and navigator.globalPrivacyControl JavaScript API, automatically applying opt-out status to the browsing session and associating it with the consumer's account if authenticated.

5. Right to Limit Use of Sensitive PI (§1798.121) — Added by CPRA

Consumers may direct a business to limit its use of sensitive personal information to specified purposes (performing services/providing goods, preventing security incidents, resisting malicious/deceptive actions, ensuring safety, short-term transient use, performing services on behalf of the business, verifying/maintaining quality, upgrading/enhancing services).

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. displays a "Limit the Use of My Sensitive Personal Information" link adjacent to the opt-out link. When activated, the system restricts processing of sensitive PI categories (precise geolocation, racial/ethnic origin data from surveys, payment card details beyond transaction processing) to the enumerated permitted purposes.

6. Right to Non-Discrimination (§1798.125)

A business may not discriminate against a consumer for exercising their CCPA rights, including by:

  • Denying goods or services
  • Charging different prices or rates
  • Providing a different level or quality of goods or services
  • Suggesting that the consumer will receive a different price or quality

Financial incentive programs are permitted if the consumer is notified and opts in, the incentive is reasonably related to the value of the consumer's data, and the business can explain the valuation methodology.

Business Obligations

Privacy Notice (§1798.100(a), §1798.130(a)(5))

The privacy notice must be updated at least once every 12 months and include:

  • Categories of PI collected in the preceding 12 months
  • Categories of sensitive PI collected
  • Purposes for which each category is used and whether it is sold or shared
  • Length of time each category is retained (or criteria for determining retention) — added by CPRA
  • Categories of sources
  • Categories of third parties to which PI is disclosed
  • Instructions for submitting consumer requests
  • Whether the business sells or shares PI, and categories involved
  • Categories of PI disclosed for a business purpose

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. publishes its California Privacy Notice at privacy.libertycommerce.com/california, updated annually in January. The notice uses a layered format with a summary table followed by detailed sections. Retention periods are specified per data category (e.g., transaction records: 7 years per tax requirements; browsing data: 13 months; account data: duration of account plus 30 days).

Data Processing Agreements (§1798.100(d)) — Added by CPRA

Businesses must enter into agreements with service providers, contractors, and third parties that:

  • Specify the business purpose for which PI is made available
  • Require the recipient to comply with CCPA/CPRA obligations
  • Grant the business rights to take reasonable steps to ensure compliance
  • Require notification if the recipient determines it can no longer meet its obligations
  • Grant the business the right to stop and remediate unauthorized use of PI

Data Minimization (§1798.100(c)) — Added by CPRA

A business's collection, use, retention, and sharing of PI must be:

  • Reasonably necessary and proportionate to the purposes for which the PI was collected or processed
  • Not further processed in a manner incompatible with those purposes

Consumer Request Processing (§1798.130)

RequirementDetail
Response deadline45 calendar days from receipt of verifiable request
ExtensionUp to 45 additional days (90 total) with notice to consumer
VerificationReasonable methods to verify identity; match at least two data points for access; three data points for specific pieces
Authorized agentsMust accept requests from authorized agents with signed permission or power of attorney
Free requestsAt least two free requests per 12-month period
FormatDelivered in readily usable, machine-readable format (for portability requests)
Toll-free numberRequired for businesses that operate exclusively online only if they have a direct relationship with the consumer

Record Keeping (CPPA Regulations §7101)

Businesses that buy, receive, or sell the PI of 10,000,000 or more consumers must compile metrics for the prior calendar year and disclose:

  • Number of requests to know, delete, correct, and opt-out received
  • Number of requests complied with in whole or in part
  • Number of requests denied
  • Median number of days to respond

Enforcement

CPPA Enforcement (§1798.199.40-199.100)

  • Administrative enforcement actions by the CPPA
  • Administrative fines up to $2,500 per violation; $7,500 per intentional violation or violations involving minors under 16
  • CPPA has authority to issue regulations, conduct investigations, and bring enforcement actions
  • 30-day cure period was eliminated by CPRA effective January 1, 2023

Private Right of Action (§1798.150)

Limited to data breach claims where nonencrypted and nonredacted PI (as defined in Cal. Civ. Code §1798.81.5(d)(1)(A)) is subject to unauthorized access due to the business's failure to implement reasonable security measures.

  • Statutory damages: $100-$750 per consumer per incident, or actual damages (whichever is greater)
  • Injunctive or declaratory relief
  • Any other relief the court deems proper
  • 30-day notice and cure period before filing suit

Implementation Roadmap for Liberty Commerce Inc.

Phase 1: Assessment (Weeks 1-4)

  1. Data inventory and mapping of all PI and sensitive PI categories
  2. Identify all data flows: collection, use, sale, sharing, disclosure
  3. Map service providers, contractors, and third parties
  4. Assess current privacy notice against CPRA requirements
  5. Evaluate consumer request processing workflows

Phase 2: Legal Framework (Weeks 5-8)

  1. Update privacy notice with retention periods, sensitive PI categories, sale/sharing disclosures
  2. Draft/update data processing agreements for all service providers and contractors
  3. Develop consumer request verification procedures
  4. Establish authorized agent acceptance procedures
  5. Create financial incentive program valuation methodology (if applicable)

Phase 3: Technical Implementation (Weeks 9-16)

  1. Deploy "Do Not Sell or Share My Personal Information" link
  2. Deploy "Limit the Use of My Sensitive Personal Information" link
  3. Implement GPC signal detection and honoring
  4. Build consumer request intake portal with identity verification
  5. Implement cascading deletion workflow
  6. Build right-to-know report generation (JSON and PDF)
  7. Implement data minimization controls and retention enforcement

Phase 4: Operations (Weeks 17-20)

  1. Train customer service team on CCPA/CPRA consumer rights
  2. Establish 45-day SLA monitoring for consumer requests
  3. Implement metrics tracking per CPPA Regulations §7101
  4. Schedule annual privacy notice review
  5. Conduct tabletop exercise for consumer request processing

Key Regulatory References

  • California Civil Code §1798.100-199 (CCPA as amended by CPRA)
  • California Privacy Rights Act (Proposition 24, approved November 3, 2020)
  • CPPA Final Regulations (effective March 29, 2023; updated regulations effective March 29, 2024)
  • CPPA Regulations §7001-7102 (Title 11, Division 6, California Code of Regulations)
  • Cal. Civ. Code §1798.81.5 — Data breach notification
  • AG Enforcement Actions: Sephora Inc. ($1.2 million settlement, August 2022) — first public CCPA enforcement action for failure to honor GPC opt-out signals
  • CPPA Enforcement Advisory No. 2024-01 — Dark patterns in consent interfaces

Colorado Privacy Act (CPA) Compliance

Overview

The Colorado Privacy Act (CPA), codified as C.R.S. §6-1-1301 through §6-1-1313, was signed into law on July 7, 2021 (SB 21-190), and became effective July 1, 2023. Colorado was the third state to enact comprehensive consumer privacy legislation. The CPA is notable for its robust rulemaking by the Colorado Attorney General, resulting in detailed implementing regulations at 4 CCR 904-3, and for being the first state (alongside Connecticut) to require recognition of universal opt-out mechanisms.

The Colorado AG published final rules effective March 1, 2024, with the universal opt-out mechanism requirement taking effect July 1, 2024.

Applicability (§6-1-1304)

The CPA applies to controllers that conduct business in Colorado or produce products or services intentionally targeted to Colorado residents AND:

  1. Control or process personal data of 100,000 or more Colorado consumers per calendar year; OR
  2. Control or process personal data of 25,000 or more Colorado consumers AND derive revenue or receive a discount on the price of goods or services from the sale of personal data.

Note: Threshold (2) does not require a specific revenue percentage (unlike Virginia's 50% threshold).

Exemptions (§6-1-1304(2)):

  • State and local government entities
  • National securities associations registered under 15 U.S.C. §78o-3
  • Financial institutions and affiliates subject to GLBA (entity-level)
  • Covered entities and business associates under HIPAA (entity-level)
  • Nonprofit organizations
  • Institutions of higher education
  • Data governed by GLBA, HIPAA, FERPA, FCRA, DPPA, COPPA, Farm Credit Act, and certain other federal statutes

Liberty Commerce Inc. Assessment: Liberty Commerce Inc. processes data of approximately 98,000 Colorado consumers and derives advertising revenue from data-related activities. It meets threshold (2) and is subject to the CPA.

Consumer Rights (§6-1-1306)

1. Right to Access (§6-1-1306(1)(a))

Confirm whether a controller is processing their personal data and access such data.

2. Right to Correct (§6-1-1306(1)(b))

Correct inaccuracies in personal data, taking into account the nature of the data and the purposes of processing.

3. Right to Delete (§6-1-1306(1)(c))

Delete personal data provided by or obtained about the consumer.

4. Right to Data Portability (§6-1-1306(1)(d))

Obtain personal data in a portable and, to the extent technically feasible, readily usable format.

5. Right to Opt Out (§6-1-1306(1)(e))

Opt out of processing for purposes of:

  • Targeted advertising
  • Sale of personal data
  • Profiling in furtherance of decisions that produce legal or similarly significant effects

Liberty Commerce Inc. Implementation: All five rights are exercisable through the privacy portal at privacy.libertycommerce.com/colorado. Opt-out rights are also accessible via universal opt-out mechanism (GPC) and a dedicated "Your Privacy Choices" link with the Colorado-approved opt-out icon.

Universal Opt-Out Mechanism (4 CCR 904-3, Rule 5.11)

The CPA is the first state law (alongside Connecticut) to mandate that controllers recognize universal opt-out mechanisms. The requirement became effective July 1, 2024.

Requirements

Controllers must:

  1. Recognize and process opt-out signals sent through a universal opt-out mechanism
  2. Treat the signal as a valid opt-out of sale of personal data and targeted advertising
  3. Not require additional consumer verification to process the signal
  4. Not display a pop-up, interstitial, or other mechanism asking the consumer to verify or modify the signal
  5. Apply the signal at the browser/device level for unauthenticated consumers
  6. Apply the signal at the account level for authenticated consumers
  7. Resolve conflicts in favor of the most recently expressed preference

Technical Standards (4 CCR 904-3, Rule 5.11)

The AG rules specify that a universal opt-out mechanism must:

  • Be a setting or extension of a platform, technology, or mechanism
  • Not be a default setting (must be affirmatively selected by the consumer)
  • Clearly communicate to the consumer what the setting means
  • Be consumer-friendly and easy to use
  • Send a signal to the controller that clearly communicates the consumer's choice

Global Privacy Control (GPC) is recognized as a compliant universal opt-out mechanism.

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. detects GPC via the Sec-GPC: 1 HTTP header and navigator.globalPrivacyControl JavaScript API. Upon detection:

  • Unauthenticated: Apply session-level opt-out of targeted advertising and sale
  • Authenticated: Permanently set account-level opt-out preferences
  • Suppress all third-party advertising tags and data sharing for cross-context behavioral advertising
  • Allow first-party analytics under processor agreement

Sensitive Data (§6-1-1304(26), §6-1-1308(7))

Categories

  1. Personal data revealing racial or ethnic origin
  2. Religious beliefs
  3. Mental or physical health condition or diagnosis
  4. Sex life or sexual orientation
  5. Citizenship or citizenship status
  6. Genetic or biometric data processed for uniquely identifying an individual
  7. Personal data of a known child

Consent Requirement

Processing of sensitive data requires the consumer's opt-in consent. Consent must be:

  • Freely given, specific, informed, and unambiguous
  • Clear affirmative act (no pre-checked boxes)
  • Specific to each sensitive data category and purpose

Profiling Opt-Out (§6-1-1306(1)(e)(III))

Consumers may opt out of profiling in furtherance of decisions that produce legal or similarly significant effects. This is broader than most state laws and includes:

  • Decisions about provision or denial of financial or lending services
  • Decisions about provision or denial of housing
  • Decisions about provision or denial of insurance
  • Decisions about provision or denial of education enrollment or opportunity
  • Decisions about provision or denial of employment
  • Decisions about provision or denial of health care services
  • Decisions about access to basic necessities (food, water, shelter, energy, transportation)

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. conducts profiling for its buy-now-pay-later feature (credit scoring). Colorado consumers are provided a specific opt-out mechanism for this profiling activity, with disclosure of the logic involved, significance of the decision, and anticipated consequences.

Controller Obligations (§6-1-1308)

Privacy Notice (§6-1-1308(1))

Must include:

  • Categories of personal data collected or processed
  • Purposes for processing
  • Consumer rights and how to exercise them
  • Categories of personal data shared with third parties
  • Categories of third parties with whom data is shared
  • Contact information (email or online mechanism)
  • Whether personal data is sold or used for targeted advertising
  • Whether profiling is conducted and opt-out information

Data Minimization (§6-1-1308(3))

Collection must be adequate, relevant, and limited to what is reasonably necessary in relation to the specified purposes.

Purpose Limitation (§6-1-1308(4))

Processing may not exceed what is reasonably necessary to and compatible with the specified purposes.

Data Security (§6-1-1308(5))

Reasonable administrative, technical, and physical security practices appropriate to the volume, scope, and nature of the data.

Non-Discrimination (§6-1-1308(6))

May not process personal data in violation of state and federal antidiscrimination laws.

DPIA Requirements (§6-1-1309)

Controllers must conduct DPIAs for:

  • Targeted advertising processing
  • Sale of personal data
  • Certain types of profiling
  • Sensitive data processing
  • Any processing presenting heightened risk of harm

DPIAs must be made available to the AG upon request.

Enforcement (§6-1-1311, §6-1-1312)

Attorney General Authority

  • Exclusive enforcement under the Colorado Consumer Protection Act (§6-1-101 et seq.)
  • May issue civil investigative demands
  • May seek injunctive relief, restitution, and civil penalties

Cure Period

  • 60-day cure period was available until January 1, 2025
  • After January 1, 2025: No automatic cure period; AG has discretion to consider good-faith efforts

Penalties

  • Treated as a deceptive trade practice under §6-1-105
  • Civil penalties up to $20,000 per violation (under Colorado Consumer Protection Act)
  • Injunctive relief and restitution

AG Rulemaking (4 CCR 904-3)

The Colorado AG published comprehensive regulations addressing:

  • Rule 2: Definitions and general provisions
  • Rule 3: Consumer rights procedures
  • Rule 4: Controller and processor obligations
  • Rule 5: Universal opt-out mechanism technical standards
  • Rule 6: Consent requirements for sensitive data
  • Rule 7: Data protection impact assessment requirements
  • Rule 8: Biennial review of universal opt-out mechanisms

Key Regulatory References

  • C.R.S. §6-1-1301 through §6-1-1313 (Colorado Privacy Act)
  • 4 CCR 904-3 (AG implementing regulations, effective March 1, 2024)
  • C.R.S. §6-1-101 et seq. (Colorado Consumer Protection Act — enforcement framework)
  • AG Technical Guidance on Universal Opt-Out Mechanisms (July 2024)
  • Global Privacy Control Specification v1.0

Connecticut Data Privacy Act (CTDPA)

Overview

The Connecticut Data Privacy Act (CTDPA), codified as Conn. Gen. Stat. §42-515 through §42-525, was signed into law on May 10, 2022 (SB 6), and became effective July 1, 2023. Connecticut was the fifth state to enact comprehensive consumer privacy legislation. The CTDPA is notable for its explicit prohibition on dark patterns in obtaining consent, its bona fide loyalty program exemption, and its requirement to recognize universal opt-out mechanisms (effective January 1, 2025).

Applicability (§42-516)

The CTDPA applies to persons that conduct business in Connecticut or produce products or services targeted to Connecticut residents AND during the preceding calendar year:

  1. Controlled or processed personal data of at least 100,000 Connecticut consumers (excluding data processed solely for payment transactions); OR
  2. Controlled or processed personal data of at least 25,000 Connecticut consumers AND derived more than 25% of gross revenue from the sale of personal data.

Note: The 25% revenue threshold is lower than Virginia's 50% and mirrors no specific percentage in Colorado.

Exemptions: State/local government, GLBA institutions (entity-level), HIPAA covered entities/BAs (entity-level), nonprofits, higher education institutions, and data governed by certain federal statutes.

Liberty Commerce Inc. Assessment: Liberty Commerce Inc. processes personal data of approximately 87,000 Connecticut consumers. With 12% advertising revenue from data sale activities, it does not meet threshold (2). However, excluding payment-only transactions, the consumer count exceeds the threshold under a conservative reading. Liberty Commerce Inc. treats itself as subject to the CTDPA.

Consumer Rights (§42-520)

Six Consumer Rights

  1. Right to Access (§42-520(a)(1)): Confirm processing and access personal data
  2. Right to Correct (§42-520(a)(2)): Correct inaccuracies
  3. Right to Delete (§42-520(a)(3)): Delete personal data
  4. Right to Portability (§42-520(a)(4)): Obtain data in portable, readily usable format
  5. Right to Opt Out (§42-520(a)(5)): Opt out of:
    • Targeted advertising
    • Sale of personal data
    • Profiling in furtherance of decisions producing legal or similarly significant effects
  6. Right to Appeal (§42-520(f)): Appeal a denial of any rights request

Response Requirements (§42-520(b)-(e))

  • Respond within 45 days of receipt
  • Extension: up to 45 additional days with notice
  • At least one free response per 12 months per right
  • Appeal: controller must respond within 60 days

Dark Pattern Prohibition (§42-515(8), §42-518(a)(5))

The CTDPA explicitly defines and prohibits dark patterns in the context of obtaining consumer consent. A "dark pattern" is defined as:

"A user interface designed or manipulated with the substantial effect of subverting or impairing user autonomy, decision-making or choice, and includes, but is not limited to, any practice the Federal Trade Commission refers to as a 'dark pattern'."

Implications

  • Consent obtained through dark patterns is not valid consent under the CTDPA
  • Applies to consent for sensitive data processing (§42-518(a)(5))
  • Applies to consent for processing children's data
  • Any consent mechanism that uses confusing language, hidden options, visual manipulation, or other deceptive practices is invalid

Dark Pattern Examples (per FTC guidance and CTDPA legislative history)

PatternDescriptionCTDPA Impact
Confirm-shamingUsing guilt-inducing language for the opt-out optionConsent invalid
Hidden optionsMaking the reject/decline option visually less prominentConsent invalid
Forced actionRequiring consent to access unrelated featuresConsent invalid
Trick questionsUsing double negatives or confusing languageConsent invalid
MisdirectionVisual design that steers users toward consentConsent invalid
NaggingRepeated prompts after consumer declinesConsent invalid

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. has conducted a dark pattern audit of all consent interfaces. Consent buttons use equal visual weight (same size, same font, same color prominence). "Accept" and "Decline" options are presented side by side. Language is affirmative and clear. No confirm-shaming language is used.

Bona Fide Loyalty Program Exemption (§42-517(c))

The CTDPA provides an exemption for bona fide loyalty, rewards, premium, discount, or club card programs. Personal data collected as part of such programs is exempt from the sale opt-out right if:

  1. The program is a bona fide loyalty program (genuine value provided to the consumer)
  2. The consumer voluntarily participates
  3. The controller clearly discloses the data collection in the loyalty program terms
  4. The data is used solely for the purpose of the loyalty program

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. operates the "Liberty Rewards" program. The program terms clearly state that purchase history and preference data are used exclusively for rewards calculation, personalized offers within the program, and member benefits. This data is not sold or used for cross-context behavioral advertising outside the loyalty program scope.

Universal Opt-Out Mechanism (§42-520(a)(6))

Effective January 1, 2025, controllers must recognize universal opt-out mechanisms. Requirements parallel Colorado's framework:

  • Must recognize and process universal opt-out signals (including GPC)
  • Signal applies to targeted advertising and sale of personal data
  • No additional consumer verification required
  • No pop-up or interstitial questioning the signal
  • Apply at browser/device level for unauthenticated; account level for authenticated

Sensitive Data (§42-518(a)(5))

Categories

Same as Virginia VCDPA:

  1. Racial or ethnic origin
  2. Religious beliefs
  3. Mental or physical health condition or diagnosis
  4. Sexual orientation
  5. Citizenship or immigration status
  6. Genetic or biometric data for identification
  7. Personal data of a known child
  8. Precise geolocation data

Consent Requirement

Processing requires opt-in consent that is not obtained through a dark pattern.

Controller Obligations (§42-518)

  1. Purpose limitation: Limit processing to what is adequate, relevant, and reasonably necessary
  2. Data minimization: Do not collect more than reasonably necessary
  3. Data security: Appropriate technical and organizational measures
  4. Non-discrimination: No processing in violation of antidiscrimination laws
  5. Sensitive data consent: Obtain consent (not via dark pattern) before processing
  6. Privacy notice: Reasonably accessible and clear
  7. DPIAs: Conduct assessments for targeted advertising, sale, profiling, sensitive data, and high-risk processing

Enforcement (§42-524, §42-525)

  • Exclusive AG enforcement — no private right of action
  • 60-day cure period until December 31, 2024
  • After January 1, 2025: AG has discretion on cure period
  • Penalties: Treated as unfair trade practices under Conn. Gen. Stat. §42-110b (CUTPA)
  • Civil penalties: Up to $5,000 per willful violation under CUTPA

Key Regulatory References

  • Conn. Gen. Stat. §42-515 through §42-525 (CTDPA)
  • Conn. Gen. Stat. §42-110b (Connecticut Unfair Trade Practices Act — enforcement)
  • FTC Dark Patterns Report (September 2022) — referenced in CTDPA definition
  • Global Privacy Control Specification v1.0 — recognized universal opt-out mechanism

CPRA Sensitive Personal Information

Overview

The California Privacy Rights Act (CPRA) introduced the concept of "sensitive personal information" (sensitive PI) as a distinct category under Cal. Civ. Code §1798.140(ae), effective January 1, 2023. This category parallels but is not identical to the GDPR's "special categories of data" under Article 9. The CPRA grants consumers the right to limit a business's use and disclosure of their sensitive PI to specific enumerated purposes under §1798.121.

Unlike the GDPR, which generally prohibits processing of special categories unless an exception applies, the CPRA permits businesses to collect and use sensitive PI but gives consumers the right to restrict that processing after collection through the "limit use" mechanism.

Sensitive PI Categories (§1798.140(ae))

Category 1: Government Identifiers

Social Security number, driver's license number, state identification card number, or passport number.

Liberty Commerce Inc. Processing: Liberty Commerce Inc. collects Social Security numbers for tax reporting (1099-K forms) from marketplace sellers exceeding $600 in annual sales per IRS reporting thresholds. Driver's license numbers are collected for age verification on restricted product purchases. These are stored in a segregated, encrypted database with access limited to the tax compliance and fraud prevention teams.

Category 2: Account Credentials

Account log-in, financial account, debit card, or credit card number in combination with any required security or access code, password, or credentials allowing access to an account.

Liberty Commerce Inc. Processing: Payment card data is processed via PCI DSS-compliant service provider PaySecure Corp. and is not stored in Liberty Commerce Inc.'s systems in cleartext. Account credentials (hashed passwords, MFA tokens) are stored in the identity management system with bcrypt hashing and per-account salt.

Category 3: Precise Geolocation

Any data that is derived from a device and that is used or intended to be used to locate a consumer within a geographic area that is equal to or less than the area of a circle with a radius of 1,850 feet (approximately 564 meters).

Liberty Commerce Inc. Processing: The mobile app collects precise geolocation for store finder, delivery tracking, and local inventory search. Geolocation data is processed in real time and retained for 30 days. Upon a consumer's limit request, geolocation processing is restricted to delivery tracking only (a permitted service fulfillment purpose).

Category 4: Racial or Ethnic Origin

Racial or ethnic origin of the consumer.

Liberty Commerce Inc. Processing: Liberty Commerce Inc. collects racial/ethnic origin data through an optional workforce diversity survey for employees and an optional customer demographic survey. Customer survey data is aggregated and anonymized within 90 days. Upon a limit request, survey data collection ceases for that consumer and existing data is deleted.

Category 5: Religious or Philosophical Beliefs

Religious or philosophical beliefs of the consumer.

Liberty Commerce Inc. Processing: Not actively collected. May be inferred from product purchase patterns (religious texts, dietary products). Liberty Commerce Inc. does not create inferences about religious beliefs for advertising purposes. Product recommendation algorithms are configured to exclude religion-indicative categories from profile building.

Category 6: Union Membership

Union membership of the consumer.

Liberty Commerce Inc. Processing: Collected only for employees where required for payroll processing (union dues deduction). Not collected from consumers. Stored in HR system with access restricted to payroll administrators.

Category 7: Private Communications Content

Contents of a consumer's mail, email, and text messages unless the business is the intended recipient of the communication.

Liberty Commerce Inc. Processing: Customer service email and chat communications are retained for quality assurance and dispute resolution. Liberty Commerce Inc. is the intended recipient of these communications, so they fall outside the sensitive PI definition for purposes of the limit right. Third-party message content is not collected.

Category 8: Genetic Data

A consumer's genetic data.

Liberty Commerce Inc. Processing: Not collected. Liberty Commerce Inc. does not process genetic data for any business purpose.

Category 9: Biometric Information

Processing of biometric information for the purpose of uniquely identifying a consumer.

Liberty Commerce Inc. Processing: Face ID and fingerprint authentication are processed locally on the consumer's device via platform APIs (Apple Face ID, Android BiometricPrompt). Liberty Commerce Inc. does not receive, store, or process raw biometric templates. Device-side biometric results are used only to unlock the app and authorize transactions.

Category 10: Health Information

A consumer's health information.

Liberty Commerce Inc. Processing: Health-related product purchases (vitamins, supplements, medical devices) are recorded as transaction data. Liberty Commerce Inc. does not infer health conditions from purchase patterns for advertising. Health product purchase data is excluded from behavioral advertising profiles.

Category 11: Sex Life or Sexual Orientation

Information concerning a consumer's sex life or sexual orientation.

Liberty Commerce Inc. Processing: Not actively collected. May be inferred from product purchases. Liberty Commerce Inc. does not create or use inferences about sex life or sexual orientation for any business purpose.

Right to Limit Use and Disclosure (§1798.121)

Consumer Exercise Mechanism

  • Business must display a "Limit the Use of My Sensitive Personal Information" link on its homepage
  • The link may be combined with the opt-out link as a single "Your Privacy Choices" link per CPPA Regulations §7026(b)
  • The CPPA-approved opt-out icon may be used in conjunction with the link
  • No identity verification is required — the consumer's direction itself is sufficient

Permitted Purposes After Limitation (§1798.121(a))

After a consumer exercises the limit right, the business may only use or disclose sensitive PI for:

#Permitted PurposeStatuteLiberty Commerce Inc. Application
1Perform services or provide goods reasonably expected by average consumer§1798.121(a)(1)Process transactions, fulfill orders, deliver products
2Prevent, detect, investigate security incidents§1798.121(a)(2)Fraud detection using account credentials and geolocation anomalies
3Resist malicious, deceptive, fraudulent, or illegal actions§1798.121(a)(3)Chargeback investigation, account takeover prevention
4Ensure physical safety of natural persons§1798.121(a)(4)Product recall notifications using health product purchase data
5Short-term, transient use including non-personalized advertising§1798.121(a)(5)Contextual (non-targeted) advertising based on current page content
6Perform services on behalf of the business§1798.121(a)(6)Customer service, account maintenance, warranty processing
7Verify or maintain quality or safety of a service or device§1798.121(a)(7)App functionality testing, payment processing verification
8Upgrade, enhance, or improve services§1798.121(a)(8)Aggregate analytics for service improvement (no individual targeting)

Processing Restrictions After Limitation

After a limit request, Liberty Commerce Inc. implements the following restrictions:

Sensitive PI CategoryProhibited UsesPermitted Uses
Precise geolocationTargeted advertising, location-based marketing, sale to data brokersDelivery tracking, store finder (if actively requested)
Payment credentialsCross-referencing for marketing profiles, sharing with ad networksTransaction processing, fraud detection
Racial/ethnic originAny marketing or profilingAggregate diversity reporting (anonymized)
Government IDsAny use beyond original collection purposeTax reporting (SSN), age verification (DL)

Privacy Notice Disclosure Requirements

Notice at Collection (§1798.100(a))

When collecting sensitive PI, the business must disclose:

  • The categories of sensitive PI to be collected
  • The purposes for which each category will be used
  • Whether each category is sold or shared
  • The retention period or criteria for each category

Privacy Policy (§1798.130(a)(5))

The privacy policy must separately identify:

  • Categories of sensitive PI collected in the preceding 12 months
  • Categories of sensitive PI sold or shared
  • Purposes for using each sensitive PI category
  • Whether consumers can limit use via the "Limit" link

Liberty Commerce Inc. Privacy Notice Excerpt:

Sensitive Personal Information We Collect: We collect the following categories of sensitive personal information: (1) Social Security numbers from marketplace sellers for tax reporting; (2) payment card details for transaction processing; (3) precise geolocation through our mobile app for delivery and store finder services. We do not sell or share your sensitive personal information. You may limit our use of your sensitive personal information by clicking "Limit the Use of My Sensitive Personal Information" in the footer of any page or by contacting us at privacy@libertycommerce.com.

Comparison with GDPR Special Categories

AspectCPRA Sensitive PIGDPR Special Categories (Art. 9)
Default rulePermitted, with consumer right to limitProhibited, unless exception applies
Legal basisNo separate legal basis needed for collectionExplicit consent or specific exceptions required
Government IDsIncluded as sensitive PINot a special category (but may be restricted by Member State law)
Financial dataAccount credentials includedNot a special category
Precise geolocationIncluded as sensitive PINot a special category (but may be covered under ePrivacy)
EnforcementCPPA administrative fines; $7,500 for violations involving minorsDPA fines up to 4% annual turnover or EUR 20M

Implementation Checklist

#ItemStatusOwner
1Inventory all sensitive PI categories collectedCompletePrivacy Team
2Map purposes for each sensitive PI categoryCompletePrivacy Team
3Deploy "Limit the Use of My Sensitive Personal Information" linkCompleteEngineering
4Implement limit-request processing workflowCompleteEngineering
5Configure purpose-based access controls for sensitive PICompleteSecurity Team
6Update privacy notice with sensitive PI disclosuresCompleteLegal
7Train customer service on limit requestsCompleteOperations
8Configure data processing agreements with sensitive PI restrictionsCompleteLegal
9Test GPC signal interaction with limit mechanismCompleteQA
10Quarterly audit of sensitive PI processing against permitted purposesOngoingPrivacy Team

Key Regulatory References

  • Cal. Civ. Code §1798.121 — Right to limit use and disclosure of sensitive PI
  • Cal. Civ. Code §1798.140(ae) — Definition of sensitive personal information
  • Cal. Civ. Code §1798.135(a)(2) — "Limit" link requirement
  • CPPA Regulations §7026 — Requests to limit sensitive PI
  • CPPA Regulations §7027 — Combined opt-out/limit link option
  • GDPR Article 9 — Processing of special categories of personal data (comparative reference)

Kentucky Consumer Privacy Protection Act (KPPA)

Overview

The Kentucky Consumer Privacy Protection Act (KPPA), codified as KRS §367.401 through §367.445, was signed into law on April 4, 2024 (HB 15), and becomes effective January 1, 2026. Kentucky follows the Virginia/Connecticut model with five consumer rights, controller-processor framework, sensitive data opt-in consent, and AG-only enforcement.

Applicability (§367.405)

The KPPA applies to persons that conduct business in Kentucky or produce products or services targeted to Kentucky residents AND during a calendar year:

  1. Control or process personal data of at least 100,000 Kentucky consumers; OR
  2. Control or process personal data of at least 25,000 Kentucky consumers AND derive more than 50% of gross revenue from the sale of personal data.

Exemptions (§367.407):

  • State and local government entities
  • GLBA-covered financial institutions (entity-level)
  • HIPAA covered entities and business associates (entity-level)
  • Nonprofit organizations
  • Institutions of higher education
  • Covered entities under FERPA
  • Data governed by GLBA, HIPAA, FERPA, FCRA, DPPA, COPPA, Farm Credit Act

Liberty Commerce Inc. Assessment: Liberty Commerce Inc. processes personal data of approximately 68,000 Kentucky consumers. It does not meet either threshold but monitors as the law becomes effective January 1, 2026.

Consumer Rights (§367.415)

Five Consumer Rights

  1. Right to Access (§367.415(1)(a)): Confirm processing and access personal data
  2. Right to Correct (§367.415(1)(b)): Correct inaccuracies
  3. Right to Delete (§367.415(1)(c)): Delete personal data
  4. Right to Portability (§367.415(1)(d)): Obtain data in portable format
  5. Right to Opt Out (§367.415(1)(e)):
    • Targeted advertising
    • Sale of personal data
    • Profiling in furtherance of decisions producing legal or similarly significant effects

Response Requirements (§367.417)

  • Respond within 45 days
  • Extension: up to 45 additional days (90 total) with notice
  • At least one free response per 12 months per right
  • Appeal: controller must respond within 60 days

Sensitive Data (§367.401(27), §367.413(5))

Categories

  1. Racial or ethnic origin
  2. Religious beliefs
  3. Mental or physical health diagnosis
  4. Sexual orientation
  5. Citizenship or immigration status
  6. Genetic or biometric data for identification
  7. Personal data of a known child
  8. Precise geolocation data

Consent Requirement

Processing requires opt-in consent before processing. The KPPA follows the Virginia model requiring affirmative, freely given consent.

Controller Obligations (§367.413)

  1. Purpose limitation: Adequate, relevant, and reasonably necessary
  2. Data minimization: Not excessive relative to purposes
  3. Data security: Appropriate technical and organizational measures
  4. Non-discrimination: No processing in violation of antidiscrimination laws
  5. Sensitive data consent: Opt-in before processing
  6. Transparency: Clear and reasonably accessible privacy notice

Privacy Notice Requirements (§367.413(2))

  • Categories of personal data processed
  • Purposes for processing each category
  • Consumer rights and how to exercise them
  • Categories of data shared with third parties
  • Categories of third parties
  • Active email or online contact mechanism

Data Protection Assessments (§367.419)

Required for:

  • Targeted advertising
  • Sale of personal data
  • Profiling with significant effects
  • Sensitive data processing
  • High-risk processing activities

DPIAs must be made available to the AG upon request.

Processor Requirements (§367.421)

Processing must be governed by a contract that includes:

  • Instructions for processing
  • Nature, purpose, and duration
  • Type of data and categories of consumers
  • Controller and processor rights and obligations
  • Confidentiality duty for persons processing data
  • Return or deletion upon end of services
  • Cooperation with compliance assessments
  • Sub-processor contract requirements with equivalent protections

Enforcement (§367.435)

Attorney General Authority

  • Exclusive enforcement — no private right of action
  • Enforcement under KRS §367.990 (Kentucky Consumer Protection Act)

Cure Period (§367.437)

  • AG must provide written notice of alleged violation
  • Controller has 30 days to cure
  • If cured and express written statement provided: AG may not bring action
  • No sunset provision — 30-day cure period is permanent

Penalties

  • Civil penalties up to $7,500 per violation
  • Injunctive relief
  • Costs and attorney fees

Implementation Timeline

MilestoneDateAction
Law enactedApril 4, 2024HB 15 signed by Governor
Compliance planningApril 2024 - December 2025Gap analysis, privacy notice updates, consent mechanisms
Data protection assessmentsJuly - December 2025Complete DPIAs for applicable processing activities
Technical implementationSeptember - December 2025Deploy consumer rights portal, opt-out mechanisms
Staff trainingNovember - December 2025Train privacy team and customer service
Effective dateJanuary 1, 2026Full compliance required

Key Regulatory References

  • KRS §367.401 through §367.445 (KPPA)
  • KRS §367.990 (Kentucky Consumer Protection Act — enforcement penalties)
  • KRS §365.732 (Kentucky Data Breach Notification)

Montana Consumer Data Privacy Act (MTDPA)

Overview

The Montana Consumer Data Privacy Act (MTDPA), codified as MCA §30-14-2801 through §30-14-2817, was signed into law on May 19, 2023 (SB 384), and became effective October 1, 2024. Montana is notable for having the lowest consumer count threshold of any comprehensive state privacy law at 50,000 consumers, making it applicable to smaller organizations operating in or targeting Montana residents.

Applicability (§30-14-2803)

The MTDPA applies to persons that conduct business in Montana or produce products or services targeted to Montana residents AND during a calendar year:

  1. Control or process personal data of at least 50,000 Montana consumers (excluding data processed solely for payment transactions); OR
  2. Control or process personal data of at least 25,000 Montana consumers AND derive more than 25% of gross revenue from the sale of personal data.

Lowest threshold: The 50,000 consumer threshold is the lowest among comprehensive state privacy laws (most states use 100,000).

Exemptions (§30-14-2803(3)):

  • State and local government entities
  • GLBA-covered financial institutions (entity-level)
  • HIPAA covered entities and business associates (entity-level)
  • Nonprofit organizations
  • Institutions of higher education
  • Air carriers

Liberty Commerce Inc. Assessment: Liberty Commerce Inc. processes personal data of approximately 28,000 Montana consumers. It does not meet either threshold but maintains compliance as part of its multi-state program.

Consumer Rights (§30-14-2808)

Five Consumer Rights

  1. Right to Access (§30-14-2808(1)(a)): Confirm processing and access personal data
  2. Right to Correct (§30-14-2808(1)(b)): Correct inaccuracies
  3. Right to Delete (§30-14-2808(1)(c)): Delete personal data
  4. Right to Portability (§30-14-2808(1)(d)): Obtain data in portable, readily usable format
  5. Right to Opt Out (§30-14-2808(1)(e)):
    • Targeted advertising
    • Sale of personal data
    • Profiling in furtherance of decisions producing legal or similarly significant effects

Response Requirements (§30-14-2810)

  • Respond within 45 days
  • Extension: up to 15 additional days (total 60 days) with notice — shorter extension than most states
  • At least one free response per 12 months per right
  • Appeal: controller must respond within 60 days

Sensitive Data (§30-14-2801(19))

Categories

  1. Racial or ethnic origin
  2. Religious beliefs
  3. Mental or physical health condition or diagnosis
  4. Sexual orientation
  5. Citizenship or immigration status
  6. Genetic or biometric data for identification
  7. Personal data of a known child
  8. Precise geolocation data

Consent Requirement

Processing sensitive data requires opt-in consent before processing. Consent must be freely given, specific, informed, and unambiguous.

Universal Opt-Out Recognition (§30-14-2808(3))

The MTDPA requires controllers to recognize universal opt-out mechanisms:

  • Must process universal opt-out signals as valid requests to opt out of targeted advertising and sale
  • Must not require additional verification for opt-out signals
  • Must apply at browser/device level for unauthenticated consumers
  • Must apply at account level for authenticated consumers
  • GPC is recognized as a compliant mechanism

Effective date: October 1, 2025 (one year after MTDPA effective date)

Controller Obligations (§30-14-2806)

  1. Purpose limitation: Adequate, relevant, and reasonably necessary
  2. Data minimization: Not excessive in relation to purposes
  3. Data security: Appropriate technical and organizational measures
  4. Non-discrimination: No processing in violation of antidiscrimination laws
  5. Sensitive data consent: Opt-in before processing
  6. Privacy notice: Clear and reasonably accessible

Privacy Notice Requirements

  • Categories of personal data processed
  • Purposes for processing
  • Consumer rights and exercise instructions
  • Categories shared with third parties
  • Categories of third parties
  • Contact information

Data Protection Assessments (§30-14-2812)

Required for:

  • Targeted advertising
  • Sale of personal data
  • Profiling with significant effects
  • Sensitive data processing
  • Any processing presenting heightened risk

Enforcement (§30-14-2816)

Attorney General Authority

  • Exclusive enforcement — no private right of action
  • May investigate and bring action under Montana Consumer Protection Act (§30-14-103)

60-Day Cure Period (§30-14-2816(2))

  • AG must provide written notice of alleged violation
  • Controller has 60 days to cure
  • If cured: AG may not bring action
  • No sunset provision — cure period is permanent

Penalties

  • Civil penalties per Montana Consumer Protection Act
  • Injunctive relief
  • Attorney fees and costs

Comparison: Threshold Analysis

StateConsumer Threshold (Option 1)Consumer Threshold (Option 2)Revenue %
Montana50,00025,00025%
Virginia100,00025,00050%
Colorado100,00025,000Any
Connecticut100,00025,00025%
Oregon100,00025,00025%
TexasN/A (non-SBA small business)N/AN/A
California100,000 householdsN/A50%

Key Regulatory References

  • MCA §30-14-2801 through §30-14-2817 (MTDPA)
  • MCA §30-14-103 et seq. (Montana Consumer Protection Act — enforcement)
  • Montana AG Consumer Protection Division guidance

Multi-State Harmonized Compliance Program

Overview

As of 2026, over 20 US states have enacted comprehensive consumer privacy legislation. Organizations operating nationwide face a complex patchwork of requirements with significant overlap but important state-specific variations. A harmonized multi-state compliance program identifies the common baseline, maps state-specific deltas, and implements a unified privacy architecture that satisfies all applicable laws.

This skill covers the eight major enacted and effective state privacy laws: CCPA/CPRA (California), VCDPA (Virginia), CPA (Colorado), CTDPA (Connecticut), TDPSA (Texas), OCPA (Oregon), MTDPA (Montana), and KPPA (Kentucky).

Common Requirements Matrix

Consumer Rights — Universal Baseline

All eight laws provide these core rights:

RightCAVACOCTTXORMTKY
Access/KnowYesYesYesYesYesYesYesYes
CorrectYesYesYesYesYesYesYesYes
DeleteYesYesYesYesYesYesYesYes
PortabilityYesYesYesYesYesYesYesYes
Opt-out: targeted adsYesYesYesYesYesYesYesYes
Opt-out: saleYesYesYesYesYesYesYesYes
Opt-out: profilingNo*YesYesYesYesYesYesYes
Limit sensitive PIYesN/AN/AN/AN/AN/AN/AN/A
Third-party listNoNoNoNoNoYesNoNo
AppealNoYesYesYesYesYesYesYes

*California provides opt-out of automated decision-making under pending CPPA regulations.

Controller Obligations — Universal Baseline

ObligationAll States
Privacy notice/policyRequired
Data minimizationRequired
Purpose limitationRequired
Data securityRequired
Non-discriminationRequired
Response timeline45 days (all states)

State-Specific Deltas

California (CCPA/CPRA) — Unique Requirements

  • Revenue threshold: $25M alternative threshold (no other state has this)
  • Sensitive PI limit right: Post-collection limit mechanism (other states require pre-collection consent)
  • CPPA enforcement: Dedicated privacy agency (only state with one)
  • Private right of action: For data breach claims (only state with any private right of action)
  • Annual metrics: Required for businesses processing 10M+ consumers
  • Data processing agreements: Explicit statutory requirement
  • No cure period: Eliminated by CPRA

Virginia (VCDPA) — Unique Requirements

  • 50% revenue threshold: Higher revenue percentage requirement than most states

Colorado (CPA) — Unique Requirements

  • AG rulemaking: Most detailed implementing regulations (4 CCR 904-3)
  • Universal opt-out: First mandated (effective July 2024)
  • Profiling opt-out scope: Broadest definition covering 7+ decision categories
  • $20,000 penalties: Higher per-violation penalties under Consumer Protection Act

Connecticut (CTDPA) — Unique Requirements

  • Dark pattern prohibition: Explicit statutory definition and prohibition
  • Loyalty program exemption: Bona fide loyalty programs exempt from sale opt-out
  • 25% revenue threshold: Lower than Virginia's 50%

Texas (TDPSA) — Unique Requirements

  • No revenue/consumer threshold: Applies to all non-SBA-small businesses
  • Data broker registration: Secretary of State registration requirement
  • CUBI interaction: Separate biometric data law (up to $25,000/violation)
  • Broadest applicability: Largest state population, lowest effective threshold

Oregon (OCPA) — Unique Requirements

  • Nonprofit coverage: Applies to nonprofit organizations
  • Third-party list right: Specific entity names, not just categories
  • De-identified data: Most detailed compliance requirements
  • Employee data partial exemption: Unique treatment of employee data
  • Transgender/nonbinary status: Explicit sensitive data category
  • 14-day cure period: Shortest cure period among states

Montana (MTDPA) — Unique Requirements

  • 50,000 consumer threshold: Lowest consumer count threshold
  • 15-day extension only: Shorter extension than most states' 45 days
  • Air carrier exemption: Unique industry exemption

Kentucky (KPPA) — Unique Requirements

  • January 2026 effective date: Most recently effective among this group
  • 50% revenue threshold: Matches Virginia

Unified Privacy Program Architecture

Tier 1: Common Baseline (Apply Everywhere)

These requirements are common across all states and form the foundation:

  1. Privacy notice with categories of PI, purposes, rights, third parties, contact info
  2. Consumer rights portal supporting access, correct, delete, portability, opt-out
  3. 45-day response SLA with tracking and metrics
  4. Data minimization and purpose limitation controls
  5. Reasonable data security measures
  6. Non-discrimination protections

Tier 2: High-Water Mark (Apply to Satisfy Strictest Requirement)

Where state requirements differ, apply the strictest standard universally:

AreaStrictest StandardSource State
Sensitive data consentOpt-in consent before collectionVA, CO, CT, TX, OR, MT, KY
Dark pattern prohibitionConsent via dark patterns invalidCT (explicit), all (implicit)
Response extension15-day extension onlyMT (strictest) or accept state-by-state
Universal opt-outHonor GPC signalsCA, CO, CT, MT
Profiling opt-outInclude 7+ decision categoriesCO (broadest scope)
De-identified dataFull compliance programOR (most detailed)
Privacy notice retention periodsInclude per-category retentionCA (CPRA requirement)

Tier 3: State-Specific (Apply Only Where Required)

RequirementState(s)Implementation
"Do Not Sell or Share" linkCAHomepage footer
"Limit Sensitive PI" linkCAAdjacent to opt-out link
Specific third-party listORAdditional disclosure in Oregon responses
Data broker registrationTXSecretary of State registration (if applicable)
Annual metrics disclosureCA (10M+)Privacy notice metrics section
Loyalty program exemptionCTProgram-specific terms
Nonprofit complianceORFull program for Oregon nonprofit operations

Implementation Strategy for Liberty Commerce Inc.

Approach: High-Water Mark with State-Specific Overlays

Liberty Commerce Inc. implements a unified privacy program at the highest common standard, with state-specific modules activated based on the consumer's state of residence.

Consumer Request Received
  │
  ├─► Determine Consumer's State
  │
  ├─► Apply Tier 1 Common Baseline
  │     (Same for all states)
  │
  ├─► Apply Tier 2 High-Water Mark
  │     (Strictest standard, applied universally)
  │
  └─► Apply Tier 3 State-Specific Module
        ├─ California module: CPRA-specific disclosures, sensitive PI limit
        ├─ Oregon module: Third-party specific list
        ├─ Texas module: Data broker check
        └─ Connecticut module: Loyalty program exemption assessment

Harmonized Privacy Notice Template

A multi-state privacy notice should include these sections to satisfy all eight laws:

  1. Categories of PI/personal data collected (all states)
  2. Categories of sensitive PI/sensitive data collected (all states)
  3. Purposes for each category (all states)
  4. Retention period or criteria per category (CA required; best practice all)
  5. Sources of PI (CA required; best practice all)
  6. Categories of third parties receiving PI (all states)
  7. Whether PI is sold or shared (all states)
  8. Whether targeted advertising is conducted (all non-CA states)
  9. Whether profiling is conducted (all non-CA states)
  10. Consumer rights and how to exercise (all states)
  11. Appeal process (VA, CO, CT, TX, OR, MT, KY)
  12. Contact information (all states)
  13. "Do Not Sell or Share" link (CA)
  14. "Limit Sensitive PI" link (CA)
  15. Universal opt-out disclosure (CA, CO, CT, MT)
  16. Last updated date (CA required; best practice all)
  17. Annual metrics (CA, if 10M+ consumers)

Key Regulatory References

  • IAPP US State Comprehensive Privacy Law Comparison Chart (updated quarterly)
  • CPPA Regulations 11 CCR §7001-7102
  • Colorado AG Regulations 4 CCR 904-3
  • Global Privacy Control Specification v1.0

Oregon Consumer Privacy Act (OCPA)

Overview

The Oregon Consumer Privacy Act (OCPA), codified as ORS §646A.570 through §646A.604, was signed into law on July 18, 2023 (SB 619), and became effective July 1, 2024. Oregon is notable for several unique provisions: it applies to nonprofit organizations (unlike most state privacy laws), has specific de-identified data compliance requirements, includes a partial exemption for employee data, and provides a 14-day cure period (the shortest of any state law with a cure period).

Applicability (§646A.572)

The OCPA applies to a person that conducts business in Oregon or provides products or services to Oregon residents AND during a calendar year:

  1. Controls or processes personal data of 100,000 or more Oregon consumers (excluding data processed solely for payment transactions); OR
  2. Controls or processes personal data of 25,000 or more Oregon consumers AND derives 25% or more of annual gross revenue from selling personal data.

Key unique features:

  • Nonprofit applicability: Unlike Virginia, Colorado, Connecticut, and Texas, the OCPA applies to nonprofit organizations
  • No revenue threshold alternative: Like Virginia and Colorado, there is no standalone revenue threshold

Exemptions (§646A.572(2)):

  • State and local government bodies
  • GLBA-covered financial institutions (entity-level)
  • HIPAA covered entities and business associates (entity-level)
  • Data governed by GLBA, HIPAA, FERPA, FCRA, DPPA, COPPA, Farm Credit Act
  • Not exempt: Nonprofit organizations (unique among state privacy laws)

Liberty Commerce Inc. Assessment: Liberty Commerce Inc. processes personal data of approximately 72,000 Oregon consumers and derives 12% of revenue from data sale activities. It does not meet either threshold. However, Liberty Commerce Inc. implements OCPA compliance as part of its multi-state program for operational consistency.

Consumer Rights (§646A.578)

Six Consumer Rights

  1. Right to Access (§646A.578(1)(a)): Confirm processing and access personal data
  2. Right to Correct (§646A.578(1)(b)): Correct inaccuracies
  3. Right to Delete (§646A.578(1)(c)): Delete personal data
  4. Right to Portability (§646A.578(1)(d)): Obtain data in portable format
  5. Right to Opt Out (§646A.578(1)(e)):
    • Targeted advertising
    • Sale of personal data
    • Profiling in furtherance of decisions producing legal or similarly significant effects
  6. Right to Know Third Parties (§646A.578(1)(f)): Obtain a list of specific third parties to whom the controller has disclosed the consumer's personal data

Note: The Right to Know Third Parties is unique to Oregon — most other state laws only require disclosure of categories of third parties, not specific names.

Response Requirements (§646A.580)

  • Respond within 45 days
  • Extension: up to 45 additional days with notice
  • Appeal: controller must respond within 45 days (not 60 like other states)

De-Identified Data Requirements (§646A.574)

Oregon has the most detailed de-identified data requirements of any state privacy law:

Controller Obligations for De-Identified Data

  1. Take reasonable measures to ensure data cannot be associated with a natural person
  2. Publicly commit to maintain and use data only in de-identified form
  3. Contractually obligate recipients to comply with de-identification requirements
  4. Exercise reasonable oversight to monitor compliance with contractual obligations
  5. Take appropriate steps to address any breach of the contractual obligations

Technical Standards

  • Must use technical safeguards to prevent re-identification
  • Must implement organizational safeguards including access controls
  • Must conduct regular assessments of re-identification risk
  • Must delete or destroy data if de-identification can no longer be maintained

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. applies k-anonymity (k=5 minimum) and differential privacy techniques to de-identified datasets. A public commitment statement is posted at privacy.libertycommerce.com/deidentification. All recipients of de-identified data sign agreements prohibiting re-identification attempts. Quarterly re-identification risk assessments are conducted by the data science team.

Employee Data Partial Exemption (§646A.572(4))

Exemption Scope

The OCPA provides a partial exemption for employee data. Personal data processed in the context of employment is exempt from:

  • Consumer rights provisions (§646A.578) — access, correct, delete, portability, opt-out
  • Consumer request processing requirements (§646A.580)

Not Exempt

Employee data is NOT exempt from:

  • Controller obligations (§646A.576) — privacy notice, data minimization, security
  • Processor requirements (§646A.582)
  • De-identified data requirements (§646A.574)
  • Data protection assessment requirements (§646A.584)
  • Sensitive data consent requirements (§646A.576(8))

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. provides a privacy notice to Oregon employees covering all data processing activities. Sensitive employee data (health information for benefits, racial/ethnic data for diversity reporting) is processed only with consent. DPIAs are conducted for employee profiling activities (performance scoring, promotion algorithms).

Nonprofit Applicability

Oregon is unique in applying its privacy law to nonprofit organizations. This has significant implications:

Organization TypeOCPAVCDPACPACTDPATDPSACCPA/CPRA
For-profitYesYesYesYesYesYes
NonprofitYesNoNoNoNoNo

Implications for nonprofits:

  • Must assess applicability against 100,000/25,000 consumer thresholds
  • Must provide consumer rights if applicable
  • Must comply with controller obligations (privacy notice, minimization, security)
  • Must obtain consent for sensitive data processing
  • Must conduct DPIAs for targeted advertising, sale, profiling, and sensitive data

Sensitive Data (§646A.574(14))

Categories

  1. Racial or ethnic origin
  2. Religious beliefs
  3. Mental or physical health diagnosis
  4. Sexual orientation
  5. Citizenship or immigration status
  6. Genetic or biometric data for identification
  7. Personal data of a known child
  8. Precise geolocation data
  9. Transgender or nonbinary status (unique to Oregon)

Note: Oregon is the first state to explicitly include transgender or nonbinary status as a sensitive data category.

Consent Requirement

Processing requires opt-in consent. Consent must be freely given, specific, informed, and unambiguous.

14-Day Cure Period (§646A.600)

Oregon provides a 14-day cure period — the shortest among state privacy laws with cure provisions:

StateCure PeriodDuration
Oregon14 daysPermanent
Virginia30 daysPermanent
Texas30 daysPermanent
Colorado60 daysExpired January 1, 2025
Connecticut60 daysExpired January 1, 2025
CaliforniaNoneEliminated by CPRA

Cure Process

  1. AG provides written notice of alleged violation
  2. Controller has 14 days to cure
  3. If cured and written statement provided: AG may not bring action
  4. If not cured: AG may proceed under Oregon Unlawful Trade Practices Act (ORS §646.607)

Key Regulatory References

  • ORS §646A.570 through §646A.604 (OCPA)
  • ORS §646.607 et seq. (Oregon Unlawful Trade Practices Act — enforcement)
  • NIST Special Publication 800-188 — De-Identification of Personal Information (reference standard)
  • Oregon AG Consumer Privacy Division guidance (as published)

State Privacy Law Applicability Assessment

Overview

Determining which US state privacy laws apply to an organization requires evaluating multiple criteria: revenue thresholds, consumer/data volume thresholds, industry-specific exemptions, entity-type exemptions, and data-type exemptions. This skill provides a systematic assessment framework and Python automation tool for evaluating applicability across all major enacted state privacy laws.

Assessment Framework

Step 1: Geographic Nexus

For each state, determine if the organization has nexus through:

  • Conducting business in the state (physical presence, employees, registered entity)
  • Targeting residents of the state (marketing, advertising, or providing products/services specifically to state residents)
  • Producing products/services consumed by state residents

Most state laws use "conducts business in [state] OR produces products or services targeted to [state] residents" as the nexus requirement.

Step 2: Threshold Assessment

StateThreshold 1Threshold 2Revenue Alternative
California100,000 consumers/households50% revenue from sale/sharing$25,000,000 annual gross revenue
Virginia100,000 consumers25,000 consumers + 50% revenue from saleNone
Colorado100,000 consumers25,000 consumers + revenue/discount from saleNone
Connecticut100,000 consumers (excl. payment)25,000 consumers + 25% revenue from saleNone
TexasNon-SBA small businessN/ANone (no threshold)
Oregon100,000 consumers (excl. payment)25,000 consumers + 25% revenue from saleNone
Montana50,000 consumers (excl. payment)25,000 consumers + 25% revenue from saleNone
Kentucky100,000 consumers25,000 consumers + 50% revenue from saleNone

Step 3: Entity-Level Exemptions

ExemptionCAVACOCTTXORMTKY
GovernmentN/A (for-profit only)ExemptExemptExemptExemptExemptExemptExempt
GLBA financial institutionsData-levelEntity-levelEntity-levelEntity-levelEntity-levelEntity-levelEntity-levelEntity-level
HIPAA covered entitiesData-levelEntity-levelEntity-levelEntity-levelEntity-levelEntity-levelEntity-levelEntity-level
NonprofitsNot exemptExemptExemptExemptExemptNot exemptExemptExempt
Higher educationNot exemptExemptExemptExemptExemptNot exemptExemptExempt
Air carriersNot exemptNot exemptNot exemptNot exemptNot exemptNot exemptExemptNot exempt

Step 4: Data-Level Exemptions

Data that is already governed by certain federal laws may be exempt even if the organization itself is not:

Federal LawFull NameData Type
GLBAGramm-Leach-Bliley Act (15 U.S.C. §6801)Financial data under GLBA privacy rules
HIPAAHealth Insurance Portability and Accountability Act (42 U.S.C. §1320d)Protected health information (PHI)
FERPAFamily Educational Rights and Privacy Act (20 U.S.C. §1232g)Education records
FCRAFair Credit Reporting Act (15 U.S.C. §1681)Consumer credit reports
DPPADriver's Privacy Protection Act (18 U.S.C. §2721)Motor vehicle records
COPPAChildren's Online Privacy Protection Act (15 U.S.C. §6501)Children's data under COPPA
Farm Credit ActFarm Credit Act of 1971 (12 U.S.C. §2001)Farm credit data

California distinction: CCPA/CPRA exempts the data governed by these federal laws, not the entity. A GLBA-covered bank is still subject to CCPA for personal data that falls outside GLBA's scope (e.g., marketing data not related to financial products).

Step 5: Employee Data Assessment

StateEmployee Data Status
CaliforniaFully covered (CPRA removed prior partial exemption)
VirginiaExempt from consumer rights; controller duties apply
ColoradoExempt from consumer rights; controller duties apply
ConnecticutExempt from consumer rights; controller duties apply
TexasExempt from consumer rights; controller duties apply
OregonPartial exemption: Rights exempt; controller duties, DPIAs, sensitive consent apply
MontanaExempt from consumer rights; controller duties apply
KentuckyExempt from consumer rights; controller duties apply

Step 6: SBA Small Business Determination (Texas TDPSA)

The TDPSA is the only state law that uses the SBA small business definition. Key steps:

  1. Identify the organization's primary NAICS code
  2. Look up the SBA size standard for that NAICS code in 13 CFR §121.201
  3. Compare the organization's annual receipts or employee count to the threshold
  4. If the organization qualifies as a small business:
    • Most TDPSA provisions are exempt
    • Prohibition on selling sensitive data without consent still applies (§541.107(b))

Common SBA thresholds for technology/retail companies:

NAICSIndustryRevenue Threshold
454110Electronic shopping$40,000,000
519130Internet publishing and web search portals$47,000,000
518210Data processing and hosting$35,000,000
511210Software publishers$47,000,000
541511Custom computer programming$34,000,000

Liberty Commerce Inc. Assessment Summary

StateConsumersRevenue from SaleApplicableBasis
California320,00012%YESRevenue >$25M + 100K consumers
Virginia145,00012%YES100K+ consumers
Colorado98,00012%YES25K+ with revenue from sale
Connecticut87,00012%BorderlineBelow 100K; below 25% revenue
Texas410,00012%YESNon-SBA small business
Oregon72,00012%NOBelow both thresholds
Montana28,00012%NOBelow both thresholds
Kentucky68,00012%NOBelow both thresholds

Key Regulatory References

  • SBA Size Standards: 13 CFR §121.201
  • GLBA: 15 U.S.C. §6801-6809
  • HIPAA: 42 U.S.C. §1320d et seq.; 45 CFR Parts 160, 164
  • FERPA: 20 U.S.C. §1232g
  • FCRA: 15 U.S.C. §1681 et seq.
  • COPPA: 15 U.S.C. §6501-6506
  • DPPA: 18 U.S.C. §2721-2725

Texas Data Privacy and Security Act (TDPSA)

Overview

The Texas Data Privacy and Security Act (TDPSA), codified as Tex. Bus. & Com. Code §541.001 through §541.203, was signed into law on June 18, 2023 (HB 4), and became effective July 1, 2024. Texas is the largest state by population to enact comprehensive consumer privacy legislation and is notable for having no revenue threshold for applicability — the TDPSA applies to any person that conducts business in Texas or produces products or services consumed by Texas residents, regardless of company size.

The TDPSA also interacts with the existing Texas Capture or Use of Biometric Identifier Act (CUBI), Tex. Bus. & Com. Code §503.001, which provides separate biometric data protections.

Applicability (§541.002)

The TDPSA applies to a person that:

  1. Conducts business in Texas or produces a product or service consumed by Texas residents
  2. Processes or engages in the sale of personal data
  3. Is not a small business as defined by the U.S. Small Business Administration (SBA)

Key feature: No revenue or consumer count threshold. Unlike California ($25M revenue), Virginia (100,000 consumers), or Colorado (100,000 consumers), the TDPSA applies broadly to any non-small business processing personal data of Texas residents.

Small business exemption: Small businesses as defined by SBA size standards are exempt from most provisions but are NOT exempt from the prohibition on selling sensitive data without consent (§541.107(b)).

Additional exemptions (§541.003):

  • State agencies and political subdivisions
  • Financial institutions subject to GLBA (entity-level)
  • Covered entities and business associates under HIPAA (entity-level)
  • Nonprofit organizations
  • Institutions of higher education
  • Electric utilities (ERCOT-related)

Liberty Commerce Inc. Assessment: Liberty Commerce Inc. is not an SBA-defined small business (annual revenue: $48M, 320 employees). It conducts business in Texas and processes personal data of Texas residents. The TDPSA applies.

Consumer Rights (§541.051)

Five Consumer Rights

  1. Right to Access (§541.051(1)): Confirm processing and access personal data
  2. Right to Correct (§541.051(2)): Correct inaccuracies
  3. Right to Delete (§541.051(3)): Delete personal data
  4. Right to Portability (§541.051(4)): Obtain data in portable, readily usable format
  5. Right to Opt Out (§541.051(5)): Opt out of:
    • Targeted advertising
    • Sale of personal data
    • Profiling in furtherance of decisions producing legal or similarly significant effects

Response Requirements (§541.055)

  • Respond within 45 days
  • Extension: up to 45 additional days with notice
  • At least one free response per 12 months per right
  • Appeal process: respond within 60 days

Sensitive Data (§541.001(29), §541.101(b)(5))

Categories

  1. Racial or ethnic origin
  2. Religious beliefs
  3. Mental or physical health diagnosis
  4. Sexual orientation
  5. Citizenship or immigration status
  6. Genetic or biometric data processed for identification
  7. Personal data of a known child
  8. Precise geolocation data

Consent Requirements

Processing sensitive data requires opt-in consent. For small businesses: selling sensitive data without consent is prohibited regardless of SBA size.

Data Broker Provisions (§541.201-§541.203)

The TDPSA includes specific data broker requirements:

Definition (§541.201)

A "data broker" is a business entity whose principal source of revenue is derived from collecting, processing, or transferring personal data the entity did not directly collect from consumers.

Registration Requirement (§541.202)

Data brokers must register with the Texas Secretary of State and pay a registration fee. Registration must include:

  • Legal name and primary business address
  • Contact information for privacy inquiries
  • Description of data collection practices
  • Whether the broker has experienced a data breach in the preceding 3 years

Consumer Rights for Data Brokers (§541.203)

Data brokers must provide:

  • Clear and conspicuous disclosure that they are a data broker
  • A mechanism for consumers to opt out of data collection
  • Instructions for submitting access and deletion requests

Liberty Commerce Inc. Assessment: Liberty Commerce Inc. is not a data broker — its principal revenue derives from e-commerce, not from collecting/processing/transferring personal data. The data broker provisions do not apply.

Biometric Data: CUBI Interaction

Texas Capture or Use of Biometric Identifier Act (CUBI) — Tex. Bus. & Com. Code §503.001

CUBI, enacted in 2009, provides additional protections for biometric identifiers:

  • Defines biometric identifier: retina or iris scan, fingerprint, voiceprint, record of hand or face geometry
  • Requires informed consent before capture
  • Prohibits sale, lease, or disclosure without consent
  • Requires reasonable care in storage, transmission, and protection
  • Requires destruction within a reasonable time (when purpose fulfilled or within 3 years of last interaction)
  • No private right of action — AG enforcement only
  • Penalties: Up to $25,000 per violation

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. does not capture biometric identifiers from Texas consumers. Device-side biometric authentication (Face ID, fingerprint) processes locally and does not transmit biometric data to Liberty Commerce Inc. servers.

Controller Obligations (§541.101)

  1. Purpose limitation (§541.101(a)(1)): Limit processing to adequate, relevant, and reasonably necessary purposes
  2. Data minimization (§541.101(a)(2)): Do not process beyond what is reasonably necessary
  3. Data security (§541.101(a)(3)): Appropriate technical and organizational measures
  4. Non-discrimination (§541.101(a)(4)): No processing in violation of antidiscrimination laws
  5. Sensitive data consent (§541.101(b)(5)): Obtain consent before processing

Privacy Notice (§541.101(b))

Must include:

  • Categories of personal data processed
  • Purposes for processing
  • Consumer rights exercise instructions
  • Categories shared with third parties
  • Categories of third parties
  • Contact information

Data Protection Assessments (§541.103)

Required for:

  • Targeted advertising
  • Sale of personal data
  • Profiling with legal or significant effects
  • Sensitive data processing
  • High-risk processing activities

Enforcement (§541.151-§541.155)

Attorney General Authority

  • Exclusive enforcement — no private right of action (except CUBI has AG enforcement only)
  • May investigate and bring action under the Deceptive Trade Practices — Consumer Protection Act (Tex. Bus. & Com. Code §17.41 et seq.)

30-Day Cure Period (§541.154)

  • AG must provide 30-day written notice of alleged violation
  • If cured within 30 days and express written statement of cure provided: AG may not bring action
  • Unlike CPRA: Cure period is permanent, not sunsetting

Penalties

  • Civil penalties up to $7,500 per violation
  • Injunctive relief
  • Reasonable attorney fees and investigation costs

Key Regulatory References

  • Tex. Bus. & Com. Code §541.001-§541.203 (TDPSA)
  • Tex. Bus. & Com. Code §503.001 (CUBI — biometric identifiers)
  • Tex. Bus. & Com. Code §17.41 et seq. (DTPA — enforcement framework)
  • SBA Size Standards (13 CFR §121.201) — small business determination
  • Texas Secretary of State — Data broker registration

Universal Opt-Out Mechanism Implementation

Overview

A universal opt-out mechanism is a browser or device-level signal that communicates a consumer's privacy preferences to websites and online services. The Global Privacy Control (GPC) is the leading universal opt-out mechanism, supported by major browsers (Firefox, Brave, DuckDuckGo) and browser extensions (Privacy Badger, Disconnect). Multiple US state privacy laws now require businesses to recognize and honor these signals.

GPC is defined in the Global Privacy Control specification (published by the GPC project), transmitted via the Sec-GPC: 1 HTTP header and the navigator.globalPrivacyControl JavaScript API.

State-by-State Requirements

StateLawSignal RequiredEffective DateScope
CaliforniaCCPA/CPRAYesJan 1, 2023Sale + Sharing
ColoradoCPAYesJul 1, 2024Targeted ads + Sale
ConnecticutCTDPAYesJan 1, 2025Targeted ads + Sale
MontanaMTDPAYesOct 1, 2025Targeted ads + Sale
TexasTDPSANot requiredN/AN/A
VirginiaVCDPANot requiredN/AN/A
OregonOCPANot requiredN/AN/A
KentuckyKPPANot requiredN/AN/A

GPC Technical Specification

HTTP Header

Sec-GPC: 1

The Sec-GPC header is a structured header with a bare item value of 1 (true) or absent (no preference expressed). The Sec- prefix indicates it is a fetch metadata header set by the browser, not by JavaScript.

JavaScript API

navigator.globalPrivacyControl  // boolean: true or undefined

The navigator.globalPrivacyControl property returns true if the user has enabled GPC in their browser or extension, or undefined if GPC is not active.

Detection Code

function detectGPC() {
    // Check JavaScript API
    const jsGPC = navigator.globalPrivacyControl === true;

    // The HTTP header is checked server-side
    // This function covers client-side detection only

    return {
        gpcEnabled: jsGPC,
        timestamp: new Date().toISOString(),
        userAgent: navigator.userAgent,
    };
}

Server-Side Detection (Node.js/Express example)

function checkGPCHeader(req) {
    const gpcHeader = req.headers['sec-gpc'];
    return gpcHeader === '1';
}

app.use((req, res, next) => {
    if (checkGPCHeader(req)) {
        req.gpcOptOut = true;
        // Apply opt-out before rendering page
        res.locals.suppressThirdPartyTags = true;
        res.locals.suppressCrossSiteBehavioralAds = true;
    }
    next();
});

Implementation Architecture

Layer 1: Signal Detection

HTTP Request Arrives
  │
  ├─► Server-Side Check
  │     └─ Parse Sec-GPC header from request
  │
  ├─► Client-Side Check (for SPAs)
  │     └─ Read navigator.globalPrivacyControl
  │
  └─► Combined Result
        ├─ GPC detected = true → Apply opt-out
        └─ GPC not detected → Normal processing

Layer 2: Scope Determination

StateSale Opt-OutSharing Opt-OutTargeted Ads Opt-OutProfiling Opt-Out
CaliforniaYesYesImplied (sharing = cross-context behavioral ads)No (separate)
ColoradoYesN/AYesNo (separate)
ConnecticutYesN/AYesNo (separate)
MontanaYesN/AYesNo (separate)

Layer 3: Consumer Identity Resolution

Authenticated Consumer (logged in):

  • Associate GPC opt-out with consumer account
  • Set persistent flag: sale_opt_out = true, targeted_ads_opt_out = true
  • Override any prior opt-in (most recent preference per CO Rule 5.13)
  • Persist across sessions and devices (account-level)

Unauthenticated Consumer (not logged in):

  • Apply opt-out to current browsing session
  • Set first-party session cookie to maintain state during session
  • Apply on each new session when GPC signal is present
  • Do not require identity verification

Layer 4: Enforcement

Upon detecting GPC signal, the system must:

  1. Suppress third-party advertising tags before page render:

    • AdReach Network pixel — BLOCKED
    • Cross-context behavioral advertising tags — BLOCKED
    • Retargeting/remarketing pixels — BLOCKED
    • Social media tracking widgets — BLOCKED
  2. Allow first-party processing:

    • First-party analytics (where data stays with controller or service provider under contract)
    • Essential functionality cookies (session, cart, security)
    • Contextual advertising (based on current page content, not behavioral profile)
  3. Update server-side systems:

    • Data sharing pipeline: suppress outbound feeds to third-party ad partners
    • CMP state: update consent management platform to reflect opt-out
    • Consumer profile: flag account (if authenticated) for persistent opt-out

Compliance Rules by State

California (CPPA Regulations §7025)

  • §7025(a): Must process opt-out preference signals as valid opt-out requests
  • §7025(b): Two-step opt-out process prohibited
  • §7025(c): Must not require consumer to verify identity
  • §7025(d): Must not display pop-up or notification questioning the signal
  • §7025(e): If consumer not identifiable, apply to browser/device
  • §7025(f): If authenticated user has different prior setting, GPC takes precedence as most recent expression
  • Scope: Sale AND sharing (cross-context behavioral advertising)

Colorado (4 CCR 904-3, Rule 5.11)

  • Rule 5.10: Must recognize universal opt-out mechanisms
  • Rule 5.11: Must not display pop-up, interstitial, or other mechanism questioning signal
  • Rule 5.12: Authenticated = account-level; unauthenticated = session-level
  • Rule 5.13: Most recently expressed preference prevails on conflict
  • Rule 5.14: AG biennial review of recognized mechanisms
  • Scope: Targeted advertising AND sale
  • Requirement: Mechanism must be affirmatively selected by consumer (not default)

Connecticut (§42-520(a)(6))

  • Must recognize universal opt-out mechanisms starting January 1, 2025
  • Same principles as Colorado: no verification, no pop-ups
  • Scope: Targeted advertising AND sale

Montana (§30-14-2808(3))

  • Must recognize universal opt-out mechanisms starting October 1, 2025
  • Same principles as Colorado and Connecticut
  • Scope: Targeted advertising AND sale

Testing Protocol

Test 1: GPC Signal Detection

  • Install GPC-enabled browser (Brave, Firefox with GPC extension)
  • Visit website
  • Verify server logs show Sec-GPC: 1 header detected
  • Verify client-side navigator.globalPrivacyControl === true

Test 2: Tag Suppression

  • With GPC enabled: verify third-party advertising tags do NOT fire
  • Without GPC: verify third-party advertising tags fire normally
  • Inspect network requests to confirm suppression

Test 3: Authenticated vs. Unauthenticated

  • Visit with GPC while logged out: verify session-level opt-out
  • Log in with GPC: verify account-level opt-out persists
  • Log in without GPC after prior GPC opt-out: verify prior opt-out persists (account-level)

Test 4: No Pop-Up or Interstitial

  • Visit with GPC: verify no pop-up asks to confirm or modify signal
  • Verify consent banner does not override or question GPC signal

Test 5: Conflict Resolution

  • Set account preference to opt-in to sale/targeted ads
  • Visit with GPC enabled
  • Verify GPC takes precedence (opt-out applied)

Liberty Commerce Inc. Implementation

Technology stack: Consent management platform (CMP) with GPC signal handler, tag management system (TMS) with server-side control, privacy operations dashboard.

Architecture:

  1. Edge proxy detects Sec-GPC: 1 header on incoming requests
  2. Request metadata includes gpc_opt_out: true flag
  3. TMS evaluates flag before injecting any tags
  4. CMP state updated for session/account
  5. Server-side data sharing pipeline checks flag before transmitting to third parties
  6. Compliance dashboard reports GPC detection rates and opt-out volume

Key Regulatory References

  • CPPA Regulations §7025 — Opt-out preference signals
  • Colorado AG Regulations 4 CCR 904-3, Rule 5 — Universal opt-out mechanism
  • Conn. Gen. Stat. §42-520(a)(6) — Universal opt-out recognition
  • MCA §30-14-2808(3) — Universal opt-out recognition
  • Global Privacy Control Specification v1.0 (globalprivacycontrol.org)
  • W3C Community Group: GPC specification
  • In re Sephora Inc. (2022) — $1.2M settlement for failure to honor GPC

Virginia Consumer Data Protection Act (VCDPA)

Overview

The Virginia Consumer Data Protection Act (VCDPA), codified as Va. Code §59.1-575 through §59.1-585, was signed into law on March 2, 2021, and became effective on January 1, 2023. Virginia was the second state to enact comprehensive consumer privacy legislation after California. The VCDPA follows the controller-processor model used in the GDPR rather than the business-service provider framework of the CCPA.

The VCDPA is enforced exclusively by the Virginia Attorney General — there is no private right of action and no dedicated privacy enforcement agency. The AG must provide a 30-day cure period before initiating enforcement action under §59.1-584.

Applicability (§59.1-576)

The VCDPA applies to persons that conduct business in Virginia or produce products or services targeted to Virginia residents AND:

  1. During a calendar year, control or process personal data of at least 100,000 Virginia consumers; OR
  2. Control or process personal data of at least 25,000 Virginia consumers AND derive over 50% of gross revenue from the sale of personal data.

Exemptions (§59.1-576(B)):

  • Virginia governmental entities
  • Financial institutions subject to GLBA (Title V of Gramm-Leach-Bliley Act, 15 U.S.C. §6801 et seq.)
  • Covered entities and business associates under HIPAA (42 U.S.C. §1320d et seq.)
  • Nonprofit organizations
  • Institutions of higher education
  • Data subject to GLBA, HIPAA, FERPA, FCRA, DPPA, or Farm Credit Act

Liberty Commerce Inc. Assessment: Liberty Commerce Inc. processes personal data of approximately 145,000 Virginia consumers through its e-commerce platform. It meets threshold (1) and is subject to the VCDPA.

Five Consumer Rights (§59.1-577)

1. Right to Access (§59.1-577(A)(1))

Consumers have the right to confirm whether a controller is processing their personal data and to access such personal data.

Liberty Commerce Inc. Implementation: Consumers access their data profile through the privacy portal at privacy.libertycommerce.com/virginia. The system generates a comprehensive data access report including all categories of personal data processed, sources, purposes, and any third-party recipients.

2. Right to Correct (§59.1-577(A)(2))

Consumers have the right to correct inaccuracies in their personal data, taking into account the nature of the personal data and the purposes of the processing.

3. Right to Delete (§59.1-577(A)(3))

Consumers have the right to delete personal data provided by or obtained about the consumer.

Liberty Commerce Inc. Implementation: Deletion requests propagate to all processors within 30 days. Retained data for legal compliance is documented with specific legal basis.

4. Right to Data Portability (§59.1-577(A)(4))

Consumers have the right to obtain a copy of their personal data previously provided to the controller in a portable and, to the extent technically feasible, readily usable format that allows the consumer to transmit the data to another controller without hindrance.

5. Right to Opt Out (§59.1-577(A)(5))

Consumers have the right to opt out of:

  • Targeted advertising — displaying advertisements to a consumer based on personal data obtained from the consumer's activities across nonaffiliated websites, applications, or online services
  • Sale of personal data — exchange of personal data for monetary consideration
  • Profiling — in furtherance of decisions that produce legal or similarly significant effects concerning the consumer

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. provides a unified opt-out mechanism on its Virginia privacy page. Consumers can opt out of each category independently. GPC signals are recognized and honored as opt-out of targeted advertising and sale, consistent with multi-state compliance.

Sensitive Data Processing (§59.1-578(A)(5))

The VCDPA requires opt-in consent before processing sensitive data. This is a stricter standard than CCPA/CPRA (which allows collection without consent but provides a limit right).

Sensitive Data Categories (§59.1-575)

  1. Personal data revealing racial or ethnic origin
  2. Religious beliefs
  3. Mental or physical health diagnosis
  4. Sexual orientation
  5. Citizenship or immigration status
  6. Genetic or biometric data processed for identification
  7. Personal data collected from a known child
  8. Precise geolocation data (within 1,750 feet / 533 meters)

Key difference from CPRA: VCDPA requires prior consent; CPRA permits collection with a post-collection limit right.

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. obtains opt-in consent before processing sensitive data from Virginia consumers. The consent mechanism presents each sensitive data category separately with clear affirmative action (unticked checkbox). Consent records include: consumer ID, category, consent text version, timestamp, and mechanism.

Controller Obligations (§59.1-578)

Data Minimization (§59.1-578(A)(1))

Limit collection to what is adequate, relevant, and reasonably necessary in relation to the purposes.

Purpose Limitation (§59.1-578(A)(2))

Do not process personal data for purposes not reasonably necessary to or compatible with the disclosed purposes.

Security (§59.1-578(A)(3))

Establish, implement, and maintain reasonable administrative, technical, and physical data security practices appropriate to the volume and nature of the personal data at issue.

Non-Discrimination (§59.1-578(A)(4))

Do not process personal data in violation of state and federal antidiscrimination laws.

Consent for Sensitive Data (§59.1-578(A)(5))

Obtain consent before processing sensitive data.

Privacy Notice (§59.1-578(B))

Provide a reasonably accessible, clear, and meaningful privacy notice that includes:

  • Categories of personal data processed
  • Purpose for processing
  • How consumers may exercise their rights (including appeal)
  • Categories of personal data shared with third parties
  • Categories of third parties with whom data is shared
  • Contact information for the controller

Response Timeline (§59.1-578(C))

  • Respond within 45 days of receipt
  • Extension: Up to 45 additional days (90 total) with notice to consumer

Data Protection Impact Assessments (§59.1-580)

Controllers must conduct and document DPIAs for processing activities that present a heightened risk of harm to consumers. Required for:

  1. Targeted advertising processing
  2. Sale of personal data
  3. Profiling where it presents a reasonably foreseeable risk of:
    • Unfair or deceptive treatment or unlawful disparate impact
    • Financial, physical, or reputational injury
    • Physical intrusion or surveillance creating offense to a reasonable person
    • Other substantial injury
  4. Sensitive data processing
  5. Any processing activity involving personal data that presents a heightened risk of harm

DPIA Content Requirements

  • Identify and weigh the benefits from the processing against potential risks
  • Consider use of de-identified data
  • Factor in the reasonable expectations of consumers
  • Consider the context of processing and the relationship between controller and consumer

Liberty Commerce Inc. Implementation: Liberty Commerce Inc. has completed DPIAs for:

  • Targeted advertising program (AdReach Network partnership)
  • Marketplace seller data sale to analytics partners
  • Consumer credit scoring for buy-now-pay-later feature
  • Precise geolocation processing for delivery optimization
  • Sensitive data processing (optional diversity surveys)

Each DPIA is reviewed annually and upon material changes. DPIAs are retained for five years.

Processor Requirements (§59.1-579)

Processing must be governed by a contract between the controller and processor that includes:

  • Instructions for processing data
  • Nature and purpose of processing
  • Type of data subject to processing and duration
  • Rights and obligations of both parties
  • Requirement that the processor ensure persons processing data are subject to a duty of confidentiality
  • Requirement to delete or return all personal data at controller's direction upon end of services
  • Requirement to make available information to demonstrate compliance (upon reasonable request)
  • Requirement to allow and cooperate with reasonable assessments by the controller or the controller's designated assessor
  • Requirement that the processor engage sub-processors only pursuant to a written contract with obligations no less protective than the controller-processor contract

Enforcement (§59.1-584)

Attorney General Authority

  • Exclusive enforcement authority under the VCDPA
  • May investigate potential violations
  • May issue civil investigative demands (CIDs)
  • Must provide 30-day written notice of alleged violations before bringing action

30-Day Cure Period

  • Controller or processor has 30 days after receiving AG notice to cure the alleged violation
  • If cured: AG may not bring action for that violation
  • If not cured: AG may bring action under the Virginia Consumer Protection Act (§59.1-196 et seq.)

Penalties

  • Civil penalties up to $7,500 per violation
  • Reasonable expenses including attorney fees
  • Injunctive relief

Key Regulatory References

  • Va. Code §59.1-575 — Definitions
  • Va. Code §59.1-576 — Applicability and exemptions
  • Va. Code §59.1-577 — Consumer rights
  • Va. Code §59.1-578 — Controller obligations
  • Va. Code §59.1-579 — Processor requirements
  • Va. Code §59.1-580 — Data protection impact assessments
  • Va. Code §59.1-581 — De-identified data
  • Va. Code §59.1-582 — Limitations
  • Va. Code §59.1-583 — Consumer rights request procedures
  • Va. Code §59.1-584 — Enforcement, 30-day cure period
  • Va. Code §59.1-585 — Relation to other laws

Sponsors

Details

Marketplace
mukul975/Privacy-Data-Protection-Skills
Source
plugins/us-state-privacy-skills
Author
Mahipal
Category
Compliance
License
Apache-2.0
Keywords
ccpa, cpra, us-privacy, state-laws, vcdpa, cpa

More from mukul975/Privacy-Data-Protection-Skills

All 21