ClearBreach

← Guides·All compliance guides →

Your SituationWe had a privacy incident →

PIPEDAAB PIPABC PIPAAll sectors

A System Holding Customer Data Was Breached: Who to Tell, and By When

By Yong DuPublished Reviewed

Share on LinkedIn

When you hold data for your customers, the regulator duty usually sits with them, and your contract sets your deadline. Who to tell, in what order.

On this page

Start with whose information it is

Most small firms hold two kinds of personal information, and a breach is handled differently for each.

Information you hold for a customer. A bookkeeper's client files, a property manager's tenant list, an IT provider's backups. The customer normally keeps the information under its control, even while it sits on your system. PIPEDA Schedule 1 clause 4.1.3 and Alberta PIPA s.5(2) keep them responsible for it.

In European terms your customer is the controller and you are the processor. Canadian law does not use those words. It speaks of information "under the control" of an organization, and of a third party it transfers information to for processing. Handing information to a processor does not hand over the responsibility for it.

Your own information. Your staff records, and your own list of customers and their contacts. That is yours, whoever hosts it.

One incident can hit both. Sort them first, because the rest of this guide follows from that split.

Who to tell

1. Your customers whose information was involved. This is the first call for a supplier. The duty to report to a regulator sits with the organization that has the information under its control: PIPEDA s.10.1(1) and Alberta PIPA s.34.1(1). They cannot assess a breach they have not heard about, so you are the start of their process.

Tell them what happened, when, which information was reachable, what you have done, and what you have not yet established. Then keep updating them. They make the reporting decision, not you.

2. Your insurer. Check your policy for a notice condition before you need it. Late notice can put cover at risk.

3. The regulator, for your own information. If your staff or customer records were involved, you assess those yourself. Under PIPEDA and Alberta PIPA, you report when the breach creates a real risk of significant harm. BC PIPA has no mandatory reporting duty for private organizations, though the BC commissioner recommends reporting.

4. Your own record. PIPEDA s.10.3(1) requires a record of every breach of security safeguards involving personal information under your control, including those you find are not reportable. Keep a dated note of who you told and when, whichever way the assessment goes.

By when

For your own information, the standard is in the Act: as soon as feasible under PIPEDA, and without unreasonable delay to the commissioner under Alberta PIPA. Neither sets a number of hours.

For your customers' information, the deadline usually comes from your contract, and it can be much shorter. We read a random sample of 200 federal service requests for proposals from 2026-27. About 13% carried a breach or incident notice term, and about 3% set a clock of 24 hours or similar. These are close counts from text matching, and federal buyers may differ from private ones.

If a customer is a bank, a telecom or another operator named under Bill C-8, expect more interest in your speed. Those operators will have to report certain incidents within at most 72 hours once that Act is in force. The Act puts no such duty on you, and it is not in force yet, but a customer's clock shapes what it will ask of you.

The problem is usually knowing who

Telling people is the easy part. Working out who to tell takes the time.

A case from October 2026. A large Canadian retailer confirmed unauthorized access to its systems on March 5, after a login for a testing platform was compromised. About two million people were affected. It posted a public advisory and informed the federal commissioner on March 10, and sent a preliminary report on March 27. Direct notices to individuals began on October 19. The company's letter to the commissioner attributes that delay to "the extensive data analysis, de-duplication and validation process."

The letter commits the company to confirm that notification is complete, explain how the data was reviewed, and obtain an independent security assessment. It is not an admission of fault, the commissioner has published no finding, and the investigation stays open until those commitments are met.

A small firm has far fewer records, and the same question to answer: which people, and which customers, are in this system? A firm that wrote the answer down beforehand starts from a list. A firm that did not starts from the logs.

Source: Office of the Privacy Commissioner of Canada, compliance letter, file PIPEDA-054471

You are not out of the picture

Telling your customer does not end your own exposure. You still owe safeguards for what you hold, as an organization in your own right: PIPEDA Schedule 1 clause 4.7 and Alberta PIPA s.34.

Also in October 2026, the federal commissioner opened an investigation into a commercial company running a tip platform for a not-for-profit's chapters. PIPEDA generally does not apply to not-for-profits. The company's own safeguards are what will be examined, and no finding has been made.

What to do this week

None of this needs software. A spreadsheet is fine.

  1. List the customers whose personal information you hold or can reach. Include the ones reached through a system you only maintain.
  2. Beside each one, write the notice term from the contract: the period, what starts it, and who to contact. Write "none" where there is none, which is also worth knowing.
  3. List your systems and providers, and match them to customers. Your cloud storage and your bookkeeping software may hold different people.
  4. Keep a copy somewhere the incident cannot reach. If your email is the thing that was compromised, the list cannot live only there.
  5. Sort the list by shortest notice period. That is your calling order.
  6. Give your IT provider a copy, and agree who calls whom. In many small firms, each assumes the other will.

Where ClearBreach fits

The compliance assessment produces an incident response plan and a personal information inventory from your own answers, so you know what you hold and where before something goes wrong. If a breach happens, the breach assessment shows what is reportable for information under your control, and produces the regulator report and the record.

Neither one tracks your customers' contract deadlines today.

We're building that. It isn't available yet. The idea is simple: pick the affected systems and see which customers to tell, soonest deadline first. You would still write your own messages. If you need this, email us with what your customers ask of you.

Privacy case of the month

Once a month, a five-minute read: a real case a Canadian privacy commissioner investigated, what went wrong, and what to check in your own organization so it doesn't happen to you. Written for organizations under federal, Alberta and BC privacy law. Not written for Quebec.

We send one email to confirm. Nothing else arrives until you confirm, and an unconfirmed address is deleted after 7 days. Sent by ClearBreach Technologies Inc. Mailing address and contact details · Privacy policy

Frequently asked questions

Do I have to report a breach of my customer's data to the regulator?

Usually not. PIPEDA s.10.1(1) and Alberta PIPA s.34.1(1) place the duty on the organization with the personal information under its control, which is normally your customer when you only process data for them. Your job is to tell that customer quickly and give them the facts. If the breach also touched your own staff or customer records, those are yours to assess.

How quickly do I have to tell my customer?

Your contract sets that, if it says anything. Privacy law gives no fixed number of hours to a supplier. Read the term for two things: the period, and what starts it, because 'becoming aware' and 'suspecting' begin at different moments. With no term at all, tell them right away, since they cannot start their own assessment until they know.

Should I wait until I know exactly what happened?

No. Tell them what you know and what you do not, then update them. 'We cannot yet say whether the data was accessed' is a useful thing to tell a customer, because they have to assess that uncertainty too.

This guide is educational and does not constitute legal advice. It is grounded in the text of PIPEDA, Alberta PIPA, and BC PIPA and published guidance from the OPC, OIPC Alberta, and OIPC BC. If your situation involves regulatory investigation, litigation risk, or circumstances not addressed here, engage a qualified privacy lawyer.

Find out what this incident requires of you

See whether you must report, to whom and by when, under each privacy law that applies to you.

How ClearBreach handles a breach →

See plans and pricing →