Start hereInventory processing and document bases
~84 days leftOpen step
Guide library
Regulation Latin America

LGPD

Lei Geral de Proteção de Dados Pessoais · Brazil

Identify Brazilian processing obligations and build operational controls around data-subject rights.

Who it applies to

Controllers and processors whose activities fall within the Brazilian law’s territorial scope and are outside defined exclusions.

What you’ll produce

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.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

Which activities and entities in Brazil are covered?
Have Privacy and local Legal document where processing takes place, whose data is involved, relevant controller or operator roles, and applicable exemptions or duties.
Who owns rights, transfers and incidents?
Assign the person responsible for data protection and the privacy contact under the applicable requirements. Fund updates to systems, transfer agreements and incident response.
What needs approval before launch?
Set a sign-off path for sensitive information, new purposes, international transfers and requests for impact reports. Include Procurement and regional Operations in the decision.

How to spend the 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.

What to review each week

Track processing with unresolved grounds, open rights cases, transfers without confirmed safeguards and pending incident decisions.

Kickoff brief to share with your team

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.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • Three business days

    Notify eligible incidents

    General ANPD deadline for controller notice to the authority and affected people, subject to more specific rules.

    Official reference (opens in a new tab)
The whole journeyabout 84 days across 4 steps
  1. 01Inventory processing and document basesPrivacy lead + legal · ~14 days
  2. 02Assign privacy duties and implement rightsController + encarregado where applicable · ~28 days
  3. 03Review transfers and higher-risk processingLegal + product · ~28 days
  4. 04Triage and report eligible incidentsSecurity + controller · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 9 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Inventory processing and document basesPrivacy lead + legalBefore processingSet a start dateProcessing register; Scope and legal-basis analysisOpen
Assign privacy duties and implement rightsController + encarregado where applicableBefore launch and upon requestSet a start datePrivacy notice; Rights workflow; Supplier instructionsOpen
Review transfers and higher-risk processingLegal + productBefore transfers or changesSet a start dateTransfer register; Risk and impact documentationOpen
Triage and report eligible incidentsSecurity + controllerAs soon as you become aware, under applicable rulesSet a start dateIncident assessment; Notification logOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Inventory processing and document bases

    Who Privacy lead + legal When Before processing

    Identify local collection, targeting and processing. Document lawful bases and separate rules for sensitive data and children.

    How to do this step

    Before you start

    Brazil entity and service records, system and vendor inventory, notices and actual data flows.

    1. Interview operating teams and follow one activity to downstream systems, suppliers, archives and deletion.
    2. Assign each purpose a legal basis with its factual justification. Review sensitive data under the provisions that apply to it.
    3. Record who decides the purposes, who operates the processing, retention and safeguards. Obtain confirmation from the activity owner.

    What a reviewer should see

    A payroll or fulfillment row names the purpose, ground, source evidence, parties, retention period and person responsible.

    When to escalate

    Bring undocumented sensitive data, a disputed role or a processing purpose without a basis to Privacy.

    What to produce

    Processing registerSpreadsheet

    Gather first

    • Interviews with product, operations and HR
    • System and vendor inventories
    • Applicable processing and recordkeeping rules

    How to prepare it

    1. Create one row per distinct purpose or disclosure. Follow the data from collection to deletion and identify accountable parties, source, storage, recipients and retention.
    2. Record whose data it is, categories, relevant lawful basis or exception, overseas destinations and safeguards where required. Mark gaps and have the appropriate owner confirm each entry.
    3. Reconcile the list with live services and contracts. Keep a last-verified date and refresh it before material changes or new data uses.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and purpose
    P-014, send invoice receipts
    Data and people
    Billing email and amount for customer account contacts
    Roles and basis to verify
    Service company as controller. Contract analysis referenced in L-019.
    Recipients and transfer
    Email provider handles delivery. Supplier assessment V-018.
    Retention and security
    Finance schedule FS-04. Access limited to billing operations.
    Owner and review
    Finance operations, verified 2026-11-12

    Check before handing it over

    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.

    Scope and legal-basis analysisMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    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.

  2. 02

    Assign privacy duties and implement rights

    Who Controller + encarregado where applicable When Before launch and upon request

    Define the privacy contact and suppliers’ roles. Set up rights verification, fulfillment and a notice in the users’ language.

    How to do this step

    Before you start

    Role analysis, rights and notice procedures, system search capabilities and current ANPD rules.

    1. Confirm applicable appointment and contact requirements. Publish the relevant contact and give a backup access to the request queue.
    2. Define intake, identity checks, system searches, decision and response steps for each request type. Record the applicable deadline and exceptions.
    3. Rehearse a request across internal and operator systems. Capture search results, the response and feedback to the system owners.

    What a reviewer should see

    A test correction case shows the request date, affected source systems, changes, verification and approved response.

    When to escalate

    Escalate missing access to a vendor system or a case at risk of missing the applicable deadline.

    What to produce

    Privacy noticeMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    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.

    Rights workflowMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    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.

    Supplier instructionsMemo

    Gather first

    • Current agreement and service description
    • Applicable flow-down terms or engagement requirements
    • Contract owner and legal review

    How to prepare it

    1. Make a clause-by-clause worksheet. Quote only what you need to identify the current clause, and record each required subject and unresolved question.
    2. Mark where scope, instructions, evidence, security, subprocessors, incident notice, audit rights or termination affect the work. Route proposed wording to authorized reviewers.
    3. Record the signed or agreed version, responsible parties and the dates you need to revisit it. Save the source agreement in its restricted store.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Party and service
    Northstar hosting provider, production backup
    Clause or requirement
    Incident notification and contacts
    Current position
    General notice terms. No operational escalation contacts listed.
    Change to review
    Add named response channel and request confirmation of the timing.
    Owner, status and record
    Vendor lead, legal review pending, contract register V-018

    Check before handing it over

    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.

  3. 03

    Review transfers and higher-risk processing

    Who Legal + product When Before transfers or changes

    Document applicable ANPD transfer mechanisms, contractual terms and any required data protection impact report.

    How to do this step

    Before you start

    Recipient and transfer data, vendor contracts, proposed activity, safeguards and current ANPD guidance.

    1. Identify transfers and access routes using the actual service design. Document destinations, parties and the applicable mechanism.
    2. Check that the contract and real business practice implement required safeguards, including ANPD clauses where relevant.
    3. Document identified risks and measures addressing them, and prepare or update an impact report where applicable. Set a review trigger for new access or purposes.

    What a reviewer should see

    The assessment shows actual recipients and locations, approved transfer treatment, key safeguards and who confirmed them.

    When to escalate

    Stop and escalate a proposed transfer or higher-risk use that lacks an approved mechanism or treatment.

    What to produce

    Transfer registerSpreadsheet

    Gather first

    • Verified transfer map and remote access paths
    • Recipient contracts and safeguards
    • Current transfer rules, mechanisms and local restrictions

    How to prepare it

    1. Record exporters, importers, roles, countries, data and purposes. Include onward transfers or remote access if relevant to the governing law.
    2. Identify the permitted basis, mechanism or exemption and why it fits. Document safeguards, any required risk assessment and supporting clauses or approvals.
    3. Secure legal review and set triggers for reassessment, such as a new country, recipient or subcontractor. Tie the decision to procurement or product release.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Transfer ID
    XFER-018
    Parties and data
    EU controller to external support provider, ticket metadata
    Country and access
    Remote access from recipient country, limited support staff
    Mechanism and review
    Use applicable transfer mechanism. Legal assessment L-019 pending.
    Controls and approval
    Role restrictions and access logs. No production access until approved.

    Check before handing it over

    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.

    Risk and impact documentationSpreadsheet

    Gather first

    • Processing or service design and affected people
    • Threats, consequences and assessment triggers
    • Risk methodology and current safeguards

    How to prepare it

    1. Screen the activity against the applicable assessment trigger. Describe the real scenario and who or what could be harmed. Record likelihood and consequence using your criteria.
    2. Describe existing safeguards. Decide what reduces the risk and what risk remains after those measures. For a required impact assessment, document necessity, alternatives and consultation where applicable.
    3. Send the result to the person who can approve, change or stop the activity. Set a review trigger and keep evidence of the decision.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Activity and risk
    Account recovery could expose invoices to an impersonator.
    Affected people or assets
    Customer account contacts and invoices
    Current controls
    Recovery uses verified channel. Sampled evidence linked.
    Proposed treatment
    Require a second check for requests to change the billing address.
    Remaining risk and decision
    Moderate under company method. Approval required before launch.
    Owner and review trigger
    Product risk owner, repeat when recovery flow changes

    Check before handing it over

    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.

  4. 04

    Triage and report eligible incidents

    Who Security + controller When As soon as you become aware, under applicable rules

    Assess relevant risk or damage to individuals and maintain documentation. Notify ANPD and affected data subjects where required.

    How to do this step

    Before you start

    Incident timeline, affected data, potential impact, supplier contacts and current ANPD notification rules.

    1. Record when the controller became aware, affected groups, data, safeguards, impact and facts still being investigated.
    2. Evaluate whether the incident can cause relevant risk or harm. Confirm notification recipients, deadline and phased reporting options with the privacy lead.
    3. Keep the decision, notice or documented rationale, submission receipt and investigation and corrective action records.

    What a reviewer should see

    The incident file ties the classification and notification decision to facts, timestamps, owners and the applicable ANPD rule.

    When to escalate

    Alert the local incident and privacy contacts promptly if harm or reportability is uncertain and assign a person to track the deadline.

    What to produce

    Incident assessmentSpreadsheet

    Gather first

    • Alert or breach report
    • Investigation facts and relevant thresholds
    • Escalation contacts and official reporting clocks

    How to prepare it

    1. Start a case with UTC timestamps for detection, awareness, assessment and containment. Keep known facts separate from estimates and update both as evidence changes.
    2. Identify affected systems, people, data and likely harms. Link your classification, notice decision and the rule that starts each clock.
    3. Record containment, preservation, escalation and notification actions. Capture who approved the decision and set a time to confirm outstanding facts.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Incident ID
    INC-041
    Awareness and facts
    2026-11-13 09:20 UTC. Export link exposed to an unauthorized account.
    Scope and uncertainty
    One confirmed access. Log review for further recipients in progress.
    Decision and reason
    Privacy lead to assess reporting threshold with counsel by 10:30 UTC.
    Actions and status
    Access revoked, logs preserved, next review at 12:00 UTC.

    Check before handing it over

    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.

    Notification logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    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.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes