Skip to main content

Building Software in Canada That Meets Privacy Law: PIPEDA, Law 25 and Health Data

What Canadian privacy law means for the software you build: PIPEDA, provincial laws including Quebec's Law 25, health information acts, data residency and the design practices that make compliance practical.

Bytesavy5 min read

Short answer: most Canadian businesses that collect personal information must follow PIPEDA or a substantially similar provincial law (Alberta, British Columbia and Quebec have their own private-sector laws). Quebec's Law 25 adds the strictest requirements, including privacy impact assessments and privacy by default. Health information is covered by separate provincial acts such as Ontario's PHIPA, Alberta's Health Information Act and Manitoba's PHIA. For software, this translates into a practical set of design choices: collect only what you need, control and log access, encrypt data, plan for breaches and make it easy to answer access and deletion requests.

This article is general information for software planning, not legal advice. Confirm your obligations with a privacy professional.

Which privacy laws apply to Canadian software?

LawWho it coversHighlights for software
PIPEDA (federal)Private-sector organizations handling personal information in commercial activity, outside provinces with substantially similar laws, and federally regulated businessesConsent, limited collection, safeguards, access requests, breach reporting when there is a real risk of significant harm
Alberta PIPA and British Columbia PIPAPrivate-sector organizations in those provincesSimilar principles to PIPEDA
Quebec Law 25Organizations handling personal information of people in QuebecPrivacy officer, privacy impact assessments, privacy by default, consent rules, data portability, significant penalties
Provincial health acts (PHIPA, HIA, PHIA and others)Custodians of personal health information and their service providersStricter rules on use, disclosure, access logging and agreements with vendors
Public-sector lawsGovernment bodies and many public institutionsFreedom of information and protection of privacy requirements, sometimes including data residency

Federal privacy reform has been proposed several times, so check the current status of federal legislation when planning a long-lived system.

What does privacy by design mean in practice?

Collect less

Every field you collect is data you must protect. Ask why each piece of personal information is needed, and drop what is not.

Control access by role

Staff should see only the data their job requires. Role-based access control, with permissions enforced on the server and in the database (for example with row-level security), is the foundation.

Log who accessed what

Audit logs that record who viewed or changed personal information are essential for health data and valuable everywhere. They also make breach investigations possible.

Encrypt in transit and at rest

Use HTTPS everywhere and enable encryption on databases, backups and file storage. The major cloud platforms make this straightforward.

Set retention rules

Decide how long each kind of data is kept, and delete or anonymize it automatically when the time is up.

Make rights requests easy

Individuals can ask what you hold about them and, under Law 25, request their data in a portable format. Build tools that let staff find, export and correct a person's records quickly.

Plan for breaches

Know how you will detect, contain, assess and report a breach. PIPEDA and Law 25 both require reporting and record keeping for qualifying incidents.

Does our data have to stay in Canada?

Not always. PIPEDA does not generally prohibit storing data outside Canada, but you remain accountable for it and should be transparent with customers. Quebec's Law 25 requires a privacy impact assessment before personal information is transferred outside Quebec. Some public-sector bodies, health organizations and contracts do require Canadian residency. AWS, Microsoft Azure, Google Cloud and Supabase all offer Canadian regions, so residency is achievable when needed. Remember to check backups, logs, email and AI services as well as the main database.

What about AI features and privacy?

AI features raise specific questions: what personal information is sent to a model, where it is processed, whether it is retained and whether it is used for training. Choose providers and regions deliberately, send only the data the task needs, and document the flow in your privacy impact assessment. Our guide to building AI agents with Claude covers practical guardrails.

A checklist for your next project

  • Identify which privacy laws apply to you and your users.
  • List the personal information the system will collect and why.
  • Complete a privacy impact assessment where required.
  • Design role-based access and audit logging.
  • Encrypt data in transit and at rest.
  • Choose hosting regions that meet residency needs.
  • Define retention and deletion rules.
  • Build tools for access, correction and portability requests.
  • Write and test a breach response plan.
  • Sign appropriate agreements with every vendor that handles personal data.

Frequently asked questions

Does PIPEDA apply to small businesses?

PIPEDA applies to organizations collecting, using or disclosing personal information in the course of commercial activity, regardless of size, unless a substantially similar provincial law applies instead.

Do we need a privacy officer?

Under Quebec's Law 25, the person with the highest authority is the default person in charge of protecting personal information unless the role is delegated. PIPEDA also requires an accountable individual. Having a named privacy lead is good practice everywhere.

Can a software vendor make us compliant?

A development partner can design and build software that supports compliance, but compliance remains the responsibility of your organization and its policies.

Build privacy into your software

Bytesavy designs around the privacy rules your organization operates under and documents how the system handles them. Explore our custom software and cloud services, see industries we build for, or book a scoping call.

Facing a challenge like this one?

We design, build and modernize the systems essential industries run on. Tell us what you are working on.

Book a scoping call

A reply within one business day. No obligation.

Prefer email? sales@bytesavy.com