Law / United States / U.S. Virgin Islands

U.S. Virgin Islands

2 of 5 named instruments researched to a stage, across two of the ten areas of law we track: 2 in force. As of .

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

in forcenot yet in forceblocked by a courtproposedno longer in force

Privacy law1 instrument, 1 in force

Research summary (89 words)

The United States Virgin Islands has no comprehensive private-sector data-protection statute and no dedicated privacy supervisory authority. Its personal-data law is limited to a security-breach notification duty at 14 V.I.C. §§ 2208-2209 (Title 14, Chapter 110, Subchapter I, Identity Theft), which requires notice to an affected territory resident following unauthorized acquisition of unencrypted personal information.

Section 2208 binds a government agency and Section 2209 binds any person or business conducting business in the territory in the same terms; neither section reaches biometric identifiers, other sensitive-category data, or cross-border transfer.

Breach notification

Disclosure of Breach of Security (Identity Theft and Privacy Protection)

14 V.I.C. §§ 2208-22092019 U.S. Virgin Islands Code, Title 14, Chapter 110, Subchapter I, Section 2209, reproduced by Justia (archived copy)

archived copyRead from a public archive copy, not the publisher directly. The publisher does not serve this page to automated readers, so a direct fetch was not an option here; how we access sources. Archived . Publisher's page: https://law.justia.com/codes/virgin-islands/2019/title-14/chapter-110/subchapter-i/2209/

In force. Binds public and private bodies.

What this law does

Any person or business that conducts business in the Virgin Islands and owns or licenses computerized personal information must disclose a breach of security to an affected territory resident without unreasonable delay following discovery, and Section 2208 imposes the identical duty on a Virgin Islands government agency.

Covered personal information is a resident's first name or initial and last name combined with an unencrypted Social Security number, driver's license number, or financial account, credit, or debit card number together with any required access code, and excludes information lawfully made available to the public through government records.

Where direct notice would cost more than $100,000, would reach more than 50,000 residents, or the covered entity lacks sufficient contact information, substitute notice by email, a conspicuous website posting, and notice to major territory-wide media satisfies the duty. No statement of the day the sections came into force has been located.

What it requires

Scraping law1 instrument, 1 in force

Research summary (226 words)

The United States Virgin Islands has no scraping-specific statute, so general law governs each dimension separately.

Its computer-crime chapter (14 V.I.C. §§ 461, 462, 464, Title 14, Chapter 22) reaches unauthorized- or fraud-purpose access, alteration, and copying of computer data, and its computer-trespass section applies with or without authority where the actor's intent matches an enumerated list that includes making an unauthorized copy of data from a computer or network; ordinary, non-fraudulent, non-disruptive automated reading of a public page does not fit any of these elements, and no reported case has applied the chapter to scraping or automated data collection.

No reported case addresses terms-of-service enforceability against a scraper in the territory; the trespass section itself preserves ordinary contract law as a separate track. As in every US jurisdiction, copyright, any text-and-data-mining exception, and database rights are federal only, and the territory's own code adds nothing there.

The territory's only personal-data statute is a security-breach notification duty (14 V.I.C. §§ 2208-2209, addressed under the privacy topic) rather than a general restriction on collecting publicly available personal data.

The territory's general Consumer Fraud and Deceptive Business Practices Act (12A V.I.C. §§ 303-331) is available in principle for unfair-competition or misappropriation claims but has not been tested against scraping specifically, and no statute or reported case assigns legal weight to a robots.txt directive or imposes an AI-training-specific rule.

Computer misuse

Virgin Islands Computer Crimes Act, unauthorized access and computer trespass

14 V.I.C. §§ 461, 462, 464 (Chapter 22, Computer Crimes)2019 U.S. Virgin Islands Code

In force. Binds public and private bodies.

What this law does

Section 464 (Computer trespass) makes it unlawful to use or access a computer or computer network of another, with or without authority, with intent to disable or alter data or programs, cause a malfunction, effect an unauthorized funds transfer, injure property, make an unauthorized copy of computer data in any form, or forge e-mail routing information for unsolicited bulk mail; unlike a bare unauthorized-access standard, the offense turns on the actor's listed intent rather than on whether access itself was authorized.

Section 461 makes it a felony, punishable as set out in section 467 of the same chapter, to knowingly and intentionally access or cause to be accessed a computer, computer system, or computer network to devise or execute a scheme to defraud, to obtain money, property, or services by false or fraudulent pretenses, or to damage, destroy, alter, delete, or remove a program or data in connection with a scheme to defraud.

Section 462 separately makes it a felony, punishable as set out in section 467 of the same chapter, to intentionally access, alter, damage, or destroy a computer, computer system, computer network, computer software, computer program, or its data, without authorization and for a fraudulent or other illegal purpose.

Section 464(b) expressly preserves an ordinary contract or license governing access to a computer service as a separate, civil matter, so a terms-of-service dispute is not itself resolved by this section. No statement of the day the sections came into force has been located.

What it requires

Where nothing was found4 areas 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.

AI law

No AI-transparency, risk-obligation, training-data, prohibited-practices, governance, or sector-specific AI statute was found in the United States Virgin Islands.

The territory's general Consumer Protection Law of 1973 (12A V.I.C. § 101) and Consumer Fraud and Deceptive Business Practices Act (12A V.I.C. § 304) apply to deceptive commercial conduct regardless of the technology used to carry it out, and the Attorney General invoked both in a December 2025 Superior Court of the Virgin Islands complaint against Meta alleging that its advertising and recommendation algorithms knowingly facilitated fraudulent advertising and youth-targeted addictive platform design, but neither statute imposes an AI-specific transparency, disclosure, or risk-management duty.

As of .

Cybersecurity law

The United States Virgin Islands has no statute or regulation setting security requirements a software product or connected device must meet before or after it reaches the market, no general duty running to an authority or a computer security incident response team (CSIRT) to report an exploited vulnerability or a security incident distinct from a personal-data breach, and no cyber-resilience regime comparable to NIS2, DORA, or an insurance-sector security model law binding an essential, important, critical, or financial entity was located in the sources read.

Its only law reaching the security of personal information is the security-breach notification pair at 14 V.I.C. §§ 2208-2209 (Title 14, Chapter 110, Subchapter I, captioned Identity Theft, inside the Crimes title's Theft chapter), under which a government agency (Section 2208) or any person or business conducting business in the territory (Section 2209) must notify an affected resident, in the most expedient time possible and without unreasonable delay, following discovery that the resident's unencrypted personal information was acquired, or is reasonably believed to have been acquired, by an unauthorized person.

Both sections define a breach as the unauthorized acquisition of computerized data compromising the security, confidentiality, or integrity of personal information, both permit substitute notice by email, website posting, and territory-wide media where direct notice would cost more than $100,000, would reach more than 50,000 residents, or the covered agency, person, or business lacks sufficient contact information, and both let a covered agency, person, or business satisfy the notice-timing requirement by following its own existing notification procedures where those procedures form part of an information-security policy addressing personal information, a permissive alternate compliance path for notice timing rather than an independent duty to adopt or maintain such a policy: nothing in either section requires a covered agency, person, or business to have one.

Neither section imposes administrative, technical, or physical safeguards, a written information security program, or any pre-breach security control, so the duty runs to the personal data and its exposure rather than to a product's, system's, or service's security posture, and that pair is already documented as this jurisdiction's privacy-topic row rather than repeated here.

Chapter 110 carries no second subchapter, and of its Subchapter I sections none beyond Sections 2208 and 2209 addresses security. The territory's separate computer-crimes chapter (14 V.I.C. §§ 461, 462, and 464), which criminalizes unauthorized access and computer trespass by an intruder, is documented under the scraping topic rather than here.

As of .

Age gating law

No adult-content age-verification, social-media minor-access, app-store age-verification, or age-appropriate design code statute was found in the United States Virgin Islands.

Title 14 (Crimes), the territory's criminal code, was reviewed by its complete table of contents: it carries Chapter 23A, the Computer Pornography and Child Exploitation Prevention Act (14 V.I.C. §§ 487-490), and Chapter 24, Child Protection (14 V.I.C. §§ 501-507), both of which criminalize child sexual exploitation rather than imposing an age-verification or age-gating duty on an online service; their operative text is not described here.

No chapter in Title 14's table of contents names an age-verification, social-media-minor, app-store, or design-code duty, and no such statute in another title has been located.

As of .

Reuse law

The United States Virgin Islands has no press-publisher neighbouring right, mandatory platform-to-publisher bargaining code, or codified hot-news misappropriation statute distinct from federal law. No Virgin Islands court decision addressing snippet reproduction, linking, framing, or a text-and-data-mining opt-out has been located.

Copyright over news content reproduced or aggregated in the territory is governed by the federal Copyright Act and its fair-use doctrine, already addressed in the federal document for this topic.

As of .

Case law

  • No current case law for U.S. Virgin Islands AI law
  • No current case law for U.S. Virgin Islands privacy law
  • No current case law for U.S. Virgin Islands scraping law
  • No current case law for U.S. Virgin Islands cybersecurity law
  • No current case law for U.S. Virgin Islands communications law
  • No current case law for U.S. Virgin Islands content moderation law
  • No current case law for U.S. Virgin Islands product and AI liability law
  • No current case law for U.S. Virgin Islands digital accessibility law
  • No current case law for U.S. Virgin Islands age gating law
  • No current case law for U.S. Virgin Islands reuse law

Reporting clocks that run here17 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 the U.S. Virgin Islands 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
72 hours
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 the U.S. Virgin Islands

The law of the United States, which applies in the U.S. Virgin Islands

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.