Mexico LFPDPPP
Put Mexico’s private-sector data protection requirements into operational practice.
Lei Geral de Proteção de Dados Pessoais · Brazil
Identify Brazilian processing obligations and build operational controls around data-subject rights.
Controllers and processors whose activities fall within the Brazilian law’s territorial scope and are outside defined exclusions.
Accountability records for lawful processing, rights, security and qualifying breach notifications.
Confirm sector-specific clocks and rules for small processing agents. Evaluate international transfers separately.
Track processing with unresolved grounds, open rights cases, transfers without confirmed safeguards and pending incident decisions.
Fill this in with your sponsor and send it to the people who own the work.
LGPD kickoff brief Business reason and required outcome [Contract, obligation or approval] Scope and exclusions [Entities, systems or activities, and reasons] Fixed deadlines and internal milestones [Date, source and owner] Executive sponsor and authorized signer [Names] Project lead and backup [Names] First workstream Inventory processing and document bases · Privacy lead + legal [Name and due date] People, effort and external costs [Estimate, owner and contingency] Evidence folder and reviewer access [Location, access owner and review date] Decisions and blockers [Item, options, owner and decision date] First week 1. Walk a local workflow from collection to deletion. Identify people, recipients, remote access and the legal ground documented for each purpose. 2. Review a vendor with access outside Brazil. Collect the contract, data pathways and the transfer mechanism, and name the person who confirms it. 3. Have the team rehearse intake for a rights request and an incident. Confirm who can make and record each decision.
General ANPD deadline for controller notice to the authority and affected people, subject to more specific rules.
Official reference (opens in a new tab)Checklist, instructions and 9 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Inventory processing and document bases | Privacy lead + legal | Before processing | Set a start date | Processing register; Scope and legal-basis analysis | Open |
| Assign privacy duties and implement rights | Controller + encarregado where applicable | Before launch and upon request | Set a start date | Privacy notice; Rights workflow; Supplier instructions | Open |
| Review transfers and higher-risk processing | Legal + product | Before transfers or changes | Set a start date | Transfer register; Risk and impact documentation | Open |
| Triage and report eligible incidents | Security + controller | As soon as you become aware, under applicable rules | Set a start date | Incident assessment; Notification log | Open |
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
Identify local collection, targeting and processing. Document lawful bases and separate rules for sensitive data and children.
Brazil entity and service records, system and vendor inventory, notices and actual data flows.
A payroll or fulfillment row names the purpose, ground, source evidence, parties, retention period and person responsible.
Bring undocumented sensitive data, a disputed role or a processing purpose without a basis to Privacy.
Fictional details. Use the same fields with evidence from your work.
The entry names a real purpose, matches actual product behavior and links to the legal and vendor decisions behind it.
Use the reviewed register when drafting notices, evaluating changes and deciding which processing needs an impact or transfer assessment.
Fictional details. Use the same fields with evidence from your work.
A reviewer can use the memo to classify a named system and see how shared dependencies are handled.
Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.
Define the privacy contact and suppliers’ roles. Set up rights verification, fulfillment and a notice in the users’ language.
Role analysis, rights and notice procedures, system search capabilities and current ANPD rules.
A test correction case shows the request date, affected source systems, changes, verification and approved response.
Escalate missing access to a vendor system or a case at risk of missing the applicable deadline.
Fictional details. Use the same fields with evidence from your work.
A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.
Send approved text to the publishing owner and give support teams the version and effective date.
Fictional details. Use the same fields with evidence from your work.
A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.
Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.
Fictional details. Use the same fields with evidence from your work.
The executed version covers the agreed roles and evidence paths. Review any jurisdiction-specific clauses with counsel.
Give named obligations to operations and procurement. Use this worksheet to track review and keep the executed agreement as the authority.
Document applicable ANPD transfer mechanisms, contractual terms and any required data protection impact report.
Recipient and transfer data, vendor contracts, proposed activity, safeguards and current ANPD guidance.
The assessment shows actual recipients and locations, approved transfer treatment, key safeguards and who confirmed them.
Stop and escalate a proposed transfer or higher-risk use that lacks an approved mechanism or treatment.
Fictional details. Use the same fields with evidence from your work.
The register shows actual access paths, the basis for each transfer and a clear release decision.
Share the decision with supplier and access owners so they can implement the conditions before data is available.
Fictional details. Use the same fields with evidence from your work.
The assessment explains the potential harm, why each measure helps and who accepts the remaining risk.
Give the signed review to the owner of the launch or processing decision. Use the regulator’s assessment form where one applies.
Assess relevant risk or damage to individuals and maintain documentation. Notify ANPD and affected data subjects where required.
Incident timeline, affected data, potential impact, supplier contacts and current ANPD notification rules.
The incident file ties the classification and notification decision to facts, timestamps, owners and the applicable ANPD rule.
Alert the local incident and privacy contacts promptly if harm or reportability is uncertain and assign a person to track the deadline.
Fictional details. Use the same fields with evidence from your work.
Timelines distinguish different events and a reviewer can reconstruct the reporting decision from the available facts.
Give the incident lead and privacy decision maker a time-stamped update. Preserve working evidence separately.
Fictional details. Use the same fields with evidence from your work.
Every open item has a next action and closed items have a verifiable record of closure or delivery.
Use the log at case reviews and provide a restricted copy only where the engagement requires it.