← Back to all briefings
Compliance 5 min read Published Updated Credibility 73/100

Brazil issues MP 959 to delay LGPD effective date

Brazil’s Provisional Measure 959/2020 proposed pushing the LGPD effective date to May 3, 2021 because of COVID-19 disruptions, forcing privacy teams to revisit project timelines while tracking congressional review of the delay.

Editorially reviewed for factual accuracy

Compliance pillar illustration for Zeph Tech briefings
Compliance controls, audit, and evidence briefings

Overview

On , Brazil issued Provisional Measure 959/2020 proposing to delay the Lei Geral de Proteção de Dados (LGPD) effective date from August 2020 to May 3, 2021. The measure responded to COVID-19 disruptions preventing organizations from completing compliance programs, though its provisional nature created uncertainty requiring scenario planning for multiple setup timelines.

Legislative Context

Understanding Brazil's legislative process is essential for compliance planning:

  • Provisional Measures: MPs have immediate force of law but require Congressional approval within 120 days or they expire.
  • Amendment risk: Congress may modify, extend, shorten, or reject the proposed delay during deliberation.
  • Previous delays: LGPD had already experienced setup delays, creating compliance fatigue and uncertainty.
  • Enforcement authority: The Autoridade Nacional de Proteção de Dados (ANPD) establishment also faced delays, complicating guidance development.

Organizations could not assume the May 2021 date would hold and needed contingency plans for earlier setup.

LGPD Compliance Scope

Organizations subject to LGPD face full requirements:

  • Territorial scope: LGPD applies to processing of Brazilian residents' personal data regardless of where the processing organization is located.
  • Legal bases: Processing requires documented legal basis including consent, legitimate interest, contract performance, or legal obligation.
  • Data subject rights: Rights to access, correction, deletion, portability, and information about processing activities.
  • Data Protection Officer: Mandatory DPO appointment with public contact information.
  • Breach notification: Notification requirements to ANPD and affected individuals for security incidents.
  • Cross-border transfers: Restrictions on international data transfers requiring adequacy decisions, SCCs, or other mechanisms.

COVID-19 Compliance Disruptions

The pandemic disrupted LGPD compliance programs in multiple ways:

  • Resource constraints: Organizations diverted compliance resources to pandemic response and business continuity.
  • Remote work challenges: Data mapping and process documentation proved difficult with distributed workforces.
  • Vendor coordination: Contract negotiations with processors and service providers stalled.
  • Budget pressures: Economic uncertainty led to privacy program budget reductions or freezes.
  • Regulatory uncertainty: ANPD establishment delays meant lack of official guidance on compliance interpretation.

Compliance Program Recommendations

If you are affected, continue LGPD preparation despite timeline uncertainty:

  • Data inventory: Complete data mapping identifying personal data flows, processing purposes, and legal bases.
  • Privacy notices: Draft and review privacy notices meeting LGPD transparency requirements.
  • Consent mechanisms: Implement consent collection and management for processing activities requiring consent.
  • Data subject request processes: Establish procedures for responding to access, deletion, and portability requests.
  • Vendor contracts: Negotiate data processing agreements with service providers and processors.
  • Breach response: Develop incident response procedures addressing LGPD notification requirements.

Multi-Jurisdiction Coordination

Organizations with global privacy programs should coordinate LGPD with other frameworks:

  • GDPR alignment: Many LGPD requirements parallel GDPR, enabling used compliance investments.
  • CCPA considerations: U.S. organizations facing both CCPA and LGPD should identify common requirements and Brazil-specific gaps.
  • Regional harmonization: Latin American privacy laws now converge, supporting regional compliance approaches.
  • Global policy frameworks: Enterprise privacy policies can address multiple jurisdictions with jurisdiction-specific addenda.

Scenario Planning

If you are affected, prepare for multiple setup scenarios:

  • Scenario A: MP 959 approved—May 2021 effective date with full compliance required by then.
  • Scenario B: MP expires or rejected—August 2020 effective date requiring accelerated completion.
  • Scenario C: Modified delay—Congressional amendments producing different effective date.
  • Scenario D: Phased setup—Different requirements becoming effective at different times.

Compliance roadmaps should identify critical path activities and resources required for each scenario.

Monitoring and Updates

Privacy teams should actively monitor legislative developments through local counsel, trade associations, and regulatory announcements to adjust planning as the setup timeline clarifies.

Continue in the Compliance pillar

Return to the hub for curated research and deep-dive guides.

Visit pillar hub

Latest guides

Coverage intelligence

Published
Coverage pillar
Compliance
Source credibility
73/100 — medium confidence
Topics
LGPD · Privacy compliance · Brazil · Regulatory timelines
Sources cited
3 sources (in.gov.br, cvedetails.com, iso.org)
Reading time
5 min

Documentation

  1. Medida Provisória nº 959, de 29 de abril de 2020 — Presidência da República do Brasil
  2. CVE Details - Vulnerability Database — CVE Details
  3. ISO 37301:2021 — Compliance Management Systems — International Organization for Standardization
  • LGPD
  • Privacy compliance
  • Brazil
  • Regulatory timelines
Back to curated briefings

Comments

Community

We publish only high-quality, respectful contributions. Every submission is reviewed for clarity, sourcing, and safety before it appears here.

    Share your perspective

    Submissions showing "Awaiting moderation" are in review. Spam, low-effort posts, or unverifiable claims will be rejected. We verify submissions with the email you provide, and we never publish or sell that address.

    Verification

    Complete the CAPTCHA to submit.