> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-fairbid/privacy/lgpd.md).
# LGPD
The Brazilian General Data Protection Law, the Lei Geral de Proteção de Dados Pessoais ([LGPD](https://www.gov.br/anpd/pt-br/centrais-de-conteudo/outros-documentos-e-publicacoes-institucionais/lgpd-en-lei-no-13-709-capa.pdf)), sets guidelines for collecting and processing personal information from individuals in Brazil. LGPD requires that you only process personal data for legitimate, specific, explicit, and clearly communicated purposes as defined by the Brazilian Data Protection Authority (ANPD).
Digital Turbine applies internal processes to anonymize user data and retain the data's value while protecting user identity. In addition, Digital Turbine flags its demand partners and mediated ad networks when a user declines LGPD consent and does not wish to receive targeted ads in the app.
## LGPD SDK APIs
All SDKs include APIs to communicate user consent provided to DT and share their consent to DT's demand partners and mediated ad networks.
{% hint style="info" %}
To comply with LGPD requirements, update the DT SDK in your app. DT also recommends notifying your users to update the app to maintain compliance.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.digitalturbine.com/dt-fairbid/privacy/lgpd.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.