> 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/gdpr.md).

# GDPR

The General Data Protection Regulation act (GDPR) sets guidelines for the collection and processing of personal information from individuals who live in the European Union (EU).

DT has implemented internal processes to anonymize user data in a way that still makes it useful for you, while ensuring that user identity is protected.

In addition, DT flags its demand partners and/or mediated ad networks, when the user did not provide the consent required under GDPR and does not wish to be served with targeted ads on the app.

{% hint style="info" %}
All DT SDKs were updated prior to May 25, 2018.
{% endhint %}

## GDPR SDK APIs <a href="#gdpr-sdk-apis-0-0" id="gdpr-sdk-apis-0-0"></a>

All new SDKs include new APIs to communicate user consent provided on the app to DT and also include features to propagate consent to DT’s demand partners and mediated ad networks.

Updating your apps to DT’s latest SDKs is **essential** to ensure your compliance with GDPR.

{% hint style="success" %}
We strongly recommend notifying your users that they must update their app to the latest version to ensure compliance with GDPR.
{% endhint %}

## GDPR FAQs <a href="#gdpr-faqs-0-2" id="gdpr-faqs-0-2"></a>

<details>

<summary>Will I have to update to the new SDK if I have already signed DT’s DPA?</summary>

Yes, we’ll ensure you’re GDPR compliant regardless of which SDK version you have, but in order to ensure you’re not limited on ad monetization potential, we recommend updating to the latest SDKs.

</details>

<details>

<summary>I need more time to present my own consent form to users, what happens in the meantime?</summary>

No worries, you are still in compliance. However ad monetization in EU may be severely impacted as user consent is crucial for most advertisers.

</details>

<details>

<summary>What happens if a user withdraws their consent?</summary>

The publisher should provide the user with an option in the app or site to withdraw consent. The DT FairBid SDK reads consent once, when the SDK starts, and ignores later changes. The SDK does not apply a withdrawal made while the SDK is running. After the user withdraws consent, the app must restart, and the app must set the withdrawn consent before starting the SDK again. For details, see [GDPR](/dt-fairbid/fairbid-sdk/sdk-reference/gdpr.md).

</details>


---

# 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/gdpr.md?ask=<question>&goal=<user_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.