- ANPD guidance explaining confirmation, access, correction, deletion, portability, objection, and review rights that shape Brazil LGPD request workflows.
"confirmação sobre a existência de um tratamento de seus dados"
Data Subject Rights under the Brazil LGPD mean giving people a clear way to confirm, access, correct, delete, move, object to, or review how their data is handled.
Use this section to define the request type, owner, evidence, and timing before you respond.
Structured answer sets in this page tree.
Cited legal and guidance references.
This page explains the main LGPD rights in Article 18 and the response path in Article 19 so teams can handle requests with clear owners, evidence, and deadlines.
Start by identifying which Article 18 right is being requested: confirmation of processing, access, correction, anonymization, blocking or deletion, portability, deletion after consent, information about sharing, information about refusing consent, revocation of consent, or a complaint to the ANPD. The response should match the request and the legal basis for the data being processed.
For confirmation or access, Article 19 says the controller must respond immediately in simplified form or within up to 15 days with a clear and complete declaration. For practical handling, capture the request date, identity check, owner, response format, and any legal reason that limits full disclosure.
Ownership should sit with the team that controls the processing purpose and the customer channel that receives the request, with privacy or legal review when the answer depends on an exception or a conflict with another legal duty.
Evidence should show the request log, identity check, the Article 18 right involved, the response sent, the date of response, and any action taken to correct, delete, block, or share the request with other controllers when required.
Most LGPD mistakes happen when teams miss the difference between a full access request and a narrower correction, deletion, or portability request, or when they fail to identify whether another law limits disclosure.
Apply this section before approving a response. If the request involves another controller, a public-body process, a child-data request, or a decision on automated profiling, route it for legal review and keep the request open until the response can be accurate.
Use a simple workflow that logs the request, confirms identity, identifies the Article 18 right, assigns an owner, and records the answer date. For confirmation or access, the reply should be immediate in simplified form or within up to 15 days as a clear and complete declaration.
Where the request requires action, the workflow should also trigger correction, deletion, blocking, anonymization, portability, or sharing of the request with other controllers when the law requires it.
This artifact page provides practical inputs, owner roles, required outputs, and evidence checkpoints for data subject rights.
Turn Data Subject Rights 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.
"confirmação sobre a existência de um tratamento de seus dados"
"Art. 19. A confirmaçao de existência ou o acesso a dados pessoais serao providenciados, mediante requisiçao do titular"
"Portaria ANPD Nº 35, de 4 de novembro de 2022"
"petição de titular: comunicação feita à ANPD pelo titular de dados pessoais"
"Esta Resolução CD/ANPD nº 4, de 24 de fevereiro de 2023, trata da aplicação de sanções administrativas"