Web analytics, cookies, tag managers, CMPs, ad pixels, and session-replay tools as deployed on websites and apps targeting Brazil. Sectoral rules (banking via BCB, healthcare, telecoms via Anatel) are touched only where they intersect with the analytics layer.
Applicable laws
The legal framework that governs personal data processing here.
National addons
Country-specific statutes layered on the EU baseline.
- Art 3 Extraterritorial scope — processing in Brazil OR offering goods/services to people in Brazil OR data collected in Brazil
- Art 5 XVIII Representante — controllers based outside Brazil must designate a representative
- Art 7 10 legal bases for processing personal data (including legitimate interest)
- Art 11 Separate legal-basis regime for sensitive data — narrower than Art 7
- Art 14 Children (under 12) — parental consent required for any processing where consent is the basis; adolescents (12–18) — best-interests test applies, all Art 7 bases available per ANPD 2023 statement
- Art 33 International transfers — adequacy decisions, SCC-equivalent contracts, BCRs, specific consent, or legal-claim necessity
- Art 41 Encarregado (DPO) — mandatory for controllers, with small-scale-agent exemption per Resolution CD/ANPD 2/2022
- Art 52 Sanctions — warning, fine up to 2% of Brazilian-group revenue capped at R$50M per infraction, daily fines, public disclosure, blocking, deletion, partial/total prohibition
- Art 8 Infraction grades — light, medium, serious — drives base-fine calculation
- Art 11 Aggravating circumstances — recidivism, profit-from-violation, victim count, sensitive data
- Art 12 Mitigating circumstances — good-faith adoption, cooperation with ANPD, prompt remediation
- § 4 Cookie categories — necessary cookies may rely on legitimate-interest; advertising cookies require consent
- § 5 Cookie banner — must be transparent, granular, and offer equal-prominence reject option
- § 6 Cookie policy — separate document recommended in addition to general privacy notice
- Art 2 Definition of small-scale agent — turnover/headcount thresholds + non-high-risk processing
- Art 11 DPO exemption — communication channel sufficient unless high-risk processing
- Art 14 ROPA simplification — minimum-content record permitted
- Art 5 Notification trigger — significant risk or damage to data subjects (sensitive data, children, financial, authentication, large-scale)
- Art 6 Notification deadline — 3 business days controllers / 6 business days small-scale agents
- Art 11 Incident management report — mandatory; ANPD may request anytime; 5-year retention
- Art 7 Internet user rights — privacy, data protection, transparency in collection terms
- Art 13 Connection log retention — 12 months mandatory for autonomous-system administrators
- Art 15 Application log retention — 6 months mandatory for application providers
Regulators
Supervisory authorities that interpret and enforce privacy law here.
Coordination body
- 2022-10-18 · ANPD Cookies Guide — Guia Orientativo 'Cookies e Proteção de Dados Pessoais' — categorizes cookies and recommends consent for advertising and most analytics cookies.
- 2023-02-24 · Dosimetry Regulation — Resolução CD/ANPD 4/2023 — sanctions calculation methodology unblocked first ANPD fines in Jul 2023.
- 2023-05 · Children & Adolescents data — ANPD statement clarifying that adolescents (12–18) may rely on any LGPD Art 7 legal basis when best-interests test is documented; consent not exclusive.
- 2024-04-24 · Incident Notification — Resolução CD/ANPD 15/2024 — 3-business-day ANPD notification + significant-risk threshold for data-subject notification.
- 2024-07-17 · DPO Statute — Resolução CD/ANPD 18/2024 — detailed DPO competencies, independence, and conflict-of-interest rules; complements small-scale exemption from Resolution 2/2022.
- 2024-10 · Meta AI suspension — Precautionary measure ordering Meta to suspend training of generative-AI models on Brazilian users' data — first major ANPD action against a US tech platform.
Notable enforcement
ANPD took a deliberately educational stance for the first 24 months — issuing guides, orientations, and warnings rather than fines. The Dosimetry Regulation (Feb 2023) unblocked the sanctions track; the first fine (Telekall, Jul 2023) was statutorily small (R$14,400 = 2% of annual revenue cap for the offender) but symbolically significant. Fast Shop (Apr 2024) crossed into six-figure-BRL territory. The Meta AI precautionary measure (Oct 2024) signalled willingness to act against US Big Tech without waiting for sanctions process. ANPD's enforcement remains far below European levels in monetary terms but is escalating in frequency and scope.
GA4 status
GA4 is usable in Brazil with prior consent for non-essential cookies under the ANPD Cookies Guide (Oct 2022). LGPD Art 7 IX (legitimate interest) is theoretically available for first-party analytics but ANPD's cookies guide treats advertising and behavioral analytics as consent-based. Cross-border transfer to Google's US servers operates under Art 33 — currently relying on contract clauses + Google's own corporate commitments since no Brazil-US adequacy decision exists. ANPD has not yet issued a specific GA4 ruling.
| DPA | Stance |
|---|---|
| ANPD | No specific GA4 enforcement yet. Cookies Guide treats analytics as consent-based; controllers should gate GA4 behind a CMP and document Art 33 transfer basis. |
| PROCONs | Focus on consumer-transparency rather than vendor-specific positions. PROCON-SP active on Big Tech consumer rights but defers to ANPD on data-protection technicalities. |
Cross-border transfers + Schrems II
Brazil has no equivalent to the EU-US DPF. Transfers from Brazil are governed by LGPD Art 33 — 9 mechanisms including adequacy decisions (none yet issued by ANPD as of May 2026), SCC-equivalent contracts (cláusulas-padrão contratuais — ANPD draft public consultation completed 2023, final regulation pending), specific consent for the transfer, and legal-claim or contract-execution necessity. The US is not on any Brazilian adequacy list — controllers transferring to US recipients rely on contract clauses + supplementary measures by analogy with Schrems II.
ANPD's draft cláusulas-padrão (SCC equivalents) released for public consultation in Aug 2023; final adoption expected 2026. In the interim, controllers use freely-drafted intercontroller/controller-processor agreements meeting LGPD Art 33-46 requirements. EU SCCs (2021/914) are commonly retro-fitted with LGPD-specific addenda.
Employee data
Key thresholds
Vendor signals
Red / yellow / green markers are an editorial reading of public regulator guidance and published enforcement actions, applied to vendor behavior we can observe or that the vendor documents. They are not legal conclusions, not endorsements, and not advice about your specific processing. Configuration changes the picture — a "yellow" vendor in one configuration may be defensible in another.
Analytics tools · 12 · 6 green · 5 yellow · 1 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | Cookieless by design. EU-routed via Cloudflare. No DPA required for Lite tier (no PII). | |
| GREEN | Self-hosted on your infrastructure. Full data control, configurable IP anon. Meets every jurisdiction with cookieless config. | |
| GREEN | EU-hosted with cookieless mode available. With cookies disabled qualifies for §25(2) exception in Germany. | |
| GREEN | German-hosted, cookieless, GDPR-aligned by design. | |
| GREEN | EU-hosted, no cookies, no PII processed. ePrivacy-exempt for cookieless tracking. No banner required. | |
| GREEN | Open-source, cookieless, fully self-hostable. Default-green when self-hosted. | |
| YELLOW | Visitor ID cookie + cross-suite stitching with Experience Platform. DPIA strongly recommended; configure ECID + IP obfuscation. | |
| YELLOW | EU residency available on paid plans; default cloud is US. Persistent user IDs require config + DPA + DPF chain. | |
| YELLOW | Default config sends data to US infrastructure. Needs Consent Mode v2 + IP anonymization + DPF active + signed DPA + reject-all banner. Server-side EU proxy moves to green. | |
| YELLOW | EU residency available on paid plans; default cloud is US. Identifies users by default — needs config. | |
| YELLOW | EU cloud helps but session recording + autocapture default to PII collection. Disable autocapture and recordings or self-host for green. | |
| RED | Auto-capture grabs every click and form value — broad PII risk under GDPR Art 5(1)(c) data minimization. |
Consent management platforms · 5 · 5 green · 0 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | Danish-based, EU-hosted. Auto-blocks third-party scripts pre-consent — verify your manual scripts also gate. | |
| GREEN | Italian-based, EU-hosted. Free tier limits 5k pageviews/mo; granular per-vendor controls require paid plan. | |
| GREEN | Open-source, self-hosted. No managed updates — site owner maintains vendor list. | |
| GREEN | GDPR + CCPA + multi-region templates available. Common config error: GDPR/CCPA mode mismatch — verify per-region defaults. | |
| GREEN | German-based, EU-hosted. v3 SDK required for Consent Mode v2; TCF flow can over-collect for non-AdTech sites. |
Tag managers · 1 · 0 green · 1 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| YELLOW | Container only — verdict depends on which tags fire and when. Block until consent. Server-side GTM in EU recommended. |
Session replay · 3 · 0 green · 0 yellow · 3 red
| Vendor | Status | Rationale |
|---|---|---|
| RED | Full session capture — highest-risk category. Explicit consent + DPIA + strict retention. | |
| RED | Session replay — high-risk processing per EDPB Guidelines 3/2019. DPIA + explicit consent required. Cannot run pre-consent. | |
| RED | Session replay + Microsoft tracking. DPIA + explicit consent required. |
Ad pixels · 3 · 0 green · 0 yellow · 3 red
| Vendor | Status | Rationale |
|---|---|---|
| RED | Loads pre-consent if naively placed; cross-device matching broad. Block until consent + IAB TCF string set. | |
| RED | Schrems II concerns persist; advanced matching hashes PII but does not fix EU→US transfer problem. | |
| RED | PRC-parent ownership flagged by Italian Garante and EDPB; transfers to China contested. Consent + risk acknowledgement required. |
Server-side · 3 · 2 green · 1 yellow · 0 red
| Vendor | Status | Rationale |
|---|---|---|
| GREEN | EU-only datacenters strong for FR/DE compliance; per-event pricing scales steeply at high traffic. | |
| GREEN | EU server containers handle the routing — but server-side tagging does NOT auto-fix consent. CMP must still gate browser-side pings. | |
| YELLOW | "EU server" ≠ EU data — clients still transmit to Google ad backends downstream. Use only for Google-ecosystem first-party-routing. |
Compare with neighbors
Side-by-side rule comparison.
Common questions
Does LGPD apply to non-Brazilian companies?
When did ANPD enforcement actually start?
Must my privacy notice be in Portuguese?
What's the child-consent age in Brazil?
Do I need a Brazilian DPO (encarregado)?
What is the ROPA / RNBD requirement?
Are sectoral rules separate from LGPD?
Is 'legitimate interest' a valid basis for analytics in Brazil?
Are international transfers from Brazil restricted?
What changed with the Meta AI precautionary measure (Oct 2024)?
// EDITORIAL · NOT LEGAL ADVICE This page summarises Brazil's privacy framework as of 2026-05-05. Rules vary by sector, establishment, and DPA position. For binding interpretation, consult counsel admitted here.