An LGPD international transfer needs two separate answers: why the processing is lawful under Article 7 or 11 and which Article 33 transfer mechanism permits the cross-border flow.
Remote access, onward transfers, and processor chains can matter. Server location alone does not describe the full transfer.
Map the real flow from to under Brazil's Lei Geral de Proteção de Dados Pessoais (LGPD), Law 13.709/2018, and Resolution 19/2024 from the Agência Nacional de Proteção de Dados (ANPD). A transfer occurs when an exporter transfers personal data to an importer in a foreign country or international organisation. International collection directly from the person is not itself a transfer, although the LGPD can still apply under Article 3. For a transfer, document both the Article 7 or 11 processing basis and the Article 33 mechanism.
1
Section 1
What should teams decide about International Transfers under the Brazil LGPD?
First identify the , , controller and operators, countries, purposes, data, people, storage, remote access, and onward transfers. The exporter is the processing agent that sends, shares, or gives access to the data; the importer is the processing agent in a foreign country or international organisation that receives it. Confirm that the operation is an and that Brazilian data-protection law applies.
Then select an Article 33 mechanism. Common routes are an ANPD or the ANPD standard contractual clauses. Specific contractual clauses and global corporate rules require prior ANPD approval. Other Article 33 routes remain available only when their case-specific conditions are met.
Resolution 32/2026 covers all EU Member States, Iceland, Liechtenstein, Norway, and EU institutions, bodies, and agencies. It does not cover every European country and excludes transfers solely for public security, national defence, state security, or criminal investigation and enforcement. Confirm the actual destination, recipient, purpose, and onward transfer.
Record the separate Article 7 or 11 processing basis and Article 33 transfer mechanism.
For ANPD standard clauses, incorporate Sections I-III in full and without changing their text; complete the permitted fields and security measures.
For specific clauses or global corporate rules, obtain ANPD approval before relying on the mechanism.
For consent, ensure it is specific, prominent, informed about the international character, and clearly separated from other purposes.
Who should own International Transfers, and what evidence should prove the decision?
The controller must verify whether the operation is a transfer, whether the LGPD applies, and whether a valid processing basis and transfer mechanism support it. Operators must provide the information they hold and implement the controller's instructions.
Keep and identity and roles, the transfer description, purposes, data, people, countries, retention, Article 7 or 11 basis, Article 33 mechanism, executed safeguard or , onward transfers, security measures, transparency, rights route, approvals, and review date. Record whether the flow is a direct transfer, access by another processing agent, onward transfer, or international collection because each description changes the mechanism analysis.
Name the controller approver, privacy or legal reviewer, contract owner, security owner, system owner, and contact.
Attach the signed clauses or , transfer record, security schedule, publication, data-subject request route, and approval evidence.
Use dated evidence for the mechanism status, contract execution, and subprocessor list, access configuration, and review.
Reassess after a new , country, purpose, data category, subprocessor, remote-access model, onward transfer, security change, or ANPD decision.
Do not use EU standard contractual clauses as a substitute for ANPD clauses unless the ANPD has formally recognised clauses as equivalent and the decision's conditions are met. The EU is a different mechanism from clause equivalence.
The foreign-origin exception is narrow. Confirm whether data merely transits Brazil without communication or shared use with a Brazilian processing agent, or returns only to its qualifying country of origin under the conditions in Resolution 19/2024. Reuse, sharing, or a different onward destination can change the result.
An does not remove the underlying LGPD duties, including purpose, necessity, transparency, rights, security, and processing records.
For ANPD clauses, publish the required Portuguese-language transfer information on a website in a clear and accessible form and provide the clauses to a data subject on request, subject to commercial and industrial secrets.
Reassess when the , country, purpose, data, subprocessor, access model, contract, security measure, or ANPD decision changes.
Use an intake that discovers both planned and existing transfers. Reject a generic vendor assurance: the approval must identify the actual , purposes, data, system, mechanism, contract or decision, security measures, onward-transfer path, and transparency control.
For ANPD clauses, the 12-month transition period from the publication of Resolution 19/2024 has ended. Existing contracts that rely on contractual clauses should now contain the ANPD clauses when that is the selected mechanism.
Inventory direct transfers and onward transfers, including access rather than only storage.
Verify the processing basis and transfer mechanism before access begins.
Implement the contract, security, rights, notice, publication, and data-subject access conditions attached to that mechanism.
Monitor the , mechanism, adequacy conditions, and safeguards throughout the transfer lifecycle.