本文へ移動
cccskills
無料GitHub で公開

transfer-records

Guides maintenance of cross-border transfer registers, audit trails, and compliance documentation under GDPR Art. 30 and Art. 46, EDPB record-keeping guidance, and supervisory authority expectations. Keywords: transfer register, audit trail, Art. 30, Art. 46, documentation, compliance records.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md12.4 KB
  • assets/template.md6.2 KB
  • references/standards.md8.0 KB
  • references/workflows.md9.2 KB
  • scripts/process.py16.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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:

FieldDescriptionLegal Basis
Transfer IDUnique identifier for the transfer entryInternal governance
Data ExporterIdentity and contact details of the transferring entityArt. 30(1)(a)
Data ImporterIdentity and contact details of the receiving entityArt. 30(1)(a)
Exporter CountryCountry from which data is transferredArt. 30(1)(e)
Importer CountryDestination country or international organisationArt. 30(1)(e)
Categories of Data SubjectsTypes of individuals whose data is transferredArt. 30(1)(c)
Categories of Personal DataTypes of personal data transferredArt. 30(1)(c)
Special Category DataWhether Art. 9 special categories are includedArt. 9(1), Art. 30(1)(c)
Purpose of TransferBusiness and legal purpose for the transferArt. 30(1)(b)
Legal Basis for ProcessingLawful basis under Art. 6 (and Art. 9 if applicable)Art. 30(1)(b)
Transfer MechanismThe Chapter V mechanism relied uponArt. 30(1)(e), Art. 46
Mechanism ReferenceSCC execution date, BCR approval reference, adequacy decision reference, etc.Art. 46
TIA ReferenceReference to the Transfer Impact Assessment (if applicable)EDPB Rec. 01/2020
Supplementary MeasuresTechnical, contractual, and organisational measures appliedEDPB Rec. 01/2020
Data Retention PeriodHow long transferred data will be retained by the importerArt. 30(1)(f)
Review DateNext scheduled review date for the transferAccountability (Art. 5(2))
StatusActive, Under Review, Suspended, TerminatedInternal governance
Risk RatingOverall risk assessment (Low, Medium, High, Critical)Accountability (Art. 5(2))

Extended Fields for Specific Mechanisms

For SCC-based transfers:

FieldDescription
SCC ModuleModule 1 (C2C), 2 (C2P), 3 (P2P), or 4 (P2C)
SCC Execution DateDate the SCCs were signed by both parties
SCC Annex I CompletedWhether the transfer description annex is completed
SCC Annex II CompletedWhether the technical/organisational measures annex is completed
SCC Annex III CompletedWhether the sub-processor list is completed (Modules 2/3)
Clause 7 DockingWhether a docking clause has been used for additional parties

For BCR-based transfers:

FieldDescription
BCR Approval AuthorityLead supervisory authority that approved the BCRs
BCR Approval DateDate of BCR approval
BCR VersionCurrent version of the BCRs
Entity CoverageWhether the specific entities are listed in the BCR member list
BCR Audit DateDate of last BCR compliance audit

For adequacy-based transfers:

FieldDescription
Adequacy Decision ReferenceEC decision number and date
Adequacy ScopeFull or partial adequacy; any sector/type limitations
Adequacy Review DateDate of next EC review of the adequacy decision
Monitoring StatusWhether developments in the destination country are being tracked

For Art. 49 derogation-based transfers:

FieldDescription
Derogation Relied UponSpecific Art. 49 paragraph
Necessity AssessmentDocumentation of why the transfer is strictly necessary
FrequencyWhether the transfer is occasional or repetitive
DPA NotificationWhether 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 TypeDetails to LogRetention
Transfer CreatedCreator identity, creation date, all initial field valuesLife of transfer + 5 years
Transfer ModifiedModifier identity, modification date, field changed, old value, new valueLife of transfer + 5 years
Mechanism ChangedOld mechanism, new mechanism, reason for change, approverLife of transfer + 5 years
TIA Completed/UpdatedTIA reference, assessment date, outcome, assessorLife of transfer + 5 years
Review ConductedReviewer identity, review date, outcome, next review dateLife of transfer + 5 years
Transfer SuspendedSuspension date, reason, authoriserLife of transfer + 5 years
Transfer TerminatedTermination date, reason, data return/deletion confirmationLife of transfer + 5 years
Document AttachedDocument type, filename, upload date, uploaderLife of transfer + 5 years
SA Inquiry ReceivedInquiry reference, SA identity, date, scopeLife 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:

  1. Executed SCCs — Signed copy with all Annexes (I, II, III where applicable)
  2. Transfer Impact Assessment — Completed TIA per EDPB 6-step methodology
  3. Supplementary measures record — List of technical, contractual, and organisational measures with effectiveness assessment
  4. Due diligence record — Evidence of importer assessment (questionnaire responses, certifications, audit reports)
  5. Annex review log — Record of periodic reviews and updates to Annex content
  6. Sub-processor management — Current sub-processor list, notification records, objection process documentation

BCR Documentation Package

  1. Approved BCR text — Current version with all amendments
  2. BCR member list — All entities bound by the BCRs with accession dates
  3. Compliance audit reports — Internal and external audit reports
  4. Training records — Evidence of BCR training for relevant personnel
  5. Complaint handling log — Records of data subject complaints and resolutions
  6. Update log — Record of all BCR amendments with approval dates

Adequacy Documentation Package

  1. Adequacy decision reference — Link to the relevant EC decision
  2. Scope assessment — Documentation confirming the transfer falls within the adequacy scope
  3. Monitoring log — Evidence of monitoring developments in the destination country
  4. Contingency plan — Plan for transitioning to alternative mechanisms if adequacy is revoked

Art. 49 Derogation Documentation Package

  1. Derogation assessment — Written analysis of why the specific derogation applies
  2. Necessity analysis — Documentation of why no alternative mechanism is available
  3. Data subject information — Evidence that data subjects were informed per Art. 49(1)(e) where applicable
  4. DPA notification — Copy of any notification to the supervisory authority under Art. 49(1)(2)
  5. 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):

  1. Complete transfer register covering all international transfers
  2. Transfer mechanism documentation for any specific transfer
  3. TIA documentation for transfers to non-adequate countries
  4. Evidence of periodic reviews and updates
  5. Audit trail for any specific transfer entry
  6. Sub-processor chains for processor-based transfers
  7. Records of any transfer suspensions or terminations and the reasons

Common SA Findings

FindingDescriptionRemediation
Incomplete registerMissing transfers or incomplete fieldsConduct full inventory; populate all mandatory fields
Stale TIAsTIAs not updated after significant legal developmentsEstablish TIA review triggers and periodic review schedule
Missing execution datesSCCs without documented execution datesObtain signed copies with dates; implement document management
No review scheduleNo evidence of periodic transfer reviewsEstablish annual review cycle; document in governance framework
Inadequate audit trailChanges to transfer records not trackedImplement audit logging; migrate to system with built-in audit trail
Missing sub-processor recordsIncomplete or outdated sub-processor listsAudit sub-processor chains; update SCC Annex III

Review and Governance Cycle

Annual Review Cycle

QuarterActivity
Q1Full transfer register review: verify all active transfers, close terminated transfers, update mechanism status
Q2TIA refresh: reassess all transfers to non-adequate countries against current legal developments
Q3Mechanism review: verify SCC execution dates, BCR compliance, adequacy decision status, derogation continuing necessity
Q4Governance 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 IDExporterImporterDest CountryMechanismTIA RefReview DateStatus
ATH-INT-001Athena GmbH (DE)TransPacific Ltd (HK)Hong KongSCCs Module 2TIA-2024-0032025-06-30Active
ATH-INT-002Athena GmbH (DE)CloudVault Pte Ltd (SG)SingaporeSCCs Module 3TIA-2024-0052025-06-30Active
ATH-INT-003Athena GmbH (DE)Athena Japan KK (JP)JapanEU Adequacy (2019/419)N/A2025-12-31Active
ATH-INT-004Athena GmbH (DE)Athena India Pvt Ltd (IN)IndiaSCCs Module 1TIA-2024-0082025-06-30Active
ATH-INT-005Athena GmbH (DE)Pinnacle TH (TH)ThailandSCCs Module 3TIA-2024-0102025-06-30Active
ATH-INT-006Athena GmbH (DE)Athena US Inc (US)United StatesDPF + SCCs fallbackTIA-2024-0122025-06-30Active

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Implements 42 CFR Part 2 protections for substance use disorder patient records. Covers written consent requirements stricter than HIPAA, re-disclosure prohibition, court order procedures, qualified service organization agreements, and 2024 amendments aligning Part 2 with HIPAA. Keywords: 42 CFR Part 2, substance use disorder, SUD records, re-disclosure, consent, Part 2 amendments.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Preparing EU AI Act compliance documentation for high-risk AI systems. Covers Annex III classification, technical documentation under Art. 11, conformity assessment, risk management systems, and CE marking requirements. Keywords: EU AI Act, high-risk AI, Annex III, conformity assessment, CE marking.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements GDPR Art. 22 automated decision-making and AI Act Art. 14 human oversight requirements for AI systems. Covers identification of solely automated decisions, meaningful human intervention design, logic explanation mechanisms, and contestation procedures. Keywords: Art. 22, automated decision, human oversight, AI Act, profiling, contestation.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

mukul975 のスキルをすべて見る

このスキルの問題を報告する