Virginia VCDPA Compliance Guide | Blue Frog Docs

Virginia VCDPA Compliance Guide

Comprehensive guide to the Virginia Consumer Data Protection Act (VCDPA), including requirements, enforcement, and implementation best practices.

Overview

The Virginia Consumer Data Protection Act (VCDPA) was the second comprehensive state privacy law enacted in the United States, following California's CCPA. It establishes data protection rights for Virginia residents and imposes obligations on businesses that process their personal data.

Full Name and Description

Virginia Consumer Data Protection Act (VCDPA): Enacted on March 2, 2021, and effective January 1, 2023, the VCDPA grants Virginia consumers rights over their personal data, including access, correction, deletion, and opt-out rights, while establishing controller and processor obligations for data protection.

Enforcement Date

  • Effective Date: January 1, 2023
  • Full Enforcement: January 1, 2023 (no grace period for compliance)

Governing Body

  • Virginia Attorney General: Exclusive enforcement authority
  • No Private Right of Action: Consumers cannot directly sue for VCDPA violations

Primary Purpose

The VCDPA aims to:

  • Provide Virginia residents control over their personal data
  • Establish clear obligations for data controllers and processors
  • Create a balanced framework that protects consumers while enabling business innovation
  • Require transparency in data collection and processing practices

Applicability

Who Needs to Comply?

The VCDPA applies to entities that conduct business in Virginia or produce products/services targeted to Virginia residents AND meet one of the following thresholds:

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

Key Exemptions

The VCDPA provides several entity-level exemptions:

  • Government entities: State and local government bodies
  • Financial institutions: Entities subject to GLBA
  • HIPAA-covered entities: Healthcare organizations and business associates
  • Nonprofits: Organizations exempt from federal income tax
  • Higher education institutions: Colleges and universities
  • Certain data types: Employment data, B2B contact information

Industry-Specific Considerations

Industry VCDPA Status Notes
Retail/E-commerce Covered Standard compliance required
Ad Tech Covered Opt-out requirements for targeted ads
SaaS Covered (usually as processor) Data processing agreements required
Healthcare Exempt (if HIPAA-covered) But marketing data may still apply
Financial Services Exempt (if GLBA-covered) Consumer banking typically exempt
Nonprofits Exempt Complete exemption

What the VCDPA Governs

Types of Data Covered

Personal Data - Any information linked or reasonably linkable to an identified or identifiable natural person. Does not include de-identified data or publicly available information.

Sensitive Data (requires opt-in consent):

  • Racial or ethnic origin
  • Religious beliefs
  • Mental or physical health diagnosis
  • Sexual orientation
  • Citizenship or immigration status
  • Genetic or biometric data
  • Personal data from a known child
  • Precise geolocation data

Consumer Rights Under VCDPA

Virginia residents have the following rights:

  1. Right to Access: Know whether a controller processes their personal data and access that data
  2. Right to Correct: Request correction of inaccuracies
  3. Right to Delete: Request deletion of personal data
  4. Right to Data Portability: Obtain a copy of data in a portable format
  5. Right to Opt-Out: Decline targeted advertising, sale of personal data, or profiling

Key Definitions

  • Controller: Entity that determines the purpose and means of processing personal data
  • Processor: Entity that processes personal data on behalf of a controller
  • Sale: Exchange of personal data for monetary consideration
  • Targeted Advertising: Displaying ads based on personal data obtained from activities across nonaffiliated websites

Compliance Requirements

Key Obligations for Controllers

1. Privacy Notice Requirements

Controllers must provide clear, accessible privacy notices that include:

  • Categories of personal data processed
  • Purpose of processing
  • How consumers can exercise rights
  • Categories of personal data shared with third parties
  • Categories of third parties with whom data is shared

2. Data Processing Limitations

  • Collect only personal data adequate, relevant, and reasonably necessary for disclosed purposes
  • Cannot process personal data for purposes incompatible with disclosed purposes without consent
  • Establish and maintain reasonable security practices

3. Consent Requirements

  • Opt-in consent required for processing sensitive data
  • Opt-out mechanism required for sale of personal data and targeted advertising
  • Consent must be freely given, specific, informed, and unambiguous

4. Consumer Request Handling

  • Respond to consumer requests within 45 days
  • One extension of 45 days permitted with notice
  • Authenticate consumer identity before fulfilling requests
  • Free of charge (reasonable fee permitted for repetitive requests)

Technical and Operational Requirements

Data Protection Assessments are required for:

  • Processing for targeted advertising
  • Sale of personal data
  • Processing for profiling with legal or significant effects
  • Processing sensitive data
  • Any processing presenting heightened risk of harm

Data Processing Agreements must be established between controllers and processors, including:

  • Instructions for processing
  • Nature and purpose of processing
  • Type of data and duration of processing
  • Rights and obligations of both parties

Consequences of Non-Compliance

Enforcement Process

The Virginia Attorney General has exclusive enforcement authority:

  1. Investigation: AG can investigate potential violations
  2. Notice of Violation: AG provides written notice of alleged violations
  3. Cure Period: 30-day opportunity to cure violations (until January 1, 2025)
  4. Enforcement Action: Civil action if violation not cured

Penalties and Fines

  • Up to $7,500 per violation
  • Investigative costs and attorney fees may be recovered
  • Injunctive relief may be ordered

No Private Right of Action

Unlike California's CCPA, the VCDPA does not grant consumers the right to sue directly for violations. Enforcement is exclusively through the Attorney General.

Business Impact

  • Reputational damage from public enforcement actions
  • Operational disruption from required compliance changes
  • Resource allocation for remediation efforts
  • Increased scrutiny in other jurisdictions

Why the VCDPA Exists

Historical Background

  • 2019-2020: California's CCPA took effect, demonstrating consumer privacy legislation was viable
  • March 2, 2021: Virginia became the second state to pass comprehensive privacy legislation
  • January 1, 2023: VCDPA took effect, establishing Virginia as a privacy leader
  • Business-Friendly Design: Intentionally structured to be more predictable for businesses than CCPA

Comparison with Other Laws

Feature VCDPA CCPA/CPRA GDPR
Opt-In for Sensitive Data Yes Yes (CPRA) Yes
Private Right of Action No Limited Yes
Cure Period 30 days None (CPRA) None
Revenue Threshold 50% from data sales 50% from data sales N/A
Data Volume Threshold 100K consumers 100K households N/A
Nonprofit Exemption Yes No Limited

Global Influence

The VCDPA served as a model for subsequent state privacy laws, including those in Colorado, Connecticut, and Utah. Its balanced approach influenced the "Virginia model" that many states have adopted.


Implementation & Best Practices

How to Become Compliant

Step 1: Data Inventory and Mapping

  • Identify all personal data collected from Virginia consumers
  • Map data flows between systems and third parties
  • Classify data as personal or sensitive
  • Document processing purposes

Step 2: Update Privacy Policies

  • Include all required disclosures
  • Clearly explain consumer rights
  • Provide opt-out mechanisms for sale and targeted advertising
  • Describe data retention practices

Step 3: Implement Consumer Rights Infrastructure

  • Create request intake mechanisms (web forms, email, phone)
  • Develop identity verification procedures
  • Establish response workflows and timelines
  • Train customer service and privacy teams

Step 4: Sensitive Data Handling

  • Implement opt-in consent mechanisms
  • Separate sensitive data processing from general data processing
  • Review necessity of sensitive data collection

Step 5: Vendor Management

  • Inventory all data processors
  • Update contracts with required DPA terms
  • Establish processor oversight procedures
  • Conduct due diligence on processor security practices

Ongoing Compliance Maintenance

  • Annual Data Protection Assessments for high-risk processing activities
  • Regular Privacy Notice Reviews to reflect current practices
  • Employee Training on privacy requirements and procedures
  • Consumer Request Audits to ensure timely responses
  • Vendor Compliance Monitoring for processor adherence

Additional Resources

Official Documentation

Industry Resources

  • IAPP Virginia Privacy Law Resource Center
  • National Law Review VCDPA Analysis
  • OneTrust VCDPA Compliance Toolkit

Comparison Guides

  • VCDPA vs. CCPA Comparison
  • State Privacy Law Tracker
  • Multi-State Compliance Frameworks


Conclusion

The Virginia Consumer Data Protection Act represents a significant milestone in U.S. privacy legislation, establishing a balanced framework that has influenced subsequent state laws. By following the "controller-processor" model familiar from GDPR while adapting it for American business practices, Virginia created a compliance path that many organizations find more predictable than California's approach.

Businesses processing Virginia consumer data should prioritize data mapping, privacy notice updates, and consumer rights infrastructure while taking advantage of the law's entity-level exemptions where applicable.

// SYS.FOOTER