Service Data governance
LGPD compliance from the data side: mapping, governance and security
For companies that have published a privacy policy but cannot say where their personal data lives: we locate that data in your systems and databases, put governance around it and define security measures according to the risk of each database. Legal matters stay with your in-house counsel or the advisers you choose.
Summary
What tends to go wrong
The privacy policy has been published, but personal data is still scattered: in production tables, in test copies, in shared spreadsheets, in old backups. Nobody can say with confidence which systems store tax IDs, who looks at that information or how long it is kept, and those are exactly the questions a data subject, a customer or the national authority (ANPD) may ask.
Who it is for
Companies that process personal data of customers, employees or suppliers under Brazil's General Data Protection Law (LGPD) and need to put it into practice inside their systems: executives, data protection officers, legal and IT teams who want to know where that data lives and who can reach it.
Deliverables
What gets delivered
- An inventory of personal data by system and database
- A gap and risk report with a prioritized action plan
- A design of the governance processes, with named owners
- Security measures implemented according to the approved plan
- Technical material supporting legal and the data protection officer
- Matrix of approved sources by purpose and profile, with named approvers and a procedure for updates, revocation and deletion
Steps
How the engagement runs
Assessment
Understanding the systems, the departments that handle personal data and what has already been done.
Mapping
A technical inventory of the databases and conversations with each department.
Priorities
Gaps ranked by risk and aligned with your legal team.
Implementation
Governance and security measures rolled out in stages.
Review
Regular reviews so the inventory does not go stale, when ongoing support is in place.
Roles
Who takes care of what
Trustwise
Technical mapping, risk assessment, governance design and implementation of security measures.
Your legal team or advisers
Legal bases, privacy notices, contracts, dealings with the ANPD and legal guidance.
Your company
Appointing the data protection officer, deciding how data is processed and involving each department in the review.
Engagement
Where to start
The starting point is an assessment of how personal data is handled in your systems. From there, the proposal, either a project or ongoing support, sets out what will be implemented and how the work is split between Trustwise, your IT team and your legal team. Commercial terms are set out in the proposal.
Scope
What is included
-
Personal data mapping
Finding where personal data sits across databases, systems and files, how it flows and who has access.
-
Risk and gap assessment
Comparing current processing with what needs to change, with the adjustments ranked by risk.
-
Data governance
Governance and management processes around personal data, so control continues after the project.
-
Personal data security
Technical protection measures chosen to fit each system's context and the sensitivity of the data.
-
Technical material for legal
Inventory and technical evidence that support the record of processing activities and responses to data subjects.
-
Approved sources for AI
Inventory, classification, retention and access control extended to the sources an AI project intends to use.
Warning signs
Signs that compliance never left the paperwork
Finished documents do not mean the systems are under control.
- A published policy, but no inventory of where personal data is stored
- Nobody can say who accesses the tables holding tax IDs, health or financial data
- Copies of production with real data used in test environments
- No retention rules: old data kept indefinitely
- Trouble gathering all the data held on a data subject when they ask for it
Technical and legal
What Trustwise covers and what stays with legal
LGPD compliance has a technical side and a legal side, and the two need to move together. Trustwise works on the data and technology side. Defining legal bases, drafting notices and contracts, dealing with the ANPD and giving legal answers to data subjects are the job of your in-house counsel or the advisers your company appoints.
Trustwise does not provide legal services.
Mapping
How the mapping is done
We start with the databases, where the volume is: we identify the tables and columns holding personal and sensitive data, who has permission on them, where they are copied to and how long they are kept. We then cross-check that with conversations in the departments that use the data, to understand the purpose of each processing activity. The result is an inventory your legal team and data protection officer can use as a starting point.
Protection
Technical protection measures
Which measures fit depends on the risk of each database. These are the ones usually discussed.
- Permission review and access control on tables holding personal data
- Encryption of sensitive data
- Masking of personal data in test environments
- Access auditing
- Protected backups
Data and AI
Which sources an AI project may use
Before an assistant or an AI pilot reads company databases and documents, the inventory, classification, retention rules and access control need to cover those sources. We handle the technical side of that decision; the legal assessment of each purpose stays with the person your company designates.
- A matrix of approved sources by purpose and access profile
- Named owners who approve each source
- A procedure to update, revoke and delete data from a source already in use
This work supports technical compliance; it does not replace legal analysis and is not a certification.
Technologies
Platforms and tools
- SQL Server security features: permissions, encryption, masking and auditing
FAQ
Questions we often hear
Does Trustwise replace our legal team or data protection officer?
No. Trustwise handles the technical side: where the data is, who reaches it and how it is protected. Interpreting the law, legal bases, contracts and communication with the ANPD stay with your in-house counsel or the advisers you choose. The work goes best when both sides are involved from the start.
Where do we start if we have done nothing yet?
With mapping. Without knowing what personal data the company holds, where it is and who accesses it, any policy stays generic. The initial assessment shows the size of the job and the priorities.
Does data in test environments count too?
Yes. A copy of the production database used for testing carries the same personal data, usually under looser access control. Masking or anonymizing that data is an important technical measure that is often overlooked.
Does the LGPD require encrypting everything?
The law calls for technical and administrative security measures able to protect the data, without listing mandatory technologies. The choice depends on risk: encryption, access control, auditing and protected backups are combined according to how sensitive the data is and how each system is used. The legal reading of your case belongs to your legal team.
Does the work end when the project ends?
The inventory ages with every new system, integration or process change. That is why governance assigns owners and regular reviews, which your team can run or which can continue under ongoing support from Trustwise.
Can we put documents containing personal data into an AI assistant?
It depends on the purpose, the legal basis and who will query the assistant. On the technical side, the question is which sources are approved for that use, who can see each one and how to withdraw a document or revoke access. The source matrix answers that; the legal decision stays with the person responsible at your company.