A Virginia resident visits your site, uses your content, and at some point decides to exercise the rights the law guarantees them. They want to know what you have on them. They want to correct an inaccuracy. They want you to stop using their data for ads.
This page covers one piece of the picture. For the full scope of the VCDPA — who must comply, the thresholds, the consumer rights and the penalties — start with our complete guide to the VCDPA and cookies.
What happens from that point on?
The Virginia Consumer Data Protection Act (VCDPA, Va. Code § 59.1-575 et seq.), in effect since January 1, 2023, defines exactly what must happen: the channel to receive the request, the deadline to respond, the appeal process in case of denial, and what happens when the business does not comply.
This article covers all of it.
DSAR stands for Data Subject Access Request. In practice, it is any formal request made by a consumer to exercise the rights the law grants them over their own data.
This includes asking to see what you collected, correcting incorrect information, requesting deletion of their data, asking for a portable copy, refusing the use of their data for targeted advertising, or contesting a decision you made about a previous request.
If you are already familiar with the GDPR, the DSAR framework is familiar. The VCDPA follows the same logic: the consumer needs a functional channel to exercise the rights the law guarantees.
Under Va. Code § 59.1-577 A, Virginia residents have five main rights:
The consumer can request confirmation that the business processes their data and obtain a copy of the personal data the business holds, under Va. Code § 59.1-577 A, 1.
The response must be provided in an accessible and comprehensible format.
The consumer can request correction of inaccuracies in personal data, taking into account the nature of the data and the purposes of processing, under Va. Code § 59.1-577 A, 2.
This covers any outdated, incomplete, or incorrect data. The business cannot ignore this request.
The consumer can request deletion of data they provided or that was obtained about them, under Va. Code § 59.1-577 A, 3.
There is a valid alternative in the VCDPA that does not exist in other laws: if the business obtained data from a source other than the consumer, it can fulfill the deletion request in two ways. It can delete the data outright, or it can retain the minimum data necessary to ensure the consumer's personal data remains deleted from active records and is not used for any other purpose (Va. Code § 59.1-577 B, 5).
The consumer can obtain a copy of their data in a portable and, where technically feasible, readily usable format, when processing is carried out by automated means, under Va. Code § 59.1-577 A, 4.
This makes it easier to transfer data to another controller.
The consumer can refuse the processing of their data for three specific purposes (Va. Code § 59.1-577 A, 5):
Targeted advertising (ads based on activities across non-affiliated websites over time).
Sale of personal data to third parties.
Profiling in furtherance of decisions that produce legal or similarly significant effects concerning the consumer (such as access to credit, housing, insurance, employment, or healthcare services).
Under Va. Code § 59.1-577 C, if the business denies a request, the consumer has the right to appeal the decision.
The appeal process must:
Be conspicuously available and easy to find.
Be comparable to the original request submission process.
Result in a written response within 60 days, including the decision and the reasoning.
If the appeal is denied, the business must inform the consumer about how to contact the Virginia Attorney General to file a complaint. Va. Code § 59.1-577 C specifies that, if available, the mechanism to contact the Attorney General should be online.
The VCDPA is direct on deadlines.
45 days from receipt of an authenticated request (Va. Code § 59.1-577 B, 1).
The deadline can be extended by another 45 days when reasonably necessary, considering complexity and volume of requests, as long as the consumer is notified within the initial period with the reason for the extension.
60 days to respond to appeals (Va. Code § 59.1-577 C).
These deadlines start when the request is received and authenticated. If additional information is needed to verify the consumer's identity, the deadline is paused until authentication is completed.
Va. Code § 59.1-577 B uses the term "receipt of the request." For deadline purposes, the request is received when the business has the minimum information needed to process it.
The identity verification process can influence this marker. If the business requests additional information to authenticate the consumer, the deadline is paused until authentication is completed, under Va. Code § 59.1-577 B, 4.
This is why the verification process must be agile, proportionate to the type of data involved, and clearly described in the submission channel.
Under Va. Code § 59.1-578 E, the controller must establish and describe in the Privacy Policy at least one secure and reliable means for consumers to submit rights requests.
This means must:
Consider how consumers normally interact with the controller.
Ensure secure and reliable communication.
Allow the controller to authenticate the consumer's identity.
Not require the consumer to create a new account. The business may require use of an existing account, but cannot force the user to register a new one just to exercise a legal right.
A well-structured Privacy Portal offers:
A request submission form with clear categories (access, correction, deletion, portability, opt-out).
A proportionate and non-discriminatory identity verification process.
Automatic receipt confirmation with a tracking reference number.
A log of each request, action taken, and response sent.
An appeal channel for denied cases.
The cookie consent on the site and the Privacy Portal must be integrated so that consumer preferences are reflected in real time in the business's operational systems.
The VCDPA requires the controller to authenticate the consumer's identity using commercially reasonable efforts, under Va. Code § 59.1-577 B, 4.
If authentication is not possible with commercially reasonable efforts, the business is not required to fulfill the request, but may ask for additional information that is reasonably necessary.
In practice, this means:
For low-risk data: an email confirmation may be sufficient.
For sensitive data or higher-risk situations: a second verification factor may be justified.
What is never acceptable: requiring physical ID documents for access to simple browsing data, creating deliberately burdensome processes to discourage requests, or denying requests based on impossible authentication when simpler methods are available.
Under Va. Code § 59.1-577 B, 3, request processing is free of charge up to twice per year per consumer.
This is an important point of difference from other state laws. The NHDPA, for example, provides free service only once per year. The VCDPA guarantees twice.
From the third request within the same 12-month period, the business may charge a reasonable fee or decline if the request is manifestly unfounded, excessive, or repetitive. The burden of demonstrating the excessive nature lies with the business.
Receive and authenticate the data subject.
Locate all personal data the business holds about this consumer across all systems.
Prepare a copy in a readable and accessible format.
Include in the response: categories of data, purposes of processing, third parties with whom the data was shared.
Send the response within the 45-day deadline.
An up-to-date data inventory is what makes this process viable at scale.
Receive and authenticate.
Identify which data is inaccurate and in which systems it is stored.
Correct in primary systems and, where applicable, notify third parties that received the data so they can also make the correction on their side.
Confirm to the consumer that the correction was made.
Receive and authenticate.
Check whether a legal exception exists that allows retaining the data (legal obligation, judicial defense, protected purpose).
If no exception: delete from active systems. For data obtained from third parties, there is the option of retaining the minimum necessary to ensure the data remains deleted from active records (Va. Code § 59.1-577 B, 5).
Notify third parties that received the data to also delete it where applicable.
Confirm to the consumer what was deleted and, if any partial retention is justified, explain the legal basis.
Receive and authenticate.
Generate a file with the consumer's data in a portable and machine-readable format, such as JSON or CSV.
Deliver it to the consumer securely within the deadline.
The opt-out of targeted advertising, data sale, or profiling with significant effects must result in the effective cessation of processing for those purposes.
The VCDPA does not specify a separate cessation deadline, unlike the NHDPA which has a specific 15-day period. The legal standard is "without undue delay" within the general 45-day response period. In practice, well-configured systems process opt-outs in real time or within a few hours.
A consent management platform integrated with the business's systems automates this workflow.
The business may deny a request when:
It cannot authenticate the consumer's identity with commercially reasonable efforts.
The request is manifestly unfounded or excessive.
A legal exception justifies continued processing or retention.
In all cases, the denial must be communicated to the consumer within the 45-day deadline, with:
The reason for the denial clearly stated.
Instructions on how to appeal the decision (Va. Code § 59.1-577 B, 2).
The appeal process must result in a written response within 60 days. If the appeal is also denied, the consumer must be informed about how to contact the Virginia Attorney General.
Va. Code § 59.1-578 A, 4 expressly prohibits businesses from discriminating against consumers who exercise their rights. This includes denying products or services, charging different prices, or offering lower quality.
The exception: voluntary loyalty, rewards, premium features, discount, or club card programs that offer benefits in exchange for data use are permitted, provided the consumer participates voluntarily.
Va. Code § 59.1-578 F prohibits processing data of known children under 13 for targeted advertising, data sale, or profiling with significant effects.
For social media platforms, starting January 2026, protection extends to minors under 16, with a 1-hour daily usage limit (Va. Code § 59.1-577.1).
If your portal receives requests from users in these age ranges, the process must have a differentiated flow.
Every processed request must be documented. This includes:
Date and time of receipt.
Type of request.
Authentication process performed.
Action taken (fulfilled, denied, or alternative adopted).
Date and form of response to the consumer.
In case of denial: recorded justification.
In case of appeal: complete history and final decision.
This documentation is what protects the business in the event of an Attorney General investigation. Without records, there is no way to demonstrate that processes were completed within the required deadlines.
Before initiating any action, the Attorney General must send notice with 30 days for the business to cure the violation (Va. Code § 59.1-584 B). If the business cures and provides a written correction statement, no action is initiated.
Businesses without a structured DSAR process have great difficulty correcting in 30 days what should have been implemented from the start. The cure period is a guarantee, not a compliance strategy.
If the violation continues, penalties can reach US$ 7,500 per violation, with each consumer whose right was violated potentially counting as a separate violation.
AdOpt logs every consent and opt-out interaction with a timestamp and unique identifier. When the consumer opts out of targeted advertising through the Privacy Portal, the system automatically updates cookie and tracker triggers.
AdOpt's auditable log serves as evidence that processes were completed as required by the VCDPA. And when legislation changes, the platform updates automatically.
Over 60,000 websites already run with AdOpt.
Privacy is not a banner. It is a position.
Want to build a Privacy Portal for your site that complies with the VCDPA? Talk to our team.
Request submission channel without requiring creation of a new account (Va. Code § 59.1-578 E).
Coverage of all 5 rights guaranteed by the VCDPA: access, correction, deletion, portability, and opt-out.
Conspicuously available appeal process comparable to the original submission channel (Va. Code § 59.1-577 C).
45-day response deadline, with the option to extend by another 45 days with notification (Va. Code § 59.1-577 B, 1).
60-day deadline to respond to appeals (Va. Code § 59.1-577 C).
Commercially reasonable identity authentication process (Va. Code § 59.1-577 B, 4).
Free service up to twice per year per consumer (Va. Code § 59.1-577 B, 3).
Documented record of each request, action taken, and response sent.
Information about how to contact the Attorney General in case of a denied appeal (Va. Code § 59.1-577 C).
Non-discrimination protection for consumers exercising their rights (Va. Code § 59.1-578 A, 4).
Differentiated treatment for known children under 13 (Va. Code § 59.1-578 F).
Notification to third parties where applicable for deletion or correction of shared data.
| Request type | Response deadline | Extension possible |
|---|---|---|
| Access, correction, deletion, portability | 45 days | +45 days with notification |
| Opt-out (advertising, sale, profiling) | 45 days | +45 days with notification |
| Appeal of a decision | 60 days | Not specified |
| Cure period for violations | 30 days guaranteed | No extension |
1. Does the VCDPA require a dedicated Privacy Portal?
Not by name. Va. Code § 59.1-578 E requires the controller to establish and describe in the Privacy Policy at least one secure and reliable means for submitting requests. A dedicated Privacy Portal is the most organized way to meet this requirement, but a well-structured contact form or a monitored email address can also fulfill the obligation, as long as they meet the security and reliability criteria.
2. Does the VCDPA have a specific deadline to cease processing after an opt-out?
Not in the same way as the NHDPA, which specifies 15 days. The VCDPA uses the criterion "without undue delay" for the general response, with a maximum of 45 days (Va. Code § 59.1-577 B, 1). In practice, for targeted advertising opt-outs, the expectation is that cessation is processed with the greatest technically reasonable agility, within the formal response deadline.
3. How many times per year must the business process DSARs free of charge?
Twice per year per consumer, under Va. Code § 59.1-577 B, 3. From the third request within the same 12-month period, the business may charge a reasonable fee or decline if the request is manifestly unfounded, excessive, or repetitive. The burden of proving the excessive nature lies with the business.
4. What happens if the business does not have a DSAR process when it receives an Attorney General notice?
The Attorney General sends notice with 30 days to cure (Va. Code § 59.1-584 B). If the business fails to implement the process within the deadline or breaches the written correction statement provided, the AG may seek penalties of up to US$ 7,500 per violation. Each consumer whose right was violated can be a separate violation, which quickly escalates the financial exposure.
5. How does the VCDPA handle data of consumers obtained from third parties in the context of a deletion request?
Va. Code § 59.1-577 B, 5 offers a specific alternative for this case. A business that obtained data from a source other than the consumer may fulfill the deletion request in two ways: by deleting the data outright, or by retaining the minimum data necessary to ensure the consumer's personal data remains deleted from active records and is not used for any purpose other than maintaining that deletion. This alternative does not exist in the NHDPA or in some other US state privacy laws.
Ready to build a Privacy Portal for your site that complies with the VCDPA? Talk to our team.
Virginia VCDPA compliance rests on documents that need to agree with each other: the cookies policy, which declares every tracker and its purpose; the privacy policy, which explains what you do with the data.
Understanding the General Data Protection Regulation (GDPR) and its impact on cookies is essential. So, let's break it down, step by step.
With the data mapping we have a clear understanding of the 5 stages that every data goes through in a company.
Utah UCPA explained: the most business-friendly US state privacy law, dual threshold requirement, opt-out for sensitive data, no right to correct, guaranteed 30-day cure period, and key differences from other state laws.
How does your website handle LGPD? What strategies does it use to comply with the General Data Protection Law? Have you thought about using a cookie notice but don't know if your site has cookies or if it's enough? If you can't answer these questions, be cautious! Your page may be exposed to fines and other sanctions.
Your website have users accessing from Texas? So be ready… the Texas Data Privacy and Security Act is here to shake things up. Don't worry; we've got your back. This guide will walk you through everything you need to know to ensure your website complies with the new regulations.
What the California CCPA/CPRA requires from your Privacy Policy: 12-month lookback, annual updates, Do Not Sell link, sensitive PI disclosures, toll-free number, and the 7 consumer rights.
What the Virginia VCDPA requires from your Cookies Policy: targeted advertising disclosure, consent standards, tracker categories, opt-out mechanisms, and the 30-day cure period explained.
In this article, we'll explore the GDPR foundations and provide practical insights from the basics to more advanced concepts of its legal basis.
How to handle DSARs under the Connecticut CTDPA: 5 consumer rights, opt-outs without mandatory authentication, 60-day appeal deadline, 15-day consent revocation, and AG-only enforcement.
Having a cookie banner on your brand's website has become indispensable for many. However, for e-commerce websites, it has practically become an obligation to have one. This is because this type of website has a technological composition in which cookies are a structural part. Login flow, items in the shopping cart, recommendation showcases, remarketing... Most of them rely on cookies.
Everything about the Oregon OCPA: who must comply, the payment transaction exclusion, 25% revenue threshold, derived data in scope, GPC requirement from January 2026, and elimination of the cure period.
Google Consent Mode (GCM) is nothing more than a way for you to integrate the consent you collect from your visitors into Google technologies. In this way, upon receiving this consent information, collection can only occur with authorization, thus complying with the legislation and having direct evidence of compliance as defense for both you and Google.
What the Oregon OCPA requires from your Cookies Policy: opt-out link, GPC from January 2026, opt-out without authentication, derived data in scope, teen protections, and the elimination of the cure period.
Want to understand why there are cookie banners on every website you visit today? This article is for you!
What the Oregon OCPA requires from your Privacy Policy: actively monitored contact channel, detailed third-party descriptions, derived data in scope, GPC from January 2026, and the elimination of the cure period.
All the important information about the General Data Protection Law - LGPD: what it is, why it exists, how it works, when it came into force, who it applies to, potential fines, steps for compliance, and its legal principles.
What the Iowa ICDPA requires from your Cookies Policy: opt-out for data sales and targeted advertising, opt-out model for sensitive data, no GPC requirement, no specific link text required, and the 90-day cure period.
Using a CMP (Consent Management Platform) is a great way to make efforts to adapt to new privacy regulations like GDPR, LGPD, DPDPA, CCPA and more...
What the Florida FDBR requires from your Cookies Policy: targeted advertising across affiliated sites, opt-out for sensitive data and voice recognition, dark patterns, and tripled penalties.
The Data Protection Officer, or DPO, is a new position that emerged all over the globe with the new privacy regulations, and more recently at the LGPD. Although it already existed in other international legislations, such as the EU's GDPR, it is still a novelty here since 2020. Along with it comes the possibility of outsourcing, known as DPO as a Service (DPOaaS).
The Connecticut Data Privacy Act (CTDPA) is a state regulation designed to protect the privacy of Connecticut residents. It also regards cookies, so in this article we will help you understand all about this new privacy regulation.
How to handle DSARs under the California CCPA/CPRA: 7 consumer rights, 45-day deadline, toll-free number required, 12-month lookback, private right of action for breaches, and CPPA enforcement.
What is a DSAR under NHDPA? Complete guide to consumer rights, response deadlines, and building a compliant Privacy Portal for your site.
Despite cookies being more well-known, what is the main difference between cookies and session storage and local storage? Why choose one over the other? This article will help you with these doubts!
What the Florida FDBR requires from your Privacy Policy: annual updates, 6 mandatory content categories, specific notices for sensitive and biometric data sales, and the 7 consumer rights.
Brazilian LGPD - General Data Protection Law brought with it several acronyms and specific terms. Many of them are imported from other countries and regulations. One of them is ROPA (Record Of Processing Activities), adapted in Brazil to Registros das Atividades de Tratamento. An essential document for any DPO, Data Processor.
Now that we have the data flow within your company, we need to highlight 2 aspects of LGPD that will help you determine the extent of your responsibility in relation to the many points listed in the company. I'm talking about the difference between Data Controller and Data Processor.
What are the criteria for this choice, and what are the strengths and weaknesses of each option? Well, we're here to help you because this decision needs to be well thought out!
Surely you've already seen the predictions of fines and sanctions, processes. But, what does it mean to your company?
Discover what the New Hampshire Privacy Act (NHDPA) means for your business. Learn about compliance steps, consumer rights, penalties, and how to simplify it all with AdOpt, a Google-certified CMP.
A privacy policy is a document that outlines how an organization collects, uses, discloses, and manages a customer's data. It's essential for building trust with users and complying with legal requirements. However, if you're not familiar with it, don't worry as we're here to help you.
LGPD is in effect. Despite that, there are still many companies ignoring it, but is that possible? How long can we ignore LGPD?
Learn what your Privacy Policy must contain under the NHDPA. We break down the 8 mandatory elements and how to comply with New Hampshire's data privacy law.
Ignoring Terms of Use and their significance within a website, particularly now with LGPD, is a common mistake that both consumers and website owners frequently commit.
Learn what your TIPA Privacy Policy must include to comply with the Tennessee Information Protection Act from consumer rights and targeted advertising disclosures to the NIST affirmative defense, appeal mechanisms, and how to keep your notice aligned with your operational program.
Learn about how to apply Montana MTCDPA Cookies Policy in your site
Here is a step-by-step explanation of how consent registration works in AdOpt.
If you're looking to understand how this law impacts businesses in Tennessee, especially those dealing with digital cookies, you're in the right place. This article will simplify the complexities of compliance and make them easy to grasp, even if you're just starting to learn about data privacy.
California CPRA explained: CCPA vs CPRA timeline and key differences, sensitive personal information, sharing of data, CPPA enforcement, GPC requirement, and tripled penalties for minors.
Google Analytics 4 cookie consent explained: what GA4 does when a visitor says no, what changes in your reports, and how to check your setup.
LGPD, GDPR, and CCPA are data privacy regulations. In this article, we discuss their similarities and differences for practical application.
California CPRA DSAR guide: new rights to correct and limit SPI, opt-out without multiple steps, GPC as valid opt-out, 12-month minor rule, private right of action, and CPPA enforcement.
Oregon OCPA DSAR guide: the L.O.C.K.E.D. rights, opt-out without authentication, derived data in deletion scope, 15-day revocation deadline, GPC from January 2026, and the elimination of the cure period.
Axeptio acquires Brazil's AdOpt, expanding global reach in consent management and LGPD compliance.
Everything you need to know about the Florida Digital Bill of Rights (FDBR): who must comply, the $1 billion threshold, 7 consumer rights, FIPA vs FDBR explained, penalties, and cookies.
26 May 2026
Address: 7345 W Sand Lake Road, Ste 210 Office 5898 Orlando, FL 32819
15 Rue du Général Campredon, 34000 Montpellier, France
207 Rue de Bercy, 75012 Paris, France
EIN: 86-3965064
Phone: +1 (407) 768-3792
AdOpt
Resources
Product
Certifications