Select the Article 33 mechanism whose express conditions match the transfer under Brazil's Lei Geral de Proteção de Dados Pessoais (LGPD), Law 13.709/2018. Adequacy depends on a decision from the Agência Nacional de Proteção de Dados (ANPD). can be adopted without case-by-case approval but must be used in full. Specific clauses and require prior ANPD approval. Consent and the other Article 33 routes are case-specific and do not replace the Article 7 or 11 processing basis.
1
Section 1
What should teams decide about International Transfer Mechanisms under the Brazil LGPD?
Adequacy is available only for a country or international organisation covered by an ANPD decision and subject to that decision's conditions. Resolution 32/2026 covers all EU Member States, Iceland, Liechtenstein, Norway, and EU institutions, bodies, and agencies. It excludes transfers solely for public security, national defence, state security, or criminal investigation and enforcement. Confirm the actual destination, recipient, purpose, and onward flow.
are the usual contractual mechanism. Adopt Sections I-III of Annex II to Resolution 19/2024 integrally and without changing their text. Complete the permitted fields, choose the applicable options, and describe security measures. Other contract terms may not exclude, change, or contradict the clauses.
Specific contractual clauses are exceptional and need prior ANPD approval after the controller shows why the standard clauses are impracticable. also need prior ANPD approval and must be tied to an Article 50 governance program. The ANPD's current transfer page states that it has not recognised equivalent foreign standard clauses and has not approved specific clauses or global corporate rules, so an application or foreign approval is not a usable mechanism by itself.
Other Article 33 routes include international legal cooperation, protection of life or physical safety, ANPD authorisation, international cooperation commitments, public policy or legal public-service duties, specific prominent consent, and necessity for the Article 7(II), (V), or (VI) situations named in Article 33(IX).
Do not treat seals, certificates, codes of conduct, foreign clauses, or a vendor's privacy certification as an approved Brazilian mechanism without the ANPD action required by law and regulation.
Record why the selected mechanism fits and why any more specific conditions are satisfied.
Keep the mechanism linked to the exact system, importer, contract, purpose, data, and onward transfers.
Who should own International Transfer Mechanisms, and what evidence should prove the decision?
The controller verifies LGPD applicability, the processing basis, and the mechanism. Privacy or legal prepares the analysis; procurement or the business owner executes the contract; security documents and tests safeguards; operators provide facts and implement instructions.
For standard clauses, keep the signed instrument, completed exporter and importer identities and roles, transfer description, selected onward-transfer option, security schedule, additional clauses, and proof that additional terms do not contradict the ANPD text. For adequacy, retain the current decision and the facts showing the transfer is covered. For another Article 33 route, record every case-specific condition rather than naming the route alone.
Name one accountable owner and one reviewer for the International Transfer Mechanisms workflow.
Keep source screenshots or source links, decision notes, implementation tickets, and approval records together.
Use dated evidence for deadlines, notices, risk assessments, contracts, user journeys, and regulator-facing records.
Review the evidence after product changes, new markets, new vendors, enforcement updates, or material changes in the source text.
Which mechanism distinctions prevent common errors?
Do not confuse EU adequacy, ANPD recognition of foreign standard clauses as equivalent, and use of ANPD standard clauses. They are distinct mechanisms with different evidence.
Specific consent must be informed, prominent, specific to the transfer, and clearly separate from other purposes. It may be unsuitable where refusal is not genuinely available or where another Article 33 route better describes a necessary, recurring transfer.
An importer can be a controller or operator, and the transfer may run controller-to-controller, controller-to-operator, or between operators on a third controller's instructions.
Check onward transfers and subprocessors; the first transfer mechanism does not excuse later incompatible transfers.
For ANPD clauses, the controller must publish clear Portuguese-language transfer information and provide the clauses to a data subject on request, subject to protected secrets.
Reassess when an approval, , importer, destination, purpose, data, subprocessor, security measure, or contract changes.
Use a mechanism register with status values such as adequate destination confirmed, ANPD clauses executed, specific clauses approved, approved, or another Article 33 route documented. Do not mark a mechanism complete while an approval application is pending.
The 12-month transition period in Resolution 19/2024 has ended. A contractual transfer that relies on clauses should now use the ANPD clauses unless another valid mechanism covers it.
Match every importer and onward-transfer path to a mechanism and processing basis.
ANPD guidance summarizing transfer mechanisms such as adequacy decisions, standard contractual clauses, specific clauses, and global corporate rules.
"Este Regulamento dispõe sobre as cláusulas-padrão contratuais, as cláusulas-padrão contratuais equivalentes, as cláusulas contratuais específicas, as normas corporativas globais e as decisões de adequação."
ANPD regulation establishing procedures, valid transfer mechanisms, standard contractual clauses, and evidence expectations for Brazil LGPD international transfers.
"Este Regulamento estabelece os procedimentos e as regras aplicáveis às operações de transferência internacional de dados"
Binding decision defining the covered EU and EEA destinations, excluded law-enforcement and security purposes, monitoring, and re-evaluation within four years from entry into force.