IRM Consulting & Advisory
Data Security & Privacy

Why Privacy Matters

Privacy is now a sales and legal issue for small businesses. PIPEDA, Quebec Law 25 and US state thresholds explained, plus a step-by-step PIA for a small team.

Privacy is now a sales and legal question for any small business selling in Canada and the US. Here is which laws apply at your size, and how to run a privacy impact assessment without a privacy team.

A privacy impact assessment (PIA) is a written analysis, done before you launch a system or share personal data, of what personal information you collect, why, where it goes, who sees it, and what could harm the people it describes, ending with safeguards. Quebec requires one in defined cases; elsewhere it is your best evidence of care.

Every few weeks we get a version of the same call. A 70-person SaaS company has a six-figure enterprise deal in legal review, and procurement has sent a privacy questionnaire. Question 14 asks for "your most recent PIA for the in-scope service". Nobody has written one. The deal stalls for three weeks while the founder learns what a PIA is. That stall is why privacy matters for a small business now: a sales issue first, a legal issue a close second.

Which privacy laws apply to a small business in Canada?

PIPEDA covers private-sector organizations handling personal information in commercial activity. There is no employee or revenue floor. Since November 1, 2018, any breach that creates a real risk of significant harm must be reported to the Privacy Commissioner and the affected individuals, and every breach must be recorded and kept for 24 months. Knowingly failing to report or record one can bring fines of up to $100,000. In June 2026 Ottawa tabled Bill C-36, which would replace PIPEDA's privacy rules with penalties of up to $10 million or 3% of global revenue. It is a bill, not law. Build to PIPEDA today.

Quebec's Law 25 amended the province's private-sector privacy act and is the strictest regime in Canada. Again, no size threshold. The person with the highest authority is the privacy officer by default unless the role is delegated in writing, and the officer's title and contact details must be published. Incidents presenting a risk of serious injury go to the Commission d'accès à l'information and the people affected, and every incident goes in a register.

Administrative penalties reach $10 million or 2% of worldwide turnover, and penal fines $25 million or 4%, whichever is greater. Individuals can sue too. Punitive damages of at least $1,000 are available only where the infringement was intentional or resulted from gross fault. They are not automatic, and anyone who says otherwise is selling fear. Health data adds provincial laws such as Ontario's PHIPA; see our guide to personal health data security.

When does Quebec Law 25 require a privacy impact assessment?

This is the part most businesses outside Quebec miss. Law 25 requires a PIA:

  1. Before acquiring, developing or overhauling an information system or electronic service involving personal information (section 3.3). A new CRM, app or AI feature qualifies.

  2. Before communicating personal information outside Quebec, or entrusting someone outside Quebec with it (section 17). That includes Ontario and any US cloud region.

  3. Before sharing personal information for research without consent (section 21).

The section 17 assessment weighs sensitivity, purposes, safeguards including contracts, and the legal regime where the data lands. The transfer is allowed only if the PIA concludes the data will be adequately protected, backed by a written agreement. You cannot hand this to your cloud provider. In practice, any SaaS company with Quebec customers hosted outside the province needs at least one PIA on file. That is most of the companies we talk to.

Which US state privacy laws apply at your size?

There is still no federal US privacy law. Twenty states have comprehensive laws in effect in 2026 (counting Florida's narrower one), with Indiana, Kentucky and Rhode Island added on January 1. "We are too small" is often wrong.

  • The common baseline. Virginia's model, copied by many states, applies if you control or process personal data of at least 100,000 consumers in that state in a year, or 25,000 consumers if over half your gross revenue comes from selling personal data.

  • Lower bars. Delaware, Maryland and Rhode Island start at 35,000 consumers, or 10,000 if you earn more than 20% of revenue from selling data.

  • No count at all. Texas and Nebraska exempt businesses that meet the US Small Business Administration's definition of a small business. Even then, those small businesses must get consent before selling sensitive personal data.

  • California. The CCPA applies if annual gross revenue exceeds $26,625,000 (the 2025 inflation-adjusted figure), or you buy, sell or share data of 100,000 or more California consumers or households, or you earn half your revenue from selling or sharing it. Fines run to $2,663 per violation and $7,988 per intentional violation.

California is also where assessments became mandatory in the US. Rules effective January 1, 2026 require risk assessments for higher-risk processing, with attestations due by April 1, 2028, and cybersecurity audit certifications phase in by revenue through April 1, 2030. A Law 25 PIA and a California risk assessment overlap heavily. Write one document that satisfies both.

How do you run a privacy impact assessment with a small team?

For a 30 to 200 person company this should take days, not months. Here is the sequence from our data security and privacy work, scaled down.

Step 1: Scope one system or one data flow

Pick the product, vendor or cross-border transfer that triggered the question. A PIA on "the whole company" never finishes.

Step 2: Build the data inventory

List each category of personal information, its source, purpose, storage location (vendor and region), who can access it, and when it is deleted. A spreadsheet is fine. This step finds most of the risk, including the shadow AI tools staff paste customer data into.

Step 3: Map the flows and the borders

Draw where data moves, including analytics, support tools and sub-processors. Mark every point where it leaves Quebec, Canada or the US.

Step 4: Test necessity

For each data element, ask whether you need it. Dropping a field you do not use is the cheapest control there is.

Step 5: Score the risks and pick safeguards

Rate likelihood and harm to the individual, not the company. Then choose safeguards: encryption, access reviews, retention limits, contract terms and a tested incident response plan. Our process, risk and controls work uses the same scoring.

Step 6: Sign, file and set a review date

The accountable executive signs. File it where procurement can find it. Revisit it when the system or vendor changes.

Privacy obligations vs effort: what to do first

Obligation

Applies to

Effort for a 50-person team

Our opinion

Name a privacy officer and publish contact details

Law 25; good practice everywhere

One hour

Do it this week. It is free and it is the first thing a Quebec customer checks.

Breach and incident register

PIPEDA (24 months), Law 25

Half a day to set up

Non-negotiable. An empty register you can show beats a full one you cannot find.

Data inventory

Everyone

2 to 4 days

The highest-value privacy work a small company can do. Skip anything else before this.

PIA for cross-border transfers and new systems

Law 25 (mandatory), California risk assessments

3 to 5 days per system

Write one template that satisfies Quebec and California. Doing them separately is wasted money.

Consumer rights request process

US state laws, CCPA, Law 25

1 to 2 days

A shared inbox and a written procedure are enough below a few requests a month. Do not buy a platform yet.

Cookie consent and privacy notice rewrite

Most regimes

1 to 3 days

Overbought. Fix the notice so it matches reality before you pay for a consent manager.

Annual cybersecurity audit (California)

Larger CCPA businesses

Weeks, external

Not your problem until your revenue tier's deadline. Do not let anyone sell it to you early.

Why the cheap rows matter: IBM's Cost of a Data Breach 2026 puts the global average at $4.99 million. A small business will not hit that number, but legal, forensics, notification and lost deals scale down far less than revenue does.

When is a full privacy program premature?

We turn down privacy program engagements regularly. If you sell only to businesses, hold no sensitive data, have no Quebec customers and sit below every US threshold, a one-page inventory, a published privacy contact and a breach register are enough. A 40-page program will sit unread.

If all your personal data lives inside one well-run platform such as payroll or a CRM, your risk lives in that contract. Read the data processing terms and confirm the hosting region first. If you are pre-product, write the inventory as you build. Retrofitting costs more.

What changes the answer: health, financial, biometric or children's data; Quebec customers; crossing a US threshold; an enterprise buyer asking for a PIA; or an ISO 27001 or SOC 2 audit with privacy in scope. Then privacy belongs inside your governance, risk and compliance work, with someone accountable.

For most clients that someone is fractional, not a hire. Our Virtual CISO service starts at the Crawling tier from $2,000 a month, enough to deliver the inventory, first PIA and register in a quarter. Details are on our pricing page.

Frequently asked questions

Does PIPEDA apply to a business with five employees?

Yes. There is no size threshold. Quebec, Alberta and British Columbia have their own private-sector laws for activity within those provinces; PIPEDA covers the rest and cross-border flows.

Can a Quebec customer automatically get punitive damages after a breach?

No. Law 25 allows punitive damages of at least $1,000 only for intentional infringement or gross fault. A documented PIA and prompt incident response are your evidence it was neither.

How long does a first PIA take?

For one system, three to five working days spread over two weeks, mostly on the inventory. If you want help scoping it, book a consultation.

Keep Reading

Related Articles

Our Industry Certifications

Our diverse industry experience and expertise in AI, Cybersecurity & Information Risk Management, Data Governance, Privacy and Data Protection Regulatory Compliance is endorsed by leading educational and industry certifications for the quality, value and cost-effective products and services we deliver to our clients.

Copyright © 2026 IRM Consulting & Advisory. All Rights Reserved.