// Security compliance
LGPD for AI-built SaaS
What LGPD asks of security
LGPD (Law 13.709) is Brazil’s personal data protection law. It is not a certification: it is a continuous legal obligation. Article 46 requires technical and administrative security measures to protect personal data from unauthorized access, loss, alteration and leakage. Sensitive data (health, biometrics, race) and minors’ data get reinforced protection (Art. 11 and Art. 14).
The legal part (legal basis, consent, policy, DPO, responding to the ANPD authority) is your legal team’s and data officer’s job. The technical part, proving the data is actually protected, is where RET fits.
What that means technically
Article 46 becomes, in practice, a set of technical controls that have to truly work in a SaaS.
- Per-customer isolation: one subject’s data must not leak to another (IDOR and tenant failures are LGPD incidents).
- Role-based, least-privilege access to personal data.
- Protection in transit and at rest, and secrets out of the client bundle.
- Logs that do not expose PII, and a trail to detect and respond to incidents.
Where RET fits
RET does NOT handle LGPD legal compliance (that is your DPO’s and lawyer’s job). What RET does is prove technically that the Article 46 measures exist and hold: a Risk Review to read the flows that touch personal data and a Manual Pentest to prove isolation and access control, with evidence. It is the technical base of your compliance, not the legal opinion.
Where to start
Start with the Promptbook to fix the obvious, run a Risk Review to map where personal data flows, and use the Manual Pentest when you need to prove isolation and access (a B2B sale, due diligence, incident response). AuditMySaaS helps monitor continuous change.
Want to know whether this happens in your system?
Manual pentest for web applications, APIs and apps, from R$9,500, with the Sprint run within 7 business days. We refund 50% if we find no flaw.
Frequently asked questions
Does RET make my SaaS LGPD-compliant?
RET covers the technical part (Art. 46): isolation, access control, data protection, proven with evidence. The legal part (legal basis, policy, DPO, ANPD) is your legal team’s. LGPD compliance is the sum of both.
Is a data leak a technical or legal problem?
Both. The cause is usually technical (IDOR, isolation failure, exposed secret), and the consequence is legal (ANPD notification, fine, harm). RET attacks the technical cause before it becomes the consequence.
Does sensitive data change anything?
It does. Health, biometric and minors’ data get reinforced protection (Art. 11 and 14). Isolation and access control must be airtight, and technical review weighs more on those flows.
Who runs the review at RET?
Gabriel Lima Ferreira, founder and lead pentester, with an authorized scope and reproducible evidence.
Keep reading
Threat and defense
MCP tool poisoning: how to prevent it
Practical guide
Multi-tenant isolation in SaaS
Threat and defense
Credential stuffing and MFA on the admin panel
Comparison
In-house pentester vs outsourcing the pentest
By tool
Security for apps built with Base44
By city
SaaS security and pentest in Curitiba (PR)