Guide

Employee privacy when you automate: what Canadian businesses need to know

Any project that looks at how your team works touches employee personal information: files, calendars, email metadata, app usage. Which rules apply depends on where you operate. Here is what to check before you start, whoever runs the project.

Updated · 4 min read

Why automation projects touch employee information

To find out how work really happens, a discovery project looks at the traces work leaves: shared files, recurring calendar events, who emails whom, which applications people use. Even when no one reads a message, that information is about identifiable employees. So the question is not whether privacy rules apply, but which ones.

Which law applies to your employees' information

Where you operateMain law for employee information
QuébecThe Act respecting the protection of personal information in the private sector, as amended by Law 25. It applies to personal information a business holds about anyone, employees included.
Alberta, British ColumbiaEach province's Personal Information Protection Act (PIPA), which covers employee personal information.
Federally regulated businesses (for example banks, airlines, telecoms, interprovincial transport)PIPEDA, the federal private-sector privacy law, covers their employees' information.
Other provinces, provincially regulated employersPIPEDA does not cover their employees' information. In Ontario, employers with 25 or more employees must have a written policy on electronic monitoring.

Sources: Office of the Privacy Commissioner of Canada on federally regulated employers, on provincially regulated employers and on substantially similar provincial laws; Québec's Act, section 1.

If you operate in Québec: Law 25

Law 25 strengthened Québec's private-sector privacy act in three stages between 2022 and 2024. These obligations matter most for a discovery or automation project:

  • A person in charge of personal information (section 3.1). By default it is the person with the highest authority in the business, usually the owner, who can delegate all or part of the role in writing. Their title and contact details must be published on your website, or made available another way if you have none.
  • A privacy impact assessment (section 3.3) for any project to acquire, develop or overhaul an information system or electronic service delivery system that involves personal information. The person in charge is consulted from the start.
  • Technology that can identify, locate or profile someone (section 8.1). People must be told beforehand that it is used, and how to activate those functions. The Commission d'accès à l'information reads this as meaning they cannot be on by default.
  • Decisions based only on automated processing (section 12.1). The person must be told no later than when they learn of the decision. On request, they can find out what information was used and the main reasons, and ask someone at the business to review it.
  • Confidentiality incidents (sections 3.5 to 3.8). If an incident presents a risk of serious injury, you must promptly notify the Commission and the people affected, and keep a register of all incidents.
  • Consent (section 14) must be given for specific purposes and requested separately for each one, in clear and simple language.

Sources: the Act (CQLR c P-39.1) and the Commission d'accès à l'information's summary of the Law 25 changes (in French).

If you operate in Ontario: electronic monitoring policies

Under the Employment Standards Act, employers with 25 or more employees in Ontario on January 1 of a year must have a written policy on electronic monitoring in place before March 1. It must say whether the employer monitors employees electronically and, if it does, how, in what circumstances and for what purposes the information may be used. Employees get a copy within 30 days, and again after any change.

The rule is about transparency: it does not create a right not to be monitored. A discovery project that collects app usage or email metadata is still a good moment to write or update the policy, because it is exactly what the policy describes.

Source: Ontario's guide to the Employment Standards Act.

A checklist before any discovery or automation project

Whatever your province, and whoever runs the project, these make it both compliant and acceptable to your team:

  • A written notice to employees: what is collected, why, who sees it, and how long it is kept.
  • An opt-in per employee for anything beyond shared work files, such as app usage or email metadata.
  • Metadata instead of content wherever it is enough: senders and subjects, not message bodies; time per application, not screenshots or keystrokes.
  • A privacy impact assessment: required in Québec for information system projects, good practice everywhere else.
  • A retention period and a date when project data is deleted.
  • A way for each person to see and correct what was collected about them.
  • No scoring of individuals. Map the work, not the people.
  • A pause that stops all collection at once.

How we run discovery

  • Access starts at zero. You choose what to share, read-only by default, and you can revoke it at any time.
  • Observe first, ask last. We use what you share to prepare short confirmation questions, so no one sits through a long interview.
  • Metadata, not content, by default. If we look at app usage, it is aggregated time per application and website, never screenshots, keystrokes or page content.
  • Each person confirms their own steps before the owner approves the map.
  • We map work, not people. There is no employee scoring.

See what the result looks like in our example workflow map, or read how the whole AI automation assessment works.

Get started

Start with one workflow.

Book a free 20-minute build call. You'll leave with a clear view of what to automate first, and a proposal the same day.

Book a 20-min build call hello [at] intelligence33.com