Privacy and data subject rights
When an employee, former employee, or customer asks "I want a copy of my data" or "delete what you have about me," this is where the request becomes a fulfilled response — with proof.
The screen
The real screen, in the theme you picked above.

What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Export dossierAnonymizeDownload the full package
Form fields
AçãoO que foi feito com o dado: consulta, alteração, exportação ou exclusão.
OrigemEm que cadastro o evento aconteceu, para localizar o titular do dado.
CampoQual informação foi tocada. É o que separa acesso banal de acesso a dado sensível.
Valor anteriorConteúdo antes do evento, para provar o que existia.
Valor novoConteúdo depois do evento, para provar o que passou a existir.
UsuárioQuem executou a ação sobre o dado pessoal.
TitularDe quem é o dado que foi acessado. É por aqui que se atende pedido de titular.
Acesso em nome de outroMarca que alguém entrou personificando outro usuário. É a linha que sempre se explica primeiro.
Start here
What it's for
The LGPD gives data subjects the right to receive a copy of everything the company holds about them (portability) and to be erased when there is no longer a reason to keep the data. This screen carries out both with one click, records who did it, when, and why — and the protocol field is your proof that the request was handled within the deadline.
How to
Exportar e anonimizar são verbos DIFERENTES de permissão
The export button depends on VIEW: handing the data subject what is already theirs is reversible. The anonymize button depends on DELETE, because it de-identifies permanently. That's why whoever administers the account received export access without receiving anonymization access — a verb is granted by looking at what the button does, not at the screen's subject.
Export everything, without going through support
"Download the complete package" takes records, chart of accounts, centers, 24 months of receivables/payables and the attachments, in open CSV. It's the portability policy: the data is yours and leaving never depends on asking permission or paying a fee.
Person on the uniform list
The employee or student the client put on the uniform contract list is also a data subject. The client of the contract decides about the data; you process it on their behalf. When the client passes on a request from the person, choose them here: the report brings their line and the record of who admitted them or changed their size; anonymizing replaces the name with a marker and erases the staff number and embroidered name. Without a request, this happens on its own 180 days after the contract ends or the person leaves (Parameters: uniform list period).
Rules
Why anonymization can be refused
The LGPD itself (art. 16) requires data to be KEPT when another law demands its retention — payroll and tax documents have their own legal retention periods. The system applies these deadlines automatically: if the retention period has expired, it anonymizes; if not, it refuses and explains until when the data needs to exist. The refusal is also logged in the trail — refusing within the law is fulfilling the request, not ignoring it.
Anonymizing cannot be undone
De-identification permanently overwrites the name, CPF, and contact information. The statistical record continues to exist (the financial and payroll history does not disappear), but the person is no longer identifiable. Confirm you have the right data subject beforehand — the screen asks for explicit confirmation precisely because there is no undo.
De onde vem o dossiê
The export scans the tables that hold the person's data (registration, payroll, transactions, logs) and generates a single file. Deliver it to the data subject through a secure channel — the file contains exactly what the law says they have the right to receive, that is, everything.
O dossiê leva os arquivos, não só a lista deles
The package comes out as a ZIP: dossie.json with all of the data subject's data, the anexos/ folder with the actual files and the index anexos.csv. Before 08/19/2026 only the index came out — and the signed contract, the receipt and the medical certificate were left behind. Under the LGPD, the attached document IS personal data: it has to come out in the portability request.
Se um anexo não couber, o índice diz — nunca corta calado
The package has a size cap (parameter EXPORT.LIMITE_ANEXOS_MB, 200 MB by default). An attachment that doesn't fit stays listed in anexos.csv with the "incluido" column set to "nao" and the reason written. A package silently truncated would be read as "everything came" — and that's exactly what can't happen in a data subject's request.
Individual supplier
An individual supplier (the contractor, the self-employed) is a data subject: they can request a file with their data and be anonymised through this screen. Contractor network data has a retention period and is removed when it expires.
Frequently asked questions
What about deadlines that run on their own?
This screen is the ON-DEMAND service. Automatic deadlines (expired candidate résumés, an employee in the trash bin past the labor-law retention period, old logs) run every day in the scheduled purge, without depending on anyone remembering.
Por que a anonimização às vezes é recusada?
The LGPD (art. 16) allows keeping data when another law requires retention — payroll and tax documents have their own period. The screen applies those periods on its own: if the retention period has expired, it anonymizes; if not, it explains until when the data needs to exist. A refusal due to legal retention is not a system error, and it stays in the trail as ANONIMIZACAO_RECUSADA.
How do I handle a request from someone who asked for the demo?
In the Demo prospect panel, pick the person by name or e-mail. Export dossier delivers everything we keep about them: the links requested, the screens they saw, the contact score and the access-limit warnings. Anonymize erases name, e-mail and screens from every link of that e-mail and erases the contact's data.
Was this article helpful?
In the same module: Governance and compliance12
DRE tree viewThe DRE navigable by nature (account category): open the line and drill down to the entry that formed it. It'…Central LGPDOs documentos vivos da proteção de dados com estado e data — DPA, RIPD, runbook de incidente e conformidade d…Advance receivablesReceivables advancing as a BUTTON: the not-yet-due receivable invoices already in your accounts receivable tu…Email queueEverything the system tried to send by email: what went out, what failed and why.Service order mapDistributes service orders on the map by technician and region to build the day's schedule without overlap. T…LGPD management (old address)Old address of LGPD management: opens and goes on to the consent list.Error logThe exceptions the system recorded: when, on which screen, with which user, and what the technical failure wa…SDCA routineStructures the improvement routine (Standardize–Do–Check–Act) around a process. The cycle only closes if the …
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.