- ANPD incident guidance explains how Article 48 LGPD and Resolution 15/2024 apply to controller communications to ANPD and affected data subjects.
"prazo de três (3) dias úteis"
Incident Reporting To Anpd decisions under the Brazil LGPD should be written in operational language: who is in scope, what must happen, what evidence proves it, and when escalation is needed.
Use this section to define scope, owner, evidence inputs, and the review outcome before execution.
Structured answer sets in this page tree.
Cited legal and guidance references.
Use this page to decide when a security incident must be reported to the ANPD and affected data subjects, who should make the call, what evidence should be recorded, and how to document the response in plain operational terms.
Start by deciding whether the issue affects controller/operator roles, lawful basis, data-subject rights, children data, international transfers, security incidents, DPO/encarregado duties, or ANPD enforcement exposure. The useful answer should name the exact trigger, affected product or process, required action, owner, evidence, and escalation point.
For incident reporting, the practical trigger is a confirmed security incident involving personal data that may cause risk or relevant damage to data subjects. Article 48 of the LGPD requires the controller to communicate the incident to the ANPD and to the holder, and ANPD guidance says not every incident qualifies; the report is for events such as unauthorized, accidental, or illicit access, destruction, loss, alteration, leakage, or other inadequate or illicit treatment that can create risk or relevant damage. If the incident qualifies, the report should also be sent within the deadline defined by the ANPD guidance source.
Keep the LGPD source, role map, lawful basis analysis, data-subject-right record, transfer basis, incident assessment, and ANPD-facing evidence together.
Ownership should sit with the team that controls the processing purpose, data-subject channel, vendor relationship, transfer mechanism, security incident response, or ANPD communication.
Evidence should show controller/operator mapping, lawful basis, transparency notice, rights response, transfer analysis, incident decision, DPO involvement, and ANPD remediation record where applicable.
Most LGPD mistakes happen at the boundary between controller and operator duties, consent and other lawful bases, academic or public-interest processing, international transfers, and incident notification thresholds.
Apply this section before approving a processing activity, vendor arrangement, transfer, rights workflow, child-data handling, or incident response under LGPD. If evidence is missing, block progression and raise a review task.
Use an LGPD workflow that captures role, purpose, lawful basis, data category, data-subject right, transfer or incident trigger, DPO review, evidence, and review date.
The output should be a lawful-basis memo, role map, privacy notice update, DSAR record, transfer note, incident assessment, or ANPD response pack.
This artifact page provides practical inputs, owner roles, required outputs, and evidence checkpoints for incident reporting to anpd.
Turn Incident Reporting To Anpd into scoped questions, evidence fields, and review tasks.
Use Research Copilot to answer follow-up questions with cited source material.
Review scope, evidence, owners, and the next compliance actions with operational practice.
"prazo de três (3) dias úteis"
"Segurança da Informação para Agentes de Tratamento de Pequeno Porte"
"O controlador deverá comunicar à autoridade nacional e ao titular a ocorrência de incidente de segurança"
"processo de fiscalização e o processo administrativo sancionador"
"Esta Resolução CD/ANPD nº 4, de 24 de fevereiro de 2023, trata da aplicação de sanções administrativas e"