Is Salesforce Law25 Compliant?

Feb 15, 2024
Share this post
Sharing to FacebookSharing to LinkedInSharing to XSharing to Email

Although they hardly need an introduction, Salesforce is a cloud-based customer relationship management (CRM) service that allows businesses to efficiently connect with their customers, find prospects, close deals, automate marketing, develop apps, and analyze their data to draw out valuable insights. In this article we explore whether Canadian businesses subject to Quebec’s private sector privacy law (Law25) whose most important provisions are coming into force September 22, 2023, can safely transfer their customers’ data to Salesforce.Salesforce places significant emphasis on trust. Given the vast amount of data the company is processing and the sensitivity of such data, this is certainly the right strategy as customers’ awareness around their privacy rights increases and the compliance pressure on businesses follows suit. Salesforce’s global reach and complexity of service offerings make it no easy task to ensure compliance. Yet, they have done a great job organizing their public-facing compliance documents in a transparent manner. Customers should nevertheless expect to do some digging when trying to surface the information they need to ensure their obligations to their customers are met when contracting with Salesforce and entrusting them with customer data.

Salesforce Does Not Mention Law25 Compliance

There may, however, be a caveat to all that praise for Salesforce’s privacy posture when it comes to compliance with laws that are lesser known compared to the GDPR and the CCPA. In particular, Quebec’s Law25 finds no mention in any of Salesforce’s extensive public documentation or agreements. While we are assured in the Data Processing Addendum FAQs that their DPA applies globally, and not only where the laws in the regions it specifically mentions applies (the European Union, the European Economic Area and their member states, Switzerland, the United Kingdom and the United States), when it comes to compliance with Canadian privacy laws, the company only points to their compliance with PIPEDA on their “Regional Privacy Laws” website.While the PIPEDA FAQ, last updated in 2019, is captioned “Compliance with Canadian Privacy Laws,” the document nowhere acknowledges that there are other privacy laws applicable in Canada, such as the considerably stricter Law25 in the province Quebec. To be fair, the main provisions of Law25 just came into force September 22, 2023, but businesses now need to know where to focus their compliance efforts.That said, we can confirm that Salesforce is very aware of Law25 and its requirements and can thus speculate that further documentation is available to Canadian customers upon request.

Does It Matter?

There are certain provisions in Law25 that are even stricter than the GDPR, for example when it comes to cookies. The Quebec regulator issued guidance stating that they interpret Law25 to require express consent before a cookie is placed on a customer’s device, while PIPEDA and the GDPR may let implied consent suffice. But that is not really an issue for Salesforce as they would not place cookies on the device of a customer whose data they store. However, some of the apps Salesforce integrates with, such as Slack, place cookies on the devices of the employees of a business using Slack for their internal communications. There’s a good chance that the information gathered on employees via cookies would be considered personal information, as Law25 only explicitly carves out “personal information concerning the performance of duties within an enterprise by the person concerned, such as the person’s name, title and duties, as well as the address, email address and telephone number of the person’s place of work.” There is of course the more salient issue of what customer information may be disclosed in employees’ chats that would thus be transferred to Slack, but we will leave this Pandora’s box unopened for now.What about cross-border data transfers? This must be considered when using Salesforce in Canada. If a Canadian company transfers the data of Quebec residents to Salesforce, this might be a cross-border data transfer requiring an assessment of the receiving jurisdiction. Post-Schrems II, this could pose an insurmountable issue if the data is transferred to the US. Commenting on the EU’s rules around safe cross-border data transfers, the Office of the Privacy Commissioner of Canada, in 2020, opined that:

Using its considerable collective economic clout, the EU has designed a system which relies heavily upon restricting data flows to organizations in jurisdictions where a comparable level of data protection is not available. This comparable level of protection may be achieved by different means. The simplest for organizations is a finding of adequacy. Where there is no adequacy, other options are available, requiring different levels of effort, and considerable involvement of the Commission or national supervisory authorities. As Schrems II makes clear, however, even these measures may be derailed if national security or law enforcement powers in the destination country allow for excessive access to personal data with inadequate recourse for EU data subjects. While such a regime may offer a high level of protection for the personal data of EU residents, it relies upon a level of economic clout that Canada does not have.

This could be read to mean that with Law25 requiring similar adequacy assurances as the GDPR in light of proposed cross-border data transfers, Canadian business may equally be unable to safely transfer data to processors in the US, with the caveat that Canada’s lower level of “economic clout” may not give these businesses sufficient bargaining power to do anything about it.But Salesforce to the rescue. Turns out, when deployed on a public cloud infrastructure, your core Salesforce (i.e., Sales Cloud and Service Cloud) instance will be hosted on AWS’s servers and there is an AWS Region in Canada with the data centre located in Montreal (AWS Canada Central). If you’re not sure where your data is located, you can find this information conveniently in the Salesforce URL. The same holds true for Marketing Cloud Einstein, but not for all Marketing Cloud services. For instance, Marketing Cloud Engagement is hosted using both Salesforce and Google infrastructure in the United States (if purchased before Nov. 28, 2019) or in France, Germany, or Belgium.

But How About Salesforce’s Sub Processors?

Some features of the core products use external APIs. These features are not necessarily made available by default as part of the core products across the customer base as customers usually require an additional level of review and approval beyond the core platform. These external services may not be delivered through the same local data centers. Depending on the Salesforce services the Canadian business wants to use, the data will be transferred by Salesforce to its sub processors. In this 53 page document listing the sub processors you can see, surprise, that not all of them are located in Quebec. For example, using the new Einstein GPT functionality, the data will be located in either the US, Germany, or India, and only one of them is a safe option from a data protection legislation perspective.This is of course not a concern unique to Law25, yet the location of sub processors shows an overwhelmingly larger presence in the EU than in Canada. And we get it, Salesforce, Canada is not that big of a player to make it a priority.

How Private AI Can Help

When it comes to the care for the protection of personal data, on the other hand, Canadian companies are world class players. Private AI, for example, provides personal information redaction software unparalleled in accuracy. The easiest way to comply with strict cross-border transfer privacy requirements is to simply not transmit the personal information. Trained to detect and redact over 50 entity types of personal information, health information, and payment card information in 50 languages, using the latest advancements in Machine Learning, the time-consuming work of redacting data with high accuracy becomes three lines of code. To see the tech in action, try our web demo, or request an API key to try it yourself on your own data.

Conclusion

In the intricate web of global privacy laws, Salesforce's commitment to transparency and trust is commendable, yet the absence of explicit compliance with Quebec's Law25 raises eyebrows. While the company's alignment with PIPEDA and other well-known regulations is clear, the nuanced requirements of Law25, particularly concerning cross-border data transfers, remain unaddressed, at least in Salesforce’s public documentation. Salesforce's utilization of AWS's Canadian data center offers some comfort, but the location of data servers used by sub-processors for additional functionality adds complexity to the compliance puzzle. The answer to the compliance question, it seems, is thus wrapped in layers of legal subtlety and technological intricacy, leaving Canadian businesses to tread carefully and consult with their Salesforce representatives and legal counsel to ensure that their data handling practices align with the stringent demands of Quebec's privacy landscape.

Data Left Behind: AI Scribes’ Promises in Healthcare

Data Left Behind: Healthcare’s Untapped Goldmine

The Future of Health Data: How New Tech is Changing the Game

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