West Virginia breach notification lookup
Use this West Virginia breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for West Virginia: statute citation, stated notification deadline, residents or regulators who may need notice, consumer-reporting-agency threshold, consumer-notice trigger, official source links, and the last verified date.
Last verified 2026-08-13. Not legal advice.
| Field | Verified value | Use in the incident file |
|---|---|---|
| Statute | W. Va. Code §§ 46A-2A-101 through 46A-2A-105 | Link the decision record to the official citation |
| Deadline | Resident notice without unreasonable delay after discovery or notification, subject to law-enforcement, civil-investigation, homeland-security, national-security, and scope/restoration delays; owner/licensee notice by data maintainers as soon as practicable; consumer-reporting-agency notice without unreasonable delay for more than 1,000 persons. | Sort multi-state response work by the shortest stated clock |
| Residents | West Virginia residents whose unencrypted and unredacted personal information was, or is reasonably believed to have been, accessed and acquired by an unauthorized person and whose breach caused or is reasonably believed to cause identity theft or other fraud. | Identify whether affected residents receive notice |
| Regulator | The reviewed West Virginia notice statute does not verify a separate routine Attorney General filing threshold, but the West Virginia Attorney General contact page lists DataBreachNotice@wvago.gov for notices of breach of security of computerized personal information requested to be provided to the state pursuant to W. Va. Code § 46A-2A-102. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify all nationwide consumer reporting agencies without unreasonable delay when the entity is required to notify more than 1,000 persons of a breach, excluding entities subject to the GLBA Title V consumer-reporting-agency notice path. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | West Virginia requires notice to nationwide consumer reporting agencies without unreasonable delay when an entity must notify more than 1,000 persons; the Attorney General's contact page provides a dedicated email address for breach notices requested to be provided to the state. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
West Virginia fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
W. Va. Code §§ 46A-2A-101 through 46A-2A-105 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
West Virginia requires notice to nationwide consumer reporting agencies without unreasonable delay when an entity must notify more than 1,000 persons; the Attorney General's contact page provides a dedicated email address for breach notices requested to be provided to the state. The consumer trigger matters because the clock usually starts only after a legally meaningful incident analysis, not merely because an IT alert appeared.
The last verified date for this West Virginia lookup is 2026-08-13. Use that date as a prompt to refresh counsel review before making a live notification decision.
How to use it during an incident
Start with containment and evidence preservation, then identify affected resident states and compare the shortest stated deadline first.
A practical incident file should record discovery time, encryption status, systems involved, affected consumer count, vendor involvement, and the person responsible for counsel review.
For West Virginia, the WISP should say where the notification decision log lives, who contacts counsel, who checks the regulator portal, and who approves any consumer notice before it is sent.
This lookup pairs with the Incident Response Plan because the plan owns the workflow: intake, escalation, containment, preservation, notice analysis, communications, and final review.
How it fits the WISP
A WISP should not guess at state-law outcomes; it should make the breach-review path fast, documented, and source-linked.
Pair this lookup with the West Virginia WISP requirements page so the firm's written program names the state-aware incident path before an event happens.
Policywright keeps the breach clock separate from the policy packet: the lookup tells you what to review, while the generated packet assigns owners, evidence records, remediation steps, and review cadence.
Not legal advice. A qualified lawyer should confirm whether the incident facts meet a statutory definition, whether substitute notice or regulator notice applies, and whether another state or federal rule changes the timeline.
FAQ
Is this West Virginia lookup legal advice?
No. It is a source-linked lookup for incident planning and should be reviewed with qualified counsel before relying on it in a live notification decision.
What if affected residents live outside West Virginia?
Use the multi-state lookup page and include every state where affected residents may live. The comparison table sorts selected states by the shortest stated deadline first.
Does this replace the FTC Safeguards Rule notice analysis?
No. State notice review is separate from the federal Safeguards Rule and 16 CFR 314.4(j) analysis. A serious incident file should preserve both review tracks.