ROPA — processing map
The company’s personal data processing operations (LGPD art. 37): activity, purpose, legal basis, retention, data categories and sharing.
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Consents and legal basis
Form fields
Atividade*
Finalidade*
Base legal*
Retenção
Categorias de dados
Compartilhamento
Start here
The processing map (ROPA)
Each row is one processing operation (art. 37): the activity, the purpose, the legal basis, how long the data is kept, which data categories go in and with whom they are shared. It is the document the data protection authority asks for in an inspection. The top search looks in the text fields; the Filters button opens the side panel with the cuts; the combination can be saved as a view and reopened with one click, and the gear picks the columns. In the ⋮ menu, Excel and PDF take the whole filtered set — not just the page on screen — and "export everything" asks for your password. What you do with each record is on the row buttons; the eye opens the detail on the side. Delete sends it to the trash, with Undo.
The processing operation record
Activity, purpose and legal basis are required. In Retention write the period and the trigger ("5 years after the contract ends"); in Data categories, what goes in (name, tax ID, e-mail…); in Sharing, who the data goes to — accountant, carrier, payment gateway.
Rules
Tratamento sem base legal não é salvo
Toda atividade precisa de finalidade, base legal (art. 7º ou 11) e prazo de retenção. Atividade sem base legal não grava — é o mínimo que o relatório de transparência e a resposta ao titular exigem.
Frequently asked questions
Preciso cadastrar um tratamento para cada tela do sistema?
Não. O ROPA descreve ATIVIDADES de tratamento (folha de pagamento, cobrança, marketing), não telas. Uma atividade cobre várias telas e tabelas; o que a lei pede é finalidade, base legal, retenção e categorias de dados por atividade — é isso que a tela guarda e que o relatório de transparência lê.
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.