The encarregado is the LGPD’s most visible obligation and its cheapest fix: a required, published point of contact that any regulator, journalist, or plaintiff can check by loading your website. Brazil made the duty universal where Europe made it conditional, then, in Resolution 18/2024, made it flexible: outsourced, shared, foreign, individual or firm, so the absence of one is hard to excuse. The first company the ANPD ever fined was cited for exactly this.
| Provision | LGPD Art. 41; ANPD Resolution 18/2024 |
|---|---|
| Who | All controllers (small agents: contact channel instead) |
| Form | Individual or legal entity; internal or outsourced |
| Publication | Identity + contact, easily accessible |
| Core duties | DSR intake, ANPD interface, staff orientation |
Standing the role up properly
Appoint by formal act, publish immediately. A documented appointment plus a monitored contact on the privacy notice closes the externally visible gap; wire the same inbox into the 15-day DSR pipeline so publication and performance match.
Choose for autonomy, not seniority. Legal, compliance, or an outsourced specialist beats a conflicted product executive; document the conflict analysis either way.
Give the role teeth. Access to the data map and lawful-basis register, sign-off on RIPDs, a training calendar, and a direct line to leadership, the elements Resolution 18/2024 expects the controller to guarantee.
Foreign controllers included. No Brazilian entity does not mean no encarregado; see the US-company guide and the LGPD vs GDPR comparison for how the duty differs from Article 37 practice.
Whether your DPO contact is actually published and reachable is checkable from outside, along with your consent behavior: run a free scan.