An officer calls, or emails, or arrives. They are investigating something, they need information about one of your customers, and they would like your help. Most small business owners' instinct is to cooperate immediately, because refusing feels obstructive. That instinct is the problem: handing over personal information you were not required to hand over is its own liability, and under Canadian privacy law it is your decision to get right, not the officer's.
This is not a guide about being difficult with police. It is about knowing which of three very different situations you are in.
The three situations
An informal request. Someone asks you to provide information voluntarily. There is no court involvement and nothing compels you. This is the most common form and the one that causes the most trouble, because it looks identical to the others if nobody reads carefully.
A production order or warrant. A judge has authorised it. It names what must be produced and by when. Here you are generally required to comply, and your job shifts from whether to how: produce exactly what is specified, nothing more.
An emergency. A genuine, imminent risk to someone's life or safety. Canadian privacy law contemplates disclosure in those circumstances, and this is the situation where acting quickly is the right call. It is also the framing most easily asserted, so it is worth being able to tell the difference.
What PIPEDA actually allows
PIPEDA permits, but does not require, disclosure without consent in certain situations, including to a government institution that has identified its lawful authority and is requesting the information for law enforcement purposes. The word that does the work is permits. An exception that allows you to disclose is not an instruction to.
Two practical consequences. If an officer has not identified a lawful authority, you are not in the exception, and disclosing anyway is a disclosure without consent that you cannot justify. And where you are compelled by a warrant or production order, complying is straightforward, but complying with more than the order asks for is not covered by it.
Some sectors carry additional duties. Lawyers have privilege obligations, health professionals have their college's rules, and regulated financial institutions have their own regime. If you are in one of those, your professional obligations come first.
What to actually do when the request arrives
- Be courteous and slow. "I want to help, and I need to check what I am permitted to provide. Can you send the request in writing?" That sentence is not obstruction and no reasonable investigator treats it as such.
- Get it in writing, always. Name, badge or identifier, agency, file or incident number, the lawful authority relied on, and precisely what is sought. If it cannot be put in writing, that tells you something.
- Verify independently. Call the agency's published main number, not the number you were given. Impersonating law enforcement to extract customer data is a real tactic, and a small business is a soft target for it.
- Read what is actually being asked for. Requests are often broader than the investigation needs. "All records relating to this customer" and "the transaction on this date" are very different disclosures.
- Produce the minimum that satisfies the order. If a warrant covers one account, do not send the whole export because it was easier. Over-disclosure is the most common mistake and the one with your name on it.
- Escalate internally. One named person decides, and it should not be whoever happened to answer the phone. Staff need a single instruction: take details, promise nothing, pass it up.
- Write it down. Date, who asked, what authority, what you decided, what you disclosed, who approved it. This record is your defence if the disclosure is ever questioned.
- Call a lawyer when the stakes are real. Anything involving privileged or health information, an unusually broad demand, a gag provision, or a request you are inclined to refuse is worth an hour of advice.
Decide the policy before it happens
A half-page written procedure is enough: who may receive such a request, who decides, what must be obtained in writing first, that verification happens via a published number, that disclosure is limited to what is compelled, and that everything gets logged. Fold it into your privacy management programme so it is a decision already made rather than one taken under pressure at the counter.
While you are there, note that the best protection against this entire category of problem is holding less. A retention schedule that deletes what you no longer need means there is simply less to compel, which is the quiet argument for records retention that has nothing to do with storage costs.
Why this is live right now
Canada's Bill C-22, the Lawful Access Act, 2026, is in Senate committee study, and the Privacy Commissioner has asked for amendments including narrowing which entities can be compelled to produce subscriber information. In other words, the scope of who can be required to hand over what is being actively debated. Whatever emerges, the operational question for a small business is the same one it is today: can you tell a request from an order, and does someone know what to do with either.
What this means for your business
You will probably never receive a production order. You are considerably more likely to get a phone call, and the cost of answering it badly is a disclosure you cannot justify to a regulator or a customer. The fix is half a page and one named decision-maker. That is a cheaper problem to solve now than to explain later, and it is the kind of thing we put in place with clients as part of ordinary privacy housekeeping.