← Guides·Privacy law by industry →
Your SituationWe want our privacy basics in place →
Privacy Law for Financial Advisors in Canada
By Yong DuPublished Reviewed
Which privacy law covers your practice, how to protect KYC and account records, and when a breach of client financial data must be reported.
A financial advisor's practice is covered by Alberta PIPA in Alberta, BC PIPA in BC, and PIPEDA elsewhere. KYC files combine SINs, income, net worth and ID, so almost any breach of them must be reported. Advisors at an investment dealer have a second, tighter deadline: the dealer must report to CIRO within three days.
What makes financial advisors distinct
An advisor's client file is the fullest picture of someone's finances that any small business holds. It covers income, net worth, asset mix, goals, risk tolerance, balances, transactions and beneficiaries. It also holds the government ID collected for know-your-client (KYC) checks.
Advisors also answer to securities regulators: CIRO (the Canadian Investment Regulatory Organization, formerly IIROC and the MFDA), the provincial securities commissions, and for insurance products, provincial insurance regulators. Their record-keeping and client data rules run alongside PIPEDA.
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 | 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 practice operates and whether its work crosses a border, not where a client lives. Outside Alberta and BC, staff records are generally outside PIPEDA unless the business is federally regulated.
Investment dealers have a three-day reporting rule with CIRO. Under CIRO's cybersecurity incident reporting rule (section 3703 of the investment dealer rules, introduced by IIROC in 2019), a dealer must report a cybersecurity incident to CIRO in writing within three calendar days of discovering it. It must file an investigation report within 30 days.
An incident counts if unauthorized access to the dealer's systems or information has caused, or is reasonably likely to cause, any of these: substantial harm to any person, a material impact on the dealer's operations, or a duty to notify a government body or regulator under applicable law.
So a breach the dealer must report to a privacy commissioner is also reportable to CIRO, and CIRO's three days is the tighter deadline. CIRO's guidance says so directly: the definition includes breaches of personal information reportable under PIPEDA. An incident at a third-party service provider can count too, if it affects the dealer's systems or information.
The three-day report can be preliminary. It goes to the dealer's Financial and Operations Compliance relationship manager at CIRO, who CIRO says can also be called when it is unclear whether an incident qualifies. If you are an advisor at a dealer, this is your dealer's report to make: tell its compliance team at once. Mutual fund dealers should confirm with CIRO whether the same rule now applies to them. The provincial securities commissions set record-keeping rules but publish no separate breach-reporting duty for advisors.
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 practice and shows which of the three reach you. Then it writes what each one requires: the regulator report, the client notification letter, and the record you have to keep. Covers PIPEDA, Alberta PIPA and BC PIPA, not Quebec.
Is this right for your practice? → · See one incident assessed under all three →
What personal information financial advisors hold
| Kind of record | What it includes |
|---|---|
| KYC files | Name, date of birth, SIN, address, employment and income, net worth and liquidity, goals, risk tolerance, time horizon, beneficiaries, government ID |
| Account records | Statements, trade confirmations, holdings, transaction history, fee disclosures, account agreements |
| Planning documents | Retirement projections, estate notes, insurance needs analyses, tax summaries |
| Correspondence | Client emails, meeting notes, suitability assessments, recommendations and the reasons for them |
| Staff | SINs, banking, licensing records, commission records |
Common breach scenarios
| What happens | Why it matters for an advisor | Playbook |
|---|---|---|
| Phishing and email compromise | An advisor's mailbox holds years of statements and planning documents. Attackers may also use it to send fake instructions for wire transfers out of client accounts | Phishing and email compromise |
| Ransomware | Files with KYC information and account details are valuable to attackers | Ransomware attack |
| A CRM or portfolio platform is breached | Cloud systems advisors use are run by vendors, and you stay accountable for client data held there | Vendor or third-party breach |
| A staff member looks where they should not | Someone opens client files outside their own book of business | Unauthorized employee access |
RROSH in a financial advisor breach
RROSH stands for a real risk of significant harm, the test that decides whether a breach must be reported. KYC files hold SINs, net worth, income and government ID: the mix most linked to financial fraud and identity theft. So the test is met in almost every breach of KYC files or account records. Exposed statements also open clients to targeted investment fraud.
Beneficiaries are affected too. KYC files often name beneficiaries, with their relationship and contact details. They are not your clients, but their information is protected, and they may be people affected by a breach.
Core compliance obligations
Privacy officer. Name one person as responsible for privacy. A dealer usually has one; check whether individual advisors have their own duties for their own client records.
Privacy policy. Say what KYC and account information you collect and why, who you share it with (the dealer, custodians, regulators, referral partners), how you protect it, and how clients can see their information.
Consent. Get the client's consent at account opening. Consent to KYC collection can be a condition of opening the account, because the law requires that information. Using it for anything else, such as marketing or cross-selling, needs separate consent. Put clear privacy wording in the account opening documents.
Retention. CIRO and securities rules set minimum periods for KYC and account records, typically seven years. Those minimums govern: PIPEDA's general retention principle does not override a longer securities-law minimum. After the minimum, destroy the records securely.
Vendor contracts. Each platform that handles client data, such as a CRM, portfolio system or planning software, should have a written contract with privacy and security terms.
Safeguards. Encrypt KYC files and account records. Turn on multi-factor sign-in for every platform with client data. Let only the advisors and staff who serve a client see their file, and keep access logs.
Telling clients after a breach. Suggest a fraud alert with Equifax (1-800-465-7166) and TransUnion Canada (1-877-525-3823). Ask them to watch their investment accounts for activity they do not recognize, and to call your dealer's client services if they see any.
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 client 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
- Phishing and Business Email Compromise
- Vendor or Third-Party Breach: What Canadian Organizations Must Do
- Responding to Individual Access Requests Under Canadian Privacy Law
This guide covers PIPEDA, Alberta PIPA, and BC PIPA obligations for financial advisors and investment dealers. CIRO, ASC, and BCSC obligations under securities legislation are separate and not fully covered here. Quebec's Law 25 is not covered here.
Frequently asked questions
Does PIPEDA apply to financial advisors?
In most provinces, yes. Financial advisors collect and use personal information in the course of commercial activity. 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. Financial advisors are also regulated under securities legislation (CIRO, and provincial securities commissions) which has its own KYC and record-keeping requirements, those run alongside privacy law.
KYC regulations require us to collect extensive client information, does collecting it for KYC purposes satisfy PIPEDA consent requirements?
You still obtain consent, but because the law requires the KYC information, you can make that consent a condition of opening the account: PIPEDA only prevents requiring consent beyond what the stated, legitimate purposes need (clause 4.3.3). Any use of KYC information beyond those purposes, such as cross-selling or sharing it with affiliated advisors, needs its own consent. The KYC requirement justifies collecting the information; it is not open-ended permission to use it.
A client's investment account statements and KYC file were accessed in a breach, what are our obligations?
Conduct a RROSH assessment immediately. A financial advisory client file typically contains: SIN, date of birth, employment and income information, net worth and asset declarations, investment objectives and risk profile, account statements, and government-issued ID. This combination is high-risk for financial fraud and identity theft. RROSH is almost certainly present. Where PIPEDA applies, report to the OPC and notify the affected client. In Alberta, report to the OIPC Alberta and notify the client with the report. In BC there is no legal duty, but the BC Commissioner expects clients to be told where there is a risk of harm. If you work through an investment dealer, the dealer may also have to report to CIRO within three days of discovery, so tell its compliance team immediately.
Our dealer's back-office system was breached, are we responsible for client notification?
The dealer organization is the accountable party for client data held in its systems. If you are an advisor employed by or contracted to a dealer, the dealer's privacy obligations cover client data held in the dealer's systems. However, if you hold your own client records separately (in a CRM, locally stored files, or personal email) you are accountable for that data independently. Confirm with your dealer's compliance team who is responsible for notification and ensure clients are not left without notification by both parties assuming the other has handled it.
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 →