# Android

Having the user consent is essential to send sensible information like the IDFA/AAID. To prevent having to manually save the consent asked to the user and manually using it with our SDKs, we created a module helping you do it automatically.This module will gather the consent and will:

* Display a consent page (if needed)
* Save consent and reload it every time the application is launched.
* Save and check the validity of the consent. The validity duration is set to 13 months.
* Send a hit to our servers to record the consent.
* Enable or disable the SDK. (if used alongside the SDK)
* Add the categories automatically to the hits the SDK sends. (if used alongside the SDK)

{% hint style="success" %}
Privacy's Implementation Guide:\
<https://github.com/CommandersAct/AndroidV5/tree/master/TCConsent>
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.commandersact.com/features/consent-management/setup-guides/mobile-apps/android.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
