South Carolina breach notification lookup
Use this South Carolina breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for South Carolina: 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 | S.C. Code Ann. § 39-1-90 | Link the decision record to the official citation |
| Deadline | Resident notice in the most expedient time possible and without unreasonable delay, subject to law-enforcement delay and scope/restoration needs; Department of Consumer Affairs and national credit reporting agency notices apply for 1,000+ South Carolina residents at one time. | Sort multi-state response work by the shortest stated clock |
| Residents | South Carolina residents whose personal identifying information was not rendered unusable through encryption, redaction, or other methods and was, or is reasonably believed to have been, acquired by an unauthorized person under the material-risk/illegal-use trigger. | Identify whether affected residents receive notice |
| Regulator | South Carolina routes large breach reporting to the Department of Consumer Affairs rather than the Attorney General; notify the Department when notice is sent to 1,000 or more South Carolina residents at one time, including breach date, awareness date, consumer notice date/method, resident count, notice copy, and corrective action. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify the national credit reporting agencies when notice is sent to 1,000 or more South Carolina residents at one time. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | South Carolina requires a business that sends data-security-breach notice to 1,000 or more South Carolina residents at one time to notify the Department of Consumer Affairs and the national credit reporting agencies. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
South Carolina fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
S.C. Code Ann. § 39-1-90 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
South Carolina requires a business that sends data-security-breach notice to 1,000 or more South Carolina residents at one time to notify the Department of Consumer Affairs and the national credit reporting agencies. 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 South Carolina 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 South Carolina, 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 South Carolina 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 South Carolina 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 South Carolina?
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.