← Guides·All compliance guides →
Your SituationWe want our privacy basics in place →
Personal Information Retention and Destruction Under Canadian Privacy Law
By Yong DuPublished Reviewed
No Canadian law sets one retention period. Keep personal information only while its purpose needs it, then destroy it securely. How to set a schedule.
On this page
Keep personal information only as long as you need it for the purpose you collected it, then destroy it securely. Some laws set a minimum first: six years for tax records, and in BC at least a year for information used to decide something about a person. A written retention schedule is how you show you do both.
The retention principle, what it requires
PIPEDA Principle 5 says to keep personal information only as long as needed for the purposes it was collected for. Alberta PIPA s.35(2) and BC PIPA s.35(2) impose the same duty to destroy.
The two provinces part company one subsection earlier, and they point opposite ways. Alberta's s.35(1) is a limit: keep personal information only as long as is reasonably required. BC's s.35(1) is a floor, and it opens with the words "despite subsection (2)":
if an organization uses an individual's personal information to make a decision that directly affects the individual, the organization must retain that information for at least one year after using it
Same section number, opposite instruction. In BC, destroying a record promptly because its purpose is finished can breach the Act, if the record was used to decide something about a person. The year runs from when you used it. It gives the person a chance to ask what the decision was based on.
This principle creates two distinct obligations:
Minimum retention. Keep information used to decide something about a person long enough for them to ask to see it, and long enough to meet any legal minimum. In BC that minimum is one year, under s.35(1). PIPEDA names no fixed period: clause 4.5.2 says such information must be "retained long enough to allow the individual access to the information after the decision has been made". Alberta sets no minimum of its own.
Maximum retention. Destroy personal information once you no longer need it for the purpose you collected it for, and never later than any maximum set by another law.
These are separate duties, and meeting one does not meet the other. Destroying records before a legal minimum breaks the minimum. Holding them forever after the purpose is served breaks the maximum. A working retention program handles both.
Step 1, Map what personal information you hold and why
Before you can write a retention schedule, you need to know what personal information you hold, where it is, and why you collected it. Everything else builds on this list.
For each category of personal information, document:
- What it is (customer names and contact information, employee payroll records, client financial files, etc.)
- Where it is stored (CRM, accounting system, email, physical files, cloud storage)
- Why it was collected (to deliver the service, to process payroll, to comply with a legal obligation)
- Any legal minimum retention period that applies to it
- Who is responsible for managing it
If you cannot answer these for something you hold, that is a gap to close, not a reason to put the exercise off.
Printable version: Retention schedule template →
This list is the slow part, and everything after it depends on it. ClearBreach asks one set of questions about your organization, then writes your personal information inventory: what you hold, where it lives, why you have it and how long you keep it. Covers PIPEDA, Alberta PIPA and BC PIPA, not Quebec.
Is this right for your organization? → · See a complete assessment →
Step 2, Apply the retention framework
For each category of personal information, your retention period is determined by the longer of:
- The legal minimum: the minimum required by any applicable law (tax, employment, limitation period, sector-specific regulation)
- The operational necessity period: the time the information is actively needed for its original purpose
Once both of those periods have expired, destruction is required.
Legal minimums that commonly apply to Canadian small businesses
| Record type | Minimum retention | Legal basis |
|---|---|---|
| Tax records (income, GST/HST, payroll) | 6 years from end of tax year | Income Tax Act s.230; Excise Tax Act s.286 |
| Employment records (general) | Alberta: 3 years from when each record is made. BC: 4 years from when each payroll record is created | Employment Standards Code (AB) s.15; Employment Standards Act (BC) s.28 |
| Payroll records | 6 years | Income Tax Act |
| Breach of security safeguards records (PIPEDA) | 24 months after the day you determine the breach occurred | PIPEDA s.10.3; Breach of Security Safeguards Regulations s.6 |
| Personal information used to make a decision about an individual | Long enough to allow the individual to access it after the decision | PIPEDA Principle 5 guidance |
| Limitation period for contract/tort claims | 2 years (Alberta, BC, from discovery) | Limitations Act (AB); Limitation Act (BC) |
| Health records (health professionals) | 10 years minimum (common practice); varies by province and sector | Provincial health legislation |
| Corporate and shareholder records | Generally for the life of the corporation; check your incorporating Act | Business Corporations Act (federal or provincial) |
Alberta employment records: the Employment Standards Code requires employment records to be kept for at least 3 years from the date each record is made (s.15).
BC employment records: the Employment Standards Act requires payroll records to be kept for 4 years after the date each record is created (s.28).
Step 3, Document your retention schedule
A retention schedule is a written list of each kind of personal information, how long you keep it, and what event starts the clock to destroy it. It does not need to be complex. It needs to be followed.
Minimum schedule structure:
| Category | Retention period | Trigger for destruction | Storage location | Owner |
|---|---|---|---|---|
| Customer contact information | Duration of relationship + 2 years | 2 years after last transaction | CRM | [Name/role] |
| Employee payroll records | 6 years from end of tax year | End of 6th calendar year | Accounting system | [Name/role] |
| Job application records (unsuccessful) | 1 year from application date | 1 year after rejection | HR folder | [Name/role] |
| Breach records | 24 months (PIPEDA) | 24 months after the day you determine the breach occurred | Compliance folder | [Name/role] |
If you operate in BC, add a column for it. Any row where the information was used to decide something about a person carries the s.35(1) floor, and the floor beats the row's own trigger. The unsuccessful job application above is the clearest case. The rejection is a decision that directly affects the applicant, so a BC employer keeps it for at least a year from the decision. Hiring, refusing credit, setting a price and ending a service all work the same way.
Review the schedule every year. Update it when you start holding a new kind of information, when a legal minimum changes, or when a business process changes.
Step 4, Implement a destruction process
A schedule only works if the destruction actually happens. Name the person who carries it out, and keep a record each time.
Digital records
What counts as secure destruction:
- Sanitization following a recognized standard such as NIST SP 800-88. Overwriting works for traditional hard drives; for SSDs and phones, use the device's built-in secure erase or cryptographic erase, because overwriting does not reliably reach every block
- Physical destruction of storage media (hard drives, SSDs, USB drives), shredding, degaussing, or incineration
- Verified destruction by a certified data destruction service with documentation
What does not count:
- Moving files to Trash and emptying it, data remains on disk and is recoverable
- Deleting a record from a database without purging backup copies that contain the same record
- Deactivating an account without purging the underlying personal data
Cloud and SaaS platforms. When you close an account with a cloud vendor, get written confirmation of whether and when it deletes your data. Many keep it for 30 to 90 days after you leave. Your retention duty covers data a vendor holds for you.
Paper records
What counts as secure destruction:
- Cross-cut shredding (confetti-sized fragments)
- Micro-cut shredding
- Incineration
- Certified third-party document destruction with a certificate of destruction
What does not count:
- Strip-cut shredding, strips can be reassembled; not adequate for sensitive personal information
- Recycling unshredded documents
- Placing documents in general trash
Certificates of destruction
If an outside service destroys records for you, get a certificate each time. It should name the vendor, the date, what was destroyed and how. Keep the certificates with your compliance records.
Step 5, Handle legal holds
A legal hold pauses your retention schedule for records relevant to a lawsuit, a regulatory investigation or another legal proceeding, under way or reasonably expected. While it applies, keep those records even if the schedule says to destroy them.
Legal holds are typically initiated by legal counsel. Once counsel notifies you that a hold applies, preserve the identified records until counsel confirms the hold is lifted.
Do not destroy records once you have reason to expect a lawsuit, or after a legal demand arrives. Destroying them then can count as destroying evidence, which is a far bigger legal risk than the privacy issue.
Special cases
Anonymization instead of destruction. If information is still useful for analysis but you no longer need to know who it is about, you can anonymize it instead. That means removing every direct and indirect identifier, so the person cannot reasonably be identified again. Anonymized information is no longer personal information under PIPEDA or the provincial PIPAs, so the retention duties stop. True anonymization is hard. Replacing names with codes while keeping a key is pseudonymization, not anonymization, and the duties still apply.
Archiving. Archiving is not destroying. Archived records are still personal information, with the same retention and access duties. Archiving is a storage decision, not a compliance one. Information archived past its retention period is being kept in breach of PIPEDA.
Where the data is stored. This guide is about how long to keep personal information, not where. PIPEDA does not require it to be stored in Canada: if a provider abroad holds it, you stay accountable and need a contract that gives comparable protection. Alberta PIPA requires your policies to say when a service provider outside Canada is used. Bill C-36 would add a privacy impact assessment before the transfer; see cross-border transfers under Bill C-36.
Information collected for more than one purpose. If one purpose has ended and another continues, you can keep the information for the one that continues, but no longer. Write down the remaining purpose and the new destruction date.
Common mistakes
No retention schedule at all. A common gap in small business privacy programs: in the OPC's 2025–26 survey, a quarter of businesses with a privacy policy did not say in it how long they keep information. Without a schedule, personal information accumulates indefinitely by default. The OPC expects to see a documented retention policy as part of a functioning privacy program.
Keeping information "just in case." A possible future need is not a purpose under PIPEDA. If you cannot name a specific, current use for information you hold, you probably should not hold it.
Deleting records but not backups. A record deleted from a live database often survives in backups. If you keep backups longer than the retention period for that information, the backups are keeping it too long. Match backup retention to your schedule, or have a way to purge records from backups when needed.
No certificates of destruction. If a destruction service mishandles records, you need to show you took care: that you used a reputable service and got confirmation. The certificates are that proof.
Not reviewing the schedule after a system change. A new CRM, payroll provider or cloud tool can put data somewhere your schedule does not cover. Review the schedule whenever your systems change.
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
- PIPEDA Compliance Requirements for Canadian Organizations
- PIPEDA Compliance Checklist, Principle 5 covers retention
- Alberta PIPA Compliance Requirements
- BC PIPA Compliance Requirements
- Physical Records Breach: What Canadian Organizations Must Do, what happens when physical records are improperly destroyed or go missing
This guide covers retention and destruction obligations under PIPEDA, Alberta PIPA, and BC PIPA for private-sector organizations. Sector-specific legislation, the Health Information Act (AB), PHIPA (ON), the Income Tax Act, Employment Standards legislation, may impose additional minimum retention requirements. Quebec's Act respecting the protection of personal information in the private sector (Law 25) is not covered here.
Frequently asked questions
How long do I have to keep personal information under Canadian privacy law?
There is no single universal retention period. PIPEDA Principle 5 requires that personal information be kept only as long as necessary for the purpose for which it was collected. Other laws (the Income Tax Act, employment standards legislation, limitation periods) impose their own minimum retention periods that override PIPEDA's 'no longer than necessary' principle when they apply. You must hold personal information at least as long as any applicable legal minimum, and no longer than is necessary for your stated purpose, unless a legal hold or other obligation requires extended retention.
What does 'necessary for the purpose' mean in practice?
It means the personal information is still actively needed to deliver the service it was collected for, to fulfill a legal obligation, or to allow an individual to exercise their right of access to a decision made about them. Once a customer relationship ends, an employment relationship terminates, or a transaction is complete, the personal information collected for that purpose no longer has an active use, and the retention clock starts running toward destruction. 'We might need it someday' is not a purpose under PIPEDA.
Can I keep personal information indefinitely just in case?
No. Indefinite retention of personal information that is no longer needed for its original purpose is a PIPEDA violation. The OPC has found against organizations that retained personal information for years beyond the end of the relationship with no documented purpose. You must have a documented retention schedule and apply it consistently. If you identify a new legitimate purpose for information originally collected for a different purpose, the new purpose must be documented and consent re-obtained if required.
Does PIPEDA require me to keep customer data in Canada?
No. PIPEDA does not require personal information to be stored in Canada. If a service provider in another country holds it, you remain accountable for it and must use contractual means to give it comparable protection. Alberta PIPA adds that your policies must say when you use a service provider outside Canada. If Bill C-36 passes, a privacy impact assessment would be required before the transfer.
What does secure destruction mean?
Secure destruction means making personal information permanently unrecoverable. For digital records, this means sanitization to a recognized standard such as NIST SP 800-88 (overwriting for hard drives, built-in secure erase for SSDs), or physical destruction of the storage media, not just moving files to the Recycle Bin. For paper records, this means cross-cut or micro-cut shredding or incineration, not strip-cut shredding, which can be reassembled, and not regular recycling. If you use a third-party destruction service, obtain a certificate of destruction. Standard file deletion is never enough for digital media.
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 →