Apac Transfers logo

Apac Transfers

Community
mukul975
apac-transfers

Guides management of cross-border data transfers under Asia-Pacific regulatory frameworks including APEC CBPR, ASEAN Model Contractual Clauses, Japan APPI supplementary rules, South Korea PIPA provisions, and Thailand/Singapore PDPA mechanisms. Keywords: APEC CBPR, ASEAN MCCs, APPI, PIPA, PDPA, APAC transfers.

Overview

Publishermukul975
RepositoryPrivacy-Data-Protection-Skills
Skill nameapac-transfers
Stars
279
Forks
59
Bundled files
4
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mukul975 on GitHub. Read the source before you install it.

Installation

Install the Apac Transfers AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git /tmp/Privacy-Data-Protection-Skills
mkdir -p .claude/skills
cp -r /tmp/Privacy-Data-Protection-Skills/plugins/cross-border-transfers-skills/skills/apac-transfers .claude/skills/apac-transfers
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Apac Transfers in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Apac Transfers on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Apac Transfers is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

PrincipleDescription
Preventing HarmRecognising the interests of the individual regarding the protection of their information
NoticeProviding clear and easily accessible statements about data practices
Collection LimitationLimiting personal information collection to that which is relevant
Uses of Personal InformationUsing personal information only for purposes fulfilling the individual's expectations or as authorised by law
ChoiceProviding individuals with choice regarding collection, use, and disclosure
Integrity of Personal InformationMaintaining the accuracy, completeness, and currency of personal information
Security SafeguardsProtecting personal information with appropriate security safeguards
Access and CorrectionProviding individuals with access to their information and the ability to correct inaccurate data
AccountabilityBeing 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

SectionContent
Clause 1Definitions aligned with ASEAN Framework on Personal Data Protection
Clause 2Obligations of the data exporter
Clause 3Obligations of the data importer
Clause 4Rights of data subjects
Clause 5Liability and indemnification
Clause 6Governing law and dispute resolution
Clause 7Termination and data return/deletion
Schedule 1Description of transfer (parties, data, purposes)
Schedule 2Technical 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:
    1. 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
    2. Adequate country: The foreign country has been recognised by the PPC as providing equivalent data protection standards (currently: EU/EEA countries and the UK)
    3. 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:
    1. Consent: The data subject's consent after being informed of the recipient, purpose, categories of data, retention period, and the right to refuse
    2. Adequacy recognition: Transfer to a country recognised by the Personal Information Protection Commission (PIPC) as having an equivalent level of protection
    3. Contractual safeguards: The recipient has provided contractual safeguards equivalent to PIPA standards
    4. 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:
    1. The destination country has adequate data protection standards as prescribed by the PDPC (Personal Data Protection Committee)
    2. Compliance with Binding Corporate Rules approved by the PDPC Office
    3. The transfer is subject to a data protection policy of the same group of business, inspected and certified by the PDPC Office
    4. The transfer is subject to contractual safeguards between the transferor and transferee
    5. 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:

  1. Contractual arrangements: Contract with the recipient obligating them to meet PDPA-equivalent standards
  2. Binding corporate rules: Intra-group policies providing equivalent protection
  3. PDPC-approved frameworks: Compliance with APEC CBPR or other PDPC-recognised certification
  4. Consent: The individual consents to the transfer after being informed of the non-comparable standard
  5. 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 → ToJapanSouth KoreaThailandSingaporeHong KongEU/EEAUnited States
JapanN/AConsent/Equivalent measuresConsent/Equivalent measuresConsent/Equivalent measuresConsent/Equivalent measuresPPC adequate countryConsent/Equivalent measures
South KoreaPIPC adequacyN/AConsent/ContractConsent/ContractConsent/ContractPIPC adequacyConsent/Contract
ThailandContract/ConsentContract/ConsentN/AContract/ConsentContract/ConsentContract/ConsentContract/Consent
SingaporePDPA contractPDPA contractPDPA contractN/APDPA contractPDPA contractPDPA contract
EU/EEAEU adequacyEU adequacySCCs + TIASCCs + TIASCCs + TIAN/ADPF / SCCs + TIA

Practical Implementation Considerations

  1. 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.
  2. Contractual harmonisation: Use a single data processing agreement with jurisdiction-specific addenda to cover GDPR, APPI, PIPA, PDPA (Thailand), and PDPA (Singapore) requirements simultaneously.
  3. Consent fatigue: Where multiple jurisdictions require consent for cross-border transfer, coordinate consent collection to avoid multiple consent requests for the same transfer chain.
  4. Monitoring burden: Each APAC jurisdiction's transfer rules evolve independently; maintain a monitoring programme covering all applicable laws.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Apac Transfers AI skill do?

Guides management of cross-border data transfers under Asia-Pacific regulatory frameworks including APEC CBPR, ASEAN Model Contractual Clauses, Japan APPI supplementary rules, South Korea PIPA provisions, and Thailand/Singapore PDPA mechanisms. Keywords: APEC CBPR, ASEAN MCCs, APPI, PIPA, PDPA, APAC transfers.

Why use Apac Transfers on TypingMind?

Because you install it once and use it with any model. Apac Transfers is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Apac Transfers in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/plugins/cross-border-transfers-skills/skills/apac-transfers. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Apac Transfers?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Apac Transfers?

As many as you like. As long as a model supports skills, you can use Apac Transfers with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Apac Transfers AI skill free?

Yes. It is published on GitHub by mukul975 under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇