Browse Skills

DPC GDPR International Transfers

    Get Started with This Skill

    Overview

    International data transfers (Art. 44–50) for DPC self-assessment: adequacy, SCCs, documentation, and transparency to data subjects.

    Getting Started

    Add your source materials to the project workspace, then activate the DPC GDPR International Transfers skill. The agent will guide you through the process step by step.

    Example conversation

    You: We use a US CRM and an Indian support team. We need to document every transfer outside the EEA and add the right wording to our privacy notice.

    Agent: I’ll build a transfer record from the DPC checklist: for each flow—recipient, country, data categories, purpose, and legal basis (adequacy decision or SCCs/other safeguards). I’ll flag any special-category data. Then I’ll draft a short, plain-language transparency paragraph for your privacy notice so data subjects are informed about international transfers as required by the DPC checklist and Art. 13/14.

    Output excerpt

    Transfer record (excerpt)

    RecipientCountryDataPurposeLegal basis
    [CRM provider]USAContact details, deal historySales, supportSCCs (EU 2021/914 Module 2)
    [Support partner]IndiaName, email, ticket contentSupportSCCs; supplementary measures documented

    Transparency wording (for privacy notice)

    We transfer some of your data outside the European Economic Area (EEA), for example to our CRM and support providers in the USA and India. We do so only where the European Commission has recognised an adequate level of protection or we use approved safeguards (such as standard contractual clauses) and ensure your data remains protected.

    Extension and validation

    This skill does not include custom validation tools. Elaboration is guided by the skill workflow and reference materials. You can add tools in extension.ts later (e.g. to check required sections or checklist coverage) if you want automated validation.

    Ready to let your expertise drive the workflow?

    Stop wrestling with rigid templates and complex tooling. Write your process in markdown, let the agent handle the rest.

    Get Started