1---2name: multi-jurisdiction-matrix3description: >-4 Guides building a multi-jurisdiction privacy compliance matrix for organisations5 operating across multiple countries. Covers common requirements identification,6 jurisdiction-specific deltas, gap analysis, and harmonised control frameworks.7 Keywords: multi-jurisdiction, compliance matrix, harmonised controls, gap analysis,8 jurisdiction mapping.9license: Apache-2.010metadata:11 source: https://skillmd.com/skills/mukul975-2/multi-jurisdiction-matrix12 author: mukul97513 version: "1.0"14 domain: privacy15 subdomain: global-privacy-regulations16 tags: "multi-jurisdiction, compliance-matrix, harmonised-controls, gap-analysis, jurisdiction-mapping"17---1819# Multi-Jurisdiction Privacy Compliance Matrix2021## Overview2223Organisations operating across multiple jurisdictions face the challenge of complying with overlapping, divergent, and sometimes conflicting privacy requirements. A multi-jurisdiction compliance matrix provides a structured approach to identifying common requirements across all applicable privacy laws, mapping jurisdiction-specific variations (deltas), identifying gaps between current compliance posture and legal requirements, and designing harmonised controls that satisfy the most stringent requirements across all jurisdictions.2425## Compliance Matrix Structure2627### Dimension 1: Requirement Categories2829| Category | Sub-Categories |30|----------|---------------|31| Lawful basis for processing | Consent, legitimate interest, contract, legal obligation, vital interests, public interest |32| Individual rights | Access, correction, deletion/erasure, portability, restriction, objection, automated decision review |33| Consent management | Form, withdrawal, children, sensitive data, separate consent |34| Data collection and notice | Notice content, timing, language, format |35| Cross-border transfers | Mechanisms, adequacy, contractual safeguards, data localisation |36| Data protection officer | Appointment criteria, qualifications, independence, functions |37| Breach notification | Authority notification, individual notification, timelines, content |38| Impact assessment | When required, contents, review cycle |39| Security safeguards | Technical measures, organisational measures, encryption, access control |40| Retention and deletion | Limitation periods, destruction methods, legal holds |41| Enforcement and penalties | Administrative fines, criminal penalties, civil liability |42| Record-keeping | Processing records, consent records, transfer records, breach records |4344### Dimension 2: Jurisdictions4546For Zenith Global Enterprises, the compliance matrix covers:4748| Jurisdiction | Primary Law | Regulator |49|-------------|-------------|-----------|50| European Union | GDPR | National DPAs / EDPB |51| United Kingdom | UK GDPR + DPA 2018 | ICO |52| Brazil | LGPD (Lei 13.709/2018) | ANPD |53| China | PIPL | CAC |54| South Korea | PIPA | PIPC |55| India | DPDP Act 2023 | DPBI |56| Thailand | PDPA B.E. 2562 | PDPC |57| Singapore | PDPA 2012 | PDPC |58| Japan | APPI | PPC |59| Australia | Privacy Act 1988 | OAIC |60| United States | State laws (CCPA/CPRA, etc.) | State AGs / CPPA (California) |6162## Cross-Jurisdiction Requirement Comparison6364### Lawful Bases Comparison6566| Jurisdiction | Consent | Contract | Legitimate Interest | Legal Obligation | Vital Interests | Other Unique Bases |67|-------------|---------|----------|-------------------|-----------------|-----------------|-------------------|68| EU (GDPR) | Art. 6(1)(a) | Art. 6(1)(b) | Art. 6(1)(f) | Art. 6(1)(c) | Art. 6(1)(d) | Public interest (Art. 6(1)(e)) |69| Brazil (LGPD) | Art. 7, I | Art. 7, V | Art. 7, IX | Art. 7, II | Art. 7, VII | Credit protection (Art. 7, X); Research (Art. 7, IV); Public policy (Art. 7, III); Health (Art. 7, VIII); Exercise of rights (Art. 7, VI) |70| China (PIPL) | Art. 13(1) | Art. 13(2) | None | Art. 13(3) | Art. 13(4) | Publicly disclosed (Art. 13(6)); Other statutory (Art. 13(7)) |71| Korea (PIPA) | Art. 15(1)(1) | Art. 15(1)(4) | Art. 15(1)(6) (2023) | Art. 15(1)(2) | Art. 15(1)(5) | Public institution duty (Art. 15(1)(3)) |72| India (DPDP) | Section 6 | N/A (under legitimate uses) | N/A | Section 7(c) | Section 7(d) | Employment (Section 7(f)); State functions (Section 7(b)) |73| Japan (APPI) | Implied consent | Permitted purpose | None (use limitation approach) | Statutory basis | Life protection | Pseudonymous processing (relaxed rules) |7475### Breach Notification Timeline Comparison7677| Jurisdiction | Authority Timeline | Individual Timeline | Threshold |78|-------------|-------------------|--------------------|-----------|79| EU (GDPR) | 72 hours from awareness | Without undue delay | Risk to rights and freedoms |80| UK GDPR | 72 hours from awareness | Without undue delay | Risk to rights and freedoms |81| Brazil (LGPD) | 3 business days | 3 business days | Relevant risk or damage |82| China (PIPL) | Promptly (no fixed deadline) | Promptly | Any PI security incident |83| Korea (PIPA) | 72 hours (1,000+ individuals) | Without delay | Any breach |84| India (DPDP) | 72 hours (draft rules) | 72 hours (draft rules) | Likely harm to data principal |85| Thailand (PDPA) | 72 hours | Without delay if high risk | Affects rights and freedoms |86| Singapore (PDPA) | 3 calendar days after assessment | As soon as practicable | Significant harm OR 500+ individuals |87| Japan (APPI) | 3-5 business days (preliminary) | Promptly | PPC-defined thresholds |88| Australia (Privacy Act) | As soon as practicable (30-day assessment) | As soon as practicable | Likely serious harm |8990### Children's Age Thresholds9192| Jurisdiction | Age Threshold | Parental Consent Mechanism |93|-------------|--------------|---------------------------|94| EU (GDPR) | 16 (Member States may lower to 13) | Art. 8: Parental consent for ISS |95| Brazil (LGPD) | Best interest standard | At least one parent's consent |96| China (PIPL) | Under 14 = minor PI | Parent/guardian consent |97| Korea (PIPA) | Under 14 | Legal representative consent |98| India (DPDP) | Under 18 | Verifiable parental consent |99| Thailand (PDPA) | Under 10 for parental consent | Parent/guardian consent |100| Singapore (PDPA) | No specific age (reasonable expectations) | Not specified |101| Japan (APPI) | No specific threshold | General consent rules apply |102| Australia | Under 18 (reform amendments) | Best interests standard; children's code |103104## Harmonised Control Framework105106### Principle: Highest Common Denominator107108The harmonised control framework applies the most stringent requirement from any jurisdiction as the baseline control, ensuring compliance across all operating jurisdictions.109110### Harmonised Controls for Zenith Global Enterprises111112| Control Area | Harmonised Standard | Driven By |113|-------------|-------------------|-----------|114| Consent | Free, specific, informed, unambiguous, separate per purpose, with easy withdrawal | EU GDPR + China PIPL separate consent |115| Breach notification | 72 hours to authority + individuals simultaneously | EU GDPR / Korea PIPA / India DPDP |116| Children's consent | Parental consent for all processing of under-18 data | India DPDP (18 threshold) |117| DPO appointment | Appoint in all jurisdictions with >500 employees or significant processing | EU GDPR / Thailand PDPA / Brazil LGPD |118| Impact assessment | Conduct for all high-risk processing, cross-border transfers, automated decisions | EU GDPR + China PIPL + Australia (2024) |119| Retention | Delete within 5 days of purpose fulfilment | Korea PIPA (most stringent) |120| Security | AES-256 encryption at rest and TLS 1.3 in transit | Cross-jurisdiction best practice |121| Cross-border transfer | Contractual safeguards + TIA + consent where required | EU GDPR SCCs + China PIPL mechanisms |122| Record-keeping | 7-year retention for consent records, processing records, transfer records | India DPDP (7-year consent manager), extended by statutory requirements |123| Automated decisions | Transparency notice + human review + impact assessment | EU GDPR Art. 22 + Australia 2024 |124125## Jurisdiction-Specific Deltas126127### Requirements Unique to Specific Jurisdictions128129| Delta | Jurisdiction | Requirement | Harmonised Approach |130|-------|-------------|-------------|-------------------|131| Credit protection basis | Brazil | Art. 7, X — lawful basis for credit protection | Document where Brazil-specific basis is relied upon |132| Separate consent (单独同意) | China | Five specific separate consent triggers | Implement separate consent globally where any trigger is met |133| Pre-transfer information | Japan | Provide destination country PI protection system info before consent | Include in all cross-border consent forms globally |134| DNC Registry check | Singapore | Mandatory check before telephone/SMS marketing | Implement DNC checking in Singapore; voluntary in other jurisdictions |135| Data localisation | China (CIIO) | CIIO must store data in PRC | Local storage for PRC data; process copies abroad |136| Resident registration number encryption | Korea | Mandatory encryption for RRN | Encrypt all government identifiers in all jurisdictions |137| Consent Manager | India | Registered intermediary for consent management | Integrate with consent manager in India; optional elsewhere |138| Pseudonymisation framework | Korea / Japan | Statutory pseudonymisation frameworks | Implement pseudonymisation programme meeting both PIPA and APPI standards |139140## Gap Identification Process141142### Step 1: Map Current Controls1431. Document existing privacy controls, policies, and procedures.1442. Map each control to the requirements of each applicable jurisdiction.1453. Identify controls that satisfy requirements in multiple jurisdictions.146147### Step 2: Identify Gaps1481. For each jurisdiction, identify requirements not met by existing controls.1492. Classify gaps as: critical (legal non-compliance), significant (enforcement risk), or minor (best practice deficit).1503. Prioritise gaps based on: regulatory activity in the jurisdiction, potential penalty exposure, data subject volume.151152### Step 3: Design Remediation1531. Where possible, design a single harmonised control that addresses the gap across all jurisdictions.1542. Where harmonisation is not possible (conflicting requirements), design jurisdiction-specific controls.1553. Estimate remediation effort and timeline.1564. Assign ownership and track implementation.157158## Compliance Matrix Governance159160| Element | Detail |161|---------|--------|162| Matrix owner | Chief Privacy Officer, Zenith Global Enterprises |163| Update frequency | Quarterly for law changes; annual comprehensive review |164| Change trigger | New jurisdiction entry, significant law amendment, enforcement action |165| Review committee | Privacy Steering Committee (CPO, regional DPOs, Legal, IT Security) |166| Tool | Compliance matrix maintained in GRC platform with automated law change alerts |