Does Canadian PIPEDA cover Act on the Implementation of the General Data Protection Regulation (OG 42/2018)?

14% of Act on the Implementation of the General Data Protection Regulation (OG 42/2018) you already have

Canadian PIPEDA already covers about 14% of Act on the Implementation of the General Data Protection Regulation (OG 42/2018), leaving 38 of 44 controls as genuinely new work.

Already covered 0 Likely covered 6 New work 38

No control in Canadian PIPEDA maps directly to one in Act on the Implementation of the General Data Protection Regulation (OG 42/2018). Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in Canadian PIPEDA reaches these. This is the list to scope.

HR-GDPR-Art.1

Subject and Scope of the Act

HR-GDPR-Art.11

Prohibition on Agency Staff Acting as DPO

HR-GDPR-Art.13

Professional Confidentiality Obligation

HR-GDPR-Art.14

Legislative Consultation with AZOP

HR-GDPR-Art.15

Cooperation with Foreign Supervisory Authorities

HR-GDPR-Art.17

Annual Work Report

HR-GDPR-Art.18

Publication of High-Risk Opinions and Decisions

HR-GDPR-Art.20

Prohibition on Genetic Data Processing for Insurance

HR-GDPR-Art.21

Biometric Data Processing - Public Sector

HR-GDPR-Art.24

Applicability of Biometric Rules and DPIA

HR-GDPR-Art.25

Video Surveillance - Definition

HR-GDPR-Art.27

Video Surveillance - Notice Requirements

HR-GDPR-Art.3

Definitions and Public Authority Bodies

HR-GDPR-Art.30

Video Surveillance of Work Premises

HR-GDPR-Art.31

Video Surveillance in Residential Buildings

HR-GDPR-Art.32

Video Surveillance of Public Areas

HR-GDPR-Art.33

Processing for Statistical Purposes

HR-GDPR-Art.34

Right to Request Determination of Breach

HR-GDPR-Art.35

Interim Relief in Deletion Cases

HR-GDPR-Art.36

Conduct of Supervision (Inspections)

HR-GDPR-Art.37

Copying, Sealing and Temporary Seizure

HR-GDPR-Art.38

Suspicion of Criminal Offence

HR-GDPR-Art.39

Handling of Classified Data

HR-GDPR-Art.4

Supervisory Authority (AZOP)

HR-GDPR-Art.40

Inspection Report (Zapisnik)

HR-GDPR-Art.41

Representation of Data Subjects

HR-GDPR-Art.42

Provision of Expert Opinions

HR-GDPR-Art.43

Fees for Acting on Requests

HR-GDPR-Art.44

Imposition of Administrative Fines

HR-GDPR-Art.45

Administrative Fine Decision

HR-GDPR-Art.46

Payment and Forced Collection of Fines

HR-GDPR-Art.47

Exclusion of Fines for Public Authority Bodies

HR-GDPR-Art.48

Publication of Final Rulings

HR-GDPR-Art.49

Statute of Limitations for Fine Collection

HR-GDPR-Art.5

National Accreditation Body for Certification

HR-GDPR-Art.50

Misdemeanour Penalties for Confidentiality Breach

HR-GDPR-Art.51

Administrative Fines for Video-Surveillance Violations

HR-GDPR-Art.6

Powers and Tasks of the Agency

Show the 6 you already have

HR-GDPR-Art.19

Child's Consent for Information Society Services

HR-GDPR-Art.22

Biometric Data Processing - Private Sector

HR-GDPR-Art.23

Biometric Data of Employees (Time and Access)

HR-GDPR-Art.26

Video Surveillance - Lawful Purpose

HR-GDPR-Art.28

Video Surveillance - Access Control and Logging

HR-GDPR-Art.29

Video Surveillance - Retention Limit

How this is calculated

Already covered means a mapping runs from a control in Canadian PIPEDA to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair · Today's edition