# Québec Law 25, PIPEDA and OSFI: what they mean for your data platform

> PIPEDA sets federal rules for personal information in Canada. Québec Law 25 adds a privacy impact assessment before personal information leaves Québec. OSFI B-10 and B-13 require federally regulated financial institutions to manage third-party and technology risk. Together they push data platforms toward clear residency, access logging and lineage.

Source: https://datanature.ai/blog/quebec-law-25-pipeda-osfi-data-platform
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

## What does PIPEDA require of a data platform?

PIPEDA requires organizations to protect personal information with safeguards appropriate to its sensitivity, and to stay accountable for it when a third party processes it. It does not ban storing data outside Canada, but organizations must be transparent about it and remain responsible.

## What changed with Québec Law 25?

Law 25 requires a privacy impact assessment before personal information is communicated outside Québec. The assessment must show the information will receive adequate protection. Keeping data in a Canadian, and ideally in-province, deployment simplifies that analysis.

## What do OSFI B-10 and B-13 expect?

B-10 covers third-party risk: banks and insurers must assess and manage risk from vendors, including cloud and data platforms. B-13 covers technology and cyber risk: secure configuration, access control, logging and resilience. A platform that runs in the institution's own environment, with strong access control and full audit logs, is easier to evidence against both.

## What should your platform provide?

- A clear answer to where data and metadata live
- Role-based access with row and column rules
- PII discovery and masking
- Audit logs for every query and agent action
- Lineage from report to source
- The option to run in your own environment

## How does DataNature help?

DataNature runs in Canadian or on-premises deployments, operated by a Canadian company, and [Atlas](/platform/atlas) provides the access, masking, audit and lineage evidence. This is not legal advice. Each organization should complete its own assessment.

## How does DataNature Atlas keep this secure and compliant?

Every rule in this article is enforced in one place, inside your jurisdiction. [DataNature Atlas](/platform/atlas) is the platform's governance module:

- **Knows your data**: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
- **Controls access**: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
- **Governs AI**: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
- **Proves it**: lineage from source to metric to decision, and an audit log of who or what accessed which data.
- **Stays local**: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read [DataNature Atlas in depth](/blog/datanature-atlas-governance-rbac-abac-pii-masking) or see [security and compliance](/security).
