Sensitive data under Brazil's LGPD: what it is, real examples, and how to handle it in your company's records
Sensitive data under Brazil's LGPD: what the law defines as sensitive, real HR and customer examples, and how to handle it safely.
Sensitive data under the LGPD (Brazil's General Data Protection Law) is a category of personal data that the law treats with more care than the rest of a company's records, because exposing this data can lead to discrimination, embarrassment, or real risk for the person involved.
The LGPD, in article 5, item II, lists what falls into this category: racial or ethnic origin, religious belief, political opinion, membership in a trade union or in a religious, philosophical, or political organization, data concerning health or sex life, genetic data, and biometric data when linked to a natural person.
Notice that the list is closed. It is not the company that decides what counts as sensitive, it is the law. And handling this data comes with a stricter rule for legal basis, consent, and security, set out in article 11.
Where sensitive data shows up in your company's records
Few companies stop to think they have sensitive data moving through their systems. But it is there, inside the records everyone uses every day.
In years spent implementing registration systems, I have seen medical certificates attached to the same employee record that any manager can open without restriction. In HR, sensitive data sits in the medical certificate, the pre-employment exam, the periodic exam, the disability information used for hiring quotas, and sometimes even in the biometric data used for time clocks.
In the customer records of health plans, insurers, and banks, it sits in claims history, in the health declaration for a life insurance policy, and increasingly in the facial biometrics used to open an account or release credit.
In companies with diversity programs, it sits in the racial self-declaration linked to the employee record, used to measure quotas and targets, and it needs far more careful handling than a job title or a salary.
And there is a point that gets missed. Many registration systems store this kind of information in the same place where any manager, with any level of access, can open the person's full record. Sensitive data does not get the separate access control the law requires.
Who answers for that data inside the company
The data protection officer, the DPO, answers for LGPD compliance as a whole, but does not register anything alone.
HR registers the medical certificate. The sales team or the broker registers the insurance health declaration. The product or support team registers the customer's biometric data. Every area that collects sensitive data in its own process decides whether that field stays exposed to everyone or only to the people who need to see it.
This is where the data steward comes in, the owner of the data within the business area. Together with the DPO and the technology area, the steward defines which field is sensitive, who can access it, how long the data is kept, and when it needs to be anonymized or deleted.
Without that role defined, sensitive data becomes everyone's responsibility, which in practice means nobody's.
Which tools help identify and protect sensitive data
The first step is finding where the sensitive data lives. Data cataloging and classification tools, such as Microsoft Purview, Collibra, and Alation, run that automatic scan across databases and systems, tagging field by field according to the type of information.
The second step is controlling access once the data has been found. Data governance and quality platforms, such as Informatica, Ataccama, and SAP Master Data Governance, let you mask the sensitive field, restrict who sees the full value, and log who accessed what and when.
For customer and employee master data, MDM tools such as Stibo Systems, Reltio, Semarchy, and Profisee help keep that field under the same governance standard applied to the rest of the record, instead of leaving sensitive data in a loose attachment outside central control.
No tool solves this on its own. The software shows where the risk sits. Deciding the access rule and enforcing it is the company's job.
How to get ready to handle this kind of data
There is no one-day course that solves this. The path runs through understanding data governance broadly, studying the LGPD's own text, especially articles 7 through 11, and learning the specific legal bases for sensitive data, which are stricter than the bases for common personal data.
The DAMA-DMBOK is the international reference for data management and devotes a full chapter to data security and privacy, including sensitive data. The CDMP certification, from DAMA itself, tests exactly that knowledge, alongside governance, quality, and data architecture.
Anyone already working in compliance, HR, or IT who wants to specialize in data governance has a natural path ahead, because demand for people who understand LGPD as it applies to real records, not just the law in theory, keeps growing.
The opportunities for people who master this subject
Data protection officer, privacy analyst, data steward, and governance analyst are the roles asking for this knowledge the most right now. Mid-size and large companies no longer hire just a lawyer to handle LGPD. They hire people who understand records, systems, and process, because that is where sensitive data actually lives.
This professional does not memorize legal articles. They sit down with HR, with sales, and with IT, and translate the legal requirement into a system field, an access rule, and a routine for discarding the data once it is no longer needed.
Frequently asked questions about sensitive data under the LGPD
Is a CPF a sensitive data point? No. A CPF (Brazil's individual taxpayer ID number) is common personal data, though it requires care because it is a unique identifier. Sensitive data is the closed list in article 5, item II: racial or ethnic origin, religious belief, political opinion, trade union membership or membership in a religious, philosophical, or political organization, health, sex life, genetic data, and biometric data.
Is a minor's data always sensitive data? Not necessarily. Children's and teenagers' data get reinforced protection for a different reason, under article 14 of the LGPD, which requires specific consent from a parent or legal guardian. That is a different layer of protection from sensitive data, and the two can stack on the same record.
Can I just ask for consent on everything and solve the sensitive data problem? Specific, highlighted consent is one of the legal bases, but it is not the only one, and it is not always the most appropriate. For health data tied to an HR benefit, for example, the basis is often performance of a contract or compliance with a legal obligation, not consent.
Is facial biometrics for access control sensitive data? Yes, when it uniquely identifies a natural person. An ordinary security camera that only records footage, without facial recognition linked to a record, does not fall into this category. What changes everything is the link between the image and the person's identity inside the system.
What is the real risk of mishandling sensitive data? Beyond the LGPD fine, which can reach 2% of a company's revenue in Brazil, capped at 50 million reais per infraction, the bigger risk is usually reputational. A leak of health data or belief-related data becomes news fast, and customer or employee trust does not come back easily.
MDM Academy
MDM Academy is 4MDG's school for data governance and master data. It was built to train people who deal with records, compliance, and data every day, with no time or patience for a generic course that talks about data without ever opening a real system.
The program treats LGPD, data quality, master records for materials, customers, and suppliers, and master data governance as connected disciplines, because that is how they show up inside a real company. Graduates leave with the right vocabulary, the right standard, and a clear sense of how to apply all of it to their own records, not just in theory.
MDM Academy lessons and materials are in Portuguese. You can take the program from any country, and an English version is on our roadmap, with no committed date. The certificate is issued in Brazil, in Portuguese, and is valid in Brazil.
If you want to learn more about MDM Academy or exchange experience with other people facing the same records problem, join our Data Club, our free WhatsApp group: https://chat.whatsapp.com/H4RudT3peYA1PDBAgOFqXG
Conclusion
Sensitive data is not an isolated chapter of the LGPD for the legal team to handle alone. It lives inside the same customer, supplier, and employee records your company already uses every day, usually without the access control the law requires.
Handling it properly starts with a simple question: who in your company knows exactly which record fields hold this kind of data right now? If the answer took a while to come, that is the first problem to solve.
Want to become a data governance specialist? Talk to our specialists now and get to know MDM Academy
I want to be a student
