How to adapt from PIPEDA to Law25: Compliance in Canada

Sep 20, 2023
Share this post
Sharing to FacebookSharing to LinkedInSharing to XSharing to Email

Canada's federal Personal Information Protection and Electronic Documents Act (PIPEDA) has been a benchmark for businesses in managing personal information. However, for organizations operating in Quebec, the introduction of Law25 (originally Bill 64) has changed the game. Although there's a foundation of compliance in most companies through PIPEDA, Law25 introduces more rigorous standards. Here's a roadmap for those who were already compliant with PIPEDA and are navigating the transition to Law25 compliance:

Revisit Consent Mechanisms

Both PIPEDA and Law25 emphasize informed consent. However, Law25 mandates more explicit and clear consent procedures. You must ensure that users are informed not just about data collection but also about the specific purpose for which their data will be used. There is, however, also a new exception to the consent requirement. Businesses can now transfer personal information to another person if this is necessary for a business transaction, i.e., if the recipient requires the information to perform a contractual obligation for the transferring entity. The exact requirement for the consent exception to apply are set out in section 18.3 of Law25. In PIPEDA, there was a proposed business transaction exception, which allowed the transfer of personal information if that was required in order to determine whether to proceed with the transaction or not. This clause allowed for the parties to exchange personal information for example when contemplating an acquisition by one of the other parties.

Automated Decision-Making and Profiling

Specific information obligations apply under Law25 when the business wants to render automated decisions, that is, decisions without any human oversight, on the basis of personal information collected by technological means. Furthermore, the business must inform individuals of technology used to profile, identify, or locate individuals by means of technology that allows for such functionality. In addition, by default, these functionalities must be turned off.

Privacy Impact Assessments (PIAs)

Law25 makes Privacy Impact Assessments mandatory for specific projects. A fundamental step in each PIA is understanding the data the business has. Private AI can help with that step, which can otherwise be difficult, particularly if the business deals with vast amounts of unstructured data. Leveraging its hyper accurate machine learning tool that can identify over 50 entities, classifying personal information in free text, images, audio, video and other unstructured data is simplified to three lines of code. Request an API key.

PIAs under Law25 are now mandatory for cross-border data transfers. These assessments must also assess the foreign jurisdiction to establish whether it provides adequate protection for the personal information transferred there. In addition, businesses must “conduct an assessment of the privacy-related factors of any project of acquisition, development and redesign of an information system or electronic service delivery involving the collection, use, communication, keeping or destruction of personal information." Businesses need to integrate this practice into their data processing activities. 

Right to Portability, to be Forgotten, and to Know the Source of Personal Information

A significant addition in Law25 is the right to data portability and the right to be forgotten. Organizations will need mechanisms to provide users with their data in a structured, standard format and to delete personal data upon request, going beyond PIPEDA's access and correction rights. The good news is that this requirement is not going to come into force until September 2024. However, whether the regulator will be able to provide guidance by that time remains to be seen, hence compliance might pose challenges. The right to be forgotten in Law25 means the de-indexing of one’s name from a hyperlink attached to it. Another new right under Law25 is the right to request the source of one’s personal information that a business holds on the requestor. This would give the individual enhanced insights in instances where the business collects information from someone other than the individual themselves, which, by the way, is only permitted with consent or under otherwise limited circumstances. 

Enhanced Data Breach Reporting

Although PIPEDA introduced mandatory breach reporting in 2018, Law25 has stricter requirements. The criteria for when a breach must be reported, and the associated penalties are more rigorous under Law25. For example, under Law25 the unauthorized use of personal information is now also considered a privacy incident, which was not the case under PIPEDA.

Appoint a Data Protection OfficerWhile PIPEDA already requires the designation of a person accountable for the business’s compliance with data privacy laws, Law25 assigns this role now by default to the person with the highest authority with the possibility to delegate this role or some of the responsibilities, in writing, to someone else.Privacy by DefaultLaw25 now requires that any privacy settings of “technological products” offered to the public have their privacy settings by default set to the highest standard. Explicitly exempted are only cookies. What the regulator had in mind with “technological products” is somewhat unclear, however. No guideline has come out yet that would clarify whether this covers any online services, or has a more limited scope.AnonymizationIn contrast to PIPEDA, which permitted the anonymization of data as an equal alternative to data disposition, under Law25, anonymization is first of all properly defined, but secondly only permitted when there is a “serious and legitimate” reason to do so. Guidelines are again still outstanding to provide more clarity on the exact requirements.Law25 has this to say about anonymization:

  • For the purposes of this Act, information concerning a natural person is anonymized if it is, at all times, reasonably foreseeable in the circumstances that it irreversibly no longer allows the person to be identified directly or indirectly.
  • Information anonymized under this Act must be anonymized according to generally accepted best practices and according to the criteria and terms determined by regulation.

Consequently, if a business has so far as a default anonymized information rather than disposed of it when the purpose for which the information had been collected has been achieved needs to revisit this decision and scrutinize whether this practice is still justified.When it comes to the requirement of “best practices,” we’d like to point you to Private AI’s state of the art, AI-driven personal information redaction solution that detects more than 50 different entity types of personal data across 50 languages. The models achieve 99+% accuracy, with structured, semi-structured, as well as unstructured data. You can try our web demo here.PenaltiesThe biggest for last: Law25 dramatically enhances the enforcement powers of the privacy commissioner. The new law provides for administrative penalties for less severe violations, and penalties for more severe ones. The maximum penalty is $25 million or, if greater, 4% of the annual turnover of the business found to be in violation. There is also a private right of action, allowing individuals to sue directly for a violation of their rights under Law25.ConclusionTransitioning from PIPEDA to Law25 compliance isn't about reinventing the wheel but refining and recalibrating your data protection measures. With a more rigorous framework, Law25 aims to provide stronger protections for individuals' personal data. For organizations, while this may require an initial investment in terms of time and resources, the end goal is a more trustful relationship with customers and stakeholders, and a robust position in a privacy-conscious world.

Get started with PrivateGPT today:

Try it free today

Data Left Behind: AI Scribes’ Promises in Healthcare

Why is linguistics essential when dealing with healthcare data?

Why Health Data Strategies Fail Before They Start

Private AI to Redefine Enterprise Data Privacy and Compliance with NVIDIA

EDPB’s Pseudonymization Guideline and the Challenge of Unstructured Data

HHS’ proposed HIPAA Amendment to Strengthen Cybersecurity in Healthcare and how Private AI can Support Compliance

Japan's Health Data Anonymization Act: Enabling Large-Scale Health Research

What the International AI Safety Report 2025 has to say about Privacy Risks from General Purpose AI

Private AI 4.0: Your Data’s Potential, Protected and Unlocked

How Private AI Facilitates GDPR Compliance for AI Models: Insights from the EDPB's Latest Opinion

Navigating the New Frontier of Data Privacy: Protecting Confidential Company Information in the Age of AI

Belgium’s Data Protection Authority on the Interplay of the EU AI Act and the GDPR

Enhancing Compliance with US Privacy Regulations for the Insurance Industry Using Private AI

Navigating Compliance with Quebec’s Act Respecting Health and Social Services Information Through Private AI’s De-identification Technology

Unlocking New Levels of Accuracy in Privacy-Preserving AI with Co-Reference Resolution

Strengthened Data Protection Enforcement on the Horizon in Japan

How Private AI Can Help to Comply with Thailand's PDPA

How Private AI Can Help Financial Institutions Comply with OSFI Guidelines

The American Privacy Rights Act – The Next Generation of Privacy Laws

How Private AI Can Help with Compliance under China’s Personal Information Protection Law (PIPL)

PII Redaction for Reviews Data: Ensuring Privacy Compliance when Using Review APIs

Independent Review Certifies Private AI’s PII Identification Model as Secure and Reliable

To Use or Not to Use AI: A Delicate Balance Between Productivity and Privacy

To Use or Not to Use AI: A Delicate Balance Between Productivity and Privacy

News from NIST: Dioptra, AI Risk Management Framework (AI RMF) Generative AI Profile, and How PII Identification and Redaction can Support Suggested Best Practices

Handling Personal Information by Financial Institutions in Japan – The Strict Requirements of the FSA Guidelines

日本における金融機関の個人情報の取り扱い - 金融庁ガイドラインの要件

Leveraging Private AI to Meet the EDPB’s AI Audit Checklist for GDPR-Compliant AI Systems

Who is Responsible for Protecting PII?

How Private AI can help the Public Sector to Comply with the Strengthening Cyber Security and Building Trust in the Public Sector Act, 2024

A Comparison of the Approaches to Generative AI in Japan and China

Updated OECD AI Principles to keep up with novel and increased risks from general purpose and generative AI

Is Consent Required for Processing Personal Data via LLMs?

The evolving landscape of data privacy legislation in healthcare in Germany

The CIO’s and CISO’s Guide for Proactive Reporting and DLP with Private AI and Elastic

The Evolving Landscape of Health Data Protection Laws in the United States

Comparing Privacy and Safety Concerns Around Llama 2, GPT4, and Gemini

How to Safely Redact PII from Segment Events using Destination Insert Functions and Private AI API

WHO’s AI Ethics and Governance Guidance for Large Multi-Modal Models operating in the Health Sector – Data Protection Considerations

How to Protect Confidential Corporate Information in the ChatGPT Era

Unlocking the Power of Retrieval Augmented Generation with Added Privacy: A Comprehensive Guide

Leveraging ChatGPT and other AI Tools for Legal Services

Leveraging ChatGPT and other AI tools for HR

Leveraging ChatGPT in the Banking Industry

Law 25 and Data Transfers Outside of Quebec

The Colorado and Connecticut Data Privacy Acts

Unlocking Compliance with the Japanese Data Privacy Act (APPI) using Private AI

Tokenization and Its Benefits for Data Protection

Private AI Launches Cloud API to Streamline Data Privacy

Processing of Special Categories of Data in Germany

End-to-end Privacy Management

Privacy Breach Reporting Requirements under Law25

Migrating Your Privacy Workflows from Amazon Comprehend to Private AI

A Comparison of the Approaches to Generative AI in the US and EU

Benefits of AI in Healthcare and Data Sources (Part 1)

Privacy Attacks against Data and AI Models (Part 3)

Risks of Noncompliance and Challenges around Privacy-Preserving Techniques (Part 2)

Enhancing Data Lake Security: A Guide to PII Scanning in S3 buckets

The Costs of a Data Breach in the Healthcare Sector and its Privacy Compliance Implications

Navigating GDPR Compliance in the Life Cycle of LLM-Based Solutions

What’s New in Version 3.8

How to Protect Your Business from Data Leaks: Lessons from Toyota and the Department of Home Affairs

New York's Acceptable Use of AI Policy: A Focus on Privacy Obligations

Safeguarding Personal Data in Sentiment Analysis: A Guide to PII Anonymization

Changes to South Korea’s Personal Information Protection Act to Take Effect on March 15, 2024

Australia’s Plan to Regulate High-Risk AI

How Private AI can help comply with the EU AI Act

Comment la Loi 25 Impacte l'Utilisation de ChatGPT et de l'IA en Général

Endgültiger Entwurf des Gesetzes über Künstliche Intelligenz – Datenschutzpflichten der KI-Modelle mit Allgemeinem Verwendungszweck

How Law25 Impacts the Use of ChatGPT and AI in General

Is Salesforce Law25 Compliant?

Creating De-Identified Embeddings

Exciting Updates in 3.7

EU AI Act Final Draft – Obligations of General-Purpose AI Systems relating to Data Privacy

FTC Privacy Enforcement Actions Against AI Companies

The CCPA, CPRA, and California's Evolving Data Protection Landscape

HIPAA Compliance – Expert Determination Aided by Private AI

Private AI Software As a Service Agreement

EU's Review of Canada's Data Protection Adequacy: Implications for Ongoing Privacy Reform

Acceptable Use Policy

ISO/IEC 42001: A New Standard for Ethical and Responsible AI Management

Reviewing OpenAI's 31st Jan 2024 Privacy and Business Terms Updates

Comparing OpenAI vs. Azure OpenAI Services

Quebec’s Draft Regulation Respecting the Anonymization of Personal Information

Version 3.6 Release: Enhanced Streaming, Auto Model Selection, and More in Our Data Privacy Platform

Brazil's LGPD: Anonymization, Pseudonymization, and Access Requests

LGPD do Brasil: Anonimização, Pseudonimização e Solicitações de Acesso à Informação

Canada’s Principles for Responsible, Trustworthy and Privacy-Protective Generative AI Technologies and How to Comply Using Private AI

Private AI Named One of The Most Innovative RegTech Companies by RegTech100

Data Integrity, Data Security, and the New NIST Cybersecurity Framework

Safeguarding Privacy with Commercial LLMs

Cybersecurity in the Public Sector: Protecting Vital Services

Privacy Impact Assessment (PIA) Requirements under Law25

Elevate Your Experience with Version 3.5

Fine-Tuning LLMs with a Focus on Privacy

GDPR in Germany: Challenges of German Data Privacy (Part 2)

Comply with US Executive Order on Safe, Secure, and Trustworthy Artificial Intelligence using Private AI

How to Comply with EU AI Act using PrivateGPT

Navigating the Privacy Paradox: A Guide to Ethical Fine-Tuning of Large Language Models

Adding Privacy to LangChain with Private AI