New Hampshire breach notification lookup
Use this New Hampshire breach notification lookup as an incident-triage clock, not as legal advice. It shows the fields Policywright has verified for New Hampshire: 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 | N.H. Rev. Stat. § 359-C:20 | Link the decision record to the official citation |
| Deadline | Promptly determine misuse likelihood after awareness of a breach; individual notice as soon as possible after the determination; maintainer notice and cooperation immediately after discovery if personal information was acquired by an unauthorized person; law-enforcement, national-security, or homeland-security delay may apply; CRA notice applies for more than 1,000 consumers. | Sort multi-state response work by the shortest stated clock |
| Residents | Affected New Hampshire individuals after a prompt determination finds that misuse of personal information occurred or is reasonably likely to occur, or when the person cannot determine whether misuse occurred or is reasonably likely. | Identify whether affected residents receive notice |
| Regulator | Notify the primary regulator if the person is subject to one; otherwise notify the New Hampshire Attorney General’s office, including the anticipated date of individual notice and approximate number of New Hampshire individuals to be notified, without providing names or personal information of the affected individuals. | Record AG or regulator portal review |
| Consumer-reporting agencies | Notify all nationwide consumer reporting agencies without unreasonable delay if notice is required for more than 1,000 consumers, including the anticipated date of consumer notice, approximate number of consumers, and notice content; this CRA provision does not apply to persons subject to GLBA Title V. | Check whether the affected count crosses a CRA threshold |
| Consumer trigger | New Hampshire requires regulator notice when individual notice will be sent: regulated persons notify their primary regulator, and all other persons notify the New Hampshire Attorney General’s office with the anticipated individual-notice date and approximate number of New Hampshire individuals to be notified. | Tie notice analysis to the statutory trigger, not an unsupported assumption |
What this state lookup shows
New Hampshire fields are rendered from the verified state dataset only when the field exists. No deadline is inferred when the data does not state one.
N.H. Rev. Stat. § 359-C:20 is the statute citation retained for this lookup, and the state page links to the official statute source when available.
New Hampshire requires regulator notice when individual notice will be sent: regulated persons notify their primary regulator, and all other persons notify the New Hampshire Attorney General’s office with the anticipated individual-notice date and approximate number of New Hampshire individuals to be notified. 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 New Hampshire 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 New Hampshire, 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 New Hampshire 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 New Hampshire 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 New Hampshire?
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.