lgpd-sanctions
Skill4 starsChanged 4 months agoMITView on GitHub
ANPD sanctions reference for LGPD risk assessment. Use when evaluating severity of data protection violations, conducting compliance audits, calculating potential fines, or assessing enforcement risk under Brazilian data protection law. For implementing compliance itself (consent, retention, rights), use lgpd-compliance instead.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- digital-eca-complianceSkill
- lgpd-complianceSkill
- lgpd-document-generatorSkill
- marco-civil-complianceSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
After at least one sanction from items II, III, IV, V, or VI has already been imposed for the same case
- Distinctive: line 87
Must be proportional to the severity of the violation and extent of damage
- Distinctive: line 192
All sanctioning proceedings conducted by ANPD to date were initiated due to non-cooperative behavior by the regulated entity.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
LGPD Sanctions & Dosimetry (Lei 13.709/2018, Arts. 52-54)
Last verified against official sources: 2026-07-10
When to Use
- Evaluating the severity of a data protection violation
- Conducting compliance audits or risk assessments
- Estimating potential fines and sanctions exposure
- Preparing defense in ANPD enforcement proceedings
- Advising on remediation priorities based on sanction risk
- Reviewing incident response plans for regulatory impact
- Assessing whether a data breach requires escalation
How to Respond
| Task | Respond with |
| Risk assessment of a violation | Classification (Low/Medium/High/Critical) from the risk table + likely sanction + the dosimetry factors present |
| Fine exposure estimate | Calculation with the 2%/R$50M caps, stating revenue assumptions and applicable aggravating/mitigating factors — always framed as an estimate, not a prediction |
| Compliance audit | Checklist results prioritized by which gaps are known ANPD enforcement triggers (incident notification, non-cooperation) |
| "ANPD contacted us" | The enforcement process phase they are in + immediate actions (cooperation is the decisive factor) |
Types of Administrative Sanctions (Art. 52)
Sanctions are applied progressively, individually or cumulatively, based on the specifics of each case:
| # | Sanction | Detail | Applies to Public Entities |
| I | Warning | With deadline for corrective measures | Yes |
| II | Simple fine | Up to 2% of gross revenue in Brazil (excluding taxes), capped at R$ 50 million per infraction | No |
| III | Daily fine | Same cap as simple fine (R$ 50M total) | No |
| IV | Publicization | Public disclosure of the infraction after confirmed | Yes |
| V | Data blocking | Suspension of processing of related data until regularized | Yes |
| VI | Data deletion | Mandatory deletion of data related to the infraction | Yes |
| X | Partial database suspension | Up to 6 months, renewable for equal period | Yes |
| XI | Total processing suspension | Up to 6 months, renewable for equal period | Yes |
| XII | Processing prohibition | Partial or total ban on data processing activities | Yes |
Escalation Rule (Art. 52, S6)
Sanctions X, XI, and XII (suspension/prohibition) can ONLY be applied:
- After at least one sanction from items II, III, IV, V, or VI has already been imposed for the same case
- For controllers subject to other sanctioning bodies, those bodies must be consulted first
Public Entities (Art. 52, S3)
Public entities are subject to sanctions I, IV, V, VI, X, XI, and XII only. They cannot receive monetary fines (items II and III).
Dosimetry Criteria (Art. 52, S1)
ANPD evaluates the following parameters when determining sanctions:
| # | Criterion | What ANPD Evaluates | Impact on Sanction |
| I | Severity and nature | Type of infraction; type of personal data affected (sensitive, children's) | Higher severity = harsher sanction |
| II | Good faith | Whether the infractor acted with honest intent | Good faith = mitigating |
| III | Advantage obtained | Economic or other benefit gained from the violation | Greater advantage = harsher sanction |
| IV | Economic condition | Financial capacity of the infractor | Larger companies face proportionally larger fines |
| V | Recidivism | Previous infractions by the same agent | Repeat offenders face escalation |
| VI | Degree of harm | Extent of damage to data subjects | More harm = harsher sanction |
| VII | Cooperation | Level of collaboration with ANPD during investigation | Cooperation = mitigating |
| VIII | Internal mechanisms | Adoption of security procedures to minimize damage (per Art. 48, S2, II) | Demonstrated mechanisms = mitigating |
| IX | Good practices and governance | Privacy policies, governance programs, certifications | Established programs = mitigating |
| X | Corrective measures | Speed and effectiveness of remediation | Prompt correction = mitigating |
| XI | Proportionality | Balance between severity of violation and intensity of sanction | Ensures fair application |
Fine Calculation (Arts. 52-54)
Simple Fine (Art. 52, II)
Fine = min(Revenue_Brazil * 2%, R$ 50,000,000.00) per infraction- Revenue base: Gross revenue of the legal entity, group, or conglomerate in Brazil in the last fiscal year, excluding taxes
- Fallback (Art. 52, S4): If branch-specific revenue is unavailable, incomplete, or unreliable, ANPD may use total company/group revenue
- Destination (Art. 52, S5): Fine proceeds go to the Fundo de Defesa de Direitos Difusos (Fund for the Defense of Diffuse Rights)
Daily Fine (Art. 54)
- Must be proportional to the severity of the violation and extent of damage
- Subject to the same R$ 50M total cap
- Notification must include: description of obligation, reasonable deadline for compliance, daily fine amount
Methodology (Art. 53)
ANPD publishes dosimetry methodologies via regulation (Resolucao CD/ANPD no 4/2023). These must:
- Be published in advance for transparency
- Present objective calculation forms and dosimetry criteria
- Contain detailed reasoning for all elements
- Establish conditions for choosing simple vs. daily fine
Dosimetry Methodology (Resolucao CD/ANPD no 4/2023)
Infraction Classification (Art. 8 of the Regulation)
| Class | Criteria |
| Leve (minor) | None of the média/grave hypotheses apply |
| Média (medium) | Can significantly affect data subjects' interests and fundamental rights: significantly impeding the exercise of rights or the use of a service, or causing material/moral damage (discrimination, violation of physical integrity, damage to image/reputation, financial fraud, identity misuse) — and not classified as grave |
| Grave (serious) | A média hypothesis plus at least one of: large-scale processing; economic advantage obtained or intended; risk to data subjects' lives; sensitive data or data of children, adolescents, or elderly; processing without any legal basis; unlawful discriminatory effects; systematic irregular practices — or obstruction of ANPD inspection |
Base Fine Value (Art. 11 of the Regulation)
The base value is calculated (methodology in Apendice I of the Regulation) from three elements:
- Infraction classification (leve/média/grave)
- Revenue of the infractor in the business segment where the infraction occurred, last fiscal year, excluding taxes — total company/group revenue is used when segment revenue is unavailable; with no documented revenue, ANPD applies absolute value ranges or presumed caps (Simples Nacional/startup limits)
- Degree of damage
Aggravating Percentages (Art. 12 of the Regulation)
Cumulative — percentages are summed when more than one applies:
| Circumstance | Increase | Cap |
| Specific recidivism (same type of infraction) | +10% each | 40% |
| Generic recidivism | +5% each | 20% |
| Non-compliance with orientation or preventive measure | +20% each | 80% |
| Non-compliance with corrective measure | +30% each | 90% |
Mitigating Percentages (Art. 13 of the Regulation)
Cumulative; burden of proof on the infractor. Cessation/mitigation done merely to comply with an administrative or judicial order does not count:
| Circumstance | Reduction |
| Ceased the infraction before ANPD opened a preparatory procedure | −75% |
| Ceased after the preparatory procedure, before the sanctioning process | −50% |
| Ceased after the sanctioning process, before the first-instance decision | −30% |
| Good practices and governance policy, or demonstrated internal damage-minimization mechanisms | −20% |
| Reversed/mitigated the effects on affected data subjects before any ANPD procedure | −20% |
| Reversed/mitigated after the preparatory procedure, before the sanctioning process | −10% |
| Cooperation or good faith | −5% |
Final Limits (Arts. 15 and 18 of the Regulation)
- Result cannot be below the minimum values of Apendice II — except when the advantage obtained is estimable, in which case the fine is at least double the economic advantage
- Result capped at 2% of revenue in Brazil / R$ 50 million per infraction
- Express waiver of the right to appeal + payment within the deadline grants an extra −25% on the final fine
- Late payment: Selic interest + 0.33%/day penalty capped at 20%
Aggravating and Mitigating Factors (Resolucao CD/ANPD no 4/2023)
Aggravating Factors
| Factor | Source |
| Non-compliance with ANPD preventive measures | Resolucao 4/2023, Art. 33, S2, II |
| Failure to cooperate during investigation | Art. 52, S1, VII LGPD |
| Obstruction of ANPD inspection activities | Resolucao 1/2021, Art. 38 |
| Processing of sensitive data or children's data | Art. 52, S1, I LGPD |
| Large volume of data subjects affected | Art. 52, S1, VI LGPD |
| Recidivism (prior sanctions for same type of infraction) | Art. 52, S1, V LGPD |
| Economic advantage obtained or intended from the violation | Art. 52, S1, III LGPD |
| Non-compliance with conformity plan | Resolucao 1/2021 |
| Failure to respond to ANPD requests | Enforcement precedent (all sanctions to date involved non-cooperation) |
Mitigating Factors
| Factor | Source |
| Good faith of the infractor | Art. 52, S1, II LGPD |
| Prompt adoption of corrective measures | Art. 52, S1, X LGPD |
| Full cooperation with ANPD during investigation | Art. 52, S1, VII LGPD |
| Demonstrated internal security mechanisms | Art. 52, S1, VIII LGPD |
| Adoption of good practices and governance policies | Art. 52, S1, IX LGPD |
| Small economic capacity (small-porte agent — Resolucao 2/2022) | Art. 52, S1, IV LGPD |
| Proposal and acceptance of Term of Conduct Adjustment (TAC) | Resolucao 1/2021, Art. 43 |
| No prior sanctions or infractions | Art. 52, S1, V LGPD (inverse) |
| Minimal or no harm to data subjects | Art. 52, S1, VI LGPD |
ANPD Enforcement Statistics
Complaints Received
| Year | Complaints in Year | Cumulative since 2021 |
| 2021 | 768 | 768 |
| 2022 | 1,047 | 1,815 |
| 2023 | 1,137 | 2,952 |
| 2024 | 4,029 | 6,981 |
Key Enforcement Insight
All sanctioning proceedings conducted by ANPD to date were initiated due to non-cooperative behavior by the regulated entity. Cooperation is the single most important factor in avoiding escalation from investigation to sanctions.
Active Investigations (Notable Cases, as of 2025)
| Entity | Scope |
| TikTok (Bytedance) | Children's/adolescents' data processing |
| Meta Platforms | Generative AI data processing |
| X Corp. (Twitter) | Generative AI data processing |
| Tools for Humanity (Worldcoin) | Biometric data processing |
| WhatsApp / Meta | Data sharing within Meta group |
| INSS / Dataprev | Data sharing for consigned loans |
| Claro / Serasa | Data processing compliance |
| RaiaDrogasil | Biometric data collection, transparency |
| FEBRAFAR (Pharmacies) | Personal data collected by associated pharmacies |
Sanction Precedents (Concluded Cases)
| Entity | Violation | Type |
| Telekall Infoservices | Non-compliance with ANPD determinations | Private company — first entity sanctioned by ANPD |
| Instituto Jardim Botanico do RJ | Failure to notify ANPD and data subjects of security incident; failure to respond to ANPD requests | Public entity |
| Secretaria de Educacao do DF | Missing incident notification to data subjects; no security measures proof; no processing records; no DPIA; failure to respond to ANPD | Public entity |
| Secretaria de Saude de SC | Missing incident notification to data subjects; missing security measures; non-compliance with ANPD determinations | Public entity |
| IAMSPE (SP) | Missing incident notification to data subjects; missing security measures | Public entity |
| INSS | Missing incident notification to data subjects; non-compliance with ANPD preventive measure | Public entity |
| Ministerio da Saude | Missing DPO designation proof; no DPIA; missing incident notification; failure to respond to ANPD | Public entity |
| Secretaria de Desenvolvimento Social (PE) | Missing incident notification; missing security measures | Public entity |
Pattern from Precedents
- Most sanctioned entities are public — because they cannot receive fines, ANPD applied warnings, publicization, and corrective measures
- Common violations: failure to communicate incidents, missing security measures, failure to respond to ANPD
- Non-cooperation is decisive — every single case escalated to sanctions involved refusal to cooperate with ANPD
Risk Classification Table
| Risk Level | Description | Examples | Likely Sanction |
| Low | Minor procedural gaps, no harm to data subjects | Missing DPO contact info on website; outdated privacy policy | Warning with deadline |
| Medium | Non-compliance with LGPD requirements, potential harm | No consent management system; missing processing records (ROPA); no DPIA for high-risk processing | Warning + corrective measures; fine if non-cooperative |
| High | Significant violations affecting data subjects | Security incident without notification; sharing data without legal basis; processing children's data without parental consent | Simple fine (up to 2% revenue / R$50M); publicization; data blocking |
| Critical | Massive violations, systemic non-compliance, sensitive data | Large-scale data breach with sensitive data; systematic obstruction of ANPD; processing biometric data without legal basis; recidivist violations | Maximum fine; daily fine; database suspension; processing prohibition |
Compliance Checklist to Reduce Sanction Risk
Governance (Mitigating Factors)
- DPO appointed by formal act and published — Written designation act + name and contact info publicly available (Art. 41 + Res. CD/ANPD 18/2024)
- Privacy governance program — Documented policies, procedures, internal controls (Art. 50)
- Processing records (ROPA) — Complete register of all processing activities (Art. 37)
- Data Protection Impact Assessment (DPIA) — For high-risk processing activities (Art. 38)
- Data processing agreements — Contracts with operators covering security and compliance (Art. 39)
Incident Response (Most Common Violation)
- Incident response plan — Documented procedure for detecting and responding to security incidents
- ANPD notification — Process to notify ANPD within 3 business days (Resolucao CD/ANPD no 15/2024)
- Data subject notification — Process to notify affected individuals when risk is significant
- Incident documentation — Record nature of data, affected subjects, measures taken, risks
Cooperation with ANPD (Most Critical Factor)
- Respond to all ANPD requests — Within stated deadlines, without exception
- Designate a contact point — Ensure ANPD can reach your organization at any time
- Preserve evidence — Maintain logs, records, and audit trails for ANPD inspection
- Adopt corrective measures promptly — When ANPD issues determinations, comply immediately
Security Measures (Art. 46)
- Technical safeguards — Encryption, access control, monitoring, vulnerability management
- Administrative safeguards — Security policies, training, access reviews
- Privacy by design — Security measures from the design phase (Art. 46, S2)
- Regular security assessments — Penetration testing, vulnerability scanning, code review
Small-Porte Agents (Resolucao CD/ANPD no 2/2022)
Small businesses, startups, and micro-enterprises may benefit from:
- Simplified processing records
- Simplified incident communication
- Flexible DPO requirements
- Extended deadlines for compliance
Note: ANPD may revoke these benefits based on the nature, volume, or risk of processing (Art. 16, Resolucao 2/2022).
Enforcement Process Overview
| Phase | What Happens | Your Action |
| 1. Monitoring | ANPD collects info from complaints and public sources | Ensure public-facing compliance (DPO, privacy policy) |
| 2. Investigation | ANPD requests documents and clarifications | Respond fully and within deadline |
| 3. Preliminary assessment | ANPD issues technical note with determinations | Comply with determinations or justify disagreement |
| 4. Follow-up | ANPD verifies compliance with determinations | Demonstrate compliance with evidence |
| 5. Preventive measure | If non-compliant, ANPD issues formal preventive measure | Last chance before sanctions — comply immediately |
| 6. Sanctioning process | Auto de infracao (infraction notice) issued | Present defense within 10 business days; cooperate fully |
| 7. First-instance decision | CGF (Coordenacao-Geral de Fiscalizacao) decides | If sanctioned, may appeal to Conselho Diretor within 10 business days |
| 8. Appeal | Conselho Diretor reviews the decision | Final administrative instance |
Conciliation and Alternatives
Direct Conciliation (Art. 52, S7)
Individual data leaks or unauthorized access may be resolved through direct conciliation between controller and data subject. If no agreement is reached, ANPD sanctions apply.
Term of Conduct Adjustment — TAC (Resolucao 1/2021, Arts. 43-44)
- The regulated entity may propose a TAC to ANPD at any time
- Subject to Conselho Diretor approval
- Suspends the sanctioning process during compliance
- Process is archived upon full TAC compliance
- Strong mitigating factor in sanction dosimetry
References
- Lei 13.709/2018 (LGPD) — Arts. 52-54
- Resolucao CD/ANPD no 4/2023 — Dosimetria e Aplicacao de Sancoes
- Resolucao CD/ANPD no 1/2021 — Regulamento de Fiscalizacao e Processo Sancionador
- Resolucao CD/ANPD no 2/2022 — Agentes de Pequeno Porte
- Resolucao CD/ANPD no 15/2024 — Comunicacao de Incidentes
- ANPD — Sancoes Administrativas
- ANPD — Atividades Fiscalizatorias
- Portal da Transparencia — Sancoes ANPD
See Also
lgpd-compliance— Use for the full compliance framework. Understanding principles, legal bases, and security requirements helps prevent sanctions in the first place.digital-eca-compliance— ECA Digital has its own penalty regime (up to 10% of revenue, R$50M cap). Use when assessing risk for children's data violations.lgpd-document-generator— Having proper compliance documents (privacy policy, ROPA, consent forms) is a mitigating factor in ANPD dosimetry.marco-civil-compliance— Marco Civil violations (e.g., failing to retain logs, net neutrality breaches) are enforced separately but may compound with LGPD sanctions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

