← Guides·Privacy law by industry →
Your SituationWe want our privacy basics in place →
Privacy Law for HR and Recruitment Firms in Canada
By Yong DuPublished Reviewed
PIPEDA and provincial PIPA for Canadian HR firms, candidate data, background check consent, breach reporting, and third-party employer obligations.
An HR or recruitment firm is covered by Alberta PIPA in Alberta, BC PIPA in BC, and PIPEDA elsewhere. It answers for two sets of data: its own, and the employee data it holds for client employers. A breach can set off duties for both, so the client employer needs to hear about it quickly.
What makes HR and recruitment firms distinct
An HR or recruitment firm has two sets of privacy duties. It has its own, as an organization that collects personal information. It also holds employee data for client employers, who have duties of their own. A breach at the firm can trigger the firm's obligations and the client's obligations at the same time.
Recruitment data is sensitive because it covers so much: identity, work history, references, background check results, salary expectations, and for some roles, health information needed for workplace accommodation.
Which laws apply
| Jurisdiction | Applies when | Regulator |
|---|---|---|
| PIPEDA | Commercial activity in provinces without their own private-sector law (such as Ontario and Manitoba), activity that crosses a provincial or national border, and federally regulated businesses, including candidate and employee information held for client employers | OPC, priv.gc.ca |
| Alberta PIPA | Activity in Alberta, including information about the business's own employees | OIPC Alberta, oipc.ab.ca / breachnotice@oipc.ab.ca |
| BC PIPA | Activity in BC, including information about the business's own employees | OIPC BC, oipc.bc.ca |
What decides it is where the firm operates and whether its work crosses a border, not where a candidate lives. Outside Alberta and BC, the firm's own staff records are generally outside PIPEDA unless it is federally regulated.
More than one of these can apply at once, and they do not ask for the same things. ClearBreach asks one set of questions about your organization and shows which of the three reach you. Then it writes what each one requires: the regulator report, the notification letter, and the record you have to keep. Covers PIPEDA, Alberta PIPA and BC PIPA, not Quebec.
Is this right for your organization? → · See one incident assessed under all three →
What personal information HR and recruitment firms hold
| Kind of record | What it includes |
|---|---|
| Candidate files | Contact details, resume, references and reference notes, interview notes and assessments, salary expectations, background checks (criminal record, credit, education), licence verification for some roles |
| Employee files held for clients | SINs, payroll banking, T4s, pay and benefits, performance reviews, discipline, accommodation requests with supporting health information, termination records |
| Applicant tracking system | Application history, stage reached, recruiter notes, messages, reasons for rejection |
| The firm's own staff | SINs, banking, T4s, employment records |
Common breach scenarios
| What happens | Why it matters for an HR or recruitment firm | Playbook |
|---|---|---|
| An applicant tracking system is breached | Platforms such as Greenhouse, Lever, Workday and BambooHR hold large volumes of candidate data, and you stay accountable for what you keep there | Vendor or third-party breach |
| Phishing | A recruiter's mailbox holds years of resumes, offer letters and background check results | Phishing and email compromise |
| A staff member looks where they should not | Someone browses candidates from a competitor's workforce, or a departing recruiter takes the candidate database | Unauthorized employee access |
| Ransomware | Systems holding records for many client employers mean one attack reaches several employers and their staff | Ransomware attack |
RROSH in an HR and recruitment breach
RROSH stands for a real risk of significant harm, the test that decides whether a breach must be reported. Three kinds of record push an HR breach towards it.
Background checks. Criminal record and credit results can lead to discrimination and damage a reputation. When they are part of a breach, the test is likely met.
Payroll records held for clients. SINs, bank details and pay together are high risk. Tell the employees directly, and tell the client employer so it can meet its own duties.
Interview notes and rejection reasons. These can hold frank judgments about a candidate. If they reach the candidate or anyone else, the harm to reputation and dignity may meet the test.
Core compliance obligations
Privacy officer. Name one person as responsible for privacy, covering both the firm's own data and the candidate data it holds.
Privacy policy. Say what candidate and employee information you collect and why, who may receive it (background check providers, client employers), how long you keep it, and how people can see their information. Give candidates your policy before they send you their information.
Consent at application. Get the candidate's consent when you collect their information. Say what you collect, why, which client employers may receive it, and whether you will keep their resume for future roles. Keeping a resume for later is not needed for the current application, so ask for it separately rather than in one catch-all consent.
Background check consent. Get express written consent before running any check. Say what kind of check, who runs it, and what happens to the results. Keep the results only as long as needed, and share them only with the people making the hiring decision.
When to collect a SIN. Collect it only once a hire is confirmed, and only for payroll and tax reporting. Never at the application stage.
Client employer contracts. If you handle employee data for clients, each contract should set out how you handle it, confirm you act on the client's behalf, and require you to tell the client promptly about any breach of its employees' data.
Retention. Keep unsuccessful candidates' files for about one to two years after the search closes. That covers a possible human rights complaint about the hiring, without keeping them forever. Employee records held for clients follow the client employer's retention rules. See Personal Information Retention and Destruction.
Experienced a breach? Find out whether you must report it, to whom and by when, under each law that applies, with the regulator report and the individual notification letters to send. See a real verdict →
Privacy case of the month
Once a month, a five-minute read: a real case a Canadian privacy commissioner investigated, what went wrong, and what to check in your own organization so it doesn't happen to you. Written for organizations under federal, Alberta and BC privacy law. Not written for Quebec.
We send one email to confirm. Nothing else arrives until you confirm, and an unconfirmed address is deleted after 7 days. Sent by ClearBreach Technologies Inc. Mailing address and contact details · Privacy policy
Related guides
- Building a privacy program: what to do first. Now that you know what applies to you, the order to build it in
- PIPEDA Breach Reporting Requirements
- Alberta PIPA Breach Notification
- BC PIPA Breach Reporting
- Vendor or Third-Party Breach: What Canadian Organizations Must Do
- Unauthorized Employee Access: What Canadian Organizations Must Do
- Personal Information Retention and Destruction Under Canadian Privacy Law
This guide covers PIPEDA, Alberta PIPA, and BC PIPA obligations for HR and recruitment firms. Human rights legislation obligations related to hiring processes are separate and not covered here. Quebec's Law 25 is not covered here.
Frequently asked questions
Does PIPEDA apply to HR and recruitment firms?
In most provinces, yes. Recruitment firms and HR service providers collect and process personal information in the course of commercial activity. PIPEDA applies to candidate data and to employee data held on behalf of client employers. Which law applies depends on where the business operates: Alberta PIPA for activity in Alberta, BC PIPA for activity in BC, and PIPEDA elsewhere and for activity that crosses a border. Your own employees are a different matter: Alberta PIPA and BC PIPA cover employee information, but PIPEDA covers it only for federally regulated employers (s.4(1)(b)).
Can we collect a SIN from a job candidate before a job offer is made?
Generally no. A SIN is a sensitive identifier that should only be collected when legally required, primarily for payroll and tax reporting after a hire is made. Collecting SINs during the application or interview process, when there is no legal requirement to do so yet, is a collection beyond what is necessary for the purpose (PIPEDA Principle 4). The OPC advises collecting a SIN only where the law requires it, such as for payroll after a hire, and never using it as a general identifier.
We conduct background checks on candidates, what consent do we need?
Express written consent from the candidate before conducting any background check. The consent must be specific about what type of check is being run (criminal record, credit, reference verification, education verification) and who will conduct it. Candidates must understand what is being checked and must consent voluntarily, consent to a background check cannot be a condition of being considered for the role unless the check is directly relevant to the position. Using a third-party background check provider requires a contract with that provider covering their data handling obligations.
We hold employee records for our client companies, who is responsible under PIPEDA?
Both you and your client may be accountable, depending on the nature of the arrangement. If you are processing employee data on behalf of the client employer, the client employer is the accountable organization, you are a processor acting on their behalf. Your contract with the client must define the data handling obligations. However, if you make independent decisions about how the employee data is used (for example, building your own candidate database from data supplied by clients) you may be an independent accountable organization for that data. The distinction matters for breach notification: if you are breached and client employee data is affected, notify the client immediately so they can meet their own PIPEDA obligations.
This guide is educational and does not constitute legal advice. It is grounded in the text of PIPEDA, Alberta PIPA, and BC PIPA and published guidance from the OPC, OIPC Alberta, and OIPC BC. If your situation involves regulatory investigation, litigation risk, or circumstances not addressed here, engage a qualified privacy lawyer.
See where you stand
Answer four questions about a fictional property manager and see where it stands in each area the law covers.
How ClearBreach shows what you have in place →