
cross-border-transfers-skills
12 cross-border transfer skills: SCCs, BCRs, adequacy assessments, TIAs, data localization, Art. 49 derogations
- version
- 1.0.0
- GitHub stars
- 340
Install
/plugin install cross-border-transfers-skills@privacy-data-protection-skillsRun it inside Claude Code after adding the marketplace with /plugin marketplace add mukul975/Privacy-Data-Protection-Skills.
Contents
Discovered from sourceSkills 12
Assessing Third-Country Adequacy
Overview
GDPR Article 45 provides that the European Commission may determine that a third country, a territory, or one or more specified sectors within a third country, or an international organisation ensures an adequate level of protection for personal data. Where such an adequacy decision exists, transfers of personal data to the covered country, territory, or sector may take place without any specific authorisation or additional safeguard requirement. This skill guides the assessment of existing adequacy decisions and the handling of partial adequacy coverage.
Current EC Adequacy Decisions
As of March 2026, the European Commission has adopted adequacy decisions for the following countries and territories:
| Country/Territory | Decision Reference | Date Adopted | Scope | Periodic Review |
|---|---|---|---|---|
| Andorra | Decision 2010/625/EU | 19 October 2010 | Full country | Ongoing monitoring |
| Argentina | Decision 2003/490/EC | 30 June 2003 | Full country | Ongoing monitoring |
| Canada | Decision 2002/2/EC | 20 December 2001 | Commercial organisations subject to PIPEDA only | Ongoing monitoring |
| Faroe Islands | Decision 2010/146/EU | 5 March 2010 | Full territory | Ongoing monitoring |
| Guernsey | Decision 2003/821/EC | 21 November 2003 | Full territory | Ongoing monitoring |
| Israel | Decision 2011/61/EU | 31 January 2011 | Full country | Ongoing monitoring |
| Isle of Man | Decision 2004/411/EC | 28 April 2004 | Full territory | Ongoing monitoring |
| Japan | Decision (EU) 2019/419 | 23 January 2019 | Commercial sector subject to APPI supplementary rules | Biennial review; first review completed January 2021; second review 2023 |
| Jersey | Decision 2008/393/EC | 8 May 2008 | Full territory | Ongoing monitoring |
| New Zealand | Decision 2013/65/EU | 19 December 2012 | Full country | Ongoing monitoring |
| South Korea | Decision (EU) 2022/254 | 17 December 2021 (effective 2022) | Commercial and public sector subject to PIPA | Biennial review |
| Switzerland | Decision 2000/518/EC | 26 July 2000 | Full country | Ongoing monitoring; assessed under revised FADP effective 1 September 2023 |
| United Kingdom | Decision (EU) 2021/1772 | 28 June 2021 | Full country | Sunset clause: expires 27 June 2025 unless renewed; renewal assessment underway |
| Uruguay | Decision 2012/484/EU | 21 August 2012 | Full country | Ongoing monitoring |
| United States (DPF) | Decision (EU) 2023/1795 | 10 July 2023 | Self-certified organisations under the EU-US DPF only | Annual review; first review October 2024 |
Adequacy Assessment Criteria (Art. 45(2))
When the Commission assesses the adequacy of the level of protection in a third country, it considers:
(a) Rule of Law and Human Rights
- Respect for human rights and fundamental freedoms
- General and sectoral legislation, including public security, defence, national security, and criminal law
- Access by public authorities to personal data
- Effective and enforceable data subject rights
(b) Independent Supervisory Authority
- Existence and effective functioning of one or more independent supervisory authorities with responsibility for ensuring and enforcing data protection rules
- Adequate enforcement powers including the power to investigate, intervene, and impose corrective measures
- Independence from government interference
(c) International Commitments
- International commitments the third country has entered into, including multilateral and bilateral agreements relating to the protection of personal data
- Binding and enforceable obligations arising from such commitments
Partial Adequacy Handling
Several adequacy decisions cover only specific sectors or types of organisations within a country. Proper handling of partial adequacy is essential.
Canada — PIPEDA Partial Adequacy
Scope: Only transfers to Canadian organisations subject to the Personal Information Protection and Electronic Documents Act (PIPEDA) are covered by the adequacy decision. Provincial private-sector privacy laws that have been declared substantially similar to PIPEDA by the Governor in Council also fall within scope (e.g., Alberta PIPA, British Columbia PIPA, Quebec Act respecting the protection of personal information in the private sector).
Not covered:
- Canadian public sector organisations (federal and provincial government agencies)
- Organisations operating under provincial health information legislation
- Organisations not subject to PIPEDA or substantially similar legislation
Verification: Before relying on the Canada adequacy decision, confirm that the specific Canadian recipient is subject to PIPEDA or a substantially similar provincial law.
Japan — APPI Supplementary Rules
Scope: The adequacy decision covers commercial sector entities subject to Japan's Act on the Protection of Personal Information (APPI) and the supplementary rules adopted by the Personal Information Protection Commission (PPC) of Japan specifically for the purpose of the EU adequacy finding.
Supplementary rules:
- Treatment of sensitive data: Japanese operators receiving data from the EU must treat all data received as "requiring special care" regardless of its category under APPI
- Retention limitation: Data must be deleted when no longer necessary for the purpose of use
- Onward transfers: Transfers outside Japan require either the data subject's consent or assurance that the recipient country provides equivalent protection
- Anonymously processed information: Restrictions on the use of anonymised data equivalent to GDPR standards
Verification: Confirm the Japanese recipient is subject to APPI and has implemented the supplementary rules.
United States — DPF Self-Certification
Scope: Only transfers to US organisations that have actively self-certified to the DPF with the Department of Commerce and are subject to FTC or DoT jurisdiction.
Not covered:
- US government agencies
- Non-certified US organisations
- Organisations subject to regulators other than FTC/DoT (e.g., national banks, telecommunications carriers, insurance companies regulated by state insurance commissioners)
Verification: Check dataprivacyframework.gov for active certification status before each transfer.
South Korea — PIPA Coverage
Scope: Covers both commercial and public sector organisations subject to the Personal Information Protection Act (PIPA), as amended in 2023.
Not covered: Processing by intelligence and national security agencies exempt from PIPA.
Adequacy Decision Monitoring
Periodic Review Obligations
Under Art. 45(3), the Commission must periodically review adequacy decisions at least every four years. Some decisions include more frequent review commitments:
| Decision | Review Frequency | Last Review | Next Review Due |
|---|---|---|---|
| Japan | Biennial | 2023 | 2025 |
| South Korea | Biennial | 2024 | 2026 |
| United States (DPF) | Annual | October 2024 | October 2025 |
| United Kingdom | Before sunset (June 2025) | Ongoing | June 2025 |
| Legacy decisions (Andorra, Argentina, etc.) | At least every 4 years | Various | Varies |
Monitoring Actions for Organisations
- Subscribe to Commission notifications: Monitor the EC's data protection page and the EDPB's news section for announcements regarding adequacy reviews.
- Track legislative changes: Monitor data protection legislative developments in countries where the organisation relies on adequacy decisions.
- UK adequacy sunset: The UK adequacy decision contains a sunset clause expiring 27 June 2025. If not renewed, organisations must transition UK transfers to SCCs or other mechanisms immediately.
- DPF legal challenges: Monitor CJEU proceedings for any challenge to the DPF adequacy decision.
- Maintain backup mechanisms: For transfers relying on adequacy decisions with upcoming reviews or known risks, maintain executed SCCs as a contingency.
Practical Verification Workflow
For each transfer relying on an adequacy decision:
- Identify the adequacy decision: Confirm which decision covers the destination country or sector.
- Verify scope coverage: Confirm the specific recipient falls within the scope of the adequacy decision (not a partial adequacy gap).
- Verify the decision remains in force: Check the EC's list of adequacy decisions and any recent amendments, suspensions, or repeals.
- Document in the transfer register: Record the adequacy decision reference, scope coverage verification, and next review date.
- Set a monitoring reminder: Calendar the next periodic review date and any sunset clause deadlines.
- Contingency planning: For decisions with known risks (UK sunset, DPF legal challenges), prepare backup SCCs.
Managing APAC Cross-Border Transfers
Overview
The Asia-Pacific region encompasses diverse data protection regimes with varying cross-border transfer mechanisms. Unlike the GDPR's unified framework, APAC transfers require navigating multiple overlapping systems: the APEC Cross-Border Privacy Rules (CBPR), ASEAN Model Contractual Clauses (MCCs), and country-specific mechanisms under Japan's APPI, South Korea's PIPA, Thailand's PDPA, and Singapore's PDPA. This skill provides a jurisdiction-by-jurisdiction guide to managing cross-border data flows across the APAC region.
APEC Cross-Border Privacy Rules (CBPR) System
Framework
The APEC CBPR system is a voluntary, accountability-based mechanism enabling participating organisations to demonstrate compliance with internationally recognised privacy protections for cross-border data flows within the APEC region.
Participating economies (as of March 2026): Australia, Canada, Japan, South Korea, Mexico, Philippines, Singapore, Chinese Taipei, United States.
Key features:
- Organisations self-certify compliance with the APEC Privacy Framework principles
- Certification is conducted by an APEC-recognised Accountability Agent (e.g., TRUSTe/TrustArc for the US, JIPDEC for Japan)
- CBPR certification covers only the data flows of the specific certified organisation, not the entire economy
- The Global CBPR Forum (established April 2022) aims to expand the system beyond APEC membership
CBPR Principles
| Principle | Description |
|---|---|
| Preventing Harm | Recognising the interests of the individual regarding the protection of their information |
| Notice | Providing clear and easily accessible statements about data practices |
| Collection Limitation | Limiting personal information collection to that which is relevant |
| Uses of Personal Information | Using personal information only for purposes fulfilling the individual's expectations or as authorised by law |
| Choice | Providing individuals with choice regarding collection, use, and disclosure |
| Integrity of Personal Information | Maintaining the accuracy, completeness, and currency of personal information |
| Security Safeguards | Protecting personal information with appropriate security safeguards |
| Access and Correction | Providing individuals with access to their information and the ability to correct inaccurate data |
| Accountability | Being accountable for complying with measures that give effect to the principles |
CBPR and EU Interoperability
- CBPR certification is not recognised as an adequate safeguard under GDPR Chapter V.
- For EU-to-APAC transfers, EU SCCs remain required even if the APAC recipient is CBPR-certified.
- However, CBPR certification can serve as evidence of the recipient's data protection maturity in a TIA assessment.
ASEAN Model Contractual Clauses (MCCs)
Framework
The ASEAN Model Contractual Clauses were adopted by the ASEAN Telecommunications and IT Ministers in 2021 to facilitate cross-border data flows within the ASEAN Economic Community while maintaining data protection standards.
ASEAN Member States: Brunei, Cambodia, Indonesia, Laos, Malaysia, Myanmar, Philippines, Singapore, Thailand, Vietnam.
Key features:
- Model clauses for controller-to-controller and controller-to-processor transfers
- Non-binding guidance — Member States may adopt or adapt the MCCs
- Designed to be compatible with other international transfer mechanisms (EU SCCs, APEC CBPR)
- Implementation varies by Member State; Singapore and Philippines have been early adopters
MCC Structure
| Section | Content |
|---|---|
| Clause 1 | Definitions aligned with ASEAN Framework on Personal Data Protection |
| Clause 2 | Obligations of the data exporter |
| Clause 3 | Obligations of the data importer |
| Clause 4 | Rights of data subjects |
| Clause 5 | Liability and indemnification |
| Clause 6 | Governing law and dispute resolution |
| Clause 7 | Termination and data return/deletion |
| Schedule 1 | Description of transfer (parties, data, purposes) |
| Schedule 2 | Technical and organisational measures |
Japan — APPI Cross-Border Transfer Provisions
Act on the Protection of Personal Information (APPI) — Amended 2022
Art. 28 (Cross-Border Transfer):
- Transfer of personal data to a third party in a foreign country requires one of:
- Consent: The individual's consent, after being provided with information about the foreign country's data protection regime, the receiving party's privacy protections, and other relevant information per PPC Rules Art. 17
- Adequate country: The foreign country has been recognised by the PPC as providing equivalent data protection standards (currently: EU/EEA countries and the UK)
- Equivalent measures: The recipient has established an equivalent system of measures for handling personal information in conformity with APPI standards, including internal rules and an independent oversight mechanism
PPC Supplementary Rules for EU Adequacy:
- Applied reciprocally under the EU-Japan adequacy mutual recognition
- Japanese operators receiving EU-origin data must treat all such data as "requiring special care"
- Additional retention limitations and onward transfer restrictions apply
Athena Global Logistics implementation (Japan operations):
- Transfers from Japan to Germany: rely on PPC adequate country recognition of the EU
- Transfers from Japan to Hong Kong: obtain individual consent per Art. 28 after providing foreign country information
- Transfers from EU to Japan: rely on EU adequacy decision (Decision 2019/419) with supplementary rules
South Korea — PIPA Cross-Border Provisions
Personal Information Protection Act (PIPA) — Amended 2023
Art. 28-2 (Cross-Border Transfer):
- Transfer permitted when:
- Consent: The data subject's consent after being informed of the recipient, purpose, categories of data, retention period, and the right to refuse
- Adequacy recognition: Transfer to a country recognised by the Personal Information Protection Commission (PIPC) as having an equivalent level of protection
- Contractual safeguards: The recipient has provided contractual safeguards equivalent to PIPA standards
- PIPC-approved certification: The recipient holds a certification recognised by the PIPC
EU-Korea interoperability:
- The EU has adopted an adequacy decision for South Korea (Decision 2022/254)
- South Korea has recognised the EU as providing equivalent protection
- This creates a bilateral mutual recognition framework similar to the EU-Japan arrangement
Athena Global Logistics implementation (Korea operations):
- Transfers from Korea to Germany: rely on PIPC adequacy recognition of the EU
- Transfers from EU to Korea: rely on EU adequacy decision for Korea
- Transfers from Korea to non-adequate countries: obtain consent per Art. 28-2 with full information disclosure
Thailand — PDPA Cross-Border Provisions
Personal Data Protection Act B.E. 2562 (2019) — Effective 1 June 2022
Section 28 (Cross-Border Transfer):
- Transfer to a foreign country permitted when:
- The destination country has adequate data protection standards as prescribed by the PDPC (Personal Data Protection Committee)
- Compliance with Binding Corporate Rules approved by the PDPC Office
- The transfer is subject to a data protection policy of the same group of business, inspected and certified by the PDPC Office
- The transfer is subject to contractual safeguards between the transferor and transferee
- The transfer is necessary for contract performance, vital interests, important public interest, legal claims, or with the data subject's explicit consent (derogation conditions similar to GDPR Art. 49)
PDPC Notification on Adequacy (pending):
- As of March 2026, the PDPC has not yet published the list of adequate countries.
- In the interim, organisations rely on contractual safeguards or consent for cross-border transfers.
Athena Global Logistics implementation (Thailand operations):
- Transfers from Thailand to Germany: contractual safeguards (data processing agreement with PDPA-aligned clauses)
- Transfers from EU to Thailand: EU SCCs Module 2 (no EU adequacy decision for Thailand)
- Domestic processing: Pinnacle Data Services Co Ltd (Bangkok) operates under Thai PDPA with contractual safeguards from TransPacific Freight Solutions
Singapore — PDPA Cross-Border Provisions
Personal Data Protection Act 2012 (PDPA) — Amended 2021
Section 26 (Transfer Limitation Obligation):
- An organisation must not transfer personal data outside Singapore unless it takes appropriate steps to ensure the recipient is bound by legally enforceable obligations to provide a standard of protection at least comparable to the PDPA.
Mechanisms for compliance:
- Contractual arrangements: Contract with the recipient obligating them to meet PDPA-equivalent standards
- Binding corporate rules: Intra-group policies providing equivalent protection
- PDPC-approved frameworks: Compliance with APEC CBPR or other PDPC-recognised certification
- Consent: The individual consents to the transfer after being informed of the non-comparable standard
- Prescribed exceptions: Necessary for contract performance, public interest, vital interests, or legal proceedings
PDPC enforcement:
- The PDPC actively enforces the transfer limitation obligation.
- Fines up to SGD 1 million per breach (increased under 2021 amendments to up to 10% of annual turnover for organisations with annual turnover exceeding SGD 10 million).
Athena Global Logistics implementation (Singapore operations):
- CloudVault Asia Pte Ltd (sub-processor in Singapore): PDPA-compliant; transfers to EU governed by PDPA contractual arrangements
- Transfers from Singapore to Germany: contractual safeguards in the data processing agreement
- Transfers from EU to Singapore: EU SCCs Module 3 (P2P, as CloudVault is a sub-processor of TransPacific)
Cross-Jurisdictional Transfer Matrix
| From → To | Japan | South Korea | Thailand | Singapore | Hong Kong | EU/EEA | United States |
|---|---|---|---|---|---|---|---|
| Japan | N/A | Consent/Equivalent measures | Consent/Equivalent measures | Consent/Equivalent measures | Consent/Equivalent measures | PPC adequate country | Consent/Equivalent measures |
| South Korea | PIPC adequacy | N/A | Consent/Contract | Consent/Contract | Consent/Contract | PIPC adequacy | Consent/Contract |
| Thailand | Contract/Consent | Contract/Consent | N/A | Contract/Consent | Contract/Consent | Contract/Consent | Contract/Consent |
| Singapore | PDPA contract | PDPA contract | PDPA contract | N/A | PDPA contract | PDPA contract | PDPA contract |
| EU/EEA | EU adequacy | EU adequacy | SCCs + TIA | SCCs + TIA | SCCs + TIA | N/A | DPF / SCCs + TIA |
Practical Implementation Considerations
- Multi-mechanism compliance: A single data flow from the EU through Japan to Singapore may require EU adequacy reliance (EU→JP), Japan Art. 28 adequate country (JP→SG equivalent measures), and Singapore PDPA contractual safeguards — three mechanisms for one flow.
- Contractual harmonisation: Use a single data processing agreement with jurisdiction-specific addenda to cover GDPR, APPI, PIPA, PDPA (Thailand), and PDPA (Singapore) requirements simultaneously.
- Consent fatigue: Where multiple jurisdictions require consent for cross-border transfer, coordinate consent collection to avoid multiple consent requests for the same transfer chain.
- Monitoring burden: Each APAC jurisdiction's transfer rules evolve independently; maintain a monitoring programme covering all applicable laws.
Assessing Article 49 Derogations
Overview
Article 49 GDPR provides a limited set of derogations permitting international data transfers in the absence of an adequacy decision (Art. 45) or appropriate safeguards (Art. 46). The EDPB has consistently emphasised in Guidelines 2/2018 on derogations under Article 49 (adopted 25 May 2018, last updated 6 February 2018) that these derogations must be interpreted restrictively and are intended as exceptions rather than the rule. They cannot serve as a basis for systematic, large-scale, or regular transfers.
Derogation Conditions
Art. 49(1)(a) — Explicit Consent
Condition: The data subject has explicitly consented to the proposed transfer, after having been informed of the possible risks of such transfers for the data subject due to the absence of an adequacy decision and appropriate safeguards.
Requirements:
- Specific: Consent must specifically cover the transfer to the identified third country, not merely the processing activity itself.
- Informed: The data subject must be told:
- The specific third country or countries to which data will be transferred
- The absence of an adequacy decision for that country
- The absence of appropriate safeguards (SCCs, BCRs)
- The specific risks arising from this (e.g., government access without EU-equivalent protections)
- Explicit: Must be an unambiguous affirmative statement; implied consent or pre-ticked boxes are insufficient.
- Freely given: No detriment to the data subject for withholding consent; must be a genuine choice.
- Withdrawable: Data subject can withdraw consent at any time; withdrawal does not affect lawfulness of prior transfers.
Athena Global Logistics example use case: A European customer requests that their consignment tracking data be shared with their own broker in a non-adequate country. The customer is informed of the risks and explicitly consents via a signed transfer consent form.
Limitations (EDPB Guidelines 2/2018):
- Cannot be used for systematic, repetitive, or large-scale transfers
- Not appropriate in employer-employee relationships due to the power imbalance (consent is unlikely to be freely given)
- Not a substitute for establishing systematic transfer mechanisms
Art. 49(1)(b) — Necessary for Contract Performance
Condition: The transfer is necessary for the performance of a contract between the data subject and the controller, or the implementation of pre-contractual measures taken at the data subject's request.
Requirements:
- Direct contractual relationship: A contract exists between the data subject and the controller (not between two controllers or a controller and a third party).
- Necessity: The transfer must be objectively necessary for performing the contract — not merely useful or commercially convenient.
- Close and substantial connection: There must be a close link between the transfer and the performance of the specific contractual obligation.
- Occasional: This derogation is appropriate for occasional transfers; systematic reliance is not permitted.
Athena Global Logistics example use case: A European individual customer contracts Athena to ship personal effects to a non-adequate country. Transfer of the customer's address and contact details to the destination country delivery partner is necessary to perform the shipping contract.
EDPB restrictive interpretation:
- The contract must be with the data subject themselves, not with a corporate customer transferring employee data
- The fact that a transfer is commercially necessary is not sufficient; it must be contractually necessary
- If alternative means of contract performance exist that do not require the transfer, this derogation may not apply
Art. 49(1)(c) — Necessary for Contract in the Interest of the Data Subject
Condition: The transfer is necessary for the conclusion or performance of a contract concluded in the interest of the data subject between the controller and another natural or legal person.
Requirements:
- Contract between controller and a third party: Unlike Art. 49(1)(b), this covers contracts where the data subject is not a party.
- In the interest of the data subject: The contract must serve the data subject's interests (e.g., insurance taken out on their behalf, travel arrangements made for them).
- Necessity: The transfer must be objectively necessary for the contract, not merely convenient.
- Occasional: Not a basis for systematic transfers.
Athena Global Logistics example use case: Athena arranges cargo insurance with a non-EU insurer on behalf of a customer. The transfer of the customer's details to the insurer is in the customer's interest to ensure coverage.
Art. 49(1)(d) — Important Reasons of Public Interest
Condition: The transfer is necessary for important reasons of public interest.
Requirements:
- Recognised in EU or Member State law: The public interest must be recognised in Union law or in the law of the Member State to which the controller is subject.
- Important: Not any public interest qualifies; it must be of significant importance (e.g., international cooperation for tax enforcement, anti-money laundering, cross-border criminal investigations).
- Necessary: The transfer must be necessary to serve that public interest.
- Cannot be used by private entities for commercial purposes: Private companies cannot invoke public interest to justify commercial data transfers.
Athena Global Logistics example use case: Transfer of customer identity and shipment data to a third-country customs authority pursuant to a bilateral customs cooperation agreement between Germany and the third country, as required by EU Regulation 952/2013 (Union Customs Code).
Art. 49(1)(e) — Legal Claims
Condition: The transfer is necessary for the establishment, exercise, or defence of legal claims.
Requirements:
- Actual or contemplated proceedings: There must be actual legal proceedings or a concrete and identifiable prospect of proceedings (not merely a theoretical possibility).
- Necessity: Only the data necessary for the legal claim may be transferred.
- Broad scope: Covers judicial proceedings, administrative proceedings, and out-of-court procedures including regulatory investigations.
- Occasional: Transfers must be linked to specific proceedings, not used as a routine transfer basis.
Athena Global Logistics example use case: Transfer of employment records to a non-EU jurisdiction where a former employee has filed a labour dispute claim, and the records are necessary for the company's defence.
Art. 49(1)(f) — Vital Interests
Condition: The transfer is necessary in order to protect the vital interests of the data subject or of other persons, where the data subject is physically or legally incapable of giving consent.
Requirements:
- Life or death: Vital interests typically relate to life-threatening situations (medical emergencies, natural disasters).
- Incapacity: The data subject must be unable to consent (unconscious, incapacitated, or legally incapable).
- Strict necessity: Only data strictly necessary to protect the vital interest.
- Rare application: This derogation is very narrow and applies to genuine emergency situations.
Athena Global Logistics example use case: Transfer of a crew member's medical records to a third-country hospital following a medical emergency during international transport operations.
Art. 49(1)(g) — Public Register
Condition: The transfer is made from a register which according to Union or Member State law is intended to provide information to the public and which is open to consultation either by the public in general or by any person who can demonstrate a legitimate interest.
Requirements:
- Legally established public register: The register must be established by law with the explicit purpose of public access.
- Not the entire register: Only specific entries may be transferred, not bulk copies of the entire register.
- Conditions for consultation met: The conditions for access specified in the law establishing the register must be fulfilled.
Athena Global Logistics example use case: Transfer of company registration data from the German Handelsregister to a non-EU business partner for due diligence purposes, where the Handelsregister is a public register under German law.
Art. 49(1) second subparagraph — Compelling Legitimate Interests
Condition: Where none of the other derogations applies, a transfer may take place if: (a) the transfer is not repetitive; (b) concerns only a limited number of data subjects; (c) is necessary for the purposes of compelling legitimate interests pursued by the controller; (d) these interests are not overridden by the interests or rights and freedoms of the data subject; and (e) the controller has assessed all the circumstances surrounding the transfer and has provided suitable safeguards.
Requirements:
- Last resort: This is the derogation of last resort, applicable only when no other Art. 49 condition is met and no Art. 45/46 mechanism is available.
- Not repetitive: One-time or very occasional transfers only.
- Limited data subjects: Small number of individuals affected.
- Compelling legitimate interest: Higher threshold than ordinary Art. 6(1)(f) legitimate interest; must be compelling.
- Balancing test: Controller must document the balancing of its interests against the data subjects' rights and freedoms.
- Suitable safeguards: Controller must provide suitable safeguards regarding the protection of personal data.
- SA notification: The controller must inform the supervisory authority of the transfer.
- Data subject information: The controller must inform the data subject of the transfer and the compelling legitimate interests pursued.
Athena Global Logistics example use case: A one-time transfer of a former employee's contact details to a non-EU regulatory authority investigating a historical compliance matter, where no other derogation applies and the transfer concerns a single individual.
Decision Tree for Art. 49 Derogation Selection
Is there an adequacy decision for the destination country? (Art. 45)
├── YES → Transfer under adequacy; Art. 49 not needed
└── NO → Can appropriate safeguards be established? (Art. 46)
├── YES → Use SCCs/BCRs/etc.; Art. 49 not needed
└── NO → Is the transfer systematic, repetitive, or large-scale?
├── YES → Art. 49 derogations generally NOT available
│ (establish Art. 46 safeguards instead)
└── NO → Apply Art. 49 derogation assessment:
├── Has the data subject explicitly consented? → Art. 49(1)(a)
├── Is transfer necessary for DS contract? → Art. 49(1)(b)
├── Is transfer for a contract in DS interest? → Art. 49(1)(c)
├── Is transfer for important public interest? → Art. 49(1)(d)
├── Is transfer for legal claims? → Art. 49(1)(e)
├── Is transfer for vital interests? → Art. 49(1)(f)
├── Is transfer from a public register? → Art. 49(1)(g)
└── None of the above? → Art. 49(1) compelling legitimate interests
(last resort, with SA notification)
Documentation Requirements
For every transfer relying on an Art. 49 derogation, the following must be documented:
- Derogation relied upon: Specific Art. 49 sub-paragraph
- Justification: Why the derogation applies to this specific transfer
- Why Art. 45/46 mechanisms are not available: Explanation of why adequacy or appropriate safeguards cannot be used
- Necessity analysis: Why the transfer is necessary (not merely useful or convenient)
- Data minimisation: Confirmation that only the minimum necessary data is transferred
- Occasional nature: Confirmation that the transfer is not systematic or repetitive
- Risk to data subjects: Assessment of the risks arising from the transfer
- Safeguards applied: Any safeguards implemented to mitigate risks
- For Art. 49(1)(a): Copy of the consent form and evidence of information provided
- For Art. 49(1) compelling legitimate interests: SA notification record, balancing test documentation, and suitable safeguards description
Establishing Binding Corporate Rules
Overview
Binding Corporate Rules (BCRs) are internal data protection policies adopted by a multinational group of undertakings or enterprises to permit transfers of personal data from EU/EEA entities to group members in third countries under GDPR Article 47. BCRs provide a legally binding framework that ensures an essentially equivalent level of protection for personal data transferred within the corporate group, regardless of the destination country. The approval process involves a lead supervisory authority, a cooperation procedure among concerned SAs, and typically spans 12 to 18 months from initial submission to final approval.
Art. 47(2) Content Requirements
(a) Structure and Contact Details of the Group
The BCR must specify the structure of the group of undertakings or enterprises, including the identity and contact details of each member bound by the BCR.
Athena Global Logistics implementation:
- Group parent entity: Athena Global Logistics GmbH, Friedrichstrasse 112, 10117 Berlin, Germany
- Group DPO: Elisa Brandt, elisa.brandt@athenalogistics.eu, +49 30 1234 5678
- Bound entities: All wholly-owned subsidiaries and majority-controlled affiliates listed in BCR Annex A (currently 47 entities across 31 jurisdictions)
- Structure chart: Updated annually and annexed to the BCR as Annex A, reflecting the legal entity hierarchy from the parent to each subsidiary
(b) Data Transfers Covered
The BCR must describe the data transfers or set of transfers, including the categories of personal data, the type of processing and its purposes, the type of data subjects affected, and the identification of the third country or countries.
Implementation requirements:
- Scope document specifying all intra-group transfer categories: HR data (employee records, payroll, benefits), customer data (shipment records, billing, communications), supplier data (contact details, contractual records), and operational data (vehicle tracking, warehouse access logs)
- Purpose register linking each transfer category to one or more specified purposes: employment administration, freight operations, financial reporting, regulatory compliance, IT support
- Data subject taxonomy: employees, contractors, temporary workers, customers (individual and corporate contacts), suppliers, business partners, website visitors
- Destination country register: all non-EEA jurisdictions where bound group entities operate
(c) Legally Binding Nature
The BCR must establish the legally binding nature of the rules, both internally and externally.
Implementation elements:
- Intra-group agreement signed by all bound entities, creating contractual obligations enforceable between group members
- BCR adopted as a binding corporate policy by resolution of the board of the parent company, with cascading adoption resolutions by each subsidiary board
- Employee handbook incorporation: BCR summary and compliance obligations included in all employment contracts and data handling procedures
- External enforceability: explicit third-party beneficiary clause granting data subjects the right to enforce the BCR provisions directly against any bound entity
(d) Application of the General Data Protection Principles
The BCR must demonstrate the application of all general data protection principles under Article 5, including purpose limitation, data minimisation, limited storage periods, data quality, data protection by design and by default, legal basis, special category data processing, and measures to ensure data security.
Required content:
- Purpose limitation: data transferred under the BCR may be processed only for the purposes specified in the BCR scope document; any new purpose requires a compatibility assessment under Art. 6(4) and BCR amendment procedure
- Data minimisation: transfers limited to data adequate, relevant, and necessary for the specified purpose; group-wide data classification policy mandating review of data elements before transfer
- Storage limitation: retention schedules specified per data category and jurisdiction; automated deletion or anonymisation upon expiry
- Accuracy: procedures for data subjects to request correction; data quality checks at transfer points
- Security: minimum security standards applicable to all bound entities per BCR Annex C (aligned with ISO 27001:2022)
(e) Third-Party Beneficiary Rights
Data subjects must be able to enforce the BCR as third-party beneficiaries and have the right to:
- Receive compensation for material and non-material damages resulting from BCR violations
- Lodge complaints with the competent supervisory authority
- Exercise all data subject rights (access, rectification, erasure, restriction, portability, objection) against any bound entity
(f) Acceptance of Liability
The BCR must include acceptance of liability by the entity established in the EU (the BCR Lead) for any breach committed by a non-EU bound entity, with the burden of proof on the BCR Lead to demonstrate the non-EU entity was not responsible.
Athena Global Logistics implementation:
- BCR Lead: Athena Global Logistics GmbH (Berlin)
- Liability clause: The BCR Lead accepts liability for breaches by any non-EU bound entity and agrees to take necessary action to remedy the breach and pay compensation
- Insurance: professional indemnity insurance covering BCR-related claims with a minimum coverage of EUR 10,000,000 per claim
(g) Information Provided to Data Subjects
The BCR must specify the information provided to data subjects about the BCR and their rights, including:
- The BCR and a summary in plain language published on the company website
- Information about the complaints procedure and the right to lodge a complaint with the SA
- Information about the right to seek judicial remedies
- The identity and contact details of the BCR Lead and the DPO
(h) DPO Tasks
The BCR must describe the tasks of the Data Protection Officer (or equivalent responsible person/entity), including:
- Monitoring BCR compliance across all bound entities
- Conducting or overseeing BCR audits
- Handling data subject complaints related to BCR transfers
- Serving as the contact point for supervisory authorities
- Reporting to the board on BCR compliance status
(i) Complaint Procedures
The BCR must establish a complaints mechanism enabling data subjects to:
- Submit complaints to any bound entity or the BCR Lead
- Receive a response within 30 calendar days
- Escalate unresolved complaints to the DPO, then to the competent SA
- Access mediation or arbitration as an alternative dispute resolution mechanism
(j) Compliance Verification Mechanisms
The BCR must describe mechanisms for ensuring compliance:
- Internal BCR audit programme: conducted by the internal audit function, with at least one full-cycle audit every three years covering all bound entities
- Annual compliance self-assessments by each bound entity, reported to the DPO
- Monitoring tools: data transfer logging, access reviews, policy adherence metrics
- Results reported to the BCR Lead's management and, upon request, to the competent SA
(k) Change Reporting Mechanisms
The BCR must establish reporting and recording mechanisms for changes:
- Amendment procedure: any change to the BCR requires approval by the BCR Lead, notification to the lead SA, and communication to all bound entities
- Annual update cycle for the entity list (Annex A) and security standards (Annex C)
- Material changes (new countries, new data categories, structural changes) must be notified to the SA before implementation
(l) Cooperation with the Supervisory Authority
The BCR must establish a cooperation mechanism with the SA:
- The BCR Lead will submit to the jurisdiction of the competent SA
- The BCR Lead will make audit results available to the SA upon request
- The BCR Lead will comply with SA advice regarding BCR interpretation and application
- Annual BCR compliance report submitted to the lead SA
(m) Local Law Reporting
The BCR must require any bound entity to report to the BCR Lead any legal requirement in its jurisdiction that is likely to have a substantial adverse effect on the guarantees provided by the BCR.
Implementation:
- Annual local law survey conducted by outside counsel in each jurisdiction
- Immediate escalation procedure for new legislation or government access demands that conflict with BCR commitments
- Assessment protocol: evaluate whether the local law requirement materially undermines BCR protections and, if so, notify the SA and suspend affected transfers
(n) Training
The BCR must describe appropriate data protection training for personnel with access to transferred data:
- Mandatory onboarding training for all new employees with data access
- Annual refresher training on BCR requirements, data subject rights, and breach reporting
- Role-specific training for IT administrators, HR staff, and customer-facing personnel
- Training records maintained centrally and available for SA audit
BCR Approval Process
Step 1: Preparation (Months 1-3)
- Draft the BCR document against the WP256 rev.01 referential (BCR for controllers) or WP257 rev.01 referential (BCR for processors).
- Map all intra-group data flows to identify the transfers covered by the BCR.
- Prepare the Annex A entity list, Annex B transfer scope, and Annex C security standards.
- Conduct a gap analysis against the referential checklist.
- Prepare the BCR application form for the lead SA.
Step 2: Lead SA Identification (Month 3)
- Identify the lead SA per the EDPB criteria: the SA of the Member State where the BCR Lead (typically the parent or the entity with delegated data protection responsibility) is established.
- For Athena Global Logistics: the lead SA is the Berliner Beauftragte fuer Datenschutz und Informationsfreiheit (BlnBDI).
- Identify concerned SAs: all SAs of Member States where bound entities are established.
Step 3: Formal Submission (Month 4)
- Submit the BCR application to the lead SA with all supporting documentation.
- Include: BCR text, entity list, data flow maps, gap analysis results, evidence of internal approval, DPO contact details.
Step 4: Lead SA Review (Months 4-9)
- The lead SA reviews the BCR for completeness and compliance with Art. 47(2).
- Expect multiple rounds of questions and amendments.
- Maintain a correspondence log and amendment tracker.
- Typical duration: 4-6 months of iterative review.
Step 5: Cooperation Procedure (Months 9-12)
- The lead SA circulates the reviewed BCR to all concerned SAs.
- Concerned SAs have a defined period (typically 2 months) to raise objections or comments.
- The lead SA consolidates feedback and works with the applicant to address concerns.
- If consensus is reached, the lead SA provides a positive opinion.
Step 6: Consistency Mechanism (Months 12-14)
- Under Art. 63-64 GDPR, the lead SA may submit the draft approval to the EDPB for an opinion if there are unresolved objections.
- The EDPB issues an opinion within 8 weeks (extendable by 6 weeks).
Step 7: Formal Approval (Months 14-18)
- The lead SA issues the formal BCR approval decision.
- The approval may include conditions or recommendations.
- The BCR Lead must implement any conditions before relying on the BCR for transfers.
- Publish the approved BCR summary on the EDPB BCR register and the company website.
Step 8: Implementation and Rollout (Post-Approval)
- Communicate the approved BCR to all bound entities.
- Execute the intra-group agreement binding all entities.
- Deploy the training programme.
- Activate the audit programme.
- Begin the monitoring and reporting cycle.
WP256 Rev.01 Referential (BCR for Controllers) — Key Elements Checklist
| Element | WP256 Section | Status |
|---|---|---|
| Binding nature of the BCR | Section 1 | Required |
| Scope — data, transfers, entities | Section 2 | Required |
| Application of GDPR principles | Section 3 | Required |
| Rights of data subjects and enforcement | Section 4 | Required |
| Liability and jurisdiction | Section 5 | Required |
| Cooperation duty with SAs | Section 5.4 | Required |
| How to handle requests from authorities | Section 5.5 | Required |
| Complaint handling | Section 6 | Required |
| Training programme | Section 7 | Required |
| Audit programme | Section 7 | Required |
| Network of privacy officers | Section 7.3 | Required |
| Update and change management | Section 8 | Required |
| Local law conflicts | Section 5.5 | Required |
| Description of conflict resolution | Section 6 | Required |
WP257 Rev.01 Referential (BCR for Processors) — Additional Elements
| Element | Description |
|---|---|
| Instructions-based processing | Processor BCR must confirm processing only on documented instructions |
| Sub-processor management | Procedures for sub-processor authorisation, due diligence, and contractual flow-down |
| Controller notification | Obligation to inform the controller of any inability to comply |
| Data return/deletion | Procedures upon termination of the processing relationship |
| Audit facilitation | Obligation to make available all information necessary to demonstrate compliance |
Post-Approval Ongoing Obligations
- Annual compliance audit: At least one comprehensive BCR audit per year, with each bound entity audited within a three-year rolling cycle.
- Entity list maintenance: Annex A updated whenever entities join or leave the group; SA notified of material changes.
- Incident reporting: Any breach involving BCR-covered data reported to the BCR Lead and, where required, to the competent SA per Art. 33.
- Local law monitoring: Continuous monitoring of legal developments in third countries that may affect BCR protections.
- Training records: Maintained and available for SA review at all times.
- BCR review and amendment: Full BCR review at least every three years, with interim amendments as needed for material changes.
Mapping International Data Flows
Overview
A comprehensive international data flow map is the foundational prerequisite for any cross-border transfer compliance programme. GDPR Article 30 requires controllers and processors to document transfers to third countries or international organisations. Beyond regulatory compliance, a data flow inventory enables identification of unprotected transfers, assignment of appropriate transfer mechanisms, and ongoing monitoring of data movement across jurisdictions. This skill provides a structured methodology for conducting a system-by-system data flow inventory, identifying all third-party recipients, assigning transfer mechanisms, and performing gap analysis.
Data Flow Inventory Methodology
Phase 1: System Inventory
Identify every information system, application, and service that processes personal data within the organisation.
System categories at Athena Global Logistics:
| Category | Systems | Personal Data Processed |
|---|---|---|
| Enterprise Resource Planning | SAP S/4HANA (hosted Frankfurt DC) | Employee data, customer data, supplier data, financial data |
| Transport Management | CargoWise One (SaaS, hosted Sydney) | Customer shipment data, consignee data, customs broker contacts |
| Customer Relationship Management | Salesforce (SaaS, hosted Frankfurt) | Customer contacts, communication history, sales pipeline |
| Human Resources | Workday (SaaS, hosted Dublin) | Employee personal data, payroll, benefits, performance, recruitment |
| Email and Collaboration | Microsoft 365 (SaaS, hosted EU DC) | Employee communications, contacts, calendar, file storage |
| Warehouse Management | Manhattan Associates (hosted Frankfurt DC) | Warehouse worker IDs, shift schedules, access logs |
| Fleet Management | Fleetio (SaaS, hosted US) | Driver names, licence numbers, GPS tracking data, vehicle assignments |
| Customer Portal | Custom web application (hosted Frankfurt DC) | Customer login credentials, shipment tracking, document uploads |
| Analytics Platform | Snowflake (SaaS, hosted Frankfurt) | Aggregated operational data, pseudonymised customer analytics |
| IT Service Management | ServiceNow (SaaS, hosted Amsterdam) | Employee IT tickets, contact details, device assignments |
Phase 2: Data Flow Identification
For each system, trace every flow of personal data that crosses a national border.
Data flow tracing methodology:
- Inbound flows: Where does personal data enter the system from? (user input, API integrations, file imports, email)
- Internal processing: Where is data stored and processed? (primary data centre, disaster recovery site, development/test environments)
- Outbound flows: Where does personal data leave the system to? (third-party integrations, data exports, email transmissions, backup replication)
- Sub-processor chains: For SaaS systems, identify the provider's sub-processors and their locations.
- Support access: Identify any remote support arrangements where third-country support staff may access personal data.
Athena Global Logistics example data flow register (excerpt):
| Flow ID | Source System | Source Location | Destination | Destination Country | Data Categories | Legal Basis for Processing | Transfer Mechanism |
|---|---|---|---|---|---|---|---|
| DF-001 | SAP S/4HANA | Frankfurt, DE | Athena Logistics (HK) Ltd — local SAP instance | Hong Kong SAR | Customer names, addresses, consignment data | Art. 6(1)(b) contract | SCCs Module 1 |
| DF-002 | CargoWise One | Sydney, AU | Athena Global Logistics GmbH — API pull | Australia | Shipment status, consignee details | Art. 6(1)(b) contract | EU adequacy decision (implied — no decision for AU; SCCs Module 2 required) |
| DF-003 | Workday | Dublin, IE | Workday Inc sub-processor (US backup DC) | United States | Employee HR data | Art. 6(1)(b) employment contract | EU-US DPF + SCCs backup |
| DF-004 | Fleetio | Atlanta, US | N/A (primary processing in US) | United States | Driver names, licence numbers, GPS data | Art. 6(1)(f) legitimate interest | EU-US DPF (verify certification) |
| DF-005 | SAP S/4HANA | Frankfurt, DE | Athena Freight Services India — SFTP batch | India | Employee data (payroll, benefits) | Art. 6(1)(b) employment contract | SCCs Module 1 |
| DF-006 | Custom portal | Frankfurt, DE | TransPacific Freight Solutions — API | Hong Kong SAR | Customer shipment data | Art. 6(1)(b) contract | SCCs Module 2 |
| DF-007 | Microsoft 365 | EU DC | Microsoft Corp sub-processors (global) | Multiple (US, SG, IE) | Employee emails, files | Art. 6(1)(b) contract | EU-US DPF (US); SCCs (SG) |
Phase 3: Third-Party Identification
Catalogue all third parties (processors, sub-processors, joint controllers, independent controllers) that receive personal data through international transfers.
| Third Party | Role | Country | Data Received | Purpose | Contract Reference |
|---|---|---|---|---|---|
| TransPacific Freight Solutions Ltd | Processor | Hong Kong SAR | Customer shipment data | Freight consolidation and customs clearance | DPA-2025-001 |
| CloudVault Asia Pte Ltd | Sub-processor (of TransPacific) | Singapore | Customer shipment data (hosting) | Cloud infrastructure | Sub-processor agreement via TransPacific |
| Pinnacle Data Services Co Ltd | Sub-processor (of TransPacific) | Thailand | Customs documentation data | Data entry and validation | Sub-processor agreement via TransPacific |
| Athena Freight Services India Pvt Ltd | Controller (intra-group) | India | Employee HR data | Local employment administration | Intra-group DPA-2024-005 |
| Workday Inc | Processor | Ireland (primary), US (backup) | Employee HR data | HRIS platform | DPA-WD-2024-001 |
| Fleetio Inc | Processor | United States | Driver data | Fleet management | DPA-FL-2024-003 |
| Microsoft Corporation | Processor | EU, US, Singapore | Employee email and files | Email and collaboration | DPA-MS-2024-001 |
Phase 4: Transfer Mechanism Assignment
For each identified international data flow, assign the appropriate transfer mechanism:
For each flow:
1. Check: Does the destination have an EU adequacy decision?
→ YES: Record "Adequacy Decision" as mechanism. Done.
→ NO: Continue.
2. Check: Is the importer DPF-certified (for US transfers)?
→ YES: Record "EU-US DPF" as mechanism. Recommend SCCs as backup.
→ NO: Continue.
3. Check: Are SCCs in place between the parties?
→ YES: Record "SCCs Module X" as mechanism. Verify TIA completed.
→ NO: Continue.
4. Check: Are BCRs in place covering the transfer?
→ YES: Record "BCRs" as mechanism. Verify scope covers the data.
→ NO: Continue.
5. Check: Does an Art. 49 derogation apply?
→ YES: Record "Art. 49(1)(x)" as mechanism. Document justification.
→ NO: FLAG AS UNPROTECTED TRANSFER — immediate action required.
Phase 5: Gap Analysis
Identify transfers that lack a valid transfer mechanism:
| Gap Type | Description | Priority | Remediation |
|---|---|---|---|
| No mechanism | Transfer occurring without any Art. 45/46/49 basis | Critical | Suspend transfer or execute SCCs within 30 days |
| Expired mechanism | SCCs based on superseded 2010/2021 versions; DPF certification expired | High | Renew mechanism within 60 days |
| Missing TIA | SCCs in place but no documented TIA | High | Complete TIA within 30 days |
| Incomplete documentation | Mechanism exists but Annex fields are incomplete | Medium | Complete documentation within 60 days |
| Sub-processor gap | Importer uses sub-processors not covered by SCCs | High | Extend SCC coverage or require importer to execute Module 3 SCCs |
| Undiscovered flow | Data flow identified during mapping that was not previously known | High | Assess, assign mechanism, and document within 30 days |
Data Flow Visualisation
Visualisation Approaches
-
Geo-map visualisation: Plot data flows on a world map with colour-coded lines:
- Green: Transfer covered by adequacy decision
- Blue: Transfer covered by SCCs/BCRs with completed TIA
- Yellow: Transfer covered by mechanism but TIA pending or in review
- Red: Transfer lacking valid mechanism — immediate action required
-
System-centric diagram: For each major system, draw a diagram showing all inbound and outbound data flows with destination countries and mechanisms.
-
Third-party relationship map: Network diagram showing the organisation at the centre with all third parties and data flows radiating outward, grouped by jurisdiction.
-
Transfer register dashboard: Tabular view with filtering by mechanism type, destination country, risk level, and review status.
Ongoing Maintenance
- Trigger-based updates: Re-map data flows upon: new system implementation, new vendor onboarding, corporate restructuring, new country operations, new data categories.
- Periodic review: Full data flow inventory review at least annually.
- Automated discovery: Implement network monitoring and data loss prevention (DLP) tools to detect undocumented cross-border data flows.
- Integration with RoPA: Data flow map feeds directly into the Art. 30 Records of Processing Activities.
- Integration with vendor register: Third-party data recipients map feeds into the vendor management and DPA tracking system.
Implementing Data Localization Requirements
Overview
Data localization laws require that personal data of a country's residents be stored, processed, or both within the territory of that country. These requirements exist independently of and in addition to transfer mechanism requirements under the GDPR. Organisations operating globally must map their data localization obligations by jurisdiction, design infrastructure architectures that comply with local storage mandates, and implement exemption procedures where cross-border transfer is permitted subject to conditions.
Country-Specific Requirements
Russia — Federal Law No. 242-FZ (Amendments to Federal Law No. 152-FZ)
Effective: 1 September 2015
Key requirements:
- Art. 18(5) of Federal Law 152-FZ (as amended by 242-FZ): When collecting personal data, including via the internet, the data operator must ensure that recording, systematisation, accumulation, storage, modification, extraction, and retrieval of personal data of citizens of the Russian Federation are carried out using databases located in the territory of the Russian Federation.
- The law applies to any organisation collecting personal data of Russian citizens, regardless of the organisation's location.
- Cross-border transfer is permitted after initial localization — the primary database must be in Russia, but copies may be transferred abroad subject to Federal Law 152-FZ cross-border transfer rules.
Enforcement:
- Roskomnadzor (Federal Service for Supervision of Communications) is the enforcement authority.
- Non-compliance can result in website blocking within Russia, fines (up to RUB 18 million for repeated violations under 2023 amendments), and criminal liability for certain violations.
- LinkedIn was blocked in Russia in 2016 for non-compliance with 242-FZ.
Athena Global Logistics implementation:
- Primary HR database for Russian employees hosted on servers in Moscow (OVHcloud Russia data centre, Bolshaya Nikitskaya 22).
- Customer data from Russian-origin shipments stored primarily in Moscow before replication to the Frankfurt analytics platform.
- Cross-border transfers from Moscow to Frankfurt covered by Russia's cross-border transfer rules (adequate countries list per Roskomnadzor Order No. 274 or consent of the data subject).
China — PIPL Art. 40 and CAC Measures
Personal Information Protection Law (PIPL) — Effective 1 November 2021
Key requirements:
- Art. 40: Critical Information Infrastructure Operators (CIIOs) and personal information processors handling personal information reaching the volume threshold specified by the Cyberspace Administration of China (CAC) must store personal information collected and generated within the territory of China domestically. Cross-border transfers require a CAC-administered security assessment.
- CAC Measures on Security Assessment of Outbound Data Transfers (effective 1 September 2022):
- Security assessment mandatory for: (a) CIIOs; (b) processors handling personal information of over 1 million individuals; (c) processors that have cumulatively transferred personal information of over 100,000 individuals or sensitive personal information of over 10,000 individuals since 1 January of the preceding year.
- Assessment conducted by the provincial-level CAC and reviewed by the national CAC.
- Assessment valid for 2 years; must be re-conducted before expiry or upon material change.
- CAC Standard Contract Measures (effective 1 June 2023): Personal information processors not subject to the mandatory security assessment may use the CAC-published Standard Contract for cross-border transfers, filed with the provincial CAC within 10 working days of execution.
- PRC Data Security Law (DSL) Art. 31: Important data collected and generated by CIIOs must be stored domestically.
Athena Global Logistics implementation:
- China operations process personal information of approximately 15,000 individuals (below the 1 million threshold for mandatory security assessment).
- Localization: Chinese customer and employee data stored on Alibaba Cloud servers in the Shanghai region.
- Cross-border transfers: Athena uses the CAC Standard Contract filed with the Shanghai CAC for transfers of logistics data to the Frankfurt headquarters.
- Personal Information Impact Assessment (PIIA) completed before cross-border transfer per PIPL Art. 55.
India — Digital Personal Data Protection Act 2023 (DPDP Act)
Effective: Provisions being brought into force in phases from 2024.
Key requirements:
- Section 16(1): The Central Government may, by notification, restrict the transfer of personal data by a significant data fiduciary to any country or territory outside India.
- Section 16(2): The Central Government may prescribe conditions for cross-border transfer to specific countries.
- Blacklist approach: India adopts a "blacklist" model — transfers are permitted to all countries except those specifically restricted by government notification. As of March 2026, no blacklist notifications have been issued.
- Significant Data Fiduciary (SDF): Designation by the Central Government based on volume of data, sensitivity, risk to data principals, and other factors. SDFs face heightened obligations including mandatory DPO appointment and data protection audit.
- RBI data localization: The Reserve Bank of India mandates that payment system data be stored exclusively in India (RBI Circular DPSS.CO.OD.No.2785, April 2018). This applies to all payment data processed by payment system operators.
Athena Global Logistics implementation:
- Indian operations data stored on AWS Mumbai region (ap-south-1).
- Cross-border transfers permitted (no blacklist notification as of March 2026) but monitored for future restrictions.
- RBI payment localization: Indian payment transaction data processed through local payment gateways with primary storage in India.
Turkey — Law No. 6698 on the Protection of Personal Data (KVKK)
Key requirements:
- Art. 9: Personal data may be transferred abroad only with the explicit consent of the data subject, or if one of the conditions in Art. 5(2) or Art. 6(3) is met and: (a) the destination country provides adequate protection (per KVKK Board list); or (b) the data controllers in Turkey and the destination country provide a written undertaking of adequate protection and the KVKK Board grants permission.
- Data Localization: No explicit data localization mandate in KVKK, but the Board Regulation on Data Transfer Abroad (2024 amendment) introduced a notification-based system requiring data controllers to apply to the Board before transferring data to countries not on the adequate list.
- Practical localization: Many organisations maintain Turkish data in Turkey due to the complexity of the Board approval process for cross-border transfers.
Vietnam — Decree 13/2023/ND-CP on Personal Data Protection
Effective: 1 July 2023
Key requirements:
- Art. 25(4): Data controllers and processors transferring personal data abroad must prepare and maintain a transfer impact assessment dossier.
- Art. 26: The transfer impact assessment dossier must be submitted to the Ministry of Public Security within 60 days of processing.
- No strict localization: Vietnam does not mandate data localization for most personal data, but the Cybersecurity Law (2018) Art. 26(3) requires storage of certain data in Vietnam for companies providing services on telecommunications networks or the internet where the data relates to national security, social order, or cybersecurity.
Indonesia — Government Regulation No. 71/2019 (GR 71)
Key requirements:
- Art. 20: Public electronic system operators must place their electronic systems and data in Indonesia for the purpose of supervision, law enforcement, data access protection, and national security.
- Art. 21: Private electronic system operators may place their systems and data outside Indonesia, provided they grant access for supervision and law enforcement.
- Practical impact: Government and public sector data must be stored in Indonesia; private sector data may be stored abroad with access provisions.
Localization Architecture Design
Pattern 1: Primary Local Storage with Replication
┌───────────────────┐ Replication ┌──────────────────┐
│ Local Data Centre │ ─────────────────→ │ Central EU DC │
│ (Country Required) │ (encrypted, │ (Frankfurt) │
│ Primary database │ compliant │ Analytics, │
│ All CRUD operations│ transfer) │ Reporting │
└───────────────────┘ └──────────────────┘
Use case: Russia (242-FZ), China (PIPL Art. 40 for CIIOs) Implementation: All create, read, update, delete operations occur on the local database. Encrypted replication to central EU systems for analytics and group reporting, subject to local cross-border transfer rules.
Pattern 2: Local Processing with Central Analytics
┌───────────────────┐ Aggregated/ ┌──────────────────┐
│ Local Instance │ Anonymised │ Central EU DC │
│ Full processing │ ─────────────────→ │ Only aggregated │
│ in-country │ │ or anonymised │
└───────────────────┘ │ data received │
└──────────────────┘
Use case: Strict localization without cross-border transfer approval (pre-CAC filing in China) Implementation: All personal data processing occurs locally; only aggregated or anonymised data (not personal data) is transferred centrally.
Pattern 3: Hybrid Cloud with Data Residency Controls
┌───────────────────┐
│ Cloud Provider │
│ Local Region │ ← Data residency policy enforced
│ (e.g., AWS Mumbai) │ via cloud service configuration
│ Personal data │
│ stored here only │
└───────────────────┘
│
│ (API access from EU for administration; no data egress)
│
┌───────────────────┐
│ Central EU DC │
│ Application logic │
│ No local PD stored │
└───────────────────┘
Use case: India (DPDP Act), Indonesia (GR 71 private sector) Implementation: Cloud provider's local region stores personal data; application logic may run centrally but personal data does not leave the local region.
Localization Compliance Checklist
| Jurisdiction | Storage Requirement | Transfer Conditions | Filing/Approval | Enforcement Authority |
|---|---|---|---|---|
| Russia | Primary DB in Russia | Permitted after localization; subject to 152-FZ transfer rules | No filing required for localization | Roskomnadzor |
| China (CIIO/threshold) | Domestic storage | CAC security assessment or Standard Contract | Security assessment filed with CAC; Standard Contract filed within 10 days | CAC |
| India | No localization (yet) | Permitted except to blacklisted countries | No filing (monitor for future requirements) | Data Protection Board of India |
| India (RBI) | Payment data in India | Not permitted for payment data | RBI compliance reporting | Reserve Bank of India |
| Turkey | No explicit localization | Board approval or adequate country list | Board application for non-adequate countries | KVKK Board |
| Vietnam | Certain data in Vietnam | Impact assessment required | Dossier to Ministry of Public Security within 60 days | Ministry of Public Security |
| Indonesia (public) | In Indonesia | Limited exceptions | No specific filing | Ministry of Communication |
| Indonesia (private) | May be abroad | Access for supervision required | No specific filing | Ministry of Communication |
Assessing the EU-US Data Privacy Framework
Overview
The European Commission adopted the adequacy decision for the EU-US Data Privacy Framework (DPF) on 10 July 2023, based on Commission Implementing Decision (EU) 2023/1795. This adequacy decision enables transfers of personal data from the EU/EEA to US organisations that have self-certified to the DPF with the US Department of Commerce (DoC), without the need for additional transfer mechanisms such as SCCs or BCRs. The DPF replaced the invalidated Privacy Shield framework and was designed to address the concerns raised by the Court of Justice in Schrems II (Case C-311/18) through the introduction of Executive Order 14086 limiting US signals intelligence activities.
DPF Adequacy Decision — Key Elements
Legal Basis
- Commission Implementing Decision (EU) 2023/1795 of 10 July 2023 pursuant to GDPR Art. 45(3)
- US Executive Order 14086 (7 October 2022) — Enhancing Safeguards for United States Signals Intelligence Activities
- Attorney General Regulation (29 June 2023) establishing the Data Protection Review Court (DPRC)
- UK Extension: The UK-US Data Bridge (effective 12 October 2023) extends DPF protections for UK-to-US transfers
Scope of Adequacy
The DPF adequacy decision applies only to transfers to US organisations that:
- Have actively self-certified to the DPF with the Department of Commerce
- Are subject to the investigatory and enforcement powers of the Federal Trade Commission (FTC) or the Department of Transportation (DoT)
- Are listed on the DPF List maintained by the DoC at dataprivacyframework.gov
The adequacy decision does not cover transfers to:
- US government agencies
- US organisations that have not self-certified
- US organisations subject to regulators other than the FTC or DoT (e.g., banks regulated by the OCC, telecommunications carriers regulated by the FCC)
Self-Certification Process
Eligibility Requirements
- The organisation must be subject to the jurisdiction of the FTC (under Section 5 of the FTC Act) or the DoT (under 49 USC).
- The organisation must commit to comply with all DPF Principles.
- The organisation must publicly disclose its DPF-compliant privacy policy.
- The organisation must identify an independent recourse mechanism for handling complaints.
- The organisation must pay the annual certification fee to the DoC.
Certification Steps
| Step | Action | Timeline |
|---|---|---|
| 1 | Review DPF Principles and assess organisational readiness | 2-4 weeks |
| 2 | Develop or update privacy policy to comply with DPF Principles | 2-3 weeks |
| 3 | Select and engage an independent recourse mechanism (IRM) | 1-2 weeks |
| 4 | Designate a contact person responsible for DPF compliance | 1 week |
| 5 | Complete the self-certification application at dataprivacyframework.gov | 1 week |
| 6 | Submit required documentation and privacy policy URL | 1 week |
| 7 | Pay annual certification fee (scaled by revenue) | Upon submission |
| 8 | DoC review and listing on the DPF List | 2-4 weeks after submission |
| 9 | Annual re-certification before expiry date | 12 months after initial certification |
Annual Certification Fee Schedule (2025)
| Organisation Annual Revenue | Fee |
|---|---|
| Up to USD 5 million | USD 0 (fee waived for small organisations) |
| USD 5 million — USD 25 million | USD 575 |
| USD 25 million — USD 500 million | USD 1,150 |
| USD 500 million — USD 5 billion | USD 2,300 |
| Over USD 5 billion | USD 3,450 |
DPF Principles
1. Notice Principle
Self-certified organisations must inform individuals about:
- The types of personal data collected
- The purposes of processing
- The right to access and correct data
- The type or identity of third parties to whom data may be disclosed
- The choices and means offered for limiting use and disclosure
- The independent recourse mechanism available
- The organisation's liability in cases of onward transfer to third parties
2. Choice Principle
Organisations must offer individuals the opportunity to opt out when personal data is:
- Disclosed to a third party (other than an agent acting on the organisation's behalf)
- Used for a purpose materially different from the purpose for which it was originally collected or subsequently authorised
For sensitive data (health, racial/ethnic origin, political opinions, religious beliefs, trade union membership, sex life, criminal record), affirmative express consent (opt-in) is required before disclosure or use for a new purpose.
3. Accountability for Onward Transfer Principle
Transfers to third-party controllers require:
- A contract stipulating the third party provides the same level of protection as the DPF Principles
- The third party notifies the organisation if it can no longer meet this obligation
Transfers to agents (processors) require:
- A contract restricting processing to specified purposes
- The agent provides the same level of protection
- The agent notifies the organisation and takes reasonable steps to stop and remediate unauthorised processing
4. Security Principle
Organisations must take reasonable and appropriate measures to protect personal data from loss, misuse, unauthorised access, disclosure, alteration, and destruction, taking into account the risks involved in processing and the nature of the data.
5. Data Integrity and Purpose Limitation Principle
Personal data must be:
- Relevant for the purposes of processing
- Reliable for its intended use
- Accurate, complete, and current
- Not processed in a way incompatible with the purposes for which it was collected or subsequently authorised
6. Access Principle
Individuals have the right to:
- Obtain confirmation of whether the organisation processes their data
- Have the data communicated to them within a reasonable time
- Challenge the accuracy of the data and have it corrected, amended, or deleted
Access may be restricted only in limited circumstances (e.g., where providing access would violate others' rights, where the burden or expense of providing access is disproportionate, or where disclosure would violate legal obligations).
7. Recourse, Enforcement, and Liability Principle
Organisations must provide:
- An accessible, independent, and affordable dispute resolution mechanism
- Procedures for verifying compliance with the DPF commitments
- Remediation of problems arising from non-compliance
- Consequences for the organisation if it fails to comply (sanctions by the FTC/DoT)
Data Protection Review Court (DPRC)
Structure
- The DPRC was established by the Attorney General Regulation of 29 June 2023 pursuant to Executive Order 14086.
- The DPRC is a two-tier review mechanism:
- First tier: Civil Liberties Protection Officer (CLPO) at the Office of the Director of National Intelligence (ODNI) reviews complaints and issues binding determinations
- Second tier: Data Protection Review Court reviews CLPO determinations upon application by the complainant or the intelligence community element
Process for EU Data Subjects
- Data subjects submit complaints to their national data protection authority (SA).
- The SA transmits the complaint to the EDPB Secretariat.
- The EDPB Secretariat forwards the complaint to the US via the designated channel.
- The CLPO investigates and determines whether a covered violation occurred.
- If a violation is found, the CLPO directs appropriate remediation.
- The complainant or the intelligence community element may apply for DPRC review.
- The DPRC appoints a special advocate to represent the complainant's interests.
- The DPRC issues a final, binding determination.
- The outcome is communicated back through the same channel to the SA and the data subject.
Key Safeguards in Executive Order 14086
| Safeguard | Description |
|---|---|
| Necessity standard | US signals intelligence collection must be necessary to advance a validated intelligence priority |
| Proportionality standard | Collection must be proportionate, balancing intelligence need against privacy impact |
| Prohibited purposes | Collection may not be conducted for suppressing dissent, disadvantaging persons based on ethnicity/race/religion, restricting freedom of the press, or gaining commercial competitive advantage |
| Bulk collection limits | Bulk collection permitted only for specific, enumerated objectives (e.g., counter-espionage, counter-terrorism); must be as tailored as feasible |
| Data retention limits | Personal data collected through signals intelligence must be deleted when no longer needed for the validated intelligence purpose |
| Binding nature | EO 14086 creates binding obligations enforceable through the DPRC |
Annual European Commission Review
The adequacy decision requires periodic review by the European Commission in cooperation with the EDPB and the European Parliament:
- First review: Conducted in 2024, published October 2024 — Commission concluded the DPF continues to ensure an adequate level of protection
- Subsequent reviews: At least every four years
- Review elements: Compliance enforcement by the FTC/DoT, DPRC functioning, implementation of EO 14086, developments in US surveillance law, FISA Section 702 reauthorization status
- Power to suspend or repeal: The Commission may suspend or repeal the adequacy decision if the level of protection is no longer adequate
Verification Checklist for EU Data Exporters
Before relying on the DPF for a transfer, the EU data exporter must verify:
| Check | Method |
|---|---|
| Importer is listed on the DPF List | Search dataprivacyframework.gov |
| Certification is active (not expired or withdrawn) | Check status and expiry date on the DPF List |
| Certification covers the relevant data categories | Review the organisation's DPF scope on the List (HR data, non-HR data, or both) |
| Importer is subject to FTC or DoT jurisdiction | Confirm regulatory jurisdiction in the DPF listing |
| Importer's privacy policy references DPF compliance | Review the published privacy policy at the URL listed |
| IRM identified | Confirm the independent recourse mechanism listed on the DPF entry |
| Data transfer falls within the scope of the adequacy decision | Confirm the transfer is to a self-certified organisation and not to a non-certified entity |
Risk Considerations and Ongoing Monitoring
Legal Stability Risks
- FISA Section 702: Reauthorised through April 2026; future legislative changes could affect the DPF adequacy assessment
- Judicial challenges: Privacy advocacy groups (notably noyb) have indicated the possibility of challenging the DPF before the CJEU, similar to the Schrems I and Schrems II proceedings
- Political risk: A change in US administration could affect the continued implementation of EO 14086
Mitigation Strategies
- Dual mechanism approach: Maintain executed SCCs as a backup mechanism for US transfers alongside DPF reliance, enabling rapid switching if the adequacy decision is suspended or invalidated.
- Monitoring programme: Track EC review outcomes, CJEU case filings, and US legislative developments.
- Contractual safeguards: Include DPF-specific termination and data return clauses in contracts with US importers, triggered by adequacy decision invalidation.
- Transfer register documentation: Record DPF as the transfer mechanism with the importer's DPF List entry date and re-certification schedule.
Implementing Standard Contractual Clauses
Overview
Commission Implementing Decision (EU) 2021/914 of 4 June 2021 introduced modernised Standard Contractual Clauses (SCCs) for the transfer of personal data to third countries under Regulation (EU) 2016/679. These SCCs replaced the prior sets adopted under Directive 95/46/EC and became the mandatory instrument from 27 December 2022. The modular architecture allows parties to select the appropriate clause set based on their roles in the transfer relationship.
Module Selection Decision Framework
Module 1: Controller to Controller (C2C)
When to use: The data exporter is a controller and the data importer independently determines the purposes and means of processing the imported data as a separate controller.
Typical scenarios at Athena Global Logistics:
- Sharing shipment tracking data with overseas partner logistics firms that independently process that data for their own route optimisation
- Providing employee data to a foreign group entity that acts as an independent controller for local employment law compliance
- Transferring customer data to an overseas insurance partner that underwrites cargo policies under its own controllership
Key Module 1 clauses:
- Clause 8.1 — Data protection safeguards: The data importer must process data only for the specific purposes described in Annex I, with an independent legal basis under the importer's applicable law
- Clause 8.2 — Purpose limitation: The importer shall not process data for purposes incompatible with those for which the data was transferred
- Clause 8.3 — Transparency: The importer must provide data subjects with a copy of the clauses and Annex I information upon request
- Clause 8.4 — Accuracy: Both parties must take reasonable steps to ensure data is accurate and up to date
- Clause 8.5 — Duration and erasure: Data processed only for the duration specified in Annex II; erasure or return upon termination
Module 2: Controller to Processor (C2P)
When to use: The data exporter is a controller and the data importer processes data on behalf of the exporter as a processor.
Typical scenarios at Athena Global Logistics:
- Engaging a cloud infrastructure provider headquartered in a third country to host the transport management system
- Using an overseas payroll processing bureau to calculate salaries for locally-hired staff
- Contracting a third-country call centre to handle customer service inquiries on behalf of the company
Key Module 2 clauses:
- Clause 8.1 — Instructions: The processor shall process data only on documented instructions from the controller as specified in Annex II
- Clause 8.2 — Purpose limitation: Processing solely for the specific purposes set out in Annex I
- Clause 8.3 — Transparency: Controller must inform data subjects of the transfer and identity of the importer
- Clause 8.5 — Sub-processing: Sub-processors only with prior specific or general written authorisation; same data protection obligations imposed by contract
- Clause 8.6 — International onward transfers: Sub-processor transfers require the same level of protection
- Clause 8.8 — Security: Technical and organisational measures as described in Annex II
- Clause 8.9 — Documentation and compliance: Processor must maintain records and allow audits
Module 3: Processor to Processor (P2P)
When to use: The data exporter is a processor (acting on behalf of an EU controller) and the data importer is a sub-processor.
Typical scenarios at Athena Global Logistics:
- The company acts as a data processor for a European shipping consortium and sub-contracts warehousing data management to a third-country sub-processor
- A managed IT services provider contracted by the company further sub-processes personal data with an offshore development centre
Key Module 3 clauses:
- Clause 8.1 — Instructions: Sub-processor processes only under the chain of instructions ultimately originating from the controller
- Clause 8.5 — Onward sub-processing: Further sub-processing only with prior specific or general written authorisation from the controller (obtained through the initial processor)
- Clause 8.8 — Security measures: Annex II security measures apply equivalently
- Clause 8.9 — Documentation and compliance: Full audit chain maintained back to the controller
Module 4: Processor to Controller (P2C)
When to use: The data exporter is a processor and the data importer is the controller whose data is being returned or transferred.
Typical scenarios at Athena Global Logistics:
- Returning processed analytics results to a non-EU client controller who originally provided the raw shipment data
- A European cloud processor returning personal data to its non-EU controller client upon contract termination
Key Module 4 clauses:
- Clause 8.1 — The importer shall process data in compliance with its obligations under the GDPR (where applicable) or equivalent standards
- Clause 8.2 — Purpose limitation and transparency obligations on the importer as controller
Module Selection Decision Tree
START: Identify the role of the data EXPORTER (EU-based party)
|
├── Exporter is a CONTROLLER
| |
| ├── Importer determines its OWN purposes → MODULE 1 (C2C)
| |
| └── Importer processes ON BEHALF of exporter → MODULE 2 (C2P)
|
└── Exporter is a PROCESSOR
|
├── Importer is a SUB-PROCESSOR → MODULE 3 (P2P)
|
└── Importer is the CONTROLLER (data return) → MODULE 4 (P2C)
Annex I: List of Parties and Transfer Details
Section A — List of Parties
| Field | Data Exporter | Data Importer |
|---|---|---|
| Name | Athena Global Logistics GmbH | TransPacific Freight Solutions Ltd |
| Address | Friedrichstrasse 112, 10117 Berlin, Germany | 88 Harbour Road, Wan Chai, Hong Kong SAR |
| Contact person | Elisa Brandt, Head of Data Protection | James Leung, Chief Privacy Officer |
| Activities relevant to transfer | International freight forwarding, customs brokerage, warehouse management for European operations | Regional freight consolidation, last-mile delivery coordination, customs clearance for Asia-Pacific operations |
| Role | Controller | Processor (Module 2) |
Section B — Description of Transfer
| Element | Detail |
|---|---|
| Categories of data subjects | Shipping customers (consignors and consignees), employees of customer companies, customs brokers, warehouse workers |
| Categories of personal data | Full name, business email, business phone number, company name, shipping address, customs identification numbers, consignment reference numbers, delivery scheduling preferences |
| Sensitive data | None transferred under this agreement |
| Frequency of transfer | Continuous real-time transfer via API integration; batch file transfer daily at 02:00 UTC |
| Nature of processing | Storage, retrieval, matching of consignment records, generation of customs documentation, delivery status tracking, exception reporting |
| Purpose of transfer | Fulfilment of freight forwarding contracts requiring regional processing of shipment data for customs clearance and last-mile delivery in Asia-Pacific jurisdictions |
| Retention period | 36 months from completion of the relevant shipment, after which data is securely deleted in accordance with Annex III procedures |
Section C — Competent Supervisory Authority
The competent supervisory authority is the Berliner Beauftragte für Datenschutz und Informationsfreiheit (BlnBDI), identified in accordance with Clause 13 as the supervisory authority of the Member State in which the data exporter is established.
Annex II: Technical and Organisational Measures
| Measure Category | Specific Measures Implemented |
|---|---|
| Encryption of data in transit | TLS 1.3 for all API communications; SFTP with AES-256 encryption for batch transfers |
| Encryption of data at rest | AES-256 encryption on all database storage volumes; encrypted backup tapes with separate key management |
| Access control | Role-based access control (RBAC) with least-privilege principle; multi-factor authentication for all administrative access; quarterly access reviews |
| Data minimisation | API payloads stripped of fields not required for the specific processing purpose; data masking applied to non-essential personal identifiers in development and testing environments |
| Logging and monitoring | Centralised SIEM with 12-month log retention; real-time alerting on anomalous access patterns; daily log review by security operations centre |
| Incident response | Documented incident response plan with 24-hour initial assessment SLA; notification to data exporter within 48 hours of confirmed breach; annual tabletop exercises |
| Physical security | ISO 27001-certified data centres; biometric access controls; 24/7 CCTV surveillance; clean desk policy in processing areas |
| Business continuity | RPO of 4 hours and RTO of 8 hours; geographically separated disaster recovery site; annual DR testing with documented results |
| Staff measures | Mandatory data protection training upon onboarding and annually thereafter; background checks for all staff with access to personal data; confidentiality agreements |
| Sub-processor management | Due diligence assessment before engagement; contractual flow-down of equivalent security obligations; annual audit of sub-processor compliance |
Annex III: List of Sub-Processors
| Sub-Processor | Location | Processing Activity | Safeguard Mechanism |
|---|---|---|---|
| CloudVault Asia Pte Ltd | Singapore | Cloud infrastructure hosting for the regional freight management platform | SCCs Module 3 (P2P) executed 15 March 2025 |
| Pinnacle Data Services Co Ltd | Bangkok, Thailand | Data entry and validation for customs documentation | SCCs Module 3 (P2P) executed 22 January 2025 |
Clause-by-Clause Implementation Checklist
Section I — General Clauses (All Modules)
| Clause | Subject | Implementation Action |
|---|---|---|
| Clause 1 | Purpose and scope | Confirm selected module is recorded in the preamble; verify parties have initialled the correct module |
| Clause 2 | Effect and invariability | Verify no modifications to the standard text; confirm any additional safeguards are in a separate addendum, not in the SCC body |
| Clause 3 | Third-party beneficiaries | Confirm data subjects can enforce Clauses 1-3, 8, 9, 12, 15-17 as third-party beneficiaries |
| Clause 4 | Interpretation | Confirm interpretation aligned with GDPR; terms have the same meaning as in the Regulation |
| Clause 5 | Hierarchy | Verify that in case of contradiction, the SCCs prevail over other contractual arrangements |
| Clause 6 | Description of transfer | Verify Annex I.B is complete with all required elements |
| Clause 7 | Docking clause | Determine if additional parties will accede; if so, prepare Annex I.A amendment procedure |
Section II — Obligations of the Parties
| Clause | Subject | Implementation Action |
|---|---|---|
| Clause 8 | Data protection safeguards | Module-specific; verify all sub-clauses completed per selected module |
| Clause 9 | Use of sub-processors | Module 2/3: Document prior authorisation mechanism (specific or general); maintain sub-processor list; establish notification procedure for changes |
| Clause 10 | Data subject rights | Establish procedure for the importer to handle data subject requests; define response timelines (within 30 days per GDPR Art. 12(3)) |
| Clause 11 | Redress | Confirm independent dispute resolution body identified; verify importer will accept jurisdiction of competent courts |
| Clause 12 | Liability | Confirm liability allocation between parties; verify insurance or financial capacity to meet potential claims |
Section III — Local Laws and Government Access
| Clause | Subject | Implementation Action |
|---|---|---|
| Clause 14 | Local laws affecting compliance | Document the Transfer Impact Assessment results; identify specific laws in the importer's jurisdiction that may impinge on SCC protections |
| Clause 15 | Government access obligations | Importer must notify exporter of government access requests (unless legally prohibited); importer must challenge disproportionate requests; importer must provide transparency report |
Section IV — Final Provisions
| Clause | Subject | Implementation Action |
|---|---|---|
| Clause 16 | Non-compliance and termination | Establish escalation procedure: notification → 30-day cure period → suspension → termination; data return or deletion upon termination |
| Clause 17 | Governing law | Select law of the EU Member State of the exporter (Germany, for Athena Global Logistics) |
| Clause 18 | Choice of forum and jurisdiction | Select courts of the EU Member State of the exporter (Berlin, Germany) |
SCC Execution and Record-Keeping
- Version control: Maintain a register of all executed SCCs with version numbers, execution dates, parties, and selected modules.
- Periodic review: Review all executed SCCs at least annually or upon any material change in processing, importer jurisdiction law, or sub-processor arrangements.
- Regulatory updates: Monitor EDPB guidance and European Commission updates for any revision to the SCC instrument or supplementary guidance.
- Integration with TIA: Each SCC must reference the corresponding Transfer Impact Assessment documenting the assessment of the importer's jurisdiction under Clause 14.
- Supervisory authority cooperation: Maintain readiness to provide all SCC documentation to the competent supervisory authority upon request under Art. 46(2)(c) and Art. 58(1).
Implementing Supplementary Measures
Overview
EDPB Recommendations 01/2020 (Version 2.0, adopted 18 June 2021) establish that where a Transfer Impact Assessment reveals protection gaps in the destination country's legal framework, supplementary measures must be adopted to bring the level of protection up to the EU standard of essential equivalence. These measures fall into three categories: technical, contractual, and organisational. The measures must be effective in practice — not merely theoretical — and their effectiveness must be reassessed at appropriate intervals.
Technical Supplementary Measures
Measure T1: End-to-End Encryption with EU-Held Keys
Description: Personal data is encrypted before leaving the EU/EEA using strong encryption algorithms, with decryption keys held exclusively by the data exporter or a trusted entity within the EU/EEA. The data importer in the third country receives and stores only ciphertext.
Technical specification at Athena Global Logistics:
- Algorithm: AES-256-GCM for data at rest; ChaCha20-Poly1305 as alternative for streaming data
- Key management: AWS KMS with Customer Managed Keys (CMK) hosted in the eu-central-1 (Frankfurt) region; keys never exported outside EEA
- Key rotation: Automatic rotation every 365 days; immediate rotation upon suspected compromise
- Certificate management: X.509 certificates issued by the internal PKI hosted in Berlin; certificate pinning for API endpoints
- Implementation: Application-layer encryption performed by the exporter's middleware before data is transmitted to the importer
Effectiveness: High — the third-country government cannot compel the importer to produce plaintext data because the importer does not possess the decryption keys. This measure is effective against compelled disclosure at rest and in transit.
Limitation: Only applicable where the importer does not need to process the data in plaintext. If the importer must read, analyse, or transform the data, this measure alone is insufficient.
Applicable scenario: Backup storage, archival, and transit-only scenarios where the importer serves as a conduit or storage provider.
Measure T2: Pseudonymisation with EU-Held Mapping Table
Description: Directly identifying personal data elements are replaced with pseudonymous identifiers before transfer. The mapping table linking pseudonyms to real identities is held exclusively by the data exporter within the EU/EEA.
Technical specification at Athena Global Logistics:
- Pseudonymisation method: HMAC-SHA256 with a secret key held in the Berlin key vault; applied to: customer names, email addresses, phone numbers, and customs identification numbers
- Mapping table: Stored in a dedicated PostgreSQL instance in the Frankfurt data centre; access restricted to the data protection team (4 authorised users)
- Transfer payload: Pseudonymised dataset retains consignment references, shipping addresses (generalised to city level), and delivery dates — sufficient for the importer to perform logistics operations
- Re-identification: Only possible by the exporter using the secret HMAC key and mapping table
Effectiveness: High — the transferred dataset cannot be attributed to identified natural persons by the importer or any third party (including government authorities) without access to the mapping table.
Limitation: Requires that the importer can fulfil its processing purpose without accessing the original identifying data. Not suitable where the importer must contact data subjects directly or produce documentation bearing real names.
Measure T3: Split Processing
Description: The processing operation is divided such that no single entity in the third country holds the complete dataset. Each fragment, viewed in isolation, does not constitute personal data or cannot be attributed to an identified individual.
Technical specification at Athena Global Logistics:
- Architecture: Two-party split where customer identity data (names, contact details) remains in the Frankfurt data centre and only operational data (consignment IDs, routing codes, timestamps) is transferred to the Hong Kong processing centre
- Linkage prevention: The transferred dataset uses internal reference codes that are meaningful only when joined with the identity dataset held in Frankfurt
- Recombination: Performed only within the EU/EEA environment by the exporter's analytics platform
Effectiveness: High — neither the importer nor the destination country government can reconstruct the full personal dataset from the transferred fragment alone.
Limitation: Requires significant architectural investment and may reduce the importer's processing efficiency. Applicable only where the processing can be meaningfully divided.
Measure T4: Transport-Layer Encryption
Description: All data transfers are protected by transport-layer security (TLS 1.3 or equivalent) to prevent interception in transit.
Technical specification at Athena Global Logistics:
- Protocol: TLS 1.3 mandatory for all API endpoints; SFTP with AES-256 for batch file transfers
- Cipher suites: TLS_AES_256_GCM_SHA384, TLS_CHACHA20_POLY1305_SHA256 (weak cipher suites disabled)
- Certificate validation: Mutual TLS (mTLS) authentication between exporter and importer systems
- HSTS: HTTP Strict Transport Security with max-age=31536000, includeSubDomains
Effectiveness: Medium — protects data against interception in transit by third parties but does not protect against compelled disclosure of data at rest by the importer or government authorities accessing the importer's systems.
Applicable as: Baseline measure for all transfers, combined with other measures for comprehensive protection.
Measure T5: Anonymisation Before Transfer
Description: Personal data is irreversibly anonymised before transfer, rendering the transferred dataset outside the scope of the GDPR (Recital 26).
Technical specification at Athena Global Logistics:
- Technique: k-anonymity (k=5) combined with l-diversity applied to aggregated shipment analytics data
- Generalisation: Geographic data generalised to country level; dates generalised to month; volumes aggregated to weekly totals
- Singling-out test: Conducted per WP29 Opinion 05/2014 on Anonymisation Techniques to verify no individual can be singled out, linked, or inferred from the anonymised dataset
Effectiveness: Complete — anonymised data is not personal data and Chapter V transfer rules do not apply. However, the utility of the data for the importer may be significantly reduced.
Contractual Supplementary Measures
Measure C1: Obligation to Challenge Government Access Requests
Contractual clause: The data importer undertakes to challenge any government access request that: (a) is disproportionate to the stated legal objective; (b) exceeds the scope authorised by the applicable legislation; (c) is incompatible with the protections afforded by the SCCs. The importer shall exhaust all available legal remedies before disclosing any data in response to a government request.
Implementation at Athena Global Logistics: Included as Clause 3.1 of the SCC Supplementary Measures Addendum executed with TransPacific Freight Solutions Ltd on 15 March 2025.
Measure C2: Transparency Obligation for Government Access
Contractual clause: The data importer shall notify the data exporter within 48 hours of receiving any government access request relating to transferred personal data. Where local law prohibits notification, the importer shall use best efforts to obtain a waiver of the prohibition and shall, at minimum, provide aggregated statistical information about government requests received on an annual basis.
Implementation: Included as Clause 3.2 of the SCC Supplementary Measures Addendum. Additionally, TransPacific Freight Solutions publishes an annual transparency report covering all government data access requests by jurisdiction and legal basis.
Measure C3: Audit Rights
Contractual clause: The data exporter or its designated independent auditor has the right to conduct on-site or remote audits of the data importer's data processing facilities, systems, and records at least once during each 12-month period, with 30 days' prior written notice. The importer shall cooperate fully with the audit and provide access to all relevant personnel, systems, and documentation.
Implementation: Included in SCC Clause 8.9 and supplemented by Clause 3.3 of the Addendum specifying the audit scope, methodology, and reporting requirements.
Measure C4: Warrant Canary
Contractual clause: The data importer shall publish a monthly statement confirming that, during the preceding month, it has not received any government order that would require the disclosure of transferred personal data under circumstances that would prevent notification to the data exporter. The absence of such a statement shall serve as notice to the exporter.
Implementation: TransPacific Freight Solutions publishes the warrant canary statement on the 5th business day of each month on a dedicated page of its corporate website accessible to Athena Global Logistics.
Measure C5: Data Localisation Commitment
Contractual clause: The data importer shall not transfer, store, or process the transferred personal data in any jurisdiction other than the agreed destination country (Hong Kong SAR) without the prior written consent of the data exporter. Sub-processor processing in other jurisdictions requires execution of separate SCCs or equivalent safeguards.
Implementation: Included as Clause 3.5 of the Addendum; enforced through technical controls restricting data replication to the Hong Kong data centre only.
Organisational Supplementary Measures
Measure O1: Internal Access Policies
Description: The data importer implements strict role-based access controls limiting data access to the minimum number of named personnel with a documented business need.
Implementation at TransPacific Freight Solutions:
- 12 named employees authorised to access transferred personal data
- Access justified by individual role description and approved by the Privacy Officer
- Quarterly access reviews conducted; access revoked within 24 hours upon role change
- Access logs retained for 24 months and available to the exporter upon request
Measure O2: Transparency Reports
Description: The data importer publishes periodic transparency reports detailing the number and nature of government data access requests received, to the extent permitted by local law.
Implementation: Annual transparency report published in Q1 covering the preceding calendar year. Report includes: number of requests by jurisdiction, legal basis cited, data categories requested, and outcome (full disclosure, partial disclosure, challenge, withdrawal).
Measure O3: ISO 27001/27701 Certification
Description: The data importer obtains and maintains independent certification against ISO 27001:2022 (information security) and ISO 27701:2019 (privacy information management), providing third-party verification that technical and organisational measures meet international standards.
Implementation: TransPacific Freight Solutions certified to ISO 27001:2022 (certificate valid to 31 December 2026) and ISO 27701:2019 (certificate valid to 31 December 2026). Surveillance audits conducted annually by TUV Rheinland.
Measure O4: Incident Escalation Protocol
Description: Documented procedure for the importer to escalate data protection incidents, including government access events, to the exporter within defined timeframes.
Implementation:
- Government access request received: Notify exporter within 48 hours (or immediately if disclosure is imminent)
- Data breach involving transferred data: Notify exporter within 24 hours per SCC Clause 8.6
- Employee misconduct involving data access: Notify exporter within 72 hours
- Escalation chain: Importer Privacy Officer → Exporter DPO → Exporter Legal Counsel → Exporter Board (if material)
Effectiveness Assessment Matrix
| Measure | Technical Risk Addressed | Effectiveness Against Compelled Disclosure | Effectiveness Against Bulk Surveillance | Residual Risk |
|---|---|---|---|---|
| T1 — E2E encryption with EU keys | Data at rest and in transit | High | High | None if keys remain in EU |
| T2 — Pseudonymisation | Re-identification | High | High | Low — sophisticated attacks may enable re-identification through auxiliary data |
| T3 — Split processing | Complete dataset exposure | High | High | Low — requires careful architecture to prevent fragment recombination |
| T4 — TLS 1.3 | Transit interception | High (transit only) | Medium | Medium — does not protect at rest |
| T5 — Anonymisation | All — data is no longer personal | Complete | Complete | None — but utility is reduced |
| C1 — Challenge obligation | Disproportionate requests | Medium | Low | Medium — effectiveness depends on importer's legal standing and judiciary |
| C2 — Transparency | Visibility | Medium | Low | Medium — may be blocked by gag orders |
| C3 — Audit rights | Compliance verification | Medium | Low | Medium — retrospective, not preventive |
| C4 — Warrant canary | Gag order detection | Low-Medium | Low | High — indirect signal only |
| O1 — Access policies | Insider risk | Medium | Low | Medium — does not prevent compelled disclosure |
| O2 — Transparency reports | Accountability | Medium | Low | Medium — aggregate data only |
| O3 — ISO certification | Control assurance | Medium | Low | Medium — certification is point-in-time |
Selection Methodology
- Identify the specific EEG gaps from the TIA (Step 3 output).
- For each gap, identify which supplementary measure category addresses it.
- Prioritise technical measures as the first line of defence — they provide the strongest protection.
- Layer contractual measures to create legal obligations that reinforce technical protections.
- Add organisational measures to provide governance and verification.
- Assess whether the combined package of measures effectively bridges all identified gaps.
- If gaps remain unbridgeable, the transfer must not proceed.
- Document the selection rationale in the TIA record.
Conducting Transfer Impact Assessment
Overview
Following the Court of Justice of the European Union's judgment in Schrems II (Case C-311/18, 16 July 2020), organisations relying on Standard Contractual Clauses (SCCs) or other Art. 46 GDPR transfer mechanisms must conduct a Transfer Impact Assessment (TIA) to evaluate whether the legal framework of the destination country provides an essentially equivalent level of protection for personal data. The EDPB adopted Recommendations 01/2020 on measures that supplement transfer tools to ensure compliance with the EU level of protection of personal data (Version 2.0, adopted 18 June 2021), establishing a six-step methodology for this assessment.
EDPB Six-Step Methodology
Step 1: Know Your Transfers
Map all personal data transfers to third countries, identifying:
| Element | Required Information |
|---|---|
| Transfer identification | Unique reference for each transfer or set of transfers |
| Data exporter | Legal entity name, establishment, role (controller/processor) |
| Data importer | Legal entity name, establishment, role (controller/processor) |
| Transfer mechanism | SCCs (specifying module), BCRs, Art. 49 derogation |
| Data categories | Personal data types transferred, including any special categories |
| Data subjects | Categories of individuals whose data is transferred |
| Purpose | Specific purpose(s) for which the data is processed after transfer |
| Destination country | Country where the importer processes the data |
| Onward transfers | Any further transfers from the importer to other jurisdictions |
| Format and channel | How data is transmitted (API, SFTP, email, physical media) |
| Storage duration | How long data is retained in the destination country |
Athena Global Logistics example transfer mapping:
| Transfer Ref | Exporter | Importer | Destination | Mechanism | Data Categories |
|---|---|---|---|---|---|
| TIA-2025-HK-001 | Athena Global Logistics GmbH | TransPacific Freight Solutions Ltd | Hong Kong SAR | SCCs Module 2 | Customer names, addresses, customs IDs, consignment data |
| TIA-2025-IN-001 | Athena Global Logistics GmbH | Athena Freight Services India Pvt Ltd | India | SCCs Module 1 | Employee names, contact details, performance records |
| TIA-2025-US-001 | Athena Global Logistics GmbH | Meridian Cloud Services Inc | United States | EU-US DPF + SCCs backup | Customer data, operational analytics |
Step 2: Identify the Transfer Tool Relied Upon
For each transfer, confirm the Art. 46 transfer mechanism:
- SCCs (Art. 46(2)(c)): Identify the specific module (1-4) and version (2021/914).
- BCRs (Art. 47): Confirm approval status and scope coverage.
- Ad hoc contractual clauses (Art. 46(3)(a)): Confirm SA authorisation.
- Codes of conduct (Art. 46(2)(e)): Confirm approved code and binding commitments.
- Certification mechanisms (Art. 46(2)(f)): Confirm certification status and scope.
Document the specific clauses that may be affected by the destination country legal framework, particularly:
- Clause 14 (SCCs) — local laws and obligations relating to access by public authorities
- Clause 15 (SCCs) — obligations of the data importer in case of government access
Step 3: Assess Whether the Transfer Tool Is Effective in Light of All Circumstances
This is the core of the TIA. Assess the legal framework of the destination country against the four European Essential Guarantees (EDPB Recommendations 02/2020):
Essential Guarantee 1: Processing Should Be Based on Clear, Precise, and Accessible Rules
| Assessment Question | Analysis |
|---|---|
| Is government access to personal data based on legislation? | Identify the specific statutes authorising government access (e.g., FISA Section 702, EO 12333 for US; National Security Law for Hong Kong; IT Act Section 69 for India) |
| Are the rules publicly available? | Assess whether the legislation and its implementing regulations are published and accessible |
| Is the scope of government access clearly defined? | Assess whether the legislation specifies the categories of data, persons, or situations subject to access |
| Are there exceptions or conditions for access? | Identify any limitations, thresholds, or prior authorisation requirements |
Essential Guarantee 2: Necessity and Proportionality
| Assessment Question | Analysis |
|---|---|
| Is government access limited to what is strictly necessary? | Assess whether the legislation requires a showing of necessity for each access request |
| Is the scope proportionate to the stated objective? | Evaluate whether bulk/mass surveillance is permitted or whether access must be targeted |
| Are there safeguards against abuse? | Assess minimisation requirements, purpose limitations, and retention limits for accessed data |
Essential Guarantee 3: Independent Oversight Mechanism
| Assessment Question | Analysis |
|---|---|
| Is there prior judicial or independent authorisation? | Determine whether a court or independent body must approve access requests before execution |
| Is there ongoing oversight? | Assess whether an independent body monitors government access activities |
| Are oversight bodies genuinely independent? | Evaluate the appointment, tenure, and dismissal conditions of oversight body members |
Essential Guarantee 4: Effective Remedies Available to the Individual
| Assessment Question | Analysis |
|---|---|
| Can individuals challenge government access in court? | Assess whether there is a right to judicial review of surveillance measures |
| Is there an effective notification mechanism? | Determine whether individuals are notified of surveillance (even if delayed) |
| Can individuals obtain a remedy? | Assess available remedies (compensation, data deletion, injunctive relief) |
Step 4: Adopt Supplementary Measures
If Step 3 reveals that the transfer tool is not effective on its own, identify and implement supplementary measures to bridge the protection gap:
Technical Measures
| Measure | Effectiveness | Applicable Scenarios |
|---|---|---|
| End-to-end encryption (data in transit and at rest) with EU-held keys | High — prevents importer and government access to plaintext | Data storage or transit where importer does not need to process plaintext |
| Pseudonymisation with EU-held mapping table | High — transferred data cannot be attributed to identified individuals | Analytics, research, or aggregation where identification is not needed at the importer |
| Split processing | High — no single entity in the third country holds the complete dataset | Multi-party computation or processing split between jurisdictions |
| Transport-layer encryption (TLS 1.3) | Medium — protects data in transit but not against compelled disclosure at rest | All transfers as a baseline measure; insufficient alone for high-risk jurisdictions |
Contractual Measures
| Measure | Effectiveness | Applicable Scenarios |
|---|---|---|
| Obligation to challenge disproportionate government access requests | Medium — depends on legal standing and judicial independence in destination country | All SCC-based transfers (already required under Clause 15) |
| Transparency obligation for government access requests received | Medium — provides visibility but does not prevent access | All transfers |
| Audit rights exercisable by the exporter or independent auditor | Medium — verifies compliance but is retrospective | All transfers |
| Warrant canary (commitment to publish regular transparency reports) | Low-Medium — provides indirect signal but does not prevent access | US transfers where gag orders may apply |
Organisational Measures
| Measure | Effectiveness | Applicable Scenarios |
|---|---|---|
| Strict internal access policies limiting who can access transferred data | Medium — reduces the surface of potential government access | All transfers |
| Regular transparency reports on government access requests | Medium — provides accountability | All transfers |
| Data protection impact assessment for government access scenarios | Medium — proactive risk identification | High-risk jurisdiction transfers |
| Adoption of ISO 27001/27701 certification by the importer | Medium — independent verification of security and privacy controls | All transfers |
Step 5: Procedural Steps If Supplementary Measures Are Adopted
- Document the supplementary measures in the SCC Annex or in a separate addendum.
- Implement the technical measures before commencing or continuing the transfer.
- Execute contractual amendments reflecting the supplementary measures.
- Verify the importer has the technical capability and legal ability to implement the measures.
- Notify the competent SA if required (for ad hoc contractual clauses under Art. 46(3)(a)).
Step 6: Re-Evaluate at Appropriate Intervals
- Schedule periodic TIA reviews: at minimum annually, or upon any of the following triggers:
- New legislation enacted in the destination country affecting government access
- Court rulings in the destination country affecting privacy protections
- Changes to the EC adequacy decision landscape
- EDPB or national SA guidance updates
- Material change in the nature, volume, or sensitivity of transferred data
- Government access request received by the importer
- Document each re-evaluation with the date, trigger, findings, and any changes to supplementary measures.
- If re-evaluation concludes that effective protection cannot be ensured, suspend the transfer and notify the competent SA.
Country-Specific Assessment Summaries
United States
| Factor | Assessment |
|---|---|
| Key surveillance laws | FISA Section 702, EO 12333, CLOUD Act, National Security Letters (18 USC 2709) |
| Necessity/proportionality | EO 14086 (October 2022) introduced necessity and proportionality requirements; applies to all signals intelligence activities |
| Independent oversight | FISC (prior authorisation for Section 702); PCLOB (oversight); DPRC (redress for EU data subjects) |
| Remedies | DPRC mechanism established under EO 14086; binding determinations |
| Overall assessment | If importer is DPF-certified: adequacy decision applies. If not DPF-certified: SCCs with supplementary measures (encryption, contractual transparency) |
People's Republic of China
| Factor | Assessment |
|---|---|
| Key surveillance laws | Cybersecurity Law (Art. 28, 37), National Intelligence Law (Art. 7, 14), Data Security Law (Art. 35-36), PIPL (Art. 38-43) |
| Necessity/proportionality | National Intelligence Law Art. 7 imposes broad cooperation obligations; no explicit proportionality requirement |
| Independent oversight | No independent judicial oversight of intelligence access; procuratorate oversight is not independent from the state |
| Remedies | Limited judicial remedies for foreign data subjects against state surveillance |
| Overall assessment | High risk; supplementary measures must include strong encryption with EU-held keys; consider data minimisation and pseudonymisation before transfer; for some data categories, transfer may not be possible with effective protection |
India
| Factor | Assessment |
|---|---|
| Key surveillance laws | IT Act 2000 Section 69 (interception), Telegraph Act 1885 Section 5, DPDP Act 2023 Section 36 (government exemptions) |
| Necessity/proportionality | Section 69 requires ministerial authorisation but proportionality review is limited; mass surveillance capability through CMS (Central Monitoring System) |
| Independent oversight | No prior judicial authorisation for interception; review committee is executive-appointed |
| Remedies | Limited remedies under IT Act; High Court writ jurisdiction available but practical access is constrained |
| Overall assessment | Medium-High risk; supplementary measures should include encryption, contractual transparency, and audit rights; TIA should assess specific risk based on data category and importer profile |
Hong Kong SAR
| Factor | Assessment |
|---|---|
| Key surveillance laws | Interception of Communications and Surveillance Ordinance (Cap. 589), National Security Law (2020), Safeguarding National Security Ordinance (2024) |
| Necessity/proportionality | Cap. 589 requires judicial authorisation for interception; however, NSL provides broad powers with limited proportionality review |
| Independent oversight | Commissioner on Interception of Communications and Surveillance provides oversight under Cap. 589; NSL cases subject to designated judges |
| Remedies | Judicial review available under Cap. 589; limited practical remedies under NSL |
| Overall assessment | Medium risk (elevated since NSL enactment); supplementary measures should include encryption and contractual obligations; assess sensitivity of data and likelihood of government interest |
TIA Documentation Requirements
Each TIA must be documented and include:
- Transfer identification (Step 1 mapping data)
- Transfer mechanism details (Step 2 analysis)
- Destination country legal assessment with specific legislation citations (Step 3)
- European Essential Guarantees analysis for each identified law (Step 3)
- Supplementary measures identified and rationale (Step 4)
- Implementation status of supplementary measures (Step 5)
- Re-evaluation schedule and triggers (Step 6)
- Overall conclusion: transfer may proceed / transfer may proceed with supplementary measures / transfer must be suspended
- Sign-off by the DPO or Head of Data Protection
- Version history tracking all updates and re-evaluations
Managing Transfer Records and Documentation
Overview
Maintaining comprehensive transfer records and documentation is a foundational obligation under the GDPR and a practical necessity for demonstrating compliance with cross-border data transfer requirements. Articles 5(2) and 24 impose a general accountability obligation, while Article 30 mandates specific records of processing activities — including details of international transfers. Beyond these baseline requirements, each transfer mechanism (SCCs, BCRs, adequacy reliance, derogations) carries its own documentation expectations. This skill provides a structured approach to building, maintaining, and auditing transfer records across all mechanisms.
Transfer Register: Core Fields
Mandatory Fields per Transfer Entry
Every cross-border transfer must be documented with the following information:
| Field | Description | Legal Basis |
|---|---|---|
| Transfer ID | Unique identifier for the transfer entry | Internal governance |
| Data Exporter | Identity and contact details of the transferring entity | Art. 30(1)(a) |
| Data Importer | Identity and contact details of the receiving entity | Art. 30(1)(a) |
| Exporter Country | Country from which data is transferred | Art. 30(1)(e) |
| Importer Country | Destination country or international organisation | Art. 30(1)(e) |
| Categories of Data Subjects | Types of individuals whose data is transferred | Art. 30(1)(c) |
| Categories of Personal Data | Types of personal data transferred | Art. 30(1)(c) |
| Special Category Data | Whether Art. 9 special categories are included | Art. 9(1), Art. 30(1)(c) |
| Purpose of Transfer | Business and legal purpose for the transfer | Art. 30(1)(b) |
| Legal Basis for Processing | Lawful basis under Art. 6 (and Art. 9 if applicable) | Art. 30(1)(b) |
| Transfer Mechanism | The Chapter V mechanism relied upon | Art. 30(1)(e), Art. 46 |
| Mechanism Reference | SCC execution date, BCR approval reference, adequacy decision reference, etc. | Art. 46 |
| TIA Reference | Reference to the Transfer Impact Assessment (if applicable) | EDPB Rec. 01/2020 |
| Supplementary Measures | Technical, contractual, and organisational measures applied | EDPB Rec. 01/2020 |
| Data Retention Period | How long transferred data will be retained by the importer | Art. 30(1)(f) |
| Review Date | Next scheduled review date for the transfer | Accountability (Art. 5(2)) |
| Status | Active, Under Review, Suspended, Terminated | Internal governance |
| Risk Rating | Overall risk assessment (Low, Medium, High, Critical) | Accountability (Art. 5(2)) |
Extended Fields for Specific Mechanisms
For SCC-based transfers:
| Field | Description |
|---|---|
| SCC Module | Module 1 (C2C), 2 (C2P), 3 (P2P), or 4 (P2C) |
| SCC Execution Date | Date the SCCs were signed by both parties |
| SCC Annex I Completed | Whether the transfer description annex is completed |
| SCC Annex II Completed | Whether the technical/organisational measures annex is completed |
| SCC Annex III Completed | Whether the sub-processor list is completed (Modules 2/3) |
| Clause 7 Docking | Whether a docking clause has been used for additional parties |
For BCR-based transfers:
| Field | Description |
|---|---|
| BCR Approval Authority | Lead supervisory authority that approved the BCRs |
| BCR Approval Date | Date of BCR approval |
| BCR Version | Current version of the BCRs |
| Entity Coverage | Whether the specific entities are listed in the BCR member list |
| BCR Audit Date | Date of last BCR compliance audit |
For adequacy-based transfers:
| Field | Description |
|---|---|
| Adequacy Decision Reference | EC decision number and date |
| Adequacy Scope | Full or partial adequacy; any sector/type limitations |
| Adequacy Review Date | Date of next EC review of the adequacy decision |
| Monitoring Status | Whether developments in the destination country are being tracked |
For Art. 49 derogation-based transfers:
| Field | Description |
|---|---|
| Derogation Relied Upon | Specific Art. 49 paragraph |
| Necessity Assessment | Documentation of why the transfer is strictly necessary |
| Frequency | Whether the transfer is occasional or repetitive |
| DPA Notification | Whether the supervisory authority has been informed (Art. 49(1)(2)) |
Audit Trail Requirements
What Must Be Logged
The audit trail for transfer records must capture:
| Event Type | Details to Log | Retention |
|---|---|---|
| Transfer Created | Creator identity, creation date, all initial field values | Life of transfer + 5 years |
| Transfer Modified | Modifier identity, modification date, field changed, old value, new value | Life of transfer + 5 years |
| Mechanism Changed | Old mechanism, new mechanism, reason for change, approver | Life of transfer + 5 years |
| TIA Completed/Updated | TIA reference, assessment date, outcome, assessor | Life of transfer + 5 years |
| Review Conducted | Reviewer identity, review date, outcome, next review date | Life of transfer + 5 years |
| Transfer Suspended | Suspension date, reason, authoriser | Life of transfer + 5 years |
| Transfer Terminated | Termination date, reason, data return/deletion confirmation | Life of transfer + 5 years |
| Document Attached | Document type, filename, upload date, uploader | Life of transfer + 5 years |
| SA Inquiry Received | Inquiry reference, SA identity, date, scope | Life of transfer + 10 years |
Audit Trail Integrity
- Each audit log entry must be immutable once created
- Entries must include a timestamp (UTC) and authenticated user identity
- The audit trail must be protected against tampering (hash chains, write-once storage, or equivalent)
- Access to the audit trail must be restricted to authorised personnel (DPO, privacy counsel, internal audit)
Documentation Packages by Mechanism
SCC Documentation Package
A complete SCC documentation package for each transfer includes:
- Executed SCCs — Signed copy with all Annexes (I, II, III where applicable)
- Transfer Impact Assessment — Completed TIA per EDPB 6-step methodology
- Supplementary measures record — List of technical, contractual, and organisational measures with effectiveness assessment
- Due diligence record — Evidence of importer assessment (questionnaire responses, certifications, audit reports)
- Annex review log — Record of periodic reviews and updates to Annex content
- Sub-processor management — Current sub-processor list, notification records, objection process documentation
BCR Documentation Package
- Approved BCR text — Current version with all amendments
- BCR member list — All entities bound by the BCRs with accession dates
- Compliance audit reports — Internal and external audit reports
- Training records — Evidence of BCR training for relevant personnel
- Complaint handling log — Records of data subject complaints and resolutions
- Update log — Record of all BCR amendments with approval dates
Adequacy Documentation Package
- Adequacy decision reference — Link to the relevant EC decision
- Scope assessment — Documentation confirming the transfer falls within the adequacy scope
- Monitoring log — Evidence of monitoring developments in the destination country
- Contingency plan — Plan for transitioning to alternative mechanisms if adequacy is revoked
Art. 49 Derogation Documentation Package
- Derogation assessment — Written analysis of why the specific derogation applies
- Necessity analysis — Documentation of why no alternative mechanism is available
- Data subject information — Evidence that data subjects were informed per Art. 49(1)(e) where applicable
- DPA notification — Copy of any notification to the supervisory authority under Art. 49(1)(2)
- Transfer log — Detailed log of each individual transfer (for occasional transfers)
Supervisory Authority Expectations
Information to Produce on Request
Supervisory authorities expect organisations to produce the following within a reasonable timeframe (typically 2-4 weeks):
- Complete transfer register covering all international transfers
- Transfer mechanism documentation for any specific transfer
- TIA documentation for transfers to non-adequate countries
- Evidence of periodic reviews and updates
- Audit trail for any specific transfer entry
- Sub-processor chains for processor-based transfers
- Records of any transfer suspensions or terminations and the reasons
Common SA Findings
| Finding | Description | Remediation |
|---|---|---|
| Incomplete register | Missing transfers or incomplete fields | Conduct full inventory; populate all mandatory fields |
| Stale TIAs | TIAs not updated after significant legal developments | Establish TIA review triggers and periodic review schedule |
| Missing execution dates | SCCs without documented execution dates | Obtain signed copies with dates; implement document management |
| No review schedule | No evidence of periodic transfer reviews | Establish annual review cycle; document in governance framework |
| Inadequate audit trail | Changes to transfer records not tracked | Implement audit logging; migrate to system with built-in audit trail |
| Missing sub-processor records | Incomplete or outdated sub-processor lists | Audit sub-processor chains; update SCC Annex III |
Review and Governance Cycle
Annual Review Cycle
| Quarter | Activity |
|---|---|
| Q1 | Full transfer register review: verify all active transfers, close terminated transfers, update mechanism status |
| Q2 | TIA refresh: reassess all transfers to non-adequate countries against current legal developments |
| Q3 | Mechanism review: verify SCC execution dates, BCR compliance, adequacy decision status, derogation continuing necessity |
| Q4 | Governance review: assess documentation completeness, audit trail integrity, SA readiness, update policies |
Trigger-Based Reviews
In addition to the annual cycle, reviews must be triggered by:
- Change in destination country legislation or enforcement practice
- CJEU judgment affecting transfer mechanisms (e.g., Schrems-type ruling)
- EC adequacy decision adopted, amended, or revoked
- EDPB guidance or recommendation affecting transfer documentation
- Organisational change (new entity, acquisition, divestiture)
- Data breach involving transferred data
- Supervisory authority inquiry or investigation
Athena Global Logistics — Transfer Register Example
Active Transfers (Extract)
| Transfer ID | Exporter | Importer | Dest Country | Mechanism | TIA Ref | Review Date | Status |
|---|---|---|---|---|---|---|---|
| ATH-INT-001 | Athena GmbH (DE) | TransPacific Ltd (HK) | Hong Kong | SCCs Module 2 | TIA-2024-003 | 2025-06-30 | Active |
| ATH-INT-002 | Athena GmbH (DE) | CloudVault Pte Ltd (SG) | Singapore | SCCs Module 3 | TIA-2024-005 | 2025-06-30 | Active |
| ATH-INT-003 | Athena GmbH (DE) | Athena Japan KK (JP) | Japan | EU Adequacy (2019/419) | N/A | 2025-12-31 | Active |
| ATH-INT-004 | Athena GmbH (DE) | Athena India Pvt Ltd (IN) | India | SCCs Module 1 | TIA-2024-008 | 2025-06-30 | Active |
| ATH-INT-005 | Athena GmbH (DE) | Pinnacle TH (TH) | Thailand | SCCs Module 3 | TIA-2024-010 | 2025-06-30 | Active |
| ATH-INT-006 | Athena GmbH (DE) | Athena US Inc (US) | United States | DPF + SCCs fallback | TIA-2024-012 | 2025-06-30 | Active |
Governance Framework
- Transfer Register Owner: Elisa Brandt, Group DPO
- Review Frequency: Quarterly (full register), plus trigger-based
- Audit Trail System: GRC platform with immutable logging
- SA Response SLA: Complete documentation package within 10 business days of request
- Escalation Path: DPO → Head of Legal → Chief Privacy Officer → Board Privacy Committee
Implementing UK International Data Transfer Mechanisms
Overview
Following the UK's exit from the EU, the UK operates its own international data transfer regime under the UK GDPR (as retained and amended by the Data Protection Act 2018 and the Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019). The Information Commissioner's Office (ICO) has developed two instruments for international transfers: the International Data Transfer Agreement (IDTA), effective 21 March 2022, and the UK Addendum to the EU SCCs. The UK also maintains its own adequacy assessment framework independent of the European Commission's adequacy decisions.
UK Transfer Mechanisms
International Data Transfer Agreement (IDTA)
The IDTA is a standalone UK transfer mechanism that does not rely on the EU SCCs. It is laid before Parliament as a statutory instrument under Section 119A of the Data Protection Act 2018.
Structure:
- Part 1: Tables (completed by the parties to describe the transfer)
- Table 1: Parties and Key Contacts
- Table 2: Transfer Details (description, purpose, data categories, data subjects, frequency, retention)
- Table 3: Technical and Organisational Security Measures (TFM Clauses)
- Table 4: Extra Protection Clauses (supplementary measures addressing destination country risks)
- Part 2: Extra Protection Clauses (mandatory assessment of whether the destination country provides equivalent protection to UK GDPR)
- Part 3: Commercial Clauses (parties may add commercial terms in a linked agreement)
- Part 4: Mandatory Clauses (fixed text that cannot be amended)
Key features:
- Covers all four transfer relationship types (C2C, C2P, P2P, P2C) in a single document
- Requires a Transfer Risk Assessment (TRA) as part of Extra Protection Clauses
- Parties must review the IDTA when notified of a change affecting the transfer
- ICO retains the power to issue a revised IDTA at any time
UK Addendum to EU SCCs
The UK Addendum is an alternative to the IDTA that allows organisations already using EU SCCs (Commission Decision 2021/914) to extend those SCCs to cover UK GDPR-governed transfers by adding the Addendum.
Structure:
- Part 1: Tables
- Table 1: Parties (references EU SCC Annex I.A)
- Table 2: Selected SCCs, Modules, and Selected Clauses
- Table 3: Appendix Information (references EU SCC Annexes I-III)
- Table 4: Ending the Addendum When the Approved Addendum Changes
- Part 2: Mandatory Clauses of the Approved Addendum
- The Addendum incorporates the EU SCC text but replaces references to EU law with UK law references
When to use the Addendum vs. IDTA:
- Use the Addendum if EU SCCs are already executed and you want to extend coverage to UK transfers with minimal additional drafting
- Use the IDTA if the transfer is UK-only (no EU nexus) or if you prefer a standalone UK instrument
- Both instruments are equally valid under UK law
UK Adequacy Assessments
Countries with UK Adequacy Regulations
The UK Secretary of State has the power to make adequacy regulations under Section 17A of the Data Protection Act 2018. As of March 2026, the UK has adopted adequacy regulations for:
| Country/Territory | Regulation | Effective Date |
|---|---|---|
| EU/EEA Member States | Data Protection, Privacy and Electronic Communications (Amendments etc.) (EU Exit) Regulations 2019 | 1 January 2021 (bridging mechanism) |
| Andorra | Adequacy Regulations 2023 | 12 October 2023 |
| Argentina | Adequacy Regulations 2023 | 12 October 2023 |
| Canada (PIPEDA organisations) | Adequacy Regulations 2023 | 12 October 2023 |
| Faroe Islands | Adequacy Regulations 2023 | 12 October 2023 |
| Guernsey | Adequacy Regulations 2023 | 12 October 2023 |
| Israel | Adequacy Regulations 2023 | 12 October 2023 |
| Isle of Man | Adequacy Regulations 2023 | 12 October 2023 |
| Japan | Adequacy Regulations 2023 | 12 October 2023 |
| Jersey | Adequacy Regulations 2023 | 12 October 2023 |
| New Zealand | Adequacy Regulations 2023 | 12 October 2023 |
| South Korea | Adequacy Regulations 2024 | 2024 |
| Switzerland | Adequacy Regulations 2023 | 12 October 2023 |
| Uruguay | Adequacy Regulations 2023 | 12 October 2023 |
| United States (UK-US Data Bridge) | Adequacy Regulations 2023 | 12 October 2023 |
UK-US Data Bridge
The UK-US Data Bridge extends the DPF self-certification mechanism to UK-to-US transfers:
- US organisations self-certified to the DPF that also opt into the UK Extension are covered
- Verification: Check the DPF List at dataprivacyframework.gov and confirm the "UK Extension" is active
- Same principles and enforcement mechanisms as the EU-US DPF apply
ICO Transfer Risk Assessment (TRA)
The ICO has published a Transfer Risk Assessment tool to assist organisations in evaluating whether a transfer provides an essentially equivalent level of protection to that under UK law.
TRA Methodology
Step 1: Assess Whether a Restricted Transfer Is Taking Place
- Confirm personal data is being transferred from the UK to a country outside the UK.
- Confirm the destination country does not have UK adequacy regulations.
- Confirm no exemption under Schedule 5 of the UK GDPR applies.
Step 2: Assess the Destination Country Legal Framework
Evaluate the destination country's laws and practices against four factors:
| Factor | Assessment Questions |
|---|---|
| Respect for rule of law and human rights | Does the country have a functioning, independent judiciary? Is there an independent data protection authority? |
| Data protection legislation | Does the country have comprehensive data protection legislation? Does it provide individual rights equivalent to UK GDPR? |
| Government access to personal data | What laws authorise government access? Are there necessity and proportionality requirements? Is there independent oversight? |
| Enforcement and redress | Can individuals exercise rights against data controllers? Is there an effective complaint mechanism? Can individuals seek judicial redress? |
Step 3: Assess the Transfer-Specific Risk
| Factor | Assessment Questions |
|---|---|
| Sector and entity type | Is the importer in a sector with heightened government access risk (e.g., telecommunications)? |
| Data sensitivity | Does the transfer include special category data or data that creates higher risk if accessed? |
| Volume and frequency | Is this a one-time transfer or ongoing? What volume of data subjects is affected? |
| Importer track record | Has the importer previously received government access requests? |
| Technical protections | What technical measures are in place (encryption, pseudonymisation)? |
Step 4: Determine Whether Additional Safeguards Are Needed
Based on the assessment, determine whether the IDTA or Addendum alone provides sufficient protection, or whether Extra Protection Clauses (supplementary measures) are needed.
Step 5: Document and Review
Document the TRA results and schedule periodic reviews (at least annually or upon trigger events).
IDTA Implementation at Athena Global Logistics
Table 1: Parties
| Field | Exporter | Importer |
|---|---|---|
| Party name | Athena Logistics (UK) Ltd | TransPacific Freight Solutions Ltd |
| Contact person | David Morrison, UK Data Protection Manager | James Leung, Chief Privacy Officer |
| Address | 30 Fenchurch Street, London EC3M 3BD, United Kingdom | 88 Harbour Road, Wan Chai, Hong Kong SAR |
| Official registration | Companies House No. 12345678 | Hong Kong Companies Registry CR-987654 |
| Role | Exporter (Controller) | Importer (Processor) |
Table 2: Transfer Details
| Element | Detail |
|---|---|
| Description of transfer | Transfer of UK customer shipment data for Asia-Pacific freight consolidation and customs clearance |
| Purpose | Performance of freight forwarding services for UK-origin shipments to APAC destinations |
| Categories of data subjects | UK shipping customers (consignors), UK-based consignees, customs brokers |
| Categories of personal data | Full name, business email, phone, shipping address, customs IDs, consignment references |
| Special category data | None |
| Frequency | Continuous (real-time API); daily batch at 02:00 UTC |
| Retention | 36 months from shipment completion |
Table 3: Security Measures
Reference to the Annex II measures from the EU SCC implementation (TLS 1.3, AES-256 encryption at rest, RBAC with MFA, centralised SIEM, ISO 27001-certified facilities).
Table 4: Extra Protection Clauses
Extra Protection Clauses mirror the supplementary measures identified in TIA-2025-HK-001:
- End-to-end encryption for archived data with UK-held keys
- Contractual obligation to challenge disproportionate government requests
- 48-hour government access notification
- Annual audit rights
- Warrant canary
- Named-personnel access restriction
Dual EU-UK Transfer Management
For organisations like Athena Global Logistics that transfer data under both EU GDPR and UK GDPR, the recommended approach is:
- EU transfers: Use EU SCCs (Commission Decision 2021/914) with EU TIA
- UK transfers: Use UK Addendum to the EU SCCs (appended to the same SCC instrument)
- Combined document: A single contractual package comprising the EU SCCs + UK Addendum covers both regimes
- Separate TIAs: The EU TIA and UK TRA may reach different conclusions due to different legal standards; document both
- Register: Maintain separate transfer register entries for EU-governed and UK-governed transfers to the same importer
Sponsors
Details
- Marketplace
- mukul975/Privacy-Data-Protection-Skills
- Source
- plugins/cross-border-transfers-skills
- Author
- Mahipal
- Category
- Compliance
- License
- Apache-2.0
- Keywords
- cross-border, sccs, bcrs, transfers, adequacy
More from mukul975/Privacy-Data-Protection-Skills
All 21- data-breach-response-skillsv1.0.0
- data-classification-skillsv1.0.0
- data-retention-skillsv1.0.0
- data-subject-rights-skillsv1.0.0
- employee-privacy-skillsv1.0.0
- gdpr-compliance-skillsv1.0.0
- global-privacy-regulations-skillsv1.0.0
- healthcare-privacy-skillsv1.0.0
- privacy-audit-skillsv1.0.0
- privacy-by-design-skillsv1.0.0
- privacy-engineering-skillsv1.0.0
- privacy-impact-assessment-skillsv1.0.0
- privacy-skills-completev1.0.0
- records-of-processing-skillsv1.0.0
- us-state-privacy-skillsv1.0.0
- vendor-privacy-management-skillsv1.0.0
- ai-privacy-governance-skillsv1.0.0
- children-privacy-skillsv1.0.0
- consent-management-skillsv1.0.0
- cookie-consent-skillsv1.0.0