ClearBreach

← Guides·All compliance guides →

Your SituationWe are adding a new vendor or software →

PIPEDAAB PIPABC PIPAAll sectors

Questions to Ask Before You Buy an AI Tool

By Yong DuPublished Reviewed

Share on LinkedIn

Twelve privacy questions for any AI vendor, what a good answer looks like, and when to walk away.

An AI vendor's sales page won't tell you what you need to know. Before client or staff information goes into a tool, ask the vendor these twelve questions. If you can't get clear answers, don't put personal information into it.

You stay responsible for personal information you hand to a vendor. As BC's privacy commissioner puts it, a business "cannot avoid its obligations under PIPA by contracting with another organization". Federal and Alberta law take the same general position on accountability.

The list draws on BC's guidance on AI scribes. That guidance was written for health care, so it applies to other businesses by analogy, not as a rule. It's still the most practical list a Canadian regulator has published. For a tool that will never see personal information, you can skip most of this.

The twelve questions

Ask Why it matters A good answer
1. What personal information do you collect, use and share? You must be able to explain it to clients and staff A specific list, in writing
2. Do you use our data to train your models? The vendor may have purposes of its own No by default, or a clear opt-out
3. Do you use "de-identified" versions of it? The term has no standard meaning An explanation of what's removed
4. Do you sell or share it with third parties? Each sharing adds risk No, or a named list
5. Does anything leave Canada? You may need to tell people Named countries and protections
6. How long do you keep it, and can we change that? Prompts and recordings shouldn't sit forever A set period you control
7. Can we delete our prompt history and records? You remain responsible for the information Yes, on your instruction
8. How do you check accuracy? AI makes mistakes Regular testing, ideally independent
9. Will you tell us before features change how data is handled? A tool can quietly start doing more Notice in advance, with a choice to accept or decline
10. Can we report errors and bias, and will you act? You'll need a fix A clear route and a response
11. What security do you have, and will you share audit results? Safeguards must suit the sensitivity Encryption, multi-factor sign-in and independent results
12. Will you tell us about your own breaches? You may have duties to act on one Yes, promptly, in writing

Also ask what happens to your data if the contract ends or the company is sold or goes bankrupt. And ask who controls the records: the answer should be you.

Three warnings

Compliance claims prove little. BC's commissioner says: "Don't take a vendor's word for it that they are PIPA compliant." There's no Canadian accreditation program for privacy claims, so a badge or a line on a website doesn't settle anything.

"De-identified" isn't a safe word. BC PIPA has no such category, and BC's commissioner warns the term has no standard meaning. Data a vendor calls de-identified may still be personal information.

Free tools usually have different terms. A vendor's business plan and its free version can treat your data differently. Read the terms for the plan you'll actually use.

When to walk away

Don't use the tool for personal information if:

  • the vendor won't say whether it trains on your data;
  • you can't delete your information;
  • it can't say where your information is stored;
  • it won't tell you about its own breaches;
  • its only answer is "we're compliant".

The BC guidance puts the test plainly: if you can't identify your legal authority, "don't go ahead with it!"

After you choose

Keep the answers. Save the vendor's replies with the date, so you can show your reasoning later.

Turn on the protective settings. Use a work account, multi-factor sign-in and any training opt-out. Regulators want vendors to offer the most protective settings by default, but check rather than assume.

Check your privacy policy. If the tool changes how you handle personal information, update it. Alberta businesses using service providers outside Canada have specific policy duties.

Look at the terms again each year, and whenever the vendor announces new AI features.

Consider a privacy impact assessment if the tool touches client records. Regulators recommend one for AI that handles personal information. See privacy impact assessments in Canada.

These are questions to ask, not contract wording. Our guide to making service providers accountable covers what a written arrangement should address.

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

Frequently asked questions

A vendor says it is PIPEDA compliant. Is that enough?

No. BC's privacy commissioner warns businesses not to take a vendor's word for it, and notes that Canada has no accreditation program for privacy compliance claims. A claim about one law doesn't settle another. Ask how the vendor handles your information, and get the answers in writing.

What does de-identified data mean when a vendor says it?

It may mean less than it sounds. BC's commissioner says the term has no standard meaning, and that a vendor's de-identified data is often still personal information. Ask what is removed, and whether the data could be linked back to a person.

Is it a problem if an AI vendor stores data outside Canada?

Not automatically. Alberta and BC businesses must still protect the information, and Alberta PIPA requires your policies to say so when service providers outside Canada are used. Know where the data goes and what protects it, and tell people as your law requires.

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.

Check an AI tool before client data goes in

See a completed privacy impact assessment for a new system: the risks identified, the mitigations recommended, and the record it leaves behind.

See a completed PIA →

See plans and pricing →