Brazil's LGPD Compliance Requirements

Type: Decision Rule Confidence: 0.89 Sources: 5 Verified: 2026-02-28 Applies to: Any organization processing personal data of individuals in Brazil

Rule

Any organization processing personal data of individuals located in Brazil, targeting individuals in Brazil, or processing data collected in Brazil must comply with the Lei Geral de Protecao de Dados (LGPD, Law 13,709/2018). Compliance requires establishing one of ten legal bases for processing, appointing a Data Protection Officer (encarregado), maintaining processing records, responding to data subject rights requests within 15 days, and notifying the ANPD and affected individuals of data breaches. Since August 23, 2025, all international data transfers must use ANPD-approved Standard Contractual Clauses or other authorized mechanisms. [src1, src2]

Evidence

LGPD penalties include fines of up to 2% of net turnover in Brazil (capped at BRL 50 million per violation, approximately USD 10.5 million), daily fines, mandatory public disclosure, blocking or deletion of personal data, and suspension of processing for up to six months. The ANPD's 2025-2026 regulatory agenda prioritizes children's data, AI and biometrics, data scraping, and DPIAs. The SCC grace period ended August 23, 2025 -- all cross-border transfers must now use authorized mechanisms. The ANPD issued its first administrative sanctions in 2023, signaling transition to enforcement-based regulation. [src1, src3, src5]

Key Properties

Conditions

Constraints

Rationale

Brazil enacted the LGPD in 2018, modeled substantially on the GDPR, to establish a comprehensive data protection framework for Latin America's largest economy. The LGPD's ten legal bases reflect Brazil's unique legal tradition, including credit protection as a standalone basis. The August 2025 SCC deadline forced organizations to formalize previously informal cross-border data flows, particularly affecting US and EU tech companies operating in Brazil. [src1, src4]

Framework Selection Decision Tree

START -- User needs Latin American privacy/data protection guidance
|-- Which jurisdiction?
|   |-- Brazil --> LGPD Summary <-- YOU ARE HERE
|   |-- EU/EEA --> GDPR Summary
|   |-- California/US --> CCPA/CPRA Summary
|   |-- Japan --> APPI Summary
|   +-- Multiple jurisdictions --> Cross-Border Data Transfers unit
|-- Does the organization process personal data of individuals in Brazil?
|   |-- YES --> LGPD applies: 10 legal bases, DPO, breach notification, SCCs
|   +-- NO --> LGPD does not apply; check other jurisdiction rules
+-- Does the organization transfer data internationally?
    |-- YES --> Must use ANPD-approved SCCs or authorized mechanisms (since Aug 2025)
    +-- NO --> Focus on domestic LGPD obligations

Application Checklist

Step 1: Determine applicability

Step 2: Establish legal bases and appoint encarregado (DPO)

Step 3: Implement cross-border transfer mechanisms

Step 4: Establish data subject rights and breach response

Anti-Patterns

Wrong: Assuming LGPD is identical to GDPR and applying GDPR compliance as-is

Organizations with GDPR programs assume they cover Brazil automatically. LGPD has 10 legal bases, a unique credit protection basis, 15-day rights response, and ANPD-specific SCC requirements. [src2]

Correct: Conduct a separate LGPD gap analysis

Map GDPR controls to LGPD requirements, identifying the four additional legal bases, shorter response deadlines, ANPD-specific SCC formats, and Brazil-specific enforcement priorities. [src1]

Wrong: Relying on informal data transfer arrangements after August 2025

Before August 23, 2025, organizations could transfer data internationally during the grace period. Continuing without ANPD-approved SCCs is now a violation. [src4]

Correct: Execute ANPD-approved SCCs for all international transfers

Implement ANPD's specific SCC format (which differs from EU SCCs) for all cross-border transfers. Conduct transfer impact assessments and maintain documentation. [src3]

Wrong: Storing payment data without explicit, separate consent

Pre-populating payment forms or retaining card data for convenience without specific consent is a commonly seen LGPD violation in e-commerce. [src2]

Correct: Obtain separate, specific consent for each data retention purpose

Request explicit consent for storing payment information with clear purpose and duration. Provide easy withdrawal mechanisms and data deletion options. [src1]

Counter-Arguments

Common Misconceptions

Misconception: LGPD is just a copy of GDPR, so GDPR compliance means LGPD compliance.
Reality: LGPD has four additional legal bases, a 15-day rights response deadline, ANPD-specific SCCs, and different penalty structures. A separate compliance assessment is required. [src1]

Misconception: LGPD only applies to companies with a physical presence in Brazil.
Reality: LGPD has extraterritorial scope: any organization processing data of individuals in Brazil or collecting data in Brazilian territory must comply. [src2]

Misconception: The ANPD is not actively enforcing LGPD yet.
Reality: The ANPD issued its first sanctions in 2023 and its 2025-2026 agenda prioritizes children's data, AI/biometrics, data scraping, and DPIAs. Enforcement is active. [src5]

Misconception: Breach notification must be made within 72 hours like GDPR.
Reality: LGPD requires notification "within a reasonable timeframe" as defined by ANPD, which is less prescriptive than GDPR's 72-hour rule. [src1]

Comparison with Similar Rules

Rule/FrameworkKey DifferenceWhen to Use
LGPD (Brazil)10 legal bases; BRL 50M cap; ANPD enforcement; 15-day rights responseProcessing data of individuals in Brazil
GDPR (EU)6 legal bases; up to 4% global turnover; DPA enforcement; 30-day responseProcessing EU/EEA resident data
CCPA/CPRA (California)Opt-out model; threshold-based; per-violation finesFor-profit businesses processing CA resident data
APPI (Japan)No size threshold; criminal penalties; PPC enforcementProcessing data of individuals in Japan

When This Matters

Fetch this when a user asks about Brazilian data protection requirements, LGPD compliance for foreign companies, cross-border data transfers involving Brazil, or privacy obligations for businesses serving Brazilian customers or collecting data in Brazilian territory.

Related Units