Law / United States / Virginia

Virginia

32 of 35 named instruments researched to a stage, across six of the ten areas of law we track: 31 in force and 1 blocked by a court. As of .

When each starts23 of 32 carry a date, 9 do not. Earlier is before 2014.
Before 2014: 6 instruments (6 in force) earlier 2014: 0 instruments 2015: 1 instrument (1 in force) ’15 2016: 0 instruments 2017: 0 instruments 2018: 0 instruments 2019: 1 instrument (1 in force) 2020: 3 instruments (3 in force) ’20 2021: 0 instruments 2022: 2 instruments (2 in force) 2023: 8 instruments (8 in force) 2024: 0 instruments 2025: 1 instrument (1 in force) 2026: 1 instrument (1 blocked by a court) ’26 today

in forcenot yet in forceblocked by a courtproposedno longer in force

  1. AI law 2
  2. Privacy law 18
  3. Scraping law 2
  4. Cybersecurity law 3
  5. Communications law 5
  6. Content moderation law not researched
  7. Product and AI liability law not researched
  8. Digital accessibility law not researched
  9. Age gating law 2
  10. Reuse law

Case lawPremium data

Our analysis of Virginia law draws on 1 court ruling.

Which laws the rulings read, and each ruling, are premium data, in the Plus, Pro and Enterprise plans.

  • No current case law for Virginia AI law
  • No current case law for Virginia privacy law
  • No current case law for Virginia scraping law
  • No current case law for Virginia cybersecurity law
  • No current case law for Virginia communications law
  • No current case law for Virginia content moderation law
  • No current case law for Virginia product and AI liability law
  • No current case law for Virginia digital accessibility law
  • Age gating law: 1 court ruling
  • No current case law for Virginia reuse law

See the plansSign in

AI law2 instruments, 2 in force

Research summary (148 words)

Virginia's AI-specific findings sit in the criminal code rather than a horizontal AI act: Va. Code Ann. § 18.2-386.2 was amended by HB 2678 (2019), effective , to extend the state's nonconsensual-image statute to a videographic or still image created, adapted, or modified to falsely depict an identifiable actual person (a deepfake), and §§ 18.2-374.1 and 18.2-374.1:1 define child pornography to reach a computer-generated depiction of an identifiable minor without requiring the depicted scene itself to have actually occurred.

A family of 2026 bills on synthetic media in campaign advertisements (including SB 141, which reached and failed at a conference committee) and a companion-chatbot bill (HB 635, referred to committee) did not advance. Executive Order 30 (2024) and the 2026 Joint Commission on Technology and Science study directed by HB 797/SB 384 each bind only Virginia government bodies or study committees and are not catalogued here.

AI prohibited practices

Computer-Generated Child Sexual Abuse Material

Va. Code Ann. §§ 18.2-374.1, 18.2-374.1:1official codified text, Virginia Law (law.lis.virginia.gov)

In force. Binds public and private bodies.

What this law does

Virginia's child pornography statute defines an identifiable minor to include a person whose image as a minor was used in creating, adapting, or modifying a visual depiction, recognizable by face, likeness, or other distinguishing characteristic, and its own text states that for this purpose the minor depicted does not have to actually exist, reaching a computer-generated or AI-manipulated depiction built from an identifiable real minor's likeness on the same terms as an unaltered photograph.

Section 18.2-374.1 punishes producing, financing, or knowingly taking part in producing such material, with penalties graduated by the subject's age and the offender's age relative to the subject; section 18.2-374.1:1 separately punishes knowing possession, and reproduction, sale, distribution, or solicitation to gain entry into a trading group. The provisions this entry describes came into force on different days.

What it requires

HB 2678 (2019), Deepfakes in Nonconsensual Image Dissemination

Va. Code Ann. § 18.2-386.2official codified text, Virginia Law (law.lis.virginia.gov)

In force since . Binds public and private bodies.

What this law does

Any person who, with intent to coerce, harass, or intimidate, maliciously disseminates or sells a videographic or still image depicting another person nude, partially exposed, or (where not exposed) obscene, knowing or having reason to know they are not licensed or authorized to do so, is guilty of a Class 1 misdemeanor.

HB 2678 (2019), effective , expanded 'another person' to include someone whose image was used in creating, adapting, or modifying a videographic or still image to depict an actual, recognizable person, reaching a falsely created or digitally manipulated (deepfake) image on the same terms as an unaltered photograph.

An internet, email, or other access-software provider is not liable under this section for content supplied by another person, and venue lies where the unlawful act occurs or where the image is produced, found, stored, or possessed.

What it requires

Privacy law18 instruments, 18 in force

Research summary (799 words)

Virginia has no general biometric-identifier statute; the Virginia Consumer Data Protection Act (VCDPA) is Virginia's comprehensive consumer-privacy regime, codified at Va. Code Ann. sections 59.1-575 to 59.1-585 (Title 59.1, Chapter 53). Effective , it requires opt-in consent for sensitive data and gives consumers access, correction, deletion, portability, and opt-out rights.

Genetic and biometric data collected to uniquely identify a person is one of VCDPA's enumerated sensitive-data categories, so biometric data itself is a heightened category here.

Within that category, VCDPA's biometric data definition separately carries a blanket exclusion for any data generated from a photograph, video, or audio recording, with no clawback for data generated to identify someone, so a faceprint or voiceprint extracted from a recording falls outside biometric data, and therefore outside sensitive data, entirely.

A separate chapter, Va. Code Ann. section 18.2-186.6, governs breach notification, and that chapter, unlike VCDPA itself, preserves an individual's right to recover direct economic damages for a violation of the notification duty. The VCDPA Attorney General has exclusive enforcement authority over the comprehensive act; there is no private right of action under VCDPA.

A 2026 amendment (S.B. 338) banned the sale of precise geolocation data, and separate minors' social-media provisions (section 59.1-577.1) are under a federal preliminary injunction: NetChoice v. Jones, No. 1:25-cv-2067 (PTG/LRV) (E.D. Va.), granted around , with the Attorney General's appeal docketed at the Fourth Circuit on .

Section 59.1-577.1 is not catalogued here as its own instrument: neither the provision's text nor the appeal's current posture is verified against the court docket, and the citation above rests on the court's own memorandum opinion and secondary reporting. Virginia's genetic data privacy chapter, sections 59.1-593 to 59.1-602 of the Code of Virginia, binds direct-to-consumer genetic testing companies.

Section 40.1-28.7:1 of the Code of Virginia bars an employer from requiring a genetic test as a condition of employment. Section 38.2-508.4 of the Code of Virginia bars an accident and sickness insurer from using genetic information to restrict or condition coverage or set premium differentials. Section 32.1-127.1:03 of the Code of Virginia bars a health care entity from disclosing an individual's health records except as the section or other state law permits or requires.

Article 1 of chapter 6 of Title 38.2 of the Code of Virginia establishes a regulatory mechanism for natural persons to learn what information has been collected about them in connection with insurance transactions and to have access to it to verify or dispute its accuracy. Sections 38.2-604.1 and 38.2-612.1 of the Code of Virginia require an insurer to give notice and a 30-day opportunity to opt out before disclosing financial information to a nonaffiliated third party.

Section 38.2-625 of the Code of Virginia requires a licensee that has determined that a cybersecurity event has actually occurred to notify the Commissioner of Insurance in the cases it lists. Section 38.2-626 of the Code of Virginia requires a licensee to notify affected consumers of a cybersecurity event without unreasonable delay in the cases it lists.

Section 59.1-443.2 of the Code of Virginia bars a person from intentionally communicating another individual's social security number to the general public. Section 22.1-289.01 of the Code of Virginia binds school service providers, which are entities that operate a school service under a contract with a local school division.

Section 59.1-478 of the Code of Virginia requires a person who requires fingerprints in a business, commercial or financial transaction, unless the parties otherwise agree, to return or destroy them within 21 days of the transaction's completion or termination.

Section 40.1-28.7:10 of the Code of Virginia bars an employer from using an employee's social security number, or a number derived from it, as the employee's identification number or placing it on an identification or access card or badge. An employer that knowingly violates section 40.1-28.7:10 is subject to a civil penalty not to exceed $100 for each violation.

Section 59.1-442 of the Code of Virginia bars a merchant, without giving notice to the purchaser, from selling to any third person information that concerns the purchaser and is gathered in connection with a retail sale at its place of business, and a merchant asked by a purchaser not to sell the information may not do so.

A person aggrieved by a violation of the Personal Information Privacy Act, other than section 59.1-443.2, may recover damages of $100 per violation, plus attorney fees and court costs if the person prevails. Section 59.1-443.3 of the Code of Virginia bars a merchant from scanning the machine-readable zone of a driver's license except for the purposes subsection A lists.

Section 59.1-443.3(C) of the Code of Virginia bars a merchant from selling or disseminating to a third party information obtained from a scan of a driver's license for any marketing, advertising or promotional purpose.

Biometric privacy

Fingerprints furnished in a business, commercial or financial transaction: return or destruction

Va. Code Ann. § 59.1-478Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds public and private bodies.

What this law does

Whenever any person requires another to furnish a fingerprint or fingerprints in conjunction with a business, commercial or financial transaction, unless the parties otherwise agree, the person must within 21 days of the transaction's completion or termination return or destroy the original record of the prints and all copies, including electronic or facsimile copies. The section does not apply to fingerprints affixed to instruments governed by Titles 8.3A and 8.4.

Chapter 715 of the 1999 Acts of Assembly numbered the section 59.1-480 in a new chapter 41 of Title 59.1. Chapter 715 of the 1999 Acts of Assembly took effect on .

What it requires

Breach notification

Breach of personal information notification

Va. Code Ann. § 18.2-186.6official Virginia statute text, Title 18.2 Chapter 6, Code of Virginia

In force. Binds public and private bodies.

What this law does

An individual or entity that owns or licenses computerized data including personal information must disclose a breach of the security of the system to the Office of the Attorney General and any affected Virginia resident without unreasonable delay following discovery.

'Personal information' here (a Social Security, driver's license or state ID, passport, or military ID number, or a financial account number with an access code, each combined with a name) is narrower than VCDPA's 'personal data' and excludes information obtained from publicly available government records.

Unlike VCDPA, which bars a private plaintiff outright, this breach-notification chapter provides that nothing in it limits an individual from recovering direct economic damages for a violation, and grants no cause of action of its own. The provisions this entry describes came into force on different days.

What it requires

Insurance Data Security Act: investigation of a cybersecurity event and records of every event

Va. Code Ann. § 38.2-624official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

A licensee that learns that a cybersecurity event has or may have occurred must conduct, or have an investigator conduct, a prompt investigation. The investigation must at a minimum determine whether a cybersecurity event has occurred, assess its nature and scope, identify any nonpublic information involved, and perform or oversee reasonable measures to restore the security of the compromised information systems.

Where the event occurs in a system a third-party service provider maintains, the licensee must complete those steps or make reasonable efforts to confirm and document that the provider has completed them. Each licensee must maintain records concerning all cybersecurity events for at least five years from the date of the event and must produce those records upon demand of the Commissioner.

What it requires

Insurance Data Security Act

Va. Code Ann. §§ 38.2-625 and 38.2-626Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

A licensee is any person licensed, authorized to operate, or registered, or required to be licensed, authorized, or registered, under the insurance laws of the Commonwealth. A licensee that has determined that a cybersecurity event has actually occurred must notify the Commissioner no later than three business days after the determination in the cases section 38.2-625(A) lists.

A licensee must notify affected consumers without unreasonable delay where nonpublic information was accessed and acquired by an unauthorized person and the event has a reasonable likelihood of causing or has caused identity theft or other fraud. A licensee that provides notice to more than 1,000 consumers at one time must also notify the nationwide consumer reporting agencies of the timing, distribution and content of the notice.

A licensee subject to Health Insurance Portability and Accountability Act (HIPAA) that has established and maintains an information security program under it, and that investigates a cybersecurity event and notifies consumers in accordance with HIPAA, is considered compliant with sections 38.2-624 and 38.2-626. The article does not create or imply a private cause of action for a violation of its provisions, and does not curtail one that would otherwise exist.

The Commissioner may examine and investigate the affairs of any licensee and take the action necessary or appropriate to enforce the article. The article and the rules adopted under it establish the exclusive state standards applicable to licensees for data security, the security of nonpublic information, and the investigation and notification of cybersecurity events.

Section 38.2-218 of the Code of Virginia punishes a knowing or willful violation of any provision of Title 38.2 by a penalty of not more than $5,000 for each violation. The article took effect on .

What it requires

Comprehensive regime

Virginia Consumer Data Protection Act (VCDPA), data protection assessments

Va. Code Ann. § 59.1-580official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

A controller must conduct and document a data protection assessment of processing for targeted advertising, the sale of personal data, certain profiling, the processing of sensitive data and any processing that presents a heightened risk of harm to consumers. A controller that offers an online service, product or feature directed to consumers it has actual knowledge are children must conduct a data protection assessment for it.

The Attorney General may request, pursuant to a civil investigative demand, that a controller disclose any data protection assessment relevant to an investigation, and the controller must make it available to the Attorney General. Data protection assessments are confidential and exempt from public inspection and copying under the Virginia Freedom of Information Act. The assessment requirements apply to processing activities created or generated after , and are not retroactive.

What it requires

Virginia Consumer Data Protection Act (VCDPA), general applicability and controller/processor duties

Va. Code Ann. §§ 59.1-575, 59.1-576, 59.1-578, 59.1-579official Virginia statute text, Title 59.1 Chapter 53, Code of Virginia

In force since . Binds private bodies.

What this law does

VCDPA governs private-sector processing of Virginia residents' personal data. Enacted in the 2021 Special Session I (cc. 35, 36), effective . Controllers need a lawful basis for processing outside disclosed purposes and opt-in consent for sensitive data; controller duties are allocated at section 59.1-578 and processor duties, including a required data-processing contract, at section 59.1-579.

A 2026 amendment (S.B. 338, Ch. 820) added a ban on the sale of precise geolocation data, effective and already reflected in the codified text.

What it requires

Data subject rights

Insurance Information and Privacy Protection

Va. Code Ann. §§ 38.2-600 to 38.2-619Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force. Binds private bodies.

What this law does

The article binds insurance institutions, agents and insurance-support organizations that, for life or accident and sickness insurance, collect, receive or maintain information about Virginia residents or engage in transactions with Virginia residents, and, for property or casualty insurance, handle information about or engage in transactions on policies delivered, issued for delivery or renewed in the Commonwealth.

The article applies only to insurance purchased primarily for personal, family or household purposes. No insurance institution, agent or insurance-support organization may use or authorize the use of pretext interviews to obtain information in connection with an insurance transaction, subject to an exception for investigating a claim. An insurance institution or agent must give every applicant or policyholder a notice of insurance information practices, at the times section 38.2-604 sets.

On a written request after proper identification, the holder must within 30 business days tell the individual the nature and substance of recorded personal information, let the individual see and copy it, disclose to whom it was disclosed within two years, and summarize the correction procedures.

Within 30 business days of a written request to correct, amend or delete recorded personal information, the holder must either do so or notify the individual of its refusal, the reasons and the right to file a statement. After an adverse underwriting decision, the insurance institution or agent responsible must give a written notice that provides the specific reasons or advises that they may be requested in writing, together with a summary of the individual's rights.

On a written request within 90 business days of the notice, the insurance institution or agent must furnish within 21 business days the specific reasons, the specific items of personal and privileged information that support them, and the names and addresses of the institutional sources.

An insurance institution, agent or insurance-support organization may not disclose medical-record information or privileged information about an individual collected or received in connection with an insurance transaction without the individual's written authorization.

A person proposing to issue accident and sickness insurance of the kind section 38.2-613(D) names may not disclose genetic information about an individual or a family member collected or received in connection with an insurance transaction unless the disclosure is made with the individual's written authorization. A person whose rights under sections 38.2-608, 38.2-609 or 38.2-610 are violated may apply to a court of competent jurisdiction for appropriate equitable relief.

An entity that discloses information in violation of section 38.2-613 is liable for the damages sustained by the individual, which may not exceed the actual damages. Except as section 38.2-617 specifically provides, there is no remedy or recovery for individuals, in law or in equity, for a violation of any provision of the article.

The State Corporation Commission may examine and investigate any insurance institution or agent doing business in the Commonwealth to determine whether it has engaged in conduct that violates the article. Section 38.2-218 of the Code of Virginia punishes a knowing or willful violation of any provision of Title 38.2 by a penalty of not more than $5,000 for each violation.

A person who knowingly and willfully obtains information about an individual from an insurance institution, agent or insurance-support organization under false pretenses is fined not more than $10,000 or jailed for not more than 12 months, or both. Chapter 264 of the 2020 Acts of Assembly amended and reenacted sections 38.2-600, 38.2-601, 38.2-602, 38.2-612.1, 38.2-612.2, 38.2-613 and 38.2-614 through 38.2-618.

What it requires

Insurance: notice of financial information practices and opt-out of disclosure to nonaffiliated third parties

Va. Code Ann. §§ 38.2-604.1 and 38.2-612.1Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

An insurance institution or agent must give clear and conspicuous notice of financial information collection and disclosure practices in connection with insurance transactions. A policyholder other than a policyholder of a title insurance policy must receive the notice not less than once in each calendar year.

No insurance institution, agent or insurance-support organization may disclose financial information about an individual to a nonaffiliated third party unless the individual has received notice, an opportunity of at least 30 days to direct that it not be disclosed, a reasonable means to do so, and the third party agrees not to disclose it further.

An insurance institution, agent or insurance-support organization may not disclose a policy number or similar access number or transaction account of a policyholder or applicant to a nonaffiliated third party for use in telemarketing, direct mail marketing or marketing through electronic mail, subject to listed exceptions. No insurance institution or agent may unfairly discriminate against an individual because the individual has directed that personal information not be disclosed.

Section 38.2-218 of the Code of Virginia punishes a knowing or willful violation of any provision of Title 38.2 by a penalty of not more than $5,000 for each violation. Chapter 371 of the 2001 Acts of Assembly added sections 38.2-513.1, 38.2-604.1, 38.2-612.1 and 38.2-612.2 to the Code of Virginia. Chapter 371 of the 2001 Acts of Assembly took effect on . Section 38.2-612.1 was amended by Chapter 264 of the 2020 Acts of Assembly.

What it requires

Virginia Consumer Data Protection Act, consumer rights

Va. Code Ann. § 59.1-577official Virginia statute text, Title 59.1 Chapter 53, Code of Virginia

In force since . Binds private bodies.

What this law does

VCDPA gives a Virginia consumer the right to confirm and access their personal data, correct inaccuracies, delete data, obtain a portable copy, and opt out of targeted advertising, sale, and profiling in furtherance of decisions producing legal or similarly significant effects, exercisable against the controller.

A controller must respond without undue delay and within 45 days of receipt, with one 45-day extension available, and must answer an appeal of a denial within 60 days, with an option to escalate to the Attorney General.

What it requires

Enforcement supervision

Virginia Consumer Data Protection Act, Attorney General enforcement

Va. Code Ann. §§ 59.1-583, 59.1-584official Virginia statute text, Title 59.1 Chapter 53, Code of Virginia

In force since . Binds private bodies.

What this law does

The Virginia Attorney General has exclusive authority to enforce VCDPA. Before suing, the Attorney General must give an alleged violator 30 days' written notice identifying the specific provisions violated; this cure right carries no sunset date in the text, unlike several peer states'. The Attorney General may seek an injunction and civil penalties of up to $7,500 per violation. The chapter creates no private right of action.

What it requires

Sensitive categories

Employer limits on genetic testing and genetic characteristics

Va. Code Ann. § 40.1-28.7:1Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

No employer may request, require, solicit or administer a genetic test to any person as a condition of employment. No employer may refuse to hire, fail to promote, discharge or otherwise adversely affect the terms or conditions of employment of an employee or prospective employee solely on the basis of a genetic characteristic or the results of a genetic test, regardless of how the employer obtained the information or results.

Section 40.1-28.7:1 of the Code of Virginia does not preclude the use of information related to a criminal investigation. An employee may sue the employer that took adverse action within 180 days of the adverse action, and the court may award actual or punitive damages, including back pay with interest, or injunctive relief. The section does not require the Department of Labor and Industry to conduct any investigations or enforcement actions.

Section 40.1-28.7:1 of the Code of Virginia excludes any long term care, life or disability insurance policy from the terms and conditions of employment to which subdivision A 2 applies. Section 40.1-2.1 of the Code of Virginia provides that the provisions of Title 40.1 do not apply to the Commonwealth, its agencies, institutions or political subdivisions, or any public body, unless coverage is extended by specific regulation of the Commissioner or the Board. The section took effect on .

What it requires

Genetic Data Privacy

Va. Code Ann. §§ 59.1-593 to 59.1-602Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds public and private bodies.

What this law does

Binds a direct-to-consumer genetic testing company, an entity that offers consumer-initiated genetic testing products or services directly to a consumer or collects, uses or analyzes genetic data collected or derived from such a product or service and directly provided by a consumer.

The chapter does not apply to protected health information collected, maintained, used or disclosed by a covered entity or business associate governed by the federal Health Insurance Portability and Accountability Act (HIPAA) privacy, security and breach notification rules.

A company must obtain a consumer's express consent for the collection, use and disclosure of genetic data, with separate express consent for the use of the data collected, for storing the biological sample after the initial testing, for each use beyond the primary purpose, for each transfer to a third party other than a service provider, and for marketing.

On revocation of consent a company must honor the revocation within 30 days of receipt and destroy the consumer's biological sample within 30 days of receipt of revocation of consent to store it. A company must keep reasonable security procedures and practices and procedures that let a consumer access and delete the consumer's genetic data and request destruction of the biological sample.

A company may not disclose a consumer's genetic data to an entity responsible for administering or making decisions about health, life, long-term care or disability insurance or employment without the consumer's express consent. Only the Attorney General may enforce the chapter. A violation carries a civil penalty of up to $1,000, and a willful violation a civil penalty of $1,000 to $10,000, each plus attorney fees, expenses and court costs. The chapter took effect on .

What it requires

Health records privacy: disclosure by health care entities

Va. Code Ann. § 32.1-127.1:03Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds public and private bodies.

What this law does

A health care entity is any health care provider, health plan or health care clearinghouse. No health care entity, or other person working in a health care setting, may disclose an individual's health records except when the section or other provisions of state law permit or require it.

Within 30 days of receiving a request for copies of or electronic access to health records, the health care entity must furnish them, say that the information does not exist or cannot be found, name the entity that maintains it, or deny the request on a ground the section lists. A person to whom health records are disclosed may not redisclose them beyond the purpose of the disclosure without first obtaining the individual's specific authorization.

The section does not apply to the health records of minors except where it specifically provides, to information governed by the workers' compensation sections 65.2-604 and 65.2-607, or to releases of juvenile health records to a secure facility or of health records to a correctional facility. An individual who requests a copy of a health record may be charged only a reasonable cost-based fee covering supplies, copying labor, postage and the preparation of an agreed summary.

Section 32.1-27(A) of the Code of Virginia makes a willful violation of any provision of Title 32.1 a Class 1 misdemeanor unless a different penalty is specified. Section 32.1-27(B) of the Code of Virginia lets the Board of Health or the Commissioner compel a person violating any provision of Title 32.1 to comply by injunction, mandamus or other appropriate remedy in an appropriate court. The section took effect on . The section's history note lists Chapter 248 of the 2026 Acts of Assembly as its most recent amending act.

What it requires

Insurance: genetic information privacy in accident and sickness insurance

Va. Code Ann. § 38.2-508.4Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

No person proposing to issue, re-issue or renew an accident and sickness insurance policy, contract or plan, other than disability income insurance, of an insurer providing hospital, medical and surgical or major medical coverage on an expense incurred basis, a health services plan corporation or a health maintenance organization may use genetic information to restrict, cancel, refuse to renew or exclude coverage, impose a waiting period or rider, or set premium differentials.

Genetic information means information about genes, gene products, or inherited characteristics that may derive from an individual or a family member. An agent's or agency's fees or commissions may not be discriminated on the basis of a person's genetic characteristics that may be associated with disability in that person or that person's offspring.

Section 38.2-508.4(C) makes information obtained from genetic screening or testing conducted before the repeal of the section confidential and bars its use to cancel, refuse to issue or renew, or limit benefits under a covered policy, contract or plan.

The State Corporation Commission may examine and investigate each person subject to the chapter on unfair trade practices to determine whether the person has engaged in an unfair method of competition or an unfair or deceptive act or practice the chapter prohibits. Section 38.2-218 of the Code of Virginia punishes a knowing or willful violation of any provision of Title 38.2 by a penalty of not more than $5,000 for each violation. The section took effect on .

What it requires

Personal Information Privacy Act: restricted use of social security numbers

Va. Code Ann. § 59.1-443.2Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

Except as otherwise specifically provided by law, a person may not intentionally communicate another individual's social security number to the general public, print it on a card required to access or receive products or services, require its use to access an Internet website without another authentication device, or send a mailing that displays it.

No person may embed an encrypted or unencrypted social security number in or on a card or document, including by a bar code, chip, magnetic strip or other technology, in place of removing it. The section does not prohibit the collection, use or release of a social security number as permitted by the laws of the Commonwealth or the United States, or its use for internal verification or administrative purposes unless a state or federal statute, rule or regulation prohibits that use.

Section 59.1-443.2(C) of the Code of Virginia made the prohibition on printing a social security number on a card required to access products or services effective on for a health care provider, a manager of a pharmacy benefit plan, an insurer, a corporation providing a health services plan, a health maintenance organization providing a health care plan, or a contractor of any of them. The section does not apply to public bodies.

A violation of section 59.1-443.2 is a prohibited practice under the Virginia Consumer Protection Act. On a finding of a willful violation under the Consumer Protection Act, the Attorney General or an attorney for the Commonwealth or a locality may recover a civil penalty of not more than $2,500 per violation. A person who suffers loss as the result of a violation of the Consumer Protection Act may recover actual damages or $500, whichever is greater.

Chapter 562 of the 2008 Acts of Assembly (Senate Bill 133), relating to access to social security numbers, amended and reenacted section 59.1-443.2. Chapter 820 of the 2008 Acts of Assembly (House Bill 633), relating to access to social security numbers, amended and reenacted section 59.1-443.2. The section took effect on .

What it requires

SB 754 (2025), reproductive or sexual health information as a prohibited practice under the Consumer Protection Act

Va. Code Ann. 59.1-200(A)(85) (2025 Va. Acts ch. 591)official codified statute text, Code of Virginia (Legislative Information System), with the bill history for SB 754

In force since . Binds private bodies.

What this law does

The Virginia Consumer Protection Act declares unlawful the listed fraudulent acts or practices committed by a supplier in connection with a consumer transaction. One listed practice is obtaining, disclosing, selling, or disseminating any personally identifiable reproductive or sexual health information without the consent of the consumer.

Reproductive or sexual health information includes efforts to research or obtain related services or supplies, including location information that may indicate an attempt to acquire them. It also includes information derived or extrapolated from non-health data by proxy, inference, or algorithm. The prohibition does not apply to nonpublic personal information subject to the Gramm-Leach-Bliley Act. The definition leaves out health information protected by Health Insurance Portability and Accountability Act (HIPAA). SB 754 was approved , as Chapter 591 of the 2025 Acts of Assembly, effective .

What it requires

School service providers and school-issued devices: student personal information

Va. Code Ann. § 22.1-289.01Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds public and private bodies.

What this law does

A school service is a website, mobile application or online service that is designed and marketed primarily for use in elementary or secondary schools, is used at the direction of school employees or by a school-affiliated entity, and collects and maintains, uses or shares student personal information. A school service provider is an entity that operates a school service under a contract with a local school division in the Commonwealth.

Each school service provider or school technology provider must provide clear information about the student personal information it collects, maintain a privacy policy, maintain a comprehensive information security program, and facilitate access to and correction of the information. Each provider must collect, maintain, use and share student personal information only with the consent of the student or, if under 18, the parent, or for the purposes the contract with the school division authorizes.

No provider may knowingly use or share student personal information for targeted advertising to students or sell it, except to a successor entity. A school service provider in operation on is not subject to the section until the contract to operate a school service is renewed. Chapter 728 of the 2015 Acts of Assembly added the section to Article 5 of Chapter 14 of Title 22.1 of the Code of Virginia. Chapter 728 of the 2015 Acts of Assembly took effect on .

Chapter 438 of the 2016 Acts of Assembly (House Bill 749) amended and reenacted section 22.1-289.01, relating to school service providers. House Bill 749 of the 2016 Regular Session defined targeted advertising and clarified that the section does not prohibit school service providers from disclosing student personal information to ensure legal or regulatory compliance, protect against liability, or protect the security or integrity of the school service.

The enrolled text of House Bill 749 of 2016 changes the definition of a school service from one designed and marketed solely for use in elementary or secondary schools to one designed and marketed primarily for that use. Chapter 439 of the 2016 Acts of Assembly (House Bill 750) amended section 22.1-289.01 in relation to school services and college and career readiness assessment.

Chapter 468 of the 2016 Acts of Assembly (House Bill 519) amended section 22.1-289.01 in relation to school-affiliated entities. Chapter 518 of the 2017 Acts of Assembly (Senate Bill 951) amended section 22.1-289.01 in relation to student access to collected personal information. Chapter 364 of the 2025 Acts of Assembly (Senate Bill 1486) established requirements for the protection of student personal information on school-issued devices. Chapter 364 of the 2025 Acts of Assembly took effect on .

What it requires

Virginia Consumer Data Protection Act, sensitive data and biometric data definitions

Va. Code Ann. § 59.1-575official Virginia statute text, Title 59.1 Chapter 53, Code of Virginia

In force since . Binds private bodies.

What this law does

VCDPA classifies the processing of genetic or biometric data to uniquely identify a person, along with racial or ethnic origin, religious belief, a mental or physical health diagnosis, sexual orientation, citizenship or immigration status, precise geolocation, and a known child's data, as sensitive data requiring prior opt-in consent.

'Biometric data' means data from automatic measurement of an individual's biological characteristics used to identify them, such as a fingerprint, voiceprint, or eye retina or iris pattern, but the definition carries a blanket, unconditional exclusion for a photograph, video or audio recording, or data generated from either, with no clawback for data generated to identify someone.

A faceprint or voiceprint extracted from a recording for identification purposes therefore falls outside both biometric data and sensitive data under this Act.

What it requires

Scraping law2 instruments, 2 in force

Research summary (288 words)

Virginia diverges from the federal baseline in two ways: its computer trespass statute is narrower than a bare without-authorization test, since it also requires malicious intent or intentionally deceptive means; and the Virginia Consumer Data Protection Act (VCDPA), the first comprehensive state privacy law in the country, was reported amended in 2026 to flatly ban the sale of precise geolocation data rather than merely requiring consent.

Copyright, text-and-data-mining, and database rights are federal only, including the unresolved question of whether commercial text-and-data-mining is fair use; Virginia adds nothing there. No Virginia statute specifically governs AI-training data.

VCDPA's current codification runs from section 59.1-575 (Chapter 53's own definitions section) to section 59.1-584 (its enforcement section); section 59.1-571, sometimes cited as its start, is now the Humane and Toxin-Free Cosmetics Act's definitions section, and section 59.1-585 is a repealed placeholder.

ToS enforceability turns on Virginia's own Uniform Computer Information Transactions Act rather than judge-made doctrine alone: clicking to accept terms during signup binds the signer or an automated agent acting for it, while terms posted only behind a link bind a crawler only if presented in a way that would call them to a reasonable person's attention, and the computer trespass statute's own text keeps this a separate, civil track.

Virginia's Consumer Protection Act and common-law trespass to chattels, which Virginia's own courts have applied to unauthorized computer-network intrusion that measurably burdens a server's capacity, are available in principle for unfair competition, untested against scraping specifically.

No mechanism in Virginia law gives robots.txt independent legal force, and no Virginia authority has addressed whether disregarding a robots.txt directive can itself supply the computer trespass statute's authority or intent elements, so continuing to crawl pages a robots.txt file disallows is unsettled here.

Computer misuse

Virginia Computer Trespass, malicious intent or deceptive means requirement

Va. Code Ann. § 18.2-152.4official text, Virginia Law (law.lis.virginia.gov)

In force. Binds public and private bodies.

What this law does

Section 18.2-152.4(A) makes it unlawful for any person, with malicious intent or through intentionally deceptive means and without authority, to remove, disable, alter, damage, or otherwise interfere with computer data, programs, software, or operation.

The section applies to a person who acts with malicious intent, or through intentionally deceptive means and without authority, so ordinary unauthenticated, non-deceptive, non-malicious automated access to a public page that performs none of the listed disruptive acts does not fit the statute's elements at all, regardless of authorization; no Virginia case law was found applying it to a scraping or automated-collection fact pattern specifically.

Subsection (C) expressly states the statute is not to be construed to interfere with or prohibit terms or conditions in a contract or license related to computers or computer services, preserving ordinary contract law as the separate track for ToS enforcement; no Virginia case addresses browsewrap versus clickwrap for a scraping dispute specifically. No day on which the section came into force has been located.

Among the acts subsection A bars, subdivision A 8 lists installing or causing to be installed, or collecting information through, computer software that records all or a majority of the keystrokes made on the computer of another.

Among the acts subsection A bars, subdivision A 9 lists installing or causing to be installed on the computer of another computer software for the purpose of taking control of that computer so that it can cause damage to another computer, or disabling or disrupting the ability of the computer to share or transmit instructions or data to other computers or to related computer equipment or devices. If a person violates subdivision A 8 with malicious intent, the offense is a Class 6 felony.

The section is not to be construed to prohibit the monitoring of the computer usage of, the otherwise lawful copying of data of, or the denial of computer or Internet access to a minor by a parent or legal guardian of the minor.

What it requires

Personal data

Virginia Consumer Data Protection Act (VCDPA)

Va. Code Ann. §§ 59.1-575 to 59.1-584official text, Virginia Law (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

VCDPA, the first comprehensive state consumer privacy law in the country, defines personal data to exclude de-identified data and publicly available information, meaning information lawfully made available through government records, or that a business has a reasonable basis to believe is lawfully made available to the general public through widely distributed media, by the consumer, or by a person to whom the consumer has disclosed the information, unless the consumer has restricted it to a specific audience; this reaches most scraped public personal data outside VCDPA's coverage at the definitional level.

Enforcement is by the Attorney General exclusively; the Act expressly states that nothing in it shall be construed as providing the basis for, or be subject to, a private right of action. This Act is sometimes cited as sections 59.1-571 to 59.1-585, which is wrong: section 59.1-571 is currently the definitions section of the unrelated Humane and Toxin-Free Cosmetics Act (Title 59.1, Chapter 52), and section 59.1-585 is a repealed placeholder.

VCDPA's actual current codification, confirmed directly against the official Virginia Law site, runs from section 59.1-575 (Chapter 53's own definitions section) to section 59.1-584 (its enforcement section).

In 2026, the General Assembly passed and Governor Spanberger signed SB 338 (signed , effective , per contemporaneous legal commentary), replacing VCDPA's prior consent-based treatment of precise geolocation as sensitive data with an outright ban on selling a consumer's precise geolocation data; the enrolled text of SB 338 is not reproduced in the official code copy cited here, so its effective date and exact mechanism rest on that commentary.

What it requires

Cybersecurity law3 instruments, 3 in force

Research summary (798 words)

Virginia's product-security and cyber-resilience posture for the private-sector duty-bearer this profile targets is thin: the one enacted instrument that reaches this shape of duty is the Insurance Data Security Act and its Bureau of Insurance regulation, filed as rows of their own, and every other candidate located in the primary text consulted here is either out of this profile's private-sector scope, already this jurisdiction's privacy-topic row, or an unenacted proposal.

No enacted Virginia statute is confirmed in the primary text consulted here to set security requirements a connected device or software product must meet before or after it is placed on the market, comparable to California's or Oregon's connected-device statutes; a bill proposing a manufacturer duty to equip a connected device with reasonable security features and to remediate a vulnerability affecting more than 500 consumers has been introduced in the General Assembly without being enacted, so this is treated as a researched absence rather than a gap in coverage.

Virginia has no general private-sector duty to report an exploited vulnerability or a security incident to an authority: Va. Code Ann. section 2.2-5514 (Chapter 55.3, Title 2.2, added by the 2022 Session's S.B. 764) requires every public body, not a private business, to report a cybersecurity incident to the Virginia Fusion Intelligence Center within 24 hours of discovery and separately bars a public body from procuring hardware, software, or services the U.S. Department of Homeland Security has prohibited on federal systems, and it is filed as a row of its own with no activity flag.

The Virginia Insurance Data Security Act, Va. Code Ann. sections 38.2-621 to 38.2-629 (Article 2 of Chapter 6, Title 38.2, added by 2020, c. 264 and effective , modeled on the NAIC Insurance Data Security Model Law), requires a licensee, any person licensed, authorized to operate, or required to be licensed under Virginia's insurance laws, to develop, implement, and maintain a written information security program (section 38.2-623), investigate a cybersecurity event (section 38.2-624), notify the Commissioner within three business days of determining a qualifying cybersecurity event has occurred (section 38.2-625), and notify affected consumers (section 38.2-626), enforced exclusively by the State Corporation Commission's Bureau of Insurance (section 38.2-627) under an act that neither creates nor curtails a private cause of action (section 38.2-622).

No standalone reasonable-security or information-security-program statute binds a Virginia business generally, outside the Consumer Data Protection Act's own clause: Va. Code Ann. section 59.1-578(A)(3) requires a controller to establish, implement, and maintain reasonable administrative, technical, and physical data security practices appropriate to the volume and nature of the personal data at issue, but that is the comprehensive privacy regime's own security-of-processing article and is already this jurisdiction's privacy-topic row rather than repeated here.

Virginia's Personal Information Privacy Act, Va. Code Ann. sections 59.1-442 to 59.1-444 (Title 59.1, Chapter 35), restricts a merchant's sale of purchaser information, use of a Social Security number, and scanning of a driver's license, arming an aggrieved person with $100-per-violation statutory damages under section 59.1-444, but the primary text imposes no general duty to maintain reasonable security or to safeguard the information it restricts, so it is a collection-and-disclosure restriction rather than a security-posture duty and does not supply this jurisdiction's analog to New York's SHIELD Act 899-bb or Colorado's C.R.S. 6-1-713.5.

Virginia has not enacted a cybersecurity safe-harbor affirmative defense of the kind Ohio, Utah, Iowa, Connecticut, Oregon, Tennessee, and Texas have.

Virginia's breach-notification duty, Va. Code Ann. section 18.2-186.6 (Title 18.2, Chapter 6), is already this jurisdiction's privacy-topic row rather than repeated here: it requires notice to the Office of the Attorney General and any affected Virginia resident without unreasonable delay, and it carries no companion safeguards-and-disposal duty of its own comparable to New York's, Delaware's, Indiana's, or Louisiana's split of that shape: its own text states no security-program or records-destruction obligation.

Section 38.2-623 of the Code of Virginia requires each licensee under the Insurance Data Security Act to develop, implement, and maintain a comprehensive written information security program based on its assessment of its risk. Section 38.2-624 of the Code of Virginia requires a licensee that learns a cybersecurity event has or may have occurred to conduct a prompt investigation.

Section 14VAC5-430-40 of the Virginia Administrative Code requires each licensee to conduct a periodic risk assessment, with compliance required on or before . Section 14VAC5-430-50 of the Virginia Administrative Code requires each licensee to implement appropriate security measures based on its risk assessments, including protecting nonpublic information by encryption or other appropriate means while it is transmitted over an external network.

Section 2.2-5514 of the Code of Virginia requires every public body to report incidents that threaten the security of the Commonwealth's data or communications to the Virginia Fusion Intelligence Center within 24 hours from when the incident was discovered.

Sector security regimes

Insurance Data Security Act: information security program and investigation of a cybersecurity event

Va. Code Ann. §§ 38.2-623 and 38.2-624Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds private bodies.

What this law does

Each licensee must develop, implement, and maintain a comprehensive written information security program, based on its assessment of its risk, that contains administrative, technical, and physical safeguards for the protection of nonpublic information and its information system.

Each licensee must establish a written incident response plan designed to promptly respond to, and recover from, any cybersecurity event that compromises the confidentiality, integrity, or availability of nonpublic information in its possession, its information systems, or the continuing functionality of any aspect of its business or operations.

Beginning , a licensee that uses a third-party service provider must exercise due diligence in selecting it and require it to implement appropriate administrative, technical, and physical measures to protect and secure the information systems and nonpublic information that are accessible to, or held by, the provider.

Beginning in 2023, each insurer domiciled in the Commonwealth must submit to the Commissioner by February 15 each year a written statement certifying that it is in compliance with section 38.2-623, any rules adopted under the article, and any requirements prescribed by the Commission. A licensee that learns that a cybersecurity event has or may have occurred must conduct a prompt investigation, or have an investigator conduct one.

Each licensee must maintain records concerning all cybersecurity events for a period of at least five years from the date of the event and produce those records upon demand of the Commissioner.

A licensee is any person licensed, authorized to operate, or registered, or required to be licensed, authorized, or registered under the insurance laws of the Commonwealth, other than a purchasing group or a risk retention group chartered and licensed in another state or a person acting as an assuming insurer domiciled in another state or jurisdiction.

A licensee subject to Health Insurance Portability and Accountability Act (HIPAA) that maintains an information security program under it is considered to meet section 38.2-623 if it is compliant, submits a written statement certifying its compliance, and certifies that it will protect nonpublic information not subject to HIPAA in the same manner as information that is subject to HIPAA.

A licensee affiliated with a depository institution that maintains a program in compliance with the Interagency Guidelines Establishing Standards for Safeguarding Customer Information is considered to meet section 38.2-623 if it produces, on request, documentation satisfactory to the Commissioner that independently validates the depository institution's program.

What it requires

Insurance Data Security Risk Assessment and Reporting regulation: risk assessment and security measures

14VAC5-430-40 and 14VAC5-430-50 (Virginia Administrative Code)Official text of the Virginia Administrative Code, Title 14, Agency 5 (State Corporation Commission, Bureau of Insurance), Chapter 430

In force since . Binds private bodies.

What this law does

Each licensee must conduct a periodic risk assessment that identifies reasonably foreseeable internal or external threats to nonpublic information, assesses the likelihood and potential damage of those threats, and assesses the sufficiency of the safeguards in place. An assessment conducted in accordance with the objectives of the most current revision of National Institute of Standards and Technology (NIST) SP 800-30, NIST SP 800-39, or another substantially similar standard meets the requirements for a periodic assessment.

Each licensee must implement appropriate security measures based on its risk assessments, including protecting by encryption or other appropriate means all nonpublic information while it is transmitted over an external network.

Effective , a licensee that uses a third-party service provider must exercise due diligence in selecting it and require it to implement appropriate administrative, technical, and physical measures to protect and secure the information systems and nonpublic information that are accessible to, or held by, the provider. Compliance with the risk assessment requirement was required of all licensees on or before .

The chapter sets out rules to carry out the Insurance Data Security Act and sets minimum standards for risk assessment and security standards required of all licensees. Section 14VAC5-430-50 derives from Virginia Register Volume 37, Issue 21, effective , and was amended effective .

What it requires

Vulnerability and incident reporting

Public bodies: incident reporting to the Virginia Fusion Intelligence Center

Va. Code Ann. § 2.2-5514Official codified statute text, Code of Virginia (law.lis.virginia.gov)

In force since . Binds government bodies.

What this law does

Every public body must report all known incidents that threaten the security of the Commonwealth's data or communications or result in exposure of data protected by federal or state laws, and other incidents compromising the security of the public body's information technology systems with the potential to cause major disruption to normal activities of the public body or other public bodies.

Such reports must be made to the Virginia Fusion Intelligence Center within 24 hours from when the incident was discovered. The Virginia Fusion Intelligence Center shares such reports with the Chief Information Officer or the Chief Information Officer's designee at the Virginia Information Technologies Agency promptly upon receipt.

A public body means any legislative body, any court of the Commonwealth, any authority, board, bureau, commission, district, or agency of the Commonwealth, any political subdivision of the Commonwealth, and other organizations, corporations, or agencies in the Commonwealth supported wholly or principally by public funds.

No public body may use, directly or through work with or on behalf of another public body, any hardware, software, or services that have been prohibited by the United States Department of Homeland Security for use on federal systems.

What it requires

Communications law5 instruments, 5 in force

Research summary (429 words)

Virginia makes it a felony to intercept a wire, electronic or oral communication, but not where the person intercepting is a party to it or one of its parties has given prior consent, so one party's consent is enough.

A person whose communication is intercepted, disclosed or used in violation of the chapter may sue for actual damages or liquidated damages of $400 a day or $4,000, whichever is higher, doubled for a communication between spouses and in several professional relationships, plus punitive damages and fees.

No person may install or use a pen register or trap and trace device without a court order, and every exception, the user-consent one included, belongs to a provider of wire or electronic communication service.

The Virginia Telephone Privacy Protection Act sets calling-hour, identification, caller-identification and abandoned-call duties on a telephone or text-message solicitation to a Virginia number or resident, and bars a solicitation to a number whose occupant has asked not to be contacted or that is on the National Do Not Call Registry; an aggrieved natural person may sue for $500 for a first violation, $1,000 for a second and $5,000 for each later one.

Since , a recipient stops text-message solicitations by replying UNSUBSCRIBE or STOP. A separate Automatic Dialing-Announcing Devices Act requires the subscriber's consent, or a live operator's disclosure followed by consent, before a prerecorded or synthesized sales message plays, and a five-second disconnect, enforced under the Virginia Consumer Protection Act.

Sending unsolicited commercial email is not itself an offense, but falsifying or forging its transmission or routing information is, a misdemeanor that becomes a felony at high volume or revenue, with a civil action for an injured recipient or email provider; the prohibition is framed as a rule against falsified or forged transmission information, the kind of state email rule the federal CAN-SPAM Act's preemption clause leaves in force.

Virginia's Consumer Data Protection Act separately gives a consumer a right to opt out of processing personal data for targeted advertising, a privacy-law right covered with the state's privacy law. Section 18.2-60.5 of the Code of Virginia makes it a Class 1 misdemeanor to install or place an electronic tracking device through intentionally deceptive means and without consent, or to cause one to be installed or placed that way, and to use it to track the location of any person.

The offense does not apply to an electronic communications provider to the extent the installation, placement or use is disclosed in the provider's terms of use, privacy policy or similar document made available to the customer.

Commercial messages

Virginia Transmission of Unsolicited Commercial Electronic Mail Statute

Va. Code 18.2-152.3:1, 18.2-152.12Official statute text, Code of Virginia, Computer Crimes article

In force. Binds public and private bodies.

What this law does

Virginia law defines spam as unsolicited commercial electronic mail, excluding mail sent to a recipient with whom the sender has an existing business or personal relationship. Electronic mail an organization sends to its members is not spam for the civil action.

Sending spam is not itself an offense under this statute; using a computer or computer network with intent to falsify or forge electronic mail transmission or other routing information in connection with transmitting spam through or into an electronic mail service provider's network or its subscribers, or knowingly selling, giving, distributing or possessing with intent to distribute software primarily designed, of limited other commercial use, or marketed to enable that falsification, is a Class 1 misdemeanor.

The falsification offense becomes a Class 6 felony where the volume of spam transmitted exceeds 10,000 attempted recipients in 24 hours, 100,000 in 30 days, or 1,000,000 in a year, or where the revenue from a single transmission exceeds $1,000 or the total revenue from all spam sent to one electronic mail service provider exceeds $50,000, and knowingly using a minor to help transmit spam in such a felony is also a Class 6 felony.

A person injured by a violation may recover damages and costs, and where the spam was sent in contravention of the authority granted or the policies set by the electronic mail service provider, and the sender knew of them or they were posted on the provider's website, the injured person may also recover attorney fees and costs and elect, in lieu of actual damages, the lesser of $10 for each spam message transmitted or $25,000 a day.

An electronic mail service provider injured the same way may elect to recover $1 for each intended recipient who is its end user, or $25,000 for each day an attempt is made, an amount a court may adjust for the number of complaints, the defendant's culpability and history, and its economic gain.

The prohibition is framed as a rule against falsified or forged transmission and routing information, the kind of state rule against falsity or deception in a commercial electronic mail message that the federal CAN-SPAM Act's preemption clause leaves in force. The sections this entry groups came into force on different days.

What it requires

Device storage and tracking consent

Virginia Pen Register and Trap and Trace Device Prohibition

Va. Code 19.2-70.1Official statute text, Code of Virginia, Interception of Wire, Electronic or Oral Communications chapter

In force. Binds public and private bodies.

What this law does

No person may install or use a pen register or a trap and trace device without first obtaining a court order under section 19.2-70.2.

A pen register is a device or process that records or decodes dialing, routing, addressing or signaling information transmitted by an instrument from which a wire or electronic communication is transmitted, and a trap and trace device is one that captures the incoming impulses identifying the originating number or other dialing, routing, addressing or signaling information; neither term reaches the contents of a communication.

A pen register does not include a device or process a provider or customer of a wire or electronic communication service uses for billing, or recording incident to billing, for the provider's communications services, or one a provider or customer of a wire communication service uses for cost accounting or similar purposes in the ordinary course of its business.

A court order is not required for a provider of electronic or wire communication service to use such a device in operating, maintaining and testing its service or protecting its rights or property or its users from abuse or unlawful use of the service, to record that a communication was initiated or completed to protect itself, another provider or a user from fraudulent, unlawful or abusive use of the service, or where the consent of the user of that service has been obtained.

All three exceptions, the user-consent one included, are exceptions for a provider; the section has none for anyone else. A knowing violation is a Class 1 misdemeanor, and the section states no civil action of its own. No day on which the section came into force has been located.

What it requires

Interception and recording consent

Virginia Wiretapping, Eavesdropping and Disclosure of Communications Statute

Va. Code 19.2-62, 19.2-69Official statute text, Code of Virginia, Interception of Wire, Electronic or Oral Communications chapter

In force. Binds public and private bodies.

What this law does

It is a Class 6 felony to intentionally intercept, or procure another person to intercept, a wire, electronic or oral communication, or to intentionally disclose or use its contents knowing or having reason to know they were obtained through interception. It is not a criminal offense for a person to intercept a communication where that person is a party to it or one of the parties has given prior consent, so one party's consent is enough and a business may record its own calls.

An oral communication is protected only where the speaker exhibits an expectation that it is not subject to interception under circumstances justifying that expectation. An electronic communication does not include a communication through a tone-only paging device, a communication from a device that tracks the movement of a person or object, or electronic funds transfer information a financial institution stores.

To intercept is to acquire the contents through an electronic, mechanical or other device, a term that excludes telephone equipment furnished by a provider, or by the subscriber for connection to the service, and used in the ordinary course of the subscriber's or user's business.

It is also not an offense to intercept an electronic communication made through a system configured so that it is readily accessible to the general public, to intercept several categories of radio communication, to use a pen register or trap and trace device as sections 19.2-70.1 and 19.2-70.2 allow, or for a provider of electronic communication service to record that a communication was initiated or completed to protect itself, another provider or a user from fraudulent, unlawful or abusive use of the service.

A person or entity providing an electronic communication service to the public must not intentionally divulge the contents of a communication while in transmission on its service to anyone other than an addressee, an intended recipient, or their agent. It may divulge them as the chapter's provider-employee exception or section 19.2-67 allows.

It may also divulge them with the lawful consent of the originator or an addressee or intended recipient, to a person who forwards the communication to its destination, or, where the contents were inadvertently obtained and appear to pertain to a crime, to a law-enforcement agency. Violating the provider-divulgence duty is a Class 1 misdemeanor.

Anyone whose communication is intercepted, disclosed or used in violation of the chapter has a civil action for actual damages but not less than liquidated damages of $400 a day of violation or $4,000, whichever is higher, doubled to $800 a day or $8,000 for a communication between spouses, an attorney and client, a licensed practitioner of the healing arts and patient, a licensed professional counselor, clinical social worker, psychologist or marriage and family therapist and client, or a clergy member and a person seeking spiritual counsel, plus punitive damages and a reasonable attorney fee and litigation costs.

The provisions this entry describes came into force on different days.

What it requires

Telephone contact

Virginia Automatic Dialing-Announcing Devices Act

Va. Code 59.1-518.1 to 59.1-518.4Official statute text

In force. Binds private bodies.

What this law does

A caller, a person who contacts or tries to contact a subscriber in Virginia by telephone, must not use an automatic dialing-announcing device (one that selects and dials telephone numbers and plays a prerecorded or synthesized voice message) to make a commercial telephone solicitation unless the subscriber has knowingly or voluntarily requested, consented to, permitted or authorized receipt of the message, or a live operator first discloses the sending entity's name, the message's purpose, the kinds of goods or services promoted and, if applicable, that the message seeks payment or a commitment of funds, and obtains the subscriber's consent before the solicitation is delivered.

A commercial telephone solicitation is an unsolicited call to a subscriber by a person who has had no prior business or personal relationship with the subscriber, made to solicit the purchase or the consideration of the purchase of goods or services; calls the Commonwealth or a political subdivision initiates for exclusively public purposes are excluded.

A caller using such a device, or any other device playing a prerecorded or synthesized voice message, must design and operate it to disconnect within five seconds after the called party ends the call. A violation is a prohibited practice under the Virginia Consumer Protection Act and subject to all of that Act's enforcement provisions.

Under that Act, a person who suffers loss as the result of a violation may recover actual damages or $500, whichever is greater, which the trier of fact may raise for a willful violation to not more than three times actual damages or $1,000, whichever is greater, plus reasonable attorney fees and court costs. On a willful violation, the Attorney General, an attorney for the Commonwealth or a local attorney may recover a civil penalty of not more than $2,500 for each violation. The chapter states no criminal penalty. No day on which the chapter came into force has been located.

What it requires

Virginia Telephone Privacy Protection Act

Va. Code 59.1-510 to 59.1-518.01Official statute text, Code of Virginia, Virginia Telephone Privacy Protection Act

In force. Binds private bodies.

What this law does

A telephone solicitation is a telephone call to a natural person's residence in Virginia, to a landline or wireless telephone with a Virginia area code, or to a telephone registered to a Virginia resident, or a text message to a wireless telephone with a Virginia area code or registered to a Virginia resident, made to offer or advertise property, goods or services for sale, lease, license or investment, including an extension of credit, or for a fraudulent purpose.

Chapter 626 of the 2025 Acts, effective , recast the Act's duties from telephone solicitation calls to telephone solicitations, and added that a recipient opts out of a text-message solicitation by replying UNSUBSCRIBE or STOP. A telephone solicitor must not initiate a telephone solicitation outside 8:00 a.m. to 9:00 p.m. local time at the contacted person's location without that person's prior consent.

On a telephone call, the solicitor must identify themselves by first and last name and name the person on whose behalf the solicitation is made promptly upon making contact.

Every solicitation must transmit the solicitor's telephone number, and its name where the carrier makes it available, and the number must let any individual ask during regular business hours not to receive solicitations; for a text message, a number that accepts a reply-text request not to receive future text messages satisfies this rule.

The solicitor must not act to prevent that transmission or cause false or misleading caller-identification information to display, though it may substitute the seller's name and customer service number. If no live sales representative is available within two seconds of the person's completed greeting on a telephone call, the solicitor must play a prerecorded message stating the name and telephone number of the person on whose behalf the solicitation was made.

A solicitor must not initiate a solicitation to a number whose occupant has said they do not want solicitations made by or for that seller, a request honored for at least ten years and made for a text message by replying UNSUBSCRIBE or STOP, or to a number on the National Do Not Call Registry.

It is an affirmative defense to a do-not-call claim that the defendant established and implemented, with due care, reasonable practices and procedures to prevent such solicitations, including using a version of the Registry obtained no more than 31 days before the call.

For the do-not-call rules only, a telephone solicitation does not include a call made with the person's prior express invitation or permission evidenced by a signed written agreement naming the party and the number, a call for a seller with an established business relationship with the person (a purchase or transaction in the preceding 18 months, or an inquiry or application in the preceding three months), or a call by a solicitor with a personal relationship to the person; the business-relationship and personal-relationship exemptions end once the person has said they do not want solicitations.

Those exemptions do not reach the calling-hour, identification, caller-identification or abandoned-call rules. A seller on whose behalf a solicitation is made and the solicitor who makes it are jointly and severally liable for a violation of the calling-hour, identification, caller-identification or do-not-call rules.

A solicitation is presumed made on the seller's behalf unless the seller shows by clear and convincing evidence that it neither retained nor requested the solicitor's calls and that they were made without its knowledge or consent.

An aggrieved natural person may sue a responsible person to enjoin a violation and recover $500 for a first violation, $1,000 for a second and $5,000 for each later violation, which a court may raise to as much as $5,000 for a willful first or second violation, plus reasonable attorney fees and court costs.

The Attorney General, an attorney for the Commonwealth or a locality's attorney may sue for the same damages for aggrieved persons, and on a willful violation a court may also assess a civil penalty of not more than $5,000 for each violation, paid into the Literary Fund or the locality's general fund. The sections this entry groups came into force on different days.

What it requires

Age gating law2 instruments, 1 in force, 1 blocked by a court

Research summary (140 words)

Virginia has required age verification for websites where a substantial portion of content is material harmful to minors since , a law that predates and survived the 2025 U.S. Supreme Court ruling in Free Speech Coalition v. Paxton upholding similar state laws.

A 2025 law requiring social media platforms to screen for minors under 16 and cap their daily use at one hour was set to take effect , but a federal court granted NetChoice a preliminary injunction in February 2026, and the state's appeal is pending at the Fourth Circuit. An App Store Accountability Act (SB 237, HB 757) was introduced in the 2026 General Assembly session but did not complete passage; HB 757 was continued to the next session in committee in February 2026. Virginia has not enacted a standalone age appropriate design code.

Adult content age verification (AV)

SB 1515 (2023), civil liability for Internet publication of material harmful to minors

Va. Code § 8.01-40.5 (2023 Va. Acts c. 811)official Code of Virginia text

In force since . Binds private bodies.

What this law does

Commercial entities that knowingly publish or distribute material harmful to minors on websites containing a substantial portion of such material, as the Act defines that term, must verify that visitors are 18 or older using a commercially available age verification database or another commercially reasonable method.

What it requires

Social media and minors

SB 854 (2025), social media platforms; responsibilities and prohibitions related to minors

Va. Code § 59.1-577.1 (2025 Va. Acts c. 703)official Code of Virginia text and federal court memorandum opinion

Blocked by a court. blocked by a court A court paused enforcement on . An injunction can be lifted, so the duty may return.

Binds private bodies.

What this law does

Amends the Virginia Consumer Data Protection Act to require social media platforms to use commercially reasonable methods, such as a neutral age screen, to determine whether a user is under 16, and to limit such minors to one hour of daily use per platform unless a parent gives verifiable consent to change the limit.

What it requires

Our analysis of this law draws on 1 court ruling.Premium data

Where nothing was found1 area of law

These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.

Reuse law

No Virginia statute creates a press-publisher neighbouring right, a platform-to-publisher bargaining code, or a snippet-reproduction right distinct from federal copyright law as of the date shown.

Title 59.1's Virginia Antitrust Act (Va. Code Ann. §§ 59.1-9.1 through 59.1-9.18) carries no publisher-bargaining or collective-negotiation carve-out, and its Virginia Consumer Protection Act (§§ 59.1-196 through 59.1-207) carries no aggregation-specific duty; neither chapter mentions journalism, news, or publishers. No Virginia bill comparable to California's Journalism Preservation Act or the federal Journalism Competition and Preservation Act has been identified in the General Assembly.

Federal copyright law, including 17 U.S.C. § 301 preemption of state-law equivalents to a reproduction right and the hiQ v. LinkedIn and hot-news case line, governs a Virginia aggregator's treatment of headlines and snippets and is recorded in the federal document rather than restated here. No Virginia appellate decision recognizing a state common-law hot-news misappropriation claim for time-sensitive news content distinct from the general unfair-competition doctrine has been identified.

As of .

Reporting clocks that run here19 instruments

The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Virginia comes first, then the law of the bodies above it that applies here.

Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.

1 hour
Incident notificationsecurity law
4 hours
Incident notificationsecurity law
8 hours
Incident notificationsecurity law
36 hours
3 business days
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
4 business days
Incident notificationsecurity law
5 business days
Incident notificationsecurity law
7 business days
Breach notificationprivacy law
30 days
Incident notificationsecurity law
Breach notificationprivacy law
Safety-incident reportfrontier-model AI law
60 days
Breach notificationprivacy law
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.

The law of Virginia

24 hours

Public bodies: incident reporting to the Virginia Fusion Intelligence Center

Va. Code Ann. § 2.2-5514security law, in force since

The sentences the clocks are read from

Report to the Virginia Fusion Intelligence Center, within 24 hours from when the incident was discovered, all known incidents that threaten the security of the Commonwealth's data or communications or result in exposure of data protected by federal or state laws.

Report to the Virginia Fusion Intelligence Center, within 24 hours from when the incident was discovered, other incidents compromising the security of your information technology systems with the potential to cause major disruption to the normal activities of your public body or other public bodies.

3 business days

Insurance Data Security Act

Va. Code Ann. §§ 38.2-625 and 38.2-626privacy law, in force since

The sentences the clocks are read from

If you are a licensee (a person licensed, authorized to operate or registered, or required to be, under the insurance laws of the Commonwealth, other than a purchasing group or a risk retention group chartered in another state or an assuming insurer domiciled elsewhere) and you determine that a cybersecurity event has actually occurred, notify the Commissioner in electronic form as promptly as possible and no later than three business days after the determination if you are a domestic insurance company, or a producer whose home state is Virginia and the event meets the Commission's thresholds, or you reasonably believe the nonpublic information involved is of 250 or more consumers residing in Virginia, or you must notify any government body, self-regulatory agency or supervisory body under federal law or another state's law (section 38.2-625(A)).

Notify affected consumers without unreasonable delay after determining or receiving notice that a cybersecurity event occurred, where consumers' nonpublic information was accessed and acquired (or you reasonably believe it was) by an unauthorized person and the event has a reasonable likelihood of causing or has caused identity theft or other fraud, describing the incident, the type of information, your acts to protect it, a telephone number if one exists, and advice to review account statements and credit reports, and send the Commissioner a copy of the consumer notice (sections 38.2-626(A) and 38.2-625(D)).

Give notice to consumers in writing to the last known postal address, by telephone or electronically, using substitute notice only where the cost exceeds $50,000, the class exceeds 100,000 consumers or you lack sufficient contact information or consent, and where you notify more than 1,000 consumers at one time, also notify without unreasonable delay all nationwide consumer reporting agencies of the timing, distribution and content of the notice (section 38.2-626(B) and (C)).

Where the event occurs in a system a third-party service provider maintains, treat it as your own event unless the provider gives notice under the article, counting your deadlines from the day after the provider notifies you or you otherwise have actual knowledge; an assuming insurer must notify affected ceding insurers and the head of its domiciliary supervisory state agency within three business days, and an insurer must notify the producers of record of affected consumers as soon as practicable as the Commissioner directs (sections 38.2-625(E) to (G) and 38.2-626(F)).

without unreasonable delay

Breach of personal information notification

Va. Code Ann. § 18.2-186.6privacy law, in force

The sentence the clocks are read from

Notify the Virginia Office of the Attorney General and each affected Virginia resident of a breach of system security involving personal information without unreasonable delay after discovery.

The law of the United States, which applies in Virginia

1 hour4 hours8 hours24 hours

NRC cyber security event notifications by nuclear power plant licensees

NRC cyber security event notifications, 10 CFR 73.77security law, in force since

The sentences the clocks are read from

Notify the NRC Headquarters Operations Center via the Emergency Notification System within one hour after discovery of a cyberattack that adversely impacted safety-related or important-to-safety functions, security functions, or emergency preparedness functions (including offsite communications), or that compromised support systems and equipment resulting in adverse impacts to those functions.

Also notify within one hour after discovery of a cyberattack that adversely impacted the safety, security, and emergency preparedness functions performed by digital assets described in 10 CFR 73.77(a)(1)(ii).

Notify the NRC Headquarters Operations Center within four hours after discovery of a cyberattack that could have caused such an adverse impact, after discovery of a suspected or actual cyberattack initiated by personnel with physical or electronic access to the systems in scope, or after notifying a local, State, or other Federal agency of an event related to your cyber security program that does not otherwise require notification.

Notify the NRC Headquarters Operations Center within eight hours after receipt or collection of information regarding observed behavior, activities, or statements that may indicate intelligence gathering or pre-operational planning related to a cyberattack against the systems in scope.

Use the site corrective action program to record vulnerabilities, weaknesses, failures and deficiencies in your cyber security program, and the notifications you make, within twenty-four hours of their discovery.

24 hours72 hours

Cyber Incident Reporting for Critical Infrastructure Act of 2022 (CIRCIA)

6 U.S.C. 681-681g (CIRCIA)security law, enacted, not yet in force

The sentences the clocks are read from

Once the final rule takes effect, report a covered cyber incident to the Agency not later than 72 hours after your organization reasonably believes that the covered cyber incident has occurred.

Once the final rule takes effect, report a ransom payment to the Agency not later than 24 hours after your organization makes the payment, even where the underlying ransomware attack is not itself a covered cyber incident.

Once the final rule takes effect, promptly submit an update to a previously submitted covered cyber incident report whenever substantial new or different information becomes available or a ransom payment is later made, continuing until your organization notifies the Agency that the incident has concluded and been fully mitigated and resolved, and preserve data relevant to the incident or payment under the procedures the final rule establishes.

24 hours5 business days30 days

SEC Regulation SCI: notification of SCI events to the Commission and to members

SEC Regulation SCI SCI event notices, 17 CFR 242.1002(b) and (c)security law, in force since

The sentences the clocks are read from

Upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, begin appropriate corrective action and notify the Commission of the SCI event immediately.

Within 24 hours of that conclusion, submit a written notification to the Commission, made on a good faith, best efforts basis, that describes the SCI event and the systems affected and, to the extent available, your assessment of the market participants potentially affected, the potential impact on the market, and the steps you have taken, are taking or plan to take.

If the SCI event is resolved and the investigation closed within 30 calendar days, submit a final written notification within five business days after resolution. If not, submit an interim written notification within 30 calendar days after the event, and a final one within five business days after resolution and closure.

36 hours

Computer-Security Incident Notification Requirements for Banking Organizations and Their Bank Service Providers

12 CFR Part 53 (OCC); 12 CFR Part 225, Subpart N (Federal Reserve Board); 12 CFR Part 304, Subpart C (FDIC)security law, in force since

The sentences the clocks are read from

If your organization is a banking organization, notify your primary federal banking regulator, the OCC, the Federal Reserve Board, or the FDIC, whichever supervises it, about a notification incident, as soon as possible and no later than 36 hours after your organization determines that a notification incident has occurred.

A notification incident is the subset of computer-security incidents that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, your ability to serve customers, a business line, or an operation whose failure would threaten the financial stability of the United States, so a computer-security incident that falls short of that threshold does not by itself start this clock.

If your organization is a bank service provider, notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible after your organization determines that it has experienced a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services provided to that banking organization for a period of four hours or more.

This duty carries a standard, as soon as possible, rather than a fixed number of hours to notify by, and that disruption threshold is what engages the duty rather than a period to notify within.

72 hours30 days

Artificial Intelligence Risk Management and Security Act of 2026

S. 5576, 119th Congressfrontier-model AI law, proposed

The sentence the clocks are read from

If you are a developer or provider of a frontier AI model, or an operator of critical infrastructure that uses an AI model to manage industrial control systems or other operational technologies, report any confirmed AI safety incident or AI security incident within 30 days of confirmation, and within 72 hours if the incident poses an imminent threat to national security, critical infrastructure or public safety.

72 hours

NCUA Cyber Incident Notification Requirements for Federally Insured Credit Unions

NCUA Cyber Incident Notification Requirements, 12 CFR 748.1(c)security law, in force since

The sentences the clocks are read from

If your organization is a federally insured credit union, notify the NCUA-designated point of contact of a reportable cyber incident by email, telephone, or another method the NCUA prescribes, so that the NCUA receives the notification as soon as possible and no later than 72 hours after your organization reasonably believes it has experienced a reportable cyber incident.

Where the reportable cyber incident is a disruption of business operations or unauthorized access to sensitive data facilitated through, or caused by, a compromise of a credit union service organization, cloud service provider, or other third-party data hosting provider, or by a supply chain compromise, the NCUA must receive the notification within 72 hours of your organization being notified by the third party if that is sooner.

72 hours30 days

Regulation S-P: incident response program and customer breach notice

17 CFR 248.30(a)(3) to (a)(5)privacy law, in force since

The sentences the clocks are read from

Send the notice as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred, delaying it only for the period the United States Attorney General specifies where the Attorney General determines that notice poses a substantial risk to national security or public safety (17 CFR 248.30(a)(4)(iii)).

Maintain written policies and procedures reasonably designed to require oversight, including through due diligence and monitoring, of service providers, including that a service provider notify you as soon as possible, and no later than 72 hours, after becoming aware of a breach in security resulting in unauthorized access to a customer information system it maintains (17 CFR 248.30(a)(5)(i)).

72 hours

SEC Regulation S-P: service provider oversight and 72-hour breach notice to the covered institution

SEC Regulation S-P service provider oversight and notice, 17 CFR 248.30(a)(5)security law, in force

The sentence the clocks are read from

Make those policies and procedures reasonably designed to ensure that each service provider takes appropriate measures to protect against unauthorized access to or use of customer information, and to notify you as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system the service provider maintains.

4 business days

SEC Cybersecurity Risk Management, Governance, and Incident Disclosure (Regulation S-K Item 106; Form 8-K Item 1.05)

17 CFR 229.106; 17 CFR 249.308 (Form 8-K Item 1.05)security law, in force since

The sentences the clocks are read from

If your organization is an Securities and Exchange Commission (SEC) reporting company, determine, without unreasonable delay after you discover a cybersecurity incident, whether the incident is material, and if it is, file a Form 8-K under Item 1.05 within four business days after you make that determination.

If the information called for in Item 1.05 is not determined or is unavailable when you file, state that in the filing and file an amendment to the Form 8-K within four business days after you determine it or it becomes available.

7 business days30 days

FCC CPNI breach notification rule

47 CFR 64.2011privacy law, in force

The sentences the clocks are read from

After you reasonably determine that a breach of your customers' CPNI has occurred, electronically notify the United States Secret Service and the Federal Bureau of Investigation through the central reporting facility as soon as practicable, and in no event later than seven business days (47 CFR 64.2011(b)).

Do not notify customers or disclose the breach where the relevant investigating agency directs you in writing not to, for an initial period of up to 30 days that the agency may extend (47 CFR 64.2011(b)(3)).

60 days

FTC Health Breach Notification Rule

16 CFR Part 318privacy law, in force since

The sentences the clocks are read from

If you are a vendor of personal health records (an entity that offers or maintains an electronic record of health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual) or a PHR related entity, notify each affected individual who is a citizen or resident of the United States, in plain language and without unreasonable delay, no later than 60 calendar days after you discover a breach of security of unsecured PHR identifiable health information.

Notify prominent media outlets serving a State or jurisdiction, without unreasonable delay and in no case later than 60 calendar days after you discover the breach, when the unsecured PHR identifiable health information of 500 or more of its residents is, or is reasonably believed to have been, acquired during the breach.

If you are a third party service provider, notify the official designated in a written contract by the vendor of personal health records or PHR related entity you serve (or else a senior official of that vendor or entity), without unreasonable delay and in no case later than 60 calendar days after you discover the breach; identify each customer of that vendor or entity whose unsecured PHR identifiable health information has been, or is reasonably believed to have been, acquired during the breach; and obtain acknowledgment that the notice was received.

60 days

HIPAA Breach Notification Rule

45 CFR Part 164, Subpart D (Sections 164.400-164.414)privacy law, in force since

The sentences the clocks are read from

Notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured protected health information.

For a breach of unsecured protected health information involving more than 500 residents of a State or jurisdiction, notify prominent media outlets serving that State or jurisdiction without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

If you are a business associate, notify the covered entity of a breach of unsecured protected health information without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.

promptly

CFTC system safeguards: prompt notice to Commission staff of cyber security incidents and targeted threats

CFTC system safeguards notices, 17 CFR 39.18(g), 38.1051(e) and 37.1401(e)security law, in force since

The sentences the clocks are read from

If your organization is a derivatives clearing organization, notify staff of the Division of Clearing and Risk promptly of any hardware or software malfunction, security incident, or targeted threat that materially impairs, or creates a significant likelihood of material impairment of, automated system operation, reliability, security, or capacity, and of any activation of your business continuity and disaster recovery plan.

If your organization is a designated contract market, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and significant systems malfunctions and activations of your business continuity-disaster recovery plan.

If your organization is a swap execution facility, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and material system malfunctions and activations of your business continuity-disaster recovery plan.

immediately

Coast Guard Cybersecurity in the Marine Transportation System: reportable cyber incidents

Coast Guard reportable cyber incident reporting, 33 CFR 101.620(b)(7) and 101.615security law, in force since

The sentence the clocks are read from

Evidence of sabotage, subversive activity, or an actual or threatened cyber incident involving or endangering any vessel, harbor, port, or waterfront facility must be reported immediately to the Federal Bureau of Investigation, the Cybersecurity and Infrastructure Security Agency (for any cyber incident), and the Captain of the Port, or to their respective representatives.

Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

This page covers the instruments LexLint has researched to a stage. Instruments named in the law library but not yet researched are counted in the head and are not listed here. Every entry carries its own primary source on its note page. This is a research index, not legal advice.