Building a data retention policy for your business
Build a Canadian retention schedule around record types, legal requirements, business needs and secure disposal, including cloud copies and backups.

Keeping every file indefinitely makes it hard to know which record matters and who still has access to it. Deleting everything after one fixed period can remove records the business must retain. A retention schedule gives each kind of record a reason, a period and an owner.
Build it with the people responsible for finance, staff, clients and IT. Have your accountant and legal or privacy adviser confirm the requirements before you turn on automatic deletion.
Set periods by record type
The Privacy Commissioner’s retention guidance explains that personal information should be disposed of when its purpose is fulfilled, subject to legal retention requirements. Information used to make a decision about someone may need to be kept so they can access and challenge that decision. There’s no single period for all records.
For tax records, the Canada Revenue Agency’s guidance gives a general period of six years from the end of the last tax year to which the records relate. It’s not six years from the file’s creation date. Your accountant should check exceptions and situations requiring longer retention, including long-term transactions and disputes.
Patient records, employment records and contract files need their own review. Don’t borrow a rule from another country, or stretch the general tax period, to cover them all. Record the specific requirement and its source for each category.
Make the schedule usable
For each category, write down the purpose, where the official copy lives, the event that starts the period, the period itself, the owner and how the record is disposed of. Note what can suspend deletion.
This is a starting structure, with periods to be confirmed for your business:
| Record | What to confirm |
|---|---|
| Tax records | Finance and your accountant confirm the period from the end of the last relevant tax year. |
| Client files | The business owner and legal adviser confirm the event that starts the period, such as contract expiry. |
| Staff records | HR and the legal adviser confirm the period and starting event for each record type. |
| Meeting notes | The record owner and privacy lead confirm when the purpose is complete and what must be kept. |
| Security logs | IT and the response lead confirm the period and starting event needed for investigations. |
Avoid a rule based only on when someone last opened a file. That date may have little connection to a tax year, a contract or the reason it was kept.
Include copies and backups
Check email attachments, laptop downloads, shared folders, exported reports and supplier systems. A deletion rule on the main folder won’t remove all those copies.
Document backup expiry, access restrictions and what happens when an older backup is restored. Ask IT how it will reapply deletion rules after a restore so expired records don’t return to ordinary use. If the system can’t delete individual backup records, have the privacy adviser review that limitation and the planned expiry process before promising a deletion date.
An archive is a storage arrangement. It still needs access controls, a retention period and an eventual disposal method.
Pause deletion when records must be preserved
Give staff a contact for litigation, investigations, audits and access requests. Have your legal adviser decide what must be preserved and tell IT which automated rules to suspend. Record who can release the hold.
Don’t delete incident evidence or disputed records as part of a routine cleanup. A retention policy needs a way to handle those exceptions.
Test disposal before automating it
Start with sample records and a small category. Check that the selection is correct, the sign-off is recorded and the removal affects the intended copies. Use a secure disposal method that fits each format: paper, devices and cloud records. Restrict any disposal log that itself contains personal information.
Keep the final schedule with the system settings. Review it when requirements, suppliers or business processes change, and check periodically that the rules are being applied.


