Hawaii breach notification lookup
Use this Hawaii breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for Hawaii: 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 | Haw. Rev. Stat. § 487N-2 | Link the decision record to the official citation |
| Deadline | Affected-person notice without unreasonable delay after discovery or notification, subject to written or contemporaneously documented law-enforcement/national-security delay and scope/restoration needs; data maintainers notify owners or licensees immediately; OCP and consumer-reporting-agency notices apply for more than 1,000 persons at one time. | Sort multi-state response work by the shortest stated clock |
| Residents | Affected persons whose Hawaii personal information was involved in a security breach held by a covered business or government agency, including businesses conducting business in Hawaii that own or license personal information in any form. | Identify whether affected residents receive notice |
| Regulator | Notify the State of Hawaii Office of Consumer Protection in writing, without unreasonable delay, when a business provides notice to more than 1,000 persons at one time; Hawaii’s OCP is part of the Department of Commerce and Consumer Affairs and handles consumer protection enforcement. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify all nationwide consumer reporting agencies in writing, without unreasonable delay, when a business provides notice to more than 1,000 persons at one time, including the timing, distribution, and content of the notice. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | Hawaii requires written notice to the Office of Consumer Protection and all nationwide consumer reporting agencies without unreasonable delay when a business provides breach notice to more than 1,000 persons at one time. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
Hawaii fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
Haw. Rev. Stat. § 487N-2 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
Hawaii requires written notice to the Office of Consumer Protection and all nationwide consumer reporting agencies without unreasonable delay when a business provides breach notice to more than 1,000 persons at one time. 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 Hawaii 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 Hawaii, 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 Hawaii 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 Hawaii 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 Hawaii?
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.