Bill C-36 Legitimate Interest: Who Decides? | Elacity
Canada's Bill C-36 would let a company skip your consent when it decides its interest outweighs your harm. The real issue is who holds the scale, and who holds the terms.
Bill C-36 and Legitimate Interest: Who Decides Your Consent Is Optional
Under the Bill C-36 legitimate interest clause, a company could collect, use or disclose your personal information without your knowledge or consent if it judges that its interest outweighs any foreseeable harm to you. Read that twice. The party that profits from your data is the party holding the scale.
Health researchers have noticed. In a commentary in the Canadian Medical Association Journal, they argue the clause leaves patient records exposed just as Ottawa pushes AI into health care. "What's concerning about this is it's the company that's making the decision," co-author Dr. Sheryl Spithoff told CBC News on November 9.
What Bill C-36's Legitimate Interest Clause Actually Says
The bill's default is sound: consent comes first, and the information you get before you agree must be specific and written in plain language. The trouble sits in the exception.
That exception has real conditions. As Norton Rose Fulbright summarises the bill, the organisation's interest must outweigh any reasonably foreseeable adverse effect, a reasonable person must expect the use, and the data cannot be used to influence your behaviour or decisions. A privacy impact assessment has to come first.
Now look at who applies each test. The company describes its own interest, assesses its own risk, takes its own mitigating steps, and keeps the record until the regulator asks to see it. You are the subject of that file, not a party to it.
Why an Old Exception Bites Harder Now
Europe has used this legal basis for years. The GDPR allows processing for legitimate interests except where they are overridden by the interests or fundamental rights and freedoms of the person the data describes. The CMAJ authors point to that override as the guardrail Bill C-36 leaves out.
The gap matters more today than when the GDPR was written. The most valuable thing to do with a health record in 2026 is to train a model on it, and once a record has shaped a model there is no consent left to withdraw.
The commentary's own example shows the pattern. A consolidated class action against Tempus AI alleges that after buying Ambry Genetics, the company took patients' genetic data, trained AI on it and licensed it to drug and biotech partners without their written consent. These are allegations a court has not yet tested, and Tempus will have its defence heard.
We have looked at what a single medical record sells for before. The price is real. The person it describes is rarely at the table when it is set.
The Honest Case for the Clause
Concede the strongest point. Fraud detection, network security and medical research all depend on data that nobody approved for that exact purpose, and a fresh consent form for every use would stall work that saves lives.
The bill also draws one line the GDPR does not. Its exception excludes any use meant to influence your behaviour or decisions, which, as one Canadian compliance guide notes, keeps direct marketing outside it. Credit where it is due.
Clickthrough consent is also mostly theatre already. Few people read the terms they accept, so a stricter consent rule alone would protect paperwork more than people.
So the real question is not consent versus no consent. It is who holds the terms when a use becomes valuable, and whether the person in the data is a party to the deal or a line in someone else's impact assessment.
From Permission to Property
Every privacy law so far, Bill C-36 included, treats you as someone to be asked. The data stays with the institution, and the law only decides how politely it must ask, or when it need not ask at all. Deleting data after the fact has the same flaw: it starts after the copy exists.
Elacity starts from a different premise. The data, the work and the rights that describe you should be property you hold, on terms you set. That is what we are building Elacity dDRM for: packaging what you own into a Wealth Capsule whose terms of use are written by its owner, so a lab, a buyer or an AI agent comes to you for a licence instead of running a balancing test about you.
We will not pretend this reaches the records a hospital already holds. What it changes is the default for what you create and share from here on: a licence you grant, not an exception someone else claims.
"The people who create the value should own it. That is the entire reason Elacity exists." Sasha Mitchell, Founder, Elacity
Bill C-36 is still a proposal, and Parliament can still add the override the GDPR has. Whatever it decides, the lesson holds: a right the other side gets to weigh is a courtesy, and a right you hold is property.
More on ownership over permission lives in The Manifesto. To follow the argument as it develops, Follow Elacity on X.