AccessPoint by Realizerwww.realizer.io/resources/privacy-breach-planner
Privacy breach response planner: who to notify, by when, under your law
Answer a few questions about the breach. Get a real-risk-of-significant-harm (RROSH) assessment with its reasons, every notice your law requires with its deadline, what it must say and where to file it, a containment checklist, starting drafts and a written record to keep in Word — for 116 privacy and breach-notification laws, using the rules AccessPoint runs on.
Runs in your browser. Nothing you enter is sent to Realizer or anyone else, and the planner never asks for names. Your answers stay on this device until you clear them.
Your breach response plan
1. Contain it now
Tick each step as it is done; the record picks them up.
2. Assess the risk of harm
3. Notify
Others to tell, and other clocks that may be running
Starting drafts
A first draft from your answers, with the contents each law requires listed under it. Fill in the bracketed parts and have it reviewed before it goes out.
4. Prevent it happening again
Keep the record
Keep a written record of every breach — including the ones you decide not to report — with the facts, the assessment and why you decided as you did. PIPEDA requires it for 24 months, and every regulator asks for it.
Run this breach in AccessPoint
AccessPoint works out these notices on every incident, re-runs them whenever the facts change, counts down to each deadline, files the letters and keeps the 24-month record — in your own Microsoft 365 or hosted for you.
The demo needs no sign-up. The trial is 30 days free, no card, with unlimited users — and Lab mode has a breach exercise to practise on.What to do in the first hours of a privacy breach
A privacy breach is the loss of, or unauthorized access to, use or disclosure of personal information. The response has the same shape under every law: contain it, assess the risk of harm, notify the people and bodies the law names, and prevent it happening again.
- Contain the breach. Stop it: recover what was sent, lock the account or device, remove access. Tell your privacy officer at once and preserve the evidence.
- Record what happened. Write down what happened, when it was discovered, what personal information was involved and how many people are affected. Start a timeline.
- Assess the risk of harm. Judge how sensitive the information is and how likely it is to be misused: who has it, whether it was protected, whether it was recovered, and whether misuse has already happened.
- Work out who must be notified. Check each privacy law that applies: the regulator, the people affected and anyone who can reduce the harm, each with its own trigger and deadline.
- Notify, and say what the law requires. Send each notice by its deadline with the contents the law lists: what happened, what information, what you have done, and what the person can do.
- Keep the record and fix the cause. Keep a written record of the breach and of the decision, including when you decide not to notify, and correct what allowed it.
Who must be notified of a privacy breach, and when?
Most privacy laws name three audiences: the regulator, the people affected, and others who can reduce the harm. Whether notice is owed usually turns on a risk threshold. In Canada it is a real risk of significant harm; under the GDPR and the UK GDPR the authority is told unless the breach is unlikely to result in a risk, and individuals are told when the risk is high; several US state laws add the attorney general once a set number of residents is affected.
The table gives the notice to the regulator under each law: what triggers it and how long you have. The planner adds the notice to individuals, the contents each notice must have, and the dates for your own breach.
| Law | Regulator notified | When notice is owed | Deadline |
|---|---|---|---|
| Canada | |||
| ABAlberta — PIPA | OIPC of Alberta | Real risk of significant harm | As soon as feasible |
| CACanada — PIPEDA | Office of the Privacy Commissioner of Canada (OPC) | Real risk of significant harm | As soon as feasible |
| QCQuébec — Secteur privé (Loi 25) | Commission d'accès à l'information | Real risk of significant harm | As soon as feasible |
| ABAlberta — HIA | Office of the Information and Privacy Commissioner of Alberta (OIPC) | Every breach, unless there is no risk of harm | As soon as feasible |
| MBManitoba — PHIA | Manitoba Ombudsman | Real risk of significant harm | As soon as feasible |
| NBNew Brunswick — PHIPAA | Office of the Ombud, New Brunswick | Every breach, unless the custodian reasonably believes it will have no adverse impact on the person's care, benefits or well-being | As soon as feasible |
| NLNewfoundland & Labrador — PHIA | Office of the Information and Privacy Commissioner for Newfoundland and Labrador (OIPC NL) — breachreport@oipc.nl.ca | Every breach | As soon as feasible |
| NTNorthwest Territories — HIA | NWT Information and Privacy Commissioner | Every breach | As soon as feasible |
| NSNova Scotia — PHIA | Review Officer (Office of the Information and Privacy Commissioner for Nova Scotia); from 1 April 2027, the Information and Privacy Commissioner | Every breach | As soon as feasible |
| ONOntario — CYFSA Part X | Information and Privacy Commissioner of Ontario (IPC) and the Minister of Children, Community and Social Services (s.308(3)) | Every breach | As soon as feasible |
| ONOntario — PHIPA | Information and Privacy Commissioner of Ontario (IPC) | Every breach | As soon as feasible |
| PEPrince Edward Island — HIA | Information and Privacy Commissioner of Prince Edward Island | Every breach, unless the custodian reasonably believes it will have no adverse impact on the person's care, benefits or well-being | As soon as feasible |
| QCQuébec — Renseignements de santé | Ministre de la Santé et des Services sociaux et Commission d'accès à l'information du Québec (CAI) | Real risk of significant harm | As soon as feasible |
| YTYukon — HIPMA | Yukon Information and Privacy Commissioner | Real risk of significant harm | As soon as feasible |
| ABAlberta | Office of the Information and Privacy Commissioner of Alberta (OIPC) | Real risk of significant harm (from 2025-06-11) | As soon as feasible |
| BCBritish Columbia | Office of the Information and Privacy Commissioner for British Columbia (OIPC BC) | Real risk of significant harm | As soon as feasible |
| CACanada — Federal | Office of the Privacy Commissioner of Canada (OPC) | Real risk of significant harm | 7 days from determining the breach |
| MBManitoba | Manitoba Ombudsman | Real risk of significant harm | As soon as feasible |
| NBNew Brunswick | Office of the Ombud, New Brunswick | Real risk of significant harm | As soon as feasible |
| NLNewfoundland & Labrador | Office of the Information and Privacy Commissioner for Newfoundland and Labrador (OIPC NL) | Every breach | As soon as feasible |
| NTNorthwest Territories | Information and Privacy Commissioner of the Northwest Territories (OIPC-NT) | Every breach | As soon as feasible |
| NSNova Scotia | Information and Privacy Commissioner for Nova Scotia (OIPC NS) | Real risk of significant harm (from 2027-04-01) | As soon as feasible |
| NUNunavut | Information and Privacy Commissioner of Nunavut (NUIPC) | Every breach | As soon as feasible |
| ONOntario — FIPPA (provincial) | Information and Privacy Commissioner of Ontario (IPC) | Real risk of significant harm | As soon as feasible |
| ONOntario — MFIPPA (municipal) | Information and Privacy Commissioner of Ontario (IPC) | Real risk of significant harm (from 2027-01-01) | As soon as feasible |
| QCQuébec | Commission d'accès à l'information du Québec (CAI) | Real risk of significant harm | As soon as feasible |
| YTYukon | Yukon Information and Privacy Commissioner | Real risk of significant harm | As soon as feasible |
| United States | |||
| CACalifornia — CCPA/CPRA | California Attorney General | More than 500 people affected | 15 days from determining the breach |
| MDMaryland — MODPA | Maryland Attorney General | Every breach, unless there is no risk of harm | As soon as feasible |
| USUnited States — HIPAA | U.S. Department of Health and Human Services, Office for Civil Rights (HHS breach-report portal) | 500 or more people affected | 60 days from discovery |
| USUnited States — Privacy Act | CISA (US-CERT) | Every breach | 24 hours from discovery |
| ALAlabama | Alabama Attorney General (Office of the Attorney General, 501 Washington Avenue, Montgomery, AL 36130) | More than 1,000 people affected | 45 days from determining the breach |
| AZArizona | Arizona Attorney General and Director of the Arizona Department of Homeland Security | More than 1,000 people affected | 45 days from determining the breach |
| ARArkansas | Arkansas Attorney General (Office of the Attorney General, 323 Center Street, Suite 200, Little Rock, AR 72201) | More than 1,000 people affected | 45 days from determining the breach |
| CACalifornia | California Attorney General | More than 500 people affected | As soon as feasible |
| COColorado | Colorado Attorney General | 500 or more people affected | 30 days from determining the breach |
| CTConnecticut | Connecticut Attorney General | Every breach, unless there is no risk of harm | 60 days from discovery |
| DEDelaware | Delaware Attorney General (Department of Justice, 820 N. French Street, Wilmington, DE 19801) | More than 500 people affected | 60 days from determining the breach |
| FLFlorida | Florida Department of Legal Affairs | 500 or more people affected | 30 days from discovery |
| IDIdaho | Office of the Idaho Attorney General (primary regulator of public agencies) | Every breach | 24 hours from discovery |
| ILIllinois | Illinois Attorney General | More than 250 people affected | 45 days from discovery |
| INIndiana | Indiana Attorney General (notice owed by public bodies that are not state agencies) | Every breach, unless there is no risk of harm | 45 days from discovery |
| IAIowa | Director, Consumer Protection Division, Office of the Iowa Attorney General | More than 500 people affected | 5 business days from discovery |
| KYKentucky | Commissioner of the Kentucky State Police; Auditor of Public Accounts; Attorney General; and the agency's oversight body (Finance and Administration Cabinet / Department for Local Government / Kentucky Department of Education / Council on Postsecondary Education) | Every breach | 72 hours from discovery |
| LALouisiana | Consumer Protection Section, Office of the Attorney General (Louisiana Department of Justice, 1885 North Third Street, Baton Rouge, LA 70802) | Every breach, unless there is no risk of harm | 70 days from discovery |
| MEMaine | Office of the Attorney General (6 State House Station, Augusta, ME 04333-0006) — or the appropriate regulator within the Department of Professional and Financial Regulation for entities it regulates | Every breach, unless there is no risk of harm | As soon as feasible |
| MDMaryland | Maryland Attorney General | Real risk of significant harm | As soon as feasible |
| MAMassachusetts | Attorney General and the Director of Consumer Affairs and Business Regulation | Every breach | As soon as feasible |
| MOMissouri | Missouri Attorney General | More than 1,000 people affected | As soon as feasible |
| MTMontana | Montana Attorney General — Office of Consumer Protection | Real risk of significant harm | As soon as feasible |
| NENebraska | Nebraska Attorney General (Office of the Attorney General, Lincoln) | Real risk of significant harm | As soon as feasible |
| NHNew Hampshire | New Hampshire Attorney General's Office (Consumer Protection and Antitrust Bureau) — or the primary state/federal regulator for RSA 358-A:3, I regulated trades | Every breach, unless there is no risk of harm | As soon as feasible |
| NJNew Jersey | New Jersey Division of State Police | Every breach, unless there is no risk of harm | As soon as feasible |
| NYNew York | New York Attorney General, Department of State and Office of Information Technology Services | Every breach | As soon as feasible |
| NCNorth Carolina | North Carolina Attorney General (Consumer Protection Division) | Real risk of significant harm | As soon as feasible |
| NDNorth Dakota | North Dakota Attorney General (by mail or electronic mail) | More than 250 people affected | As soon as feasible |
| OKOklahoma | Oklahoma Attorney General | 500 or more people affected | 60 days from determining the breach |
| OROregon | Oregon Attorney General (Department of Justice), in writing or electronically | More than 250 people affected | 45 days from discovery |
| PAPennsylvania | District attorney (county, public school or municipality) or the Office of Administration and the Attorney General (State agency) | Real risk of significant harm | 3 business days from determining the breach |
| PRPuerto Rico | Departamento de Asuntos del Consumidor (DACO), Secretario — Apartado 41059, Estación Minillas, San Juan, PR 00940-1059 | Every breach | 10 days from discovery |
| RIRhode Island | Rhode Island Attorney General | More than 500 people affected | As soon as feasible |
| SCSouth Carolina | Consumer Protection Division, South Carolina Department of Consumer Affairs | More than 1,000 people affected | As soon as feasible |
| SDSouth Dakota | South Dakota Attorney General (Consumer Protection Division) | More than 250 people affected | As soon as feasible |
| TXTexas | Texas Attorney General | 250 or more people affected | 30 days from determining the breach |
| UTUtah | Utah Cyber Center (Division of Technology Services) and the Office of the Attorney General | 500 or more people affected | 5 days from discovery |
| VTVermont | Vermont Attorney General (Consumer Protection Unit) or, for DFR-regulated data collectors, the Department of Financial Regulation | Every breach | 14 business days from discovery |
| VAVirginia | Virginia Attorney General | Real risk of significant harm | As soon as feasible |
| WAWashington | Washington Attorney General | More than 500 people affected | 30 days from discovery |
| Europe | |||
| GGBailiwick of Guernsey | Office of the Data Protection Authority (ODPA) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| GIGibraltar | Information Commissioner (Gibraltar Regulatory Authority) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| IMIsle of Man | Isle of Man Information Commissioner (online personal data breach report) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| JEJersey | Data Protection Authority (Jersey Office of the Information Commissioner) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| EUEuropean Union — GDPR | Competent supervisory authority (national / lead DPA) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| EUEuropean Union — Institutions (2018/1725) | European Data Protection Supervisor | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| CHSwitzerland | Federal Data Protection and Information Commissioner (FDPIC) | High risk to the people affected | As soon as feasible |
| IEIreland | Data Protection Commission (DPC) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| SCOScotland | Information Commission (ICO) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| UKUnited Kingdom — DPA / UK GDPR | Information Commission (ICO) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| UKUnited Kingdom — DPA 2018 Part 3 | Information Commission (ICO) | Every breach, unless it is unlikely to result in a risk to people | 72 hours from discovery |
| Rest of World | |||
| BRBrazil | Agência Nacional de Proteção de Dados (ANPD) | High risk to the people affected | 3 business days from discovery |
| INIndia | Data Protection Board of India (DPBI) | Every breach (from 2027-05-13) | 72 hours from discovery |
| ZASouth Africa | Information Regulator (South Africa) | Every breach | As soon as feasible |
| AUAustralia — Federal | Office of the Australian Information Commissioner (OAIC) | Real risk of significant harm | As soon as feasible |
| NSWAustralia — New South Wales | NSW Privacy Commissioner (IPC NSW) | Real risk of significant harm | As soon as feasible |
| AUAustralia — Privacy (APPs) | Office of the Australian Information Commissioner (OAIC) | Real risk of significant harm | As soon as feasible |
| QLDAustralia — Queensland | Office of the Information Commissioner Queensland | Real risk of significant harm | As soon as feasible |
| WAAustralia — Western Australia | WA Information Commissioner | Real risk of significant harm (from 2027-01-01) | As soon as feasible |
| NZNew Zealand | Office of the Privacy Commissioner | Real risk of significant harm | As soon as feasible |
| NZNew Zealand — Health Information Privacy Code | Office of the Privacy Commissioner | Real risk of significant harm | As soon as feasible |
| NZNew Zealand — Privacy Act (private sector) | Office of the Privacy Commissioner | Real risk of significant harm | As soon as feasible |
From AccessPoint's jurisdiction packs, 2026-11-18. Where a law sets no fixed count the table says “as soon as feasible”. Confirm against the law before you rely on a date.
How the planner decides
The planner is a public version of the notification calculator inside AccessPoint's incident register. It reads the breach rules from AccessPoint's jurisdiction packs — 313 rules across 116 privacy and breach-notification laws in Canada, the United States, the UK and Europe, Australia, New Zealand and beyond — and applies them the way the product does.
How is the risk of harm assessed?
The risk of harm is scored on the two factors Canadian law names and other regimes echo: the sensitivity of the information, and the probability that it has been, is being or will be misused. Each is scored from 1 to 4 and the two are multiplied. A product of 12 or more is a real risk of significant harm; 6 to 11 is a possible harm; 3 to 5 a minimal risk. Sensitive information — health, government identifiers, financial details, credentials — raises the floor, so a sensitive breach never scores as no risk. The GDPR's “high risk” for telling individuals is read as the same top band. The real risk of significant harm guide works three common breaches through the test by hand.
Each notice comes from a rule in the pack: who receives it, what triggers it (the risk threshold, a number of residents, or every breach), what the clock counts from, and what the notice must contain. Where a law sets no fixed count — “as soon as feasible” — the planner shows the internal target the pack suggests, so the notice still has a date. Rules that come into force later, such as Ontario's municipal breach duties in January 2027, apply only to breaches discovered after they start.
Checked against the law. In November 2026 every notice rule was checked against the current text of its statute or regulation, and the packs were corrected where they differed. A notice the law owes for every breach — a US state law with no risk-of-harm exemption — is owed whatever the risk, and a notice owed “unless the breach is unlikely to result in a risk” says so, with the provision in the rule’s detail. Government ID numbers, banking details or passwords held by a recipient who has not confirmed deleting them are treated as still at large, so a misdirected message that goes unanswered is not scored as low risk.
What it cannot know: your contracts, your insurer's conditions, sector rules outside privacy law, and the facts you have not found yet. Treat the result as a starting point built from public information about each law, not legal advice, and confirm the decision with your legal counsel.
Where AccessPoint fits
A planner helps with one breach in one sitting. A privacy office needs the same discipline on every incident, kept for years: the facts, the two-factor assessment, every notice with its deadline and proof it went, the containment and remediation steps with owners, and the annual statistics the regulator asks for.
A live notification checklist
The calculator re-runs on every save, so a new affected count or a changed risk determination moves the notices and their due dates at once.
Containment and remediation with owners
Each measure has an owner, a target date and a progress log, and confirming containment is stamped with who and when.
Letters filed on the incident
Regulator reports and individual notices generate from templates in the pack's languages and file under the incident's correspondence.
The record keeps itself
Every breach, reported or not, keeps its assessment, decision and audit trail, and feeds the regulator's annual breach statistics.
See privacy breach management in AccessPoint Log a breach yourself in the demo, no sign-up (opens the demo in a new tab)
Breach response questions
Do I have to report every privacy breach?
How does the planner decide whether there is a real risk of significant harm?
How long do I have to report a privacy breach?
Who has to be notified of a privacy breach?
When does the notification clock start?
Is anything I enter sent to Realizer?
What if the breach affects people in several provinces, states or countries?
Can I rely on this for a legal decision?
Sources
- PIPEDA, sections 10.1 to 10.3 — Justice Laws Canada (accessed November 2026).
- What you need to know about mandatory reporting of breaches of security safeguards — Office of the Privacy Commissioner of Canada (accessed November 2026).
- Regulation (EU) 2016/679 (GDPR), Articles 33 and 34 — EUR-Lex (accessed November 2026).
- Notification rules for each law — AccessPoint's jurisdiction packs, built from the public text of the legislation.
Related reading
The real risk of significant harm guide explains the threshold in PIPEDA, Alberta PIPA and Ontario's Bill 194, with worked examples; privacy breach management in AccessPoint shows the incident register this planner is drawn from; and the PIA readiness check tests the program that should catch the next one before it happens. Browse the jurisdiction packs to see each law's rules, or book a live demo.
Last reviewed: November 2026. The rules are exported from AccessPoint's jurisdiction packs, researched from public legislation and regulator guidance. General information for privacy practitioners, not legal advice.