Colour theme
Book a consultation

Keeping privacy requirements current

Watch the right Canadian privacy sources, check what a change means for your business, then update forms, systems and training with proof it's done.

An illustration of a blue padlock within layered digital circles.

Privacy requirements can change when the law changes, but also when your business changes what it does with personal information. A new service, customer group or supplier can raise questions that an annual policy review misses.

Keep a record of applicable requirements and a process for assessing changes before they affect everyday work.

Establish the starting point

The Office of the Privacy Commissioner’s Canadian privacy-law overview explains that different federal, provincial and sector laws may apply. Scope depends on the organization, activity and information involved.

Have your privacy officer, or a lawyer when the answer isn’t clear, confirm which laws apply. If you serve customers outside Canada, ask about their laws too. Europe’s GDPR, for example, can apply to a Canadian business that offers goods or services to people in the EU. The European Data Protection Board’s territorial-scope guidance explains the relevant scope tests for that law.

Keep contract terms and industry standards, such as PCI DSS for card payments, on a separate list from the laws. They change on different schedules and come from different sources.

Assign monitoring and an alternate

List the official sources to watch: the OPC, your provincial privacy commissioner and any regulator for your sector. Sign up for their news updates, and have them sent to one person who reviews them and a second who covers when they’re away.

Record the source, date and issue. Avoid changing policy based only on a vendor summary or an alarming headline.

A bill, new guidance from a regulator and a law in force are different things. Check which one you’re reading and when it takes effect.

Review operational changes too

Include privacy review when adopting a new application, changing a supplier, collecting new fields or enabling analytics.

Ask what information is collected, why it’s needed, who can see it, how long it’s kept and where it’s sent. Check whether earlier notices and agreements still describe the work.

Use the Canadian privacy basics guide for the wider inventory and accountability questions.

Translate a requirement into work

With your adviser, list the forms, contracts, systems, procedures and training the change affects. Give each change an owner and a due date.

Specify the evidence of implementation, such as a tested access restriction or a verified deletion workflow. Rewriting the policy doesn’t change how the system behaves, so test that too.

Use the OPC accountability guidance for what a privacy management program should include.

Update staff instructions

Explain the action staff need to take in the work they do. Provide a contact for uncertain requests and incidents.

Log who was trained, when and on what. Keep the personal details in those records to what you need.

Verify and maintain the result

Test the changed workflow and confirm that public wording, internal instructions and supplier arrangements agree. Record unresolved issues for the responsible decision-maker.

Review after significant business or system changes as well as on the regular schedule. When the legal scope is unclear, ask a privacy lawyer. Buying an IT product doesn’t make the business compliant.


Featured Image Credit