LGPD
Identify Brazilian processing obligations and build operational controls around data-subject rights.
Ley Federal de Protección de Datos Personales en Posesión de los Particulares
Put Mexico’s private-sector data protection requirements into operational practice.
Private-sector persons and organizations covered by the law, subject to the exclusions in the current statute.
A privacy notice, documented rights process, transfer controls and incident response.
Use the current 2025 statute and applicable implementing rules. Public-sector processing is governed under a separate regime.
Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.
Fill this in with your sponsor and send it to the people who own the work.
Mexico LFPDPPP 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 Map activities and define privacy ownership · Privacy lead + local counsel [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. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work. 2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts. 3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
Checklist, instructions and 11 templates.
| Step | Owner | When to act | Estimated target | Deliverables | Status |
|---|---|---|---|---|---|
| Map activities and define privacy ownership | Privacy lead + local counsel | Before implementation | Set a start date | Processing inventory; Responsibility matrix | Open |
| Implement notices and consent | Product + legal | Before covered processing | Set a start date | Aviso de privacidad; Consent records; Purpose register | Open |
| Operationalize ARCO rights and transfers | Privacy operations + vendor lead | On requests and before disclosure | Set a start date | ARCO workflow; Transfer records; Supplier terms | Open |
| Secure data and notify significant incidents | Security + responsible party | Ongoing and upon qualifying incidents | Set a start date | Safeguards record; Incident assessment; Notice 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 responsible entities, processing purposes, sensitive data, operators and transfer destinations. Assign the person or department that handles rights requests.
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.
Every decision has one accountable person, a backup and a practical route to reach them.
Share the approved instructions with the people expected to follow them and test the handoffs at the next exercise.
Document notice content, consent and exceptions, purpose limitation and choices for secondary processing. Provide clear means to exercise privacy rights.
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.
You can demonstrate what the person saw, how they acted and how the decision was honored.
Provide the consent log and tested withdrawal flow to privacy operations and downstream system owners.
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.
Support access, rectification, cancellation and opposition. Document response and implementation windows, transfers and applicable consent or exemptions.
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 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 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.
Apply safeguards appropriate to the data. Evaluate effects on affected people and communicate qualifying breaches in accordance with the statute.
Fictional details. Use the same fields with evidence from your work.
A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.
Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.
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.