Toolkit · Technology

The Data Privacy and Breach Response Toolkit

42 U.S.C. § 1320

Type
Toolkit
Jurisdiction
National
Date
2026-02-25
Topic
Technology

This toolkit supplies the working documents for a privacy program and for the incident that tests it. It opens with a data map template and an applicability worksheet, because coverage and scope determine everything downstream. Compliance sections supply a privacy notice outline, a consent design review that tests for dark patterns, a rights request intake form, an identity verification protocol, a response letter, and a deletion exception log. Vendor sections supply the processor contract clauses that matter most, including the breach notification deadline whose absence makes the controller's own deadline impossible. Assessment sections supply a data protection assessment template. Incident sections supply a first-hour card, a decision log, an encryption safe harbor analysis, a breach notice letter, and a regulator notification outline. Individual sections supply a rights request letter and the credit freeze steps. Closing sections supply a retention schedule, a tabletop exercise, and an annual audit.

The Data Privacy and Breach Response Toolkit

Technology > Data Privacy and Security | Published 25 February 2026 - Updated 16 August 2026 | UpLaw - uplaw.us

⚠ State privacy statutes differ in every material detail and are amended every session. ⭐ Conform every template to the specific statutes that apply, and re-check them annually.

Companion documents: Responding to a Data Breach and Exercising Privacy Rights: A Practical Checklist · Data Privacy and Security: A Comprehensive Guide to Collection, Consent, Breach Response, and Enforcement · The Data You Did Not Know They Had: How Privacy Law Actually Reaches Your Information


Tool 1 — Data map

⭐ Everything else in this toolkit depends on this table. Build it first.

System Business owner Data elements ⚠ Sensitive? Source Purpose Legal basis / notice reference Recipients Retention Location Encrypted at rest? In scope for rights requests?
☐ ☐ ☐

Systems people forget: ☐ Marketing automation and email platforms ☐ Customer support ticketing ☐ Analytics and product telemetry ☐ ⭐ Advertising pixels and software development kits embedded in the site and app ☐ Data warehouses and business intelligence tools ☐ Spreadsheets on shared drives ☐ Backups, snapshots, and disaster recovery copies ☐ Development and staging environments with production data ☐ Vendor-hosted systems ☐ Physical files and archived media ☐ Chat and collaboration platforms ☐ Voicemail and call recordings

⚠ The last five are where deletion requests and breach scoping both fail.


Tool 2 — Applicability worksheet

Question Answer Statute engaged
Do we handle protected health information as a provider, plan, clearinghouse, or business associate? ☐ 45 C.F.R. Part 160 · 45 C.F.R. Part 164 · ⚠ 42 U.S.C. § 1320d-6
Are we a financial institution or do we receive data from one? ☐ 15 U.S.C. § 6801 · 15 U.S.C. § 6802
Do we assemble or use consumer reports for credit, employment, insurance, or housing? ☐ 15 U.S.C. § 1681b · 15 U.S.C. § 1681e · 15 U.S.C. § 1681m
Is our service directed to children under thirteen, or do we have actual knowledge? ☐ 15 U.S.C. § 6501 · 15 U.S.C. § 6502
Do we handle education records or serve schools? ☐ 20 U.S.C. § 1232g
Are we a federal agency or contractor operating a system of records? ☐ 5 U.S.C. § 552a
Do we record calls, capture sessions, or monitor communications? ☐ 18 U.S.C. § 2510 · 18 U.S.C. § 2511 · ⚠ stricter state all-party rules
Are we a provider that stores user communications? ☐ 18 U.S.C. § 2701 · 18 U.S.C. § 2702
Do we place calls or send texts for marketing? ☐ ⭐ 47 U.S.C. § 227 — private right of action
Are we a telecommunications carrier? ☐ 47 U.S.C. § 222
Do we obtain or use motor vehicle records? ☐ 18 U.S.C. § 2721
Do we send commercial email? ☐ 15 U.S.C. § 7701
Do we make representations about privacy or security to anyone? ⭐ Always yes 15 U.S.C. § 45
Do we meet any state comprehensive statute's thresholds? ☐ State statutes — list each: ______
Do we process biometric identifiers? ☐ ⚠ State biometric statutes — statutory damages per violation
Do we serve residents of other countries? ☐ Foreign law

Tool 3 — Privacy notice outline

⚠ Draft this LAST, from the data map — never first, from a template. ⭐ The gap between the notice and the code is the leading enforcement theory in this field.

  1. Who we are and how to contact us
  2. Categories of personal data we collect, by source
  3. Sensitive data we process, and why
  4. Purposes for each category
  5. ⭐ Whether we sell or share personal data, and to which categories of third parties — ⚠ check every pixel and software development kit before answering
  6. Categories of third parties to whom we disclose, by purpose
  7. Retention periods or the criteria used to determine them
  8. Your rights, and how to exercise each
  9. How we verify a request
  10. Authorized agents
  11. The appeal process and its timeline
  12. Universal opt-out signals we honor
  13. Children's data practices
  14. Security — described accurately, ⚠ without promises the program cannot keep
  15. Cross-border transfers
  16. Changes to this notice, and how we give notice of them
  17. Effective date and version history — ⭐ retain every prior version; the notice in force when data was collected governs what may be done with it

Tool 4 — Consent design review

⭐ The test: is declining as easy as accepting?

Check Pass
"Accept" and "Reject" are equally prominent — same size, color weight, and position ☐
⚠ Rejecting takes no more clicks than accepting ☐
No pre-checked boxes for optional processing ☐
No double negatives or confusing language ☐
No repeated prompting after a refusal ☐
No emotionally manipulative framing ("No thanks, I don't care about security") ☐
Consent is separate for each distinct purpose ☐
⭐ Sensitive data uses opt-in, not opt-out ☐
Withdrawal is as easy as granting ☐
No account required to exercise a right ☐
Universal opt-out signals honored automatically ☐
⚠ The consent actually controls the technical behavior — verified by testing, not by assumption ☐

⚠ That last row fails more often than any other. ⭐ Have someone load the page with a network inspector open, reject everything, and watch whether the transfers stop.


Tool 5 — Rights request intake and verification

Intake form fields: requester name · contact method · state of residence · relationship (consumer, employee, minor's parent, authorized agent) · right requested · specific accounts or products · preferred response format · date received · assigned owner · statutory deadline.

Verification protocol:

Request type Verification level Method
Opt out of sale or targeted advertising ⭐ Minimal — none required in several statutes Honor it
Access to categories Reasonable degree Match two data points already on file
Access to specific pieces Reasonably high Match three data points; signed declaration under penalty of perjury in some statutes
Correction Reasonable Match, plus documentation of the correct value
Deletion Reasonably high Match three data points
Authorized agent Both Written authorization, plus verify the consumer directly

⚠ Do not collect new personal data solely to verify, beyond what is necessary. ⭐ If you cannot verify, say so, explain why, and tell them what would suffice.

Response letter skeleton:

Dear ______,

We received your request dated ______ to [exercise right] under [statute]. We have verified your identity and respond as follows.

Categories of personal data we collected about you in the preceding twelve months: ______ Categories of sources: ______ Business or commercial purposes: ______ ⭐ Categories of third parties to whom we disclosed personal data, and the purpose of each disclosure: ______ Whether we sold or shared personal data, and the categories involved: ______

[For deletion] We have deleted the personal data described above from our production systems and directed our service providers to do the same. ⚠ We have retained the following, under the exception for [completing a transaction / legal obligation / security incident detection / defense of legal claims / internal use aligned with your expectations]: ______. Data in routine backups will be deleted on the ordinary backup cycle, and will not be used in the interim.

[For opt-out] We have recorded your opt-out and will not sell or share your personal data. This takes effect immediately and applies until you direct otherwise.

If you disagree with this response, you may appeal by ______. We will respond within ______ days.

⭐ Log every request, response, and date. The log is the compliance record and the litigation defense.


Tool 6 — Processor contract clauses

Processing instructions. Processor shall process Personal Data only on Controller's documented instructions and only for the purposes set out in Exhibit A. ⚠ Processor shall not sell, share, retain, use, or disclose Personal Data for any purpose other than performing the Services, including for Processor's own product development, analytics, benchmarking, or the training or improvement of any model.

Confidentiality. Processor shall bind personnel with access to confidentiality obligations.

Security. Processor shall implement and maintain the technical and organizational measures set out in Exhibit B, including encryption of Personal Data at rest and in transit, access controls with multi-factor authentication, logging, vulnerability management, and secure disposal.

⭐ Breach notification. Processor shall notify Controller within twenty-four hours of becoming aware of any Security Incident affecting Personal Data, shall provide all information reasonably required for Controller to meet its notification obligations, shall cooperate fully with Controller's investigation, and shall provide the forensic report or a detailed factual summary. ⚠ Processor shall not notify any individual or regulator without Controller's prior written consent, except where required by law.

Subprocessors. Processor shall not engage a subprocessor without Controller's prior written consent, shall impose these same obligations by written contract, and shall remain fully liable for subprocessor performance. Processor shall maintain a current subprocessor list at ______.

Assistance. Processor shall assist Controller in responding to consumer rights requests within ______ days, and in conducting data protection assessments.

Audit. Processor shall make available all information necessary to demonstrate compliance and shall permit audits on reasonable notice, not more than ______ times annually.

⭐ Deletion. On termination, and on Controller's instruction at any time, Processor shall delete or return all Personal Data and certify deletion in writing within ______ days, including from backups on the ordinary cycle.

Location. Processor shall process Personal Data only in ______ and shall not transfer it outside those jurisdictions without prior written consent.

⚠ The two clauses most often missing are the breach notification deadline and the prohibition on the processor's own use. ⭐ Without the first, the controller cannot meet its own statutory clock. Without the second, the vendor's model gets trained on the controller's customers.


Tool 7 — Data protection assessment

Data Protection Assessment — [Processing Activity] Prepared by ______ · Date ______ · Approved by ______ · Next review ______

1. Description. What processing, by which system, for what purpose. 2. Categories of personal data, including any sensitive categories. 3. Sources and whether the individual provided the data directly. 4. Recipients, including processors, third parties, and any sale or sharing. 5. Retention period and criteria. 6. Benefits — to the controller, to the consumer, to other stakeholders, and to the public. 7. Risks to consumers. ⭐ Be specific: unfair or deceptive treatment · disparate impact · financial injury · physical injury · reputational harm · intrusion on private affairs where the intrusion would be offensive to a reasonable person · loss of control. 8. Consumer expectations. ⭐ Would a reasonable consumer in this relationship expect this processing? ⚠ If the honest answer is no, that is the finding, and it is what a regulator will focus on. 9. Safeguards — technical, organizational, and contractual — and residual risk after each. 10. Balance. Do the benefits outweigh the residual risk? State the reasoning. 11. Alternatives considered, including less intrusive options and why they were rejected. 12. Conclusion. Proceed · proceed with modifications · do not proceed.

⭐ Write it to be read by a regulator, because it will be produced on request. ⚠ Refresh it whenever the processing materially changes.


Tool 8 — Incident first-hour card and decision log

Card — post it where the on-call engineer will see it:

SUSPECTED INCIDENT — FIRST HOUR

  1. ⚠ DO NOT wipe, rebuild, reimage, or restore.
  2. ⚠ DO NOT delete logs. Suspend rotation NOW.
  3. Isolate from the network; do not power off if memory capture is possible.
  4. Revoke credentials; rotate keys.
  5. Call: counsel → security lead → executive sponsor → cyber insurer.
  6. ⚠ Counsel retains the forensic firm, not you.
  7. ⚠ No email outside the response team. No speculation in writing.
  8. ⚠ No public statement. None.
  9. Open the decision log.
  10. Ask: what data lived on that system?

Decision log:

Time Action or decision Who Basis Follow-up

⭐ One log, one owner, contemporaneous. ⚠ Reconstructed timelines are the weakest evidence in a regulator inquiry.


Tool 9 — Encryption safe harbor analysis

Data element Encrypted at rest? Algorithm and key length ⚠ Was the key compromised? Safe harbor available? State variations
☐ ☐ ☐

☐ ⭐ Document the encryption status BEFORE the incident. ⚠ Establishing it afterward, from memory, is not persuasive. ☐ Confirm key management — where the keys were stored, and whether the attacker reached them. ☐ ⚠ Note that some statutes require the data be rendered unusable, unreadable, or indecipherable, which is not identical to "encrypted." ☐ Note redaction and tokenization where they apply.


Tool 10 — Breach notice letter

[Date]

NOTICE OF DATA BREACH

Dear ______,

What happened. On ______, we learned that ______. We immediately ______, and we engaged a forensic firm to investigate. Our investigation determined that an unauthorized party ______ between ______ and ______.

What information was involved. The information involved for you may have included: ______. [⭐ Be specific and accurate. ⚠ Do not describe the categories more narrowly than the investigation supports.]

What we are doing. We have ______ [contained, remediated, reset credentials, added controls]. We have notified ______ [law enforcement, regulators]. We are offering ______ [monitoring or identity restoration] at no cost to you, which you may enroll in by ______ using code ______ before ______.

What you can do.

  • ⭐ Place a security freeze on your credit files. A freeze is free and prevents new accounts from being opened in your name. [Contact information for each of the three nationwide agencies, with mailing addresses, phone numbers, and websites.]
  • Place a fraud alert, which is free and lasts one year.
  • Review your account statements and credit reports for accounts you do not recognize.
  • Change your password on any account where you used the same password.
  • You may obtain a free copy of your credit report as provided by federal law.
  • [State-specific required content, including any required statements about reporting identity theft to law enforcement and the attorney general.]

For more information. Call ______ [toll-free], Monday through Friday, ______, or write to ______.

We regret that this occurred and we take it seriously.

⚠ Check every affected state's required content, required order of sections, and required font size. ⭐ Put the freeze first — it is the only thing on the list that actually prevents harm.


Tool 11 — Regulator notification outline

To: Office of the Attorney General, [State] · Re: Notification of security breach

  1. Notifying entity — name, address, and relationship to the affected individuals (owner or licensee of the data).
  2. Date of the breach, date of discovery, and date individuals were or will be notified.
  3. Nature of the breach — how it occurred, and the vector.
  4. Data elements involved, by category.
  5. Number of state residents affected.
  6. ⭐ Encryption status of each element and the safe harbor analysis.
  7. Steps taken to contain, investigate, and remediate.
  8. Services offered to affected individuals.
  9. Sample of the individual notice, attached.
  10. Contact for the office's follow-up.

☐ File in the format the state requires — several have prescribed online forms. ☐ ⚠ Check whether the state requires notice above a threshold or in every case. ☐ Notify the consumer reporting agencies above the applicable threshold.


Tool 12 — Individual rights request letter

[Date]

Re: Request under [State] [statute name]

To the Privacy Officer:

I am a resident of [state] and a consumer of your services. I am exercising the following rights:

☐ Right to know / access. Please provide the categories and specific pieces of personal data you have collected about me, the categories of sources, the business or commercial purposes for collecting it, ⭐ and the categories of third parties to whom you have disclosed it, along with the purpose of each disclosure. ☐ Right to correct. The following information is inaccurate and should be corrected: ______ ☐ Right to delete all personal data you hold about me. Please identify any data retained under a statutory exception and state which exception applies. ☐ Right to opt out of the sale and sharing of my personal data. ☐ Right to opt out of targeted advertising. ☐ Right to opt out of profiling that produces legal or similarly significant effects. ☐ Right to limit the use of my sensitive personal data. ☐ Right to data portability, in a structured, commonly used, machine-readable format.

My contact information is ______. I understand you may need to verify my identity, and I am willing to provide reasonable verification. ⚠ Please do not require me to create an account or provide substantial new personal information for this purpose.

Please respond within the statutory period. If you deny any part of this request, please state the basis and describe the appeal process.

⭐ Keep a copy, note the date sent, and diary the deadline.

Credit freeze steps: ☐ Contact each of the three nationwide consumer reporting agencies — online, by phone, or by mail — under 15 U.S.C. § 1681 ☐ Store the PIN or password each provides ⭐ somewhere you will find it in five years ☐ Freeze children's files as well, where the agency offers it ☐ ⚠ Remember to temporarily lift the freeze before applying for credit, which is free and usually immediate ☐ Also opt out of pre-screened offers under 15 U.S.C. § 1681b


Tool 13 — Retention schedule

Data category System Retention period Basis for the period Deletion method Automated? Owner
☐

☐ Set a period for every category — ⚠ "as long as needed" is not a period. ☐ Tie each period to a stated basis: legal requirement · statute of limitations · tax rules · operational necessity · contractual obligation. ☐ ⭐ Enforce technically, not by policy. ⚠ A retention policy nobody automated is a document, not a control. ☐ Include backups, with a defined cycle. ☐ Include development and staging environments. ☐ Include vendor-held copies, with contractual deletion obligations. ☐ Document exceptions for legal holds — see Issuing a Litigation Hold and Preserving ESI: A Practical Checklist.

⭐ Indefinite retention is the most common finding in a privacy audit, and it converts every legacy system into a breach exposure.


Tool 14 — Tabletop exercise

⭐ Ninety minutes, annually. It is the cheapest item in this toolkit and the one that most changes outcomes.

Scenario: At 6:40 a.m. on a Saturday, an engineer notices unusual outbound traffic from a database server holding customer records. She is not sure whether it is a misconfiguration or an intrusion.

Injects, delivered in sequence:

  1. The server holds records for customers in nineteen states, ⚠ and nobody in the room can say which data elements.
  2. Two hours in, a journalist emails asking about "a report of a breach."
  3. The forensic firm the security lead wants to call is not on the insurer's panel.
  4. A major customer's contract requires notice within twenty-four hours of "any security incident."
  5. The engineer restored the server from backup at hour three ⚠ and the original disk was reformatted.
  6. The investigation finds the data was encrypted — ⚠ but the key was stored on the same server.
  7. Preliminary counts show five hundred and eighty residents of one state, ⭐ crossing the HIPAA media notice threshold.

Questions to answer out loud: ☐ Who did we call, in what order, and how long did it take? ☐ ⚠ Could we answer "what data" without the map? ☐ Did anyone say anything in writing they would not want produced? ☐ What is the shortest applicable deadline, and who computed it? ☐ Was the safe harbor available, and who decided? ☐ What would we change?

⭐ Write the after-action notes and fix two things before the next exercise.


Tool 15 — Annual audit

Item Done Notes
Data map refreshed, including new systems and vendors ☐
⭐ Privacy notice re-verified against actual code and tags ☐ ⚠ The leading enforcement gap
Consent flows re-tested with a network inspector ☐ Does rejecting actually stop the transfers?
Universal opt-out signal handling verified ☐
Rights request log reviewed — volumes, timeliness, appeals ☐
Deletion capability tested end to end across all systems ☐ ⚠ Including warehouse, marketing platform, and support tool
Retention schedules enforced and verified ☐
Vendor list reconciled; contracts checked for breach deadlines and use restrictions ☐
Data protection assessments current for all high-risk processing ☐
Encryption at rest verified for all sensitive categories ☐ ⭐ And key storage reviewed
Access reviews completed; stale accounts removed ☐
Incident response plan updated; tabletop run ☐
Training delivered; attendance recorded ☐
Legislative tracking reviewed; new statutes assessed ☐ ⚠ This area changes every session

Tool 16 — Where privacy work touches the rest of the file

Also in play Read
An automated system made the decision The Model Said No: How Automated Decisions Are Made and How They Are Challenged · Automated Decisions and Artificial Intelligence: A Comprehensive Guide to Disclosure, Bias, and Accountability · Challenging an Automated Decision and Auditing an AI System: A Practical Checklist · The Automated Decision and AI Accountability Toolkit
Credit reports or collections are involved Consumer Credit Reporting and Debt Collection: A Comprehensive Guide to the FCRA, FDCPA, and Identity Theft Remedies · Disputing a Credit Report Error and Defending a Debt Collection Suit: A Practical Checklist · The Consumer Debt and Credit Reporting Toolkit · Sued by a Stranger: Debt Buyers, Default Judgments, and the Consumer Who Shows Up
A departing employee took data What Walks Out the Door: Trade Secrets, Non-Competes, and the Employee Who Leaves · Protecting Trade Secrets and Handling a Departing Employee: A Practical Checklist · The Trade Secret and Restrictive Covenant Toolkit
An older adult was targeted The Quiet Theft: How Elder Financial Exploitation Happens and How It Is Unwound · Detecting, Reporting, and Unwinding Elder Financial Exploitation: A Practical Checklist · The Elder Financial Exploitation Response Toolkit
Employment monitoring or termination is involved At Will Does Not Mean For Any Reason: What Actually Makes a Firing Unlawful · Filing and Pursuing an Employment Discrimination Charge: A Practical Checklist
Online accounts must be reached after a death Who Gets the Password? Digital Assets, Online Accounts, and the Estate You Left in the Cloud · The Digital Estate and Online Account Toolkit
Litigation is likely Issuing a Litigation Hold and Preserving ESI: A Practical Checklist

Related Documents