Richmond, VA
AI governance in Richmond
No Virginia AI Act to comply with
Richmond is a government and professional-services metro: state agencies and the vendors that sell to them, insurers and other financial institutions, health systems, law firms, and campuses. The AI question is usually whether a Virginia statute exists to comply with. It does not.
TrustEdge serves organizations in Richmond and across Virginia, with engineers and assessors on-site for the work. AI Academy and agent engagements are delivered nationally.
The pressure
What Richmond organizations are actually dealing with
HB 2094 passed both chambers and died on a veto that was sustained. The Consumer Data Protection Act is the privacy duty that remains, and its entity-level exemptions remove many of the organizations in this market. Vendors to executive-branch agencies also answer to VITA’s procurement standards. The mistake is buying a program for a bill that is not law.
Sectors we serve here
- State government and contractors
- Insurance and financial services
- Healthcare
- Higher education and legal
A capital, and the buyers who sit in it
Richmond is the seat of state government and a center for the organizations that sell to it, alongside insurance and other financial services, healthcare, law, higher education, and distribution. Virginia’s regulation page records the Commonwealth’s posture, including the state’s data-center concentration. That concentration is not what a Richmond buyer is managing. The buyer in this metro is more often an agency, a vendor to an agency, an insurer, a health system, a law firm, or a campus.
The question those buyers are sold is often whether they need Virginia AI Act compliance. There is no Virginia AI Act. The state’s overview states the operating fact in one sentence: if you deploy AI in Virginia today, no Virginia AI statute governs you. This page exists so that sentence is the one a Richmond reader hears first.
The bill passed, and it is still not law
HB 2094, the High-Risk Artificial Intelligence Developer and Deployer Act, passed both chambers in February 2025. It would have imposed a duty of reasonable care against algorithmic discrimination on developers and deployers of high-risk AI making consequential decisions in employment, lending, health care, housing, insurance, education, and parole, together with impact assessments and risk-management policies. Governor Youngkin vetoed it on March 24, 2025. Overriding required two-thirds of both chambers. The House sustained the veto on April 2, 2025. No successor has been enacted.
The 2026 session, under Governor Spanberger, did not revive it. Our Virginia regulation page records two narrow results from that session: a study of independent verification organizations, and guidance for AI use in public schools. The comprehensive bills were killed. Comprehensive AI legislation is a 2027 conversation. Any description of Virginia as having a high-risk AI act, or as about to enact one, is more than a year out of date. The provision title on this page is the accurate status: vetoed, sustained, and dead.
Building a Richmond program around that bill is building a program for a law that does not exist. Employment, lending, housing, and insurance decisions are still governed by the anti-discrimination and sector laws that already applied. Our Virginia regulation page’s penalties section is explicit that an AI system producing discriminatory outcomes in employment, lending, housing, or insurance remains actionable under Virginia and federal anti-discrimination law, and that deceptive claims about an AI system remain actionable as consumer fraud. The absence of an AI statute is not the absence of liability. It is the absence of a Virginia duty of care, impact-assessment mandate, risk-management-program requirement, disclosure requirement, and chatbot rule for private businesses. Our Virginia regulation page says that absence is the state of the law, not a gap in the research.
The privacy statute, and the exemptions that end the analysis
The Consumer Data Protection Act has been in force since January 1, 2023. It is the privacy duty that remains. Consumers may opt out of profiling in furtherance of decisions that produce legal or similarly significant effects. Profiling, in the statute, is any automated processing of personal data to evaluate, analyze, or predict a person’s economic situation, health, preferences, interests, reliability, behavior, location, or movements. A separate provision requires a documented data protection assessment for profiling that presents a reasonably foreseeable risk of unfair or deceptive treatment, unlawful disparate impact, or specified injuries, and for other heightened-risk processing. The Attorney General may compel production of those assessments.
Enforcement is exclusive to the Attorney General. The statute requires 30 days’ written notice and an opportunity to cure, and that cure period has no sunset. There is no private right of action. Penalties run up to $7,500 per violation after the cure period, plus reasonable expenses and attorney fees. There are no AI-specific penalties in Virginia law, because there is no AI-specific prohibition to violate.
The exemptions are why the analysis stops early for a large share of this metro. Thresholds come first: the Act applies to entities that control or process personal data of at least 100,000 Virginia consumers in a calendar year, or at least 25,000 consumers while deriving more than half of gross revenue from selling personal data. On top of the thresholds, the exemptions are entity-level, not data-level. Financial institutions subject to the Gramm-Leach-Bliley Act, HIPAA-covered entities and business associates, nonprofits, institutions of higher education, and government bodies are excluded entirely. Employee and contractor data collected in the employment context is outside scope as well.
A Richmond health system, a GLBA insurer or bank, a university, a nonprofit, or a state agency should confirm that exemption and then stop treating the VCDPA as its AI program. A professional-services firm or another controller that clears the thresholds and is not exempt cannot. Confirming an exemption is not a finding that no rule applies. HIPAA, the FTC Act, fair-lending and consumer-reporting rules, and employment-discrimination law are not repealed by a privacy exemption. Our Virginia regulation page’s practical implication is the planning judgment to follow: do not build a Virginia-specific AI compliance program. Build against the obligations that already travel with the activity. Where a customer or a procurement office asks for a process, the NIST AI Risk Management Framework is one our Virginia regulation page names. ISO/IEC 42001 is a standard an organization may choose to pursue. TrustEdge does not certify anyone to it.
Selling to the Commonwealth is a procurement standard
Executive Order 30, issued January 18, 2024, directed the Virginia Information Technologies Agency to publish AI policy and IT standards for executive branch agencies. VITA maintains Enterprise Architecture Standard EA-225 and an AI Utilization Policy. They reach AI an agency uses, including AI embedded in other systems and AI built by a third party. A company selling AI-enabled software to a Virginia executive branch agency will be assessed against that framework in procurement. It is policy, not a statute, and our Virginia regulation page calls it the most operationally consequential AI rule in the Commonwealth for a government-facing vendor. A Richmond company that does not sell to the state does not inherit the standard by sitting in the capital.
Public schools are a narrower track. HB 1186 and SB 394, effective July 1, 2026, direct the Department of Education to study current use and issue guidance on safe, ethical, and equitable use of AI in public elementary and secondary schools. Local school boards then set policy consistent with that guidance. The same legislation creates a pilot program. Obligations fall on the Department and the school divisions, not on private deployers generally. An education vendor should expect division policy to show up as a procurement gate, and should not describe that guidance as a private-sector AI statute.
The Joint Commission on Technology and Science report on independent verification organizations is due November 1, 2026. HB 797 and SB 384 direct the study. They do not license or regulate anyone today. If a later session acts on the report, the shape our Virginia regulation page describes is closer to third-party assessment than to the duty-of-care bill that failed. That is a reason to read the report when it exists. It is not a reason to implement a regime that has not been enacted. Two comprehensive-style bills failed in the 2026 session, SB 365 and HB 1294. They are not law.
How the work is delivered in Richmond
TrustEdge serves organizations in Richmond and across Virginia. Scoping what a model touches means sitting on-site with the people who bought it and the people who run it. The engagement is an inventory, plus a reading of which Virginia rules reach that organization and which do not.
For many regulated buyers in this metro the honest reading is short. Virginia contributes the VCDPA exemption analysis and, for a vendor to an executive-branch agency, the VITA standard. It does not contribute an AI act. Organizations that are not exempt, and that clear the consumer thresholds, still owe the profiling opt-out and, for profiling that presents a heightened risk, the data protection assessment. Those two items are the privacy work. They are not a substitute for a high-risk AI statute, and they should not be scoped as if HB 2094 had taken effect.
The provision text on this page is looked up from our Virginia regulation page by title. The Virginia regulation page holds the rest of the record, including the bill list and the enforcement detail. This page does not add a legal fact that page does not already state.
Regulatory context
The Virginia rules that reach Richmond buyers
Virginia has no comprehensive AI statute. HB 2094 was vetoed in 2025 and the veto was sustained. The real obligations run through the Consumer Data Protection Act, and its exemptions remove most healthcare and financial services entities outright.
There is no Virginia AI statute reaching private-sector deployment
Virginia imposes no algorithmic-discrimination duty, no impact-assessment mandate, no AI risk-management-program requirement, no AI disclosure requirement, and no chatbot-specific rules on private businesses. This is not a gap in our research. It is the state of the law. Virginia is a light-touch jurisdiction and has been deliberate about staying one.
HB 2094 — vetoed, sustained, and dead
HB 2094 would have imposed a duty of reasonable care against algorithmic discrimination on developers and deployers of high-risk AI making consequential decisions in employment, lending, health care, housing, insurance, education, and parole, together with impact assessments and risk-management policies. It passed the Senate by two votes and the House by four. Governor Youngkin vetoed it on March 24, 2025, writing that its rigid framework failed to account for a fast-moving industry and placed an onerous burden on smaller firms and startups. Overriding required two-thirds of both chambers. The House sustained the veto on April 2, 2025. Any vendor or tracker still describing Virginia as having a high-risk AI act, or as likely to enact one imminently, is more than a year out of date.
The exemptions do most of the work for regulated industries
The VCDPA applies only to entities that control or process personal data of at least 100,000 Virginia consumers in a calendar year, or at least 25,000 consumers while deriving more than half of gross revenue from selling personal data. On top of that, the exemptions are entity-level, not data-level: financial institutions subject to the Gramm-Leach-Bliley Act, HIPAA-covered entities and business associates, nonprofits, institutions of higher education, and government bodies are excluded from the statute entirely. Employee and contractor data collected in the employment context is also outside scope. For a great many healthcare and financial services organizations, the honest answer is that Virginia privacy law does not reach them at all.
Executive Order 30 and the VITA standards — binding on state agencies and their suppliers
Governor Youngkin's Executive Order 30, issued January 18, 2024, directed the Virginia Information Technologies Agency to publish AI policy and IT standards for executive branch agencies, AI education guidelines, law enforcement standards, and an AI task force. VITA maintains Enterprise Architecture Standard EA-225 and an AI Utilization Policy, which reach existing and new AI use, embedded and generative AI inside other systems, and AI developed by agencies or by third parties. If you sell AI-enabled software to a Virginia executive branch agency, this is the framework your product and your documentation will be assessed against. It is procurement policy, not a statute — but it is the most operationally consequential AI rule in the Commonwealth for government-facing vendors.
All Virginia AI provisions, in full →
Reviewed against primary sources as of September 14, 2026.
This page summarizes public law for orientation and is not legal advice.
How we help
What we do in Richmond
AI Governance
AI Academy
AI Operations
Other markets we serve on-site
- San Francisco, CAWhere the AI is the product
- San Jose, CASelling AI into regulated buyers
- Oakland, CAAI inside the HIPAA boundary
- Alameda, CAOur home market
- Sacramento, CAWhere the rules are written, and applied
- Omaha, NEYour regulator is rarely in your state
- Nashville, TNHealthcare and a recorded voice, under narrow laws
- Chattanooga, TNOperations running ahead of any AI statute
- Arlington, VACustomer contracts, not a Virginia AI act
- Salt Lake City, UTOn-request disclosure, and a chatbot statute
- Austin, TXIntent-based rules, and no city overlay
- Denver, CORepealed and replaced before it took effect
- Memphis, TNTwo deepfake statutes, and no comprehensive law
- San Antonio, TXPrivate biometric consent, government-only bans
- Baltimore, MDFrameworks, contracts, and other states
- Pittsburgh, PANarrow laws, and enforcement already underway
- Tampa, FLNo comprehensive statute, and a deceptive-practices theory
- Providence, RISeveral buyer types, and separate inventories
- Albany, NYEnacted, in three layers that rarely meet
Talk to us about AI governance in Richmond
No pitch, no pressure. We will tell you what is actually in scope and what an assessor will accept.
