ClearBreach

← Guides·All compliance guides →

Your SituationWe are adding a new vendor or software →

PIPEDAAB PIPABC PIPAAll sectors

Does Your IT Provider Handle Your Privacy Obligations?

By Yong DuPublished Reviewed

Share on LinkedIn

Your IT provider runs the systems. Your business still owns the privacy duties. Who does what, and what to agree now.

On this page

Many small businesses assume their IT provider looks after privacy. The provider runs the computers, the email, the backups and the security software, so privacy feels like part of the same job.

Researchers at the University of Guelph found exactly that gap when they interviewed Canadian business owners and the providers who serve them. Owners "assumed complete cybersecurity management by third-party vendors, while vendors saw their role as advisory." Neither side was wrong about its own role. They simply never agreed on it, and the gap shows up at the worst moment: during a breach.

This guide sets out who usually does what, and the short conversation that closes the gap.

The short answer

Your IT provider can do much of the work. Your business keeps the responsibility.

That is the law, not a contract term. Under federal law, an organization "is responsible for personal information in its possession or custody, including information that has been transferred to a third party for processing" (PIPEDA, Schedule 1, clause 4.1.3). Alberta PIPA s.5(2) says the same in its own words, and BC PIPA s.4(2) makes an organization responsible for personal information under its control, even when it is not in its custody.

So the useful question is not whether your provider handles privacy. It is which parts they handle, and whether you both know which parts are yours.

Who usually does what

Every arrangement is different, so treat this as a starting point to confirm with your provider, not a rule.

Task Usually your IT provider Usually your business
Running systems, backups and updates ✓
Security tools, such as multi-factor sign-in and antivirus ✓ Decides who gets access
Spotting and containing a security incident ✓
Telling you promptly about an incident, with the facts ✓
Deciding whether a breach must be reported Supplies the facts ✓
Notifying the regulator and the people affected ✓
Keeping a record of every breach Can help ✓
Your privacy policy, and naming who is responsible for privacy ✓
Rules for staff on handling client information Can advise ✓
Agreements with every service provider that handles personal information ✓

The bold rows matter most. Under federal law and Alberta PIPA, the duty to assess a breach and report it sits with the organization that controls the information (PIPEDA s.10.1, Alberta PIPA s.34.1). Federal law also requires you to keep a record of every breach involving personal information under your control, reportable or not (PIPEDA s.10.3). British Columbia works differently, and the BC PIPA breach reporting guide explains how.

Where it usually goes wrong

The provider finds the problem, and assumes you will take it from there. They contain it on a Friday and send a short note. You read it on Monday, unsure whether it is serious. Meanwhile the clock on reporting has already started. Knowing in advance that the decision is yours, and what facts you will need to make it, turns that weekend into an orderly handover.

"We're compliant" is heard as "you're compliant." A provider can meet its own obligations perfectly and still not be doing yours. Your privacy policy, your privacy officer and your breach decisions are not things a provider can hold for you.

The work doesn't match the need. The same research heard from owners who felt pushed toward security measures beyond what their business needed. A clear agreement on what you actually need cuts both ways: nothing important missed, nothing unnecessary sold.

Five questions to ask your IT provider this week

These are questions to start a conversation, not contract wording. The answers tell you where your part begins.

  1. If you find an incident affecting our data, how quickly will you tell us, and what will you tell us? You need what happened, when, which information could have been reached, and what is still unknown.
  2. What records do you keep that would show what was accessed, and for how long? Without them, it is hard to tell whether a breach affected anyone.
  3. Who else handles our information through you, such as other software providers or subcontractors, and where are they located?
  4. What happens to our information and access when we stop working together?
  5. Is our arrangement written down, including the answers above?

If an answer is "we haven't thought about that," that is useful to know now. Our guide to making service providers accountable covers what a written arrangement should address.

Three things to do this week

  1. Write down the split. One page: what your provider does, what you do. The table above is a starting point.
  2. Name the person in your business responsible for privacy. In a small business it is often the owner. See do I need a privacy officer?
  3. Agree how incidents reach you, and who on your side receives them, including outside business hours.

If you are an IT provider reading this

Your clients probably think you have their privacy covered. A short conversation in the first week, about what you do and what stays with them, prevents a difficult one during an incident. Our guides for providers cover the privacy questions worth asking when onboarding a client and who notifies whom when a client has a breach.

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

Sources

  • Hoong, Y. and Rezania, D. (2024). "Balancing talent and technology: Navigating cybersecurity and privacy in SMEs." Telematics and Informatics Reports, 15, 100151. Open access: doi.org/10.1016/j.teler.2024.100151. The study was supported in part by the Office of the Privacy Commissioner of Canada.

Frequently asked questions

My IT provider says they are compliant. Does that cover my business?

No. A provider can run its own business in compliance with privacy law and still not be doing the things the law asks of yours. Deciding whether a breach must be reported, notifying the people affected, publishing a privacy policy and naming someone responsible are duties of the organization that controls the information, which is you.

Can I make my IT provider responsible in the contract?

You can make them responsible to you for doing their part: protecting the systems, telling you quickly about an incident, giving you the facts. You cannot move your legal accountability to them. The law holds your business responsible for information it controls, including information a provider handles for you.

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.

See what to check before you sign up

A completed privacy impact assessment: which law applies, where the information goes, and the risks to address first.

How ClearBreach reviews a new vendor →

See plans and pricing →